Scribd
Upload
32 views

SPM - Algorithmic Techniques Estimation

Uploaded by

Mohamed Kadry
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
32 views

SPM - Algorithmic Techniques Estimation

Uploaded by

Mohamed Kadry
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/ 4

By: Shaimaa Mostafa lecture 5 SPM

Algorithmic Techniques for Estimation: “Function Points”


There are TWO classes of metrics to measure effort required to develop application:

Productivity metrics: ‫مقاييس االنتاجيه‬


1. Function based metrics: measure number of complexity of functions to develop.
‫بقيس حجم السوفت وير بتاعي من وجهة نظرعدد الفانكشنز‬
• Advantage:
✓ Can estimated when requirement is ready.
✓ Not depend on specific programming language
• Disadvantage:
o Difficult to measure.
o Difficult to link.

2. Size based metrics: measure size of system by line of code


• Advantage:
✓ Easy to link.
• Disadvantage:
▪ Sensitive to programming language

Function Point(FP)
Combination of program from requirements. First suggested by Albrecht. First application in
business systems.

Steps:

1. Define boundary.
2. Measure Functional Requirements and use formula to get Unadjusted Function
Points(UFP)
3. Measure to Non-functional requirements: calculate Complexity Adjustments
Factor(CAF)
4. Calculate the Function Points: FP = UFP X CAF

There are 5 characteristics used in UFP, use : Simple, Average, Complex.

1. Input
2. Output
3. Files
4. Interface
5. Inquiry

There is a table given(required) “weigh complexity.


By: Shaimaa Mostafa lecture 5 SPM

CAF
Answer for 14 questions, each question takes a value (from 0 to 5), then sum all these numbers.

Formula: FP = UFP X (0.65 + 0.01 X CAF)

Example:

Given the following values, compute function point, when all complexity adjustment factor (CAF)
and weighting factors are average.

User Input = 50, User Output = 40, User Inquiries = 35, User Files = 6, External Interface = 4

Low Average High Low Average High


Input 3 4 6 Input 0 50 x 4 0
Output 4 5 7 Output 0 40 x 5 0
File 7 10 15 File 0 6 x 10 0
Interface 5 7 10 Interface 0 4x7 0
Inquiry 3 4 6 Inquiry 0 35 x 4 0

UFP = (50 x 4) + (40 x 5) + (6 x 10) + (4 x 7) + (35 x 4) = 628

CAF = 0---irrelevant, 1--- insignificant, 2--- moderate, 3--- average, 4--- significant, 5--- extremely
relevant. So, CAF = 14 x 3 = 42

FP = UFP X CAF

FP = 628 X ( 0.65 + 0.01 X 42) = 628 X 1.07 = 671.96


COCOMO

Basic COCOMO
COCOMO I (original ) Intermediate COCOMO
Detailed COCOMO

Application composition model


COCOMO II Early design model
Post-architecture model
By: Shaimaa Mostafa lecture 5 SPM

COCOMO I : different types of projects:

1. Organic → small team, good experience


2. Semi-detached → medium team, mix experience.
3. Advanced (embedded) → high constraints, combine of organic & semi – detached project.

• Program size estimate in KLOC(Kilo Line Of Code)


• Quick Estimate
• Limited accuracy
• Lack factor for differences in project attributes.
• Basic COCOMO equation:
➢ Effort(E): a x KLOCb
➢ Duration(D): 2.5 x (E)d
➢ Resources = Effort / Duration
Ex: use basic COCOMO model to estimate effort, duration, and number of resources for
intermediate project environment involving 8000 LOC
‫ لكن لو مش مديني الرقم اساسا فكده هعمل الطريقه االولى‬,‫ عشان احولها لكيلو من الكود‬1000 ‫ هقسم على‬8000 ‫نالحظ ان السايز معطى في المساله ب‬
‫للفانكشن بوينت عشان الحجم ويكون جدول اللغات موجود فيه االرقام كلها والرقم الي يطلع اضربو في جدول اللغات واجيب الرقم هنا اقسمو على‬
‫عشان يبقى بالكيلو واستعملو في الكوكو مو‬1000
Size must be in KLOC, so divide on 1000. Size = 8000 LOC/ 1000 = 8KLOC
Look: Use basic COCOMO model, but the value will use it for intermediate project
Effort(E): a x KLOCb
E = 3.0 X 81.12 = 30.8 person-month

Duration(D): 2.5 x Ed
D = 2.5 X (30.8)0.35 = 8.29 month

Resources = Effort / Duration


Resources = 30.8 / 8.29 = 3.71 person

• Account differences in projects attributes.


• Set of FOUR categories, each with number of attributes
1. Product 2. HW 3. Personnel 4. Project
• Nominal mean not affect in project.
• EAF: effort adjustment factor(cost driver)
• Intermediate COCOMO equation:

➢ Effort(E): a x KLOCb x EAF


➢ Duration(D): 2.5 x Ed
➢ Resources: Effort / Duration
By: Shaimaa Mostafa lecture 5 SPM

We sum the size because there are in KLOC no need to divide.

We will see the range in cost driver (EAF) in the table then multiple them.

Be careful, when use the table for basic project & intermediate project.
EAF = 1.15 x 1.06 x 1.13 x 1.17 = 1.6
Effort(E): a x KLOCb x EAF
E = 3.2 x 31.05 x 1.6 = 16.22 person – month
Duration(D): 2.5 x (E)d
D = 2.5 X (16.22)0.38 = 7.20 month
Resource = Effort / Duration
Resource = 16.22 / 7.20 = 2.25 person

• Given according to each phase of SDLC.


• Assess cost driver impact on each step.
• Software divided into modules.

End lecture 5

You might also like