CBAP - Requirement LifeCycle

Description

IIBA Knowledge Area
Timothy Ope
Flashcards by Timothy Ope, updated more than 1 year ago
Timothy Ope
Created by Timothy Ope over 7 years ago
30
1

Resource summary

Question Answer
Requirement Life Cycle Management Task 1. Trace Requirements 2. Maintain Requirements 3. Prioritize Requirements 4. Assess Requirements Changes 5. Approve Requirements
INPUT for Trace Requirements  Requirements  Designs
ELEMENTS for Trace Requirements  Level of Formality  Relationships  Traceability Repository
GUIDELINES AND TOOLS for Trace Requirements  Domain Knowledge  Information Management Approach  Legal/Regulatory Information  Requirements Management Tools/Repository
TECHNIQUES for Trace Requirements  Business Rules Analysis  Functional Decomposition  Process Modelling  Scope Modelling
STAKEHOLDERS for Trace Requirements  Customers  Domain subject matter expert  End users  Implementation Subject Matter Expert  Operational Support  Project Manager  Sponsor  Suppliers  Testers
OUTPUT for Trace Requirements  Requirements(traced)  Design(traced)
INPUT for Maintain Requirements  Requirements  Designs
ELEMENT for Maintain Requirements  Maintain Requirements  Maintain Attributes  Reusing Requirements
GUIDELINES AND TOOL for Maintain Requirements  Information Management Approach
TECHNIQUES for Maintain Requirements  Business Rules Analysis  Data Flow Diagrams  Data Modelling  Document Analysis  Functional Decomposition  Process Modelling  Use Cases and Scenarios  User Stories
STAKEHOLDERS for Maintain Requirements  Domain S.M.E  Implementation S.M.E  Operational Support  Regulator  Tester
OUTPUT for Maintain Requirements Requirements(maintained) Designs(maintained)
INPUT for Prioritize Requirements  Requirements  Designs
ELEMENTS for Prioritize Requirements  Basis for prioritization  Challenges of Prioritization  Continual Prioritization
GUIDELINES AND TOOL for Prioritize Requirements  Business Constraints  Change Strategy  Domain Knowledge  Governance Approach  Requirements Architecture  Requirement Management Tools/Repository  Solution scope
TECHNIQUES for Prioritize Requirements  Backlog Management  Business Cases  Decision Analysis Estimation  Financial Analysis  Interviews  Item Tracking  Prioritization  Risk Analysis And Management  Workshops
STAKEHOLDERS for Prioritize Requirements  Customer  End User  Implementation S.M.E.  Project Manager  Regulator  Sponsor
OUTPUT for Prioritize Requirements  Requirements (prioritized)  Designs (prioritized)
INPUT for Assess Requirements Changes  Proposed Change  Requirements  Designs
ELEMENTS for Assess Requirements Changes  Assessment Formality  Impact Analysis  Impact Resolution
GUIDELINES AND TOOL for Assess Requirements Changes  Change Strategy  Domain Knowledge  Governance Approach  Legal/Regulatory information  Requirements Architecture  Solution Scope
TECHNIQUES for Assess Requirements Changes  Business Cases  Business Rules Analysis  Decision Analysis  Document Analysis  Estimation  Financial Analysis  Interface Analysis  Interviews  Item Tracking  Risk Analysis and Management  Workshops
STAKEHOLDERS for Assess Requirements Changes  Customer  Domain S.M.E.  End User  Operational Support  Project Manager  Regulator  Sponsor  Tester
OUTPUT for Assess Requirements Changes  Requirements Change Assessment  Designs Change Assessment
INPUT for Approve Requirements  Requirements (verified)  Design
ELEMENT for Approve Requirements  Understand Stakeholder Roles  Conflict and Issue Management  Gain Consensus  Track and Communicate Approval
GUIDELINES AND TOOL for Approve Requirements  Change Strategy  Governance Approach  Legal/Regulatory Information  Requirement Management Tools/Repository  Solution Scope
TECHNIQUES for Approve Requirements  Acceptance and Evaluation Criteria  Decision Analysis  Item Tracking  Reviews  Workshops
STAKEHOLDER for Approve Requirements  Customer  Domain S.M.E.  End User  Operational Support  Project Manager  Regulator  Sponsor  Tester
OUTPUT for Approve Requirements  Requirements (approved)  Designs (approved)
Show full summary Hide full summary

Similar

3.2 Securing the enterprise
DJ Perrone
BABOK 3 - Tasks & Descriptions
Giovanni Basso
Basic Business Analyst questions
Yulia Faizrahmanova
The Engineering Stakeholder Interview
Yulia Faizrahmanova
Writing high level requirements - business analysis
Angel Falese JP
aldo
czdent
BABOK 3 - Tasks & Purposes
Giovanni Basso
Business Analysis Beyond Projects
Mohamed Elgendy
Chemistry Module C2: Material Choices
James McConnell