Correlations between problem and solution domain measures of open source software

Download

index.pdf

Date

2017-01-01

Author

Ayyildiz, Tulin Ercelebi
Koçyiğit, Altan

Metadata

Show full item record

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.

Item Usage Stats

125
views

73
downloads

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 regression and cross validation techniques are applied to investigate the relation between the sizes of problem domain (i.e., conceptual) and solution domain (i.e., design) measures. The results reveal a strong correlation between the problem domain measures and the solution domain measures constituting the corresponding software. The results suggest that it is possible to use problem domain descriptions in the early stages of software development projects to make plausible predictions for the size and effort of the software.

Subject Keywords

Software size measurement, Problem domain, Solution domain, Linear regression, Open source software projects

URI

https://hdl.handle.net/11511/29896

Journal

JOURNAL OF THE FACULTY OF ENGINEERING AND ARCHITECTURE OF GAZI UNIVERSITY

DOI

https://doi.org/10.17341/gazimmfd.337641

Collections

Graduate School of Informatics, Article

Suggestions

OpenMETU
Core

A Case Study on the Utilization of Problem and Solution Domain Measures for Software Size Estimation AYYILDIZ, TÜLİN ERÇELEBİ; Koçyiğit, Altan (2016-09-02) 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 correspondin...
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...
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. ...
PL-FSM: an aproach and a tool for the application of functional size measurement in software product line environments Eren, Önder; Demirörs, Onur; Özkan, Barış; Department of Information Systems (2014) In order to develop cost-efficient software it is crucial to measure the accurate software size. However; measuring the software size has up to now been almost entirely a manual process and, as such, is both time-consuming and prone to human error which can end up with time and money loss. Automation of this process is a must for the software developing companies to improve the quality of project and budget planning. This thesis introduces a mapping between COSMIC concept elements and UML conceptual element...
Conceptual Association of Functional Size Measurement Methods Demirörs, Onur; Gencel, Cigdem (Institute of Electrical and Electronics Engineers (IEEE), 2009-05-01) Functional size determines how much functionality software provides by measuring the aggregate amount of its cohesive execution sequences. Alan Albrecht first introduced the concept in 1979. Since he originally described the function point analysis (FPA) method, researchers and practitioners have developed variations of functional size metrics and methods. The authors discuss the conceptual similarities and differences between functional size measurement methods and introduce a model for unification.

Citation Formats

T. E. Ayyildiz and A. Koçyiğit, “Correlations between problem and solution domain measures of open source software,” JOURNAL OF THE FACULTY OF ENGINEERING AND ARCHITECTURE OF GAZI UNIVERSITY, pp. 887–900, 2017, Accessed: 00, 2020. [Online]. Available: https://hdl.handle.net/11511/29896.