1. 03/12/2001 © Bennett, McRobb and Farmer 2002 1 Modelling Concepts Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design Using UML, (2 nd Edition), McGraw Hill, 2002.

2. © Bennett, McRobb and Farmer 2002 2 In This Lecture You Will Learn: n What is meant by a model n The distinction between a model and a diagram n The UML concept of a model

3. © Bennett, McRobb and Farmer 2002 3 What is a Model n Like a map, a model represents something else n A useful model has the right level of detail and represents only what is important for the task in hand n Many things can be modelled: bridges, traffic flow, buildings, economic policy

4. © Bennett, McRobb and Farmer 2002 4 Why Use a Model? n A model is quicker and easier to build n A model can be used in a simulation n A model can evolve as we learn n We can choose which details to include in a model n A model can represent real or imaginary things from any domain

5. © Bennett, McRobb and Farmer 2002 5 Modelling Organizations Organizations are human activity systems. n The situation is complex n Stakeholders have different views n We have to model requirements accurately, completely and unambiguously n The model must not prejudge the solution

6. © Bennett, McRobb and Farmer 2002 6 What is a Diagram? n Abstract shapes are used to represent things or actions from the real world n Diagrams follow rules or standards n The standards make sure that different people will interpret the diagram in the same way 40°

7. © Bennett, McRobb and Farmer 2002 7 An Example of a Diagram n An activity diagram of the tasks involved in producing a book. Write Chapter Review Chapter AuthorPrinterTypesetterReviewer Typeset Book Correct Proofs Reset Book Print Book [book complete] [book not complete] Revise Chapter

8. © Bennett, McRobb and Farmer 2002 8 Write Chapter Review Chapter AuthorPrinterTypesetterReviewer Typeset Book Correct Proofs Reset Book Print Book [book complete] [book not complete] Revise Chapter Hiding Detail Plan Chapter Produce First Draft Revise Draft [satisfied] [not satisfied] Add Exercises Add References to Bibliography Write Chapter

9. © Bennett, McRobb and Farmer 2002 9 Diagrams in UML n UML diagrams consist of: –icons –two-dimensional symbols –paths –Strings n UML diagrams are defined in the UML specification. Plan Chapter Produce First Draft Revise Draft [satisfied] [not satisfied] Add Exercises Add References to Bibliography Write Chapter

10. © Bennett, McRobb and Farmer 2002 10 Diagrams vs Models n A diagram illustrates some aspect of a system. n A model provides a complete view of a system at a particular stage and from a particular perspective. n A model may consist of a single diagram, but most consist of many related diagrams and supporting data and documentation.

11. © Bennett, McRobb and Farmer 2002 11 Examples of Models n Requirements Model –complete view of requirements –may include other models, such as a Use Case Model –includes textual description as well as sets of diagrams

12. © Bennett, McRobb and Farmer 2002 12 Examples of Models n Behavioural Model –shows how the system responds to events in the outside world and the passage of time –an initial model may just use Collaboration Diagrams –a later model will include Sequence Diagrams and Statecharts

13. © Bennett, McRobb and Farmer 2002 13 Models in UML n A system is the overall thing that is being modelled n A sub-system is a part of a system consisting of related elements n A model is an abstraction of a system or sub-system from a particular perspective n A model is complete and consistent at the chosen level of abstraction

14. © Bennett, McRobb and Farmer 2002 14 Models in UML n Different models present different views of the system, for example: –use case view –design view –process view –implementation view –deployment view (Booch et al., 1999)

15. © Bennett, McRobb and Farmer 2002 15 Packages, Sub-systems and Models n UML has notation for showing sub- systems and models, and also for packages, which are a mechanism for organising models (e.g. in CASE tools) Use CasesUse Case Model Campaign Management PackageModelSub-system

16. © Bennett, McRobb and Farmer 2002 16 Developing Models n During the life of a project using an iterative life cycle, models change along the dimensions of: –abstraction—they become more concrete –formality—they become more formally specified –level of detail—additional detail is added as understanding improves

17. © Bennett, McRobb and Farmer 2002 17 Development of the Use Case Model Iteration 1 Obvious use cases. Simple use case descriptions. Iteration 2 Additional use cases. Simple use case descriptions. Prototypes. Iteration 3 Structured use cases. Structured use case descriptions. Prototypes. Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 2002 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 1997 Spring Jewellery Campaign 2001 Spring Jewellery Campaign 2002 Summer Collection 1998 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client: Yellow Partridge Spring Jewellery Campaign 2002 OKQuit Campaign: Campaign Selection Holborn Motors Lynch Properties Yellow Partridge Zeta Systems Client:

18. © Bennett, McRobb and Farmer 2002 18 Summary In this lecture you have learned about: n What is meant by a model n The distinction between a model and a diagram n The UML concept of a model

19. © Bennett, McRobb and Farmer 2002 19 References n Booch, Rumbaugh and Jacobson (1999) (For full bibliographic details, see Bennett, McRobb and Farmer)