2007 Exam answers

Revision as of 08:40, 6 October 2008

Question 1

[26 marks for whole question] For each part (a)-(m), name the idea (or ideas) that best match the description and briefly explain your answer. If possible, include WikiNames.

1. (a) [2 marks] Keep the number of fields in a class small.

   Answer: One key abstraction, Large class smell, Single responsibility principle, Keep it simple, limit compositions in a class

2. (b) [2 marks] Methods should use most of the fields of the method’s object.

   Answer: Single responsibility principle, One key abstraction, Keep related data and behavior in one place, Methods should use most fields of a class

3. (c) [2 marks] When several methods cooperate to do a job, give them the same name.

   Answer: Recursion introduction

4. (d) [2 marks] Objects should invoke methods of contained objects.

   Answer: Tell, don't ask, Beware accessors, Favor composition over inheritance, Law of Demeter

5. (e) [2 marks] A CodeSmell that supports one of RielsHeuristics.

   Answer: Switch statement smell supports Beware type switches, Large class smell supports Avoid interface bloat and Minimize number of methods.

6. (f) [2 marks] A pattern that conflicts with TellDontAsk.

   Answer: Observer, Visitor.

7. (g) [2 marks] A pattern that supports TellDontAsk.

   Answer: Factory Method, Command, Interpreter.

8. (h) [2 marks] A pattern that employs DoubleDispatch.

   Answer: Visitor

9. (i) [2 marks] A pattern based on ModelTheRealWorld.

   Answer: Singleton, Composite, Model View Controller? Strategy/State?

10. (j) [2 marks] A pattern that conflicts with one of RielsHeuristics.

    Answer: Avoid no-op overrides - Composite, Hide data within its class - Visitor.

11. (k) [2 marks] A pattern that exhibits a CodeSmell.

    Answer: Iterator - Parallel inheritance hierarchies smell, Visitor - Feature envy smell

12. (l) [2 marks] An architectural pattern that contains a design pattern.

    Answer: Observer + Strategy = Model View Controller

13. (m) [2 marks] A design problem that the Waterfall Process was intended to fix.

    Answer: Big ball of mud

Question 2

[10 marks] Which of RielsHeuristics can be traced back to ideas described in JohnsonAndFoote1988? For each heuristic you identify, explain how it is based on the earlier idea.

Answer:

• Avoid concrete base classes - The top of the class hierarchy should be abstract.
• Inheritance for specialization - Subclasses should be specializations.
• Favour deep hierarchies - Class hierarchies should be deep and narrow.
• Beware type switches and Beware value switches - Eliminate case analysis.
• Beware of non-communicating methods - Separate methods that do not communicate.

Question 3

[16 marks for whole question] For each of the following maxims (a)-(d) name other maxims (as many as you can) that support it. Briefly explain each answer.

1. [4 marks] Program to the interface not the implementation

   Answer: Dependency inversion principle

2. [4 marks] Separation of concerns

   Answer: Single responsibility principle, One key abstraction

3. [4 marks] Software reuse

   Answer: Favor composition over inheritance, Reusable frameworks over reusable components

4. [4 marks] Open closed principle

   Answer: Abstraction, Make all Member Variables Private, No Global Variables

Question 4

[8 marks for whole question] Describe a design flaw in a 427 project produced by one of your classmates. Choose the most serious flaw you can find, clearly describe where it occurs (including where it can be found in the wiki) and support your argument, where possible, with maxims etc.

Answer:

Question 5

[5 marks] Imagine it was your job to interview an applicant for an OO design job. If you were allowed to ask only one question, and from the answer you had to judge whether the person was a skilled OO designer, what would you ask? Explain your reasoning.

Answer: Explain in what ways you can make an OO system more maintainable and reusable. --Elliot Fisher 08:39, 6 October 2008 (UTC)

Question 6

[35 marks for whole question] See Trains design.