Chapter 10 - Project Planning

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall with Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/60

flashcard set

Earn XP

Description and Tags

These flashcards cover key vocabulary and concepts related to project planning in software engineering, drawn from lecture notes on the topic.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No study sessions yet.

61 Terms

1
New cards

Project Plan

A document that outlines the resources available, work breakdown, schedule, and objectives for a plan-driven development project.

2
New cards

SWOT Analysis

A strategic planning tool used to identify Strengths, Weaknesses, Opportunities, and Threats related to a project or business.

3
New cards

Gantt Chart

A visual representation of a project schedule, showing the start and finish dates of various elements of a project.

4
New cards

COCOMO Model

A cost estimation model that calculates the effort and time required to develop software based on project attributes.

5
New cards

Agile Planning

An incremental approach to project management and software development that focuses on adaptability and customer feedback.

6
New cards

Cost Estimation Techniques

Methods used to estimate the expenses related to a project, including algorithmic models and expert judgment.

7
New cards

Plan-driven Development

A structured approach to software development that emphasizes upfront planning and documentation.

8
New cards

Project Scheduling

The process of organizing the work in a project into tasks, estimating the resources and time required to complete each task.

9
New cards

Milestone

A significant point in a project schedule used to mark the completion of a key phase or deliverable.

10
New cards

Resources

The people, equipment, and material resources needed to execute project tasks.

11
New cards

Specific, Measurable, Attainable, Relevant, Timely (SMART) Goals

A framework for setting clear and achievable goals that align with project objectives.

12
New cards

Quality Plan

Documentation that describes quality assurance practices and standards to be used during a project's lifecycle.

13
New cards

Validation Plan

A plan detailing the approach, resources, and timelines for system validation and testing.

14
New cards

Contingency Factor

An additional percentage added to project estimates to cover unforeseen obstacles or risks.

15
New cards

Activity Network

A graphical representation of the sequence of tasks in a project, illustrating dependencies and the critical path.

16
New cards

Which section is NOT typically part of a project plan in plan-driven development?

Marketing strategy

17
New cards

A distributor

Purchases from manufacturers and resells to retailers or public

18
New cards

Which business model charges low prices initially but extra for minor services?

Nickel and dime

19
New cards

The "Freemium" business model

Offers basic service for free and charges for premium services

20
New cards

When estimating task durations, a good rule of thumb is to

Estimate as if nothing will go wrong and then add contingency

21
New cards

What does a milestone represent in a Gantt chart?

A significant event or completion point

22
New cards

In a staff allocation chart, diagonally-slashed boxes indicate

Part-time work

23
New cards

The critical path in an activity network is

The longest sequence of activities determining minimum project time

24
New cards

Cost estimation techniques in project planning are used to estimate

The cost and effort required

25
New cards

Estimation uncertainty is

Highest at the start and decreases over time

26
New cards

In algorithmic cost modeling, the effort E is a function of

Product, project, process, and people attributes

27
New cards

What does COCOMO stand for?

Constructive Cost Model

28
New cards

COCOMO estimation models can be applied at which project phases?

Early design, application composition, post-architecture, etc.

29
New cards

An Integrated Computer-Aided Software Engineering (ICASE) environment typically includes

Application framework, utilities, domain components, and tools for design and testing

30
New cards

The Application Composition Model supports

Prototyping and projects with extensive reuse

31
New cards

Productivity (PROD) in the Application Composition Model is measured in

Application points per month

32
New cards

Which of the following is NOT part of NAP (Number of Application Points) estimation?

Number of users

33
New cards
34
New cards

According to Aaron Rababaah, if a factor has a negative impact on person-month effort, you should use

Negative multiplier row

35
New cards

When converting Unadjusted Function Points (UFP) to SLOC, the conversion depends on

The programming language used

36
New cards

In the Early Design Model, the effort PM is calculated using

A formula involving constants A, B, size, and multiplier M

37
New cards

Which of these is NOT a multiplier used in the Early Design Model?

CPU speed

38
New cards

Multipliers in the Early Design Model have values generally in the range

[1, 6]

39
New cards
40
New cards

The Reuse Model accounts for

Both black-box and white-box code reuse

41
New cards

Which of the following is NOT a factor contributing to white-box reuse effort?

Effort to market the software

42
New cards

In the Black Box Reuse Model, effort PM is proportional to

SLOC multiplied by AT over ATPROD

43
New cards

The Adaptation Adjustment Multiplier (AAM) is used in

White-box reuse to adjust estimated SLOC

44
New cards

The Post-architecture model uses

The same formula as Early Design, but with 17 multipliers

45
New cards

The exponent term "B" in COCOMO depends on how many scale factors?

5

46
New cards

The 17 multipliers in the Post-architecture model are categorized into all EXCEPT:

Marketing attributes

47
New cards

When a multiplier in the Post-architecture model is unknown, it should be assumed as

Nominal (neutral)

48
New cards

High values of reliability, complexity, memory constraints, low tool use, and accelerated schedule lead to

Higher effort estimates

49
New cards

Low values for reliability and complexity, with very high tool use, lead to

Lower effort estimates

50
New cards

The formula to estimate calendar time (TDEV) in COCOMO 2

TDEV = 3 (PM)^(0.33 + 0.2(B - 1.01))

51
New cards

Which statement about staffing requirements is TRUE?

Rapid build-up of people often causes schedule slippage

52
New cards

SMART stands for

Specific, Measurable, Attainable/Achievable, Relevant, Timely

53
New cards

Which project plan supplement describes the procedures for version management, system building, and release management?

Configuration management plan

54
New cards

What is the recommended contingency factor to cover unanticipated problems in project scheduling estimates?

30-50%

55
New cards

In project scheduling, the 'Critical Path' is

The sequence of activities taking the longest time

56
New cards

In algorithmic cost modeling, the effort (E) is estimated using the formula

E = A Size^B M

57
New cards

The Application Composition Model effort formula is

PM = (NAP * (1 - %reuse)) / PROD

58
New cards

Which of the following is NOT a factor that influences the exponent term 'B' in COCOMO models?

Marketing budget

59
New cards

In the Early Design model, what does multiplier 'RCPX' represent?

Product reliability and complexity

60
New cards

What is the main purpose of the Reuse Model in cost estimation?

To take into account reused code, both black-box and white-box

61
New cards

What happens to the total effort when more people are added rapidly to a project?

Total effort usually increases