5 Requirements Life Cycle Management Flashcards
analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation.
Trace Requirements
ensures that requirements and designs are accurate and current throughout the life cycle and facilitates reuse where appropriate
Maintain Requirements
assesses the value, urgency, and risks associated with particular requirements and designs to ensure that analysis and/or delivery work is done on the most important ones at any given time.
Prioritize Requirements:
evaluates new and changing stakeholder requirements to determine if they need to be acted on within the scope of a change.
Assess Requirements Changes
works with stakeholders involved in the governance process to reach approval and agreement on requirements and designs.
Approve Requirements
relationship between two requirements, used when a requirement is derived from another requirement. This type of relationship is appropriate to link the requirements on different levels of abstraction. For example, a solution requirement derived from a business or a stakeholder requirement.
Derive
(relationships)
when it only makes sense to implement a particular requirement if a related requirement is also implemented.
Necessity
(Relationships)
when a requirement is easier to implement if a related requirement is also implemented.
Effort
(Relationships)
relationship between an implementation element and the requirements it is satisfying. For example, the relationship between a functional requirement and a solution component that is implementing it.
Satisfy
(Relationships)
relationship between a requirement and a test case or other element that can determine whether a solution fulfills the requirement.
Validate
(Relationships)
documented and maintained in accordance with the methods identified by the business analysis approach. Requirements management tools can provide significant benefits when there is a need to trace a large number of requirements that may be deemed unmanageable with manual approaches.
Traceability Repository
Information such as the requirement’s source, priority, and complexity aid in managing each requirement throughout the life cycle.
Maintain Attributes
Requirements that are candidates for long-term use by the organization are identified, clearly named, defined, and stored in a manner that makes them easily retrievable by other stakeholders.
Reusing Requirements
is performed as** new needs** or possible solutions are identified.
Assess Requirements Changes
can be identified at any time and impact any aspect of business analysis work or deliverables completed to date
Proposed Change
the assessment process based on the information available, the apparent importance of the change, and the governance process.
Assessment Formality
is performed to assess or evaluate the effect of a change.
Impact Analysis
Depending on the planned approach, various stakeholders (including the business analyst) may be authorized to approve, deny, or defer the proposed change.
Impact Resolution
The business analyst records approval decisions, possibly in requirements maintenance and tracking tools. In order to communicate the status of requirements, it is necessary to keep accurate records of current approval status.
Track and Communicate Approval