Requirement Life Cycle Mgmt 5 20%

Question 1

What are the tasks in the requirements life cycle management knowledge area?

Answer 1

Trace requirements

Maintain requirements

Prioritize requirements

Assess requirements changes

Approve requirements

Question 2

What are the inputs to the requirements life cycle management knowledge area?

Answer 2

Requirements

Design

Proposed change

Requirements (verified)

Question 3

What are the outputs in the requirements life cycle management knowledge area?

Answer 3

Requirements traced

designs traced

Requirements maintained

designs maintained

Requirements prioritize

designs prioritize

Requirements change assessment

design change assessment

Requirements approved

designs approved

Question 4

What are the steps of the tasks in the requirements life cycle management knowledge area?

Answer 4

1- trace requirements

2- maintain requirements

3- prioritize requirements

4- assess requirements changes

5- approve requirements

Question 5

What is the purpose of the Trace requirements

process in the requirements life cycle management

(RLCM) process?

Answer 5

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

Question 6

What does traceability enable?

Answer 6

Traceability enables:

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

Question 7

What are the elements of the Trace Requirements?

Answer 7

Level of formality
Relationship
Traceability repository

Question 8

What are the relationships to consider when defining the traceability approach?

Answer 8

Derive

Depends

Satisfy

Validate

Question 9

What are the Guidelines and tools used in the Trace requirements process

Answer 9

Domain knowledge

Information management approach

Legal/regulatory information

Requirements management tools repository

Question 10

What are the techniques used in the Trace requirements process?

Answer 10

Business rules Analysis

Functional decomposition

Process modeling

Scope modeling

Question 11

List the stakeholders in the Trace requirements process.

Answer 11

Customers

domain subject matter expert

end user

implementation subject matter expert

operational support

project manager

sponsor

suppliers

tester

Question 12

What are the outputs produced in the Trace requirements process?

Answer 12

Requirements (traced)

Design (traced)

Question 13

What is the purpose of the Maintain requirements process?

Answer 13

To retain requirements accuracy and consistency through out and

beyond the change during the entire requirements life cycle and to

support reuse of requirements in other solutions.

Question 14

What are the inputs to the maintain requirements process?

Answer 14

Requirements

Design

Question 15

What are the elements of the maintain requirements process?

Answer 15

Maintain requirements

Maintain attributes

Reusing requirements

Question 16

What are the techniques used in the maintain requirements process?

Answer 16

Business rules Analysis

Data flow diagrams

Data modeling

Document Analysis

Functional decomposition

Process remodeling

Use cases and scenarios

User stories

Question 17

List the stakeholders in the maintain requirements process.

Answer 17

Domain subject matter expert

Implementation subject matter expert

Operational support

Regulator

Tester

Question 18

True Or false

A business requirement attribute may change even though the requirement does not

Answer 18

True

Question 19

What is the purpose of the prioritize requirements process?

Answer 19

To rank requirements in the order of relative importance

Question 20

What are the inputs to the prioritize requirements process?

Answer 20

Requirements

Design

Question 21

What are the outputs to the prioritize requirements process?

Answer 21

Requirements

Design

Question 22

What are the Guidelines and tools used in the prioritize requirements process?

Answer 22

Business constraints

Change strategy

Domain knowledge

Governance approach

Requirements architecture

Requirements management tools/repository

Solution scope

Question 23

What are the outputs to the prioritize requirements process?

Answer 23

Requirements prioritize

Design prioritize

Question 24

What are the elements of the prioritize requirements process?

Answer 24

Basis for prioritization

Challenges of prioritization

Continual prioritization

Question 25

What are the technique to be used in the prioritize requirements process?

Answer 25

Backlog management, business cases Decision Analysis, estimation Financial analysis, interviews Item tracking, prioritization Risk Analysis and management Workshops

Question 26

Who are the stakeholders in the prioritize requirements process?

Answer 26

Customers end user Implementation subject matter expert Project manager regulator sponsor

Question 27

What are the outputs to the prioritize requirements process?

Answer 27

Requirements (prioritized) Design (prioritized)

Question 28

What are the factors that influence prioritization?

Answer 28

Benefits Penalty Cost Risk Dependencies Time sensitivity Stability Regulatory or policy compliance

Question 29

What is the purpose of assess requirements changes process?

Answer 29

To evaluate the implications of proposed changes to requirements and designs

Question 30

What are the inputs to the assess requirements changes process?

Answer 30

Proposed change Requirements Designs

Question 31

List the Guidelines and tools to the assess requirements changes process.

Answer 31

Change strategy Domain knowledge Governance approach Legal regulatory information Requirements architecture Solution scope

Question 32

What are the outputs to the assess requirements changes process?

Answer 32

Requirements change assessment Design change assessment

Question 33

What are the elements of the assess requirements changes process?

Answer 33

Assessment formality Impact Analysis Impact resolution

Question 34

What are the techniques used in the assess requirements changes techniques?

Answer 34

Business case Business rules Analysis Decision Analysis document Analysis Estimation financial analysis Interface Analysis interviews Item tracking workshops Risk Analysis management

Question 35

Who are the stakeholders in the assess requirements process?

Answer 35

Customers Domain subject matter experts End user operational support Project manager regulator sponsor Tester

Question 36

What does the BA consider while assessing the impact of the proposed change?

Answer 36

Benefit Cost Impact Schedule Urgency

Question 37

What are the inputs to the approve requirements process?

Answer 37

Requirements (verified) Designs

Question 38

What are the Guidelines and tools used in the approve requirements process?

Answer 38

Change strategy Governance approach Legal/regulatory information Requirements management tools/ repository Solution scope

Question 39

What are the elements of the approve requirements process

Answer 39

Understand stakeholders roles Conflict and issue management Gain consensus Track and communicate approval

Question 40

What techniques are used in the approve requirements process?

Answer 40

Acceptance and evaluation criteria Decision Analysis Item tracking Reviews Workshops

Question 41

Who are the stakeholders in the approve requirements process?

Answer 41

Customers Domain subject matter expert End user operational support Project Manager regulator sponsor Tester

Question 42

Which of these is the core function of the knowledge area  of requirements life cycle management ? A. The requirements are analyzed properly. B. The business need and requirements is elicited correctly C. The Project vision is implemented. D. Ensure business, stakeholders, solutions and design is aligned .

Answer 42

D. Ensure business, stakeholders, solutions and design is aligned .

Question 43

Which if these statements is NOT TRUE regarding requirements life cycle? A. They provide value when well managed . B. It ends when the solution is implemented . C. The life cylce is different from the methodology or process that is implemented . D. It is the same as the Software development life cycle 

Answer 43

It ends when the solution is implemented .

Question 44

Which of these is NOT a task related to requirements life cycle management ? Manintain requirements Trace requirements Approve requirements Specify and model requirements

Answer 44

Specify and model requirements

Question 45

Which of these is NOT a function of the task trace requirements ? Get good understanding on the scope of changes  Understand impact analysis faster. Reduce the cost of the project  Understand which requirements are impacted and which ones are not.

Answer 45

Reduce the cost of the project 

Question 46

Which of these is the correct chain of process traceablity ? Business process > Activity > Sub process > Task> Value chain Value chain > Business process > Task > sub process Value Chain > Business process > Sub process > Activity > Task . Task > sub process >Activity > Task > Value chain 

Answer 46

Value Chain > Business process > Sub process > Activity > Task .

Question 47

Which of these is the core purpose of the task maintain the requirements ? Ensure the scope is manintaned . Reduce the project risk .. . Maintain requirements accuracy and consistensy throughout the entire requirements life cycle. Ensure the project budget is strictly maintained.

Answer 47

Maintain requirements accuracy and consistensy throughout the entire requirements life cycle.

Question 48

What is the output from the task Trace requirements ? Tracablity Matrix Requirements traced and Designs traced . Backward Traceablity Coverage Matrix

Answer 48

Requirements traced and Designs traced

Question 49

Which of these is a technique used by the task - Trace requirements ? Use case modeling Scope Modeling  Requirements workshops Focus groups

Answer 49

Scope Modeling 

Question 50

What is the output of the task - Maintain requirements ? Requirements maintained and Designs maintained . Coverage matrix Requirements traceablity  Requirements matrix

Answer 50

Requirements maintained and Designs maintained .

Question 51

What could go wrong if requirements prioritization is NOT done ? The Modeling standards will get hampered. The most valueable requirements will not be  given higher priority The KPI will not be meet for the project The Tracing cannot be done effectively

Answer 51

The most valueable requirements will not be  given higher priority

Question 52

Which one is not a basis for prioritization ? Visualization Time sensitivity Benefit Risk

Answer 52

Visualization

Question 53

Which of these is a technique used for prioritization ? Observation Processs Modeling Backlog management  Metrics and KPI

Answer 53

Backlog management 

Question 54

What is or /are the outputs from the task prioritize requirements ? Use cases and user stories GUI designs and Wireframes. Business needs and stakeholder needs Requirements prioritized and Designs prioritized

Answer 54

Requirements prioritized and Designs prioritized

Question 55

Which of these can be a guideline or tool for the task prioritize requirements ? LAN and Wikis Backward traceablity Coverage matrixes Requirements management tools or repository

Answer 55

Requirements management tools or repository

Question 56

What is the core purpose of the task assess requirements changes ? To define a process of how changes should be managed  To make sure that unwanted changes are parked for latter releases  To evaluate how the changes will impact the requirements and designs To make sure that no changes are taken after the signoff is obtained.

Answer 56

To evaluate how the changes will impact the requirements and designs

Question 57

What is the important aspect that the BA looks when evaluating change requests ? To take a decision if the same is to be taken up or not To take it up with the sponsor for approval To assess the potential effect of the change to solution value, To take it up with the project manager for approval.

Answer 57

To assess the potential effect of the change to solution value,

Question 58

Which of these is NOT a factor when the BA evaluates changes to the solution ? To evaluate if cost can be reduced due to this changes . To evaluate of the changes affect the overall value to the stakeholders. To evaluate if there is any change in risks or opportunities to the initiative. To evaluate if it aligns with the overall strategy

Answer 58

To evaluate if cost can be reduced due to this changes .

Question 59

Which of these is a technique used in the task assess requirements changes ? Metrics and KPI SWOT analysis  Focus groups Business cases

Answer 59

Business cases

Question 60

Which of these can be a guideline or tool for the task assess requirements changes ? Business Model canvas Business architecture Change strategy Business plan

Answer 60

Change strategy

Question 61

Which of these is the core purpose of the task approve requirements ? To get the correct requirements  To reduce the project risk as much as possible . To obtain agreement on approval of requirements and designs. To get maximum value for money 

Answer 61

To obtain agreement on approval of requirements and designs.

Question 62

Which of these techniques is used for task approve requirements ? Acceptance and evaluation criteria  Observation Domain Modeling Mind mapping

Answer 62

Acceptance and evaluation criteria 

Question 63

What is the output from the task approve requirements ? Approval matrix Requirements approved and Designs approved . Project Charter BRD document

Answer 63

Requirements approved and Designs approved .

Question 64

Which of these is an input for the task approve requirements ? Business goals ( approved) Requirements ( approved ) Project charter ( approved ) Requirements ( verified)

Answer 64

Requirements ( verified)

Question 65

Which of these is an output for the task assess requirements changes ? Migration plans  Change request docuemnts Impact analysis document Requirements change assesment 

Answer 65

Requirements change assesment