The document discusses the Unified Modeling Language (UML), which was created to provide a standard modeling language for visualizing, specifying, constructing, and documenting software systems. It originated from the need for a universal modeling approach, and was formed by merging the modeling languages of Booch, Rumbaugh, and Jacobson. The Object Management Group later standardized UML in 1997. UML includes structural diagrams like class and component diagrams and behavioral diagrams like use case and activity diagrams to model different aspects of a system.

1. Nabeel Jamil
Muhammad Sayam
Bilawal Saeed

2. UML

3.  In early stages of model driven development
there was a great need for some universal
approach for modeling a software system
 As different people understand the notation
in different way if there is no universal
model approach
 At that time brooch, rumba, Jacobson gave
there theories and universally accepted
 All of three decided to build a notation
language by merging all of three language
and out product of that was UML (unified
modeling language )

4.  In 1997 OMG (Object management group) a non
profit organization standardized the UML
 Since then they are making improvement in UML
 Released versions of UML
 1.1 November 1997
 1.2 July 1998
 1.3 March 2000
 Latest >> 2.4.1 August 2011

5.  UML stands for Unified Modeling Language
 The Art of Software Modeling
 The UML represents a collection of best
engineering practices that have proven successful
in the modeling of large and complex systems.
 Standard language for specifying, visualizing,
constructing, and documenting the artifacts of
software systems, business modeling and other
non-software systems.

6.  The UML is a very important part of developing
object oriented software and the software
development process.
 Using the UML helps project teams
communicate, explore potential designs, and
validate the architectural design of the
software.
 UML is a notation system though which we can
visualize a model of a system

7.  If software is complex need of model
 If a system is developed by the hundreds of
People there is also need of model for smooth
communication and understanding the software
system
 mange complexity in design
 build and design architecture
 Visualize the implementation
 Design secure , scalable, robust and extendable
system

8.  UML is divided in to two General set of
Diagrams
 Structured modeling diagrams
(It shows the static view of the model)
 Behavioral modeling diagram
(Behavior diagrams shows the varieties
of interface within a model as it
'executes' over time)

9.  Class Diagram
 Object Diagram
 Component Diagram
 Package Diagram
 Composite Structure
 Deployment Diagram

10.  Use Case Diagram
 Activity Diagram
 State Machine Diagram
 Interaction Diagram
 Communication Diagram
 Sequence Diagram
 Timing Diagram
 Interaction Over view Diagram

13.  It shows the static view of a model
 It is the basic building block of the object oriented
system
 It show the relation ship between classes in the system
 Class diagram consist of:
 It consist of rectangle.
Class name is added in this this compartment
(teacher)
Class attribute is added in this department (name )
Class methods are placed in this compartments
(teach)

14.  + sign with attributes or methods shows class
member are public
 - sign with attribute or methods shows class
members are
private
Class name is added in this this compartment (teacher)
Class attribute is added in this department (-name
Class methods are placed in this compartments
(+teach)

15. Sis class diagram
Login
+username
+password
+Login()
+validation()
+get_data()
+display()
Student details
+Name
+Address
+Age
+Course
+Department
+Phone no
+get_data()
+Display()
Update details
+Student details
+Result details
+Updae_info()
+get_detail()
+Display()

16.  An object diagram may be considered a
special case of a class diagram
 Object diagrams highlight the relationship
between classes at some point in time
 Object is shown by a rectangular with
classifier name in the center of rectangular
and under line
 Object diagram shows complex relationship
between classes
 It is useful if we feel classes as more abstract

18. UML component diagrams shows the
dependencies among software components,
including the classifiers that specify them
(for example implementation classes) and
the object that implement them; such as
source code files, binary code files,
executable files, scripts and tables.

21.  This diagram consist of:
 Actor
It is represented by a human, either the actor is a
human
Or and external system.
Actor is role
 Use case
It is represented by an oval shape with
title in it

22.  USE CASE diagram have relationship
 It is relationship between a use case to another
use case
In which a include use case in necessary to
perform other use case,
for example in place order every time the
check funds is included to complete the place
order
place order(use case) <include >
(check funds) use case

23. Student
Databases
Student Login
Message
Attendance
Profile
Result
Time Table
Fee
Library
Log Out
USE CASE

24.  Activity diagram is also dynamic view of the
system
 Activity diagram similar to flow charts
 Each activity consist of series of actions
 Actions are represented by oval shapes
 Actions are connected by arrows
 Arrow shows the flow of the activity diagram
 Activity diagram also shows decision points
called decision node

25.  Activity diagram is used to describe the
individual use case
 Use case is used to describe the user goal
 Activity diagram can be used where we can
use flow charts

26. Login
Student Registration
back to registration
Select Course
Profile
Result
Fee
Library
Log Out
If No
Yes

27.  All the same controls from activity diagrams
(fork, join, merge, etc.)
 Controls can be used on interaction overview
diagrams to put the control logic around the
lower level diagrams.

29. If ( no )
{
Cout << “ Thank you  “;
}