Chapter 30

Question 1

Does software requirements should be stable for software sizing/estimation

Answer 1

Yes

Question 2

What is software sizing

Answer 2

In terms of project planing, size refers to a quantifiable outcome of the software project.

Question 3

What are 2 approaches of size measurement

Answer 3

1- Direct approach (measured in Line of Code)

2- Indirect approach (measured in functional point)

Question 4

What are 3 decomposition techniques

Answer 4

1- Fuzzy logic sizing
2- Standard component sizing
3- Change sizing

Question 5

What is fuzzy logic sizing

Answer 5

This approach uses the approximate reasoning techniques that are the cornerstones of fuzzy logic. planner can consult to historical database of
projects to guess better idea of estimation.

Question 6

What is functional point sizing

Answer 6

The planner develops estimates of the information domain.

Question 7

What is standard component sizing

Answer 7

Software is composed of a number of different “standard components” that are generic to a particular application area. standard components examples are subsystems, modules, screens, reports, interactive programs, batch programs, files, LOC and object-oriented insructions. Project planner estimates the number of occurances of each standard component and then use historical data to determine size per standard unit.

Question 8

What is combined size value

Answer 8

The number of lines of code calculated and computational results are called combined size value for a project.

Question 9

Which approach is used when software updates

Answer 9

Standard component sizing

Question 10

What are the benefits of using WBS

Answer 10

1. It gives an idea to management about the complexity and size of the project.
2. It helps in planning, scheduling and monitoring a project realistically.

Question 11

What is PERT

Answer 11

Program evaluation and review techniques

Question 12

What is measuring effort for a project

Answer 12

cost estimation

Question 13

What are techniques for measure effort for project/cost estimation

Answer 13

1. (SLOC) Source lines of code is technique for cost estimation/measure effort for project
2. Functional point (FP)
3. (COCOMO) Constructive cost model
4. Delphi technique

Question 14

What is delphi technique

Answer 14

For cost estimation, in addition to quantitative estimation techniques, there is human based technique known as Delphi Technique

Question 15

What is KLOC (thousand lines of code)

Answer 15

The effort spent on creating the source lines of code is expressed in relation to thousand lines of code

Question 16

Does SLOC language dependent

Answer 16

Yes

Question 17

What is the most famous technique used for project cost estimation

Answer 17

FP

Question 18

What is FP technique

Answer 18

Instead line by line technique like SLOC, it uses output-oriented technique

Question 19

What is FP gradation for different sized projects

Answer 19

For small projects: 10-99
For medium projects: 100-999
For large projects: 1000-9999
For very large projects: >10k

Question 20

Which cost estimation technique is language independent

Answer 20

FP