GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Kostenlos registrieren

Karteikarten

CBAP - Requirement LifeCycle

Timothy Ope BUSINESS ANALYSIS VERSION 3 Englisch 31 Karten

Karten in diesem Stapel (31)

  1. 1Requirement Life Cycle Management Task1. Trace Requirements
    2. Maintain Requirements
    3. Prioritize Requirements
    4. Assess Requirements Changes
    5. Approve Requirements
  2. 2INPUT for Trace Requirements Requirements  Designs
  3. 3ELEMENTS for Trace Requirements Level of Formality  Relationships  Traceability Repository
  4. 4GUIDELINES AND TOOLS for Trace Requirements Domain Knowledge  Information Management Approach  Legal/Regulatory Information  Requirements Management Tools/Repository
  5. 5TECHNIQUES for Trace Requirements Business Rules Analysis  Functional Decomposition  Process Modelling  Scope Modelling
  6. 6STAKEHOLDERS for Trace Requirements Customers  Domain subject matter expert  End users  Implementation Subject Matter Expert  Operational Support  Project Manager  Sponsor  Suppliers  Testers
  7. 7OUTPUT for Trace Requirements Requirements(traced)  Design(traced)
  8. 8INPUT for Maintain Requirements Requirements  Designs
  9. 9ELEMENT for Maintain Requirements Maintain Requirements  Maintain Attributes  Reusing Requirements
  10. 10GUIDELINES AND TOOL for Maintain Requirements Information Management Approach
  11. 11TECHNIQUES for Maintain Requirements Business Rules Analysis  Data Flow Diagrams  Data Modelling  Document Analysis  Functional Decomposition  Process Modelling  Use Cases and Scenarios  User Stories
  12. 12STAKEHOLDERS for Maintain Requirements Domain S.M.E  Implementation S.M.E  Operational Support  Regulator  Tester
  13. 13OUTPUT for Maintain RequirementsRequirements(maintained) Designs(maintained)
  14. 14INPUT for Prioritize Requirements Requirements  Designs
  15. 15ELEMENTS for Prioritize Requirements Basis for prioritization  Challenges of Prioritization  Continual Prioritization
  16. 16GUIDELINES AND TOOL for Prioritize Requirements Business Constraints  Change Strategy  Domain Knowledge  Governance Approach  Requirements Architecture  Requirement Management Tools/Repository  Solution scope
  17. 17TECHNIQUES for Prioritize Requirements Backlog Management  Business Cases  Decision Analysis Estimation  Financial Analysis  Interviews  Item Tracking  Prioritization  Risk Analysis And Management  Workshops
  18. 18STAKEHOLDERS for Prioritize Requirements Customer  End User  Implementation S.M.E.  Project Manager  Regulator  Sponsor
  19. 19OUTPUT for Prioritize Requirements Requirements (prioritized)  Designs (prioritized)
  20. 20INPUT for Assess Requirements Changes Proposed Change  Requirements  Designs
  21. 21ELEMENTS for Assess Requirements Changes Assessment Formality  Impact Analysis  Impact Resolution
  22. 22GUIDELINES AND TOOL for Assess Requirements Changes Change Strategy  Domain Knowledge  Governance Approach  Legal/Regulatory information  Requirements Architecture  Solution Scope
  23. 23TECHNIQUES 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
  24. 24STAKEHOLDERS for Assess Requirements Changes Customer  Domain S.M.E.  End User  Operational Support  Project Manager  Regulator  Sponsor  Tester
  25. 25OUTPUT for Assess Requirements Changes Requirements Change Assessment  Designs Change Assessment
  26. 26INPUT for Approve Requirements Requirements (verified)  Design
  27. 27ELEMENT for Approve Requirements Understand Stakeholder Roles  Conflict and Issue Management  Gain Consensus  Track and Communicate Approval
  28. 28GUIDELINES AND TOOL for Approve Requirements Change Strategy  Governance Approach  Legal/Regulatory Information  Requirement Management Tools/Repository  Solution Scope
  29. 29TECHNIQUES for Approve Requirements Acceptance and Evaluation Criteria  Decision Analysis  Item Tracking  Reviews  Workshops
  30. 30STAKEHOLDER for Approve Requirements Customer  Domain S.M.E.  End User  Operational Support  Project Manager  Regulator  Sponsor  Tester
  31. 31OUTPUT for Approve Requirements Requirements (approved)  Designs (approved)

Informationen

Beschreibung
IIBA Knowledge Area
Erstellt von
Timothy Ope · Jun 2017
Aktualisiert
1 Jul 2017
Aufrufe
42
Bewertung

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck