四川大学面向对象程序设计导论课件 Lecture5.pptVIP

* * Specification of multiplicity flushes out business rules and assumptions. The lower bound is critical, as the lower bound is what determines whether or not the relationship is optional (e.g., a lower bound of 0 indicates that the relationship is optional). Multiplicity is needed on both ends of a relationship, even if you can only navigate in one direction. Even though there is no need to navigate in that direction, the multiplicity still provides valuable business information. Sometimes navigation decisions are made for performance reasons, which may change over time. The multiplicity should reflect the requirements. Navigation is discussed on later slides. The use of ‘N’ instead of ‘*’ is Booch, not UML (e.g., the use of “0..N” and ‘N’ is not UML). * * * * * * * * * * * * Aggregation hierarchy of a book * Composition(合成) Models a whole/part relationship with a strong ownership; when the whole dies, the part does so as well. The whole part is responsible for creation and destruction of its parts. Stem RootSystem Plant * Specialization/Generalization 具体化/概括化 It is a “is a ” relationship For example: Client is a person. * Specialization/Generalization notation Specialization/generalization is represented in UML by adding a triangle next to the generalization class: * Specialization/Generalization (cont.) How do we structure these classes? * Specialization/Generalization (cont.) Employee and Manager are Person Manager is an Employee * Specialization/Generalization (cont.) The associate is a inheritance relationship. * Specialization/Generalization (end) A subclass inherits from its superclass: Attributes Operations Relationships. A subclass may add to its definition: Attributes Operations Relationships Redefine inherited operations * Common Class Structure Although the definition of classes and their relationships depends on the particular application, some class structures are common to many designs. These class structures are thought of as basic buil