Certification of Capability in Business Analysis (CCBA) — Lesson 3: Requirements Analysis, Models, Lifecycle Control, and Solution Design

Learning Objectives

• Explain how requirement specification, process and data models, and prioritization shape the lesson decision.
• Create a reviewable model package, requirements baseline, and design comparison using the supplied scenario and evidence.
• Resolve the condition where approved requirements change informally and create inconsistent process, interface, and acceptance expectations without introducing a new gap.

Detailed Topics

• Clarify requirement specification by identifying purpose, ownership, boundaries, dependencies, and decision criteria.
• Apply process and data models to the scenario and preserve the evidence supporting the selected approach.
• Compare alternatives for prioritization and explain practical value, risk, and operating consequences.
• Challenge traceability control with a realistic exception that exposes assumptions or weak accountability.
• Document design assessment with acceptance conditions, review responsibility, and a clear next action.

Instructor Demonstration

The instructor demonstrates how to create a model package, baseline the requirements, and evaluate two solution designs. The walkthrough explains which requirements and design choice should be approved for implementation, builds the model package, requirements baseline, and design comparison, and tests the exception where approved requirements change informally and create inconsistent process, interface, and acceptance expectations.

Hands-On Exercise

Complete a controlled exercise to create a model package, baseline the requirements, and evaluate two solution designs and preserve the result in the model package, requirements baseline, and design comparison.

1. Confirm the facts, stakeholders, constraints, evidence sources, and success conditions relevant to requirement specification.
2. Perform the central analysis involving process and data models, prioritization, and traceability control.
3. Introduce the exception where approved requirements change informally and create inconsistent process, interface, and acceptance expectations and revise the proposed response.
4. Complete the model package, requirements baseline, and design comparison with ownership, acceptance evidence, unresolved concerns, and follow-up actions.

Scenario Analysis

• Identify the assumption with the greatest influence on which requirements and design choice should be approved for implementation.
• Compare two defensible responses involving traceability control and explain their trade-offs.
• Specify the evidence required before the model package, requirements baseline, and design comparison can be accepted.

Troubleshooting Guidance

Trace the first difference between the intended outcome and the available evidence. Recheck scope, roles, source quality, dependencies, decision criteria, and retained records independently. The analysis remains incomplete while approved requirements change informally and create inconsistent process, interface, and acceptance expectations.

Validation Checklist

• Scope and ownership for requirement specification are explicit.
• The selected treatment for process and data models is supported by reviewable evidence.
• The exception involving traceability control was tested and its impact recorded.
• The model package, requirements baseline, and design comparison contains acceptance criteria, accountable owners, and next actions.

Lesson Outcome

Learners can apply Requirements Analysis, Models, Lifecycle Control, and Solution Design, explain which requirements and design choice should be approved for implementation, and support the conclusion with a model package, requirements baseline, and design comparison.