Software system documentation process maturity model

Authors:
Marcello Visconti;Curtis Cook
Affiliations:
Computer Science Department, Oregon State University, Corvallis, Oregon;Computer Science Department, Oregon State University, Corvallis, Oregon
Venue:
CSC '93 Proceedings of the 1993 ACM conference on Computer science
Year:
1993

Citing 10
Cited 2

Software errors and complexity: an empirical investigation0

Communications of the ACM
Evaluating Software Engineering Technologies

IEEE Transactions on Software Engineering
Software Cost Reduction Methods in Practice

IEEE Transactions on Software Engineering
Software cost reduction methods in practice: a post-mortem analysis

Journal of Systems and Software - Special issue on software maintenance
Using documentation blueprints to produce mandated DoD data items

Journal of Systems and Software - Special issue on software maintenance
The Future Engineering of Software: A Management Perspective

Computer
Managing application program maintenance expenditures

Communications of the ACM
Problems in application software maintenance

Communications of the ACM
Some standards for software maintenance

Computer
Software Process Improvement at Hughes Aircraft

IEEE Software

An empirical analysis of the impact of software development problem factors on software maintainability

Journal of Systems and Software
Towards detailed software artifact specification with SPEMArti

Proceedings of the 2011 International Conference on Software and Systems Process

Quantified Score

Hi-index	0.00

Visualization

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.