How unit 5 is examined
This unit is one topic, the case study, which applies the life cycle, standards and design patterns of Units 1-4 to a single software product; no past question has been asked on it.
Case Study
<span style="display:inline-block;padding:.16em .6em;border:1.5px solid currentColor;border-radius:999px;font-size:.68em;font-weight:700;letter-spacing:.06em;text-transform:uppercase;opacity:.75">Not asked since 2022</span>
Definition. <mark>A case study is a detailed, end-to-end examination of one real software product or project, showing how the life cycle, development standards and design patterns were applied and what result they gave.</mark>
Key points.
- A case study follows the product through the software life cycle: requirements, design, implementation, testing, deployment and maintenance.
- It shows which development standards, such as coding conventions, documentation and quality standards, were followed and why.
- It names the design patterns used, for example Singleton or Factory (creational) and Observer or Strategy (behavioural), and the problem each one solved.
- It ends with the outcome and lessons learned, meaning what worked, what failed and what would be done differently.
Last-minute revision
- A case study is a detailed study of one real product or project.
- It applies the life cycle, standards and design patterns of Units 1-4.
- Life cycle stages: requirements, design, implementation, testing, deployment, maintenance.
- Every design pattern in a case study is tied to the problem it solves.
- A case study closes with results and lessons learned.
- No past question has been asked on Unit 5, so answer from the product you studied in the lab.
Memory hooks
- Case study = "Plan, Pattern, Product, Post-mortem": life cycle, patterns, the built product, lessons learned.
- Unit 5 is Units 1-4 applied to one product.
Coverage checklist
- Case Study: no past questions; definition and four key points covered.