UML and Rational Rose

8/2/2019 UML and Rational Rose

1/36

January 2, 2012 UML and Rational Rose 1

UML with Rational Rose

Sandip M Vaniya


2/36


Outline

Traditional Approach

Introduction of UML

Use case diagram

Sequence diagram

Collaboration diagram

Class diagram

Component diagram

Deployment diagram


3/36


Traditional Approach

Structure analysis (SA)

Data Flow Diagram (DFD)

Structure Design (SD) Structure Chart

WBS


4/36


Data Flow Diagram Notation

Function symbol:-It call as

Function or bubble.

External Entity Symbol:-Librarian, memberEtc.it represent external entity who isInteract with system by inputting dataInto system or consume outputting

data.


5/36


Data flow symbol

data store symbol

Output symbol:- it is used whenthe hard Copy is produce and there are

Several user of the output.


6/36


Important concept

Synchronization and ASynchronization.

Data dictionary:-list all the data item appearing in DFD.

Data definition:-

1. +:-denotes composition of two data item.

2. [ , ,]:-denote selection.

3. ( ):-denote optional data which may or may not appear.

4. { }:-iterative data definition.

5. =:-represent equivalence.

6. /* represent Comment


7/36

Example of SC


8/36


UML

What is Visual Modeling?

Developing object oriented software.

Graphical notations

Developers and customers view software system from

a different perspective.

UML is a standard language for specifying,

visualizing, constructing, and documenting theartifacts of software systems, as well as for business

modeling and other non-software systems.


9/36


Software Design

Steps for analysis & design of object

oriented system


10/36


Use case Diagrams-- represents what happens when actor interacts with a system.

-- captures functional aspect of the system.--Use Cases are for what the system is , not how the system

will be designed

Use Case

Relationship betweenactors and use caseand/or between theuse cases.

-- Actors appear outside the rectangle.

--Use cases within rectangle providing functionality.

--Relationship association is a solid line between actor & use cases.

Actor


11/36


Use case for ATM System

Transfer

fund

Change

PIN

Make

Payment

View

Balance

Withdraw

money

Bank officer

Customer

Credit System


12/36

Use case specification

http://login%20flow%20of%20events.doc/http://login%20flow%20of%20events.doc/http://login%20flow%20of%20events.doc/http://login%20flow%20of%20events.doc/


13/36

Activity Diagram


Show the flow of activities through thesystem.

Describe the workflow behavior of asystem.

An activity diagram shows the flow ofevents within our system.


14/36



15/36



16/36


Select courses

to teach

Create

curriculum

Createcatalog

Place catalogin bookstore

Openregistration

Closeregistration

[ Registration time period expired ]

Mail catalogto students


17/36

Swimlane Diagrams



18/36

What Is a Sequence Diagram? A sequence diagram shows step by step

what must happen to accomplish a piece offunctionality provided by the system.

The diagram shows

The objects participating in the interaction.

The sequence of messages exchanged.

Sequence Diagrams


19/36


Sequence diagram-Example
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


20/36


Joe : Customer

Card Reader :

CardReader

ATM Screen :

ATMScreen

Joe's Account :

Account

1. Accept CardreadCardNo( )

InitializeScreen( )

openAccount( )

verifyPIN( )

promptPIN( )

Enter PIN no
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


21/36

What Is a CollaborationDiagram?

A collaboration diagram emphasizes theorganization of the objects that participate in

an interaction. The collaboration diagram shows The objects participating in the interaction.

Links between the objects.

Messages passed between the objects.

Collaboration Diagrams
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


22/36


Collaboration Diagram

sandip : Customer

Sandip's

Account

Cash

Dispacher

ATM

Screensd

13: 13:Verify Fund14: 14:Deduct Fund

Card

Reader

2: 2. Read Card No

1: 1.Accept Card

4: 4.Open Account

17: 17:Eject Card

3: 3.Intialized Screen

15: 15:Provide Cash

16: 16:Provide Receipt

5: 5.Prompt for PIN8: 8:Promt for Transaction10: 10:Promt for Amount

6: 6:Enter PIN(1234)9: 9:Select Transaction(Withdraw)

11: 11:Enter Amount7: 7:Verify the PIN

12: 12:Withdraw Fund
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


23/36

Class diagram

The class diagram is a static model thatshows the classes and the relationshipsamong classes in the system.


class name

attributes

operations
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


24/36


UML Class symbol has

three parts:

1) Name2) List of attributes3) List of operations
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


25/36


Client

- companyAddress

- companyEmail

- companyFax

+ companyName

# companyTelephone

Class namecompartment

Attributescompartment

Operationscompartment

+ getClientInfo( )

- updateClientInfo( )

private

public

protected

Elements of classdiagram
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


26/36

Types of Attributes

Simple attributes contain single data item

Identifiers connect unique key value

Multi valued attributes contain multiplevalues simultaneously

Composite attributes group of related

attributes

http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


27/36

http://sequence%20diagram.bmp/


28/36



29/36


Composite attributes have multiple sections (sub attributes). They are treated as separate classes in

conceptual data models.
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


30/36

Operation


Actions or function that a class can perform in

manipulating the attributes

Example:

insertInfo(), verifyPassword()
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


31/36



32/36


State Chart Diagrams

Open

NewState

Overdrawn

Customer Request Closure

Withdrawal( Balance


33/36


Component Diagram

Cash Dispenser

card reader

Card Reader

ATM.exe

Cash Dispenser

ATM Screen

ATM Screen
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


34/36


Deployment Diagrams

BankingDatabase Server

Regional ATMServer

Oracle

Server

ATM Server.exe Printer

12 Anand ATM100 V.V.Nagar

ATM

ATM

Client.Exe

ATM

Client.Exe
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/


35/36

Summary


Use Case Diagram displays the relationship among actors and use cases.

Class Diagram models class structure and contents using design elements such as classes, packages andobjects. It also displays relationships such as containment, inheritance, associations and others.

Interaction Diagrams

Sequence Diagram displays the time sequence of the objects participating in the interaction. This consists of thevertical dimension (time) and horizontal dimension (different objects).

Collaboration Diagram displays an interaction organized around the objects and their links to one another.Numbers are used to show the sequence of messages.

State Diagram displays the sequences of states that an object of an interaction goes through during its life inresponse to received stimuli, together with its responses and actions.1

Activity Diagram displays a special state diagram where most of the states are action states and most of thetransitions are triggered by completion of the actions in the source states. This diagram focuses on flows driven byinternal processing.

Physical Diagrams

Component Diagram displays the high level packaged structure of the code itself. Dependencies amongcomponents are shown, including source code components, binary code components, and executablecomponents. Some components exist at compile time, at link time, at run times well as at more than one time.

Deployment Diagram displays the configuration of run-time processing elements and the software components,processes, and objects that live on them. Software component instances represent run-time manifestations ofcode units
http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://sequence%20diagram.bmp/http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/use_case.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/class.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/interaction.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/state.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/diagrams.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/activity.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/physical.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/physical.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/activity.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/diagrams.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/state.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/interaction.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/class.htmhttp://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/use_case.htm


36/36

Thank You

January 2 2012 UML and Rational Rose 36

UML and Rational Rose

Documents

Transcript of UML and Rational Rose