The Community for Technology Leaders
Green Image
Issue No. 05 - September (1995 vol. 12)
ISSN: 0740-7459
pp: 68-77
For decades, hardware capacity and the size of software systems have steadily increased. With such large and complex bodies of code at stake, we believe it is essential to separate software development and quality assurance. Unless you can separate the two, it is difficult to know what software quality is, and thus it is difficult to control it. You cannot manage what you do not know. <p>At Hitachi Software, we organize software projects in a way that retains high-quality software and improves scheduling. We do this by forcing "necessary" conflicts among independent groups within the larger software-development team. We believe that by creating a competitive atmosphere between the design and quality-assurance departments, engineers on both teams are motivated to be quality sensitive.</p> <p>From 1979 to 1992, software productivity at Hitachi Software rose 3.2 times, proof that reducing field failures can also increase productivity. In this article, we describe our software-development process and provide further advice for implementing sound quality-assurance into your own development cycles.</p>

A. K. Onoma and T. Yamaura, "Practical Steps Toward Quality Development," in IEEE Software, vol. 12, no. , pp. 68-77, 1995.
87 ms
(Ver 3.3 (11022016))