Question 24 of 28: Polymorphism, Dynamic Binding, Overloading, Overriding
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Notes on this paper
98-Comp-B11 Advanced Software Design — National Exams, May 2016. 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, agile methods, design principles, 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 (Singleton, Proxy, Template Method, Observer, etc.); Sebesta, Concepts of Programming Languages (12th ed.) — polymorphism, dynamic binding, inheritance and language-level object semantics; Bertrand Meyer, Object-Oriented Software Construction — design by contract, preconditions/postconditions/invariants, the open–closed principle; Barbara Liskov's 1987 substitutability paper for Question 11; Rogers, Sharp & Preece, Interaction Design, and Nielsen, Usability Engineering, for Question 21's HMI-specific non-functional requirements; Myers, The Art of Software Testing, for Question 28's boundary value analysis.
Polymorphism is the ability of a single name (a method call, a variable) to refer to, or be applied to, objects of more than one type, so that code written against a general interface can operate uniformly over different concrete types without knowing which one it holds.
Dynamic binding (late binding) is the RUNTIME mechanism that resolves a call to a polymorphic operation to the actual implementing method based on the object's real, runtime type — not its declared, compile-time type — typically implemented via a per-class dispatch table (vtable) that is consulted at the moment of the call.
Overloading is defining multiple methods that share the same name but differ in parameter signature (number/type of parameters). It is resolved entirely at COMPILE time, by the compiler matching the call site's argument types against the available signatures — no runtime dispatch is involved.
Overriding is a subclass supplying its own implementation of a method already declared in a superclass, with an IDENTICAL signature. This is precisely what dynamic binding dispatches between at runtime: when client code calls the method through a base-type reference, dynamic binding selects whichever override matches the object's actual runtime type.
How they relate. Polymorphism is the general concept (one interface, many forms); overriding plus dynamic binding together are the runtime MECHANISM implementing one specific and very common kind of polymorphism (inclusion/subtype polymorphism, exercised through inheritance, and the basis for Question 11's LSP discussion). Overloading is a DIFFERENT kind of polymorphism entirely (ad hoc polymorphism) that is resolved statically at compile time and never touches the vtable/dynamic-dispatch mechanism at all. A common confusion is treating overloading and overriding as the same idea because both "give a method multiple forms" — they do not share a resolution mechanism, and a method accidentally declared with a superclass-matching name but a DIFFERENT signature silently overloads rather than overrides it, meaning it never participates in dynamic dispatch at all.
