Lecture 7 - Software Estimation I Flashcards

1
Q

In Scope management, what does Scoping mean?

A

Define boundaries of the project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the elements that make up Scope Management? (3)

A
  • Time
  • Resources
  • Functionality
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is Brook’s Law?

A

Adding a human resource to a late software project makes it later

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

5 persons working full time for six weeks in a project, 35 hours of work per week. What is the Work Effort?

A

Work Effort = (5 persons x 6 weeks x 35 hours/week) = 1050 person-hours

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is “productive effort”?

A

A person’s effort on project related tasks. Excludes lunch, coffee, team meetings, etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

TF: Effort and Cost estimation all you to estimate how many features can be delivered within a specific development iteration

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

TF: Estimating time needed for defect correction work is a benefit of Effort and Cost Estimation

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a solution for a project that is over-scoped?

A

Reduce scope by defining a feature subset (release/project baseline) such that it is no longer over-scoped

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How do you define requirements baseline-steps? (3)

A
  • Establish business value
  • Assess effort (person-hours) required to develop feature
  • Assess risk involved in developing feature
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

TF: Assessing scope effort early in the project is easy

A

False. Difficult to estimate since requirements not detailed and design unclear

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

TF: A factor to consider when assessing scope risk is new unproven technologies being used

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the Priority categories in Requirements Priority? (3)

A
  • Critical
  • Important
  • Useful
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What does it mean if a requirement is said to be Critical in Requirement Priority?

A

Means requirement must be incorporated in next product release

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What does it mean if a requirement is said to be Important in Requirement Priority?

A

Means requirement is necessary but can be deferred to later release if necessary

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What does it mean if a requirement is said to be Useful in Requirement Priority?

A

Means it would be nice to have, but might be dropped if there is insufficient time or resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the Prioritization techniques? (3)

A
  • Ranking
  • Grouping
  • Hundred-dollar method
17
Q

How does the Ranking prioritization technique work?

A

Rank requirements using a scale

18
Q

How does the Grouping prioritization technique work?

A

Group requirements based on priority groups (critical, important, useful)

19
Q

How does the Hundred-dollar method prioritization technique work?

A

Stakeholders get a conceptual $100 to distribute among requirements

20
Q

What is the first principle of Estimation Fundamental Principles?

A

An estimate is a projection from past to future, accounting for differences between past and future

21
Q

How is the past captured in the first principle of Estimation Fundamentals?

A

Historical data

22
Q

How is the future captured in the first principle of Estimation Fundamentals?

A

Requirements for the software to be developed

23
Q

In the second principle of Estimation Fundamental Principles, all estimates are based on…

A
  • Set of assumptions that must be realized
  • Set of constraints that must be satisfied
24
Q

What is an assumption?

A

Statement taken to be true without verifying
(ex: might be assumed that productivity factor for project will be 500 lines of code per month)

25
Q

What is a constraint?

A

An externally imposed condition that must be observed
(ex: project might be constrained to 5 people for 6 months)

26
Q

Say you are given the constraint that 5 people will work for 6 months, and that similar past projects had an average of 50 delivered source lines of code (DSLOC) per person month, what product can we build?

A

5 people x 6 month = 30 person-months
50 x 30 = 1500 DSLOC per person-month

27
Q

What is the third principle of Estimation Fundamental Principles?

A

Projects must be re-estimated periodically as understanding grows and aperiodically as project parameters change

28
Q

How often should re-estimation and re-planning occur for a project less than 12 months long?

A

Monthly basis

29
Q

How often should re-estimation and re-planning occur for a project more than 12 months long?

A

Quarterly basis

30
Q
A