UNIT -II

CHAPTER 3
SYSTEM MODELS
 SYSTEM MODELS

• Context models
• Behavioural models
• Data models
• Object models
• Structured methods
 SYSTEM MODELS

• The graphical representation of the system which the

software developer wants to develop is called a system
model.
• System modeling is the process of developing abstract
models of a system, with each model presenting a
different view or perspective of that system.
• The system is developed based on user requirements
and system requirements.
• The system models describe the system in detail using
graphical notation which is now almost always based
on notations in the Unified Modeling Language (UML)
 SYSTEM MODELS
• System modeling helps the analyst to
understanding the functionality of the system and
models are used to communicate with customers .
• Benefits of System Modeling
• Ease project management tasks.
• Can provide complete views of a system, as well
as detailed views of subsystems.
• Clarify structures and relationships.
• Offer a communication framework for ideas
within and between teams.
• Can generate new ideas and possibilities.
 System Perspectives
• Different models may represent a system from
different perspectives.
• An external perspective model representing the
context or environment of the system
• An interaction perspective Model where the
interactions between a system and its environment or
between the components of a system is represented.
• A structural perspective model showing the
organization of a system or the structure of the data
that is processed by the system.
• A behavioral perspective, where the model shows the
dynamic behavior of the system and how it responds
to events.
Context Models
 Context Models

• The context model represents how the system

that must be built will interact with other
systems within its environment.
• It shows the boundaries of a system that
includes various automated systems in an
environment.
• It describes the inside and outside of the system.
It is important to find what is inside and outside
of the environment.
• The position of the system boundary plays a
vital role that affects the system's requirements.
 Context Models
• The requirements of employees and stakeholders are
discussed while creating the context model to decide the
system's functionality that needs to be developed.
• It shows the relationships between the system to be
created and other systems.
• No technical knowledge is assumed or required to
understand the diagram
• Easy to draw and amend due to its limited notation
• Easy to expand by adding related systems
• Can benefit a wide audience including stakeholders,
business analyst, data analysts, developers
 Examples of the Context Model
The Order Processing System:
• The context model diagram has the main system in the middle called the
"Order Processing System". The main system is connected to other systems,
which are Customer Channels, Delivery Dispatch System, Inventory
Management System, and Payment Processing System.

The context model diagram has the main system in

the middle called the "Order Processing System".
The main system is connected to other systems,
which are Customer Channels, Delivery Dispatch
System, Inventory Management System, and
Payment Processing System.
 Context Models
 The "Order Processing System" is used to manage the orders easily.
 First, the Order Processing System will interact with customer channels, and the order may
come from different channels.
 The data is also exchanged between the main system and other systems. The order is
received from the customer channels, so the data exchange between the Order Processing
System and Customer Channels is "order details and customer info".
 The Payment Processing System is used to get the payment from the system.
 The data discussed between the Order and Payment Processing System is "order amount and
payment status".
 The main system will confirm the order and pass the information to the Inventory
Management System because every order requires certain ingredients. The data discussed
between the Order Processing System and Inventory Management System is "order detail
and low inventory alerts".
 Context Models
• If enough ingredients are not in the inventory,
the inventory management system will alert the
main system.
• When the order is prepared, it must be
delivered with the help of the Delivery
Dispatch System that manages the trucks and
drivers required.
• The data discussed between the Order
Processing System and Delivery Dispatch
System is "order details and delivery status".
 Context Models
• Simple and powerful. This basic diagram can help
discover gaps, missed impacts, interactions and
requirements early in the project.
• And early is the best time, so that the scope of the
project can be defined more accurately and
realistically, and so that the analysis does not miss
any important interactions
3.2 BEHAVIORAL
MODELS
 3.2Behavioral Model
• behavioral model describe the overall behavior of
the system.
• There are two types of behavioral models that are
used to describe the system behavior.
• Data processing model (DFD)
• State machine models(State Transition Diagram.)
• Data processing models are also known as DFD
(Data Flow Diagram) which is used to show how
data is processed as it moves through the system
• State machine model is also known as State
diagram which is used to show how the system will
react with external events.
 Data Flow Diagram

• Data flow diagram is used to model the system’s data

processing.
• It is also the Functional model as it is a graphical
representation of an enterprise function within a
defined scope. Data flow diagram shows end to end
data processing.
• It can be easily converted into software as they just
represent flow of the data objects. DFD diagram
enable Software engineer to develop a model of the
information domain and Functional domain at the
same time.
• It provide a logical model of the system and show the
flow of the data and the flow of logic involved.
 Characteristics of Data Flow Diagram

• It shows the process, that transforms incoming

data flows into outgoing data flows.
• Process that performs this transformation
normally creates as well as uses data.
• External entities send and receive data flow
from the systems.
• It is also called a bubble chart.
• Data flow diagram support a top-down
approach for analysis.
 Data Flow Diagram Notation

• Data flow diagram consists of a series of

symbols joined together by a line.
• Data objects are represented by circles which
are also called bubble charts.
• Data flow diagram are represented in
hierarchical order. The first level data flow
model is also called as DFD 0 level or context
diagram which represents the system as a
whole.
• Second level data flow model refines the
context diagram and provides more details of
first-level DFD. In a similar way, third level
 Notations of data flow diagram
• Circle: A circle (bubble) shows a process that
transforms data inputs into data outputs.
• Data Flow: A curved line shows the flow of
data into or out of a process or data store.
• Data Store: A set of parallel lines shows a
place for the collection of data items. A data
store indicates that the data is stored which can
be used at a later stage or by the other
processes in a different order. The data store
can have an element or group of elements.
• Source or Sink: Source or Sink is an external
DFD Level 0
DFD Level 1
 2-Level DFD
2-level DFD goes one process deeper into parts of 1-level
DFD. It can be used to project or record the
specific/necessary detail about the system's functioning.
2-Level DFD
 State Transition Diagram
• It is a collection of states and events.
• It usually describes overall states that a
system can have and events which are
responsible for a change in state of a
system.
• Example :
Consider an Elevator. This elevator is for n
number of floors and has n number of
buttons one for each floor
 State Transition Diagram
• Elevator buttons are type of set of buttons
which is there on elevator.
• For reaching a particular floor you want to
visit, “elevator buttons” for that particular floor
is pressed.
• Pressing, will cause illumination and elevator
will start moving towards that particular floor
for which you pressed “elevator buttons”.
• As soon as elevator reaches that particular
floor,
illumination gets canceled.
 State Transition Diagram

• Floor buttons are another type of set of

buttons on elevator.
• If a person is on a particular floor and he
wants to go on another floor, then elevator
button for that floor is pressed.
• Then, process will be same as given above.
Pressing, will cause illumination and elevator
to start moving, and when it reaches on
desired floor, illumination gets canceled.
• When there is no request for elevator, it
remains closed on current floor.
 Advantages
• Behavior and working of a system can easily be
understood without any effort.
• Results are more accurate by using this model.
• This model requires less cost for development
as cost of resources can be minimal.
Disadvantages
• This model does not have any theory, so trainee
is not able to fully understand basic principle and
major concept of modeling.
• This modeling cannot be fully automated.
• Sometimes, it’s not easy to understand overall
result.