1、Software Development with UML Copyright Ken Lunn 2003Figure 11.1 A customer represented in UMLSoftware Development with UML Copyright Ken Lunn 2003Figure 11.2 The UML representation of the Red Riding Hood objectSoftware Development with UML Copyright Ken Lunn 2003Figure 11.3 All requests on an objec

2、t are controlled via the operationsSoftware Development with UML Copyright Ken Lunn 2003Figure 11.4 Illustration of polymorphism two objects with operations with the same names but different meaningsSoftware Development with UML Copyright Ken Lunn 2003Figure 11.5 Computer systems are networks of coo

3、perating objectsSoftware Development with UML Copyright Ken Lunn 2003Figure 11.6 A one-to-one relationshipSoftware Development with UML Copyright Ken Lunn 2003Figure 11.7 A unidirectional one-to-one relationshipSoftware Development with UML Copyright Ken Lunn 2003Table 11.1 The different multiplicit

4、y notationsSoftware Development with UML Copyright Ken Lunn 2003Figure 11.8 A one-to-many relationshipSoftware Development with UML Copyright Ken Lunn 2003Figure 11.9 A many-to-many relationshipSoftware Development with UML Copyright Ken Lunn 2003Figure 11.10 Removing a many-to-many relationship wit

5、h an intermediate objectSoftware Development with UML Copyright Ken Lunn 2003Figure 11.11 Two fairy story objects sharing common operationsSoftware Development with UML Copyright Ken Lunn 2003Figure 11.12 An example of inheritanceSoftware Development with UML Copyright Ken Lunn 2003Figure 11.13 Inhe

6、ritance from a common objectSoftware Development with UML Copyright Ken Lunn 2003Figure 11.14 Inheritance through multiple levelsSoftware Development with UML Copyright Ken Lunn 2003Figure 11.15 A simple example of reuseSoftware Development with UML Copyright Ken Lunn 2003Figure 11.16 A simple examp

7、le of aggregationSoftware Development with UML Copyright Ken Lunn 2003Figure 11.17 A class diagram for the Red Riding Hood storySoftware Development with UML Copyright Ken Lunn 2003Figure 11.18 A simple class diagram to describe patient referralsSoftware Development with UML Copyright Ken Lunn 2003F

8、igure 11.19 A class diagram for a lift controller systemSoftware Development with UML Copyright Ken Lunn 2003Figure 11.20 A class diagram for a Web shopping systemSoftware Development with UML Copyright Ken Lunn 2003Figure 11.21 Noun phrases highlighted as candidate objects for the ICANDO site safet

9、y systemSoftware Development with UML Copyright Ken Lunn 2003Table 11.2 Selection of objects from noun listSoftware Development with UML Copyright Ken Lunn 2003Table 11.2 Selection of objects from noun list (continued)Software Development with UML Copyright Ken Lunn 2003Table 11.2 Selection of objec

10、ts from noun list (continued)Software Development with UML Copyright Ken Lunn 2003Figure 11.22 Inheritance hierarchy for facilities on a siteSoftware Development with UML Copyright Ken Lunn 2003Figure 11.23 Representing a site as a collection of facilitiesSoftware Development with UML Copyright Ken Lunn 2003Figure 11.24 The guidelines and relationships in the site safety systemSoftware Development with UML Copyright Ken Lunn 2003Figure 11.25 The audit report and infringements