Requirement Life Cycle Mgmt 5 20% Flashcards
What are the tasks in the requirements life cycle management knowledge area?
Trace requirements
Maintain requirements
Prioritize requirements
Assess requirements changes
Approve requirements
What are the inputs to the requirements life cycle management knowledge area?
Requirements
Design
Proposed change
Requirements (verified)
What are the outputs in the requirements life cycle management knowledge area?
Requirements traced
designs traced
Requirements maintained
designs maintained
Requirements prioritize
designs prioritize
Requirements change assessment
design change assessment
Requirements approved
designs approved
What are the steps of the tasks in the requirements life cycle management knowledge area?
1- trace requirements
2- maintain requirements
3- prioritize requirements
4- assess requirements changes
5- approve requirements
What is the purpose of the Trace requirements
process in the requirements life cycle management
(RLCM) process?
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
What does traceability enable?
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.
What are the elements of the Trace Requirements?
Level of formality
Relationship
Traceability repository
What are the relationships to consider when defining the traceability approach?
Derive
Depends
Satisfy
Validate
What are the Guidelines and tools used in the Trace requirements process
Domain knowledge
Information management approach
Legal/regulatory information
Requirements management tools repository
What are the techniques used in the Trace requirements process?
Business rules Analysis
Functional decomposition
Process modeling
Scope modeling
List the stakeholders in the Trace requirements process.
Customers
domain subject matter expert
end user
implementation subject matter expert
operational support
project manager
sponsor
suppliers
tester
What are the outputs produced in the Trace requirements process?
Requirements (traced)
Design (traced)
What is the purpose of the Maintain requirements process?
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.
What are the inputs to the maintain requirements process?
Requirements
Design
What are the elements of the maintain requirements process?
Maintain requirements
Maintain attributes
Reusing requirements
What are the techniques used in the maintain requirements process?
Business rules Analysis
Data flow diagrams
Data modeling
Document Analysis
Functional decomposition
Process remodeling
Use cases and scenarios
User stories
List the stakeholders in the maintain requirements process.
Domain subject matter expert
Implementation subject matter expert
Operational support
Regulator
Tester
True Or false
A business requirement attribute may change even though the requirement does not
True
What is the purpose of the prioritize requirements process?
To rank requirements in the order of relative importance
What are the inputs to the prioritize requirements process?
Requirements
Design
What are the outputs to the prioritize requirements process?
Requirements
Design
What are the Guidelines and tools used in the prioritize requirements process?
Business constraints
Change strategy
Domain knowledge
Governance approach
Requirements architecture
Requirements management tools/repository
Solution scope
What are the outputs to the prioritize requirements process?
Requirements prioritize
Design prioritize
What are the elements of the prioritize requirements process?
Basis for prioritization
Challenges of prioritization
Continual prioritization
What are the technique to be used in the prioritize requirements process?
Backlog management, business cases
Decision Analysis, estimation
Financial analysis, interviews
Item tracking, prioritization
Risk Analysis and management
Workshops
Who are the stakeholders in the prioritize requirements process?
Customers
end user
Implementation subject matter expert
Project manager
regulator
sponsor
What are the outputs to the prioritize requirements process?
Requirements (prioritized)
Design (prioritized)
What are the factors that influence prioritization?
Benefits
Penalty
Cost
Risk
Dependencies
Time sensitivity
Stability
Regulatory or policy compliance
What is the purpose of assess requirements changes process?
To evaluate the implications of proposed
changes to requirements and designs
What are the inputs to the assess requirements changes process?
Proposed change
Requirements
Designs
List the Guidelines and tools to the assess requirements changes process.
Change strategy
Domain knowledge
Governance approach
Legal regulatory information
Requirements architecture
Solution scope
What are the outputs to the assess requirements changes process?
Requirements change assessment
Design change assessment
What are the elements of the assess requirements changes process?
Assessment formality
Impact Analysis
Impact resolution
What are the techniques used in the assess requirements changes techniques?
Business case
Business rules Analysis
Decision Analysis
document Analysis
Estimation
financial analysis
Interface Analysis
interviews
Item tracking
workshops
Risk Analysis management
Who are the stakeholders in the assess requirements process?
Customers
Domain subject matter experts
End user
operational support
Project manager
regulator
sponsor
Tester
What does the BA consider while assessing the impact of the proposed change?
Benefit
Cost
Impact
Schedule
Urgency
What are the inputs to the approve requirements process?
Requirements (verified)
Designs
What are the Guidelines and tools used in the approve requirements process?
Change strategy
Governance approach
Legal/regulatory information
Requirements management tools/ repository
Solution scope
What are the elements of the approve requirements process
Understand stakeholders roles
Conflict and issue management
Gain consensus
Track and communicate approval
What techniques are used in the approve requirements process?
Acceptance and evaluation criteria
Decision Analysis
Item tracking
Reviews
Workshops
Who are the stakeholders in the approve requirements process?
Customers
Domain subject matter expert
End user
operational support
Project Manager
regulator
sponsor
Tester
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 .
D. Ensure business, stakeholders, solutions and design is aligned .
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
It ends when the solution is implemented .
Which of these is NOT a task related to requirements life cycle management ?
Manintain requirements
Trace requirements
Approve requirements
Specify and model requirements
Specify and model requirements
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.
Reduce the cost of the project
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
Value Chain > Business process > Sub process > Activity > Task .
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.
Maintain requirements accuracy and consistensy throughout the entire requirements life cycle.
What is the output from the task Trace requirements ?
Tracablity Matrix
Requirements traced and Designs traced .
Backward Traceablity
Coverage Matrix
Requirements traced and Designs traced
Which of these is a technique used by the task - Trace requirements ?
Use case modeling
Scope Modeling
Requirements workshops
Focus groups
Scope Modeling
What is the output of the task - Maintain requirements ?
Requirements maintained and Designs maintained .
Coverage matrix
Requirements traceablity
Requirements matrix
Requirements maintained and Designs maintained .
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
The most valueable requirements will not be given higher priority
Which one is not a basis for prioritization ?
Visualization
Time sensitivity
Benefit
Risk
Visualization
Which of these is a technique used for prioritization ?
Observation
Processs Modeling
Backlog management
Metrics and KPI
Backlog management
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
Requirements prioritized and Designs prioritized
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
Requirements management tools or repository
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.
To evaluate how the changes will impact the requirements and designs
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.
To assess the potential effect of the change to solution value,
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
To evaluate if cost can be reduced due to this changes .
Which of these is a technique used in the task assess requirements changes ?
Metrics and KPI
SWOT analysis
Focus groups
Business cases
Business cases
Which of these can be a guideline or tool for the task assess requirements changes ?
Business Model canvas
Business architecture
Change strategy
Business plan
Change strategy
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
To obtain agreement on approval of requirements and designs.
Which of these techniques is used for task approve requirements ?
Acceptance and evaluation criteria
Observation
Domain Modeling
Mind mapping
Acceptance and evaluation criteria
What is the output from the task approve requirements ?
Approval matrix
Requirements approved and Designs approved .
Project Charter
BRD document
Requirements approved and Designs approved .
Which of these is an input for the task approve requirements ?
Business goals ( approved)
Requirements ( approved )
Project charter ( approved )
Requirements ( verified)
Requirements ( verified)
Which of these is an output for the task assess requirements changes ?
Migration plans
Change request docuemnts
Impact analysis document
Requirements change assesment
Requirements change assesment
