Brainscape's Knowledge GenomeTM

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


See full index

BABOK Version 3 > Chapter 5 > Flashcards

Chapter 5 Flashcards

Concept Mastery

1
Q

The purpose of requirements life cycle management

A

ensure that business, stakeholder, and solution requirements and designs are aligned to one another
and that the solution implements them.

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

3 major components of the requirements life cycle management

A
  • 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The Requirements Life Cycle Management knowledge area includes the following tasks:

A

Trace Requirements, Maintain Requirements, Prioritize Requirements, Assess Requirements Changes, Approve Requirements

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

During Requirements Life Cycle

Management, business analysts what is change?

A

manage how proposed changes to requirements and designs are evaluated during an initiative.

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

During Requirements Life Cycle

Management, business analysts what is need?

A

trace, prioritize and maintain requirements to ensure that the need is met.

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

During Requirements Life Cycle

Management, business analysts what is Solution?

A

trace requirements and designs to solution components to ensure that the solution satisfies the need.

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

During Requirements Life Cycle Management, business analysts what is Stakeholder?

A

work closely with key stakeholders to maintain understanding, agreement, and approval of requirements and designs.

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

During Requirements Life Cycle Management, business analysts what is value?

A

maintain requirements for reuse to extend

value beyond the current initiative.

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

During Requirements Life Cycle Management, business analysts what is context?

A

analyze the context to support tracing and prioritization activities.

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

What is the purpose of trace requirements?

A

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
11
Q

Traceability is used to help ensure that

A

the solution conforms to requirements and to assist in scope, change, risk, time, cost, and communication management.

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

Traceability enables:

A

• 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.

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

relationships that the business analyst considers when

defining the traceability approach:

A

Derive, Depend, satisfy, validate

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

What is derive?

A

relationship between two requirements, used when a requirement is derived from another requirement.

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

What are the types of depend traceability?

A

necessity, effort

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

What is satisfy traceability?

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
17
Q

What is validate traceability?

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
18
Q

What are the guidelilnes/tools for traceability?

A

knowledge domain, Information Management Approach, Legal/Regulatory Information, Requirements Management Tools/Repository

19
Q

What are some techniques for traceability?

A

Business Rules Analysis, Functional Decomposition, Process Modelling, Scope Modelling

20
Q

What are the outputs of traceability?

A

Requirements and Design

21
Q

The purpose of Maintain Requirements

A

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.

22
Q

In order to maximize the benefits of maintaining and reusing requirements, the requirements should be:

A

consistently represented,
• reviewed and approved for maintenance using a standardized process that
defines proper access rights and ensures quality, and
• easily accessible and understandable.

23
Q

What are the inputs for maintaining requirements?

A

Requirements and Design

24
Q

What are the guidelines and tools of maintaining requirements?

A

Information Management Approach

25
Q

What are the techniques of maintaining requirements?

A

Business Rules Analysis, Data Flow Diagrams, Data Modelling, Document Analysis, Functional Decomposition, Process Modelling, Use Cases and Scenarios, User Stories

26
Q

What are the outputs of maintaining requirements?

A

Requirements and design

27
Q

What are the inputs of prioritizing requirements?

A

Requirements and Design

28
Q

Typical factors that influence prioritization include:

A

Benefit, Penalty, Cost, Risk, Dependency, time sensitivity, stability, regulatory or policy compliance

29
Q

What are the guidelines and tools of prioritizing requirements?

A

Business Constraints, change strategy, domain knowledge, Governance Approach, requirements architecture, Requirements Management Tools/Repository, solution scope,

30
Q

What are some techniques of prioritizing requirements?

A

Backlog Management, business cases, decision analysis, estimation, Financial Analysis, Interviews, Item Tracking, Prioritization, Risk Analysis and Management, Workshops

31
Q

What are the outputs of prioritizing requirements?

A

Design and Requirements

32
Q

The purpose of Assess Requirements Changes

A

evaluate the implications of proposed changes to requirements and designs.

33
Q

When assessing changes, business analysts consider if each proposed change:

A

• aligns with the overall strategy,
• affects value delivered to the business or stakeholder groups,
• impacts the time to deliver or the resources required to deliver the value,
and
• alters any risks, opportunities, or constraints associated with the overall
initiative.

34
Q

what are the inputs of Assess Requirements Changes?

A

Proposed Change, Requirements, Designs

35
Q

What are the guidelines and tools of assessing requirements changes?

A

Change Strategy, Domain Knowledge, Governance Approach, Legal/Regulatory Information, Requirements Architecture, Solution Scope

36
Q

What are the techniques of assessing requirements changes?

A

business cases, business rules analysis, decision analysis, document analysis, estimation, financial analysis, interface analysis, interviews, item tracking, risk analysis, and mangement, workshops

37
Q

What are the outputs of asssessing requirements changes?

A

Requirements Change Assessment, design change assessment

38
Q

The purpose of Approve Requirements is?

A

to obtain agreement on and approval of

requirements and designs for business analysis work to continue and/or solution construction to proceed.

39
Q

What are the inputs of approve requirements?

A

Requirements and Design

40
Q

The approval process is defined by

A

Plan Business Analysis Governance

41
Q

What are the guidelines and tools of approve requirements?

A

Change Strategy, governance approach, Legal/Regulatory Information, Requirement Management Tools/Repository, solution scope

42
Q

What are the techniques of approval requirements?

A

Acceptance and Evaluation Criteria, Decision Analysis, item tracking, reviews, workshops

43
Q

What are the outputs of approval requirements?

A

Requirements and Design

BABOK Version 3 (8 decks)

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