System models

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 1

Objectives
q

To explain why the context of a system should be modelled as part of the RE process To describe behavioural modelling, data modelling and object modelling To introduce some of the notations used in the Unified Modeling Language (UML) To show how CASE workbenches support system modelling

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 2

Topics covered
q q q q q

Context models Behavioural models Data models Object models CASE workbenches

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 3

System modelling
q

System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different models present the system from different perspectives
External perspective showing the systems context or environment; Behavioural perspective showing the behaviour of the system; Structural perspective showing the system or data architecture.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 4

Model types
q

q q

Data processing model showing how the data is processed at different stages. Composition model showing how entities are composed of other entities. Architectural model showing principal sub-systems. Classification model showing how entities have common characteristics. Stimulus/response model showing the systems reaction to events.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 5

Context models
q

Context models are used to illustrate the operational context of a system - they show what lies outside the system boundaries. Social and organisational concerns may affect the decision on where to position system boundaries. Architectural models show the system and its relationship with other systems.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 6

The context of an ATM system

Sec sys Br to anch Ac acco da ta ba syste A da u Us sys Br ge anch coun syste Mai sys
Software Engineering, 7th edition. Chapter 8 Slide 7

Ian Sommerville 2004

Process models
q

Process models show the overall process and the processes that are supported by the system. Data flow models may be used to show the processes and the flow of information from one process to another.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 8

Equipment procurement process

Ian Sommerville 2004

Deli vDel enot ryc note ery Check ed vtio Equipm Specify Acce spec.er Vlida aspec. tetede Get equipme deli v Ch ery v ed specific tionite estim tesins r quir Ins e FindIns edChoo equi Spec supp Ortio der Equipme estim notif tion spec.eq Suppli Plac Supplier equi supplie da suppl ta blank baserAc OrIns der or der deta ac fChec oor ra meq de v e ed ed sign der m Eq de Eq da ta ba
Software Engineering, 7th edition. Chapter 8 Slide 9

Behavioural models
q

Behavioural models are used to describe the overall behaviour of a system. 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.

These models show different perspectives so both of them are required to describe the systems behaviour.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 10

Data-processing models
q

Data flow diagrams (DFDs) may be used to model the systems data processing. These show the processing steps as data flows through a system. DFDs are an intrinsic part of many analysis methods. Simple and intuitive notation that customers can understand. Show end-to-end processing of data.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 11

Cf e Comp Sign Sign Se d ordeta dersup orlida more orafd deril orco mb+ der orsi mno OrVOr ti derder details Compl te u dlOr bor Rb lor aorde ankfm deror or eAd m der or v der f or or der Sig m der am + de Or ders Bu file file
Order processing DFD
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 12

Data flow diagrams

q

DFDs model the system from a functional perspective. Tracking and documenting how the data associated with a process is helpful to develop an overall understanding of the system. Data flow diagrams may also be used in showing the data exchange between a system and other systems in its environment.
Software Engineering, 7th edition. Chapter 8 Slide 13

Ian Sommerville 2004

Bloo par l ame Bloodq Blood Bloo Blo senso ana ysis le v e In rti e em co Pum olrns com Insulin Iry Insu Insuli deli veq eem pump con olle
Insulin pump DFD
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 14

State machine models

q

These model the behaviour of the system in response to external and internal events. They show the systems responses to stimuli so are often used for modelling real-time systems. 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. Statecharts are an integral part of the UML and are used to represent state machine models.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 15

Statecharts
q

Allow the decomposition of a model into submodels (see following slide). A brief description of the actions is included following the do in each state. Can be complemented by tables describing the states and the stimuli.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 16

Fdo:po uF ll600 u w e pomer wll r po eset r =ll Ope Talf ti ido: Wwr do:s apoNum iting ge do:close display FSet umer timeope poStar er tove exit: HDoori wDoor eopend HalfEnab poTclose wrwDoor edo: ope Ca i r3Doo W a Halfpo eleddo po set di = do:'R 00 tim Disa b do: displa 'W aiting
Microwave oven model
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 17

Microwave oven state description

State Waiting Half power Full power Set time Disabled Enabled Operation Description The oven is waiting for input. The display shows the current time. The oven power is set to 300 watts. The display shows H power alf . The oven power is set to 600 watts. The display shows F power ull . The cooking time is s et to the user input value. The display shows the cooking time s selected and is updated as the time is set. Oven operation is disabled for safety. Interior oven light is on. Display shows N ot ready . Oven operation is enabled. Interior oven light is off. Display shows Ready to cook . Oven in operation. Interior oven light is on. Display shows the timer countdown. On completion of cooking, the buzzer is sounded for 5 s econds. Oven light is on. Display shows Cooking complete w buzzer is sounding. hile

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 18

Microwave oven stimuli

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 19

Microwave oven operation

Ope T ime Chec Coo OK do:me chec do: run statu gen TEmit ufault rnta T i fault Don Alarm do: buz do:Ca displa for even Doo Disab W aiti
Software Engineering, 7th edition. Chapter 8 Slide 20

Ian Sommerville 2004

Semantic data models

q

Used to describe the logical structure of data processed by the system. An entity-relation-attribute model sets out the entities in the system, the relationships between these entities and the entity attributes Widely used in database design. Can readily be implemented using relational databases. No specific notation provided in the UML but objects and associations can be used.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 21

Library semantic model

Sour Article publis title titlefile m1 nin publ authors pdfissue fee-pa feedate page 1Copyr 1 nu delivers 1in pay 1 r nhas-lin Cou Order Agenc 1copy 1 order name total tax addres datestatu tax n places 1 Buyer i name address e-mail billing
Software Engineering, 7th edition. Chapter 8 Slide 22

Ian Sommerville 2004

Data dictionaries
q

Data dictionaries are lists of all of the names used in the system models. Descriptions of the entities, relationships and attributes are also included. Advantages
Support name management and avoid duplication; Store of organisational knowledge linking analysis, design and implementation;

Many CASE workbenches support data dictionaries.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 23

Data dictionary entries

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 24

Object models
q

Object models describe the system in terms of object classes and their associations. An object class is an abstraction over a set of objects with common attributes and the services (operations) provided by each object. Various object models may be produced
Inheritance models; Aggregation models; Interaction models.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 25

Object models
q

Natural ways of reflecting the real-world entities manipulated by the system More abstract entities are more difficult to model using this approach Object class identification is recognised as a difficult process requiring a deep understanding of the application domain Object classes reflecting domain entities are reusable across systems

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 26

Inheritance models
q q

Organise the domain object classes into a hierarchy. Classes at the top of the hierarchy reflect the common features of all classes. Object classes inherit their attributes and services from one or more super-classes. these may then be specialised as necessary. Class hierarchy design can be a difficult process if duplication in different branches is to be avoided.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 27

Object models and the UML

q

The UML is a standard representation devised by the developers of widely used object-oriented analysis and design methods. It has become an effective standard for objectoriented modelling. 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.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 28

Library class hierarchy

Libr it ary n Ca() talo gue umbe Acqui te Cost ( Tpe ycopi Sta tus Numb Acqui eturn Ca talo gue Dispo Issue RT cor eie Pub lished R ded TMaCom ilisher tle tle Med Bookrsi gazine Film pr o g r a ector ABarm uthorof Y Dir m eDa V e teda eleas rtf Edition Issue Pla Pub or tion te Ilica S Distri N utor
Software Engineering, 7th edition. Chapter 8 Slide 29

Ian Sommerville 2004

Libr u ary Name Ad dr ess Phon Rion eg istr a t ister De-r eg r Rader e Item Bor o w e Af Staf filia Stu tion Max f Ma Depa tmen Hom dr es
User class hierarchy
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 30

Multiple inheritance
q

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. This can lead to semantic conflicts where attributes/services with the same name in different super-classes have different semantics. Multiple inheritance makes class hierarchy reorganisation more complex.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 31

Boo Vo ABte utho Sp er Editi Du aio tc Pub lica tion te R e din I S N Tlki a es #T p
Multiple inheritance
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 32

Object aggregation
q

An aggregation model shows how classes that are collections are composed of other classes. Aggregation models are similar to the part-of relationship in semantic data models.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 33

Stud Cour Num Year Instr Lec eipe Ve OH.de PTslid Assign not Cr eT edits Slide p xa t Exercis Solut T e x #Pr obt lems Descrip Diag rams
Object aggregation
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 34

Object behaviour modelling

q

A behavioural model shows the interactions between objects to produce some particular system behaviour that is specified as a usecase. Sequence diagrams (or collaboration diagrams) in the UML are used to model interaction between objects.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 35

Lib Ecat: :Libr Ne Catal :Librar Looku Displa Issue Issue Accep Com Deliv
Issue of electronic items
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 8 Slide 36

Structured methods
q

Structured methods incorporate system modelling as an inherent part of the method. Methods define a set of models, a process for deriving these models and rules and guidelines that should apply to the models. CASE tools support system modelling as part of a structured method.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 37

Method weaknesses
q

q q

They do not model non-functional system requirements. They do not usually include information about whether a method is appropriate for a given problem. The may produce too much documentation. The system models are sometimes too detailed and difficult for users to understand.

Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 8

Slide 38

CASE workbenches
q

A coherent set of tools that is designed to support related software process activities such as analysis, design or testing. Analysis and design workbenches support system modelling during both requirements engineering and system design. These workbenches may support a specific design method or may provide support for a creating several different types of system model.
Software Engineering, 7th edition. Chapter 8 Slide 39

Ian Sommerville 2004

An analysis and design workbench

Stru edp R e t Da mm taalaio dia g ge r fac a Qu dictio tool Cen Code inft ort/e tion lan ge gener arma torpo rysis e Im fac F Desi o and msfac crtool ea xp tion tools
Software Engineering, 7th edition. Chapter 8 Slide 40

Ian Sommerville 2004

Analysis workbench components

q q q q q q q q

Diagram editors Model analysis and checking tools Repository and associated query language Data dictionary Report definition and generation tools Forms definition tools Import/export translators Code generation tools
Software Engineering, 7th edition. Chapter 8 Slide 41

Ian Sommerville 2004

Key points
q

A model is an abstract system view. Complementary types of model provide different system information. Context models show the position of a system in its environment with other systems and processes. Data flow models may be used to model the data processing in a system. State machine models model the systems behaviour in response to internal or external events
Software Engineering, 7th edition. Chapter 8 Slide 42

Ian Sommerville 2004

Key points
q

Semantic data models describe the logical structure of data which is imported to or exported by the systems. Object models describe logical system entities, their classification and aggregation. Sequence models show the interactions between actors and the system objects that they use. Structured methods provide a framework for developing system models.
Software Engineering, 7th edition. Chapter 8 Slide 43

Ian Sommerville 2004