Chapter 5 Flashcards
Concept Mastery
The purpose of requirements life cycle management
ensure that business, stakeholder, and solution requirements and designs are aligned to one another
and that the solution implements them.
3 major components of the requirements life cycle management
- begins with the representation of a business need as a requirement,
- continues through the development of a solution, and
- ends when a solution and the requirements that represent it are retired.
The Requirements Life Cycle Management knowledge area includes the following tasks:
Trace Requirements, Maintain Requirements, Prioritize Requirements, Assess Requirements Changes, Approve Requirements
During Requirements Life Cycle
Management, business analysts what is change?
manage how proposed changes to requirements and designs are evaluated during an initiative.
During Requirements Life Cycle
Management, business analysts what is need?
trace, prioritize and maintain requirements to ensure that the need is met.
During Requirements Life Cycle
Management, business analysts what is Solution?
trace requirements and designs to solution components to ensure that the solution satisfies the need.
During Requirements Life Cycle Management, business analysts what is Stakeholder?
work closely with key stakeholders to maintain understanding, agreement, and approval of requirements and designs.
During Requirements Life Cycle Management, business analysts what is value?
maintain requirements for reuse to extend
value beyond the current initiative.
During Requirements Life Cycle Management, business analysts what is context?
analyze the context to support tracing and prioritization activities.
What is the purpose of trace requirements?
ensure that requirements and designs at different levels are aligned to one another, and to manage the effects of change to one level on related requirements.
Traceability is used to help ensure that
the solution conforms to requirements and to assist in scope, change, risk, time, cost, and communication management.
Traceability enables:
• faster and simpler impact analysis,
• more reliable discovery of inconsistencies and gaps in requirements,
• deeper insights into the scope and complexity of a change, and
• reliable assessment of which requirements have been addressed and which
have not.
relationships that the business analyst considers when
defining the traceability approach:
Derive, Depend, satisfy, validate
What is derive?
relationship between two requirements, used when a requirement is derived from another requirement.
What are the types of depend traceability?
necessity, effort
What is satisfy traceability?
relationship between an implementation element and the requirements it is satisfying.
What is validate traceability?
relationship between a requirement and a test case or other element that can determine whether a solution fulfills the requirement.
What are the guidelilnes/tools for traceability?
knowledge domain, Information Management Approach, Legal/Regulatory Information, Requirements Management Tools/Repository
What are some techniques for traceability?
Business Rules Analysis, Functional Decomposition, Process Modelling, Scope Modelling
What are the outputs of traceability?
Requirements and Design
The purpose of Maintain Requirements
retain requirement accuracy and consistency throughout and beyond the change during the entire requirements life cycle, and to support reuse of requirements in other solutions.
In order to maximize the benefits of maintaining and reusing requirements, the requirements should be:
consistently represented,
• reviewed and approved for maintenance using a standardized process that
defines proper access rights and ensures quality, and
• easily accessible and understandable.
What are the inputs for maintaining requirements?
Requirements and Design
What are the guidelines and tools of maintaining requirements?
Information Management Approach
