CPIT BA study plan

Map the six tasks of Requirements Analysis and Design Definition (specify and model requirements, verify, validate, define design options, analyze potential value, recommend solution) and write a one-paragraph summary of each in your own words.

Draft a personal glossary of 25 core BA terms (requirement, design, traceability, stakeholder, value, solution scope) with a one-line definition and one example each.

Build a blank requirements-modeling template you can reuse: a context diagram, a process flow, and a data model skeleton.

Distinguish business requirements, stakeholder requirements, and solution requirements by classifying 15 sample statements you write yourself.

Practice writing and critiquing requirements for quality: create 20 requirements, then rewrite each to remove ambiguity, vagueness, and compound statements.

Construct a traceability matrix linking 8 stakeholder requirements to solution requirements to test cases.

Compare at least four design options for a small scenario using weighted criteria and justify a recommendation in writing.

Produce a verification and validation checklist and apply it to your week-2 requirements set.

Outline the five tasks of Business Analysis Planning and Monitoring and identify the inputs, outputs, and stakeholders for each.

Write a stakeholder engagement plan for a fictional project covering stakeholder analysis, roles, and communication cadence.

List at least eight elicitation techniques and match each to a situation where it is the best fit, with a stated rationale.

Design a governance plan describing how requirements changes and approvals will be handled.

Prepare a full elicitation session plan: objectives, participants, technique, agenda, and pre-reading.

Run a 30-minute mock elicitation interview with a colleague or study partner and record what worked and what failed.

Draft a set of 15 open and probing questions that avoid leading or solution-biased phrasing.

Write a post-session confirmation summary that records decisions, open items, and follow-ups.

Describe the five Requirements Life Cycle Management tasks and list the inputs and outputs of each.

Build a traceability approach for a scenario with at least three requirement types and two solution components.

Write a requirements baseline and change-control procedure, including impact analysis steps.

Prioritize a set of 12 requirements using two different techniques and explain where the rankings diverge and why.

Draft a requirements-approval workflow identifying who signs off and at which gate.

Summarize the four Strategy Analysis tasks and identify the key techniques used in each.

Perform a current-state assessment of an organization you know, capturing capabilities, gaps, and root causes.

Define a future state with measurable business goals and a gap analysis linking current to future.

Produce a change strategy that addresses scope, risk, and readiness, and compare it to at least one alternative.

List the five Solution Evaluation tasks and explain how each feeds back into requirements management.

Design an evaluation approach with at least four measures, their data sources, and acceptance thresholds.

Analyze a set of mock performance results, identify two limiting factors, and recommend corrective action.

Revisit your week-5 traceability matrix and update it to reflect evaluation findings.

Consolidate all seven domains into a one-page concept map showing how the tasks interconnect.

Complete two timed 60-question practice sets and log every missed item by domain and task.

Re-study your three weakest tasks using your glossary and templates, then re-test those areas.

Write a personal exam-day strategy covering pacing, flagging, and handling scenario questions.