Object Oriented Modeling

Group Members:-
• Ch Inaam
• Rana Isharab
• Muhammad Afzaal
• Faizan yaseen
• Muhammad Nawaz
• Muhammad Abubakar
What is a use case diagram?
• In the Unified Modeling Language (UML),

a use
diagram can summarize the details of your
system's
users (also known as actors) and their
interactions
with the system. To build one, you'll use a set
of
specialized symbols and connectors.
Characteristics of use case
A use case has this characteristics:-
• Organize functional requirements
• Models the goals of system/actor
(user) interaction
• Records path from trigger events to
goals
• Is multi-level ,so that one use case can
use the functionality of another one
Use Case Diagram
objects
Use case diagrams consist of 4 objects:-
1) Actor
2) Use case
3) System
4) Package
Explanation of objects
What is Actor?
• Actor in a use case diagram is any entity
that performs a role in one given system.
This could be a person, organization or an
external system and usually drawn like
skeleton shown below.
what is Use Case?
• A use case represents a function or an
action within the system. It’s drawn as
an oval and named with the function.
what is System?
• The system is used to define the scope of the use
case and drawn as a rectangle. This an optional
element but useful when you’re visualizing large
systems. For example, you can create all the use
cases and then use the system object to define
the scope covered by your project. Or you can
even use it to show the different areas covered in
different releases.
what is Package?
• The package is another optional element
that is extremely useful in complex
diagrams. Similar to class diagrams,
packages are used to group together use
cases. They are drawn like the image
shown below.
Relationships in Use Case
Diagrams
• There are five types of relationships in a use case diagram. They
are
• Association between an actor and a use case
• Generalization of an actor
• Extend relationship between two use cases
• Include relationship between two use cases
• Generalization of a use case
• Book publishing use case diagram
example
• This use case diagram is a visual representation of the process
required to write and publish a book. Whether you’re an
author, an agent, or a bookseller, inserting this diagram into
your use case scenario can help your team publish the next big
hit.
Use case of Book Publishing
A use case for ATM
Online shopping system
What is a data flow diagram?
• A data flow diagram (DFD) maps out the flow of
information for any process or system.
• It uses defined symbols like rectangles, circles and arrows,
plus short text labels, to show data inputs, outputs, storage
points and the routes between each destination.
• Data flowcharts can range from simple, even hand-drawn
process overviews, to in-depth, multi-level DFDs that dig
progressively deeper into how the data is handled.
• They can be used to analyze an existing system or model
a new one. Like all the best diagrams and charts, a DFD
can often visually “say” things that would be hard to
explain in words, and they work for both technical and
nontechnical audiences, from developer to CEO.
• That’s why DFDs remain so popular after all these years.
While they work well for data flow software and systems,
they are less applicable nowadays to visualizing
interactive, real-time or database-oriented software or
systems.
History of the DFD
• Data flow diagrams were popularized in the late
1970s, arising from the book Structured Design, by
computing pioneers Ed Yourdon and Larry
Constantine.
• They based it on the “data flow graph” computation
models by David Martin and Gerald Estrin.
• The structured design concept took off in the
software engineering field, and the DFD method took
off with it.
• It became more popular in business circles, as it was
applied to business analysis, than in academic
circles.
Components of DFD
• External Entity
• Process
• Data store
• Data flow
External entity:-
an outside system that sends or receives data,
communicating with the system being
diagrammed. They are the sources and
destinations of information entering or leaving the
system. They might be an outside organization or
person, a computer system or a business system.
They are also known as terminators, sources and
sinks or actors. They are typically drawn on the
edges of the diagram.
Process:-
• any process that changes the data, producing an output.
• It might perform computations, or sort data based on
logic, or direct the data flow based on business rules.
• A short label is used to describe the process, such as
“Submit payment.”
Data store:-
• Data store: files or repositories that hold information for
later use, such as a database table or a membership
form.
• Each data store receives a simple label, such as “Orders.”
Data flow:-
• Data flow: the route that data takes between the external
entities, processes and data stores.
• It portrays the interface between the other components
and is shown with arrows, typically labeled with a short
data name, like “Billing details.”
DFD rules and tips
• Each process should have at least one input and an
output.
• Each data store should have at least one data flow in and
one data flow out.
• Data stored in a system must go through a process.
• All processes in a DFD go to another process or a data
store.
DFD levels:
There are three levels of DFD:-
1. DFD Level 0
2. DFD Level 1
3. DFD Level 2
DFD Level 0
• DFD Level 0 is also called a Context Diagram.
• It’s a basic overview of the whole system or
process being analyzed or modeled.
• It’s designed to be an at-a- glance view, showing
the system as a single high-level process, with its
relationship to external entities.
• It should be easily understood by a wide
audience, including stakeholders, business
analysts, data analysts and developers.
Example of DFD Level 0
DFD Level 1
1
• DFD Level provides a more detailed breakout of pieces
of the Context Level Diagram.
• You will highlight the main functions carried out by the
system, as you break down the high-level process of the
Context Diagram into its sub processes.
DFD Level 2
• DFD Level 2 then goes one step deeper into parts of Level
1.
• It may require more text to reach the necessary level of
detail about the system’s functioning.
Examples of how DFD can be used
• Data flow diagrams are well suited for analysis or

modeling of various types of systems in different fields.
• DFD in software engineering: This is where data flow
diagrams got their main start in the 1970s. DFDs can
provide a focused approached to technical
development, in which more research is done up front to
get to coding.
• DFD in business analysis: Business analysts use DFDs to
analyze existing systems and find inefficiencies.
Diagramming the process can uncover steps that might
otherwise be missed or not fully understood.
Continue….
• DFD in business process re-engineering: DFDs can be used
to model a better, more efficient flow of data through a
business process. BPR was pioneered in the 1990s to help
organizations cut operational costs, improve customer
service and better compete in the market.
• DFD in agile development: DFDs can be used to visualize
and understand business and technical requirements and
plan the next steps. They can be a simple yet powerful tool
for communication and collaboration to focus rapid
development.
• DFD in system structures: Any system or process can be
analyzed in progressive detail to improve it, on both a
technical and non-technical basis.
Logical DFD vs. Physical DFD
Logical DFD
• These are the two categories of a data flow
diagram. A Logical DFD visualizes the data flow
that is essential for a business to operate. It
focuses on the business and the information
needed, not on how the system works or is
proposed to work.
• In logical DFD ,The processes represent the
business activities.
• The data store represent the collection of data
regarding of data is stored.
• It is how business control.
Physical DFD
• However, a Physical DFD shows how the
system is actually implemented now, or how it
will be. For example, in a Logical DFD, the
processes would be business activities, while in
a Physical DFD, the processes would be
programs and manual procedures.
• As compare to logical DFD, the process
represent the program, program modules and
manual procedures.
• The data store represent the physical files and
database.

Object Oriented Modeling

Uploaded by

Document Information

Original Description:

Original Title

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

Object Oriented Modeling

Uploaded by

Copyright:

Available Formats

Group Members:-

• In the Unified Modeling Language (UML),

• Data flow diagrams are well suited for analysis or

You might also like