Managing the software process
Software engineering (3rd ed.): a practitioner's approach
Software engineering (3rd ed.): a practitioner's approach
TQM for information systems management: quality practices for continuous improvement
TQM for information systems management: quality practices for continuous improvement
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
Quantitative evaluation of software process improvement
Journal of Systems and Software
Software Quality Management and ISO 9001: How to Make Them Work for You
Software Quality Management and ISO 9001: How to Make Them Work for You
Hi-index | 0.00 |
In an era of rapid information exchange, the use of computers apparently becomes a necessity both at work in order to get the jobs done and at home for leisure and entertainment purposes. To support the pace of massive computerisation, the need for on-time, cost effective and high quality software is ever increasing. With the turn of the century, software re-engineering exercises are being actively pursued in enterprises of all magnitudes worldwide. The software process improvement (SPI) program is among one of the contemporary approaches commonly adopted for rationalising the capability and performance of software development and maintenance in an enterprise. This paper explains the basic principles behind SPI and outlines the features and characteristics of some of the SPI models commonly used in the industry. The functional, organisational and resources implications of implementing the models are discussed. A real-life case study is given to illustrate how an SPI program was put into practice in a medium-sized enterprise whose business well-being was underpinned by the quality, punctuality and cost effectiveness of its systems development activities.