INFO6007 Chap.6 Quality Planning, Assurance and Control
Quality Planning, Assurance and Control
This chapter turns broad quality goals into measurable criteria, named evidence and authorised acceptance. It distinguishes preventive process assurance from product inspection and testing, then connects verification, validation and failure costs. Strong quality planning links every standard to a deliverable, threshold, test condition, evidence owner and decision rather than listing frameworks without implementation.
Quality assurance reviews whether suitable methods, responsibilities and controls are operating; quality control inspects outputs and verifies correction. Verification checks conformance to specification, while validation checks whether the chosen solution works for the real stakeholder need. Criteria should identify the measure, threshold, environment, version and acceptance authority.
Defect counts also need severity and consequence because one security exposure may matter more than many cosmetic issues. Prevention and appraisal consume planned effort, but internal and external failures can create rework, outage, compliance exposure and lost trust. The objective is risk proportionate evidence, not maximum testing or a decorative list of standards.
What this chapter covers
- 01
Quality objectives in IT projects
- 02
Measurable standards and criteria
- 03
Quality assurance
- 04
Quality control
- 05
Verification and validation
- 06
Prevention, appraisal and failure costs
- 07
Acceptance evidence
- 08
Translate a quality aspiration into a measurable metric, threshold, method, timing and accountable reviewer
- 09
Select Pareto, cause-and-effect, check-sheet, flowchart or control-chart analysis according to the question the evidence must answer
- 10
Distinguish process control limits from customer specification limits when interpreting variation and conformance
- 11
Compare prevention and appraisal spending with internal and external failure exposure rather than maximising inspection
- 12
Connect corrective action to a detected nonconformity and preventive improvement to the system mechanism that may recur
- 13
Scale quality evidence to consequence and uncertainty rather than demanding identical controls for every deliverable
Worked example · free
Plan quality for an identity service
- +1Define security and performance measures.
- +1Set thresholds and test conditions.
- +1Name assurance reviews for the process.
- +1Name control tests for the product.
- +1Assign the acceptance owner and evidence.
Key terms
- Quality assurance
- Preventive and process oriented work checking whether suitable methods and controls are used.
- Quality control
- Inspection and testing of deliverables against defined acceptance criteria.
- Validation
- Evidence that the delivered solution meets the stakeholder need and intended use.
Quality Planning, Assurance and Control FAQ
How do QA and QC differ?
Quality assurance examines and improves the process used to create outputs. Quality control inspects and tests the actual outputs against measurable criteria, then verifies corrections.
What is the difference between verification and validation?
Verification asks whether the team built according to specification. Validation asks whether the specified and delivered product is the right solution for the user need.
Why link quality criteria to deliverables?
A generic standard cannot guide acceptance. Deliverable links reveal the test, owner, threshold and decision, allowing defects and process weaknesses to trigger specific corrective work.
Exam move
Study quality by converting intentions into controlled evidence. Choose one IT deliverable and replace vague terms such as reliable, secure, accurate and usable with a measure, threshold, test condition, evidence record and acceptance owner. Separate assurance from control every time.
Assurance asks whether suitable processes, standards, reviews and responsibilities are operating; control inspects or tests the product and records defects. Create paired examples, such as a design review for assurance and a penetration test for control. Then distinguish verification from validation.
Verification checks conformance to specification; validation checks whether the specified solution actually meets stakeholder need. A workflow can pass every technical test and still fail validation when users cannot perform their real work. Map responsibility for setting criteria, performing checks, recording defects, verifying correction and accepting the output.
Consider independence where a supplier or security exposure makes self-assessment weak. Add a response threshold so measurement triggers action rather than decorating a dashboard. Review cost of quality as a trade-off: prevention and appraisal require planned effort, internal failure creates rework before release, and external failure can create outage, compliance exposure and lost trust. Do not recommend maximum testing.
Select evidence proportionate to risk and consequence. For a fresh case, link each quality activity to schedule, cost and risk, then show how a failed criterion enters corrective work or change control. Put the assurance versus control and verification versus validation boundaries on the notes sheet beside a criterion pattern: measure, threshold, condition, owner and decision.
When answering a case, name the deliverable first, then give a process control, an output test and the authorised acceptance route. This makes the recommendation project specific and prevents a list of standards from replacing an operational quality plan.
Working through Quality Planning, Assurance and Control in INFO6007? Sia is AskSia’s AI Project Management tutor — ask any INFO6007 Quality Planning, Assurance and Control question and get a clear, step-by-step explanation grounded in how INFO6007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.