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

This article mainly introduces the example analysis of UML sequence diagram in Java modeling, which is very detailed and has certain reference value. Friends who are interested must finish it!

Java Modeling: UML sequence Diagram

Unified Modeling language (UML) is a standard notation used to build object-oriented system models. UML made its debut in the object-oriented programming community between 1995 and 1997, and was recognized by the object Management Organization (OMG) in late 1997. Although it was controversial at first-- because it was proposed in support of and against-- UML later became the industry standard for system tagging. The current version of UML is 1.4, and it will continue to evolve to meet the needs of object-oriented developers.

UML can be difficult to learn, mainly because it attempts to provide modeling notation for a fairly wide range of situations. Each modeling notation uses one diagram, while there are currently nine diagrams in the UML specification. Fortunately, learning UML can be a gradual process; you can learn only one diagram at a time, and you don't have to include anything very complicated in the diagram.

In this column, I'll teach you step-by-step UML design and markup based on Java application development. I'll introduce the basics of the UML framework and other modeling techniques in a logical (and possibly enjoyable) way, and you'll learn how to do it by modeling real-world examples. In the * * section, we use the loan processing application as an example, starting with the creation of a sequence diagram. Note that it is assumed that you are familiar with the Java language and have a basic knowledge of object-oriented methods and terminology. This column will briefly explain the concept of object orientation, but will not discuss it in depth.

About sequence diagrams

UML does not exclude any particular software development method or process; it simply standardizes the format of notation. However, many development methods incorporate UML. The Rational Unified process (RUP) is one such approach; the other is function-driven development (FDD). Because of its intuition and versatility, UML sequence diagrams have become part of the front-end modeling activities of these processes. Sequence diagrams are used to model the following:

◆ use case scenario

Protocols in the ◆ framework

◆ subsystem

◆ class

◆ method logic

The following is a brief description of each of the above functions.

Use case scenario

For the sample application, we will use UML sequence diagrams to model a single use case scenario. A use case is a single task performed by an actor interacting with an application to achieve a specified goal. Participants can be any end user, organization, or system that interacts with the application and is external to the application. (to learn about the four actor roles, see about actor roles; for an in-depth discussion of use case scenarios, see Resources. )

Protocols in the framework

The protocol lies between the framework and its exchangeable components called aggregates. Understanding the interactions required by the framework can help you develop new aggregates. UML sequence diagrams are often used to document these interactions.

Sub-system

Large projects are broken down into smaller and manageable parts, called subsystems. The interface between subsystems is critical to integrating them into a larger whole (that is, the system). UML sequence diagrams are used to specify the interaction between classes on subsystem boundaries.

Class

Some classes, such as Socket and InetAddress, require a complex sequence of method calls in order to interact correctly. These sequences make up the protocols used to interact with such a class or group of classes. UML sequence diagrams can be used to describe the use of a class or a set of interacting classes, thus describing the protocols required for interaction.

Method logic

UML sequence diagrams are excellent in recording method logic. In fact, some CASE tools automatically generate a sequence diagram whenever the Java method is given. Sequence diagrams can be used to design future methods or to document the process of existing methods.

These are all the contents of the article "sample Analysis of UML sequence diagrams in Java Modeling". Thank you for reading! Hope to share the content to help you, more related 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.