||This article may be confusing or unclear to readers. (July 2008) (Learn how and when to remove this template message)|
In software engineering, many 'reuse metrics and models have been developed to measure code reuse and reusability. A metric is a quantitative indicator of an attribute of a thing. A model specifies relationships among metrics. Reuse models and metrics can be categorized into six types:
- reuse cost-benefits models
- maturity assessment
- amount of reuse
- failure modes
- reuse library metrics
Reuse cost-benefits models include economic cost-benefit analysis as well as quality and productivity payoff. Maturity assessment models categorize reuse programs by how advanced they are in implementing systematic reuse. Amount of reuse metrics are used to assess and monitor a reuse improvement effort by tracking percentages of reuse for life cycle objects. Failure modes analysis is used to identify and order the impediments to reuse in a given organization. Reusability metrics indicate the likelihood that an artifact is reusable. Reuse library metrics are used to manage and track usage of a reuse repository.
- Frakes, William and Carol, Terry. "Software Reuse: Metrics and Models." ACM Computing Surveys 28(2), pp. 415-435, 1996.
|This software-engineering-related article is a stub. You can help Wikipedia by expanding it.|