A Framework for Process Maintenance

Software processes are now increasingly being recognized to be critical for software development and maintenance. Like software, software processes also need to be evolved lest they become obsolete. Consequently, it is important to maintain software processes such that their maturity would be improved and their decay over a period of time would be minimal. This paper presents a framework, called the process cycle, which can assist in supporting and controlling process maintenance. The process cycle incorporates engineering, management, performance, and improvement of processes by human agents subjected to desirable goals and policy constraints. Process maintenance is supported by incorporating feedback cycles so that processes, goals and policies can be assessed and improved. In particular this paper addresses the identification of the reasons why processes change, the overall process change process, and the issue of policy improvement. Furthermore, this paper assesses the applicability of the process cycle framework by relating it to current process maintenance practices. Only by a miracle can the quality of sofnvare product be better than that of the process that produced it and that maintains it satisfactory as the application and its operational environment evolve. Quality sofnvare is the output of a quality process.

[1]  Victor R. Basili,et al.  The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..

[2]  Meir M. Lehman,et al.  Software engineering, the software process and their support , 1991, Softw. Eng. J..

[3]  Watts S. Humphrey,et al.  The Role of Assessment in Software Process Improvement , 1989 .

[4]  Meir M. Lehman,et al.  A Model of Large Program Development , 1976, IBM Syst. J..

[5]  Watts S. Humphrey Software and the factory paradigm , 1991, Softw. Eng. J..

[6]  Nazim H. Madhavji,et al.  The process cycle [software engineering] , 1991, Softw. Eng. J..

[7]  D. J. Frailey,et al.  Defining a Corporate-Wide Software Process , 1991, Proceedings. First International Conference on the Software Process,.

[8]  Nazim H. Madhavji The Prism model of changes , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[9]  A. Nico Habermann,et al.  The Engineering Institute: Bridging Practice and Potential , 1985, IEEE Software.

[10]  Shari Lawrence Pfleeger,et al.  Software metrics in the process maturity framework , 1990, J. Syst. Softw..

[11]  Watts S. Humphrey,et al.  The State Of Software Engineering Practice: A Preliminary Report , 1989, 11th International Conference on Software Engineering.

[12]  Stan Rifkin,et al.  Software Engineering Process Group Guide , 1990 .

[13]  Douglas C. Schmidt,et al.  Metric-driven analysis and feedback systems for enabling empirically guided software development , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[14]  Tarek K. Abdel-Hamid,et al.  Understanding the "90% syndrome" in software project management: A simulation-based case study , 1988, J. Syst. Softw..

[15]  Bill Curtis,et al.  On building software process models under the lamppost , 1987, ICSE '87.

[16]  Meir M. Lehman Programs, life cycles, and laws of software evolution , 1980 .

[17]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .