Title: Use Case Points
1Use Case Points
2Use Case Points
Use Case Points (UCP) is a current technique for
measuring functionality of a software system. It
can be used for each use case or all use cases.
Apparently also called use case function
points, based on analogy to function point
metric.
3Use-Case Points
- A size and effort estimation technique that was
developed around use cases - Better for OOSAD projects than function points
- Requires at a minimum
- The set of essential use cases
- The use case diagram
- All actors and use cases classified as simple,
average, or complex
4Steps of UCP (Use Case Points) Estimation
For each use case
- Classify actors, to determine UAW (Unadjusted
Actor weight) - Classify use case, to determine UUCW (Unadjusted
Use case Weight) - Compute UUCP (Unadjusted Use Case Points)
- Compute technical and environmental factors
- Computer the Adjusted Use Case Points
- Translate into an estimate of human effort
5Steps in UCFP Estimation
- 1. Determine the UAW (Unadjusted Actor weight)
- Using the Actor Classification Table determine
the classification of each of the actors in the
system. - Add the values of all the actors to determine the
unadjusted actor weight of the system.
6Actor Classification Table
Classification Test to recognize classification Value/Factor
Simple Communicate to system through API. 1
Average Interact with the system through some protocol (HTTP, FTP, or probably some user defined protocol), or Are data stores (Files, RDBMS). 2
Complex Interacts through HCI (GUI) 3
7Steps in UCFP Estimation
- Determine number of UUCW (Unadjusted Use case
Weight) - Using the Use Case Classification Table,
determine the classification of each use case on
the use case diagram. - Add the values of each use case to yield the
unadjusted use case weight.
8Use Case Classification Table
Use Case Type Test to recognize classification Value/Factor
Simple 1-3 transactions 5
Average 4-7 transactions 10
Complex More than 7 transactions 15
9Steps in UCFP Estimation
- Determine Total UUCP (Unadjusted Use Case Points)
using the formula below. - Total UUCP Total UAW Total UUCW.
10Technical Complexity Factors
Factor Number Description Weight
T1 Distributed system 2.0
T2 Response time or throughput performance objectives 1.0
T3 End-user online efficiency 1.0
T4 Complex internal processing 1.0
T5 Reusability of code 1.0
T6 Easy to install 0.5
T7 Ease of use 0.5
T8 Portability 2.0
T9 Ease of change 1.0
Technical Complexity Factor (TCF) 0.6 (0.01
TFactor)
11Environmental Factors
Factor Number Description Weight
E1 Familiarity with system development process in use 1.5
E2 Application experience 0.5
E3 Object-oriented experience 1.0
E4 Lead analyst capability 0.5
E5 Motivation 1.0
E6 Requirements stability 2.0
E7 Part time staff -1.0
E8 Difficulty of programming language -1.0
Environmental Factor (EF) 1.4 (-0.03
EFactor)
12Person-Hours Multiplier
- If the sum of (number of Efactors E1 through E6
assigned value lt 3) and (number of Efactors E7
and E8 assigned value gt 3) 2 - PHM 20
- Else If the sum of (number of Efactors E1 through
E6 assigned value lt 3) and (number of Efactors
E7 and E8 assigned value gt 3) 3 or 4 - PHM 28
- Else
- Rethink project it has too high of a risk for
failure
13Computing Use-Case Points
- Adjusted Use Case Points (UCP)
- UUCP TCF ECF
- Effort in Person Hours
- UCP PHM