Improving Size Estimates Using Historical Data

A software project's estimate of effort commonly requires input specifying the project size, and a reliable size estimate depends on many factors. This study examines a completed C++ project and considers programming artifacts that we can readily trace to requirements and early class design.

[1]  Robert E. Park,et al.  Software Size Measurement: A Framework for Counting Source Statements , 1992 .

[2]  Richard E. Fairley.  Recent advances in software estimation techniques , 1992, International Conference on Software Engineering.

[3]  Barry W. Boehm,et al.  Cost models for future software life cycle processes: COCOMO 2.0 , 1995, Ann. Softw. Eng..

[4]  A. Schaft,et al.  Hamiltonian formulation of distributed-parameter systems with boundary energy flow , 2002 .

[5]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[6]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[7]  John Stuart Lakos,et al.  Large-Scale C++ Software Design , 1996 .

[8]  T.-H. Nguyen,et al.  Mapping the OO-Jacobson approach into function point analysis , 1997, Proceedings of TOOLS USA 97. International Conference on Technology of Object Oriented Systems and Languages.

[9]  Lawrence H. Putnam,et al.  A General Empirical Solution to the Macro Software Sizing and Estimating Problem , 1978, IEEE Transactions on Software Engineering.