0% found this document useful (0 votes)
5 views14 pages

UCP Slides

Use Case Points (UCP) is a software estimation technique for forecasting software size in development projects using UML and RUP methodologies. Developed by Gustav Karner in 1993, UCP calculates software size based on use cases, factoring in technical and environmental considerations. The final UCP can be used to estimate project effort, as demonstrated with an example of an Online Shopping System resulting in an estimated effort of 3501 hours.

Uploaded by

hs22csb0f21
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views14 pages

UCP Slides

Use Case Points (UCP) is a software estimation technique for forecasting software size in development projects using UML and RUP methodologies. Developed by Gustav Karner in 1993, UCP calculates software size based on use cases, factoring in technical and environmental considerations. The final UCP can be used to estimate project effort, as demonstrated with an example of an Online Shopping System resulting in an estimated effort of 3501 hours.

Uploaded by

hs22csb0f21
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

11/6/2021

1
11/6/2021

• Use case points (UCP or UCPs) is a software estimation


technique used to forecast the software size for software
development projects.
• UCP is used when the Unified Modeling Language (UML) and
Rational Unified Process (RUP) methodologies are being
used for the software design and development.
• The concept of UCP is based on the requirements for the
system being written using use cases
• The software size (UCP) is calculated based on elements of
the system use cases with factoring to account for technical
and environmental considerations.
• The UCP for a project can then be used to calculate the
estimated effort for a project.

2
11/6/2021

History
• The UCP technique was developed by Gustav Karner in 1993 while
employed at what was known at the time as Objectory Systems, which
later merged into Rational Software and then IBM.

• The UCP method was created to solve for estimating the software size of
systems that were object oriented.

• It is based on similar principles as the Function Point (FP) estimation


method, but was designed for the specific needs of object oriented
systems and system requirements based on use cases

3
11/6/2021

Method
• The method for determining the size estimate to develop a system is based on a calculation with the
following elements:
• Unadjusted Use Case Weight (UUCW) – the point size of the software that accounts for the number
and complexity of use cases.
• Unadjusted Actor Weight (UAW) – the point size of the software that accounts for the number and
complexity of actors.
• Technical Complexity Factor (TCF) – factor that is used to adjust the size based on technical
considerations.
• Environmental Complexity Factor (ECF) – factor that is used to adjust the size based on
environmental considerations.
• Once the previous four elements have been calculated, the final size estimate can be calculated. This
final number is known as the use case points or UCP for a software development project.

• The following sections walk through the various calculations to determine the UCP for a project.

4
11/6/2021

Unadjusted Use Case Weight (UUCW)

UUCW = (Total No. of Simple Use Cases x 5) + (Total No. Average Use Cases
x 10) + (Total No. Complex Use Cases x 15)

5
11/6/2021

Unadjusted Actor Weight (UAW)

UAW = (Total No. of Simple actors x 1) +


(Total No. Average actors x 2) + (Total No. Complex actors x 3)

6
11/6/2021

Technical Complexity Factor (TCF)

TCF = 0.6 + (TF/100)

7
11/6/2021

Environmental Complexity Factor (ECF)

ECF = 1.4 + (-0.03 x EF)

8
11/6/2021

Use Case Points (UCP)

• Finally the UCP can be calculated once the


unadjusted project size (UUCW and UAW),
technical factor (TCF) and environmental factor
(ECF) have been determined.

• The UCP is calculated based on the following


formula:

UCP = (UUCW + UAW) x TCF x ECF

9
11/6/2021

Unadjusted Use Case Weight (UUCW)

• UCW = (Total No. of Simple Use Cases x 5) +


(Total No. Average Use Cases x 10) + (Total No.
Complex Use Cases x 15)

For the Online Shopping System, the


UUCW = (2 x 5) + (3 x 10) + (4 x 15) = 100

UUCW = 100

10
11/6/2021

Unadjusted Actor Weight (UAW)

• UAW = (Total No. of Simple Actors x 1) + (Total


No. Average Actors x 2) + (Total No. Complex
Actors x 3)

• For the Online Shopping System, UAW = (1 x 1)


+ (0 x 2) + (4 x 3) = 13
• UAW = 13

11
11/6/2021

Technical Complexity Factor (TCF)

For the Online Shopping System, TCF = 0.6 + (TF/100)

TCF = 0.6 + (42/100) = 1.02

12
11/6/2021

Environmental Complexity Factor (ECF)

13
11/6/2021

Use Case Points (UCP)


• UCP = (UUCW + UAW) x TCF x ECF

• UCP = (100 + 13) x 1.02 x 1.085 = 125.06

• UCP = 125.06

• For the Online Shopping System, the total estimated size to develop the software is 125.06
Use Case Points.

• Now that the size of the project is known, the total effort for the project can be estimated. For
the Online Shopping System example,

• if 28 man hours per use case point will be used.

• Estimated Effort = UCP x Hours/UCP


• For the Online Shopping System, Estimated Effort = 125.06 x 28
• Estimated Effort = 3501 Hours

14

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy