面向对象的Java与UML课件Chapter-13The-interaction-of-use-ca.ppt

1、Software Development with UML Copyright Ken Lunn 2003Figure 13.1 The interaction of use cases through objectsSoftware Development with UML Copyright Ken Lunn 2003Figure 13.2 The primary inputs and outputs of designSoftware Development with UML Copyright Ken Lunn 2003Table 13.1 Visibility of attribut

2、esThe full syntax for an attribute definition in UML is:visibility namemultiplicity:type-expression=initial-valueSoftware Development with UML Copyright Ken Lunn 2003Table 13.2 Sample attribute definitionsSoftware Development with UML Copyright Ken Lunn 2003Operation SyntaxThe general syntax is:visi

3、bility name(parameter-list):return-typeparameter-list is a comma-separated list of parameters with the syntaxkind name:type-expression=default-valuetype-expression is a language-specific definition of the type of the parameter,and default-value is a language-specific expression to set the value of t

4、he parameter if it is not supplied.Software Development with UML Copyright Ken Lunn 2003Table 13.3 Visibility rules for operationsSoftware Development with UML Copyright Ken Lunn 2003Table 13.4 Parameter kinds for operation specificationsSoftware Development with UML Copyright Ken Lunn 2003Table 13.

5、5 Examples of operation signaturesSoftware Development with UML Copyright Ken Lunn 2003Figure 13.3 Associations with adornmentsSoftware Development with UML Copyright Ken Lunn 2003Figure 13.4 An example of two associations between the same pair of classesSoftware Development with UML Copyright Ken L

6、unn 2003Figure 13.5 Example of multiple associations between objects in the same classSoftware Development with UML Copyright Ken Lunn 2003Figure 13.6 An object lifelineSoftware Development with UML Copyright Ken Lunn 2003Figure 13.7 Locus of control bar on a lifelineSoftware Development with UML Co

7、pyright Ken Lunn 2003Figure 13.8 Initiating locus of controlSoftware Development with UML Copyright Ken Lunn 2003Figure 13.9 Showing an object creating another objectSoftware Development with UML Copyright Ken Lunn 2003Software Development with UML Copyright Ken Lunn 2003Figure 13.11 An object calli

8、ng itselfSoftware Development with UML Copyright Ken Lunn 2003Figure 13.12 Iteration on a sequence diagramSoftware Development with UML Copyright Ken Lunn 2003Table 13.6 Message flow notation for sequence diagramsSoftware Development with UML Copyright Ken Lunn 2003Figure 13.13 Standard design patte

9、rn for interactive systemsSoftware Development with UML Copyright Ken Lunn 2003Figure 13.14 A simpler pattern for simple interactive systemsSoftware Development with UML Copyright Ken Lunn 2003Figure 13.15 A pattern that shows the use of factories to instantiate objects that have been stored in a da

10、tabaseSoftware Development with UML Copyright Ken Lunn 2003Figure 13.16 A collaboration diagramSoftware Development with UML Copyright Ken Lunn 2003Figure 13.17 Pseudo-code to describe invoice printingSoftware Development with UML Copyright Ken Lunn 2003Figure 13.18 An activity diagram to specify op

11、eration logicSoftware Development with UML Copyright Ken Lunn 2003Figure 13.19 The relationship between screens and use casesSoftware Development with UML Copyright Ken Lunn 2003Figure 13.20 Class diagram used to show the layout of a user interfaceSoftware Development with UML Copyright Ken Lunn 200

12、3Figure 13.21 UML notation for a componentSoftware Development with UML Copyright Ken Lunn 2003Figure 13.22 UML notation for an interface classSoftware Development with UML Copyright Ken Lunn 2003Figure 13.23 An interface class linked to a component,publishing the services of the componentSoftware D

13、evelopment with UML Copyright Ken Lunn 2003Figure 13.24 The organization of components to define the overall structureof the applicationSoftware Development with UML Copyright Ken Lunn 2003Figure 13.25 The workflow for component-based developmentSoftware Development with UML Copyright Ken Lunn 2003F

14、igure 13.26 Use of a frameworkSoftware Development with UML Copyright Ken Lunn 2003Figure 13.27 A simple pattern to show the typical structure of an orderSoftware Development with UML Copyright Ken Lunn 2003Figure 13.28 Layout of the welcome screen for the Validate Customer use caseSoftware Developm

15、ent with UML Copyright Ken Lunn 2003Figure 13.29 A UML representation of the welcome screenSoftware Development with UML Copyright Ken Lunn 2003Figure 13.30 The addition of a factory object to create an object from the databaseSoftware Development with UML Copyright Ken Lunn 2003Figure 13.31 Class d

16、efinition for the Validation control classSoftware Development with UML Copyright Ken Lunn 2003Figure 13.32 The DataFactory class definition.Software Development with UML Copyright Ken Lunn 2003Figure 13.33 Class definition for a customer objectSoftware Development with UML Copyright Ken Lunn 2003Fi

17、gure 13.34 User interface structure for telephone orderingSoftware Development with UML Copyright Ken Lunn 2003Figure 13.35 First definition of the edit control objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.36 A class to represent coordinatesSoftware Development with UML Copyr

18、ight Ken Lunn 2003Figure 13.37 The revised Site classSoftware Development with UML Copyright Ken Lunn 2003Figure 13.38 The revised edit control objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.39 The revised site classSoftware Development with UML Copyright Ken Lunn 2003Figure 13

19、.40 The revised standard objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.41 Revised guidelineSoftware Development with UML Copyright Ken Lunn 2003Figure 13.42 StockControl objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.43 A Stock objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.44 A reservation objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.45 The revised StockControl objectSoftware Development with UML Copyright Ken Lunn 2003Figure 13.46 The class diagram for the orders