CN110276592B - A microservice system business process variability modeling method and system - Google Patents

Abstract

The invention provides a micro-service system business process variability modeling method and a system, wherein the method comprises the following steps: grouping the service flows; for the business processes in the same group, identifying variation points and variants, and determining the selection relation between the variation points and the variants; establishing a variable business process model based on the selection relation between the variation points and the variations; and selecting variants for each variation point in the variable business process model based on business requirements corresponding to the business processes of the versions, and generating the business process models of different versions. The invention provides a visual modeling method for the business process of the micro-service system and the variability of the business process, the established variable business process model is easy to map to a code with actual execution semantics, the difficulty from business representation to technical realization is reduced, the development efficiency of the micro-service system is improved, the developed micro-service system has high flexibility and adaptability, and the dynamic operation environment and the business requirements can be quickly responded.

Description

A microservice system business process variability modeling method and system

technical field

The present invention relates to the technical field of microservice systems, in particular to a method and system for modeling variability of business processes in microservice systems.

Background technique

In recent years, with the rapid development of technologies such as cloud computing, container virtualization, and DevOps, the microservice architecture is gradually emerging and has become the preferred architecture for developing large-scale software systems. Under a microservices architecture, a software system consists of a set of small services (microservices). These services run independently on different processes and interact with each other through lightweight communication mechanisms (eg, RESTful API). Compared to traditional monolithic architectures, microservice architectures offer the following benefits: increased agility, developer productivity, elasticity, scalability, reliability, maintainability, separation of concerns, and ease of deployment. Due to the significant advantages of the microservice architecture, more and more Internet companies (eg, Google, eBay, Netflix) migrate their applications from the monolithic architecture to the microservice architecture.

The functions implemented by a single microservice are usually very limited, and it is difficult to provide complex functions, so it often cannot meet actual business needs. To provide more complex functionality, microservices need to cooperate with each other. The process of coordinating and organizing multiple services in a certain way to support complex business processes is called service assembly. Through service assembly, services developed at different times and institutions can be integrated together to realize business processes with more complex functions and higher application value.

In order to meet different business requirements, there are usually multiple versions of the business process of the microservice system. For example, different product types may have different sales processes. However, traditional business process modeling languages (UML activity diagrams, EPC, YAWL, and BPMN, etc.) can only describe business processes statically, and usually use two methods to model different versions of the same business process: modeling separately and building together mold. Modeling alone tends to generate a large number of similar business process models, resulting in a lot of duplication and redundancy. Modeling together is prone to a sharp increase in the complexity of the business process model, which is difficult to analyze and maintain. Since the above method does not support variability description, the software system implemented based on business process description lacks flexibility and adaptability, and it is difficult to quickly respond to changing operating environments and business requirements.

In recent years, people have researched business process variability modeling techniques for various business process modeling languages. However, existing business process variability modeling methods are not suitable for describing the variability of business processes in microservice systems for the following reasons:

1. The traditional business process modeling language describes the business process at a high level of abstraction, and cannot accurately describe the business process of the microservice system. It is difficult to directly map the established model to the code with actual execution semantics, which increases from Difficulty from business representation to technical realization.

2. The business process of the microservice system is formed by coordinating and organizing multiple microservices in a certain way, and the existing methods describe the business process from the perspective of a single participant and expand the variability, which is difficult to describe Interaction and variability between multiple microservices.

Contents of the invention

The technical problem to be solved by the present invention is to provide a microservice system business process variability modeling method and system; provide a visual modeling method for the microservice system business process and business process variability, reduce the business process model from From business representation to technical realization, improve the development efficiency of the microservice system, increase the flexibility and adaptability of the developed microservice system, and enable the developed microservice system to quickly respond to the dynamic operating environment and business needs.

In order to solve the above technical problems, the present invention provides a microservice system business process variability modeling method, the method comprising:

Based on the business requirements of the micro-service system to be developed, establish the business process of the micro-service system to be developed, and divide the business processes of different versions corresponding to the same business into the same group;

For business processes in the same group, analyze the commonality and difference between business processes, identify variation points, determine the variants that can be selected under each variation point, and the selection relationship between variation points and variants;

Based on the variants that can be selected under each variation point and the selection relationship between the variation point and the variation, determine the type of each variation point, and establish a variable business process model according to the type of each variation point;

Based on the business requirements corresponding to the business processes of each version, a variant is selected for each variation point in the variable business process model to generate different versions of the business process model.

Further, based on the business requirements of the microservice system to be developed, establish the business process of the microservice system to be developed, and divide the business processes of different versions corresponding to the same business into the same group, including:

Analyzing the business requirements of the microservice system to be developed, and establishing a functional requirement set of the microservice system to be developed based on the business requirements of the microservice system to be developed;

Analyzing the corresponding microservices and their operations according to the set of functional requirements, organizing the microservices and their operations according to the preset business logic, and forming the business process of the microservice system to be developed;

Analyze the business corresponding to each business process, group the business processes, and divide the business processes of different versions corresponding to the same business into the same group.

Further, the variation point represents the location where the change of the business process of different versions occurs; the variation represents an implementation solution of the change, that is, the operation of a microservice.

Further, the selection relationship represents the number of selections of variants associated with the variation points.

Further, the selection relationship includes: selecting one variant, selecting one or more variants, not selecting a variant or selecting one variant, not selecting a variant or selecting one or more variants.

Further, the types of variation points include: mandatory single item variation points, mandatory multi-item variation points, optional single item variation points, and optional multi-item variation points; wherein,

The mandatory single variation point means to select a variation under the variation point; the mandatory multiple variation points means to select one or more variations under the variation point; the optional single variation point means not to select the variation under the variation point. The variant of the variation point or select a variation under the variation point; optional multiple variation points means not selecting the variation under the variation point or selecting one or more variations under the variation point.

Further, the establishment of a variable business process model according to the type of each variation point includes:

For the same business process fragment, it is represented by native BPMN elements;

For different business process fragments, according to the type of the corresponding variation point, use different types of variation point elements to represent, and use the realization relationship element to associate the variation point element with the variation.

Further, based on the business requirements corresponding to each version of the business process, a variant is selected for each variation point in the variable business process model, and different versions of the business process model are generated, including:

For the mandatory single item variation point, replace it with a combination of sending task and receiving task;

For mandatory multiple variation points, replace with one or more combinations of sending tasks and receiving tasks;

For an optional single variation point, if you do not select the variation under the variation point, ignore it, otherwise replace it with a combination of sending task and receiving task;

For multiple optional variation points, if the variation under this variation point is not selected, it will be ignored; otherwise, it will be replaced by one or more combinations of sending tasks and receiving tasks.

Further, the sending task means initiating a request to call a microservice operation; the receiving task means receiving a response from the called microservice operation.

Correspondingly, in order to solve the above technical problems, the present invention also provides a microservice system business process variability modeling system, which includes:

A business process grouping module, the business process grouping module is used to establish the business process of the micro-service system to be developed based on the business requirements of the micro-service system to be developed, and divide the business processes of different versions corresponding to the same business into the same group;

Variation point and variant identification module, the variation point and variant identification module is used for business processes in the same group, analyze the commonality and difference between each business process, identify the variation point, and determine the possible Selected variants, and the selection relationship between mutation points and variants;

A business process variability modeling module, the business process variability modeling module is used to determine the type of each variation point based on the variants that can be selected under each variation point, and the selection relationship between the variation points and the variants, And establish a variable business process model according to the type of each variation point;

A variable business process model customization module, the variable business process model customization module is used to select a variant for each variation point in the variable business process model based on the business requirements corresponding to the business processes of each version, and generate Different versions of business process models.

The beneficial effects of above-mentioned technical scheme of the present invention are as follows:

The present invention establishes the business process of the micro-service system to be developed based on the business requirements of the micro-service system to be developed, and divides the business processes of different versions corresponding to the same business into the same group; for the business processes in the same group, analysis Identify the commonality and difference between business processes, identify variation points, determine the variants that can be selected under each variation point, and the selection relationship between variation points and variants; based on the options available for each variation point , and the selection relationship between variation points and variants, determine the type of each variation point, and establish a variable business process model according to the type of each variation point; based on the business requirements corresponding to each version of the business process, the variable business process Each point of variation in the model selects variants to generate different versions of the business process model.

Compared with the existing technology, on the one hand, the present invention can more accurately describe the business process of the microservice system, and the established business process model is easy to map to the code with actual execution semantics, reducing the difficulty from business representation to technical implementation. The development efficiency of the microservice system is improved; on the other hand, the present invention can describe the variability of the business process of the microservice system, and the microservice system developed according to the variable business process model has better flexibility and adaptability, and can respond quickly Changing operating environment and business needs. This is of great significance to the development and maintenance of large-scale software systems based on microservice architecture.

Description of drawings

Fig. 1 is the metamodel of the microservice system business process variability modeling language VxBPMN4MS provided by the embodiment of the present invention;

FIG. 2 is a schematic flow diagram of a microservice system business process variability modeling method provided by an embodiment of the present invention;

Fig. 3 is the variable business process model of the weather forecast query provided by the embodiment of the present invention;

Fig. 4 is the specific business process model 1 of the weather forecast query provided by the embodiment of the present invention;

Fig. 5 is a specific business process model 2 of the weather forecast query provided by the embodiment of the present invention.

detailed description

In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, the following will describe in detail with reference to the drawings and specific embodiments.

Aiming at the problem that the existing business process modeling method cannot accurately describe the business process of the micro-service system and describe the variability of the business process of the micro-service system, the present invention provides a micro-service system business process variability modeling method and system; Microservice system business process variability modeling language VxBPMN4MS realizes microservice system business process variability modeling.

The microservice system business process variability modeling language VxBPMN4MS provided by the embodiment of the present invention is a variability extension of BPMN, which adds a business process variability description on the basis of describing the static business process of the microservice system, and its metamodel is shown in Figure 1 , each element and the relationship between elements are defined as follows:

1. Collaboration: Indicates the interaction between two or more microservices, and completes a business process through interaction. It has a mandatory attribute id, which represents the unique identification of the variable business process model of the microservice system; two or more participants, representing the operation of the microservice; zero or more message flows, representing the microservice Calls between; there are zero or more realization relationships, which represent the association between a mutation point and its variants.

2. Participant: indicates the operation of the microservice. It has a mandatory attribute id, which represents the unique identifier of the microservice operation; an optional attribute name, which is used to describe the operation of the microservice; an optional attribute application, which represents the name of the microservice, which can be queried by the service registration center Bind to existing microservices; there is an optional attribute operation, indicating the name of the microservice operation, which can be bound to the existing microservice operation by querying the service registry; there is an optional attribute method, indicating the microservice The HTTP request method of the operation; there is an optional attribute path, which indicates the path of the microservice operation; there is an optional attribute request, which indicates the parameters of the microservice operation, and its value satisfies the regular expression "([a-zA-Z][ a-zA-Z_0-9]*,[a-zA-Z]+,(query)|(path);)*", where "[a-zA-Z][a-zA-z_0-9] *" indicates the parameter name, "[a-zA-Z]+" indicates the parameter type, "(query)|(path)" indicates the parameter style; there is an optional attribute response, which indicates the return value of the microservice operation, its value Satisfies the regular expression "([a-zA-Z][a-zA-Z_0-9]*,[a-zA-Z]+)?", where "[a-zA-Z][a-zA -Z_0-9]*" indicates the return value, "[a-zA-Z]+" indicates the return value type; there is a process, which indicates the execution process of the microservice operation.

3. Process: Indicates the execution process of microservice operations. It has a mandatory attribute id, which represents the unique identification of the microservice operation execution process; there are elements such as message start event, message end event, gateway, task and sequence flow (there is and only one message start event and one message end event) .

4. Sequence Flow (SequenceFlow): Indicates the execution sequence between two nodes. It has a mandatory attribute id, which represents the unique identifier of the sequence flow; an optional attribute name, which is used to describe the sequence flow; it has an input node and an output node.

5. Task: Indicates the atomic activity of microservice operations (except for microservice calls). It has a mandatory attribute id, which represents the unique identifier of the task; an optional attribute name, used to describe the task; there is an input sequence flow and an output sequence flow. Use subclasses of Task when you need to represent microservice calls: SendTask and ReceiveTask.

a) Send Task: Indicates a request to initiate a call to a microservice operation. It has an output message stream.

b) Receive Task (Receive Task): Indicates receiving the response of the called microservice operation. It has an input message stream.

6. Message Start Event: Indicates the start of microservice operation. It has a mandatory attribute id, which represents the unique identifier of the message start event; an optional attribute name, which is used to describe the message start event; there is only one output sequence flow, and no input sequence flow.

7. Message End Event: Indicates the end of the microservice operation. It has a mandatory attribute id, which represents the unique identifier of the message end event; an optional attribute name, which is used to describe the message end event; there is only one input sequence flow, and no output sequence flow.

8. Gateway: used to control the execution path of the process. It has a mandatory attribute id, which represents the unique identifier of the gateway; an optional attribute name, which is used to describe the gateway. According to the method of selecting the execution path, the gateway is divided into:

a) Exclusive Gateway: When the process is executed to the exclusive gateway, the first path that meets the conditions is executed, and the other paths are not executed. When the exclusive gateway has one input sequence flow and multiple output sequence flows, it is called an exclusive branch gateway (Exclusive Decision Gateway), and when the exclusive gateway has multiple input sequence flows and one output sequence flow, it is called an exclusive aggregation gateway (Exclusive Decision Gateway). Merge Gateway). They come in pairs, and exclusive gateways with multiple input sequence flows and multiple output sequence flows are not allowed.

b) Parallel Gateway (Parallel Gateway): When the process is executed to the parallel gateway, all paths are executed simultaneously. When a parallel gateway has one input sequence flow and multiple output sequence flows, it is called a parallel branch gateway (ParallelFork Gateway), and when a parallel gateway has multiple input sequence flows and one output sequence flow, it is called a parallel aggregation gateway (Parallel Join Gateway). They come in pairs, disallowing parallel gateways with multiple input sequence flows and multiple output sequence flows.

9. Variation Point: It indicates the position where different versions of the same business process of the microservice system change. At this position, different versions of the business process call different microservice operations. It has a mandatory attribute id, which represents the unique identification of the mutation point; an optional attribute name, used to describe the mutation point; a mandatory attribute async, when the value is "true", it means asynchronously calling the operation of the microservice , when the value is "false", it means that the operation of the microservice is called synchronously. According to the number of variants that can be selected under the mutation point (each variant represents an implementation of the change, that is, the operation of a microservice), the variation points are divided into:

a) Mandatory Single Variation Point (MS): Indicates selecting a variant under the variation point, that is, calling a microservice operation.

b) Mandatory multiple mutation points (MM): Indicates the selection of one or more variants under the mutation point, that is, the operation of calling one or more microservices.

c) Optional Single Variation Point (OS): Indicates not to select a variation under this variation point or to select a variation under this variation point, that is, not to call an operation of a microservice or to call an operation of a microservice.

d) Optional Multiple Variation Point (OM): Indicates not to select the variation under the variation point or to select one or more variations under the variation point, that is, not to call the operation of the microservice or to call one or more microservices The operation of the service.

10. Message Flow: Indicates the transfer of messages between two microservices. It has a mandatory attribute id, which represents the unique identifier of the message flow; an optional attribute name, which is used to describe the message flow. When invoking the operation of the microservice, the message flow exists in pairs, connecting the sending task of the microservice consumer to the message start event of the microservice provider and connecting the message end event of the microservice provider to the reception of the microservice consumer Task.

11. Realization relationship (IR): indicates the association between the variation point and the corresponding variant. It has a mandatory attribute id, which represents the unique identification of the realization relationship; an optional attribute name, which is used to describe the realization relationship. It connects the mutation point to the variant's message start event.

In addition, the graphic representation of the mandatory single variation point is a solid-line diamond embedded in "S", the graphic representation of the mandatory multiple variation points is a solid-line diamond embedded in "M", and the graphical representation of the optional single variation point is A dashed diamond embedded in an "S", the graphical representation of an optional multivariate point is a dashed diamond embedded in an "M", and the graphical representation of a realization relationship is a solid line beginning with a solid diamond and ending with an arrow.

The scheme of the present invention is further described below with the mode of specific embodiment:

first embodiment

As shown in FIG. 2, this embodiment provides a method for modeling variability of business processes in a microservice system, the method including:

S101, based on the business requirements of the micro-service system to be developed, establish the business process of the micro-service system to be developed, and divide the business processes of different versions corresponding to the same business into the same group;

It should be noted that the above steps are specifically:

Analyze the business requirements of the microservice system to be developed, and establish the functional requirement set of the microservice system to be developed based on the business requirements of the microservice system to be developed;

Analyze the microservices and their operations that need to be used according to the set of functional requirements, organize each microservice and its operations according to certain business logic, and form the business process of the microservice system to be developed;

Analyze the business corresponding to each business process, group the business processes, and divide the business processes of different versions corresponding to the same business into the same group; that is, divide similar business processes into the same group; among them, similar business processes have similar business rules/goals.

S102. For the business processes in the same group, analyze the commonality and difference among the business processes, identify the variation points, determine the variants that can be selected under each variation point, and the selection relationship between the variation points and the variants;

It should be noted that the mutation point is an abstraction of the position where the change occurs. In different versions of the same business process in the microservice system, what changes is the microservice operation to be called. A variant is an abstraction over alternatives to change. A variation point can contain multiple variants, and each variant is an implementation of business logic in a specific scenario, providing the same function. A selection relationship defines the number of choices for a variant associated with a variation point, and includes four basic types: select a variant, select one or more variants, select no variant or select a variant, select no variant, or Select one or more variants.

S103, based on the variants that can be selected under each variation point, and the selection relationship between the variation point and the variation, determine the type of each variation point, and establish a variable business process model according to the type of each variation point;

It should be noted that the above steps are to express the business processes in the same group with VxBPMN4MS to build a variable business process model. The same business process fragments are represented by native BPMN elements, while different business process fragments use different types of variation point elements according to the relationship between variation points and variants, and use realization relationship elements to associate them.

S104. Based on the business requirements corresponding to the business processes of each version, a variant is selected for each variation point in the variable business process model, and different versions of the business process model are generated.

It should be noted that the above steps are based on the specific needs of the microservice system and the user's preferences, select a variant for each variation point under the variable business process model, and derive a specific business process model. For a mandatory single variation point, replace it with a combination of sending tasks and receiving tasks; for mandatory multiple variation points, replace it with a combination of one or more sending tasks and receiving tasks; for an optional single variation point, use a combination of sending tasks and receiving tasks A combination of tasks to replace or ignore; for optional multivariate points, replace or ignore with a combination of one or more sending tasks and receiving tasks.

In the following, with reference to FIGS. 3 to 5 , taking a weather forecast query microservice system as an example, the microservice system business process variability modeling method provided in this embodiment will be described in detail.

Due to the diversity of users, there are multiple versions of the business process of weather forecast query. For example, a certain version of the business process BP ₁ obtains weather forecast data based on the input names of Chinese provinces/municipalities and cities, while another version of the business process BP ₂ obtains English weather based on the input English foreign country names and city names Forecast data, etc. Therefore, two microservices, weather forecast and text translation, are needed. The weather forecast microservice MS ₁ provides four operations: the first operation OP ₁ is supported by the names of Chinese provinces and municipalities and their corresponding ids; the second operation OP ₂ is supported by the names of foreign countries and their corresponding ids ; The third operation OP ₃ obtains the supported city name and its corresponding id according to the input Chinese province/municipality/foreign country name or id; the fourth operation OP ₄ obtains the corresponding weather forecast according to the input city name or id data. The text translation microservice MS ₂ provides two operations: the first operation OP ₁ translates the input Chinese text into English text; the second operation OP ₂ translates the input English text into Chinese text.

According to the above description, the functions implemented by a single microservice are very limited and cannot meet the actual business needs, so they need to be assembled to support complex business processes. For BP ₁ , OP ₁ , OP ₃ and OP ₄ of MS ₁ need to be assembled sequentially, while for BP ₂ , OP ₂ of MS ₂ , OP ₂ , OP ₃ , OP ₄ and MS ₂ of MS ₁ need to be assembled sequentially OP ₁ assembled.

Analysis of BP ₁ and BP ₂ identified three mutation points and corresponding variants. At the first variation point, the OP ₂ of MS ₂ may be called, or the operation of the microservice may not be called; at the second variation point, the OP ₁ of MS ₁ may be called, or the OP ₂ of MS ₁ may be called, or both Call; at the third point of variation, OP ₁ of MS ₂ may be called, or the operation of the microservice may not be called.

According to the analysis results, VxBPMN4MS is used to model the variability of the business process of weather forecast query, and a variable business process model of weather forecast query is constructed, as shown in Figure 3. Wherein, since OP ₁ , OP ₂ , OP ₃ and OP ₄ of MS ₁ and OP ₁ and OP ₂ of MS ₂ are used, they are represented by pools respectively. Because both BP ₁ and BP ₂ use the OP ₃ and OP ₄ of MS ₁ , the combination of the send task and the receive task is used to represent their invocation, and because the invocation is synchronous, they are directly connected. In addition, because at the first variation point, the OP ₂ of MS ₂ may be called, or the operation of the microservice may not be called, so an optional single item variation point is used to represent it; at the second variation point, the OP ₁ of MS ₁ may be called, and also It is possible to call OP ₂ of MS ₁ , or both, so it is represented by multiple mandatory variation points; at the third variation point, OP ₁ of MS ₂ may be called, or the operation of the microservice may not be called, so it is possible to use Menu item variation point representation.

According to the description of BP ₁ , no variation is selected at the first variation point, OP ₁ of MS ₁ is selected at the second variation point, and no variation is selected at the third variation point, and a specific business process model is derived, as shown in Figure 4 Show.

According to the description of BP ₂ , OP ₂ of MS ₂ is selected at the first variation point, OP ₂ of MS ₁ is selected at the second variation point, and OP ₁ of MS ₂ is selected at the third variation point to derive a specific business process model, As shown in Figure 5.

second embodiment

This embodiment provides a microservice system business process variability modeling system, the system includes:

A business process grouping module, the business process grouping module is used to establish the business process of the micro-service system to be developed based on the business requirements of the micro-service system to be developed, and divide the business processes of different versions corresponding to the same business into the same group ;

Variation point and variant identification module, the variation point and variant identification module is used for business processes in the same group, analyze the commonality and difference between each business process, identify the variation point, and determine the possible Selected variants, and the selection relationship between mutation points and variants;

A business process variability modeling module, the business process variability modeling module is used to determine the type of each variation point based on the variants that can be selected under each variation point, and the selection relationship between the variation points and the variants, And establish a variable business process model according to the type of each variation point;

A variable business process model customization module, the variable business process model customization module is used to select variants for each variation point in the variable business process model based on the business requirements corresponding to the business processes of each version, and generate different versions business process model.

The microservice system business process variability modeling system in this embodiment corresponds to the microservice system business process variability modeling method in the first embodiment above; wherein, the microservice system business process variability modeling system The functions realized by each module correspond one-to-one to each process step of the method in the above-mentioned first embodiment, so details are not repeated here.

The present invention establishes the business process of the micro-service system to be developed based on the business requirements of the micro-service system to be developed, and divides the business processes of different versions corresponding to the same business into the same group; for the business processes in the same group, analysis Identify the commonality and difference between business processes, identify variation points, determine the variants that can be selected under each variation point, and the selection relationship between variation points and variants; based on the options available for each variation point , and the selection relationship between variation points and variants, determine the type of each variation point, and establish a variable business process model according to the type of each variation point; based on the business requirements corresponding to each version of the business process, the variable business process Each point of variation in the model selects variants to generate different versions of the business process model.

Compared with the existing technology, on the one hand, the present invention can more accurately describe the business process of the microservice system, and the established business process model is easy to map to the code with actual execution semantics, reducing the difficulty from business representation to technical implementation. The development efficiency of the microservice system is improved; on the other hand, the present invention can describe the variability of the business process of the microservice system, and the microservice system developed according to the variable business process model has better flexibility and adaptability, and can respond quickly Changing operating environment and business needs. This is of great significance to the development and maintenance of large-scale software systems based on microservice architecture.

In addition, it should be noted that those skilled in the art should understand that the embodiments of the embodiments of the present invention may be provided as methods, devices, or computer program products. Accordingly, embodiments of the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, embedded processor, or other programmable data processing terminal processor to produce a machine such that instructions executed by the computer or other programmable data processing terminal processor produce instructions for A device for realizing the functions specified in one or more procedures of a flowchart and/or one or more blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the The instruction means implements the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram. These computer program instructions can also be loaded into a computer or other programmable data processing terminal equipment, so that a series of operational steps are performed on the computer or other programmable terminal equipment to produce computer-implemented processing, thereby The instructions executed above provide steps for implementing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

While preferred embodiments of the present invention have been described, additional changes and modifications can be made to these embodiments by those skilled in the art once the basic inventive concept is appreciated. Therefore, the appended claims are intended to be construed to cover the preferred embodiment and all changes and modifications which fall within the scope of the embodiments of the present invention.

It should also be noted that in this document, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or terminal device comprising a series of elements includes not only those elements, but also other elements not expressly listed, or elements inherent in such process, method, article or terminal equipment. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or terminal device comprising said element.

The above description is a preferred embodiment of the present invention, it should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, these improvements and modifications It should also be regarded as the protection scope of the present invention.

Claims (5)

1. A micro-service system business process variability modeling method is characterized by comprising the following steps:

establishing a service flow of the micro service system to be developed based on the service requirement of the micro service system to be developed, and dividing the service flows of different versions corresponding to the same service into the same group;

for the business processes in the same group, analyzing the commonality and the difference among the business processes, identifying variation points, determining selectable variants under each variation point and the selection relation between the variation points and the variants;

determining the type of each variation point based on the selectable variation under each variation point and the selection relation between the variation points and the variations, and establishing a variable business process model according to the type of each variation point; the method comprises the following steps that a micro-service system business process variability modeling language VxBPMN4MS is adopted to realize micro-service system business process variability modeling, the micro-service system business process variability modeling language VxBPMN4MS is variability extension of BPMN, and business process variability description is added on the basis of describing micro-service system static business processes;

selecting a variant for each variation point in the variable business process model based on business requirements corresponding to business processes of various versions, and generating business process models of different versions;

the variation points represent positions where the business process variation of different versions occurs; the variant represents one implementation of the change, namely the operation of one microservice;

wherein the selection relation represents a selected number of variants associated with a variation point;

wherein the selection relationship comprises: selecting a variant, selecting one or more variants, not selecting a variant, or selecting a variant, not selecting a variant, or selecting one or more variants;

wherein, the establishing of the variable business process model according to the type of each variation point comprises the following steps:

for the same business process segment, the original BPMN element is used for representing;

for different business process segments, expressing the variant point elements of different types according to the types of the corresponding variant points, and associating the variant point elements with the variants by using an implementation relation element;

the generating of the business process models of different versions by selecting the variant for each variation point in the variable business process model based on the business requirement corresponding to the business process of each version comprises:

for the necessary list item variation point, a combination of a sending task and a receiving task is used for replacing;

for the necessary multiple variation points, one or more combination of sending task and receiving task are used for replacing;

for the selectable single variation point, if the variation under the variation point is not selected, ignoring the variation, otherwise, replacing the variation with a combination of a sending task and a receiving task;

for an optional plurality of variation points, if a variation under the variation point is not selected, it is ignored, otherwise it is replaced with a combination of one or more sending tasks and receiving tasks.

2. The method for modeling the variability of the business process of the microservice system according to claim 1, wherein the step of establishing the business process of the microservice system to be developed based on the business requirements of the microservice system to be developed, and dividing the business processes of different versions corresponding to the same business into the same group comprises:

analyzing the service requirement of the micro service system to be developed, and establishing a function requirement set of the micro service system to be developed based on the service requirement of the micro service system to be developed;

analyzing the corresponding micro-services and the operation thereof according to the function demand set, and organizing the micro-services and the operation thereof according to preset service logic to form a service flow of the micro-service system to be developed;

and analyzing the service corresponding to each service flow, grouping the service flows, and dividing the service flows of different versions corresponding to the same service into the same group.

3. The microservice system business process variability modeling method of claim 1, wherein the types of variation points include: the optional single variation point, the optional multiple variation point, the optional single variation point and the optional multiple variation point; wherein,

the option-required variation point represents that a variation under the variation point is selected; the mandatory multiple variation points represent one or more variants under the variation points selected; an optional single variation point means that the variant under the variation point is not selected or one variant under the variation point is selected; an optional plurality of variation points means that no variant under the variation point is selected or that one or more variants under the variation point are selected.

4. The microservice system business process variability modeling method of claim 1, wherein the send task represents a request to initiate a call to a microservice operation; the receive task represents receiving a response to the invoked microservice operation.

5. A micro-service system business process variability modeling system, comprising:

the business process grouping module is used for establishing the business process of the micro service system to be developed based on the business requirements of the micro service system to be developed and dividing the business processes of different versions corresponding to the same business into the same group;

the variation point and variant identification module is used for analyzing the commonality and the difference among the business processes in the same group, identifying variation points, determining selectable variants under each variation point and the selection relation between the variation points and the variants;

the business process variability modeling module is used for determining the type of each variation point based on the selectable variation under each variation point and the selection relation between the variation points and the variations, and establishing a variable business process model according to the type of each variation point; the method comprises the following steps that a micro-service system business process variability modeling language VxBPMN4MS is adopted to realize micro-service system business process variability modeling, the micro-service system business process variability modeling language VxBPMN4MS is variability extension of a BPMN, and business process variability description is added on the basis of describing a micro-service system static business process;

the variable business process model customizing module is used for selecting a variant for each variation point in the variable business process model based on business requirements corresponding to business processes of various versions, and generating business process models of different versions;

the change points represent positions where business process changes of different versions occur; the variant represents an implementation of the change, i.e. the operation of one microservice;

wherein the selection relation represents a selected number of variants associated with a variation point;

wherein the selection relationship comprises: selecting a variant, selecting one or more variants, not selecting a variant, or selecting a variant, not selecting a variant, or selecting one or more variants;

wherein, the establishing of the variable business process model according to the type of each variation point comprises the following steps:

for the same business process segment, the original BPMN element is used for representing;

for different business process segments, expressing the variant point elements of different types according to the types of the corresponding variant points, and associating the variant point elements with the variants by using an implementation relation element;

the variable business process model customizing module is specifically used for replacing a necessary option change point by a combination of a sending task and a receiving task; for the necessary multiple variation points, replacing by one or more combination of sending task and receiving task; for the selectable single variation point, if the variation under the variation point is not selected, ignoring, otherwise replacing by a combination of a sending task and a receiving task; for the optional multiple variation points, if the variation under the variation point is not selected, it is ignored, otherwise it is replaced by one or more combinations of sending tasks and receiving tasks.

Images