Effective business modeling with UML (compile)
- Describe business use cases and their implementation herein from 9CBS
Most software development practitioners know that UML is very good when modeling the real world. This feature can effectively help analysts and customers communicate. Some teams that wish to use business modeling often have some empirical issues, such as: 1, when do you really need business model? When is the use case model exists independently?
2. What UML graphics I can use when I use an accurate business modeling? How do I know if I use a sequential map or interaction. Is there an example?
3. How do business models involve other models (such as domain models, use case models, etc.)? How do I organize these models?
Unfortunately, the focus of this article focuses on the application of UML for business modeling, and rarely compares business modeling and system modeling. This will make the user and analysts feel discouraged by using UML business modeling. This paper mainly tells the relationships through an example. This example is mainly used to improve the process of a business, mainly involving IT departments, legal counsels, corporate architects, project managers.
1. The first step in this simple example is the first step in this simple example is to complete the business case model overview. As shown, there are two business leads and two business use cases. We summarize the business, for example, following: Prepare Tender: Prepare the process of system manual. Select Vendor: Select the seller's process. We summarize the protagonist: End User Manager: The company needs to automatically control the system.
Vendor Manager: The seller's manager. In this example, the core business objective of a new system is refined to two sub-objectives:
Detailed description of the system you want.
Select and evaluate candidates.
1. In this section, let's take a look at how to describe business use cases, although there is a very detailed template for business use cases in RUP, we mainly put energy on basic streams and expansion. The basic stream of Prepare Tender:
The goal of the use case is to determine the bidding document, and the bidding documents can be issued to the candidate seller.
1. Specify the user representative.
2. The user represents the system status.
3, IT department review system statute, and improve it to form bidding documents.
4, the user represents the approved bidding document.
Expansion stream:
1. The system status is invalid. When the IT department finds that demand is too vague, the end user's managers must re-create demand. Then this use will start from the second step, and if the end user manager does not want to continue, it can be terminated.
2, the system already exists. If the IT department finds that the system of this needed system and other departments is very similar, the IT department is submitted to the end user manager. If the end user manager wants to continue looking for a new system, he must write the feature of the system and re-submit the manual, return to the second step, and if the end user manager does not want to continue, it can also terminate.
3, bidding documents and demand regulations conflict. In the fourth step, the end user manager discovers that the bidding documents have problems, it will be rejected, the IT department must re-do it, and the use case continues in the third step.
2. Business use cases are implemented in this section, we have achieved business uses from several aspects.
N is centered on workflow
n with process automation as the center N with information processing as a center
Focus focuses on workflow we have to concentrate on the role of business roles, as shown, PREPARE TENDER has three business roles: The following sequence diagram describes the basic stream of Prepare Tender. The message in the above figure can be mapped to each business role (as shown below). This technology is very similar to the use case analysis. It can be seen that the technology of RUP business modeling is very powerful: the same technique can be used in business modeling and system modeling. Focus focus on process automation Now we are ready to explore business leads and business roles, clear when using business systems and how to use business systems. In our example, we have two business systems, as shown below. TMS is a system that is preparing for bidding and choosing a seller. This is a new system.
CMS is a system that tracks the contract, exacerbated.
In RUP, the guidelines for business object modeling can define a new generic icon for the Business System, in which we will use the Business Role icon to represent the Business System. There will be a new icon in the new UML business modeling specification.
The following sequence diagram describes the implementation of the Prepare Tender's basic stream, which includes a service system for demand. The message in the above figure can map the responsibility of the business role. As shown below: From the above figure, you can get system use cases, as shown below: Focus focus on information processing now let us see the implementation of business use in information processing, this is how many business entities. After analysis, we will get four business entities, as shown below:
The following figure is the interaction map for implementing Prepare Tern (focus on information processing).
The above two graphs can be mapped to the duties of each board, as shown below:
The figure below is a simplification of the above figure.
4 Conclusion
Software systems are developed to achieve business goals, but users, analysts, and developers often live in different worlds; they have different views and different jars. Communication barriers between groups have led to a lot of intense debate in explaining various system requirements. It is representative that their changes are not because users have changed their ideas, but because the initial demand needs to be purified.
