| dc.contributor |
Computer Science (CS) |
|
| dc.creator |
Schneidewind, Norman F. |
|
| dc.date |
2015-05-06T00:49:23Z |
|
| dc.date |
2015-05-06T00:49:23Z |
|
| dc.date |
1991 |
|
| dc.date.accessioned |
2022-05-19T00:51:12Z |
|
| dc.date.available |
2022-05-19T00:51:12Z |
|
| dc.identifier |
http://hdl.handle.net/10945/45151 |
|
| dc.identifier.uri |
http://localhost:8080/xmlui/handle/CUHPOERS/60660 |
|
| dc.description |
We show how metrics that are
collected and validated during
development can be used during
maintenance to control quality and
prioritize maintenance work. Our
approach is to capitalize on knowledge
acquired and experience gained with the
software during development through
measurement. The motivation for this
research stems from the need to provide
maintenance management with the
following: 1) quantitative basis for
establishing quality objectives during
maintenance and 2) rationale for
allocating resources - people, money,
and equipment - to maintenance tasks. We
base our approach on validating selected
metrics against related quality factors
during development and using the
validated metrics duringmaintenance to:
1) establish initial quality objectives
and quality control criteria and 2)
prioritize software components (e.g.,
module) and allocate resources to
maintain them. We use the validity
criteria discriminative power and
tracking to illustrate the process. |
|
| dc.format |
application/pdf |
|
| dc.publisher |
IEEE |
|
| dc.rights |
This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States. |
|
| dc.title |
Setting Maintenance Quality Objectives and Prioritizing Maintenance Work by Using Quality Metrics |
|
| dc.type |
Article |
|