Brainscape's Knowledge GenomeTM

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


See full index

ECBA > Requirement Life Cycle Mgmt 5 20% > Flashcards

Requirement Life Cycle Mgmt 5 20% Flashcards

1
Q

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

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

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

A

Requirements
Design
Proposed change
Requirements (verified)

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

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

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

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

A

Requirements traced, designs traced
Requirements maintained, designs maintained
Requirements prioritize, designs prioritize
Requirements change assessment, design change assessment
Requirements approved, designs approved

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

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

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

What is the purpose of the Trace requirements process in the requirements life cycle management (RLCM) process?

A

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

What does traceability enables

A

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.

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

What are the elements of the Trace Requirements?

A

Level of formality
Relationship
Traceability repository

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

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

A

Derive
Depends
Satisfy
Validate

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

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

A

Domain knowledge
Information management approach
Legal/regulatory information
Requirements management tools repository

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

What are the techniques used in the Trace requirements process?

A

Business rules Analysis
Functional decomposition
Process modeling
Scope modeling

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

List the stakeholders in the Trace requirements process.

A

Customers, domain subject matter expert, end user, implementation subject matter expert, operational support, project manager, sponsor, suppliers, tester

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

What are the outputs produced in the Trace requirements process?

A

Requirements (traced)

Design (traced)

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

What is the purpose of the Maintain requirements process?

A

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.

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

What are the inputs to the maintain requirements process?

A

Requirements

Design

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

What are the elements of the maintain requirements process?

A

Maintain requirements
Maintain attributes
Reusing requirements

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

What are the techniques used in the maintain requirements process?

A 
Business rules Analysis
Data flow diagrams
Data modelling
Document Analysis
Functional decomposition
Process remodeling
Use cases and scenarios
User stories
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

List the stakeholders in the maintain requirements process.

A 
Domain subject matter expert
Implementation subject matter expert
Operational support
Regulator
Tester
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

True Or false

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

A

True

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

What is the purpose of the prioritize requirements process?

A

To rank requirements in the order of relative importance

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

What are the inputs to the prioritize requirements process?

A

Requirements

Design

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

What are the outputs to the prioritize requirements process?

A

Requirements

Design

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

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

A 
Business constraints
Change strategy
Domain knowledge
Governance approach
Requirements architecture
Requirements management tools/repository
Solution scope
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What are the outputs to the prioritize requirements process?

A

Requirements prioritize

Design prioritize

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

What are the elements of the prioritize requirements process?

A

Basis for prioritization
Challenges of prioritization
Continual prioritization

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

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

A 
Backlog management, business cases
Decision Analysis, estimation
Financial analysis, interviews
Item tracking, prioritization
Risk Analysis and management
Workshops
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Who are the stakeholders in the prioritize requirements process?

A

Customers, end user
Implementation subject matter expert
Project manager, regulator, sponsor

28
Q

What are the outputs to the prioritize requirements process?

A

Requirements (prioritized)

Design (prioritized)

29
Q

What are the factors that influence prioritization?

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

What is the purpose of assess requirements changes process?

A

To evaluate the implications of proposed changes to requirements and designs

31
Q

What are the inputs to the assess requirements changes process?

A

Proposed change
Requirements
Designs

32
Q

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

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

What are the outputs to the assess requirements changes process?

A

Requirements change assessment

Design change assessment

34
Q

What are the elements of the assess requirements changes process?

A

Assessment formality
Impact Analysis
Impact resolution

35
Q

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

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

Who are the stakeholders in the assess requirements process?

A 
Customers
Domain subject matter experts
End user, operational support
Project manager, regulator, sponsor
Tester
37
Q

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

A 
Benefit
Cost
Impact
Schedule
Urgency
38
Q

What are the inputs to the approve requirements process?

A

Requirements (verified)

Designs

39
Q

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

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

What are the elements of the approve requirements process

A

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

41
Q

What techniques are used in the approve requirements process?

A 
Acceptance and evaluation criteria
Decision Analysis
Item tracking
Reviews
Workshops
42
Q

Who are the stakeholders in the approve requirements process?

A 
Customers
Domain subject matter expert
End user, operational support
Project Manager, regulator, sponsor
Tester
43
Q

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 .

A

Ensure business, stakeholders, solutions and design is aligned .

44
Q

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

A

It ends when the solution is implemented .

45
Q

Which of these is NOT a task related to requirements life cycle management ?

Manintain requirements
Trace requirements
Approve requirements
Specify and model requirements

A

Specify and model requirements

46
Q

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.

A

Reduce the cost of the project

47
Q

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

A

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

48
Q

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.

A

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

49
Q

What is the output from the task Trace requirements ?

Tracablity Matrix
Requirements traced and Designs traced .
Backward Traceablity
Coverage Matrix

A

Requirements traced and Designs traced

50
Q

Which of these is a technique used by the task - Trace requirements ?

Use case modeling

Scope Modeling

Requirements workshops

Focus groups

A

Scope Modeling

51
Q

What is the output of the task - Maintain requirements ?

Requirements maintained & Designs maintained .

Coverage matrix

Requirements traceablity

Requirements matrix

A

Requirements maintained & Designs maintained .

52
Q

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

A

The most valueable requirements will not be given higher priority

53
Q

Which one is not a basis for prioritization ?

Visualization

Time sensitivity

Benefit

Risk

A

Visualization

54
Q

Which of these is a technique used for prioritization ?

Observation

Processs Modeling

Backlog management

Metrics and KPI

A

Backlog management

55
Q

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

A

Requirements prioritized and Designs prioritized

56
Q

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

A

Requirements management tools or repository

57
Q

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.

A

To evaluate how the changes will impact the requirements and designs

58
Q

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.

A

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

59
Q

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

A

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

60
Q

Which of these is a technique used in the task assess requirements changes ?

Metrics and KPI

SWOT analysis

Focus groups

Business cases

A

Business cases

61
Q

Which of these can be a guideline or tool for the task assess requirements changes ?

Business Model canvas

Business architecture

Change strategy

Business plan

A

Change strategy

62
Q

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

A

To obtain agreement on approval of requirements and designs.

63
Q

Which of these techniques is used for task approve requirements ?

Acceptance and evaluation criteria

Observation

Domain Modeling

Mind mapping

A

Acceptance and evaluation criteria

64
Q

What is the output from the task approve requirements ?

Approval matrix

Requirements approved and Designs approved .

Project Charter

BRD document

A

Requirements approved and Designs approved .

65
Q

Which of these is an input for the task approve requirements ?

Business goals ( approved)

Requirements ( approved )

Project charter ( approved )

Requirements ( verified)

A

Requirements ( verified)

66
Q

Which of these is an output for the task assess requirements changes ?

Migration plans

Change request docuemnts

Impact analysis document

Requirements change assesment

A

Requirements change assesment

ECBA (7 decks)

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