A survey on software effort estimation

Usharani, K.; Ananth, V. Vignaraj; Velmurugan, D.

doi:10.1109/iceeot.2016.7755665

Cited by 15 publications

(9 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this step the amount of effort for a specific change request implementation will be estimated after receiving the required information such as Value of A (constant), Scale Drivers Exponent B and Value of Effort Multipliers, Development Phase and change request completion date. The Value of A (constant), Scale Drivers Exponent B and Value of Effort Multipliers will be calculated by using COCOMO II [27] as shown in Figure 4.…”

Section: Step 4: Effort Estimationmentioning

confidence: 99%

Software Requirement Change Effort Estimation Model Prototype Tool for Software Development Phase

Shah¹,

Kama²,

Bakar³

et al. 2019

IJSEA

View full text Add to dashboard Cite

In software development phase software artifacts are not in consistent states such as: some of the class artifacts are fully developed some are half developed, some are major developed, some are minor developed and some are not developed yet. At this stage allowing too many software requirement changes may possibly delay in project delivery and increase development budget of the software. On the other hand rejecting too many changes may increase customer dissatisfaction. Software change effort estimation is one of the most challenging and important activity that helps software project managers in accepting or rejecting changes during software development phase. This paper extends our previous works on developing a software requirement change effort estimation model prototype tool for the software development phase. The significant achievements of the tool are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the estimation accuracy over current change effort estimation models.

show abstract

Section: Step 4: Effort Estimationmentioning

confidence: 99%

Software Requirement Change Effort Estimation Model Prototype Tool for Software Development Phase

Shah¹,

Kama²,

Bakar³

et al. 2019

IJSEA

View full text Add to dashboard Cite

show abstract

“…Two most common non-algorithmic SCEE models are: Expert Judgement and Estimation by Analogy. Expert Judgement is a non-algorithmic SEE model [17]. According to Sufyan, et al [29] usually software development teams preferred to use expert judgement effort estimation model instead of other estimation models because of its flexibility and simplicity.…”

Section: Software Change Effort Estimationmentioning

confidence: 99%

“…Some of the most common algorithmic-based models are: COCOMO II [13], Function Point Analysis [14] and Use-Case Points [15]. Whereas, some of the non-algorithmic-based models are: Expert Judgement [16], Analogy Based Estimation [17] and Delphi [18]. Although, several extensions of these models are developed to estimate effort in Software Development Phase (SDP).…”

Section: Introductionmentioning

confidence: 99%

A Novel Effort Estimation Model for Software Requirement Changes During Software Development Phase

Shah¹,

Kama²,

Bakar³

2018

IJSEA

View full text Add to dashboard Cite

Software Requirements Changes is a typical phenomenon in any software development project. Restricting incoming changes might cause user dissatisfaction and allowing too many changes might cause delay in project delivery. Moreover, the acceptance or rejection of the change requests become challenging for software project managers when these changes are occurred in Software Development Phase. Where in Software Development Phase software artifacts are not in consistent state such as: some of the class artifacts are Fully Developed, some are Half Developed, some are Major Developed, some are Minor Developed and some are Not Developed yet. However, software effort estimation and change impact analysis are the two most common techniques which might help software project managers in accepting or rejecting change requests during Software Development Phase. The aim of this research is to develop a new software change effort estimation model which helps software project manager in estimating the effort for software Requirement Changes during Software Development Phase. Thus, this research has analyzed the existing effort estimation models and change impact analysis techniques for Softwrae Development Phase from the literature and proposed a new software change effort estimation model by combining change impact analysis technique with effort estimation model. Later, the new proposed model has been evaluated by selecting four small size software projects as case selections in applying experimental approch. The experiment results show that the overall Mean Magnitude Relative Error value produced by the new proposed model is under 25%. Hence it is concluded that the new proposed model is applicable in estimating the amount of effort for requirement changes during SDP.

show abstract

“…Many cost estimation methods and techniques have been suggested for collocated environment during last decades before emergence of GSD concept. They are broadly divided into categories i.e., Algorithmic models, Artificial Intelligence and Expert estimation based techniques (Usharani, Ananth, & Velmurugan, 2016). Algorithmic methods like COCOMO (Constructive Cost Model), Putnams Model, Function Point based models and SEER-SEM Models make use of input like source line of code, function point and cost driver to perform the process of estimation by using mathematical equations.…”

Section: Introductionmentioning

confidence: 99%

Software Cost Estimation in Global Software Development Business: A Review of Models and Cost Drivers for Economical Business

Ahmed¹,

Ateeq²,

Khan³

et al. 2021

Int. j. bus. econ. aff.

View full text Add to dashboard Cite

Global Software Development (GSD) has grown in popularity as important tool for ensuring the efficient use of resources in internationally distributed environments across multiple geographical locations for business. The most prominent features of GSD are lowering costs, speeding up growth, and gaining access to talented developers all over the world. However, there are a number of drawbacks that result from the distance between development teams including coordination and communication causing the hidden business costs involved in development process. In the context of GSD, it is necessary to focus on economic cost estimation models as estimating the needed resources and effort remains a difficult task. Software cost estimation has become a critical factor in determining software development effectiveness economically. There are many cost estimating models, including algorithmic, non-algorithmic, and hybrid for business development environment. Over the last decade, several studies have focused on economic cost estimate in GSD. To the best of our understanding, current cost estimation techniques/models do not take into account all the additional business cost drivers that are necessary to calculate accurate cost estimation in the GSD context. In this paper we present a comparative analysis of economic software cost estimation techniques along with cost divers used in GSD context. This paper summarizes the additional cost drivers in GSD and discusses open research topics in economic cost estimation in GSD based on the results review of the associated literature.

show abstract

A survey on software effort estimation

Cited by 15 publications

References 15 publications

Software Requirement Change Effort Estimation Model Prototype Tool for Software Development Phase

Software Requirement Change Effort Estimation Model Prototype Tool for Software Development Phase

A Novel Effort Estimation Model for Software Requirement Changes During Software Development Phase

Software Cost Estimation in Global Software Development Business: A Review of Models and Cost Drivers for Economical Business

Contact Info

Product

Resources

About