PMI CD-BA flashcards
PMI CD-BA · Build recall with a focused review session.
34 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Business need
- The problem or opportunity facing the organization that justifies investing in a solution; it is the root input to needs assessment and anchors all downstream traceability.
- Situation statement
- A document describing the problem or opportunity, affected stakeholders, the impact of the problem, and the potential value of resolving it before solution work begins.
- Gap analysis
- A comparison of current-state capability against desired-state capability that identifies the specific shortfall a solution must close to satisfy the business need.
- Root cause analysis
- A technique set including 5 Whys, fishbone diagrams, and process mapping used to move from observed symptoms to the underlying cause of a business problem.
- Go/no-go recommendation
- The needs assessment conclusion stating whether the organization should proceed to solution development, based on viability, value, and feasibility of the identified options.
- Measurable business objective
- A goal statement that is specific, time-bound, and quantified so solution performance can later be evaluated against a defined target.
- Business analysis approach
- The planned method for performing business analysis on an initiative, selected based on delivery method, risk tolerance, regulatory constraints, and stakeholder needs.
- Stakeholder engagement plan
- A plan defining which stakeholders are involved, at what level, through which techniques and channels, and how their participation will be maintained across the initiative.
- RACI matrix
- A responsibility assignment model where each activity has one accountable party, plus responsible, consulted, and informed parties to clarify decision rights.
- Elicitation plan
- The schedule of elicitation techniques, sources, and timing, matched to stakeholder availability and the type of information still needed for analysis.
- Traceability approach
- The planned level of traceability granularity and the repository or tool that will record links between needs, requirements, designs, and test cases.
- Governance and approval rules
- Documented rules specifying who approves requirement changes, what escalation thresholds apply, and how baselines are authorized and modified.
- Information management plan
- A plan for how business analysis information is stored, versioned, accessed, and secured, including format standards and retention of work products.
- Stakeholder analysis
- Assessment of stakeholders by influence, interest, authority, attitude toward change, and impact from the solution, used to tailor engagement and communication.
- Requirement types
- The classification of requirements as business, stakeholder, solution (functional and non-functional), and transition, each serving a distinct purpose in the solution lifecycle.
- Requirement quality criteria
- A test of a requirement as necessary, unambiguous, complete, consistent, feasible, verifiable, and traceable, used to judge readiness for approval.
- Functional requirement
- A statement of behavior the solution must perform, describing what the solution does in response to inputs, events, or user actions.
- Non-functional requirement
- A quality or constraint requirement such as performance, availability, security, usability, scalability, maintainability, or compliance that bounds how the solution behaves.
- Acceptance criteria
- The conditions of satisfaction that a solution component must meet, written to be testable and used as the basis for verification and sign-off.
- Verification versus validation
- Verification confirms a requirement is well-formed and correctly written; validation confirms it accurately represents the real stakeholder need and delivers intended value.
- MoSCoW prioritization
- A ranking scheme classifying requirements as must have, should have, could have, or will not have this time, based on business value and delivery constraints.
- Use case components
- The elements of a use case: actors, preconditions, main success scenario, alternate and exception flows, and postconditions describing the outcome state.
- Requirement decomposition
- Breaking a requirement into smaller components until each can be independently estimated, built, and verified, improving clarity and traceability.
- Model selection rule
- Choose the modeling technique by the question to answer: process flow for sequence, state model for lifecycle, data model for structure, decision model for rules.
- Forward traceability
- Linking a requirement forward to its design elements, build components, and test cases to confirm it is implemented and verified.
- Backward traceability
- Linking a requirement back to its source business need or stakeholder request to confirm that every requirement has a legitimate origin.
- Requirement baseline
- The approved, frozen version of a set of requirements; changes to it are permitted only through the documented change control process.
- Change impact analysis
- Assessment of a proposed requirement change against scope, schedule, cost, quality, risk, and affected designs and test cases before approval.
- Traceability matrix
- A table recording requirement ID, source, rationale, linked design elements, test cases, status, and owner to support coverage and orphan detection.
- Orphan requirement
- A requirement with no upstream source or no downstream test case, indicating a traceability gap that must be resolved before approval or verification.
- Solution evaluation
- The assessment of how well a delivered solution meets the business goals and objectives, including measured performance, benefit timing, and residual gaps.
- Solution limitation
- A constraint or deficiency within the solution itself that prevents it from achieving the target performance or value defined in the business objectives.
- Enterprise limitation
- An organizational constraint outside the solution, such as policy, staffing, or process, that restricts the value the solution can deliver.
- Solution replacement or retirement
- The evaluation decision to remove or substitute a solution, requiring assessment of stakeholder impact, data migration, cost, and continuity of business value.