PBA IQA study plan

Map every task and output of Requirements Analysis and Design Definition into a personal one-page model, then explain each element aloud without notes.

Distinguish requirements classification schema types by sorting 30 self-written example statements into stakeholder, solution, functional, non-functional, and transition categories.

Compare requirements attributes by writing a table that assigns priority, complexity, and ownership to 12 sample requirements.

Practice selecting between process modeling, data modeling, and use case notation for 10 short business scenarios and justify each choice in two sentences.

Draft a full requirements package outline for a fictional service business, covering verification activities and design options.

Evaluate three design option trade-offs by scoring each against cost, risk, and value criteria.

Identify and correct ambiguous or unmeasurable wording in 20 sample requirement statements.

Produce a traceability matrix linking 15 requirements to their business objectives and acceptance criteria.

Analyze a fictional company case to distinguish current-state problems from future-state opportunities.

Assess internal and external change drivers, then rank them by impact and urgency.

Construct a future-state description with measurable business goals and supporting assumptions.

Compare alternative solution approaches and recommend one with a documented feasibility rationale.

Define a change strategy that names stakeholders, risks, and transition steps.

Design solution evaluation measures for a new system, covering both leading and lagging indicators.

Analyze a provided performance data set to identify variance between expected and actual results.

Determine whether a shortfall stems from solution limitations or enterprise limitations, and record the reasoning.

Plan an acceptance and evaluation cycle that specifies timing, participants, and evidence sources.

Appraise deployed solution performance against the plan from week 4 and recommend corrective actions.

Trace five requirements through their full life cycle, from elicitation to retirement, and record each status change.

Apply prioritization techniques to re-rank a requirement backlog and justify each change.

Assess the impact of a proposed requirement change on scope, schedule, and dependent requirements.

Formulate a stakeholder engagement approach that assigns influence, interest, and communication frequency to eight stakeholder types.

Plan business analysis activities by sequencing tasks, effort, and dependencies for a medium project.

Select appropriate requirements approval and traceability approaches for two contrasting project types.

Draft a governance plan describing how requirement baselines, changes, and rework will be controlled.

Prepare elicitation activity plans for interviews, workshops, observation, and document analysis, each with purpose and preparation steps.

Write 12 open-ended questions that avoid leading or solution-bias wording.

Confirm elicitation results by identifying inconsistencies and documenting resolution decisions.

Communicate business analysis information to two different audiences using adapted formats and terminology.

Manage a simulated stakeholder conflict by writing a resolution summary with agreed actions.

Apply analytical and problem-solving techniques to three short case scenarios and record the reasoning path.

Demonstrate behavioral characteristics by writing responses to six situational prompts about ethics, adaptability, and collaboration.

Complete two timed mixed-domain practice sets and log every miss with its underlying knowledge gap.

Consolidate weak areas into a final review sheet and re-test those areas until accuracy improves.