Requirements Life Cycle Management Flashcards
What are the steps of requirements life cycle
- Representation of a business need as a requirement
- Development of a solution
- Retirement of the solution and of the requirements that represent it.
What are the tasks related to RLCMgmt
Trace requirements -> analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation
Maintain requirements -> ensure that requirements and designs are accurate and current throughout the life cycle and facilitates reuse where appropriate
Prioritize requirements -> assesses the value, urgency, and risks associated with particular requirements and designs to ensure that analysis and/or delivery work is done on the most important ones at any given time
Assess requirements changes -> evaluates new and changing stakeholder requirements to determine if they need to be acted on within the scope of a change
Approve requirements -> works with stakeholders involved in the governance process to reach approval and agreement on requirements and designs
What are the relationships between requirement to consider when defining the traceability approach
- Derive (e.g. solution requirement derived from a business or stakeholder requirement)
- Depends (necessity, effort)
- Satisfy (e.g. relationship between a functional requirement and a solution component that implements it)
- Validate (e.g. relationship between a requirement and a test case)
What are the techniques to trace requirements
- Business rules analysis (trace br to requirements they support)
- Functional decomposition (break down solution scope into smaller components for allocation, trace high-level concepts to low-level concepts)
- Process modelling (visually show the future state process and trace requirements to the future state proce)
- Scope modelling (visually depict scope and trace requirements to the area of scope)
What is the purpose of trace requirements
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 is the purpose of maintain requirements
to retain accuracy and consistency throughout and beyond the change throughout the entire requirements life cycle, and to support reuse of requirements in other solutions.
What are the techniques to maintain requirements
- Business rules analysis
- Data flows diagrams
- Data modelling
- Document analysis
- Functional decomposition
- Process modelling
- Use cases and scenarios
- User stories
What is the purpose of prioritize requirements
To rank requirements in the order of relative importance
What are the typical factors that influence prioritization
Benefit
Penalty
Cost
Risk
Dependency
Time sensitivity
Stability (likelihood that the requirement will change)
Regulatory or policy compliance
What are the tools to prioritize requiremetns
- Business constraints
- Change strategy
- Domain knowledge
- Governance approach
- Requirements architecture
- Requirements management tools / repository
- Solution scope
What are the techniques useful to requirements prioritization
Backlog management -> to compare requirements to be prioritized
Business cases -> to assess requirements against identified business goals and objectives to determine importance
Decision analysis -> to identify high-value requirements
Estimation -> to produce estimates for the basis of prioritization
Financial analysis -> to assess the financial value of a set of requirements and how the timing of delivery will affect that value
Interviews -> to gain an understanding of a single or small group of stakeholders basis of prioritization or priorities
Item tracking -> to track issues raised by stakeholders during prioritization
Prioritization -> to facilitate the process of prioritization
Risk analysis and management -> to understand the risks for the basis of prioritization
Workshops -> to gain an understanding of stakeholders’ basis of prioritization or priorities in a facilitated group setting
What is the purpose of assess requirements changes
To evaluate the implication of proposed changes to requirements and design
When assessing changes what the BA should consider
If each change
- Aligns with the overall strategy
- Affects value delivered to the business of stakeholder groups
- Impacts the time to deliver or the resources required to deliver the value
- alters any risks, opportunities or constraints associated with the overall initiative
What are the tools to use when assessing change
- Change strategy
- Domain knowledge
- Governance approach
- Legal/Regulatory information
- Requirements architecture
- Solution scope
What are the techniques to use when assessing change
- Business cases -> to justify a proposed change
- Business rules analysis -> to assess changes to business policies and business rules and develop revised guidance
- Decision analysis -> to facilitate the change assessment process
- Document analysis -> to analyse any existing documents that facilitate an understanding of the impact of the change
- Estimation -> to determine the size of the change
- Financial analysis -> to estimate the financial consequences of a proposed change
- Interface analysis -> to help business analysts identify interfaces that can be affected by the change
- Interviews -> to gain an understanding of the impact on the organization or its assets from a single or small group of stakeholders
- Item tracking -> to track any issues or conflicts discovered during impact analysis
- Risk analysis and management -> to determine the level of risk associated with the change
- Workshops -> to gain an understanding of the impact or to resolve changes in a group setting
