visual modeling using rational rose

1

Visual Modeling Using Rational Rose

Networking LAB

OOSD 담당조교석사과정 이정환

Kyung Hee University

2

Contents Introduction to visual modeling

using a rational rose Getting started with rational rose Introduction to diagrams Introduction to specifications Class diagrams and specifications Simple Example (hello world)


3

Introduction to Visual Modeling Using a Rational Rose

Rational Rose provides support for two essential elements of modern software engineering Component based development Controlled iterative development

Rational Rose use Component Object Modeling (COM) Object Modeling Language (OMT) Booch ’93 method for visual modeling


4

Introduction to Visual Modeling Using a Rational Rose (cont’d)

Visual Modeling Help organize, visualize, understand, and

create complex things The mapping of real world processes of a

system to a graphical representation. Useful for understanding problems,

communication with everyone involved with the project (customers, domain experts, analysts, designers, etc.), modeling complex systems, preparing documentation, and designing programs and databases.


5


Modeling promotes better understanding of requirements, cleaner designs, and more maintainable systems

Visual modeling captures business processes by defining the software system requirements from the user’s perspective


6


Modeling with Rational Rose Rational Rose is the visual modeling

software solution that lets you create, analyze, design, view, modify and manipulate components and implement system in a way that makes them truly easy to communicate


7

Getting Started With Rational Rose

The application window


Toolbar

Menu Bar

Browser

DocumentationWindow

Specification Window

Diagram Window

8

Getting Started With Rational Rose (cont’d)

Documentation Window Describe model elements or

relationship The description can include such

information as the roles, keys, constraints, purpose, and essential behavior of the element


9


Diagram Window Diagram windows allow you to create

and modify graphical views of the current model

Each icon in a diagram represents an element in the model


10


Overview Window The overview window is a

navigational tool that helps you move to any location on all Rational Rose diagrams


11


Specification Window A specification enables you to display

and modify the properties and relationships of a model element, such as a class, a relationship, an operation, or an activity


12

Introduction to Diagrams Overview

Diagrams are views of the information contained in a model

Diagram windows Class diagram Use-case diagram Collaboration diagram Sequence diagram Component diagram Statechart diagram Deployment diagram Activity diagram


13

Introduction to Specifications

A specification enables you to display and modify the properties and relationships of a model element, such as a class, a relationship, or an operation


14

Class Diagrams and Specifications

Class diagram overview A class diagram is a picture for describing

generic descriptions of possible systems Class diagrams and collaboration diagrams

are alternate representations of object models

Class diagrams contain classes and object diagrams contain objects, but it is possible to mix classes and objects when dealing with various kinds of metadata, so the separation is not rigid


15

Class Diagrams and Specifications (cont’d)

Class specification A class specification displays and modifies

class properties and relationships Stereotype

A stereotype represents the subclassification of an element

It represents a class within the UML metamodel itself

Some stereotypes are already predefined, but you can also define your own to add new kinds of modeling types


16


Cardinality The cardinality field specifies the number of

expected instances of the class. In the case of relationships, this field

indicates the number of links between each instance of the client class and the instance of the supplier

You can set a specific cardinality value for the client class, supplier class, or both


17



Type Description

N(default) Unlimited number of instances

1 One instance only

0..n Zero or more instances

1..n One or more instances

0..1 Zero or one instance

<literal>* Exact number of instances

<literal>..n Exact number of more instances

<literal>..<literal> Specified range of instance

<literal>..<literal>,<literal> The number of instances will be in theSpecified range or an exact number of instances

<literal>..<literal>,<literal>..<literal>

The number of instances will be in one of the specified ranges

18


Concurrency A class concurrency defines its

semantics in the presence of multiple threads of control


19



Type Description

Sequential (default) The semantics of the operation are guaranteed only in the presence of a single thread of control. Only on thread of control can be executing in the method at any one time

Guarded The semantics of the operation are guaranteed in the presence of multiple threads of control. A guarded class requires collaboration among client threads to achieve mutual exclusion

Active The class has its own thread of control

Synchronous The semantics of the operation are guaranteed in the presence of multiple threads of control; mutual exclusion is supplied by the class

20

Simple Example (Hello World) Abstract of key point

import java.awt.Graphics;

class HelloWorld extends java.applet.Applet {public void paint (Graphics g) {

d.drawString ("Hello, World!", 10, 10);}

}


21

Simple Example (cont’d) The UML modeling


HelloWorld

paint()

g.drawString("Hello World!", 10, 10)

22

Simple Example (cont’d)


Applet

HelloWorld

paint()

Graphicsg.drawString("Hello World!", 10, 10)

23



Object

Component

ImageObserver

Container

Panel

Applet

HelloWorld

paint()

24



: Thread : Toolkit : ComponentPeer target: HelloWorld

painthandleExpose

callbackLoop

run

25



HelloWorld.html HelloWorld.class HelloWorld.java

Hello.jpg

26

Practice time Make the class diagram of this

source code OOSD.java


27


visual modeling using rational rose

Documents