1. Software Engineering, 8th edition. ------ Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models

2. Software Engineering, 8th edition. ------ Chapter 8 2 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System modelling l System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. l Different models present the system from different perspectives External perspective showing the system’s context or environment; Behavioural perspective showing the behaviour of the system; Structural perspective showing the system or data architecture.

3. Software Engineering, 8th edition. ------ Chapter 8 3 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Model types l Data processing model showing how the data is processed at different stages. l Composition model showing how entities are composed of other entities. l Architectural model showing principal sub-systems. l Classification model showing how entities have common characteristics. l Stimulus/response model showing the system’s reaction to events.

4. Software Engineering, 8th edition. ------ Chapter 8 4 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Context models l Context models are used to illustrate the operational context of a system - they show what lies outside the system boundaries. l Social and organisational concerns may affect the decision on where to position system boundaries. l Architectural models show the system and its relationship with other systems.

5. Software Engineering, 8th edition. ------ Chapter 8 5 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 The context of an ATM system

6. Software Engineering, 8th edition. ------ Chapter 8 6 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Process models l Process models show the overall process and the processes that are supported by the system. l Data flow models may be used to show the processes and the flow of information from one process to another.

7. Software Engineering, 8th edition. ------ Chapter 8 7 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Equipment procurement process

8. Software Engineering, 8th edition. ------ Chapter 8 8 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Behavioural models l Behavioural models are used to describe the overall behaviour of a system. l Two types of behavioural model are: Data processing models that show how data is processed as it moves through the system; State machine models that show the systems response to events. l These models show different perspectives so both of them are required to describe the system’s behaviour.

9. Software Engineering, 8th edition. ------ Chapter 8 9 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Data-processing models l Data flow diagrams (DFDs) may be used to model the system’s data processing. l These show the processing steps as data flows through a system. l DFDs are an intrinsic part of many analysis methods. l Simple and intuitive notation that customers can understand. l Show end-to-end processing of data.

10. Software Engineering, 8th edition. ------ Chapter 8 10 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Order processing DFD

11. Software Engineering, 8th edition. ------ Chapter 8 11 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Data flow diagrams l DFDs model the system from a functional perspective. l Tracking and documenting how the data associated with a process is helpful to develop an overall understanding of the system. l Data flow diagrams may also be used in showing the data exchange between a system and other systems in its environment.

12. Software Engineering, 8th edition. ------ Chapter 8 12 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Insulin pump DFD

13. Software Engineering, 8th edition. ------ Chapter 8 13 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 State machine models l These model the behaviour of the system in response to external and internal events. l They show the system’s responses to stimuli so are often used for modelling real-time systems. l State machine models show system states as nodes and events as arcs between these nodes. When an event occurs, the system moves from one state to another. l Statecharts are an integral part of the UML and are used to represent state machine models.

14. Software Engineering, 8th edition. ------ Chapter 8 14 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Statecharts l Allow the decomposition of a model into sub- models (see following slide). l A brief description of the actions is included following the ‘do’ in each state. l Can be complemented by tables describing the states and the stimuli.

15. Software Engineering, 8th edition. ------ Chapter 8 15 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Microwave oven model

16. Software Engineering, 8th edition. ------ Chapter 8 16 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Microwave oven state description

17. Software Engineering, 8th edition. ------ Chapter 8 17 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Microwave oven stimuli

18. Software Engineering, 8th edition. ------ Chapter 8 18 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Microwave oven operation

19. Software Engineering, 8th edition. ------ Chapter 8 19 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Semantic data models l Used to describe the logical structure of data processed by the system. l An entity-relation-attribute model sets out the entities in the system, the relationships between these entities and the entity attributes l Widely used in database design. Can readily be implemented using relational databases. l No specific notation provided in the UML but objects and associations can be used.

20. Software Engineering, 8th edition. ------ Chapter 8 20 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Library semantic model

21. Software Engineering, 8th edition. ------ Chapter 8 21 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Data dictionaries l Data dictionaries are lists of all of the names used in the system models. Descriptions of the entities, relationships and attributes are also included. l Advantages Support name management and avoid duplication; Store of organisational knowledge linking analysis, design and implementation; l Many CASE workbenches support data dictionaries.

22. Software Engineering, 8th edition. ------ Chapter 8 22 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Data dictionary entries

23. Software Engineering, 8th edition. ------ Chapter 8 23 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Object models l Object models describe the system in terms of object classes and their associations. l An object class is an abstraction over a set of objects with common attributes and the services (operations) provided by each object. l Various object models may be produced Inheritance models; Aggregation models; Interaction models.

24. Software Engineering, 8th edition. ------ Chapter 8 24 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Inheritance models l Organise the domain object classes into a hierarchy. l Classes at the top of the hierarchy reflect the common features of all classes. l Object classes inherit their attributes and services from one or more super-classes. these may then be specialised as necessary. l Class hierarchy design can be a difficult process if duplication in different branches is to be avoided.

25. Software Engineering, 8th edition. ------ Chapter 8 25 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Object models and the UML l The UML is a standard representation devised by the developers of widely used object-oriented analysis and design methods. l It has become an effective standard for object- oriented modelling. l Notation Object classes are rectangles with the name at the top, attributes in the middle section and operations in the bottom section; Relationships between object classes (known as associations) are shown as lines linking objects; Inheritance is referred to as generalisation and is shown ‘upwards’ rather than ‘downwards’ in a hierarchy.

26. Software Engineering, 8th edition. ------ Chapter 8 26 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Library class hierarchy

27. Software Engineering, 8th edition. ------ Chapter 8 27 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 User class hierarchy

28. Software Engineering, 8th edition. ------ Chapter 8 28 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Multiple inheritance l Rather than inheriting the attributes and services from a single parent class, a system which supports multiple inheritance allows object classes to inherit from several super-classes. l This can lead to semantic conflicts where attributes/services with the same name in different super-classes have different semantics. l Multiple inheritance makes class hierarchy reorganisation more complex.

29. Software Engineering, 8th edition. ------ Chapter 8 29 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Multiple inheritance

30. Software Engineering, 8th edition. ------ Chapter 8 30 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Object aggregation l An aggregation model shows how classes that are collections are composed of other classes. l Aggregation models are similar to the part-of relationship in semantic data models.

31. Software Engineering, 8th edition. ------ Chapter 8 31 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Object aggregation

32. Software Engineering, 8th edition. ------ Chapter 8 32 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Object behaviour modelling l A behavioural model shows the interactions between objects to produce some particular system behaviour that is specified as a use- case. l Sequence diagrams (or collaboration diagrams) in the UML are used to model interaction between objects.

33. Software Engineering, 8th edition. ------ Chapter 8 33 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Issue of electronic items

34. Software Engineering, 8th edition. ------ Chapter 8 34 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Structured methods l Structured methods incorporate system modelling as an inherent part of the method. l Methods define a set of models, a process for deriving these models and rules and guidelines that should apply to the models. l CASE tools support system modelling as part of a structured method.

35. Software Engineering, 8th edition. ------ Chapter 8 35 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Method weaknesses l They do not model non-functional system requirements. l They do not usually include information about whether a method is appropriate for a given problem. l The may produce too much documentation. l The system models are sometimes too detailed and difficult for users to understand.

36. Software Engineering, 8th edition. ------ Chapter 8 36 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 CASE workbenches l A coherent set of tools that is designed to support related software process activities such as analysis, design or testing. l Analysis and design workbenches support system modelling during both requirements engineering and system design. l These workbenches may support a specific design method or may provide support for a creating several different types of system model.

37. Software Engineering, 8th edition. ------ Chapter 8 37 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 An analysis and design workbench

38. Software Engineering, 8th edition. ------ Chapter 8 38 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 Analysis workbench components l Diagram editors l Model analysis and checking tools l Repository and associated query language l Data dictionary l Report definition and generation tools l Forms definition tools l Import/export translators l Code generation tools