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

LEC21

Uploaded by

Aayush Dhakad
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

LEC21

Uploaded by

Aayush Dhakad
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/12/2024

Lecture Topic: UCP

By : Dr. Anjali
Assistant Professor
ABV-IIITM Gwalior

USE-CASE
PRESENTATION TITLE

A Use-Case is a series of Use-Cases are a way to


related interactions capture functional
between a user and a requirements of a system.
system that enables the The user of the system is
user to achieve a goal. referred to as an ‘Actor’.

1
11/12/2024

U S E - C AS E P O IN T S – D E F I NI TI ON
PRESENTATION TITLE

• Use-Case Points (UCP) is a software estimation technique used to measure the


software size with use cases. The concept of UCP is similar to FPs.
• The number of UCPs in a project is based on the following −
• The number and complexity of the use cases in the system.
• The number and complexity of the actors on the system.
• Various non-functional requirements (such as portability, performance,
maintainability) that are not written as use cases.
• The environment in which the project will be developed (such as the language,
the team’s motivation, etc.)

HI S T O R Y O F US E - CA SE P O I N T S
PRESENTATION TITLE

• The Use-Case Point estimation method was introduced by Gustav Karner in 1993. The
work was later licensed by Rational Software that merged into IBM.

2
11/12/2024

U S E - C AS E P O IN T S C O U N T ING P R O C E S S
PRESENTATION TITLE

The Use-Case Points counting process has the following steps −

Calculate unadjusted UCPs

Adjust for technical complexity

Adjust for environmental complexity

Calculate adjusted UCPs


5

STEP 1: CALCULATE UNADJUSTED USE-CASE POINTS.


PRESENTATION TITLE

1 2 3
Determine Determine Calculate Unadjusted
Unadjusted Use-Case Unadjusted Actor Use-Case Points
Weight Weight

3
11/12/2024

S T EP 1 . 1 − D E T E R MI N E U N A D J US TE D U S E -
PRESENTATION TITLE

C A S E W E IG H T .

Step 1.1.1 − Find the number of transactions in each Use-Case.

If the Use-Cases are written with User Goal Levels, a transaction is


equivalent to a step in the Use-Case. Find the number of transactions
by counting the steps in the Use-Case.
7

STEP 1.1 − DETERMINE UNADJUSTED USE-


PRESENTATION TITLE

CASE WEIGHT.

Step 1.1.2 − Classify each USE-CASE NUMBER OF USE-CASE


Use-Case as Simple, Average COMPLEXITY TRANSACTIONS WEIGHT

or Complex based on the


number of transactions in the Simple ≤3 5
Use-Case. Also, assign Use-
Case Weight as shown in the Average 4 to 7 10
following table −
Complex >7 15

4
11/12/2024

ST EP 1 . 1 − D E T E R MI N E U N A D J US TE D U S E -
PRESENTATION TITLE

C A S E W E IG H T .
• Repeat for each Use-Case and get all the Use-Case Weights. Unadjusted Use-Case
Weight (UUCW) is the sum of all the Use-Case Weights.

S T EP 1 . 1 − D E T E R MI N E U N A D J US TE D U S E -
PRESENTATION TITLE

C A S E W E IG H T .
Use- Number
Use-Case
• Step 1.1.4 − Find Unadjusted Case of Use- Product
Complexity
Use-Case Weight (UUCW) using Weight Cases
the following table −
Simple 5 NSUC 5 × NSUC

Average 10 NAUC 10 × NAUC


Where,
NSUC is the no. of Simple Use-Cases. Complex 15 NCUC 15 × NCUC
NAUC is the no. of Average Use-Cases.
NCUC is the no. of Complex Use-Cases.
5 × NSUC + 10
Unadjusted Use-Case Weight
× NAUC + 15 ×
(UUCW)
NCUC
10

10

5
11/12/2024

S T EP 1 . 2 − D E T E R MI NE U N A D JUS T E D A C T O R
PRESENTATION TITLE

W E I G HT .
Actor Actor
Example
Complexity Weight
• Step 1.2.1 − Classify Actors
as Simple, Average and A System with
Complex and assign Actor Simple 1
defined API
Weights as shown in the
following table −
A System interacting
Average 2
through a Protocol

A User interacting
Complex 3
11
through GUI

11

S T EP 1 . 2 − D E T E R MI NE U N A D JUS T E D A C T O R
PRESENTATION TITLE

WEIGHT.
• Repeat for each Actor and get all the Actor Weights. Unadjusted Actor Weight (UAW)
is the sum of all the Actor Weights.

12

12

6
11/12/2024

PRESENTATION TITLE

STEP 1.2 − DETERMINE UNADJUSTED ACTOR WEIGHT.

Actor Actor Number of


Product
Complexity Weight Actors
Step 1.2.3 − Find Unadjusted Actor
Weight (UAW) using the following Simple 1 NSA 1 × NSA
table −
Where, Average 2 NAA 2 × NAA
NSA is the no. of Simple Actors. Complex 3 NCA 3 × NCA
NAA is the no. of Average Actors.
1 × NSA + 2 ×
NCA is the no. of Complex Actors. Unadjusted Actor Weight (UAW)
NAA + 3 × NCA

13

13

Factor Description Weight


STEP 2: ADJUST T1 Distributed System 2.0
PRESENTATION TITLE

FOR TECHNICAL Response time or throughput performance


COMPLEXITY T2 1.0
objectives
T3 End user efficiency 1.0
Step 2.1 − Consider the 13 Factors that
contribute to the impact of the Technical T4 Complex internal processing 1.0
Complexity of a project on Use-Case
Points and their corresponding Weights T5 Code must be reusable 1.0
as given in the following table − T6 Easy to install .5
T7 Easy to use .5
T8 Portable 2.0
T9 Easy to change 1.0
T10 Concurrent 1.0
T11 Includes special security objectives 1.0
14
T12 Provides direct access for third parties 1.0
T13 Special user training facilities are required 1.0

14

7
11/12/2024

STEP 2: ADJUST FOR TECHNICAL


PRESENTATION TITLE

COMPLEXITY

Step 2.2 − For each of the 13 Factors, assess the project and
rate from 0 (irrelevant) to 5 (very important).

Step 2.3 − Calculate the Impact of the Factor from Impact


Weight of the Factor and the Rated Value for the project as

Impact of the Factor = Impact Weight × Rated Value


15

15

Weight Rated Value (0 Impact (I = W


Factor Description
(W) to 5) (RV) × RV)

STEP 2: ADJUST
PRESENTATION TITLE

T1 Distributed System 2.0


Response time or throughput
FOR TECHNI CA L T2
performance objectives
1.0

COMPLEXI TY T3 End user efficiency 1.0


T4 Complex internal processing 1.0
T5 Code must be reusable 1.0
Step (2.4) − Calculate the sum of
T6 Easy to install .5
Impact of all the Factors. This
gives the Total Technical Factor T7 Easy to use .5
(TFactor) as given in table below − T8 Portable 2.0
T9 Easy to change 1.0
T10 Concurrent 1.0
Includes special security
T11 1.0
objectives
Provides direct access for
T12 1.0
third parties
16 Special user training facilities
T13 1.0
are required
Total Technical Factor (TFactor)
16

8
11/12/2024

S T E P 2 : A D J U S T F O R T E C H N ICA L C O M P LE XIT Y
PRESENTATION TITLE

• Step 2.5 − Calculate the Technical Complexity Factor (TCF) as −


• TCF = 0.6 + (0.01 × TFactor)

17

17

STEP 3: ADJUST FOR ENVIRONMENTAL COMPLEXITY


PRESENTATION TITLE

Factor Description Weight


• Step 3.1 − Consider the 8 Familiar with the project model
F1 1.5
Environmental Factors that that is used
could affect the project F2 Application experience .5
execution and their
corresponding Weights as given F3 Object-oriented experience 1.0
in the following table −
F4 Lead analyst capability .5
F5 Motivation 1.0
F6 Stable requirements 2.0
F7 Part-time staff -1.0
18
F8 Difficult programming language -1.0

18

9
11/12/2024

STEP 3: ADJUST FOR ENVIRONMENTAL COMPLEXITY


PRESENTATION TITLE

Step 3.2 − For each of the 8 Factors, assess the project and
rate from 0 (irrelevant) to 5 (very important).

Step 3.3 − Calculate the Impact of the Factor from Impact


Weight of the Factor and the Rated Value for the project as

Impact of the Factor = Impact Weight × Rated Value

19

19

STEP 3: ADJUST FOR ENVIRONMENTAL COMPLEXITY


PRESENTATION TITLE

Weight Rated Value Impact (I =


Factor Description
(W) (0 to 5) (RV) W × RV)
• Step 3.4 − Calculate the sum of Familiar with the
Impact of all the Factors. This F1 project model that is 1.5
gives the Total Environment used

Factor (EFactor) as given in the F2 Application experience .5


following table − F3
Object-oriented
1.0
experience
F4 Lead analyst capability .5
F5 Motivation 1.0
F6 Stable requirements 2.0
F7 Part-time staff -1.0
Difficult programming
F8 -1.0
20 language
Total Environment Factor (EFactor)

20

10
11/12/2024

STEP 3: ADJUST FOR ENVIRONMENTAL COMPLEXITY


PRESENTATION TITLE

• Step 3.5 − Calculate the Environmental Factor (EF) as −


• 1.4 + (-0.03 × EFactor)

21

21

STEP 4: CALCULATE ADJUSTED USE-CASE POINTS (UCP)


PRESENTATION TITLE

Calculate Adjusted Use-Case


Points (UCP) as −
UCP = UUCP × TCF × EF
22

22

11
11/12/2024

PRESENTATION TITLE

EXAMPLE – THE
ONLINE SHOPPING
SYSTEM

23

23

UUCW AND UAW


CALCULATION
24

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


• (Total No. Average Actors x 2) + (Total No. Complex Actors x 3)
• UAW = (1 x 1) + (0 x 2) + (4 x 3) = 13
• UUCW = (Total No. of Simple Use Cases x 5) + (Total No. Average Use
Cases x 10) + (Total No. Complex Use Cases x 15)
• UUCW = (2 x 5) + (3 x 10) + (4 x 15) = 100

24

12
11/12/2024

TCF CALCULATI ON
PRESENTATION TITLE

TCF = 0.6 + (TF*0.01)


TCF = 0.6 + (42*0.01) = 1.02

25

25

ECF CA LCULA TION


PRESENTATION TITLE

ECF = 1.4 + (-0.03 * EF)


ECF = 1.4 + (-0.03 * 10.5) = 1.085

26

26

13
11/12/2024

USE CASE POINTS


• UCP = (UUCW + UAW) x TCF x ECF
• UCP = (100 + 13) x 1.02 x 1.085 = 125.06
27

• The total estimated size to develop the software is 125.06 Use Case Points
• For the Online Shopping System example, 28 man hours per use case point
will be used
• Estimated Effort = UCP x Hours/UCP
• Estimated Effort = 125.06 x 28= 3501 Hours

27

THANK YOU

28

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