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

This article shares the content of case analysis on UML business modeling. Xiaobian thinks it is quite practical, so share it with everyone for reference. Let's follow Xiaobian and have a look.

In the previous section, we analyzed the requirements of the library management system and drew a use case diagram as follows:

Figure 1: System Use Case Diagram

UML business modeling examples can have a general understanding of system functions through use case diagrams. For complex systems, we can combine IDEF methods to describe system functions through hierarchical decomposition and gradual refinement. For use case diagrams, it is recommended not to draw too complex, especially the relationship between use cases, because complex use case diagrams not only do not allow better communication between requirements analysts and customers, but create a communication barrier.

The next step is to compile the detailed description of each use case. The main information of the use case description includes: use case name, number, short description of the use case, participants of the use case, management with other use cases, preconditions for starting the use case, post-conditions after the end of the use case, input and output of the use case, execution event flow of the use case, etc. In a real project, we don't have to be exhaustive, but tailor the use case description to the actual situation. There are several important pieces of information that cannot be reduced: use case name, description, inputs, outputs, execution event flow, and participants. In addition, if the actual situation requires, you can also use MS Visio and other tools to draw a schematic diagram of the interface.

As mentioned in the example above, we describe each use case in detail and establish the functional use case model of the current system. Requirements communication and analysis is an iterative process, through continuous communication with users, and finally reach a consensus understanding of the target system. If the user confirms the results of the requirements analysis, usually after the requirements specification, the project begins to enter the system analysis design phase, that is, to start constructing the logical model of the target system.

In order for system design to be expressed in terms of structure, organization, and code reuse, the design phase should overlap with the analysis phase for system design planning. Demand is constantly evolving, and design itself drives demand (and vice versa). In the modeling design of library management system, the following three aspects should be paid attention to: the representation of business objects, the implementation of business services, and the organization of user interfaces.

Representation of business objects

In UML business modeling instance library management system, business object is mainly the representation of database and data entity class. When modeling, a static model of the system can be constructed, that is, the system class diagram to represent. The static structure diagram of the library use case is shown below. To illustrate the relationships between classes, the attributes and basic operations of each class are not shown in the following figure.

Implementation of business services

The implementation of business services requires the implementation of various business rules and logics, such as the business logic of loan processing. Each module information entry, modification, deletion, query, etc. The implementation of business rules and logic is basically similar, and there are not many rules to follow. UML is used to model business services. UML sequence diagrams, state diagrams, and activity diagrams can be used. This part of the work is usually done through a series of interactions between classes. UML provides many other types of diagrams to describe systems at a more dynamic level.

Scenario diagrams are particularly useful for B/S system design. Plot diagrams are divided into two types: Collaboration Diagram and Sequence Diagram. Rational Rose, a UML modeling tool, can generate sequence diagrams from collaboration diagrams as well as collaboration diagrams from sequence diagrams. For example, the business process of borrowing books can be described by the following sequence diagram:

The book borrowing process mainly comprises the following steps: an administrator selects a "book borrowing" menu, a dialog box pops up, the administrator inputs book information and user information, the system searches a database, and whether the physical book exists or not; if not, prompt information is displayed, and the use case ends; if not, borrower information exists or not; if not, prompt information is displayed, and the use case ends; otherwise, after the administrator clicks a confirmation button, the book is borrowed to the borrower, and the system stores the borrowing information into the database.

Organization of the user interface

The UI layout diagram in UML business modeling instance can help organize the layout structure of system pages, files and services. In UML, the organization of pages and files can be modeled using Component Diagrams or Class Diagrams. In this system, class diagrams are used to model the interface organization, page structure and various business services are bundled into different regions.

In UML, the architecture of a system is accomplished using a Deployment Diagram. Application deployment planning is useful for planning the entire B/S system. It defines an effective planning and organization of application deployment and can be applied as a pattern to multiple similar B/S systems.

After modeling is complete, developers use UML Case tools such as Rational ROSE to generate the program code framework, modify and supplement the code framework to form the complete code, and can also reverse generate UML models from the code. This ensures consistency between the model and the code.

Testing must be carried out throughout the project cycle, and each phase should be tested with the established model, so as to ensure the quality of development and reduce the risk of development.

Unified Modeling Language (UML) is an epoch-making achievement in the field of international software engineering. It is suitable for describing any type of system with object-oriented technology, and for different stages of system development, from requirement specification description to testing and maintenance after system completion. As software systems grow in scale and complexity, RUP's iterative incremental approach reduces risk and adapts to changing requirements.

In this UML business modeling example, we analyze the requirements of the library management system, apply UML to each stage of system development, establish the requirements model, static model and dynamic model of the system, and follow the core idea and basic principle of Rational Unified Process (RUP), adopt iterative object-oriented analysis and design process driven by use cases and centered on architecture.

Figure 2: Activity Diagram Figure 3: Class Structure Diagram of the Borrowing Section

UML Behavior Diagram

A use case diagram describes a set of use cases and actors (a special class) and the relationships between them.

Interaction diagram is a general term for sequence diagram and collaboration diagram.

a sequence diagram is an interaction diagram that emphasizes the temporal order of messages.

a collaboration diagram is an interaction diagram that emphasizes the structural organization of objects that send and receive messages.

A state diagram shows a state machine consisting of states, transitions, events, and activities.

The activity diagram shows the flow from activity to activity in the system.

Thank you for reading! About "UML business modeling case analysis" this article is shared here, I hope the above content can be of some help to everyone, so that we can learn more knowledge, if you think the article is good, you can share it to let more people see it!

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.