What a Design Pattern Is, and Why Design Patterns Matter: 25-Comp-B11 Advanced Software Design, December 2019, Q13

Question 13 of 28: What a Design Pattern Is, and Why Design Patterns Matter

Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)

Notes on this paper

17-Comp-B11 Advanced Software Design — National Exams, December 2019. 3 hours, closed book exam with one aid sheet allowed (written on both sides), no calculator permitted. The paper is organized into five parts, and candidates were instructed to answer any five (5) questions in Part I, any three (3) in Part II, any four (4) in Part III, any two (2) in Part IV, and any five (5) in Part V — only the first questions answered, in each part, as they appear in the answer book are marked. All questions carry equal weight, so the 19 questions actually marked (5+3+4+2+5 of 28) each count for 100/19 ≈ 5.26% of the paper. All 28 questions are answered below for completeness.

Reference texts: Sommerville, Software Engineering (10th ed., Pearson) — software processes, requirements engineering, design principles, testing, dependability; Pressman, Software Engineering: A Practitioner's Approach (9th ed.) — supplementary process and quality coverage; Gamma, Helm, Johnson & Vlissides (GoF), Design Patterns: Elements of Reusable Object-Oriented Software — creational/structural/behavioural pattern catalogue and the "program to an interface, not an implementation" / "favor object composition over class inheritance" principles; Sebesta, Concepts of Programming Languages (12th ed.) — polymorphism, dynamic binding, visibility, and multiple inheritance semantics; Bertrand Meyer, Object-Oriented Software Construction — design by contract, preconditions/postconditions/class invariants; Barbara Liskov's 1987 substitutability paper for Question 12; Karl Wiegers, Software Requirements (3rd ed.); Myers, The Art of Software Testing, for Question 6.

PART I — General Principles (answer any 5 of 7)

PART III — Patterns (answer any 4 of 5)

Question 13: What a Design Pattern Is, and Why Design Patterns Matter (Part III)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

A design pattern is a named, reusable solution to a recurring design problem within a particular context, documented in a standard format (GoF: name, problem/intent, solution structure, and consequences/trade-offs) so it can be recognized and applied by other designers without re-deriving it from scratch.

Example — Observer. Problem: several dependent objects must be automatically notified whenever one subject's state changes, without the subject needing to know their concrete types. Solution: the subject keeps a list of registered Observer references and calls a common update() method on each whenever its state changes; observers register/unregister themselves and decide independently how to react.

Why patterns matter. They give designers a shared VOCABULARY ("just use Observer here") that communicates an entire design structure in one word instead of a paragraph of diagrams; they encode already-proven solutions, so a designer benefits from the collective experience of prior designers instead of rediscovering the same solution (and its pitfalls) independently; and each pattern's documented CONSEQUENCES section explicitly states its trade-offs, helping a designer choose the right pattern for the actual problem rather than force-fitting a familiar one.