Submitted By :

P. Saikiran
lll CSE
07G71A0561
Contents:
 Why modeling
 Aims of Modeling
 Imp of Modeling
 Object oriented modeling
 Principles of modeling
 Building Blocks of UML
 A model is a simplification of reality.
 The process of representing real-world object

 Modeling is a technical sport

 It gives people creativity , manual , mechanical ,

and observation skills and the ability of solving
problems.
 Aims achieved throughout modeling
 Model help us to visualize a system as it is or
as we want it to be.
 Models permit us to specify the structure or
behavior of a system.
 Models gives us a template that guides us in
constructing a system.
 Models document the decision we have made.
 Questions arise when we need Modeling.

Where do I start?

What models should be created?

What diagrams are used where?

 UML is a Language :
A Modeling language is a language whose
vocabulary and rules focus on the conceptual and
physical representation of a system.
 UML is a Language for Visualizing :

Visualizing Some thing are best modeled textually;

other are best modeled graphically. In all
interesting system, there are structure that
transcend what can be represented in a
programming language.
 UML is a Language for Specifying :
Specifying means building models that are
precise, unambiguous and complete. The UML
addresses the specification of all the important
analysis, design and implementation decision.
 UML is a Language for Constructing :

The UML is not a visual programming language,

but its models can be directly connected to a
variety of programming language (Java, C+
+, ...)
 UML is a Language for Documenting :
A software solution is made up by all sort of artifacts in
addition to raw executable code.
These artifacts include:
-> Requirements -> Architecture
-> Design -> Source code
-> Project Plans -> Tests
-> Prototypes -> Releases
 Two most common ways in modeling software
systems are
 Algorithmic
 Procedures or functions
 Object oriented
 Objects or classes
 Class :  Object :
Class represents Every object has
set of objects having identity, state and
similar behavior.
responsibilities.
Class: Objects:

Attributes Attributes

Operations Operations
 The choice of what models to create has a profound
influence on how a problem is
attacked and how a solution is shaped.
 Every model may be expressed at different
levels of precision.
 The best models are connected to reality.
 No single model or view is sufficient. Every nontrivial
system is best approached through a small set of nearly
independent models with multiple viewpoints.
 Things
* Structural Things
* Behavioral Things
* Grouping Things
* Annotational Things
 Relationships
* Association
* Generalization
* Realization
* Dependency
 Building Blocks of UML

 Class diagram
 Object diagram

 Component diagram

 Deployment diagram

 Use case diagram

 Sequence diagram

 Collaboration diagram

 State chart diagram

 Activity diagram
 Structural —They represent physical and conceptual elements. They are
nouns of UML models.

 Behavioral —They consists of the dynamic parts of UML models verbs

parts of UML models.

 Grouping — It can be defined as a mechanism to group elements of a

UML model together. It is organizational parts of UML models.
 Annotational — It is a mechanism to capture remarks, descriptions, and
comments of UML model elements. explanatory parts of UML models.
 Class
 Interface

 Collaboration

 Use Case

 Active Class

 Component

 Node
 Structural Things

Class: <<Interface>>

Collaboration

Use case

Class:
(active position)

Component
Node
 Interaction
A set of objects exchanging messages, to accomplish a specific purpose.

”
Element A Element B

 State Machine
specifies the sequence of states an object or an interaction goes through during its
lifetime in response to events.

State A State B
For organizing elements (structural/behavioral) into groups, Purely conceptual.

University Administration
Student Admission
Course Manager
-Student
+Department

Annotational Things in UML: Note

Explanatory or Comment parts of UML models called adornments .

Note
1. Associations
Structural relationship that describes a set of links, a link being a connection
between objects.
Student University
attends

2. Generalization
a specialized element (the child) is more specific the generalized element.

Person
Student
 3. Realization
one element guarantees to carry out what is expected by the other element.

Class A Class B

4. Dependency
a change to one thing (independent) may affect the semantics of the other thing (dependent).

Class A Class B
Class Diagram : MITS

Ge
ne
r al
iz a
ti o
n
MCA MBA B-
TECH
 TECH
B-

n
ti o
iz a
r al
ne
Ge
MBA
MITS

MCA
Use Case Diagram
Buy
Book

Pay
Money

Take Shop Keeper

receipt
Customer
Sequence diagram

Person ATM BANK

Insert card

pin request
Enter pin Verify pin

Accepted
Amount Request
Amount
Enter amount Verification
Receive Money
Accepted

Receipt
Card
 Student
Admission
ssion
d mi
1:come to college
iv eA
2: G

3: Give Dept to
MITS Department
Student

4:G
i ve H
all T
ic k e Roll Number
t
Specification elements

Stopped Running

Maintenance

Error Exhausted
 Activity
Diagram :
Manage Thread

Thread Exists

Remove thread
New thread Modify thread

Create Thread Modify Thread Delete Thread

Complete Thread