Marcello Visconti
ABSTRACT
Low 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 Development Maturity model. We believe our model will be a useful tool in assessing an organization's documentation level and identifying improvement areas to move the organization to the next level.
- Basi84.Basili, Victor R. and Perricone, Barry T. Software errors and complexity: An empirical investigation. Communications of the ACM, Vol. 27, No. 1, 1984. Google Scholar
Digital Library
- Basi91.Basili, Victor R. and Musa, john D. The future engineering of software" a management perspective. IEEE Computer, September, 1991. Google ScholarDigital Library
- Boehm75.Boehm, Barry W. The high cost of software. From Horowitz, Practical Strategies for Developing Large Software Systems, Addison- Wesley, Reading, Mass, 1975.Google Scholar
- Buck89.Buckley, J. Some standards for software maintenance. Standards, IEEE Computer, November 1989. Google ScholarDigital Library
- Card87.Card, David N., Mc Garry, Frank E. and Page, Gerald T. Evaluating software engineering technologies. IEEE Transactions on software engineering, Vol. SE-13, No. 7, 1987. Google ScholarDigital Library
- Chapin87.Chapin, Ned. The job of software maintenance. Proceedings Conference on Software Maintenance, IEEE, 1987.Google Scholar
- Chapin88.Chapin, Ned. Software maintenance life cycle. Proceedings Conference on Software Maintenance, IEEE, 1988.Google ScholarCross Ref
- Fagan76.Fagan, M.E. Design and code inspections to reduce errors in program development. IBM Systems Journal, Vol. 15, No. 3, 1976.Google ScholarDigital Library
- Fjel79.Fjelstad, R.K and Hamlen, W.T. Application program maintenance study report to our respondents. Proceedings GUIDE 48, Philadelphia, PA, 1979.Google Scholar
- Gamal88.Gamalel-Din, Shehab A. and Osterweil, Leon J. New perspectives on software maintenance processes. Proceedings Conference on Software Maintenance, IEEE, 1988.Google ScholarCross Ref
- Guim83.Guimaraes, Tor. Managing application program maintenance expenditures. Communications of the ACM, Vol. 26, No. 10, 1983. Google ScholarDigital Library
- Hager89.Hager, James A. Software cost reduction methods in practice. IEEE Transactions on software engineering, Vol. SE-15, No. 12, 1989. Google ScholarDigital Library
- Hager91.Hager, James A. Software cost reduction methods in practice: a post mortem analysis. Journal of systems and software, Vol. 14, No. 2, 1991. Google ScholarDigital Library
- Humph87.Humphrey, Watt S. and Sweet, W. L. A method for assessing the software engineering capability of contractors. CMU/SEI-87-TIL23, ESD-TR.87-186, September 1987.Google Scholar
- Humph91.Humphrey, Watt S., Snyder, Terry R. and Willis, Ronald R. Software process improvement at Hughes Aircraft. IEEE Software, July 1991. Google ScholarDigital Library
- Kell89.Kellner, Marc I. Non-traditional perspectives on software maintenance. Panel, Proceedings Conference on Software Maintenance, IEEE, 1989.Google Scholar
- Lien81.Lientz, Bennet P. and Swanson, E. Burton. Problems in app{ication software maintenance. Communications of the ACM, Vol. 24, No. 1 i, 1981. Google ScholarDigital Library
- Osborne87.Osborne, Wilma M. Building and Sustaining Software Maintainability. Proceedings Conference on Software Maintenance, IEEE, 1987.Google Scholar
- Paulk91.Paulk, M. C., Curtis, B., Chrissis, M. B., et al. Capability Maturity model for software. CMU/SEI-91-TR,24, August 1991.Google Scholar
- Post84.Poston, Robert M. When does more documentation mean less work?. Software Standards, IEEE Software, October 1984.Google Scholar
- Ramam88.Ramamoorthy, C.V. Our job is to reduce the errors. From Myers, Ware. Can software for the strategic defense initiative ever be error free? IEEE Computer, Vol. 21, No. 11, 1988.Google Scholar
- Romb87.Rombach, H. Dieter and Basili, Victor R. Quantitative assessment of maintenance: an industrial case study. Proceedings Conference on Software Maintenance, IEEE, 1987.Google Scholar
- Scheff91.Scheff, Benson H. and Georgon, Thomas. Using documentation blueprints to produce mandated DoD data items. Journal of Systems and Software, Vol. 14, No. 2, 1991. Google ScholarDigital Library
Index Terms
- Software system documentation process maturity model
Comments