On the Use of Requirements Measures to Predict Software Project and Product Measures in the Context of Android Mobile Apps: A Preliminary Study

Francese, Rita; Gravino, Carmine; Risi, Michele; Scanniello, Giuseppe; Tortora, Genoveffa

doi:10.1109/seaa.2015.22

Cited by 19 publications

(18 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In [2] initially were proposed two sets of independent variables. The first set, reported and described in Table I, collects variable obtained from the RAD or from the requirements, while the second set in Table II, collects variables from the source code gathered by exploiting the Understand 2 tool.…”

Section: A Variablesmentioning

confidence: 99%

“…The estimation technique adopted in [2] is StepWise Linear Regression (SWLR) technique [22], which explores the relationship between a dependent variable and one or more independent variables, providing a prediction model described by a linear equation:…”

Section: B Estimation Techniquementioning

confidence: 99%

“…In particular, in [2] the problem of predicting software project and product measures in the domain of Android development has been addressed considering as sample mobile applications produced by students during a mobile application development course.…”

Section: Introductionmentioning

confidence: 99%

“…We decided to try to estimate in the earlier phases of the projects the required effort and to resize the project 1 University of Salerno, Italy {francese, gravino, mrisi, tortora}@unisa.it 2 University of Basilicata {giuseppe.scanniello}@unibas.it requirements according to this suggestion. In particular, we exploited the results we got in [2], where we demonstrated that requirement analysis measures can effectively employed to estimate software project and product measures of a mobile app and estimations can be done early in the software development process. The metrics extracted from the projects of academic year 2013/14 have been used in the successive year to intervene on the requirements to adjust the project size.…”

Section: Introductionmentioning

confidence: 99%

“…In this paper we apply the effort estimation model for mobile application development presented in [2], which is based on the metrics extracted from the projects of academic year 2013/14. This model has been conceived using the dataset of the experience presented in [15] and is detailed and discussed in Section IV.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Supporting Mobile Development Project-Based learning by Software Project and Product Measures

Francese

Gravino

Risi

et al. 2016

International Conferences on Distributed Multimedia Systems

Self Cite

View full text Add to dashboard Cite

Abstract-Project-based learning is a kind of learning activity which has great educative effect, but which presents also several issues. In particular, if we consider an university course that requires the design and the implementation of a software project, may be difficult to estimate the number of hours that a team of students has to take to accomplish that project. There is the risk to underestimate the project (too difficult) or to overestimate it (too easy) with respect to the other projects of the same course and the amount of foreseen work hours. In this paper, we present the experience we gained in the adoption of Software Project and Product Measures for addressing the project size of projects performed during a Mobile Application Development course for Computer Science students at the University of Salerno. The course foresaw a project work conducted by students organized in teams. The goal of the project work was to design and develop an Android-based application with back-end for smart devices. Software estimation project measures are applied to some metrics extracted in the requirement analysis phase to get an estimation of the effort in terms of man/hours and consequently to adjust the project size by adding/reducing requirements. The metrics extracted from the projects of academic year 2013/14 have been used in the successive year for estimating the project effort and intervene on the project size variables.

show abstract

Section: A Variablesmentioning

confidence: 99%

Section: B Estimation Techniquementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Supporting Mobile Development Project-Based learning by Software Project and Product Measures

Francese

Gravino

Risi

et al. 2016

International Conferences on Distributed Multimedia Systems

Self Cite

View full text Add to dashboard Cite

show abstract

Effort estimation of open source Android projects via transaction analysis

Kan

Boehm

2020

J Software Evolu Process

View full text Add to dashboard Cite

Transactions have been used in many software sizing methods to measure software functional size and provide a basis for effort estimation. To further investigate the effects that transactions have on software functional size and more accurately estimate project effort using the transactional information, in this paper, we propose a method to identify transactions, as well as their complexity attributes that are influential to software functional size, directly from the source code of Android projects using static and dynamic analyses. The identified transactions are classified into different complexity levels and applied with different weights based on their evaluated complexity levels to distinguish their effects on software functional size. A size metric called sum of weighted transactions (SWT) is proposed to measure software functional size. We calibrate an effort estimation model using SWT based on a data set of 34 open source Android projects, and show the effectiveness of using SWT as a software functional size measure to estimate project effort.

show abstract