UML - OOA unified approach

object-oriented analysis unified

approach so in this session we are going

to discuss and concentrate on this topic

in the previous video we have discussed

what is the unified approach and what is

the layered architecture in the next

video we'll be discussing

object-oriented design - unified

approach so object-oriented design

unified approach must be coming after

object-oriented analysis unified

approach so let us discuss what is the

object oriented analysis unified

approach and what are the steps to be

followed up with the numbers step 1 step

2 step 3 in this way so the goal of

object-oriented analysis is to

understand the problem domain and the

system responsibilities by understanding

how the user will use the system so

depending upon the users usage how the

user will use the system the analysis

has to be done and all the requirements

are to be gathered and they are to be

analyzed in this object-oriented

analysis phase so OAH step 1 identify

the actors who is the user of the system

so at first we are supposed to find out

all the actors what is the meaning of

the actors that means who will be the

user of the systems later we shall show

you that these actors can be categorized

as the primary actors and the secondary

actors next one is the object-oriented

analysis step number two a simple

business model using UML activity

diagram has to be developed so a simple

business model is to be developed and

here will be having the list of

operations or list of processes which

will be initiated by these actors they

are to be represented in certain diagram

next one is object-oriented analysis

step 3 so develop the use case leaves

the works carried out by the users of

the system and provide comprehensive

documentation of the system under study

so what is the use case use cases means

nothing but the functional requirement

of the system so what are the use

cases will be initiated by these actors

they are to be represented in a certain

diagram and then also we should have to

write one documentation where this UCS

detailing will be written step number

four Oh

step number four develop interaction

diagrams to identify the classes so

determine the sequence of actions and

develop their sequence and the

collaboration diagrams so in this

particular phase we are going to form

the sequence diagrams and that

collaboration diagrams and they are

collectively known as the interaction

diagrams so as we are not having the

idea on these particular diagrams we are

having the separate chapters we will be

discussing what is the sequence diagram

and what is the collaboration diagram I

can tell you this one that this sequence

diagram and collaboration diagrams they

are actually denoting that how the

messages are being passed and received

between objects in case of sequence

diagram will be discussing this passing

of messages and receiving of this

messages along with the time that at

what time which message has been

received by which object and which

message has been sent by which object

and their respective serial orders and

in case of collaboration diagram

actually it will give us a static or the

dynamic view rather I should say the

dynamic view of the system and hear how

this objects are passing their messages

and receiving their messages that will

be depicted so in the case of step four

we are interested to draw the respective

interaction diagram so now we are going

for object oriented analysis step five

developed static UML class diagrams so

here will be developing the class

diagrams identify the classes identify

relationships identify attributes and

identify their respective methods a

class will be consisting of certain

number of attributes which will be

holding values and certain number of

methods which will be denoting that what

are the permitted operations that we can

carry out on those attributes and

identify the classes with the proper

nomenclature should be there so that

from the gnome

richard itself we can get the idea what

is the purpose of that class and

identify the respective relationships

between these classes oh eh oh eh step

number six that is object-oriented

analysis step number six iterate and

define if needed and repeat the

preceding steps so again we shall go for

step number one to step number five

again and again until until the

refinement has been completed now the

analysis phase object-oriented analysis

phase will get completed so here you see

we're having this actors develop useless

activity diagrams developed interaction

diagrams here will be having the

sequence diagram and collaboration

diagrams identify the classes and

relationships and attributes and methods

so attribute means the respective values

whatwhat the class can hold and this

methods are the permitted operations on

them and refine and reiterate again and

again until the system has become stable

and in accordance with our requirement

so that is our object-oriented analysis

a unified approach thanks for watching

this video