Advances in software inspections
IEEE Transactions on Software Engineering
The cleanroom approach to quality software development
The cleanroom approach to quality software development
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
Introduction to the personal software process
Introduction to the personal software process
A framework for identifying software project risks
Communications of the ACM
Introduction to the team software process
Introduction to the team software process
A Discipline for Software Engineering
A Discipline for Software Engineering
Using A Defined and Measured Personal Software Process
IEEE Software
| Hi-index | 0.00 |
Technical issues are important for software work, but so are personal disciplines, teamworking skills, and application‐domain knowledge. Also, much like an artistic performance, first‐class software engineering requires constant practice, good technique, and effective coaching. The challenge of producing high‐quality large‐scale software products is substantial today and will be even more demanding in the future. Without concerted action, we cannot expect software organizations' capabilities to improve. To address these problems, the Software Engineering Institute (SEI) has developed the Personal Software Process (PSP) and the Team Software Process (TSP). This paper addresses the problems of software engineering and discusses the intellectual nature of software work. It then reviews the characteristics of this kind of work and describes the principal conditions for effective software performance. In the conclusion, the author makes some observations about the challenges ahead and the future actions required.