A Case Study on the Utilization of Problem and Solution Domain Measures for Software Size Estimation

2016-09-02
AYYILDIZ, TÜLİN ERÇELEBİ
Koçyiğit, Altan
Detailed requirements is the primary input of software size measurement and effort estimation methodologies and a significant amount of time and expertise is needed for size measurement. In order to streamline size measurement and effort estimation, this study exploits the correlations between the problem domain measures such as the number of distinct nouns and distinct verbs in the requirements artifacts and the solution domain measures such as the number of software classes and methods in the corresponding object oriented software. In this case study, 12 commercial software projects are analyzed and multiple regression analysis is carried out to develop an estimation model for the solution domain metrics in terms of problem domain metrics. The results suggest that, for the projects examined, it is possible to use problem domain measures to make plausible predictions for the solution domain metrics.
42nd Euromicro Conference Series on Software Engineering and Advanced Applications (SEAA)

Suggestions

Correlations between problem and solution domain measures of open source software
Ayyildiz, Tulin Ercelebi; Koçyiğit, Altan (2017-01-01)
Software size measurement and effort estimation methodologies in use today usually take the detailed requirements of software to be developed as the primary input and a certain amount of time and expertise is needed for size measurement. This paper analyzes the open source projects' correlations between the problem domain measures (the number of nouns and verbs) and solution domain measures (the number of software classes and methods). In this paper, 27 open source software projects are analyzed. Linear reg...
A Functional software measurement approach bridging the gap between problem and solution domains
Ungan, Erdir; Demirörs, Onur; Department of Information Systems (2013)
There are various software size measurement methods that are used in various stages of a software project lifecycle. Although functional size measurement methods and lines of code measurements are widely practiced, none of these methods explicitly position themselves in problem or solution domain. This results in unreliable measurement results as abstraction levels of the measured artifacts vary greatly. Unreliable measurement results hinder usage of size data in effort estimation and benchmarking studies. ...
An Error prevention model for cosmic functional size measurement method
Salmanoğlu, Murat; Demirörs, Onur; Department of Information Systems (2012)
Estimation and measurement of the size of software is crucial for project management activities. Functional size measurement is one of the most frequently used methods to measure size of software and COSMIC is one of the popular methods for functional size measurement. Although precise size measurement is critical, the results may differ because of the errors made in the measurement process. The erroneous measurement results cause lack of confidence for the methods as well as reliability problems for effort...
A Software functionality model for functional size measurement
Özkan, Barış; Demirörs, Onur; Department of Information Systems (2012)
Functional size is among the few software size measures for which well-structured and standardized methods exists for its measurement. Although Functional Size Measurement(FSM) methods have gone a long way, one ongoing criticism on FSM methods is the discrepancies in the measurement results of the same software obtained by different measures. In this thesis study the sources of discrepancies that involve the functional properties of measurands and constructs of the FSM method models are investigated in two ...
Size and effort estimation based on correlations between problem and solution domain measures for object oriented software
Erçelebi Ayyıldız, Tülin; Koçyiğit, Altan; Department of Information Systems (2015)
Software size measurement and effort estimation methodologies in use today usually take the detailed requirements of software to be developed as the primary input and a certain amount of time and expertise is needed for size measurement. This thesis analyzes the correlations between the problem domain measures such as the number of distinct nouns and distinct verbs in the requirements artifacts and the solution domain measures such as the number of software classes and methods in the corresponding object or...
Citation Formats
T. E. AYYILDIZ and A. Koçyiğit, “A Case Study on the Utilization of Problem and Solution Domain Measures for Software Size Estimation,” presented at the 42nd Euromicro Conference Series on Software Engineering and Advanced Applications (SEAA), Limassol, CYPRUS, 2016, Accessed: 00, 2020. [Online]. Available: https://hdl.handle.net/11511/30712.