Requirements Analysis and Design Definition Flashcards
RADD Tasks
Specify and model requirements
vErify requirements
vAlidate requirements
define Requirements architecture
define design Options
Analyze potential value and Recommend solution
Purpose of Specify and Model Requirements task
to transform elicitation results into requirements and designs by refining them through analysis and synthesis.
Inputs to Specify and Model Requirements task
Elicitation Results (any state)
Elements of Specify and Model Requirements task
Model Requirements
Analyze Requirements
Represent Requirements and Attributes
Implement the Appropriate Levels of Abstraction
Guidelines and Tools for Specify and Model Requirements task
Modelling Notations/Standards Modelling Tools Requirements Architecture Requirements Life Cycle Management Tools Solution Scope
Stakeholders for Specify and Model Requirements task
Any stakeholder
Outputs of Specify and Model Requirements task
Requirements (specified and modelled)
Purpose of Verify Requirements task
to ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve.
Tasks using Requirements (specified and modelled)
Verify Requirements
Validate Requirements
Inputs to Verify Requirements task
Requirements (specified and modelled)
Elements of Verify Requirements task
Characteristics of Requirements and Designs Quality
Verification Activities
Checklists
Guidelines and Tools for Verify Requirements task
Requirements Life Cycle Management Tools
Stakeholders of Verify Requirements task
All stakeholders
Outputs of Verify Requirements task
Requirements (verified)
Purpose of Validate Requirements task
to ensure that all requirements and designs align to the business requirements and support the delivery of needed value.
Inputs to Validate Requirements task
Requirements (specified and modelled)
Tasks using Requirements (verified) output
Approve Requirements
Elements of Validate Requirements task
Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope
Guidelines and Tools for Validate Requirements task
Business Objectives
Future State Description
Potential Value
Solution Scope
Stakeholders of Validate Requirements task
All stakeholders
Outputs of Validate Requirements task
Requirements (validated)
Tasks using Requirements (validated) output
Define Design Options
Measure Solution Performance
Purpose of Define Requirements Architecture task
is to ensure that the requirements collectively support one another to fully achieve the objectives
Inputs to Define Requirements Architecture task
Information Management Approach
Requirements (any state)
Solution Scope
Elements of Define Requirements Architecture task
Requirements Viewpoints and Views
Template Architectures
Completeness
Relate and Verify Requirements Relationships
Business Analysis Information Architecture
Guidelines and Tools for Define Requirements Architecture task
Architecture Management Software
Legal/Regulatory Information
Methodologies and Frameworks
Stakeholders of Define Requirements Architecture task
Domain Subject Matter Expert, Implementation Subject Matter Expert, Project Manager, Sponsor, Tester
Any Stakeholder
Outputs of Define Requirements Architecture task
Requirements Architecture
Tasks using Requirements Architecture output
Prioritize Requirements
Assess requirements Changes
Specify and Model Requirements
Define Design Options
Purpose of Define Design Options task
to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state.
Inputs to Define Design Options task
Change Strategy
Requirements (validated, prioritized)
Requirements Architecture
Elements of Define Design Options task
Define Solution Approaches
Identify Improvement Opportunities
Requirements Allocation
Describe Design Options
Guidelines and Tools for Define Design Options task
Existing Solutions
Future State Description
Requirements (traced)
Solution Scope
Stakeholders of Define Design Options task
Domain SME Implementation SME Operational Support Project Manager Supplier
Outputs of Define Design Options task
Design Options
Tasks using Design Options output
Define Change Strategy
Analyze Potential Value and Recommend Solution
Purpose of Analyze Potential Value and Recommend Solution task
to estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements.
Inputs to Analyze Potential Value and Recommend Solution task
Potential Value
Design Options
Elements of Analyze Potential Value and Recommend Solution task
Expected Benefits
Expected Costs
Determine Value
Assess Design Options and Recommend Solution
Guidelines and Tools for Analyze Potential Value and Recommend Solution task
Business Objectives
Future State Description
Risk Analysis Results
Solution Scope
Stakeholders for Analyze Potential Value and Recommend Solution task
Customer Domain SME End User Implementation SME Project Manager Regulator Sponsor
Outputs of Analyze Potential Value and Recommend Solution task
Solution Recommendation
Tasks using Solution Recommendation output
Define Change Strategy
Model Categories (RAP CD)
Rationale Activity Flow People & Roles Capability Data & Information
Quality Characteristics of Requirements (FACt CUP CUT)
Feasible Atomic Complete Consistent Unambiguous Prioritized Concise Understandable Testable
Verify Requirements Techniques (AIM-R)
Acceptance and Evaluation Criteria
Item Tracking
Metrics and KPIs
Reviews
“Representations”
A tangible business deliverable resulting from clarifying either the need (requirements) or the solution (designs).
Two types of requirements models
Matrices (mostly text)
Diagrams (graphical with some text)
Verification activities to be done
Completeness checks Comparison checks Correctness checks Compliance checks Terminology checks Examples to clarify
Quality criteria used to examine requirements relationships (DUNCC)
Defined Unambiguous Necessary Correct Consistent
Examples of ways to improve current state
Increased efficiencies
Increased access to information
Additional capabilities
Design Option elements (BABOSO)
business policies and business rules affected stakeholders business processes operational business decisions software applications organizational structures
Types of expected costs
schedule and effort support purchase and/or implementation resources opportunity
Considerations when assessing design options
A RODeO
Available resources Relationships with proposed vendor Other constraints Dependencies between requirements Other factors