Unit 3 Waterfall Fundamentals: Process Groups and Knowledge Areas Part 1 Flashcards
Business requirements
software features and functionality required to execute the business workflow and/or meet business guidelines and standards.
Change control
the process of reviewing change requests, approving changes, and managing changes to deliverables and the project plan and communicating the decisions.
Control schedule
monitoring and updating the project schedule to reflect the current task status and approved change requests.
Gantt Chart
a graphical depiction of a project schedule showing tasks scheduled over time.
Medical device
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.
Medical device software
software used for operating a medical device, manufacturing a medical device, or supporting medical purposes that are not part of the hardware.
Milestone
a task of zero duration that marks an important achievement in a project at a point in time.
Post-mortem review
a meeting with all internal stakeholders and the project sponsor
to discuss how well the project was initiated, planned, executed, and controlled.
Project baseline
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.
Project charter
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.
Project integration management
the act of identifying, defining, coordinating, and managing the interrelationship between project management processes and activities.
Project knowledge
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.
Project life cycle
the five phases that PMs follow to manage a project from initiation to closure.
Project Management Body of Knowledge (PMBOK)
a set of standard project management guidelines published by the Project Management Institute (PMI).
Project management plan
a document consisting of the project schedule and budget that describes the process for carrying out the project.
Project schedule
a timetable that outlines start and end dates and milestones that must be met for the project to be completed on time.
Project schedule management
planning and monitoring how and when the project will deliver work products as defined in the project WBS.
Project schedule management plan
describes how the schedule will be developed, monitored, and controlled.
Project scope management
the act of ensuring that the project includes only the work required to complete the project successfully.
Project stakeholder management
the act of identifying the individuals, groups, or organizations that may impact, or be impacted by, the project.
Requirements elicitation
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.
Requirements gathering
the process of writing down what stakeholders say they want.
Requirements specification
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.
Requirements Traceability Matrix (RTM)
links each requirement to the associated design document and test case used to implement the requirement.
Scope
all the functional pieces that make up the final project deliverable.
Scope creep
uncontrolled addition of product features or project deliverables without adjustments to time, cost, and resources.
Scope management plan
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.
Stakeholder
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.
Stakeholder register
a document that lists internal and external project stakeholders and identifying information about them pertaining to the project.
System requirements
technical and measurable specifications for the development team to understand how to practically meet user requirements using available technologies.
Functional system requirements
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.
Non-functional system requirements
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.
Task list
a detailed table view of the work items in the WBS containing tasks necessary to create the work items.
User requirements
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.
Waterfall methodology
a software development methodology where one phase immediately follows the next. Phases include: requirements, design, development, testing, deployment, and maintenance.
Explain the purpose of project stakeholder management.
Complete a stakeholder register for a waterfall software project.
Describe the purpose of project integration management.
Write a project charter for a waterfall software project using a business case and template.
Create the outline of a project management plan for a waterfall customization project.
Explain the purpose of the project management plan.
Define the scope management plan and its components.
Fill in a work breakdown structure for a waterfall customization project.
Analyze a business case to determine business requirements.
Differentiate between business, user, system, regulatory, interface, and performance requirements.
Compare and contrast various requirements elicitation techniques.
Document business requirements as statements in industry-standard language.
Determine dependencies for project activities in a project task list based on knowledge of the sequence of software development artifact creation.
Determine project schedule task start dates based on dependencies in the task list to complete a Gantt chart.
