Unit 4: Quality and release management
Software Engineering notes · PTU syllabus (UGCC2514)
On this page
Unit summary
Quality must be built into software, not added at the end, and a product's life continues long after its first release. This unit covers quality concepts, software quality assurance, formal technical reviews, statistical SQA, reliability, and release management — from release planning to maintenance, end of life and migration.
After this unit you can
- Explain quality concepts and the cost of quality
- Describe SQA activities, formal technical reviews and statistical SQA
- Define software reliability and its measures
- Plan releases and explain maintenance, end of life and migration strategies
PTU syllabus topics
- Quality concepts
- software quality assurance
- formal technical reviews
- statistical SQA
- software reliability
- release planning
- development and build plans
- release strategies
- post-deployment monitoring
- maintenance
- updates
- end of life and migration strategies
Topic 1
Quality concepts
Software quality is conformance to explicit requirements, standards and implicit expectations. It has two views: quality of design and quality of conformance. Cost of quality: prevention costs (training, planning), appraisal costs (reviews, testing) and failure costs (internal — before release; external — after release, the most expensive).
Example
Verification and validation: reviewing the design document to check that it follows the SRS is verification (are we building the product right?). Running the finished system with users to check that it meets their needs is validation (are we building the right product?).
Topic 2
Software quality assurance and reviews
SQA is a planned set of activities to ensure software meets quality standards: setting standards, reviews and audits, testing, error collection and analysis, change management and education. A formal technical review (FTR) is a meeting of 3–5 people who examine a work product (design or code) to find errors early. Guidelines: review the product, not the producer; set an agenda; limit debate; keep it under two hours; record issues. Statistical SQA collects defect data, traces each defect to its cause and uses the Pareto principle (80% of defects come from 20% of causes) to fix the vital few causes first. Six Sigma aims for 3.4 defects per million opportunities (DMAIC: Define, Measure, Analyse, Improve, Control).
Example
A formal technical review: three reviewers examine the design of the fee module for two hours and find that instalment payments are not handled. Fixing it now costs far less than after coding.
Exam tip
Defects found early are cheaper to fix.
Topic 3
Software reliability
Hardware wears out; software does not wear but changes introduce new defects, producing spikes
Reliability is the probability of failure-free operation for a specified time in a specified environment.
MTTF
Mean time to failure
MTTR
Mean time to repair
MTBF
MTTF + MTTR
Availability
MTTF / (MTTF + MTTR) × 100
Example
Availability: a server runs for 480 hours between failures (MTTF) and takes 20 hours to repair (MTTR). MTBF = 480 + 20 = 500 hours; availability = 480 ÷ (480 + 20) × 100 = 96%. Cutting MTTR to 5 hours raises availability to 480 ÷ 485 = 98.97%.
Topic 4
Release management
- 1
Release planning
Scope, dates, versions
- 2
Development and build plan
Builds, branching, integration
- 3
Release strategy
Big bang, phased, canary or beta release
- 4
Deployment
- 5
Post-deployment monitoring
Errors, performance, user feedback
- 6
Maintenance and updates
Patches and new versions
- 7
End of life and migration
Retire and move users to a new system
Exam tip
Quality questions often ask for the cost of quality split: prevention + appraisal + failure. Failure found after release (external failure) costs the most, which is why reviews and testing before release pay for themselves.
- Types of maintenance: corrective (fix bugs), adaptive (adapt to new environments), perfective (improve features) and preventive (avoid future problems).
- End of life (EOL): support stops; users must be informed in advance.
- Migration strategies: parallel running, phased migration or direct cutover, with data migration and user training.
Example
A planned release: version 2.1 is planned with a fixed scope, built and tested, released to 10% of users first, monitored, then rolled out fully — with a rollback plan ready if problems appear.
Exam tip
Use version numbers (major.minor.patch) and keep release notes.
Key terms
- SQA
- Activities that ensure software meets quality standards
- Formal technical review
- A structured meeting to find errors in a work product
- Reliability
- Probability of failure-free operation over time
- MTBF
- Mean time between failures
- Release management
- Planning, building, deploying and supporting software versions
Quick revision
- Cost of quality: prevention, appraisal, failure (external costliest).
- FTR reviews the product, not the producer.
- Pareto: fix the vital few causes.
- Availability = MTTF / (MTTF + MTTR).
- Maintenance: corrective, adaptive, perfective, preventive.
Important exam questions
Practice questions written to the PTU exam pattern for this unit's syllabus: short answers (Section A style) and long answers (Sections B and C style).
Short-answer questions
- Q1.Define software quality.
- Q2.What is a formal technical review?
- Q3.What is statistical SQA?
- Q4.Define MTBF and availability.
- Q5.Name the four types of software maintenance.
- Q6.What is end of life in software?
Long-answer questions
- Q1.Explain software quality assurance and its activities.
- Q2.Explain formal technical reviews and the guidelines for conducting them.
- Q3.Explain software reliability and its measures with an example.
- Q4.Explain release planning, release strategies, maintenance and migration.
Stuck on this unit?
Message SBS on WhatsApp for help with Software Engineering, or to ask about studying BCA at Synetic.
