面向对象的Java与UML课件Chapter-08The-primary-models-output

Figure 8.1 The primary models output by business modelling and their input into other software development processesSoftware Development with UML Copyright Ken Lunn 2003Figure 8.2 The stages of business modellingSoftware Development with UML Copyright Ken Lunn 2003Figure 8.3 A process map showing all levels of the processes defined so farSoftware Development with UML Copyright Ken Lunn 2003The primary path in a bank for someone cashing a cheque would be:1.Customer presents cheque2.Clerk checks signature3.Clerk checks details4.Clerk checks account balance5.Clerk counts money6.Clerk files chequeSoftware Development with UML Copyright Ken Lunn 2003Alternative way of making a cup of tea1.Fill kettle2.Boil kettle3.Put tea in teapot4.Pour boiling water5.Wait for two minutes6.Pour tea into cup7.Add milk and sugarSoftware Development with UML Copyright Ken Lunn 2003Figure 8.4 A process analysis using primary and alternative pathsSoftware Development with UML Copyright Ken Lunn 2003Figure 8.5 The UML notation for an activity to print an invoiceSoftware Development with UML Copyright Ken Lunn 2003Figure 8.6 A simple transition from one activity to anotherSoftware Development with UML Copyright Ken Lunn 2003Figure 8.7 A transition triggered by an event interrupting an activitySoftware Development with UML Copyright Ken Lunn 2003Figure 8.8 A state in an activity diagramSoftware Development with UML Copyright Ken Lunn 2003Figure 8.9 A simple activity diagram showing the process of obtaining paymentSoftware Development with UML Copyright Ken Lunn 2003Figure 8.10 An activity diagram with swimlanes indicating which business areas carryout the activities.Software Development with UML Copyright Ken Lunn 2003Figure 8.11 A simple example of a decisionSoftware Development with UML Copyright Ken Lunn 2003Figure 8.12 The UML notation for an object or classSoftware Development with UML Copyright Ken Lunn 2003Figure 8.13 Showing relationships between objects in UMLSoftware Development with UML Copyright Ken Lunn 2003Figure 8.14 Objects on activity diagramsSoftware Development with UML Copyright Ken Lunn 2003Figure 8.15 A simple statechart model for an orderSoftware Development with UML Copyright Ken Lunn 2003Figure 8.16 A statechart model for an accountSoftware Development with UML Copyright Ken Lunn 2003Figure 8.17 The business process map for ICANDO chemicals,focusing on the aspects relevant to the new sales order processing systemSoftware Development with UML Copyright Ken Lunn 2003Figure 8.18 Workflow for the telephone order processSoftware Development with UML Copyright Ken Lunn 2003Figure 8.19 Workflow for adjusting delivery volumesSoftware Development with UML Copyright Ken Lunn 2003Figure 8.20 Workflow for electronic orderingSoftware Development with UML Copyright Ken Lunn 2003Figure 8.21 Business object model for ICANDO Chemical orderingSoftware Development with UML Copyright Ken Lunn 2003Figure 8.22 ICANDO site safety process mapSoftware Development with UML Copyright Ken Lunn 2003Figure 8.23 Workflow for checking safety distancesSoftware Development with UML Copyright Ken Lunn 2003Figure 8.24 Business object model for ICANDO site safetySoftware Development with UML Copyright Ken Lunn 2003Figure 8.25 ICANDO customer loyalty process mapSoftware Development with UML Copyright Ken Lunn 2003Figure 8.26 Workflow for registration with the ICANDO retail promotion schemeSoftware Development with UML Copyright Ken Lunn 2003Figure 8.27 Workflow for customer ordering goods from ICANDO retail promotionsSoftware Development with UML Copyright Ken Lunn 2003Figure 8.28 Business object model for ICANDO retail promotionsSoftware Development with UML Copyright Ken Lunn 2003