Abstract
Early software size estimation is a challenging task since limited information is available at the time of project inception. Additional information, however, is gradually added as development progresses. The goal of this research is to quantitatively capture the impact on early software size estimation of this additional information introduced especially when transitioning from the analysis phase to the design phase by comparing the analysis class diagram (ACD) and the design class diagram (DCD). We introduce a new class of metrics called analysis-to-design adjustment factors (ADAFs) to accomplish this goal. ADAFs are calculated for four different class diagram metrics - number of classes (NOC), number of attributes (NOA), number of methods (NOM), and number of relationships (NOR) - used in different class diagram-based software size estimation models. We use practical, theoretical, and empirical validation methods to evaluate the applicability of these ADAFs. To assess the utility of these ADAFs in early software size estimation, we compare the accuracy of existing early software size estimation models before and after the application of ADAFs. Results indicate a marked improvement in the accuracy of these models after the application of ADAFs. Furthermore, regression-based models employing problem domain metrics have also been built to predict these ADAFs. All of these models are statistically significant (p-values <; 0.05) with R <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">2</sup> values between 0.42 and 0.88.
Highlights
Estimation of software size, development effort, and cost are essential for project planning, which, in turn, is an important component of software project management [1]
To assess the utility of these analysis-to-design adjustment factors (ADAFs) in early software size estimation, we compared the accuracy of existing early software size estimation models before and after the application of ADAFs
EVALUATION AND EMPIRICAL VALIDATION OF ADAFS The framework proposed by Misra et al [23] was used for evaluation and validation of ADAFs because it provides a more comprehensive criteria as compared to other frameworks proposed in the literature
Summary
Estimation of software size, development effort, and cost are essential for project planning, which, in turn, is an important component of software project management [1]. Software size estimation is a crucial task as many software cost and effort estimation models take software size, measured in Lines of Code (LOC) [2] and/or Function Points (FPs), [2], [3] as input. Inaccurate software size estimation (overestimation or underestimation), leads to incorrect effort and cost estimation of a software project which, in turn, may lead to project failure. Researchers have used metrics extracted from different analysis and design models (e.g. use case diagram, ER diagram, sequence diagram, class diagram, etc.) to predict software size [4]–[18].
Sign-in/Register to view highlights & summary 
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call