Estimating Software Development Effort Based on Use Cases — Experiences from Industry

Anda, Bente; Dreiem, Hege; Sjøberg, Dag I. K.; Jørgensen, Magne

doi:10.1007/3-540-45441-1_35

Cited by 98 publications

(93 citation statements)

References 9 publications

(10 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Agarwal et al cited by Damodaran and Washington [20] presents an example of use of this method for estimating an Internet project held in Infosys (Bangalore, India). Other experiences of use of UCP in industry were carried out by Anda et al [21], by Ribu [22] and by some companies as the Rational, SUN and IBM [23].…”

Section: B Use Case Pointsmentioning

confidence: 99%

“…Anda et al [21] applied the Karner method [6] in three projects of a software development company in Norway, Sweden and Finland to compare the estimates made by the UCP with the estimates made by senior members of the development projects. The results showed that the estimation performed through UCP method was close to the real estimation performed by experienced developers.…”

Section: B Use Case Pointsmentioning

confidence: 99%

See 1 more Smart Citation

An Empirical Study on the Estimation of Size and Complexity of Software Applications with Function Points Analysis

Alves

Oliveira

Ribeiro

2014

2014 14th International Conference on Computational Science and Its Applications

View full text Add to dashboard Cite

Abstract-Empirical studies are important in software engineering to evaluate new tools, techniques, methods and technologies in a structured way before they are introduced in the industrial (real) software process. Perform empirical studies in a real context is very difficult due to various obstacles. An interesting alternative is perform empirical studies in an educational context using students as subjects and share the results with the academia and the industry. This paper describes a case study with two teams that developed a software system (Web application) for a real customer. In this study we used a model based on Function Points Analysis (FPA) to estimate the size and complexity of software system.

show abstract

Section: B Use Case Pointsmentioning

confidence: 99%

Section: B Use Case Pointsmentioning

confidence: 99%

An Empirical Study on the Estimation of Size and Complexity of Software Applications with Function Points Analysis

Alves

Oliveira

Ribeiro

2014

2014 14th International Conference on Computational Science and Its Applications

View full text Add to dashboard Cite

show abstract

“…In this way, each team can work independently on a particular requirement without waiting for others. To evaluate the efforts of developing a requirement, we refer to [21,22] for techniques based on XML use cases and feature estimations.…”

Section: Introductionmentioning

confidence: 99%

An integrated approach for requirement selection and scheduling in software release planning

Akker

Brinkkemper

et al. 2010

Requirements Eng

View full text Add to dashboard Cite

It is essential for product software companies to decide which requirements should be included in the next release and to make an appropriate time plan of the development project. Compared to the extensive research done on requirement selection, very little research has been performed on time scheduling. In this paper, we introduce two integer linear programming models that integrate time scheduling into software release planning. Given the resource and precedence constraints, our first model provides a schedule for developing the requirements such that the project duration is minimized. Our second model combines requirement selection and scheduling, so that it not only maximizes revenues but also simultaneously calculates an on-time-delivery project schedule. Since requirement dependencies are essential for scheduling the development process, we present a more detailed analysis of these dependencies. Furthermore, we present two mechanisms that facilitate dynamic adaptation for over-estimation or underestimation of revenues or processing time, one of which includes the Scrum methodology. Finally, several simulations based on real-life data are performed. The results of these simulations indicate that requirement dependency can significantly influence the requirement selection and the corresponding project plan. Moreover, the model for combined requirement selection and scheduling outperforms the sequential selection and scheduling approach in terms of efficiency and on-time delivery.

show abstract

“…An estimation method based on use cases, the use case points method, was introduced by Karner [9]. This estimation method has been evaluated in several software development projects with promising results [2,3,12]; it was considered easy to use and performed similar to or better than teams of very experienced software developers. Nevertheless, more knowledge is needed about how to apply the method and tailor it to a specific organization.…”

Section: Introductionmentioning

confidence: 99%

“…Nevertheless, more knowledge is needed about how to apply the method and tailor it to a specific organization. We evaluated the use case points method on three projects as the first activity in a software process improvement project on improving estimation in a Scandinavian software development company, Mogul [3]. Since then, the company has also applied the method on a couple of other projects with success.…”

Section: Introductionmentioning

confidence: 99%

Improving Estimation Practices by Applying Use Case Models

Anda

Angelvik²,

Ribu

2002

Product Focused Software Process Improvement

Self Cite

View full text Add to dashboard Cite

Abstract. An estimation method based on use cases, the use case points method, has given promising results. However, more knowledge is needed about the contexts in which the method can be applied and how it should be adapted to local environments to improve the estimation process. We applied the use case points method to several projects in a Scandinavian software development company as the first activity in a software process improvement project on improving estimation. The second activity of the improvement project was to conduct interviews with project managers and senior developers about how to obtain continued and more widespread use of the method in the company. Based on the interviews, we propose a tailored, potentially improved version of the method and suggest how estimation practices can be improved by applying it. We believe that these experiences may be of interest to other companies that consider applying use case models as part of their estimation practices.

show abstract

Estimating Software Development Effort Based on Use Cases — Experiences from Industry

Cited by 98 publications

References 9 publications

An Empirical Study on the Estimation of Size and Complexity of Software Applications with Function Points Analysis

An Empirical Study on the Estimation of Size and Complexity of Software Applications with Function Points Analysis

An integrated approach for requirement selection and scheduling in software release planning

Improving Estimation Practices by Applying Use Case Models

Contact Info

Product

Resources

About