OOAD unit2

Post on 10-Apr-2018

268 views 1 download

Transcript of OOAD unit2

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 1/98

Unit-2

Rumbaugh Methodology Booch Methodology  Jacobson Methodology Patterns Frameworks

Unified Approach Unified Modeling Language Use case class diagram Interactive Diagram

Collaboration Diagram State Diagram Activity Diagram.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 2/98

Chapter Objectives

You should be able to define and understand

Object Oriented methodologies.

- The Rumbaugh OMT- The Booch methodology

- Jacobson’s methodologies

Patterns

Frameworks

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 3/98

Rumbaugh’s Object Modeling Technique (OMT)

-A method for analysis,design and implementation by

an object oriented technique.

-fast and intuitive approach for identifying and

modeling all objects making up a system.-Class attributes, methods, inheritance and association can

be expressed easily.

-Dynamic behavior of objects can be described using

the OMT dynamic model.-Detailed specification of state transitions and their -descriptions within a system

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 4/98

Four phases of OMT

(can be performed iteratively)  Analysis: objects,dynamic and

functional models 

System Design: Basic architecture of the system.

Object Design: static, dynamic andfunctional models of objects.

Implementation: reusable, extendibleand robust code.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 5/98

 Three different parts of OMT

modeling An object model - object model &

data dictionary

A dynamic model - state diagrams &event flow diagrams

A functional model - data flow &

constraints

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 6/98

Object Model structure of objects in a system.

Identity, relationships to otherobjects, attributes and operations.

Object diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 7/98

Object Diagram Classes interconnected by

association lines

Classes- a set of individual objects

Association lines- relationshipamong classes (i.e., objects of one

class to objects of another class)

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 8/98

OMT Dynamic Model States, transitions, events and

actions

OMT state transition diagram-network of states and events

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 9/98

OMT Functional Model DFD- (Data Flow Diagram) Shows flow of data between different

processes in a business. Simple and intuitive method for

describing business processes without

focusing on the details of computersystems.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 10/98

Data Flow Diagram Four primary symbols

Process- any function being performed

Data Flow- Direction of data element movement

Data Store – Location where data is stored

External Entity-Source or Destinationof a data element

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 11/98

 The Booch Methodology Widely used OO method

Uses the object paradigm

Covers the design and analysisphase of an OO system

Criticized for his large set of symbols

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 12/98

method Class diagrams-

describe roles and responsibilities of objects Object diagrams

describe the desired behavior of the system interms of scenarios

State transition diagrams

state of a class based on a stimulus

Module diagrams

to map out where each class & object should

be declared Process diagrams

to determine to which processor to allocate aprocess

Interaction diagramsdescribes behavior of the system in terms of 

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 13/98

Booch method prescribes: Macro Development Process

Micro Development Process

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 14/98

Macro Development

Process Controlling framework for the

micro process.

Primary concern-technicalmanagement of the system.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 15/98

Steps for macro development

process1. Conceptualization

2. Analysis & Development of the model

3. Design or create the systemarchitecture

4. Evolution or implementation

5. Maintenance

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 16/98

Micro Development ProcessEach macro process has its ownmicro development process

Steps:- Identify classes & objects

- Identify class & objects semantics

- Identify class & object relationship- Identify class & objects interface

and implementation

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 17/98

 JACOBSON METHODOLOGIES Use Cases.

Object Oriented SoftwareEngineering.

Object Oriented BusinessEngineering.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 18/98

Use Cases Understanding system requirements Interaction between Users and Systems  The use case description must contain

How and when the use case begins and ends.  The Interaction between the use case and its actors,

including when the interaction occurs and what isexchanged.

How and when the use case will need data stored inthe system.

Exception to the flow of events How and when concepts of the problem domain arehandled.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 19/98

OOSE Object Oriented Software

Engineering.

Objectory is built models Use case model

Domain object model

Analysis object model Implementation model

 Test model

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 20/98

OOBE Object Oriented Business

Engineering

OOBE is object modeling at theenterprise level. Analysis phase

Design and Implementation phase Testing phase

E.g. Unit testing, integration and system

testing.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 21/98

PATTERNS It is an instructive information that

captures the essential structure

and insight of a successful familyof proven solutions to a recurringproblem that arises within a

certain context and system of forces.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 22/98

Good Pattern will do the

following It solves a problem.

It is a proven concept.

 The Solution is not obvious.

It describes a relationship.

 The pattern has a significanthuman component.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 23/98

Patterns

Patterns

Generative Patterns(describe recurring phenomena

with saying how to

reproduce them)

 Non Generative Patterns(describe recurring phenomena

without saying how to

reproduce them)

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 24/98

Patterns Template Essential Components should be clearly

recognizable on reading a pattern: Name

Problem Context Forces Solution Examples Resulting context Rationale Related Patterns Known uses

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 25/98

Frameworks Way of delivering application

development patterns to support

best practice sharing duringapplication development.

Can be viewed as theimplementation of a system of design patterns.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 26/98

Benefits of Frameworks Reusability

Modularity

Extensibility

Inversion of Control

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 27/98

Difference between Patterns

and Frameworks Design patterns are more abstract

than frameworks.

Design patterns are smallerarchitectural elements thanframeworks.

Design patterns are lessspecialized than frameworks.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 28/98

Model An abstract representation of a

system.

 Types of model1. Use case model

2. Domain model

3. Analysis object model4. Implementation model

5.  Test model

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 29/98

Model  Types of model

• Use case model defines the outside(actors) & inside (use case) of the

system’s behavior.• Domain model maps real world object

into the domain object model.• Analysis object model how source code

should be carried out & written.• Implementation model represents the

implementation of the system.•  Test model test plans, specifications &

reports.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 30/98

Model Model is an iterative process.

It can represent static or dynamic

situations. Model

Static Dynamic

Represents a system’s behaviors

that, taken together, reflect its

behavior over time.

(e.g.) interaction & activity diagrams

Provides a system’s

parameters at rest or at a

specific point in time.

(e.g.) class diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 31/98

Why modeling Blue print

Clarity

Familiarity

Maintenance

Simplification

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 32/98

Advantages of modeling Easy to express complex ideas

Reduce complexity

Enhance & reinforce learning andtraining

Low cost

Easy to change the model

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 33/98

What is Unified Modeling

Language (UML)? The UML is a graphical /

standard language for

visualizing, specifying,constructing & documentingthe artifacts of a software

system.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 34/98

History of UML 1980 – 1990 Many different

methodologies

Booch method by Grady Booch• Object Modeling Technique (OMT) by JimRumbaugh

• Object Oriented Software Engineering (OOSE) byIvar Jacobson 

Each method had its strengths &weaknesses.• Booch was great in design• OMT & OOSE were great in analysis

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 35/98

History of UMLUML 1.0 (January 1997)

UML 1.1 (November 1997)

UML 1.3 (Current Minor revision 1999)

UML 1.4 (Planned Minor revision 2000)

UML 2.0 (Planned Major revision 2004)

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 36/98

UML Concepts

UML can be used to supportyour entire life cycle.

1. The interaction of your application with theoutside world (use case diagram)

2. Visualize object interaction (sequence &collaboration diagrams)

3. The structure of your system (class diagram)

4. View the system architecture by looking atthe defined package.

5. The components in your system (componentdiagram)

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 37/98

What are Diagrams ? Graphical presentation of model

elements. A diagram is a graphical means to

view a system’s parts

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 38/98

UML Diagrams

8 diagrams  You will model the following 5 diagrams

only:1. Use case diagram

2. Activity diagram

3. Sequence diagram4. Collaboration diagram

5. Class diagram

The other UML diagrams that can be

modeled in Rose are:1. State chart diagram

2. Component diagram

3. Deployment diagram

Interaction

diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 39/98

Behavior Diagram Sequence diagram

Collaboration diagram

State chart diagram

Activity diagram

Interaction

diagram

behavior 

diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 40/98

UML Diagrams

1. Class diagram

2. Use case diagram

3. Activity diagram4. Sequence diagram

5. Collaboration diagram

6. State chart diagram7. Component diagram

8. Deployment diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 41/98

1. Class diagram Class a set of objects that share the

same attributes, operations &

relationships. It represented by a compartmentalized

rectangle.

It shows the structure of your

software. 3 compartments

1.  Top

2. Middle

3. Bottom

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 42/98

1. Class diagram

1.  Top shows class name2. Middle shows class attributes

3. Bottom shows class operation

LoginForm

UserName

PIN

Enter Login Details()

Submit()

LoginController 

Validate()

CustomerInfo

User Name

PINAddress

getLoginDetails()

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 43/98

1. Class diagram1. Attributes defines the characteristics or

structure of a class.

  displayed in the middle of the

compartmentalizedrectangle.

LoginForm

UserName

PIN

Enter Login Details()

Submit()

LoginController 

Validate()

CustomerInfo

User Name

PINAddress

getLoginDetails()

Attributes

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 44/98

1. Class diagram

2. Operation the service provided by theclass.

  displayed in the bottom of the

compartmentalizedrectangle.

LoginForm

UserName

PIN

Enter Login Details()

Submit()

LoginController 

Validate()

CustomerInfo

User Name

PINAddress

getLoginDetails()

Operations

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 45/98

2.Use case diagram It shows a set of use cases andactors and their relationships.

Address the static view of a system.

 Actor   user (or) someone /something outside the system thatinteracts with the system (it must be

a noun) & it is represented by astickman.

……contd

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 46/98

2.Use case diagram Use case  a sequences of actions (itmust be a verb) & it is represented by anoval.

Relationship illustrates a connectionamong model elements.

Unidirectional  Bi-

directional 

It is created to visualize the interaction of your system with the outside world.

(e.g.) ATM

……contd

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 47/98

2. Use case diagram (ATM)

CASH

DISPENSER

PRINTER

CHANGE PIN

WITHDRAW

CHECK BALANCE

LOGIN

CUSTOMER

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 48/98

2. Use case diagram (Pay

roll) Actors employee & account

Use case count leave, disbursesalary, check loans, calculate PF,prepare IT returns, calculate HRA &

check salary

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 49/98

Customer 

Calculate PF

Check loans

Disburse salary

Count leave

Prepare IT returns

Check salary

Calculate HRA

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 50/98

3.Activity Diagram It shows the flow of events with

our system & what is going on

inside a use case. We draw the activity diagram for

each & every use case. Login (use case) – (e.g.) ATM It is showing flow of control from

activity to activity.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 51/98

3.Activity Diagram Activity it represents the

performance of a task within the

workflow. Activity is represented by a lozenge

(horizontal top and bottom with convexsides)

Start state shows the beginning of aworkflow on an activity diagram.

 There is only one start state.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 52/98

3.Activity Diagram A start state is represented by a

solid circle.

An end state represents a final orterminal state on an activity

diagram. A end state is represented by a

bull’s eye.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 53/98

3.Activity Diagram A state transition shows what

activity follows after another.

It is represented by a solid linewith an arrow.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 54/98

3.Activity Diagram A decision is a point in an activity

diagram where guard conditions are

used to indicate different possibletransitions.

It is represented by a diamond.

Guard conditions control the transition

of a set of alternate transitions thatfollows after the activity has beencompleted.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 55/98

3.Activity Diagram AND

Joint

Synchronization bar 

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 56/98

3.Activity Diagram A synchronization bar allows you to

show concurrent threads in a work

flow of a use case. It represented by a thick horizontal

or vertical line.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 57/98

3.Activity Diagram A swimlane is used to partition an

activity diagram to help us better

understand who or what isinitiating an activity.

. v y –

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 58/98

ycase

Customer Enters

the login details

System retrives

the details

System validates

the customer 

System welcomes

the customer 

System prompts to

reenter 

[ True ]

[ False ]

i

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 59/98

4.Sequence Diagram

It shows step by step what musthappen to accomplish a piece of functionality provided by thesystem.

It has 2Ds.• Vertical dimensions represents time

• Horizontal dimensions represents

different objects.

Vertical line is called the object’slife line.

S i

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 60/98

4.Sequence Diagram

Life line the existence object ata particular time.

Objects are shown at the top.

 The object role is shown as avertical dashed line, the life line.

4 S Di

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 61/98

4.Sequence Diagram

A message is the communicationbetween 2 objects that triggers an

event.

It is represented by a labeled arrow.

Each message is represented by anarrow between the life lines of 2objects.

4 S Di

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 62/98

4.Sequence Diagram

A focus of control shows theperiod of time during which an

object is performing an action,either directly or through asubordinate procedure.

It represented by a tall, thinrectangle.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 63/98

4.Sequence Diagram –login success

: Customer : Customer : LoginForm: LoginForm : LoginController  : LoginControl ler : CustomerInfo: CustomerInfo

Enter Login Detail...

Submit( )

Validate( )

getLoginDetails( )

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 64/98

5.Collaboration Diagram It displays objects and their links to

one other.

It is also known as an interactiondiagram.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 65/98

5.Collaboration Diagram It is made up of the following basic

elements :

1. Actors

2. Objects

3. Links

4. Messages

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 66/98

5.Collaboration Diagram• Actors user

• Objects data + logic / the representationof some real world entity.

3. Links a pathway for communication

between objects.

  represented by a solid linebetween 2 objects

4. Messages the communication between

objects that triggers an event.

  represented by a labeled arrowabove

the link.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 67/98

5.Collaboration Diagram –Login use case

: Customer 

: LoginForm

: LoginController 

: CustomerInfo

1: Enter Login Details( )2: Submit( )

3: Validate( )

4: getLog inDetails ( )

6 State Chart Diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 68/98

6. State Chart Diagram

It shows the sequence of states. A state is represented as a rounded

box, which may contain one or morecompartments.

Name compartment holds thename of the state.

Internal transition compartment

 list of actions / activities

Start & end states

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 69/98

7.Component Diagram

It shows relationship between thecomponents in the system.

A component may be a softwarecomponent [for (e.g.) a.h file in

C++ (or) a .java file in Java], a runtime component [for (e.g.) a.DLLfile]

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 70/98

8. Deployment Diagram

It shows the configuration of runtime processing elements & the

software components, processes &objects that live in them.

It shows the nodes in the system &

the connections between them.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 71/98

Review

Name the 2 benefits of visual modeling.

What is UML?

Name three UML diagrams. What are the elements of a use-case

diagram?

Define a use case. Define an actor.

What is meant by a relationship?

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 72/98

Module Summary

Visual modeling1. The interaction of your application with the

outside world (use case diagram)

2. Visualize object interaction (sequence &collaboration diagrams)

3. The structure of your system (class diagram)

4. View the system architecture by looking atthe defined package.

5. The components in your system (componentdiagram)

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 73/98

Module Summary

UML

The UML is a graphical / standard

language for visualizing,specifying, constructing &documenting the artifacts of asoftware system.

M d l S

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 74/98

Module Summary

 You can model the following 8 UMLdiagrams in Rational Rose.1. Use case diagram

2. Activity diagram

3. Sequence diagram4. Collaboration diagram

5. Class diagram

6. State chart diagram

7. Component diagram8. Deployment diagram

Views and Diagrams in Rational

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 75/98

Rose

What is model?A model is a simplification of reality or the

blueprint of the system.

What is view?

A view is a perspective of the model (ie)meaningful to specific stakeholders.

Views

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 76/98

Logical View Implementation View(Analyst / Designer) (Programmers)

Structure Software Management

Process View Deployment View

(System integrators) (System Engineering)

Performance, scalability System topology,

Delivery,& throughput installation &

Communication

Use case view (end

user functionality

Views

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 77/98

Views

In Rose, you can create the followingviews

1. Use-case view

2. Logical view

3. Process view

4. Component view (Implementation view)

5. Deployment view

These views together create what we

call the 4+1 Architectural View

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 78/98

Use Case View

It specifies WHAT the system should do?

Servers as a contract between customerand developer.

Essential to analysis, design and testactivities.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 79/98

Logical View

It supports the functionalrequirements of the system.

It includes use-case realizations,class and interaction diagrams.

It can also include state chart andactivity diagrams.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 80/98

Process View Addresses the performance,

scalability and throughput of the

system.

Is not necessary for a single

Processing environment.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 81/98

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 82/98

Deployment View

Addresses issues like deployment,installation and performance.

.Used for distributed system only.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 83/98

Rational Rose Interface

It includes the following : Browser Diagram window Diagram toolbar Documentation window Log window Options window

 The options window is not technically part of the rose interface. However, it is importantin your initial setup.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 84/98

 The Browser  The browser allow you to

textually view and navigate theviews and diagrams in rationalrose.

Display the elements that youhave modeled. if an elementdoesn’t appear in the browser, itnot a part of your modeledsystem.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 85/98

Diagram window

 The diagram window allows you tocreate and update graphical views

of the current model.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 86/98

Diagram Toolbar

 The diagram toolbarincludes the elements to

build a diagram. Each diagrams toolbar

unique to that diagram.

It is active only when thediagram is displayed.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 87/98

Documentation window

Used to create, view or modify textthat explains a selected item

within a diagram.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 88/98

Log window

Reports progress, result and errors.

For (e.g.) code generation commands

post progress and error messages tothis window.

 To display log window, go to Viewmenu, click LOG to show or hide the

window.  To clear the contents of log window,

click CLEAR LOG.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 89/98

Options window

Used to set all of your default formodeling.

Note that if you change default,existing model elements are not

changed.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 90/98

Basic tool techniques

 There are two basic tooltechniques we will discuss before

you begin the labs. They are1. Deleting diagram elements

2. Adding diagram elements

 

Deleting diagram

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 91/98

Deleting diagramelements

What happens when you delete anelement from the browser? Rosedoes the following.

Removes the selected elements fromthe model

Removes all icons representing the

elements from all diagrams on whichthey appear.

Delete the specification for the

element .

Deleting Diagram Elements

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 92/98

 There are three ways to delete anelement.

• Click the element in the diagram andthen press ctrl-D

• Right click the element in browser,and then click delete

• Click the element in the browser ordiagram. From the edit menu, clickdelete from model.

Deleting Diagram Elements

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 93/98

Adding diagram elements

How do you add diagramelements? You add elements to a diagram from

either the diagram tool bar orbrowser.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 94/98

Review

What are views?

Name a view in rose and discuss

its purpose. Name two feature of the rose

interface

Discuss deleting from the browserversus the diagram.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 95/98

Module Summary

Rational Rose uses views & diagramsto depict varying perspectives and asystem’s parts.

 There are 5 views in Rational Rose :

1. Use case view

2. Logical view

3. Process view4. Component / implementation view

5. Deployment view

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 96/98

Module Summary

Diagrams are a graphical means toview a system’s parts.

 The browser shows all of your model

elements Diagram window is to create a view Diagram toolbar includes the elements

to build a diagram. Documentation window is used tocreate, view or modify text thatexplains a selected item within a

diagram.

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 97/98

Log window reports progress, results &errors.

Option window allows you to set your

defaults. Deleting diagram elements ctrl D,

DEL key (or) go to edit menu, clickDELETE FROM MODEL.

Adding diagram elements click theelement & then click in the diagramwindow.

Module Summary

8/8/2019 OOAD unit2

http://slidepdf.com/reader/full/ooad-unit2 98/98

Thank You!