Advances in software inspections
IEEE Transactions on Software Engineering
Managing the software process
Experiences with defect prevention
IBM Systems Journal
On the economics of mass-marketed software
ICSE '97 Proceedings of the 19th international conference on Software engineering
Using Group Support Systems for Software Inspections
IEEE Software
Design-For-Debug in Hardware/Software Co-Design
CODES '97 Proceedings of the 5th International Workshop on Hardware/Software Co-Design
Representing variability in a family of MRI scanners
Software—Practice & Experience
An Empirical Investigation of the Key Factors for Success in Software Process Improvement
IEEE Transactions on Software Engineering
Supporting inspections with an electronic meeting system
Journal of Management Information Systems
Using Software Reliability Growth Models in Practice
IEEE Software
Exploring defect causes in products developed by virtual teams
Information and Software Technology
| Hi-index | 0.00 |
The software content in consumer electronics products has increased significantly in recent years. In the late 1980s, a high-end television set contained less than 64 Kbytes of ROM, while today's model often has more than 500 Kbytes. The expanding use of software in consumer electronics products calls for a more effective software-development process and the introduction of new technology. Until recently, the limited amount of software in consumer electronics products made it possible to deliver them without defects. Today, the amount of software contained in such products may reach 100,000 lines of source code. Organizations in the professional electronics industry have found how difficult it is to put a product of this size on the market without any defects.In 1991, Philips' CEO named a Software Process Improvement task force to focus on the increasing importance of software.We describe improvement activities undertaken at Philips Sound & Vision to meet the specific requirements of developing software for consumer electronics products at a time when the amount of software contained in each unit increased rapidly. In addition to improving its processes, the organization improved its requirements-and-design engineering architecture and its inspections, and it introduced metrics. We examine the results of these improvements in terms of effort and schedule overruns and defect density for three projects.