Scribd
Upload
17 views16 pages

System Modeling

Uploaded by

laxbro290
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views16 pages

System Modeling

Uploaded by

laxbro290
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

SOFTWARE ENGINEERING

SYSTEM MODELING
SYSTEM MODELING
▪ System modeling is the process of developing abstract models (simplified
representations) of a system, with each model presenting a different view or
perspective of that system.

1. External perspective, where you model the environment of a system.


▪ An environment refers to everything external to the system that interacts with or influences it
(e.g., users, other systems, devices, environmental conditions, etc.)

2. Interaction perspective, where you model the interactions between a system and its
environment or between the components of a system.

3. Structural perspective, where you model the physical or organizational layout in terms of
the components that makeup the system and their relationships.

4. Behavioral perspective, where you model the dynamic behavior of the system and how it
responds to events over time.
SYSTEM MODELING

▪ System modelling helps:

▪ The analyst to understand the functionality of the system and models are used to
communicate with customers.

▪ The developer and the customer to assess quality, once the software is built.
UML
▪ UML stands for Unified Modeling Language

▪ UML is a general-purpose, modelling language in the field of software engineering.

▪ UML provides a standard way to visualize the design of a system using kind of graphical
notations.

▪ UML diagrams are categorized into two main types:


1. Structural Diagrams - represent static structure of the system
2. Behavioral Diagrams - represent dynamic behavior of a system by showing
collaborations among objects and changes to the internal states of objects
UML DIAGRAMS
ESSENTIAL DIAGRAMS
1. Use Case Diagrams - show the interactions between a system and its environment.
▪ To represent Behavioral Perspective

2. Sequence Diagrams - show interactions between actors and the system and
between system components.
▪ To represent Interaction Perspective

3. Activity Diagrams - show the activities involved in a process or in the data


processing.
▪ To represent Behavioral Perspective

4. Class Diagrams - show the object classes in the system and the associations
between these classes.
▪ To represent Structural Perspective
SYSTEM MODEL TYPES
1. Interaction Models - focus on the communication and data exchange between
different parts of the system or between the system and external entities.

Use Case Diagrams:

▪ Use Case diagrams should use lines without


arrows because in a use case messages pass in
both directions.

▪ A use case is shown as an 'ellipse' with the actors


involved in the use case represented as 'stick'
figures.
SYSTEM MODEL TYPES
2. Interaction Models - focus on the communication and data exchange between
different parts of the system or between the system and internal entities.

Sequence Diagrams:
▪ Lifelines - rectangles on dotted lines
drawn vertically from objects and
actors.
▪ Interactions - annotated arrows
between lifelines.
▪ Sequence of Interactions: Read from
top to bottom.
▪ Annotations on Arrows - provide more
information about the interactions.
SYSTEM MODEL TYPES
3. Behavioral Models - focus on how the system behaves in response to stimulus
from its environment.

▪ Stimuli as being of two types:


1. Data - some data arrives that must be processed by the system.
2. Events - some event happens that triggers system processing.

▪ Crucial for understanding the logic and flow of processes within the system.

▪ Describe the dynamic behavior and state transitions of the system.


SYSTEM MODEL TYPES
Data-Driven Modeling:
▪ Activity diagrams used to show the sequence of actions involved in processing
input data and generating an associated output.

An Activity Diagram of the


Insulin Pump’s Operation
SYSTEM MODEL TYPES
Event-driven Modeling:
▪ State diagrams used to show how a system responds to external and internal
events.

▪ Example - a system controlling valve may move from a state 'Valve open' to a
state 'Valve closed' when an operator command (the stimulus) is received.

▪ This view of a system is particularly appropriate for real-time systems.


SYSTEM MODEL TYPES

State Diagram of a Microwave Oven


SYSTEM MODEL TYPES

States and Stimuli for the Microwave Oven


SYSTEM MODEL TYPES
4. Structural Models - display the organization of a system in terms of the
components that make up that system and their relationships.

Class Diagrams:
▪ Show the static structure of an object-oriented system including classes and
attributes, and relationships (associations, generalizations, dependencies).

▪ In class diagrams:
▪ Entities as object classes
▪ Attributes as object class attributes
▪ Relations as named associations between object classes

The Consultation Class


SYSTEM MODEL TYPES
Class Diagrams:
▪ An association is a link between classes that indicates that there is a relationship
between these classes.

Classes and Associations in the MHC-PMS The Consultation Class

▪ 1:1 relationship - each patient has exactly one record and each record maintains information about exactly one patient.

▪ * means that there are an indefinite number of objects involved in the association.
SYSTEM MODEL TYPES
Class Diagrams:
▪ Generalization helps in organizing classes into a hierarchy, making the system
easier to understand and manage.

▪ Shows inheritance relationships between classes, where one class inherits


attributes and behaviors from another class.

You might also like