Unit 3 Waterfall Fundamentals: Process Groups and Knowledge Areas Part 1

Question 1

Business requirements

Answer 1

software features and functionality required to execute the business workflow and/or meet business guidelines and standards.

Question 2

Change control

Answer 2

the process of reviewing change requests, approving changes, and managing changes to deliverables and the project plan and communicating the decisions.

Question 3

Control schedule

Answer 3

monitoring and updating the project schedule to reflect the current task status and approved change requests.

Question 4

Gantt Chart

Answer 4

a graphical depiction of a project schedule showing tasks scheduled over time.

Question 5

Medical device

Answer 5

anything that could be used for the following applications:

• Manufacturing or dispensing medications.
• Diagnosing, mitigating, treating, or preventing disease in humans or other animals.

• Affecting the structure or function of the body of humans
or other animals.

Question 6

Medical device software

Answer 6

software used for operating a medical device, manufacturing a medical device, or supporting medical purposes that are not part of the hardware.

Question 7

Milestone

Answer 7

a task of zero duration that marks an important achievement in a project at a point in time.

Question 8

Post-mortem review

Answer 8

a meeting with all internal stakeholders and the project sponsor
to discuss how well the project was initiated, planned, executed, and controlled.

Question 9

Project baseline

Answer 9

a starting point from which to measure a project’s progress.
The three components of a project baseline include:

Scope baseline:
the first approved version of a scope statement and work breakdown structure (WBS).

• Schedule baseline:
the first approved version of the project schedule.

• Cost baseline:
the first approved version of the project budget.

Question 10

Project charter

Answer 10

a high-level document summarizing the general project information, problems, goals, deliverables, scope, schedule, resources, benefits, and risks. Its purpose is to define the project at a high level and tie it to the business case.

Question 11

Project integration management

Answer 11

the act of identifying, defining, coordinating, and managing the interrelationship between project management processes and activities.

Question 12

Project knowledge

Answer 12

the combination of project documentation and the skills, experience, and expertise of the project team and other stakeholders used before, during, and after the project.

Question 13

Project life cycle

Answer 13

the five phases that PMs follow to manage a project from initiation to closure.

Question 14

Project Management Body of Knowledge (PMBOK)

Answer 14

a set of standard project management guidelines published by the Project Management Institute (PMI).

Question 15

Project management plan

Answer 15

a document consisting of the project schedule and budget that describes the process for carrying out the project.

Question 16

Project schedule

Answer 16

a timetable that outlines start and end dates and milestones that must be met for the project to be completed on time.

Question 17

Project schedule management

Answer 17

planning and monitoring how and when the project will deliver work products as defined in the project WBS.

Question 18

Project schedule management plan

Answer 18

describes how the schedule will be developed, monitored, and controlled.

Question 19

Project scope management

Answer 19

the act of ensuring that the project includes only the work required to complete the project successfully.

Question 20

Project stakeholder management

Answer 20

the act of identifying the individuals, groups, or organizations that may impact, or be impacted by, the project.

Question 21

Requirements elicitation

Answer 21

the process of gathering requirements and analyzing them to produce a set of requirements.

• Document analysis:
reviewing paper or electronic documentation to determine software requirements.

• Interviews:
questions verbally asked by BA of one or more specific stakeholders that might or might not be predefined.

• Observations:
looking and/or listening to stakeholders performing a task related to the software being created.

• Surveys:
a set of predefined questions that a BA asks a stakeholder, either in written or verbal form.

Question 22

Requirements gathering

Answer 22

the process of writing down what stakeholders say they want.

Question 23

Requirements specification

Answer 23

a document written by the business analyst with input from the end users and project team containing text statements and diagrams describing how the software product should function.

Question 24

Requirements Traceability Matrix (RTM)

Answer 24

links each requirement to the associated design document and test case used to implement the requirement.

Question 25

Scope

Answer 25

all the functional pieces that make up the final project deliverable.

Question 26

Scope creep

Answer 26

uncontrolled addition of product features or project deliverables without adjustments to time, cost, and resources.

Question 27

Scope management plan

Answer 27

a document written by the project manager with input from the sponsors containing several sections that describe how the project and product scope will be defined, validated, and controlled. Sections include:

• Scope statement:
lists the product features and project deliverables
to be created during the project.

• Work breakdown structure (WBS):
a hierarchy diagram that breaks down the project scope, as defined in the project charter, into smaller pieces.

Question 28

Stakeholder

Answer 28

a person who has an interest in or is responsible for a project
or project component.

• Internal stakeholder:
a stakeholder who works for the organization executing the project.

• External stakeholder:
a stakeholder who does not work for the organization executing the project.

• Key stakeholders:
stakeholders who rank as high interest and high power on a power/interest grid.

Question 29

Stakeholder register

Answer 29

a document that lists internal and external project stakeholders and identifying information about them pertaining to the project.

Question 30

System requirements

Answer 30

technical and measurable specifications for the development team to understand how to practically meet user requirements using available technologies.

Question 31

Functional system requirements

Answer 31

the requirements specifically used by software developers to create the software design.

– General system requirements:
used in waterfall development as more detailed user requirements.

– Interface requirements:
System requirements that must be met for the software to communicate with another system.

– Regulatory requirements:
Requirements resulting from government or industry standards to be met by the software.

Question 32

Non-functional system requirements

Answer 32

specify criteria that can be used to judge the operation of a system rather than specific behaviors.

– Performance requirements:
define how well the system should perform certain functions under specific conditions.

– Recoverability requirements:
specifications to recover the system to normal operations in the event it goes offline.

– Security requirements:
features the system must possess to administratively, physically, and technically safeguard it.

Question 33

Task list

Answer 33

a detailed table view of the work items in the WBS containing tasks necessary to create the work items.

Question 34

User requirements

Answer 34

features and functionality expected of users of a software product. They explain from a user’s perspective why a business requirement is important to the end user.

Question 35

Waterfall methodology

Answer 35

a software development methodology where one phase immediately follows the next. Phases include: requirements, design, development, testing, deployment, and maintenance.

Question 36

Explain the purpose of project stakeholder management.

Question 37

Complete a stakeholder register for a waterfall software project.

Question 38

Describe the purpose of project integration management.

Question 39

Write a project charter for a waterfall software project using a business case and template.

Question 40

Create the outline of a project management plan for a waterfall customization project.

Question 41

Explain the purpose of the project management plan.

Question 42

Define the scope management plan and its components.

Question 43

Fill in a work breakdown structure for a waterfall customization project.

Question 44

Analyze a business case to determine business requirements.

Question 45

Differentiate between business, user, system, regulatory, interface, and performance requirements.

Question 46

Compare and contrast various requirements elicitation techniques.

Question 47

Document business requirements as statements in industry-standard language.

Question 48

Determine dependencies for project activities in a project task list based on knowledge of the sequence of software development artifact creation.

Question 49

Determine project schedule task start dates based on dependencies in the task list to complete a Gantt chart.