CBAP - Requirements Analysis and Design Definition

Question	Answer
Requirements Analysis and Design Definition TASK	1. Specify and Model Requirements 2. Verify Requirements 3. Validate Requirements 4. Define Requirements Architecture 5. Define Design Options 6. Analyze Potential Value and Recommend Solutions
INPUTS for Specify and Model Requirements	 Elicitation Results (any state)
ELEMENTS for Specify and Model Requirements	 Model Requirements Matrices Diagrams People and Roles Rationale Activity flow Capability Data and Information  Analyze Requirements  Represent Requirements and Attributes  Implement the Appropriate Levels of Abstraction
GUIDELINES AND TOOL for Specify and Model Requirements	 Modelling Notations/Standards  Modelling Tools  Requirements Architecture  Requirements Life Cycle Management Tools  Solution Scope
TECHNIQUES for Specify and Model Requirements	 Acceptance and Evaluation Criteria  Business Capability Analysis  Business Model Canvas  Business Rules Analysis  Concept Modelling  Data Dictionary  Data Flow Diagrams  Data Modelling  Decision Modelling  Functional Decomposition  Glossary  Interface Analysis  Non-Functional Requirements Analysis  Organizational Modelling  Process Modelling  Prototyping  Roles and Permissions Matrix  Root Cause Analysis  Scope Modelling  Sequence Diagrams  Stakeholder List, Map, or Personas  State Modelling  Use Cases and Scenarios  User Stories
STAKEHOLDER for Specify and Model Requirements	 Any Stakeholder
OUTPUT for Specify and Model Requirements	 Requirements[prioritized]
INPUT for Verify Requirements	 Requirements (specified and modelling)
ELEMENT for Verify Requirements	 Characteristics of Requirements and Designs Quality: Atomic Complete Consistent Concise Feasible Unambiguous Testable Prioritized Understandable  Verification Activities  Checklists
GUIDELINES AND TOOL for Verify Requirements	 Requirements Life Cycle Management Tools
TECHNIQUES for Verify Requirements	 Acceptance And Evaluation Criteria  Item Tracking  Metrics And Key Performance Indicators (KPIs)  Reviews
STAKEHOLDERS for Verify Requirements	All stakeholders
OUTPUT for Verify Requirements	Requirements (verified)
INPUT for Validate Requirements	 Requirements (specified and modelled)
ELEMENT for Validate Requirements	 Identify Assumptions  Define Measurable Evaluation Criteria  Evaluate Alignment with Solution Scope
GUIDELINES AND TOOL for Validate Requirements	 Business Objectives  Future State Description  Potential Value  Solution Scope
TECHNIQUES for Validate Requirements	 Acceptance Evaluation Criteria  Document Analysis  Financial Analysis  Item tracking  Metrics and Key Performance Indicators (KPIs)  Reviews  Risk Analysis and Management
STAKEHOLDER for Validate Requirements	 All stakeholders
OUTPUT for Validate Requirements	Requirements [validated]
INPUT for Define Requirements Architecture	 Information Management Approach  Requirements(any state)  Solution Scope
ELEMENT for Define Requirements Architecture	 Requirements Viewpoints and Views  Template Architectures  Completeness  Relate and Verify Requirements Relationships: Defined Necessary Correct Unambiguous Consistent  Business Analysis Information Architecture
GUIDELINES AND TOOL for Define Requirements Architecture	 Architecture Management Software  Legal/Regulatory Information  Methodologies and Frameworks
TECHNIQUES for Define Requirements Architecture	 Data Modelling  Functional Decomposition  Interviews  Organizational Modelling  Scope Modelling  Workshops
STAKEHOLDER for Define Requirements Architecture	 Domain subject Matter Expert  Implementation Subject Matter Expert  Project Manager  Sponsor  Tester  Any Stakeholder
OUTPUT for Define Requirements Architecture	 Requirements Architecture
INPUT for Define Design Options	 Change Strategy  Requirements (validated, prioritized)  Requirements Architecture
ELEMENT for Define Design Options	 Define Solution Approaches  Identify Improvements Opportunities  Requirements Allocation  Describe Design Options
GUIDELINES AND TOOL for Define Design Options	 Existing Solutions  Future State Description  Requirements (traced)  Solution Scope
TECHNIQUES for Define Design Options	 Benchmarking and Market Analysis  Brainstorming  Document Analysis  Interviews  Lesson learned  Mind mapping  Root cause Analysis  Survey or Questionnaire  Vendor Assessment  Workshops
STAKEHOLDERS for Define Design Options	 Domain S.M.E.  Implementation S.M.E  Operational Support  Project Manager  Supplier
OUTPUT for Define Design Options	 Design Options
INPUT for Analyze Potential Value and Recommend Solutions	 Potential Value  Design Options
ELEMENT for Analyze Potential Value and Recommend Solutions	 Expected Benefits  Expected Costs  Determine Value  Assess Design Option and Recommend Solution
GUIDELINES AND TOOL for Analyze Potential Value and Recommend Solutions	 Business Objectives  Current state Description  Future State Description  Risk Analysis Results  Solution Scope
TECHNIQUES for Analyze Potential Value and Recommend Solutions	 Acceptance and Evaluation Criteria  Backlog Management  Brainstorming  Business cases  Business Model Canvas  Decision Analysis  Estimation  Financial Analysis  Focus Groups  Interviews  Metrics and Key Performance Indicators (KPIs)  Risk Analysis and Management  Survey or Questionnaire  SWOT Analysis  Workshops
STAKEHOLDER for Analyze Potential Value and Recommend Solutions	 Customer  Domain S.M.E.  End user  Implementation S.M.E.  Project manager  Regulator  Sponsor
OUTPUT for Analyze Potential Value and Recommend Solutions	Solution Recommendation

Next up

CBAP - Requirements Analysis and Design Definition

Description

Resource summary

Similar

	Created by Timothy Ope almost 7 years ago