GoConqr has a new look! Let us know what you think.

Sign up free

Flashcards

CBAP - Requirements Analysis and Design Definition

Timothy Ope BUSINESS ANALYSIS VERSION 3 English 37 cards

Cards in this deck (37)

  1. 1Requirements Analysis and Design Definition TASK1. 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
  2. 2INPUTS for Specify and Model Requirements Elicitation Results (any state)
  3. 3ELEMENTS 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
  4. 4GUIDELINES AND TOOL for Specify and Model Requirements Modelling Notations/Standards  Modelling Tools  Requirements Architecture  Requirements Life Cycle Management Tools  Solution Scope
  5. 5TECHNIQUES 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
  6. 6STAKEHOLDER for Specify and Model Requirements Any Stakeholder
  7. 7OUTPUT for Specify and Model Requirements Requirements[prioritized]
  8. 8INPUT for Verify Requirements Requirements (specified and modelling)
  9. 9ELEMENT for Verify Requirements Characteristics of Requirements and Designs Quality: Atomic Complete Consistent Concise Feasible Unambiguous Testable Prioritized Understandable  Verification Activities  Checklists
  10. 10GUIDELINES AND TOOL for Verify Requirements Requirements Life Cycle Management Tools
  11. 11TECHNIQUES for Verify Requirements Acceptance And Evaluation Criteria  Item Tracking  Metrics And Key Performance Indicators (KPIs)  Reviews
  12. 12STAKEHOLDERS for Verify RequirementsAll stakeholders
  13. 13OUTPUT for Verify RequirementsRequirements (verified)
  14. 14INPUT for Validate Requirements Requirements (specified and modelled)
  15. 15ELEMENT for Validate Requirements Identify Assumptions  Define Measurable Evaluation Criteria  Evaluate Alignment with Solution Scope
  16. 16GUIDELINES AND TOOL for Validate Requirements Business Objectives  Future State Description  Potential Value  Solution Scope
  17. 17TECHNIQUES for Validate Requirements Acceptance Evaluation Criteria  Document Analysis  Financial Analysis  Item tracking  Metrics and Key Performance Indicators (KPIs)  Reviews  Risk Analysis and Management
  18. 18STAKEHOLDER for Validate Requirements All stakeholders
  19. 19OUTPUT for Validate RequirementsRequirements [validated]
  20. 20INPUT for Define Requirements Architecture Information Management Approach  Requirements(any state)  Solution Scope
  21. 21ELEMENT 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
  22. 22GUIDELINES AND TOOL for Define Requirements Architecture Architecture Management Software  Legal/Regulatory Information  Methodologies and Frameworks
  23. 23TECHNIQUES for Define Requirements Architecture Data Modelling  Functional Decomposition  Interviews  Organizational Modelling  Scope Modelling  Workshops
  24. 24STAKEHOLDER for Define Requirements Architecture Domain subject Matter Expert  Implementation Subject Matter Expert  Project Manager  Sponsor  Tester  Any Stakeholder
  25. 25OUTPUT for Define Requirements Architecture Requirements Architecture
  26. 26INPUT for Define Design Options Change Strategy  Requirements (validated, prioritized)  Requirements Architecture
  27. 27ELEMENT for Define Design Options Define Solution Approaches  Identify Improvements Opportunities  Requirements Allocation  Describe Design Options
  28. 28GUIDELINES AND TOOL for Define Design Options Existing Solutions  Future State Description  Requirements (traced)  Solution Scope
  29. 29TECHNIQUES 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
  30. 30STAKEHOLDERS for Define Design Options Domain S.M.E.  Implementation S.M.E  Operational Support  Project Manager  Supplier
  31. 31OUTPUT for Define Design Options Design Options
  32. 32INPUT for Analyze Potential Value and Recommend Solutions Potential Value  Design Options
  33. 33ELEMENT for Analyze Potential Value and Recommend Solutions Expected Benefits  Expected Costs  Determine Value  Assess Design Option and Recommend Solution
  34. 34GUIDELINES AND TOOL for Analyze Potential Value and Recommend Solutions Business Objectives  Current state Description  Future State Description  Risk Analysis Results  Solution Scope
  35. 35TECHNIQUES 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
  36. 36STAKEHOLDER for Analyze Potential Value and Recommend Solutions Customer  Domain S.M.E.  End user  Implementation S.M.E.  Project manager  Regulator  Sponsor
  37. 37OUTPUT for Analyze Potential Value and Recommend SolutionsSolution Recommendation

Information

Description
VERSION 3 BUSINESS ANALYSIS Flashcards on CBAP - Requirements Analysis and Design Definition, created by Timothy Ope on 01/07/2017.
Created by
Timothy Ope
Views
101
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?