- 1.Albrecht, A, J., and Gaffney, J. E. Software function, source lines of code and development effort prediction' A software science validation. IEEE Transactions on Software En~qineering, Vol, SE-9, No. 6, Nov. 1983, pp. 639-647.Google Scholar
- 2.Humphrey, W. S., and Sweet, W. L. A Method for Assessing the Software Engineering Capability of Contractors. Software Engineering Institute, Technical Report CMU/SEt-87-TR-23. Preliminary Version, September 1987.Google Scholar
- 3.Humphrey, Watts S., Manaaino the Software Process, Addison-Wesley Publishing Company, Inc., Reading, Massachusetts, 1989. Google ScholarDigital Library
- 4.Mogilensky, Judah and Stipe, Dennis. Apl31ying Reusability to Software Process Definition. Proceedinqs:of Tri- Ada '89, October 23-26,1989, ACM Order Number 825891, pp. 355-366. Google ScholarDigital Library
- 5.Mogilensky, Judah. Applying TQM to Software Development: Contel's Process Enhancement Program. PrQ- ceedinqs of the AIAA/ADPA/NSiA 1 st~lation~l Total Quality Management_SvmDosium, November 1-3, 1989, pp. 98-104.Google Scholar
- 6.Williams, Charles B. Creating an Integrated Software/ Systems Engineering Environment. ProceedinQs of the ~ixth Washinqton Ada Sympo_~ium ~WAda$. '89), June 26-29. 1989, pp. 89-95. Google ScholarDigital Library
Index Terms
- Approaches to upgrading software process maturity
Recommendations
Software system documentation process maturity model
CSC '93: Proceedings of the 1993 ACM conference on Computer scienceLow quality or missing documentation is a major cause of errors in software development and maintenance. We address this problem by proposing a 4-level Documentation Process Maturity model based on the Software Engineering Institute (SEI) Software ...
Measuring Maturity Goes beyond Process
We've historically determined an organizationýs process maturity by conducting a maturity assessment that evaluates whether key process areas are documented and practiced. We've assumed that the higher the maturity level, the more cost effective the ...
Comments