GREEN UNIVERSITY OF BANGLADESH

SUBMITTED BY : SUBMITTED TO :
MD ISHRAKH BARI SHUVO MD. SOLAIMAN MIA
ID – 181002027 ASSISTANT PROFESSOR
SEC - DA
OVERVIEW OF SYSTEM MODELING

 Models of dynamic systems are very important tools for design and analysis to understand many
domains including mechanical systems, electrical systems, information systems, life sciences etc.
Moreover, most real-world applications include multiple domains in the same system that interact
dynamically across domain boundaries. System modeling functionality in the Wolfram language
provides powerful tools for simulation, analysis, and programming modeling capabilities. The
extensive algorithms available in the Wolfram language allow you to easily switch between easy-to-
use functions and create your own advanced custom workflow.
 TYPES OF UML DIAGRAMS
UML stands for Unified Modeling Language. It is a rich language for modeling software solutions, application
structures, system behavior and business processes. There are two main categories. Structure diagrams and behavioral
diagrams.

Structure Diagrams Behavioral Diagrams

1.Class Diagram 1.Use Case Diagram
2.Component Diagram 2.Activity Diagram
3.Deployment Diagram 3.State Machine Diagram
4.Object Diagram 4.Sequence Diagram
5.Package Diagram 5.Communication Diagram
6.Profile Diagram 6.Interaction Overview Diagram
7.Composite Structure Diagram 7.Timing Diagram
CONTEXT MODEL (DESIGN AN EXAMPLE FOR AN ATM SYSTEM)

Context models are used to illustrate the operational

context of a system. They show what is outside the
boundaries of the system. They show how IT applications
are in the context of people and the companies they serve.
Contextual models are sometimes called enterprise
architecture models, sometimes high-level design models,
and sometimes conceptual models. They only show other
systems in the environment, not how the system is
evolving in that environment
 USE CASE MODELING (DESIGN AN EXAMPLE FOR AN ATM
SYSTEM)

A UML use case diagram is an initial form of system / software requirements for a
new underdeveloped software program. Using cases specifies the expected
behavior and is not the correct method of creation. Specific uses Once identified,
both text and visual presentations can be identified. A key concept of modeling in
terms of usage is that it helps us design a system from a user’s perspective. It is an
effective strategy for communicating system behavior in user terms by specifying
the behavior of all externally visible systems.
The image is generally easy to use and usually does not display details when used:
It summarizes some of the relationships between the actor and the system, just in
case of use.
It does not display the sequence of steps performed to achieve the goal in each use.
As mentioned, the diagram should be easy to use and can have several shapes. If
you have more than 20 uses, you are probably using the image for use.
SEQUENCE DIAGRAM (DESIGN AN EXAMPLE FOR AN ATM
SYSTEM)

UML Sequence Diagrams Interaction diagrams describe how

operations are conducted. They capture interactions between
objects in the context of collaboration. Sequence diagrams
visually show the time focus and the sequence of views using the
vertical axis of the diagram to represent what messages are sent
and when they are displayed.
CLASS DIAGRAM (DESIGN AN EXAMPLE FOR AN ATM SYSTEM)

The class diagram is a static diagram. It presents a static view of

an application. Class diagram is used not only for visualizing,
describing and documenting various aspects of a system, but
also for constructing executable code for software applications.
The class diagram describes the characteristics and activities of
a class and the constraints imposed on the system. Class
diagrams are widely used in modeling object-oriented systems
because they are only UML images, which can be mapped
directly to object-based languages.
The class diagram shows a collection of classes, interfaces,
associations, collaborations and limitations. This is also known
as structural diagram
GENERALIZATION (DESIGN AN EXAMPLE FOR AN ATM SYSTEM)

In UML modeling, generalization is a relationship that

applies the concept of object orientation called inheritance.
Generalization relationship occurs between two entities such
as the father or mother of one entity and the other child. The
child inherits the functionality of his parents and can also
access updates.
The generalization relationship refers to the child’s activities,
characteristics, and inheritance of his or her parental
relationship using class, material, location, and case
diagrams.
TRANSACTION PROCESSING OF DATA DRIVEN MODELING
(DESIGN AN EXAMPLE FOR AN ATM SYSTEM)

A transaction is an exchange between two or

more business entities, and a transaction
processing system is an information system that
stores information about a transaction and
sometimes controls the decisions made as part
of the transaction. In addition, transaction
processing systems capture and process the
detailed information needed to update the data
of an organization's initial activities.
ADVANTAGES AND DISADVANTAGES OF MODEL DRIVEN
ENGINEERING
Advantages :
1.Model driven development is
faster
2.It is more cost-effective
3.It leads to increased quality
4.It leads to meaningful validation
5.It bridges the gap between
business and IT
6.It results in software being less
sensitive to changes in business
requirements.
7. It provides up-to-date
documentation.
Disadvantages:
1.Model driven development actually
introduces a lot of rigidity.
2. Models are only flexible where
flexibility has been designed.
3. The roles of project members are quite
different.
4. The modeling environment doesn’t
always support version control.
5. The modeling tool is "almost" finished
at project start.
6. The requirements team needs to
understand what is allowed and what not.
 EXECUTABLE UML

Executable UML is a modeling language designed to express requirements clearly and unequivocally. Notation is a
subset of the Unified Modeling Language of the Object Management Group. But the underlying semantics is
completely different than any UML. The goal of the executable UML approach was to define UML models with
appropriate behavioral specifications in order to be effective. In its purest form, executable UML software eliminates
system programming requirements.

Semantically Precisely Defined

xUML = UML - +
weak elements actions semantics