Anda di halaman 1dari 46



Ô 
@ 2 
       
      
@          
        

@        

    
J!"
@               
 
      

@ 
       !   
  
@ "2  
      !
   
@ #            
    
@ $
          
          
           
-Ô #
@ +   
    ,     

 
@   
2 -.  .
 
/ 2           
  
0          
   
" # 
" # 
Object Modeling Technique
+ Object Oriented Software Engineering
=
UML
J!"
MAIN OBJECTIVE OF UML :
ü TO STANDARDIZE ALL OBJECT-
ORIENTED METHODS WITH
GENERAL SPEAKING NOTATIONS.
ü TO REPRESENT USER REQUIREMENTS
PICTORIALLY
Ô-" # 
 1 021 232-
 042 232-
 5/610+ 232-
7 +2+1082+ 232-
7 20+7+9 232-
7 1:1;01 232-
705442/52+5; 232-
705-<5;1;+ 232-
= 1<459-1;+ 232-
! " # 
Purpose :
To present a graphical overview of the
functionality provided by a system in terms of actors,
their goals (represented as use cases), and any
dependencies between those use cases.
´!"
Components :
Ë Use cases
Ë Actors
Ë System boundary boxes (optional)

EXAMPLE
! 
@ Each scenario has a sequence of steps.

± Scenario 1 : Student is enrolled for the subject.


@ Student chooses the ´enroll subjectµ action.
@ Check the student has enrolled in less than 10
subjects.
@ Check if the subject is valid.
@ Assign the subject to the student.
! 
@ Each scenario has a sequence of steps.

± Scenario 2 : Enrolling fails since the student is


already enrolled in 5 subjects.
@ Student chooses the ´enroll subjectµ action.
@ Check the student has enrolled in less than 10
subjects.
@ Return an error message to the student
! " # 
Purpose :
Translating the models
into programming code.
J!"
Components:
Boxes which contain three parts --
ËThe upper part holds the name of the class
ËThe middle part contains the attributes of the
class
ËThe bottom part gives the methods or
operations the class can take or undertake
EXAMPLE
$!" # 
Purpose :
It focuses on some
particular set of object instances and attributes,
and the links between the instances
J!"
Components :
Same as class diagrams , however the attributes
are assigned values or arguments

EXAMPLE
 !% " # 
Purpose :
@ To model life time of an
active system.
@ To describe different states
of an object during its life time.
J!"
Ë +     
  
  
  >
Ë 2   
 
  
  

   
>
Ë 2 
  
   

   >
Ë 2    
    >
Ë 5       
  

  
      
!" # 
Purpose :
An activity diagram shows the
overall flow of control
J!"
0   
@ ’ ’
     >
@       >
@ b’     ? 
@   ? @ 
  >
@  b
 ’
     ?   
 @ 
 

>
@   ’
b
 ’
     ? 

@
"--!  "
!" # 
 !%  " #  !" # 

State diagram shows the object Activity diagram is a fancy flow


undergoing a process. It gives a chart which shows the flow of
clear picture of the changes in the activity of a process.
object's state in this process

1A     1A    


 B  7
  1+0 2  C         
   1+0
&!" # 
Purpose :
It shows the messages exchanged
between processes AND the order in which
they occur.
J!"
Components :
@ Ôarallel vertical lines (lifelines)
@ The arrows represent messages (stimuli)
from an actor or object to other objects.

EXAMÔ 
!Ô" # 
Purpose :
A component diagram depicts
how components are wired together to form
larger components and or software systems.
J!"
Components :
 2ssembly connector
 Delegation connector
!  " # 
Purpose :
@ To describe the message
flow in the system.
@ To describe structural
organization of the objects.
J!"
0   
š / A     !
š 2
        
  


1=2-<41
"Ô" # 
Purpose :
Models the physical deployment
of artifacts on nodes.
J!"
Components :

@ The nodes appear as boxes


@ The artifacts allocated to each node appear
as rectangles within the boxes.

EXAMPLE
Ô 
| |


|  |  

| |

|    |