Shulou(Shulou.com)06/02 Report--

This article mainly shows you the "class and use case UML package diagram how to use", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "class and use case UML package diagram how to use" this article.

Brief introduction of UML package Diagram

A UML package diagram is a combination of model elements represented by symbols similar to folders in UML. Each element in the system can only be owned by one package, and one package can be nested in another package. Using UML package diagrams, you can group related elements into a system. A package can contain ancillary packages, diagrams, or individual elements.

A "UML package diagram" can be composed of any kind of UML diagram, usually a UML use case diagram or a UML class diagram. A package is a UML structure that allows you to organize model elements such as use cases or classes into groups. Packages are described as folders and can be applied to any kind of UML diagram. Although UML package diagrams are not formal UML diagrams, they are actually very useful. A UML package diagram is created for ∶

◆ describes a high-level overview of your requirements.

◆ describes a high-level overview of your design.

◆ logically modularizes a complex diagram.

◆ organizes the Java source code.

1. UML-like package diagram

1. Create a UML-like package diagram to logically organize your design

?? Figure 1 depicts a UML class diagram organized into packages. In addition to the package principles described below, apply the following rules to organize UML class diagrams into UML package diagrams:

Put all the classes of a framework in the same package. Classes with the same inheritance hierarchy are generally placed in the same package. Classes that aggregate or combine with each other are usually placed in the same package. Classes that cooperate frequently with each other, classes whose information can be reflected by UML sequence diagrams and UML collaboration diagrams are usually placed in the same package.

Figure 1. A UML-like package diagram.

two。 Create UML component diagrams to physically organize your design.

?? If your components are close to technology, such as those that go through EnterpriseJavaBeans (EJB) or VisualBasic, you should prefer UML component diagrams to describe physical designs rather than UML package diagrams. The version of figure 1 is derived from the component diagram section. As you can see, this diagram is most suitable for physical design. Always remember to follow the practice of Agile Modeling (AM) (Ambler2002)-applying the right Artifact to select models for your work.

3. Put the subbag under the master bag.

?? Figure 1 depicts the inheritance between packages, and you can see that the inherited packages are displayed under the parent package branch. This is consistent with the guidelines for placing subclasses under superclasses in the UML class diagram.

4. Vertically layer the class UML package diagram.

?? Package-to-package dependencies indicate that the contents of dependent packages depend on the contents of another package, or structurally on the contents of other packages. You can see the figure in figure 1. Class interaction, domain classes use infrastructure classes, and infrastructure classes access the database. Traditionally, this order of layering is described from top to bottom.

2. Use case UML package diagram

?? Use cases are usually the main requirement artifact in object-oriented development methodology, especially when your approach is a unified process (Kruchten2000;Ambler2000) instance. And for large project UML package diagrams, it is usually created to organize usage requirements.

1. Create a use case UML package diagram to organize your requirements

?? In addition to the package principles described below, apply the following rules to organize UML use case diagrams into UML package diagrams:

?? Put related use cases together ∶ included, extending, and inheriting use cases in the same package, just like base/parent use cases.

?? Organizational use cases should be based on the needs of the main protagonist. For example, in figure 2, the Enrollment package contains use cases related to students enrolled in a class, a collection of important services provided by the university.

Figure 2. A UML use case UML package diagram that contains the main packages.

two。 Include roles on the use case UML package diagram

?? Figure 2 contains the roles on the UML package diagram, which helps to understand the package in context so that the UML package diagram is more easily understood by the reader.

3. Arrange the use case UML package diagram horizontally

?? The primary audience of the use case UML package diagram is the project stakeholders. Therefore, the organization of the map should be able to reflect their needs. The packages in figure 2 are placed horizontally, and the dependencies drawn from left to right reflect the reading habits of Western culture.

The above is all the content of the article "how to use UML package diagrams for classes and use cases". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.