logo logo2
 

 Use Case Points

 

Use Case Points

Use Case points were first described by Gustav Karner, but his original work is closely guarded by Rational Software. These notes, therefore, primarily documents Karner's work as described by Schneider and Winters (1998), Ribu (2001) and Cohn (2005).

 

Lalcrest can help you size your software according to these conventions. Thus allowing you to make meaningful comparisons between different systems and /or development and enhancement projects.

 

The number of Use Case Points is a function of the following:

  • the number and complexity of the use cases in the system
  • the number and complexity of the actors in the system
  • various non-functional requirements
  • the environment in which the project will be developed.

 

Lalcrest can help you build models of your use case points and extract information therefrom.

 

 

 

Use Case Hierarchy

 

Colour Coding Key

 

 

 


 

Use Case Point Summary

 

 

Use Case Point Type

Complexity

Number of Use Cases and Actors

Use Case Points Awarded

Use Case Points

Use Case

Low

0

5

0

Average

0

10

0

High

5

15

75

sub-total

5

 

75

Actor

Low

0

1

0

Average

0

2

0

High

1

3

3

sub-total

1

 

3

Total Unadjusted Use Case Points

78

Technical Complexity Factor

1.05

Environmental Complexity Factor

0.99

Total Use Case Points

81

 

 

 

Use Case Points and Function Points are intended to measure similar aspects of software developments. It can be useful to use both measures.

Using Use Case Points with Function Points

 

 

All Rights Reserved | © Lalcrest Ltd