Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

ECBA - Babok v3 review > 5 Requirements Lifecycle Management (20%) > Flashcards

5 Requirements Lifecycle Management (20%) Flashcards

1
Q

What is Requirements Life Cycle Management ?

A

The purpose requirement of life cycle management is to ensure that business, stakeholders, and solution requirements and designs are aligned to one another and that the solution implement them.

The requirements life cycle begins with the representation of a business need a a requirement, continues through the development of a solution, ends when a solution and the requirements that represent it are retired.

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

What are the TASKS of Requirements Life Cycle Management (5)?

A
  • 5.1 Trace Requirements
  • 5.2 Maintain Requirements
  • 5.3 Prioritize Requirements
  • 5.4 Assess Requirements Changes
  • 5.5 Approve Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
  1. 0 Requirements Life Cycle Management
  2. 1 Trace Requirements

What is the “Trace Requirements” purpose ?

A

The purpose of Trace Requirements is to 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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  1. 0 Requirements Life Cycle Management
  2. 2 Maintain Requirements

What is the “Maintain Requirements” purpose ?

A

The purpose of Maintain Requirements is to 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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
  1. 0 Requirements Life Cycle Management
  2. 3 Prioritize Requirements

What is the “Prioritize Requirements” purpose ?

A

The purpose of Prioritize Requirements is to rank requirements in the order of
relative importance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  1. 0 Requirements Life Cycle Management
  2. 4 Assess Requirements Changes

What is the “Assess Requirements Changes” purpose ?

A

The purpose of Assess Requirements Changes is to evaluate the implications of
proposed changes to requirements and designs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q
  1. 0 Requirements Life Cycle Management
  2. 5 Approve Requirements

What is the “Approve Requirements” purpose ?

A

The purpose of Approve Requirements is to obtain agreement on and approval of requirements and designs for business analysis work to continue and/or solution construction to proceed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q
  1. 0 Requirements Life Cycle Management
  2. 1 Trace Requirements

What is the “Trace Requirements” Outputs ?

A
  1. 1 Requirements (traced)

5. 1 Designs (traced)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  1. 0 Requirements Life Cycle Management
  2. 2 Maintain Requirements

What is the “Maintain Requirements” Outputs ?

A
  1. 2 Requirements (maintained)

5. 2 Designs (maintained)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  1. 0 Requirements Life Cycle Management
  2. 3 Prioritize Requirements

What is the “Prioritize Requirements” Outputs ?

A
  1. 3 Requirements (prioritized)

5. 3 Designs (prioritized)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
  1. 0 Requirements Life Cycle Management
  2. 4 Assess Requirements Changes

What is the “Assess Requirements Changes” Outputs ?

A
  1. 4 Requirements Change Assessment

5. 4 Designs Change Assessment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q
  1. 0 Requirements Life Cycle Management
  2. 5 Approve Requirements

What is the “Approve Requirements” Outputs ?

A
  1. 5 Requirements (approved)

5. 5 Designs (approved)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  1. 0 Requirements Life Cycle Management
  2. 1 Trace Requirements

What are the “Trace Requirementsn” Elements ?

A

1- Level of Formality
2- Relationships (Derive / Depends / Satisfy / Validate)
3- Traceability Repository

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q
  1. 0 Requirements Life Cycle Management
  2. 2 Maintain Requirements

What are the “Maintain Requirements” Elements ?

A

1- Maintain Requirements
2- Maintain Attributes
3- Reusing Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
  1. 0 Requirements Life Cycle Management
  2. 3 Prioritize Requirements

What are the “Prioritize Requirements” Elements ?

A

1- Basis for Prioritization
2- Challenges of Prioritization
3- Continual Prioritization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q
  1. 0 Requirements Life Cycle Management
  2. 4 Assess Requirements Changes

What are the “Assess Requirements Changes” Elements ?

A

1- Assessment Formality (based on the information available, the apparent importance of the change, and the governance process)
2- Impact Analysis (Benefit, Cost, Impact, Shcdule, Urgency)
3- Impact Resolution

17
Q
  1. 0 Requirements Life Cycle Management
  2. 5 Approve Requirements

What are the “Approve Requirements” Elements ?

A

1- Understand Stakeholder Roles
2- Conflict and Issue Management
3- Gain Consensus
4- Track and Communicate Approval

18
Q

5.0 Requirements Life Cycle Management

This output is define as:

Have clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.

A

Requirements (Traced)

19
Q

5.0 Requirements Life Cycle Management

This output is define as:

Clearly defined relationships to other requirements, solution components, or releases, phases, or iterations, within a solution scope, such that coverage and the effects of change are clearly identifiable.

A

Design (Traced)

20
Q

5.0 Requirements Life Cycle Management

This output is define as:

Defined once and available for long-term usage by the organization. They may become organizational process assets or be used in future initiatives. In some cases, a requirement that was not approved or implemented may be maintained for a possible future initiative.

A

Requirements (Maintained)

21
Q

5.0 Requirements Life Cycle Management

This output is define as:

May be reusable once defined. For example, as a selfcontained component that can be made available for possible future use.

A

Design (Maintained)

22
Q

5.0 Requirements Life Cycle Management

This output is define as:

Prioritized or ranked requirements are available for additional work, ensuring that the highest valued requirements are addressed first.

A

Requirements (Prioritized)

23
Q

5.0 Requirements Life Cycle Management

This output is define as:

Prioritized or ranked designs are available for additional work, ensuring that the highest valued designs are addressed first.

A

Design (Prioritized)

24
Q

5.0 Requirements Life Cycle Management

This output is define as:

The recommendation to approve, modify, or deny a proposed change to one or more requirements or design components.

A

Requirements and Design change Assessment

25
Q

5.0 Requirements Life Cycle Management

This output is define as:

Requirements or Designs which are agreed to by stakeholders and are ready for use in subsequent business analysis or solution development efforts.

A

Requirements and Design (Approved)

ECBA - Babok v3 review (14 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions