CPIT BA flashcards
CPIT BA · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Stakeholder matrix
- A grid that plots stakeholders by influence and interest to determine engagement strategy, communication frequency, and level of involvement in business analysis activities.
- Business analysis approach
- The planned method for performing business analysis work, describing deliverables, timing, techniques, and level of formality; it may be predictive, adaptive, or hybrid.
- Governance
- The decision-making framework for business analysis work, defining who approves requirements, how changes are controlled, and how conflicts are escalated.
- Information management plan
- The plan describing how business analysis information is stored, structured, traced, accessed, and reused throughout the initiative and beyond.
- Performance improvement
- The process of measuring business analysis work, identifying gaps, and taking corrective action to increase effectiveness and efficiency.
- Elicitation
- The activity of drawing out information from stakeholders and other sources through preparation, conduct, confirmation, and communication, not simply collecting stated requirements.
- Prepare for elicitation
- The step of defining scope, selecting techniques, scheduling sessions, and ensuring stakeholder availability before conducting elicitation activities.
- Observation
- An elicitation technique in which the analyst watches stakeholders perform work to capture tacit knowledge and actual process steps that interviews may miss.
- Confirm elicitation results
- The check that captured information accurately reflects stakeholder intent before it is treated as a validated requirement or design input.
- Stakeholder collaboration
- Ongoing engagement with stakeholders throughout the initiative to maintain alignment, resolve concerns, and support effective communication of business analysis information.
- Traceability
- The ability to link requirements to their sources, designs, tests, and other requirements, supporting impact analysis and verification of coverage.
- Requirements baseline
- An approved set of requirements placed under formal change control, against which subsequent changes are assessed and managed.
- Impact analysis
- The assessment of a proposed change on scope, schedule, cost, risk, dependencies, and affected stakeholders before a decision to approve or reject.
- Requirements attributes
- Metadata assigned to each requirement, such as identifier, source, priority, status, owner, complexity, and acceptance criteria, used to manage the requirement life cycle.
- Maintain requirements
- The ongoing activity of keeping requirements and their attributes accurate and current as the business and solution context change.
- Reuse requirements
- The practice of applying existing requirements to a new context after confirming that they remain valid and relevant.
- Current state analysis
- The examination of the existing business environment, including processes, capabilities, and problems, to establish a baseline for change.
- Future state definition
- The description of the desired business environment, including goals, objectives, capabilities, and constraints that the change should achieve.
- Gap analysis
- A comparison of current and future states that identifies missing capabilities, process changes, and organizational impacts required to close the gap.
- SMART objectives
- Business objectives stated as specific, measurable, achievable, relevant, and time-bound, enabling clear evaluation of progress and success.
- Change strategy
- The recommended approach for transitioning from current to future state, selected by comparing solution options on cost, benefit, risk, and feasibility.
- SWOT analysis
- A technique that pairs internal strengths and weaknesses with external opportunities and threats to inform strategy and identify areas requiring change.
- Requirements classification
- The organization of requirements into categories such as business, stakeholder, solution, and transition, or functional and nonfunctional, to support analysis and design.
- Verify requirements
- The quality check that requirements are complete, consistent, unambiguous, and testable, independent of whether they align with business goals.
- Validate requirements
- The check that requirements and designs align with business goals and deliver value to stakeholders, confirming the right solution is being built.
- Acceptance criteria
- The conditions a solution must satisfy to be accepted by stakeholders, expressed independently of design specifications and used to verify fitness for purpose.
- Design options
- Alternative solution designs evaluated against trade-off criteria such as cost, time, risk, and architectural alignment before a recommendation is made.
- Nonfunctional requirements
- Requirements describing solution qualities and constraints, such as performance, security, usability, reliability, and maintainability, rather than specific behaviors.
- Solution performance measures
- Metrics defined to evaluate how well a delivered solution meets business objectives, requiring baselines for meaningful interpretation.
- Solution limitations
- Constraints or defects internal to the solution, such as design gaps or technical shortcomings, that reduce its ability to deliver value.
- Enterprise limitations
- Constraints external to the solution, such as organizational policy, process, or capability gaps, that affect the value the solution can deliver.
- Core concept model
- The framework of Change, Need, Solution, Stakeholder, Value, and Context that defines business analysis and links each concept to the others.