Assignment of OOAD: Submitted To: Sir Fiaz
Assignment of OOAD: Submitted To: Sir Fiaz
Submitted To:
Sir Fiaz
Submitted By:
M.Shahbaz Ali
Roll No: MITF17S-38
Semester 3nd
University of Sargodha
( Sub-Campus Bhakker )
Structural UML diagrams
Class diagram
Package diagram
Object diagram
Component diagram
Composite structure diagram
Deployment diagram
Behavioral UML diagrams
Activity diagram
Sequence diagram
Use case diagram
State diagram
Communication diagram
Interaction overview diagram
Timing diagram
Class Diagram
Class diagram are the backbone of almost every object-oriented method,
including UML. They describe the static structure of a system.
Package Diagram
Package diagrams are a subset of class diagrams, but developers sometimes treat
them as a separate technique. Package diagrams organize elements of a system
into related groups to minimize dependencies between packages.
Object Diagram
Object diagrams describe the static structure of a system at a particular time. They
can be used to test class diagrams for accuracy.
Activity Diagram
Activity diagrams illustrate the dynamic nature of a system by
modeling the flow of control from activity to activity. An activity
represents an operation on some class in the system that results in a
change in the state of the system. Typically, activity diagrams are
used to model workflow or business processes and internal operation.
Sequence Diagram
discribe interactions among classes in terms of an exchange
of messages over time.
Interaction Overview Diagram
Interaction overview diagrams are a combination of activity and
sequence diagrams. They model a sequence of actions and let you
deconstruct more complex interactions into manageable occurrences.
You should use the same notation on interaction overview diagrams
that you would see on an activity diagram.
Timing Diagram
A timing diagram is a type of behavioral or interaction UML diagram
that focuses on processes that take place during a specific period of
time. They're a special instance of a sequence diagram, except time is
shown to increase from left to right instead of top down.
Communication Diagram
Communication diagrams model the interactions between objects in
sequence. They describe both the static structure and the dynamic
behavior of a system. In many ways, a communication diagram is a
simplified version of a collaboration diagram introduced in UML 2.0.
State Diagram
Statechart diagrams, now known as state machine diagrams and state
diagrams describe the dynamic behavior of a system in response to
external stimuli. State diagrams are especially useful in modeling
reactive objects whose states are triggered by specific events.
Component Diagram
Component diagrams describe the organization of physical software
components, including source code, run-time (binary) code, and
executables. Learn more.
Deployment Diagram
Deployment diagrams depict the physical resources in a system,
including nodes, components, and connections.
USE CASE Diagram
Log in
Student Registration
reererrRegis
View Students
Enrollement
View supervisor
Log out
Log in
Student Registration
reererrRegis
View Students
Enrollement
View supervisor
Log out
Log in
Registration reererrRegis
Find Class
TeacherCase Diagram
Manage Attendence
Manage Class
Lectures
Manage Class
Reset Password
Log out
Registration
Log in
View Item
CustomerCase Diagram
Search item
Buy item
Payment
Cancel Order
Change item
Log out