Effort Estimation 2

Question 1

Software Sizing: LOC vs. FP

Answer 1

• (LOC = Lines of Code) Different programming languages need different number of lines of code for the same program
• (FP = Function Point) Estimation based on external design independent of programming language

Question 2

Function Point Method

Answer 2

Function point - size measure based on a combination of system characteristics from a userʼs view

Question 3

Function Point Counting Rules

Answer 3

1. Identify elementary processes (user functions)
   a) Smallest unity of activity that is meaningful to the user
   b) Self-contained (leaves the application in a consistent state)
2. Classify each elementary process based on its primary intent
   a) input, output, or inquiry
3. Identify logical and user identifiable groups of data
4. Classify each group of data as external or internal data
5. Assess the complexity of each
   a) elementary process
   b) group of data

Question 4

Estimating the Program Size

Answer 4

To estimate the program size in COCOMO II considers:
- the size of code that is reused
- stability of requirements (requirements volatility, REVL)

Question 5

Scale Factors

Answer 5

1. Precedentness (PREF)
   - Are there former experience with similar projects?
2. Development flexibility (FLEX)
   - Can we freely choose the development process?
3. Architecture / risk resolution (RESL)
   - Do we have high skills in risk management and architecture design?
4. Team cohesion (TEAM)
   - Is the project team experienced and homogenious?
5. Process maturity (PMAT)
   - Do we apply mature process (according to CMMI)?

Question 6

SCED Effort Multiplier

Answer 6

A SCED rating of very low corresponds to an Effort Multiplier of 1.43 resulting in a schedule compression of at most 75% of the nominal schedule.