Use case estimation - the devil is in the detail

Vinsen, Kevin; Jamieson, D.; Callender, Guy

doi:10.1109/icre.2004.1335649

Cited by 7 publications

(5 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Smith [1999] also goes on to describe other problems with the UCP method. Although the paper is dated 1999 the problems listed appear in more recent articles also [Vinsen 2004]. The articles that discuss the issues with the UCP method appear to still be referencing Smith's 1999 paper and Karner's original UCP method.…”

Section: Uml Use Case Point Methodsmentioning

confidence: 99%

1.4.3 Applying Systems Engineering Modeling Language (SysML) to System Effort Estimation Utilizing Use Case Points

Bone

Cloutier

2011

INCOSE International Symp

View full text Add to dashboard Cite

This paper proposes that as model based systems engineering begins to play a larger role in system development it may be utilized in estimating systems effort, making model based systems engineering more valuable to system engineering. This paper proposes to extend the Use Case Points (UCP) estimating approach, used by some software engineers, to SysML for estimating the systems engineering effort. The paper reviews literature that encourages the notion of a UCP method for Systems Engineering (UCPSE). Finally the paper maps out the research plan to develop and validate the UCPSE method.

show abstract

Section: Uml Use Case Point Methodsmentioning

confidence: 99%

1.4.3 Applying Systems Engineering Modeling Language (SysML) to System Effort Estimation Utilizing Use Case Points

Bone

Cloutier

2011

INCOSE International Symp

View full text Add to dashboard Cite

show abstract

“…They suggest to use good examples of use cases or to define specific guidelines for the use case modeling process. Vinsen et al [12] point out that the function point method has been successfully applied to small scale use case systems, but that there may be difficulties with large-scale systems because the detailed functionality of the system may not be specified in the use case, but in ancillary documents such as rules, conditions, exclusions, etc. In addition, Mohagheghi et al [13] have dealt with this topic when calculating use case points in a large scale software development.…”

Section: Related Workmentioning

confidence: 98%

Employing use cases to early estimate effort with simpler metrics

Robiolo

Orosco

2008

Innovations Syst Softw Eng

View full text Add to dashboard Cite

In order to calculate size and to estimate effort in applications, the standard method most usually used is function points, which has been used with good results in the development of industrial software for some time. However, some aspects should be improved, namely: the time at which the estimation of effort is performed and the margin of error in the effort estimation. Consequently, another size metric which could be used to obtain more accurate estimations should be found. This article presents two other size metrics for projects based on use cases: transactions and entity objects. Effort is estimated by using the technique mean productivity value. There is also a description of two case studies, one which involved four academic projects and the other one which involved four industrial projects. They were developed in order to compare the estimations obtained with each method. The result shows that the current way of estimating effort can be improved by using the number of transactions as a size metric and the technique mean productivity value.

show abstract

“…The original textual descriptions were modified in order to avoid the use case level of detail problem [25] and to have a similar reading time.…”

Section: B Planningmentioning

confidence: 99%

How Simple is It to Measure Software Size and Complexity for an IT Practitioner?

Robiolo

2011

2011 International Symposium on Empirical Software Engineering and Measurement

View full text Add to dashboard Cite

An empirical study was conducted in order to evaluate the simplicity of FPA, COSMIC and Paths, from the IT practitioners' viewpoint. The results have shown that P are the simplest measure because they presented a significantly lower measurement time. The study has also been useful to see which aspects of Paths should be clarified in order to facilitate the practitioners' application of this measure and to demonstrate in a mathematical form how the complexity of an application which is measured with P increases if the number of "transactions" increases. The results obtained cannot be generalized because the number of measurements performed was small, and the subjects had particular characteristics, but a new empirical study using use case textual descriptions of different domains and subjects with different characteristics is expected to solve this limitation.

show abstract

Use case estimation - the devil is in the detail

Abstract: Abstract

Cited by 7 publications

References 3 publications

1.4.3 Applying Systems Engineering Modeling Language (SysML) to System Effort Estimation Utilizing Use Case Points

1.4.3 Applying Systems Engineering Modeling Language (SysML) to System Effort Estimation Utilizing Use Case Points

Employing use cases to early estimate effort with simpler metrics

How Simple is It to Measure Software Size and Complexity for an IT Practitioner?

Contact Info

Product

Resources

About