Chap 2Intro to UML概要1.pptVIP

Don’t cover the details of the graphic on this slide. The semantics of each of the relationships will be discussed later. It is not necessary to discuss any of these diagrams in detail. The points to make are: 1. More than one diagram is necessary to represent software 2. The UML has made a tremendous contribution in giving us a common visual language to express these models. All of these diagrams can be created using Rational Rose with the exception of the activity diagrams. Use this slide to review the key concepts and UML notation described earlier in this module. For example, ask the students the following: What are the classes in this diagram? What relationship exists between Salesperson and Sale? What relationship exists between Corporate and Customer? How would you interpret the diagram? The new Plane class, explosion around the Plane class, and the associated text only appear after a mouse click. The use of object-oriented analysis and design techniques severely reduces the impact of requirements changes on the overall design. For example, given the above object model, what would need to change in the model to support the addition of another type of shipping vehicle, say an airplane? Answer: Just add a subclass to the Vehicle class to represent the new shipping vehicle. Also, if the requirements for any of the shipping vehicles change, you only need to make the change in one place in the model -- the class representing the shipping vehicle. The requirements changes are simplified by encapsulation, generalization, and polymorphism. The Sale class is only aware that there is a shipping mechanism, it is not concerned with the type of shipping mechanism. Stereotypes allow you to extend the basic UML notation. By allowing you to define a new modeling element based on an existing modeling element. The new element may contain additional semantics, but still applies in all instances where the original element is used. In this way, the number of unique U