Business use case diagram of EA Business Modeling Practice

This article focuses on business modeling practices, as well as the modeling tools EA Primary use process log.

Previous documents have been written to describe the business modeling from different angles, but the rationale and the norm are still not at a glance. During the Spring Festival, when I read the first few chapters of the Software method, there is a resonance: misunderstanding everywhere, through the UML normative communication environment, is the lesson of hard sweat.

According to the book View and answer questions are as follows:

Business Modeling: Describe the systems within the Organization (human flesh systems, mechanical systems, computer systems ...). How to collaborate enables organizations to provide valuable services to other organizations. The new system is simply a part that the organization buys for its own internal redesign in order to provide better service to the outside. Organizations to introduce a software system, and recruit a new employee no essential difference. If you can learn to use business modeling to derive the needs of a new system, rather than taking a head-on demand, false "demand changes" will be greatly reduced.

Requirements: focus on the boundaries of the system to be developed, detailing the performance that the system must have to sell-function and performance. The significance of this skill is to force us to think from the perspective of "selling" what is the stakeholder (stakeholder) cares about, the immutable contract, which is not, to prevent the "do" pollution "sell". The result of the demand workflow-the requirement specification is the convergence point of "sell" and "do".

What problems the organization is going to solve.

For the organization to provide process management, process reengineering services for the organization of Office process capacity, execution, efficiency to provide management support services.

in order to solve the organizational problem, what functions and performance should be provided by the system to be developed.

Provide localized, personalized BPM services, provide rapid development process support (within 5 business days), and provide management innovation support services for the organization through a comprehensive lifecycle of processes (process definition and process instances).

1. Research object and business use case diagram

The research object of this practice is the business process of office management.

The business use case model is a model that describes the expected functionality of the business. As a core input model, the business use case model is used to determine the individual roles and deliverables of an organization.

Figure 1

According to the business process of office management, the stakeholders have Office management staff, process management staff (a subset of the office management staff, which is a professional management process personnel), process developers (operations and maintenance personnel), system builders, and business use cases are concerned about the main stakeholders are office managers, process management personnel, Process developers, i.e. business performers.

There are arrows that point from the performer to the use case, and the arrows point from the use case to the performer. The former performer is called the main performer of the use case, and the latter is called the secondary performer of the use case.

1, as described in the easy-to-expand core model of Office process Management (1th Edition), the use case in this diagram is to organize business modeling use cases, answer the real core needs of the organization, not People's daily view of the tariff approval process, labor leave process ..., It is a process management competency platform that supports rapid development processes and enables management innovation.

Please see the next article for requirements and functions.

2. Modeling with EA

Enterprise Architect is a platform based on UML standards that integrates efficient modeling and visualization with design. It has a full tracking capability from mind mapping, to business requirements, to software design, to deployment.

1. Create a project

Using the Model Wizard, select Use case, and others are selected according to the actual situation.

Figure 2

2. Subcontracting Management

Create Business Group Packages (package) under the use case model

Figure 3

Figure 4

The results are as follows:

Figure 5

3. Create a use case diagram (Diagram)

Figure 6

The graphics type selects use cases.

1) first determine the boundary of the study case object

Figure 7

Drag "boundary" into the use case diagram and define it with the name "process Management".

Figure 8

The resulting boundary is as shown.

Figure 9

2) Add business Performer

Drag the "actor" into the use case diagram, named "Office Staff", and press set to "Business Actor".

Figure 10

The results are as follows:

Figure 11

3) Adding Use cases

Drag-and-drop "use cases" into the case diagram. Pop up the Use Case Definition window as shown, and enter the name of the use case as "request".

Figure 12

Generate the graphic shown below.

Figure 13

4) Add an association line

Select the "Use Case relationships", "Associate" line in the tool box, click the "Office personnel" actor and drag and drop the mouse button to the "Application" (associated ghost) and release the

Figure 14

Figure 15

Mouse double-click on the Association line (solid line), pop-up Correlation line Definition window.

Figure 16

In the pop-up window, define the relationship between the business performer and the use case by selecting Define Association line type "stereotype", in this case, "Source->destination" is selected.

Figure 17

Figure 18

The use case diagram shown in the final 1.

References and excerpts from:

"Software Method" Umlchina Pangayu 2012.11

Easy-to-expand core model of Office process Management (1th edition) Sho Yongwei 2015.1

Business use case diagram of EA Business Modeling Practice