Object-Oriented Design Lectures

Lectures

Intro
Software Process
What does it mean to be Object-Oriented ? (Page-Jones Chapter 1. p. 3 - 47)
UML: Classes, Attributes and Methods (Page-Jones Chapter 3. p. 85 - 101)
UML: Class Diagrams (Page-Jones Chapter 4. p. 107 - 130)
UML: Object-Interaction Diagrams (Page-Jones Chapter 5. p. 137 - 160)
UML: Finite State Automata
UML: State Diagrams (class transparencies (pdf) based on
David Harel. On Visual Formalisms. Communications of the ACM, 31(5):514-530. May 1988. read pages 514 - 523
(only accessible from within the mcgill.ca domain),
Page-Jones Chapter 6. p. 164 - 181 is optional reading)
The drawingTool example from class.

Midterm

UML: Architecture Diagrams, Package Diagrams (Page-Jones Chapter 7. p. 188 - 196).
Criteria for good OO design: Encapsulation and Connascence. (Page-Jones Chapter 8. p. 207 - 229).
Criteria for good OO design: Domains, Encumbrance and Cohesion. (Page-Jones Chapter 9. p. 233 - 253).
Design Patterns: Observer. (GoF p. 293 - 300).
Design Patterns: Composite. (GoF p. 163 - 169).
Design Patterns: Command. (GoF p. 233 - 238).
Design Patterns: Visitor. (GoF p. 331 - 336).
State-space and Behaviour. (Page-Jones Chapter 10. p. 259 - 272).
Type conformance and closed behaviour. (Page-Jones Chapter 11. p. 278 - 291).

Final

Not exam material, but very informative: Chapter 2 "A Case Study: Designing a Document Editor" of the GoF book.