2003
DOI: 10.1049/ip-sen:20031056
|View full text |Cite
|
Sign up to set email alerts
|

Effort estimation in incremental software development

Abstract: Incremental software development offers many benefits compared with more traditional development approaches. Indeed, incremental approaches have been utilised for many years due to the involvement of users, the early demonstration of capability and the potential for risk reduction that they offer. However, there appears to have been little work on modelling, planning and controlling incremental development. The paper attempts to introduce a quantitative analytical framework for evaluating such approaches and t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
23
0
1

Year Published

2004
2004
2021
2021

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 37 publications
(24 citation statements)
references
References 8 publications
0
23
0
1
Order By: Relevance
“…This approach allows them to gain enough knowledge and experience with the production in order to move on to the next increment which they will face something a little more challenging. This process model also ensures early realization of business values as well as other project requirements with quick deliveries for users and clients to react upon [5,13]. However, as the user base grows, there is more concern with reliability, which is hard to retrofit into an easiestfirst code base.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…This approach allows them to gain enough knowledge and experience with the production in order to move on to the next increment which they will face something a little more challenging. This process model also ensures early realization of business values as well as other project requirements with quick deliveries for users and clients to react upon [5,13]. However, as the user base grows, there is more concern with reliability, which is hard to retrofit into an easiestfirst code base.…”
Section: Discussionmentioning
confidence: 99%
“…Based on Boehm's discussion about estimate for incremental development, Benediktsson and Dalcher conducted a series of studies [4][5][6] estimating IID production effort and size using expanded calculations derived from Basic COCOMO [21] and COCOMOII [20]. In their reports, they noted that relative productivity, which is the productivity for IID, is inversely proportional to the scale factor exponents-meaning if a project is developed under single increment setting and it is thought to be productive, but it may not be the case if the same project is developed with IID.…”
Section: Literature Reviewmentioning
confidence: 99%
“…Product size: Development e®ort, in general, is strongly correlated with product size. Many research e®orts have been made to empirically relate e®ort with product size [26]. This facet documents whether the agile team uses size as a predictor and which metric is used to represent the size.…”
Section: E®ort Predictorsmentioning
confidence: 99%
“…Three types of COCOMO models are presented. They are: Organic, Semidetached and Embedded models [27]. …”
Section: A Cocomo Modelmentioning
confidence: 99%