Certifying the reliability of software
IEEE Transactions on Software Engineering
Managing the development of large software systems: concepts and techniques
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Advanced Engineering Mathematics: Maple Computer Guide
Advanced Engineering Mathematics: Maple Computer Guide
An analysis of software project failure
ICSE '79 Proceedings of the 4th international conference on Software engineering
An Analysis Of Recurrent Software Errors In A Real-Time Control System
ACM '78 Proceedings of the 1978 annual conference
IEEE Transactions on Software Engineering
IEEE Software
How to Design Practical Test Cases
IEEE Software
Can a software project be like Einstein?
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
| Hi-index | 0.00 |
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.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.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.