A Method for Calculating Acknowledged Project Effort Using a Quality Index

Software size is the fundamental metric for project planning. Effort and duration are calculated based on the size estimate. However, for a given software size, the actual development effort could be significantly different. The question is whether the increase in effort is due to the low productivity of the development team or higher product quality. While higher product quality is highly desirable and usually worth investing in, the reasons for additional effort might be elsewhere. In the research presented in this paper, the focus is on the correlation between code quality and productivity. Code quality is only one aspect of product quality. This paper presents a method for calculating a new type of project effort named “acknowledged effort”. Acknowledged effort is calculated based on the actual effort and code quality. This new type of effort reflects not only the project’s size and the productivity of the development team, but also the quality aspect of the delivered software system. Povzetek: V prispevku je analizrana korelacija med kakovostjo programske kode in produktivnostjo.

[1]  Radu Marinescu,et al.  Quantifying the quality of object-oriented design: the factor-strategy model , 2004, 11th Working Conference on Reverse Engineering.

[2]  Shinji Kusumoto,et al.  Function-point analysis using design specifications based on the Unified Modelling Language , 2001, J. Softw. Maintenance Res. Pract..

[3]  Giuliano Antoniol,et al.  Object-Oriented Function Points: An Empirical Validation , 2003, Empirical Software Engineering.

[4]  Tibor Gyimóthy,et al.  Empirical validation of object-oriented metrics on open source software for fault prediction , 2005, IEEE Transactions on Software Engineering.

[5]  Linda H. Rosenberg,et al.  Software Quality Metrics for Object-Oriented System Environments , 1995 .

[6]  Giuliano Antoniol,et al.  A Function Point-Like Measure for Object-Oriented Software , 1999, Empirical Software Engineering.

[7]  Marjan Hericko,et al.  Empirical Assessment of Methods for Software Size Estimation , 2003, Informatica.

[8]  David P. Darcy,et al.  Managerial Use of Metrics for Object-Oriented Software: An Exploratory Analysis , 1998, IEEE Trans. Software Eng..

[9]  Paolo Nesi,et al.  Metrics for controlling effort during adaptive maintenance of object oriented systems , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).

[10]  Marjan Hericko,et al.  The Impact of Details in the Class Diagram on Software Size Estimation , 2005, Informatica.

[11]  Marjan Hericko,et al.  Automated software size estimation based on function points using UML models , 2005, Inf. Softw. Technol..