Will DI change the way we teach OOD ?

As technologies such as Dependency Injection frameworks like Guice and Spring gain traction and become main stream practices, do we need to change the way we teach Object-Oriented Design ?

DI usage has an impact on the dependencies between classes, and how classes are instantiated and generally "wired" together. These patterns greatly facilitate unit testing of our implementations.

Current OOD material does not yet support this concept, may be we should start to think about that.

Recommended reading for AIT's OOAD bootcamp

The following is a list of recommended books for use in the OOAD bootcamp which I shall be teaching during 20 Jan 2010 - 8 Feb 2010 at AIT.
Textbook(s):

• P. Kruchten (2003), The Rational Unified Process: An Introduction, 3rd edition, Addison Wesley.
• Booch, G. et al. (2007), Object-Oriented Analysis and Design with Applications, 3rd edition, Addison Wesley.

Reference(s):

• A. Hunt, et al. (1999), The Pragmatic Programmer: From Journeyman to Master, Addison Wesley.
• E. Evans (2003), Domain-Driven Design: Tackling Complexity in the Heart of Software, Addison Wesley.
• F. Buschmann, et al. (1996), Pattern Oriented Software Architecture: A System of Patterns, Wiley.
• L. Bass, et al. (2003), Software Architecture in Practice, 2nd edition, Addison Wesley.
• J. Rumbaugh, et al. (2004), The Unified Modeling Language Reference Manual, 2nd edition, Addison Wesley.
• E. Gamma, et al. (1994), Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley.
• M. Fowler (1999), Refactoring: Improving the Design of Existing Code, Addison Wesley.
• J. Bloch (2008), Effective Java, 2nd edition, Prentice Hall.
• T. Quatrani (2002), Visual Modeling with Rational Rose 2002 and UML, 3rd edition, Addison Wesley.
• T. Quatrani et al. (2006), Visual Modeling with IBM Rational Software Architect and UML, Addison Wesley.

There may be some additional books which I shall add at a later date.