5 Requirements Life Cycle Management Flashcards

1
Q

analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation.

A

Trace Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

ensures that requirements and designs are accurate and current throughout the life cycle and facilitates reuse where appropriate

A

Maintain Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

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.

A

Prioritize Requirements:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

evaluates new and changing stakeholder requirements to determine if they need to be acted on within the scope of a change.

A

Assess Requirements Changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

works with stakeholders involved in the governance process to reach approval and agreement on requirements and designs.

A

Approve Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

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.

A

Derive
(relationships)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

when it only makes sense to implement a particular requirement if a related requirement is also implemented.

A

Necessity
(Relationships)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

when a requirement is easier to implement if a related requirement is also implemented.

A

Effort
(Relationships)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

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.

A

Satisfy
(Relationships)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

relationship between a requirement and a test case or other element that can determine whether a solution fulfills the requirement.

A

Validate
(Relationships)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

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.

A

Traceability Repository

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Information such as the requirement’s source, priority, and complexity aid in managing each requirement throughout the life cycle.

A

Maintain Attributes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

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.

A

Reusing Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

is performed as** new needs** or possible solutions are identified.

A

Assess Requirements Changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

can be identified at any time and impact any aspect of business analysis work or deliverables completed to date

A

Proposed Change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

the assessment process based on the information available, the apparent importance of the change, and the governance process.

A

Assessment Formality

17
Q

is performed to assess or evaluate the effect of a change.

A

Impact Analysis

18
Q

Depending on the planned approach, various stakeholders (including the business analyst) may be authorized to approve, deny, or defer the proposed change.

A

Impact Resolution

19
Q

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.

A

Track and Communicate Approval