System Modeling

Chapter 5 System modeling 1

Topics covered

 Context models
 Process models
 Interaction models
 Structural models

Chapter 5 System modeling 2

System modeling

 System modeling is the process of developing abstract

models of a system, with each model presenting a
different view or perspective of that system.
 System modeling has now come to mean representing a
system using some kind of graphical notation, which is
now almost always based on notations in the Unified
Modeling Language (UML).
 System modelling helps the analyst to understand the
functionality and organization of the system and models
are used to communicate with customers.

Chapter 5 System modeling 3

Existing and planned system models

 Models of the existing system can help clarify what the

existing system does and can be used as a basis for
discussing its strengths and weaknesses. These then can
lead to requirements for the new system.
 Models of the new system can help explain the proposed
system to stakeholders. Engineers use these models to
discuss design proposals and to document the system for
implementation.
 In a model-driven engineering process, it is possible to
generate a complete or partial system implementation from
the system model.

Chapter 5 System modeling 4

System perspectives

 An external perspective, where you model the context or

environment of the system.
 An interaction perspective, where you model the
interactions between a system and its environment, or
between the components of a system.
 A structural perspective, where you model the
organization of a system or the structure of the data that
is processed by the system.
 A behavioral perspective, where you model the dynamic
behavior of the system and how it responds to events.

Chapter 5 System modeling 5

UML diagram types

 Activity diagrams, which show the activities involved in a

process or in data processing .
 Use case diagrams, which show the interactions
between a system and its environment.
 Sequence diagrams, which show interactions between
actors and the system and between system components.
 Class diagrams, which show the object classes in the
system and the associations between these classes.
 State diagrams, which show how the system reacts to
internal and external events.

Chapter 5 System modeling 6

Use of graphical models

 As a means of facilitating discussion about an existing or

proposed system
▪ Incomplete and incorrect models are OK as their role is to
support discussion.
 As a way of documenting an existing system
▪ Models should be an accurate representation of the system but
need not be complete.
 As a detailed system description that can be used to
generate a system implementation
▪ Models have to be both correct and complete.

Chapter 5 System modeling 7

Context models

 Context models are used to illustrate the operational

context of a system - they show what lies outside the
system boundaries.
 Social and organizational concerns may affect the
decision on where to position system boundaries.
 Architectural models show the system and its
relationship with other systems.

Chapter 5 System modeling 8

The context of the MHC-PMS

Chapter 5 System modeling 9

Process perspective

 Context models simply show the other systems in the

environment, not how the system being developed is
used in that environment
 Process models reveal how the system being developed
is used in broader business processes
 UML activity diagrams may be used to define business
process models

Chapter 5 System modeling 10

Process model of involuntary detention

Chapter 5 System modeling 11

Interaction models

 Modeling user interaction is important as it helps to

identify user requirements
 Modeling system-to-system interaction highlights the
communication problems that may arise
 Modeling component interaction helps us understand if a
proposed system structure is likely to deliver the required
system performance and dependability
 Use case diagrams and sequence diagrams may be
used for interaction modeling

Chapter 5 System modeling 12

Use case modeling

 Use cases were developed originally to support

requirements elicitation and now are incorporated into
the UML.
 Each use case represents a discrete task that involves
external interaction with a system.
 Actors in a use case may be people, time, or other
systems.

Chapter 5 System modeling 13

Transfer-data use case

 A use case in the MHC-PMS

Chapter 5 System modeling 14

Tabular description of the ‘Transfer data’ use-
case

MHC-PMS: Transfer data

Actors Medical receptionist, patient records system (PRS)
Description A receptionist may transfer data from the MHC-PMS to a
general patient record database that is maintained by a
health authority. The information transferred may either
be updated personal information (address, phone
number, etc.) or a summary of the patient’s diagnosis
and treatment.
Data Patient’s personal information, treatment summary
Stimulus User command issued by medical receptionist
Response Confirmation that PRS has been updated
Comments The receptionist must have appropriate security
permissions to access the patient information and the
PRS.

Chapter 5 System modeling 15

Use cases in the MHC-PMS involving the role
‘Medical Receptionist’

Chapter 5 System modeling 16

Sequence diagrams

 Sequence diagrams are part of the UML and are used to

model the interactions between the actors and the
objects within a system
 A sequence diagram shows the sequence of interactions
that take place during a particular use case or use case
instance
 The objects and actors involved are listed along the top
of the diagram, with a dotted line drawn vertically from
these
 Interactions between objects are indicated by annotated
arrows
Chapter 5 System modeling 17
Sequence diagram for View patient information

Chapter 5 System modeling 18

Sequence diagram for Transfer Data

Chapter 5 System modeling 19

Class diagrams

 Class diagrams are used when developing an object-

oriented system model to show the classes in a system
and the associations between these classes
 An object class can be thought of as a general definition
of one kind of system object
 An association is a link between classes that indicates
that there is some relationship between these classes
 When you are developing models during the early stages
of the software engineering process, objects represent
something in the real world, such as a patient, a
prescription, doctor, etc.
Chapter 5 System modeling 20
UML classes and association

Chapter 5 System modeling 21

Classes and associations in the MHC-PMS

Chapter 5 System modeling 22

The Consultation class

Chapter 5 System modeling 23