25-Comp-B11 Advanced Software Design · December 2019
Question 27 of 28: Interface vs. Class, and Simulating a Java Interface in C++
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)
Question 27: Interface vs. Class, and Simulating a Java Interface in C++ (Part V)
Interface vs. class. A Java class is a full blueprint combining both STATE (instance fields) and BEHAVIOUR (implemented methods), can be instantiated directly if concrete, and supports only SINGLE inheritance of another class. A Java interface declares a pure contract — method signatures (plus, since Java 8, optional default implementations) and constants, with NO instance state and no constructors of its own; a class implementing it must supply concrete implementations of its abstract methods. Critically, a class may implements any number of interfaces — multiple inheritance of TYPE is allowed even though multiple inheritance of class IMPLEMENTATION is not (Question 24's dynamic binding still applies: a call through an interface reference dispatches to whichever concrete class's method actually implements it).
Simulating in C++. C++ has no dedicated interface keyword, but a Java-style interface is simulated with an ABSTRACT CLASS containing ONLY pure virtual functions (= 0) and no data members, no implemented methods (beyond a virtual destructor). Because C++ already permits multiple inheritance of ordinary classes, a class can "implement" several such pure-abstract classes simultaneously — achieving Java's multiple-interface-implementation directly, and safely, because a class with zero data members and zero implemented methods carries none of the diamond-problem ambiguity (conflicting inherited state or behaviour) that motivated Java's restriction to single class inheritance in the first place.