| < Day Day Up > |
|
When you have completed this chapter, you should understand:
The difference between "is-a" and "has-a" relationships and how to implement these relationships.
The difference between an abstract class and an interface.
How to use classification to "composite" an object, and why this is a bad idea.
Why "is-a" and "has-a" relationships are dependent on the problem context.
Why classification should not be used to represent the state of an object.
Why roles should not be represented using classification.
How composition and classification can be used to extend not only representation, but also behavior.
| < Day Day Up > |
|