On building systems that will fail
Communications of the ACM - Special issue on LISP
Computer related risks
ICSE '97 Proceedings of the 19th international conference on Software engineering
Software aspects of strategic defense systems
ACM SIGSOFT Software Engineering Notes
Understanding process and the quest for deeper questions in software engineering research
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
Death March
Software Process Improvement: Blueprints versus Recipes
IEEE Software
Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968, Brussels, Scientific Affairs Division, NATO
The risks of large organizations in developing complex systems
ACM SIGSOFT Software Engineering Notes
A rational theory of system-making systems
ACM SIGSOFT Software Engineering Notes
Debugging debugged, a metaphysical manifesto of systems integration
ACM SIGSOFT Software Engineering Notes
Software maturity: design as dark art
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
One applies process improvement to the software development process to increase efficiency and decrease defects. Process improvement is not a one-shot deal. Theoretically processes can be improved continuously, forever, but... The belief that continuous improvement can continue forever is analogous to the belief that by continuously improving an automobile's efficiency, eventually the day will come when the driver is forced to stop every so often to pour off excess spontaneously created gasoline. Here, the limits are the laws of thermodynamics. For the software development process the limits are the constraints of the software development organization. To improve a software process past a certain point, the organization that hosts the process's context will need to be improved, and then the context that hosts 'that' organization's process, and so on.Aha! A recursive pattern!The recognition of having a recursive problem raises deeper questions about the nature of process and process improvement, which, for this paper, will be addressed in the context of the development of large, complex, information intensive systems. Systems of this type are the ones most prone to failure and thus should benefit most from process improvement.