Package Diagram introduction and common operations of package diagram in rational

Package Diagram introduction and common operations of package diagram in rational

Package chart Introduction

1. Definition: group model elements and provide a namespace for the elements in the group.

2. role: it is easy to understand complex systems and control the connections between various parts of the system structure. Logically, you can modularize a complex diagram. Describe your requirements and design overview.

3. Deep understanding: the package is only a graphical tool for conceptual model management, but exists in the software development process. In my understanding, the role of a package is to summarize and describe the package as a folder and apply it to any UML diagram.

4. Nature:
Nesting: a package is a package element in addition to a namespace. That is to say, a package can be an element in another package.
Visibility: visibility refers to the visibility of the elements in the package, which indicates whether the elements in the package can be accessed by other elements without warranty.

5. indicates:
1. Graphic Representation and name in Rational Rose:

 

The package name is a string in two forms: simple name and path name
2. Elements
A package can have all the elements in UML: classes, interfaces, components, nodes, collaboration, use cases and diagrams, and even packages.
Note: A Model element cannot be owned by more than one package.
3. Introduction: Allow one package element to one element in another package in one house
Representation Method: dependency representation with constructor import Modifier
Output: the public part of the package is called the input (export)
Note: import and access dependencies cannot be passed.

As shown in, this does not mean package1 can introduce package3.

4. Relationship:
1. Introduction and access dependency: used to introduce the elements output by another package to one package
2. generalization: indicates the package family.
6. The following two package diagrams are introduced: Class package diagram and use case package diagram.
Class package diagram: logically organize your design
Organize a class chart into a package chart:
1. Generally, classes with inheritance relationships are placed in the same package.
2. Place classes that are aggregated or composite with each other in the same package
3. Frequent mutual rent sharing classes are placed in the same package
. Use Case package diagram: organizational needs

The Use Cases of the group organization should be based on the needs of the main protagonists. The main audience of the use case package diagram is the stakeholders of the project.

 

Operation Process of the package diagram in Rational Rose
I divided him into two steps:
First: set a single package

Two methods

Modify package attributes

Add package information

Double-click to open ---- A main

Note that there are two methods to add each element to the package.
Drag and Drop in the View window and create in the drawing window.
First, we will move the model element we created to the package. That is to say, the element we created will be completely deleted if it is deleted from the package.
Result 2: only an element is drawn in the canvas. Is it permanently deleted if it is deleted from the package.

Second: Set the relationship between packages

The contact of this package chart can be created in the mian in the view.