Research of Software Size Estimation Method

Ren, Aihua; Chen, Yun

doi:10.1109/csc.2013.32

Cited by 10 publications

(4 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Then the project is divided into sub-projects or software component. This method can be used at the early phase of development because at that stage minimum derails are available which can be tackled in this model easily [20]. This method is useful when no detailed information is there.…”

Section: Top-down Methodsmentioning

confidence: 99%

Systematic Literature Review of Identifying Issues in Software Cost Estimation Techniques

Saleem¹,

Ahmad²,

Alyas³

et al. 2019

IJACSA

View full text Add to dashboard Cite

Software cost estimation plays a vital role in software project management. It is a process of predicting the effort and cost in terms of money and staff required for developing the software system. It is very much clear that software project will be successful if its estimated cost will be near to the real cost. When the project is at the acquisition stage the least details are available about a software project to be developed, due to which Problems arises in cost estimation. As the stages move on details increases for software development of software which is quite fruitful in cost estimating. However, it can be considered that estimating the software cost in the first phases will produce better results. In this research cost estimation techniques are discussed along with the issues in that particular technique and focus will be on understating the points or issues which cause hurdles or issues in estimating the cost of the software project.

show abstract

Section: Top-down Methodsmentioning

confidence: 99%

Systematic Literature Review of Identifying Issues in Software Cost Estimation Techniques

Saleem¹,

Ahmad²,

Alyas³

et al. 2019

IJACSA

View full text Add to dashboard Cite

show abstract

“…In software projects, modifications are considered agreed upon scope of the project. These modifications are due [5] Agile EVM [26] Burn-down charts [46] Burn-up charts [46] Function Points [48] Work-Breakdown Structure [49] Expert judgement [51] Performance analysis [52] Feature Transition Charts [53] Story Mapping [54] Stakeholder analysis [55] Benefit analysis [56] Requirement Matrix [56] Scope Change Control System [57] Functional Size Measurement (FSM) [58] Feature Survival Charts [59] Feature Growth Charts [60] SPSRI [61] Activity Based (top down) [62]- [63] Task based (bottom up) [62]- [63] PERT [64] Object point [65] Source line of code (SLOC) [65] Analogy technique [65] Price-to-win [62] VOLUME , 2020 to inevitable change and complexity of the project scope. According to [50] author "Half of the system requirements change till deployment".…”

Section: B Scope Definition Techniques/toolsmentioning

confidence: 99%

Measuring the Impact of Scope Changes on Project Plan Using EVM

et al. 2020

View full text Add to dashboard Cite

Earned Value Management (EVM) measures project performance against a baseline plan. It identifies deviations in budget and schedule, aids project managers in taking earlier corrective actions against cost and schedule overruns. Although the literature highlights the significance of scope by adopting it as a leading indicator to measure project success or failure. However, EVM does not include scope when evaluating the performance of any software project. While considering the importance of scope and its ever-changing nature, it is imperative to measure the effect of changes in scope on the project plan. To analyse such effects, this study aims to enhance the traditional EVM by incorporating scope into it. The main objectives of this paper are: i) to extract the effects of project scope changes, ii) to map extracted effects of project scope changes with Software Project Scope Rating Index (SPSRI) elements, and iii) to quantify the extracted effects and integrate them with EVM. An extensive literature review is conducted to achieve the first objective, which results in the seventeen unique effects; that were used to map with SPSRI elements. To forecast the variations in scope for a given project budget, Monte Carlo simulations were run on the top eight scope elements, whereas, the results were incorporated with EVM to identify the deviations between actual and projected values of scope's score and cost. Finally, the multivariate regression model was used to evaluate the influence of individual element on the overall estimated cost of the project. The correlation between the independent variables (SPSRI elements) and the dependent variable (overall cost) was calculated along with the valuation of each independent variable on the dependent variable. Moreover, the effects are statistically shown that independent variables have influenced the dependent variable. This technique could assist the project managers to forecast deviations in project scope earlier.

show abstract

“…Barry Boehm [28] conducted a study based on literature analysis, conducting interviews and surveys with leading resource estimators and users, and concludes that the study on resource estimation has a direct impact with software engineering practices. Aihua Ren and Chen Yun [29] worked on most widely used size estimation models like analogy based Function Point, PERT, Delphi and other methods. Not all methods are suitable for all type of projects.…”

Section: Expert Judgement Approachmentioning

confidence: 99%

A Survey on Software Estimation Techniques in Traditional and Agile Development Models

Prakash

Viswanathan

2017

IJEECS

View full text Add to dashboard Cite

<p>Software projects mostly exceeds budget, delivered late and does not meet with the customer’s satisfaction for years. In the past, many traditional development models like waterfall, spiral, iterative, and prototyping methods are used to build the software systems. In recent years, agile models are widely used in developing the software products. The major reasons are – simplicity, incorporating the requirement changes at any time, light-weight approach and delivering the working product early and in short duration. Whatever the development model used, it still remains a challenge for software engineer’s to accurately estimate the size, effort and the time required for developing the software system. This survey focuses on the existing estimation models used in traditional as well in agile software development.</p>

show abstract

Research of Software Size Estimation Method

Cited by 10 publications

References 0 publications

Systematic Literature Review of Identifying Issues in Software Cost Estimation Techniques

Systematic Literature Review of Identifying Issues in Software Cost Estimation Techniques

Measuring the Impact of Scope Changes on Project Plan Using EVM

A Survey on Software Estimation Techniques in Traditional and Agile Development Models

Contact Info

Product

Resources

About