Rational Rose-Introduction

Document directory

• Structured things
• Action
• Group transaction
• Comments

Rational Rose

Rational Rose is a visual modeling tool developed by Rational Corporation for an object-oriented unified modeling language. Component Construction for visual modeling and corporate-level horizontal software applications.

The current version of Rational Rose can be used to do the following work: 1. Business Modeling (workflow); 2. Object Modeling (representing the objects in the Information System, (3) how to collaborate between them to complete system functions). 3. model the database and perform positive and reverse engineering and synchronization between the object model and the data model; 4. Build a component model (indicating the physical composition of the information system, such as what files, processes, threads, and distribution are available). 5. Generate framework code for the target language, such as VB, Java, and Delphi.

 

View in Rational Rose

1. Use Case View)
2. logical view (logical view)
3. Component view (Component view)
4. Deployment view (configuration view)

 

Several views that constitute the system model

1. Use Case View
2. Logic View
3. Component View
4. Concurrency View
5. Configuration View

 

Case View

Purpose: Describe the functions that the system should have, that is, the functions observed by external users called participants.
The Use Case view is the core of several views, and its content directly drives the development of other views.

 

Logic View

Purpose: describe the implementation of the system functions proposed in the use case view.
The logical view describes both the static structure of the system and the dynamic collaboration relationships within the system.
Users: Mainly designers and developers.
Composition: The static structure is described in the class diagram and object diagram. The dynamic model is described in the state diagram, sequence diagram, collaboration diagram, and activity diagram.

 

Concurrency View

Purpose: consider the effective use of resources, parallel code execution, and asynchronous event processing in the system environment.
Users: developers and system integrators.
Composition: status chart, collaboration diagram, and activity diagram.

 

Component View

Purpose: Describe the implementation modules of the system and their dependencies.
Component: component diagram.
Users: developers.

 

Configuration View

Purpose: display the physical deployment of the system and describe the deployment of running component instances on the node instances.
Composition: configuration diagram.
Users: developers, system integrators, and testers.

 

Ration rose can be used to create the following graphs:

1 use case diagram
Two types of Graphs
3. object graph
4 status chart
5 Sequence Chart
6. Collaboration Diagram
7 activity diagram
8. Component Diagram
9. Configuration chart

 

Model Element

Relationships in things and UML

 

Things

1. Structured things
2. Action
3. group things
4. Comment on things

 

Structured things

The most basic structured thing in the UML model, including: Class, interface, collaboration, use case, Activity Class, component, node

Class: Abstraction of objects with the same attributes, methods, relationships, and semantics.

 

Interface: a set of operations that a class or component provides for a specific service. It describes the externally visible actions of a class or component.

 

Collaboration: defines interactive operations, representing the implementation of the mode that constitutes the system.

 

Use Case: describes a series of actions performed by the system on a specific role to organize action things.

 

Activity Class: A class object has one or more processes or threads. Its Objects represent the behavior of elements and the existence of other elements at the same time.

 

Component: implements the physically replaceable system part of an interface set.

 

Node: A physical element that exists during running, representing a computing resource. It usually occupies some memory and has processing capabilities.

 

Action

The dynamic part of the UML model, including interaction and state machine.

Interaction: A group of objects in a specific context, in order to achieve a specific purpose and a series of message exchange actions.

 

A state machine is composed of the States of a series of objects.

 

Group transaction

Section of the UML model.
There is only one type of group thing: package.
A package is a mechanism for grouping organized elements.
The package only exists in the development phase.

 

Comments

Description of the UML Model

 

Relationships in UML