Quick questions on Dependency Inversion reading

Being able to answer these questions does not prove that you remember the reading perfectly! But at least, not being able to answer them does suggest you should reread it.

There's no automated checking of these: just see if you could answer each question. If not, revisit the reading.

Q1 According to the author, three characteristics of bad design are fragility, rigidity and immobility. What does each of these mean, in the context of software design? How are they related?

Q2 What is the Dependency Inversion Principle?

Q3 Explain the DIP with the aid of a simple example. In what sense have dependencies been inverted? In your example, how does this inversion help (in principle!) to prevent the software becoming fragile, rigid and immobile?


This page is maintained by Perdita Stevens (perdita@inf.ed.ac.uk)


Home : Teaching : Courses : Seoc : 2014_2015 

Informatics Forum, 10 Crichton Street, Edinburgh, EH8 9AB, Scotland, UK
Tel: +44 131 651 5661, Fax: +44 131 651 1426, E-mail: school-office@inf.ed.ac.uk
Please contact our webadmin with any comments or corrections. Logging and Cookies
Unless explicitly stated otherwise, all material is copyright © The University of Edinburgh