Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Estimation > Fundamental Estimation Techniques > Flashcards

Fundamental Estimation Techniques Flashcards

1
Q

What does it mean to estimate Size?

A

Estimating Size refers to estimating the scope of technical work of a given feature set - in units such as lines of code, function points, stories or some other measure.

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

What does it mean to estimate Features?

A

Estimating Features refers to estimating how many features can be delivered within schedule and budget constraints.

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

What is a Small project?

A

Around 5 tech people or less, duration of at most approx. 3 months.

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

What is a Medium project?

A

Around 5-25 tech people, projects which last 3-12 months

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

What is a Large project?

A

25 or more tech people, 6-12 months or more

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

How does a small project affect estimates?

A

Small projects typically can’t use the statistically oriented techniques that larger projects can because variations in individual productivity drown out other factors.
The best estimation techniques tend to be “bottom-up”, based on estimates created by individuals who will actually do the work.

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

How does a large project affect estimates?

A

The techniques differ significantly from the beginning of a project (Top-down-techniques), the middle (combination of top-down and bottom-up) and the end (Bottom-Up)

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

How does a medium project affect estimates?

A

They have the advantage of being able to use virtually all estimation techniques that large projects can use, and several of the small-project techniques, too.

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

Which development styles are important in relation to estimation?

A

Sequential, where a lot of requirements are defined upfront, vs iterative, where a lot of requirements are defined after construction is underway.

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

How does the development style affect estimates?

A

Both styles usually start top-down or statistically-based estimation and migrate toward bottom-up techniques.
Iterative projects transition to refining their estimates more quickly using project specific data.

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

Which factors should be taken into account when selecting estimation techniques?

A
  • What should be estimated (Size vs Features)
  • The size of the project
  • The development stage
  • The development style
  • Accuracy needed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is estimated with “Count”?

A

Size, Features

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

For which project sizes can “Count” be used?

A

Small, Medium and Large

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

In which Development Stages can “Count” be used?

A

Early, Middle and Late

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

For which development styles can “Count” be used?

A

Iterative and Sequential

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

Which level of accuracy is possible with “Count”?

A

High

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

What is estimated with “Compute”?

A

Size, Effort, Schedule, Features

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

For which project sizes can “Compute” be used?

A

Small, Medium and Large

19
Q

In which Development Stage can “Compute” be used?

A

Early and Middle

20
Q

For which Development Styles can “Compute” be used?

A

Iterative and Sequential

21
Q

Which level of accuracy is possible with “Compute”?

A

High

22
Q

What is “Count”?

A

Counting means to count things which are directly available. If the number of bugs is available, you can just count them instead of estimating them.

23
Q

What is “Compute”?

A

Some countable things are not directly related to effort. For instance, when counting requirements, often only the average effort per requirement is available. Applying this to the counted result is “Computing”.

24
Q

What are the guidelines to find something to be counted?

A
  • Count things which are correlated with the size of software
  • Count things which are available sooner than later
  • Count something that provides a meaningful average (at least 20 items)
  • Count something you understand and have checked your assumptions
  • Count something you can count with minimal effort
25
Q

How do you compute an estimate from a count?

A

You take historical data. For example, by counting the number of stories and multiply it with the average total effort per story.

26
Q

What is Judgement?

A

Judgement is added to an estimate not entirely based on historical data, such as: “Given the feedback from X, I think we will deliver in Y”, or “The room holds 50 people and I think it is half full now, so I estimate the total number of people to be 25”

27
Q

How should Judgement be used?

A

Not at all or only as a last resort, as this usually degrades the accuracy.

28
Q

What is estimated with “Calibration with Industry Data”?

A

Size, Effort, Schedule, Features

29
Q

What is estimated with “Calibration with Organizational Data”?

A

Size, Effort, Schedule, Features

30
Q

What is estimated with “Calibration with Project-Specific Data”?

A

Size, Effort, Schedule, Features

31
Q

For which project sizes can “Calibration with Industry Data” be used?

A

Small, Medium and Large

32
Q

For which project sizes can “Calibration with Organizational Data” be used?

A

Small, Medium and Large

33
Q

For which project sizes can “Calibration with Project-Specific Data” be used?

A

Small, Medium and Large

34
Q

In which Development Stage can “Calibration with Industry Data” be used?

A

Early-Middle

35
Q

In which Development Stage can “Calibration with Organizational Data” be used?

A

Early-Middle

36
Q

In which Development Stage can “Calibration with Project-Specific Data” be used?

A

Middle-Late

37
Q

For which Development Styles can “Calibration with Industry Data” be used?

A

Iterative, Sequential

38
Q

For which Development Styles can “Calibration with Organizational Data” be used?

A

Iterative, Sequential

39
Q

For which Development Styles can “Calibration with Project-Specific Data” be used?

A

Iterative, Sequential

40
Q

Which level of accuracy is possible with “Calibration with Industry Data”?

A

Low-Medium

41
Q

Which level of accuracy is possible with “Calibration with Organizational Data”?

A

Medium-High

42
Q

Which level of accuracy is possible with “Calibration with Project-Specific Data”?

A

High

43
Q

What is Calibration?

A

Calibration is used to convert counts to estimates by using available data.

44
Q

Which kinds of data can be used for Calibration?

A

Industry Data, which refers to data from other organizations that develop the same basic kind of software
Historical data/”Documented Facts”, which refers to data from the same organiziation
Project data, which refers to data generated earlier in the same project.

Software Estimation (2 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions