Requirements Life Cycle Management Flashcards

1
Q

Purpose of the Requirements Life Cycle Management knowledge area

A

Manage & maintain requirements & design info from inception to retirement. Establish meaningful relationships between related requirements & designs, & assess, analyze & gain consensus on proposed changes to requirements & designs.

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

Requirements Life Cycle Management Tasks

A
  1. Trace Requirements
  2. Maintain Requirements
  3. Prioritize Requirements
  4. Assess Requirements Changes
  5. Approve Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Requirements Life Cycle Management Inputs

A
  1. Requirements
  2. Designs
  3. Proposed Change
  4. Requirements (verified)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Requirements Life Cycle Management Outputs

A
  1. Requirements (traced)
  2. Designs (traced)
  3. Requirements (maintained)
  4. Designs (maintained)
  5. Requirements (prioritized)
  6. Designs (prioritized)
  7. Requirements Change Assessment
  8. Designs Change Assessment
  9. Requirements (approved)
  10. Designs (approved)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Input(s) to 5.1 Trace Requirements

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

Output(s) of 5.1 Trace Requirements

A
  1. Requirements (traced)
  2. Designs (traced)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Derive Relationship (Requirements)

A

Relationship between two requirements where one requirement is derived from another requirement.

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

Depends Relationship (Requirements)

A

Relationship between two requirements where one requirement depends on another requirement.

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

Types of Dependency Relationships (Requirements)

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

Dependency Relationship of Necessity

A

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

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

Dependency Relationship of Effort

A

When a requirement is easier to implement if a related requirement is also implemented

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

Satisfy Relationship

A

Relationship between an implementation element and the requirements it is satisfying.

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

Validate Relationship

A

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

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

Input(s) to 5.2 Maintain Requirements

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

Output(s) of 5.2 Maintain Requirements

A
  1. Requirements (maintained)
  2. Designs (maintained)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Input(s) to 5.3 Prioritize Requirements

A
  1. Requirements
  2. Designs
17
Q

Output(s) of 5.3 Prioritize Requirements

A
  1. Requirements (prioritized)
  2. Designs (prioritized)
18
Q

Factors that influence requirements prioritization

A
  1. Benefit
  2. Penalty
  3. Cost
  4. Risk
  5. Dependencies
  6. Time Sensitivity
  7. Stability
  8. Regulatory or Policy Compliance
19
Q

Input(s) to 5.4 Assess Requirements Changes

A
  1. Requirements
  2. Designs
  3. Proposed Change
20
Q

Output(s) to 5.4 Assess Requirements Change

A
  1. Requirements Change Assessment
  2. Designs Change Assessment
21
Q

Proposed Change Considerations

A
  1. Benefit
  2. Cost
  3. Impact
  4. Schedule
  5. Urgency
22
Q

Input(s) to 5.5 Approve Requirements

A
  1. Requirements (verified)
  2. Designs
23
Q

Output(s) to 5.5 Approve Requirements

A
  1. Requirements (approved)
  2. Designs (approved)