CSQE study plan

Map the full CSQE Body of Knowledge outline and mark each area as strong, weak, or unknown before studying anything

Define quality in software terms and distinguish quality control, quality assurance, and quality planning with your own written examples

Trace the cost of quality model and classify at least ten real defects or prevention activities from your own work into prevention, appraisal, internal failure, and external failure

Identify the standards bodies and core standards families most likely to appear (ISO 9000 vocabulary, ISO/IEC 25010 quality characteristics, IEEE 730 and 829 concepts) and note what each covers

Compare plan-driven and iterative delivery models and state how each changes where quality activities land in the lifecycle

Sequence verification and validation activities across requirements, design, code, and release for a sample project

Write entry and exit criteria for three review types (requirements inspection, design review, code review) including roles and defect logging rules

Explain how software configuration management, baselines, and change control protect quality during maintenance

Differentiate measurement scales (nominal, ordinal, interval, ratio) and pick a valid statistic for each

Compute and interpret basic descriptive statistics, control chart limits, and process capability on a small dataset you generate

Select the correct sampling approach for a stated inspection scenario and justify the sample size logic

Distinguish accuracy, precision, reliability, and validity when evaluating a measurement system

Apply the seven basic quality tools to a described defect scenario and choose the tool that fits each question asked

Build a Pareto analysis and a cause-and-effect diagram from the same defect data and explain what each reveals that the other does not

Distinguish root cause analysis approaches and write a corrective action with verification of effectiveness

Explain prevention versus detection and where mistake-proofing fits in software work

Walk through the audit lifecycle for a process audit: charter, criteria, evidence, findings, and follow-up

Draft audit findings that separate observation, nonconformity, and opportunity for improvement

Explain how supplier and subcontractor quality is evaluated and controlled, including acceptance criteria and records

Outline what a software quality management system must contain and how it is maintained and improved

Write testable requirements and identify ambiguity, missing constraints, and unverifiable statements in a supplied requirement set

Design a verification strategy that matches test level to risk, including review, inspection, and analysis where testing is insufficient

Explain validation against user needs and how acceptance criteria differ from verification criteria

Describe how test results, defect trends, and coverage data feed release decisions

Define the core metrics categories (defect, process, product, and project) and state the decision each metric supports

Design a small metrics set with operational definitions, data sources, and thresholds so the numbers cannot be gamed

Interpret trend and variation data and distinguish common cause from special cause signals

Explain how metrics are communicated to management without overreacting to normal variation

Re-rate every BoK area and close the remaining weak spots with targeted review rather than full rereads

Complete timed practice sets and log every miss by root cause (knowledge gap, misread, or reasoning error)

Rehearse the calculations and definitions most often confused, writing them from memory without notes

Build a final-week review sheet limited to items you have personally gotten wrong