System Modeling

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 of

the system and models are used to communicate with customers.
Chapter 5 System modeling
 UML (Unified Modeling Language)
• UML is used for visual representation of system.

• UML is a way of visualizing a software program using a collection of

diagrams.

• UML can be used for modeling a system independent of a platform

language.

• UML is a graphical language for visualizing, specifying, constructing, and

documenting information about software systems
UML Diagram Types
Structural and Behavioral UML
Structural diagrams
• Structure diagrams show the static structure of the elements in your system.
• It shows the things in the system - classes, objects, packages or modules,
physical nodes, components and interfaces.
• They also show the relationships between these things
Behavior diagrams
• Behavior diagrams depict the dynamic behavior of the elements in your
system.
It shows how the system behaves and interacts with itself and other entities
(users, other systems).
• They show how data moves through the system, how objects communicate
with each other, how the passage of time affects the system, or what events
cause the system to change internal states.
Class Diagram

Class name student student student

name name : string +name : string

Class attributes roll no. : int - roll no. : int
roll no.

Class operations Create record () Create record (): int #Create record (): int

Visibility notations: + , - , #
+ = public class
- = private class
# = protected
 Class Diagram (cont..)

• Association
1 1* student
Teacher

• Dependency
consumer supplier
• Aggregation
(no strong dependency)

library books
• Composition
A B

• Generalization person

student teacher
Class diagram Example
Class diagram Example
Class diagram Example
Class diagram Example
Class diagram Example
Class diagram Example
Use Case Diagram
• A use case describes how a user uses a system to accomplish a
particular goal.

• Use cases represent only the functional requirements of a system.

• A use case is a useful technique for identifying, clarifying, and

organizing system requirements.

• use cases help ensure that the correct system is developed by capturing
the requirements from the user's point of view.
Use Case diagram Components
1. Actor: roleplay (it may be system or group of people

2. Use case: capability of system (function)

3. Connector: interaction

4. Generalization

5. Stereotype or relationship
Use case diagram relationships
1. <include>
• "Include" is used to extend the base use case and it is a must
condition i.e. included use case run must run successfully to complete
base use.

2. <extend>
• “Exclude" is optional use case which extends the base use case, base
use case can run successfully even without invoking/calling the
extending use case.
Use Case Diagram Example
Use Case Diagram Example
Use Case Diagram Example
Sequence Diagram
• In software engineering, a system sequence diagram (SSD) is a sequence
diagram that shows,
• particular scenario of a use case, the events that external actors generate, their
order, and possible inter-system events.

• The components of sequence diagram include:

i. Object
ii. Life line
iii. Actor
iv. activation bar
v. Message (synchronous, asynchronous, return, create, delete, self)
Sequence Diagram
Sequence Diagram
Activity Diagram
• Activity diagram is another important behavioral diagram in UML
diagram.

• It describe dynamic aspects of the system.

• Activity diagram is essentially an advanced version of flow chart that

modeling the flow from one activity to another activity.
Activity Diagram
Activity Diagram
MCQ’s
What is a sequence diagram?

a) A diagram that shows interacting individuals along the top of the

diagram and messages passed among them arranged in temporal order down
the page

b) A diagram that shows messages superimposed on a diagram depicting

collaborating individuals and the links among them

c) A diagram that shows the change of an individual’s state over time

d) All of the mentioned

MCQ

What is a lifeline?

a) It is a frame consisting of a rectangle with a pentagon in its upper left- hand

corner

b) It is a rectangle containing an identifier with a dashed line extending below

the rectangle

c) It is a name compartment; the interaction is represented inside the rectangle

d) None of the mentioned

MCQ

What does a message mean?

a) It Passes all communications from one object to another and are

represented by message arrows in sequence diagrams

b) The message goes from the sending object’s lifeline to the receiving
object’s lifeline

c) It is a rectangle containing an identifier with a dashed line extending

below the rectangle

d) All of the mentioned

MCQ

What are the three different types of message arrows?

a) Synchronous, asynchronous, asynchronous with instance creation

b) Self, Multiplied, instance generator
c) Synchronous, Asynchronous, synchronous with instance creation
d) None of the mentioned
MCQ

• Which of these are true with respect to the message arrows?

a) The synchronous message arrow is used when a sending individual

continues execution after sending the message

b) The asynchronous message arrow is used when a sending individual

suspends execution after sending the message

c) The dashed arrow is used either to show the return of control from a
synchronous message or to create a new entity

d) All of the mentioned

Context Models
• 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.

• The Unified Modeling Language as used in systems engineering defines

a context model
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
modelling.
 Structural models
• Structural models of software display the organization of a system in
terms of the components that make up that system and their
relationships.

• Structural models may be static models, which show the structure of the
system design, or dynamic models, which show the organization of the
system when it is executing.

• Class diagram is an example of structural model.

Behavioral models
• Behavioral models are models of the dynamic behavior of a system as
it is executing.

• They show what happens or what is supposed to happen when a

system responds to a stimulus (event occur) from its environment.

• You can think of these stimuli as being of two types:

• Data Some data arrives that has to be processed by the system. (activity
diagram)
• Events Some event happens that triggers system processing. Events may have
associated data, although this is not always the case. (state diagram)
State diagram of a microwave
oven
States and stimuli for the
microwave oven (a)
State Description
Waiting The oven is waiting for input. The display shows the current time.
Half power The oven power is set to 300 watts. The display shows ‘Half power’.
Full power The oven power is set to 600 watts. The display shows ‘Full power’.
Set time The cooking time is set to the user’s input value. The display shows
the cooking time selected and is updated as the time is set.
Disabled Oven operation is disabled for safety. Interior oven light is on.
Display shows ‘Not ready’.
Enabled Oven operation is enabled. Interior oven light is off. Display shows
‘Ready to cook’.
Operation Oven in operation. Interior oven light is on. Display shows the timer
countdown. On completion of cooking, the buzzer is sounded for five
seconds. Oven light is on. Display shows ‘Cooking complete’ while
buzzer is sounding.
States and stimuli for the microwave
oven (b)
Stimulus Description
Half power The user has pressed the half-power button.

Full power The user has pressed the full-power button.

Timer The user has pressed one of the timer buttons.

Number The user has pressed a numeric key.

Door open The oven door switch is not closed.
Door closed The oven door switch is closed.
Start The user has pressed the Start button.
Cancel The user has pressed the Cancel button.
MCQ
• Which of the following model in system modelling depicts the
dynamic behaviour of the system?

A. Behavioral Model
B. Context Model
C. Structural Model
D. Object Model
MCQ

• Which of the following model in system modelling depicts the static

nature of the system ?

A. Structural Model
B. External Model
C. Behavioral Model
D. Data Model
MCQ

• Which of the following perspective in system modelling shows the

system or data architecture?

A. Data perspective
B. External perspective
C. Behavioral perspective
D. Structural perspective
MCQ

The UML supports event-based modeling using ____________

diagrams.

A. Deployment
B. Collaboration
C. State chart
D. All of the above
MCQ
• Which of the following diagram is not supported by UML considering
Data-driven modeling ?

A. Activity
B. Data Flow Diagram (DFD)
C. State Chart
D. Component
MCQ
• Which diagram of UML represent Interaction modeling?

A. Use Case
B. Sequence
C. State Chart
D. Both A and B
Usage of model-driven
engineering
• Model-driven engineering is still at an early stage of development,
and it is unclear whether or not it will have a significant effect on
software engineering practice.

• Pros
• Allows systems to be considered at higher levels of abstraction
• Generating code automatically means that it is cheaper to adapt systems to
new platforms.
• Cons
• Models for abstraction and not necessarily right for implementation.
• Savings from generating code may be outweighed by the costs of developing
translators for new platforms.
Model driven architecture
• Model-driven architecture (MDA) was the precursor of more general
model-driven engineering

• MDA is a model-focused approach to software design and

implementation that uses a subset of UML models to describe a
system.

• Models at different levels of abstraction are created. From a high-

level, platform independent model, it is possible, in principle, to
generate a working program without manual intervention.