System Diagrams 1

System
Diagrams
Presented By:
Ms. Kinjal Mistree
Ms. Niyanta Desai
Session on "System Diagrams" 03/18/2021

Table of Contents
• Modeling
• Class diagram
• Use case diagram
• Sequence diagram
• Activity diagram
• E-R diagram
• Data flow diagram

Modeling
• A model is an abstraction of something for the purpose of
understanding it before building it.
- Both physical models and computer models are usually
cheaper than building a complete system.
- Communication with customers
- Visualization
- Reduction of complexity
- Abstract view of the system

Class Model
• A class describe a group of objects with the same properties.
• Objects in a class have the same attributes and behaviour.
• Class diagram provides a graphical notation for modelling
classes and their relationships.

Attributes and Operations
• An operation is a function or procedure that may be applied to

or by objects in a class.
• A method is the implementation of an operation for a class.

Links and Associations

Multiplicity
• Multiplicity specifies the number of instances of one class that
may relate to single instance of an associated class.
• Ex: 1; 1…* ; 3…5 ; 0…1 ; *
• Multiplicity is constraint on cardinality.

Association end names
• We can give name to the end of association.

• Association end names are nouns in problem descriptions.

Ordering
• Ordering is used when objects have an explicit order.

Association class
• An association class is an association that is also a class.
• Like a class, an association class can have attributes and operations.

Qualified associations
• A qualifier selects among the target objects, reducing the

effective multiplicity, from ‘many’ to ‘one’.

Generalization
• Relationship between superclass and subclasses.

Visibility
• Visibility refers to the ability of a method to reference a

feature from another class.
• It has possible values of public (+), private (-), protected (#).

N-ary associations

Aggregation
• Aggregation is string form of association in which an

aggregate object is made of constituent parts.
• Part-whole relationship
• Aggregation vs. Association

Composition
• Composition is a form of aggregation with two additional

constraints:
1. A constituent part can belong to at most one assembly.
2. It has a coincident lifetime with the whole assembly.

Example Airline System

Example: IoT

Guidelines for class diagrams
• Try to avoid n-ary associations.

• Restrict generalization upto 4-5 levels.
• Don’t get confused between aggregation and composition.
• Associations are bidirectional, without specifying arrows.
• Try to use minimal number of classes, avoid redundancy.

Interaction Modelling
• Class model describes the objects in a system and their
relationships, and the interaction model describes how the
objects interact.
• Interactions can be modelled at different levels of abstractions.
• At high level, use cases describe how a system interacts with
outside actors.
• Sequence diagram provides more detail and show the
messages exchanged among a set of objects over time.
• Activity diagram provides further detail and show the flow of
control among the steps of a computation.

Use Case Model
• Actor: object or set of objects that communicates directly with
the system.
• Use case: functionality that a system can provide by
interacting with actors.

Use Case Relationships
• Include relationship

• Exclude relationship

• Generalization relationship

Guidelines for use case diagrams
• The actors need not be always persons.

• Distinct behaviour sequence (exceptions) and error conditions.
• Multiple actors can participate in a use case.
• Every use case should have at least one actor, and every actor
should participate in at least one use case.

Sequence Model
• A sequence diagram shows participants in an interaction and
the sequence of messages among them.
• Lifeline
• Message
• Concurrent signals
• Each use case requires one or more sequence diagrams to
describe its behaviour.
• Each sequence diagram shows a particular behaviour sequence
of a use case.

Example: IoT

Guidelines for sequence diagrams
• Break large interactions into small tasks and prepare a

sequence diagram for each of them.
• Prepare separate sequence diagram for each error condition.

Activity Model
• An activity diagram shows flow of control, similar to a
sequence diagram, but focuses on operations rather than
objects.
• Unlike a flow chart, an activity diagram can show both
sequential and concurrent flow of control.
• Branches
• Initiation and termination
• Concurrent activities (fork and merge)

Example: IoT

Guidelines for activity diagrams
• Concurrent activities means that the activities can complete in

any order. Before a merge can happen, all inputs must first
complete.
• If there are conditions, at least one must be satisfied when an
activity completes.

E-R Model
• The ER model defines the conceptual view of a database.
• ER Model is a database modeling technique that generates an

abstract diagram or visual representation of a system’s data
that can be helpful in designing a relational database. These
diagrams are known as entity-relationship diagrams, ER
diagrams or ERDs.
• It works around real-world entities and the associations among

them.
• At view level, the ER model is considered a good option for

designing databases.
ER Model Concepts
•ER model has three main concepts:
o Entities(and their entity types and entity sets)
o Attributes (simple, composite, multivalued)
o Relationships (and their relationship types and relationship

sets)
Entity
• An entity is an object that exists and is distinguishable
from other objects.
• Entities are specific objects or things in the real-world

that are represented in the database.
• Entity may be an object with a physical existence for

example student.
• Entity may be an object with a conceptual existence

for example a company, a job, a university course.
Entity Sets
• An entity set is a set of entities of the same type
that share the same properties.
• The set of all persons who are customers at a

given bank can be defines as the entity set
customer.
• The entity loan might represent the set of all

loans to be awarded by a particular bank.
Attribute
• An entity is represented by a set of attributes, that is
descriptive properties possessed by all members of an
entity set.
o For example, an STUDENT entity may have the

attributes ID, Name, Address, Gender, Birth Date.
Notations
Types of Attributes
•Simple or Atomic Attribute
•Composite Attribute
•Single-Valued Attribute
•Multivalued Attribute
•Stored Attribute
•Derived Attribute
Simple or Atomic Attribute
• It cannot be divided into simpler components
Example age of an employee.
Composite Attribute
• Composite Attributes can be divided into smaller subparts,
which represent more basic attributes with independent
meanings.
• The attribute may be composed of several components. For
example: Address(House#, Street, City, State, ZipCode,
Country), or Name(FirstName, MiddleName, LastName).
• Composition may form a hierarchy where some components are
themselves composite.
Example
Single Valued
Attribute
• Single valued attribute has a single value for a
particular entity.
• E.g.: age of employee. There can be only one value for
this.
Multi-valued Attribute
• Multi-valued attribute has multiple values.
• Example: skill set of employee
• Another example, employee entity set with the attribute
phone number.
• An employee may have zero, one or several phone
numbers.
Derived Attribute and Stored
Attribute
• The value of this type of attribute can be derived from
the values of other related attributes or entities.
E-R Diagram with Composite, Multi-valued, And Derived Attributes
Mapping Cardinalities
• Mapping cardinality or cardinality ratio express the number of
entities to which another entity can be associated via a
relationship set.
• Most useful in describing binary relationship sets, although they

can contribute to the description of relationship sets that involve
more than two entity sets.
• For a binary relationship set R between entity sets A and B, the

mapping cardinalities must be one of the following:
o One to one
o One to many
o Many to one
o Many to many
Participation Constraints
• Total Participation − Each entity is involved in the
relationship. Total participation is represented by double lines.
E.g. every loan entity to be related to at least one customer
through borrow relationship.
• Partial participation − Not all entities are involved in the

relationship. Partial participation is represented by single lines.
E.g. the participation of customer in the borrower relationship
set is partial as not all customer has borrowed loan from bank.
E-R Diagrams
 An E-R diagram can express the overall logical structure of a
database graphically.
 Rectangles represent entity sets.
 Diamonds represent relationship sets.
 Lines link attributes to entity sets and entity sets to relationship
sets.
 Ellipses represent attributes
 Double ellipses represent multi-valued attributes.
 Dashed ellipses denote derived attributes.
 Underline indicates primary key attributes.
 Double Lines indicate total participation of an entity in a
relationship set.
 Double rectangles represent weak entity sets.
Example 1
• Library System
Example 2
• Banking System
Data Flow Diagram
• Data flow diagram is graphical representation of flow of data in an
information system. It is capable of depicting incoming data flow,
outgoing data flow and stored data.
• It views a system as a function that transform the input into desired
output .
• There is a prominent difference between DFD and Flowchart.
o The flowchart depicts flow of control in program modules with all
computation, loops.
o DFDs depict flow of data in the system at various levels.
o DFD does not contain any control or branch elements.
Creating Data Flow Diagrams
Steps:
1.Create a list of activities
2.Construct Context Level DFD
(identifies external entities and processes)
3.Construct Level 0 DFD
(identifies manageable sub process )
4.Construct Level 1- n DFD
(identifies actual data flows and data stores )
5.Construct further levels if required
Symbols
Production Example
Example Steps:
The operations of a simple 1. Create a list of activities
lemonade stand will be used
2. Construct Context Level DFD
to demonstrate the creation (identifies sources and sink)
of dataflow diagrams.
3. Construct Level 0 DFD
(identifies manageable sub processes )
4. Construct Level 1- n DFD
(identifies actual data flows and data stores )
Example 1. Create a list of activities
Think through the activities

that take place at a
lemonade stand.
Customer Order
Serve Product
Collect Payment
Produce Product
Store Product
Also think of the additional

activities needed to support
the basic activities.
Customer Order
Serve Product
Collect Payment
Produce Product
Store Product
Order Raw Materials

Pay for Raw
Materials
Pay for Labor
Group these activities in

some logical fashion,
possibly functional areas.
Customer Order
Serve Product
Collect Payment
Produce Product
Store Product
Order Raw Materials

Pay for Raw Materials
Pay for Labor

Example 2. Construct Context Level DFD
(identifies sources and sink)
Create a context level
diagram identifying the Context Level DFD (Level 0)
sources and sinks (users).
Example 3. Construct Level 0 DFD
Create a level 0 diagram (identifies manageable sub processes )
identifying the logical Level 1DFD
subsystems that may exist.
Example 4. Construct Level 1- n DFD
Create a level 1 (identifies actual data flows and data stores )
decomposing the processes Level 2 DFD
in level 0 and identifying
data stores.
Example 4. Construct Level 1 (continued)
Create a level 1
in level 0 and identifying
data stores.
Create a level 1
in level 0 and identifying Order Decision
PURCHASE
data stores. 3.1 ORDER
Produce
Purchase
Customer Order Order Quantity On-Hand
Serve Product RAW
Quantity MATERIALS
Collect Payment Received Received
Goods
3.2
Produce Product Receive
Items
Store Product RECEIVED
ITEMS
Payment Approval
Order Raw Materials
VENDOR
Pay for Raw Materials 3.3
Pay
Vendor
Pay for Labor
Payment
Create a level 1
in level 0 and identifying Time Worked
data stores. 4.1 TIME CARDS

Record
Time
Customer Order Worked Employee ID
Serve Product EMPLOYEE
Collect Payment
Payroll Request
4.2
Unpaid time cards
Produce Product Calculate
Payroll
Store Product PAYROLL
Payment Approval
Order Raw Materials
4.3
Pay for Raw Materials Pay
Employe
e PAYMENTS
Pay for Labor
Payment
Process Decomposition
1.1 1.2
1.0
Record Receive
Sale
Order Payment
2.1 2.2 2.3

2.0
Serve Produce Store
Production
Product Product Product
0.0
Lemonade
System
3.1
3.0 3.2 3.3
Produce
Procure- Receive Pay
Purchase
ment Items Vendor
Order
4.1 4.3
4.2
4.0 Record Pay
Calculate
Payroll Time Employe
Payroll
Worked e
Context Level (Level 0) Level 1 Level 2

Example 3 Level 0 Library
Level 1 Library
Level 2 Library
Example 3 IoT
Example 3 IoT
Any Questions??
THANK YOU

System Diagrams 1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Diagrams 1

Uploaded by

Copyright:

Available Formats

System

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• An operation is a function or procedure that may be applied to

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• We can give name to the end of association.

Session on "System Diagrams" 03/18/2021

• Ordering is used when objects have an explicit order.

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• A qualifier selects among the target objects, reducing the

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• Visibility refers to the ability of a method to reference a

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• Aggregation is string form of association in which an

Session on "System Diagrams" 03/18/2021

• Composition is a form of aggregation with two additional

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• Try to avoid n-ary associations.

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• The actors need not be always persons.

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• Break large interactions into small tasks and prepare a

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

Session on "System Diagrams" 03/18/2021

• Concurrent activities means that the activities can complete in

Session on "System Diagrams" 03/18/2021

• ER Model is a database modeling technique that generates an

• It works around real-world entities and the associations among

• At view level, the ER model is considered a good option for

o Entities(and their entity types and entity sets)

o Attributes (simple, composite, multivalued)

o Relationships (and their relationship types and relationship

• Entities are specific objects or things in the real-world

• Entity may be an object with a physical existence for

• Entity may be an object with a conceptual existence

• The set of all persons who are customers at a

• The entity loan might represent the set of all

o For example, an STUDENT entity may have the

• Most useful in describing binary relationship sets, although they

• For a binary relationship set R between entity sets A and B, the

• Partial participation − Not all entities are involved in the

Think through the activities

Also think of the additional

Order Raw Materials

Group these activities in

Order Raw Materials