Ii. Business Process Model (BPM)

 

1. BPM Overview

Business Process Model (BPM) is a conceptual model that describes business logic and rules in detail from the perspective of business personnel, the process, process, message, and collaboration protocols between one or more start points and end points are displayed using flowcharts. BPM can be used to describe system behaviors and requirements. It can use graphs to represent the conceptual organizational structure of objects and then generate required documents. As a conceptual module, BPM is suitable for System Analysis of application systems and completes System Requirement Analysis and logic design. Relationship between BPM and other powerdesigner modules

 

1.1 powerdesigner BPM consists of three stream graphs:

1) process hierarchydigraphs: identifies system functions in a hierarchical manner.

2) Business process flow chart: used to analyze the specific implementation mechanism of A/group process.

3) process service flow chart (process service digraphs): Describes the business flow chart in the form of business services.

 

1.2 create a BPM object

(1) create a package

(2) create Business Rules

(3) create a start point

(4) creation process

(5) create an organizational unit/organizational unit dashboard

(6) creation process

(7) define the Message format

(8) create resources

(9) Resource creation process

(10) Create an endpoint

Ii. Example 2.1 create BPM

File --> New Model

 

Note that the precess language is selected here. The default value is analysis. In palette, the organizational unit is organization unit routing Lane. The following is a detailed description.

 

2.2 set BPM configuration options

Tools → model option, or right-click the menu in the flowchart window and select the model option command.

 

2.3 modify BPM attributes

Three methods:

(1) model → model Properties

(2) Right-click the menu Properties command in the Workspace

(3) Right-click the Properties command in the list on the left.

 

 

BPM attribute list

Attribute name	Description	Length
Name	Model name	254 characters
Code	ModelCode	254 characters
Comment	Model comment	-
Filename	Model file storage path.This item is null if it has not been saved	-
Author	Author	254 characters
Process Language	Processing language
Version	Model Version Number	-
Default digoal	Flow chart opened by default when the model is opened

 

2.4 Business Rules

Business Rules are specific conditions that information systems must comply with or must be built according to business needs. The system must comply with this business rule, just as it complies with laws and regulations, customer requirements, or internal regulations.

 

2.4.1 create Business Rules

Model → business rules.

 

Add Rules:

 

Modify rule attributes:

 

(1) Description of the "general attributes" tab

This tab contains the attributes name, code, comment (description), and type (type ). You can select the following types of attributes.

Name	Description
Constraint (constraint)	Additional checks on the value, the restrictions will be used in PDM and databases.For example, "the project start date must be earlier than the end date ".
Definition)	Attributes of objects in information systems, such as "customers are identified by names and addresses"
FACT (fact)	The fact in the information system, "If a customer can fill in one or more orders"
Formula (formula)	Calculation formula used in the system. For example, "the total order price is the sum of the unit price of each order"
OLC constraint (Object constraint language)	Is a UML Expression Language used to define additional constraints on objects.
Requirement (requirement)	Specific functions in the system, such as "sales losses cannot exceed 10%"
Validation)	The limit value in the system, such as "the total price of a customer's order cannot be greater than its credit value"

 

(2) expression tab or OLC constraint tab.

If you select OLC constraint as the type attribute, the "Object constraint language" tab appears; otherwise, the "expression attributes" tab appears. For expression attributes, each business rule can contain the following two types of expressions.

Server: Apply business rules to databases.

Client: Mainly used for document preparation.

 

2.4.2 apply rules in BPM

Right-click the object to which you want to specify the rule, set the attribute, and select more. You can see the option of rule.

 

 

 

2.5 process BPM 2.5.1 create a new business processing Flowchart

Business Process Flow Chart (BPD) represents the relationship between business processes. What is important is the data process in the process. You can define multiple business processing flowcharts in a model or package. Each flowchart designs a business processing process for each other.

Generally, when we create a BPM module, a BPD is created by default. We can rename this BPD or create a new BPD.

 

Two methods:

(1) view → digoal → new digoal

(2) Right-click BPM and choose new> businessprocess digoal.

 

 

2.5.2 define the start point

Start is the starting point of the entire processing process expressed by BPD, indicating the external endpoint of the processing process and processing process.

Note: Multiple BPD can be defined in one bpm, So multiple start points can be created in one model or package.

 

2.5.2.1 create start

Two methods:

(1) Click the start icon in the toolbar.

(2) model → starts command

 

2.5.2.2 modify the starting point attribute

Three methods:

1) double-click the icon to open the "Start property" window.

2) Right click → Properties

3) run the model → starts command to open the start point list.

 

2.5.2.3 display the default BPM start point name

By default, the start point name is not displayed, and only the code of the start point is displayed in BPM. It is difficult to intuitively understand the meaning of the start point.

(1) Select the tools> display preferences command to open the display preferences window.

(2) on the left side of content --> Start, select the name check box.

 

2.5.3 define the processing process

The processing process can be considered as an action to achieve a certain goal. Each processing process has at least one input stream and one output stream.

 

2.5.3.1 creation process

Select process in the toolbar, and click Create process in the workspace.

 

2.5.3.2 processing process attributes

Double-click the process object.

 

Attributes of a processing process include name, code, comment, stereotype, organization unit, and composite status. These attributes can be defined in the Properties window.

(1) Board

A board is a user-defined value, which comes from the original object. You can use a panel to expand the semantics of an object without changing its structure.

(2) organizational unit

An organizational unit indicates that an organizational unit is related to a specific process.It can represent a system, a server, an organization, or a user.

(3) Compound Processing Process

Select the decomposed process (below) Single-choice button to indicate that this process is a composite process, indicating that a subprocess diagram of the decomposition process is created during the process.

A composite process is a child process that describes the behavior of a parent process. It can be infinitely divided into multiple child processes. Sub-processes do not need to be further decomposed.

 

2.5.4 define organizational unit

An organizational unit is an organization (which can be a company, system, service, organization, user, or role) responsible for the processing process, or a business partner who uses a more advanced processing process.

 

In the toolbar, click the Organization Unit Lane icon or organization unit icon ". The icons that can be selected depend on the processing language used by BPD.

 

 

 

The language used here is analysis. Double-click to view its properties:

 

Note that organization unit routing Lane is mutually exclusive with organizaion unit and role association, that is, only one of them can be used.

The switching between them is as follows:

 

Right-click the workspace and you will see an enable routing Lane mode. After swinlane mode is disabled, organization unit becomes available. The organization unit processing language is Data Flow digoal.

 

 

 

 

Double-click to view properties:

 

2.5.5 define the process

(1) Create

 

 

(2) double-click to View Properties

 

Attributes of a process include name, code, comment, source (start object), destination (end object), stereotype, transport (data stream transmission mode), and flow type (process type) and the message format (Data Exchange Format) during the processing. These attributes can be modified in the "Property definition" window.

 

Where:

(1) Data Stream Transmission Mode

This attribute is mainly used for document compilation and provides information about the data stream transmission mode. The transport drop-down list box provides three alternative methods: fax, email, and phone. You can also directly enter other transmission methods.

(2) process type

You can directly enter the process type or select the process type:

1) Success: normal process

2) Timeout: timeout Process

3) technical error: technical error process

4) Business error: Business error process

5) Compensation: supplemental process.

6) can be customized

(3) Message format

You can select the following message format types:

None: indicates that there is no data exchange between processes.

Undefined: the default option, indicating that the Message format will be defined later.

 

You can click the "new" icon next to the Message format drop-down list box to define the Message format for the process.

 

(4) Process Conditions)

When multiple processes exist, you can select the execution process based on the process conditions. In the process Properties windowCondition TabTo define process conditions, as shown in:

 

Condition has the following parameters:

Alias: process condition Summary (alias ).When the process conditions are complex, you can set the alias attribute so that the alias of the summary can be displayed in the flowchart without the entire complex process conditions.

Editor: process condition details. Conditions used to describe the process.

 

Note: The total alias of the flow chart is displayed next to the flow line. If condition is defined and alias is not specified, all editor information is displayed next to the flow line.

 

2.5.6 define the Message format

The message format defines the data format of the data to be exchanged between two objects in the process.. If there is no data exchange, you do not need to define any message format. The message format can be XML document, XML mode, or parameters that call stored procedures.

In the flowchart, the message format is accompanied by the relevant process. When the Message format is defined in the "process properties" window, the message format is linked to the flowchart, as shown in.

Note: you cannot copy the Message format icon in the flowchart. If you delete the Message format icon, set the Message format attribute of the "process" to "NONE ".

 

The message format can be created using either of the following methods:

(1) select model> Message format command

(2) Use the crate option of the flow attribute to create a crate, for example:

 

 

Message format attributes include name, code, comment, stereotype, type, and Message format. These attributes can be modified in the Properties window. The message format type can be directly input or selected.

DTD: indicates that the Message format type is document type definition)

XML Schema: indicates that the Message format type is an XML model.

Relax NG: A syntax-based XML schema language that can be used to describe, define, and limit XML vocabulary.

 

2.5.7 Define Resources

Resources are similar to data storage. They can be processes such as data, documents, databases, and organization, and can be used for special transactions.

 

(1) create resources

 

(2) define the resource Process

The "processing process" accesses resources through the "resource flow.In the flowchart, use the dotted line with arrows to represent the resource flow.

The resource access method determines the direction of the resource process.

When the "resource process" comes from the "processing process", the resource access method should be "CREATE", "Update", or "delete. Indicates the "resource stream" from the "processing process", indicating that the "processing process" creates, modifies, or deletes resource data.

 

Double-click flow to view attributes:

 

The access method of the resource flow from the "resource" is read, indicating that the "resource" is read by the "processing process", as shown in:

 

When the resource access mode is a combination of read and other access methods (creat, update, and delete), the resource flow chart is marked as a two-way arrow.

 

 

2.5.8 define the end point

The end is the end point of the overall processing process of the business flow chart. Because multiple business processing flows can be used in one model or package, multiple endpoints can be defined in one package or model. You can even define multiple endpoints in the same business flow chart. For example, the endpoints of correct and wrong conditions can be different.

 

 

The endpoint type includes the following options:

1) Success: indicates that the process is terminated normally.

2) Timeout: indicates that the process is terminated due to timeout.

3) Business error: indicates that the process is terminated due to a business logic error.

4) technical error: indicates that the process is terminated due to a technical error.

5) Compensation: supplements the endpoint.

 

 

Example of powerdesigner: