Abstract
We present a case study that aimsat quantitative assessment of the impact of requirements changes,and quantitative estimation of costs of the development activitiesthat must be carried out to accomplish those changes. Our approachis based on enhanced traceability and an integrated view of theprocess and product models. The elements in the process and productmodels are quantitatively characterised through proper measurement,thus achieving a sound basis for different kinds of sophisticatedanalysis concerning the impact of requirements changes and theircosts. We present the results of the application of modelingand measurement to an industrial project dealing with real-timesoftware development. The ability to predict the impact of changesin requirements and the cost of related activities is shown.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Albrecht, A. J. 1979. Measuring application development productivity. Proc. IBM Applications Develop. Symp. Monterey, USA.
Albrecht, A. J., and Gaffney, J. E. 1983. Software function, source lines of code, and development effort prediction: A software science validation. IEEE Trans. Software Engineering 9: 639-648.
Basili, V., Caldiera, G., and Rombach, D. 1994. Goal/question/metric paradigm. Marciniak, J. C. (Ed). in Encyclopedia of Software Engineering. Wiley, vol. 1.
Behrens, C. 1983. Measuring the productivity of computer systems development activities with function points. IEEE Trans. Software Engineering 9: 648-652.
Bøegh, J., Depanfilis, S., Kitchenham, B., and Pasquini, A. 1999. A method for software quality planning, control, and evaluation. IEEE Software 16(2): 69-77.
Boehm, B. 1981. Software Engineering Economics. Prentice-Hall.
Boehm, B., Clark, B., Horowitz, E., Madachy, R., Shelby, R., and Westland, C. 1995. Cost models for future software life cycle processes: COCOMO 2.0. Arthur, J. D., and Henry, S. M. (eds). Annals of Software Engineering. Amsterdam: Baltzer Science Publishers. Vol. 1, pp. 57-94.
COCOMO Research Group. 1997. COCOMO II model definition manual. Available at http://sunset.usc.edu/COCOMOII/cocomo.html.
Hammer, T., Huffman, L., Wilson, W., Rosenberg, L., and Hyatt, L. 1996. Requirement metrics for risk identification. Proc. Ann. Software Eng. Workshop. NASA-GSFC, USA.
IFPUG. 1994. IFPUG function point counting practices: Manual release 4.0. Westerville: International Function Point Users' Group.
Kitchenham, B. A., and Kirakowski, J. 1990. The MERMAID approach to software cost estimation. Proc. Annual ESPRIT Conference. Brussels, Belgium.
Lavazza, L., and Valetto, G. 2000. Requirements-based estimation of change costs. Proc. 4th Int. Conf. on Empirical Assessment and Evaluation in Software Eng. Keele, U.K. http://www.cefriel.it/~lavazza/ease2000.html.
McCabe, T. J. 1976. A complexity measure IEEE Trans. Software Engineering 4: 308-320.
Meli, R. 1999. Risks, requirements, and estimation of a software project. Proc. 10th European Software Control and Metrics Conf. Hestermonceaux Castle, United Kingdom.
Ramesh, B., Stubbs, C., Powers, T., and Edwards, M. 1997. Requirements traceability: Theory and practice. Annals of Software Engineering 3: 397-415.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Lavazza, L., Valetto, G. Requirements-Based Estimation of Change Costs. Empirical Software Engineering 5, 229–243 (2000). https://doi.org/10.1023/A:1026590615963
Issue Date:
DOI: https://doi.org/10.1023/A:1026590615963