CN107943457B - Workflow modeling method and system for business object - Google Patents
Workflow modeling method and system for business object Download PDFInfo
- Publication number
- CN107943457B CN107943457B CN201711148590.2A CN201711148590A CN107943457B CN 107943457 B CN107943457 B CN 107943457B CN 201711148590 A CN201711148590 A CN 201711148590A CN 107943457 B CN107943457 B CN 107943457B
- Authority
- CN
- China
- Prior art keywords
- name
- param
- tag
- business
- task
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 92
- 230000009471 action Effects 0.000 claims abstract description 7
- 238000012546 transfer Methods 0.000 claims abstract description 6
- 230000008569 process Effects 0.000 claims description 33
- 238000013468 resource allocation Methods 0.000 claims description 15
- 238000013499 data model Methods 0.000 claims description 10
- 230000007704 transition Effects 0.000 claims description 7
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000004891 communication Methods 0.000 claims description 4
- 230000003993 interaction Effects 0.000 claims description 4
- 238000007726 management method Methods 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000000354 decomposition reaction Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000010845 search algorithm Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/067—Enterprise or organisation modelling
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Educational Administration (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a workflow modeling method facing to a business object, which comprises the following steps: s1, discovering a service object in a service flow; s2, modeling the service data of the service object; s3, modeling the business operation for operating the business object; s4, analyzing all states possibly experienced in the life cycle of the business object, modeling the life cycle of the business object, and associating business operation with state transfer action; s5, defining the dependency relationship between the business objects; and S6, completing modeling of the workflow to obtain a service object description file.
Description
Technical Field
The invention relates to the technical field of workflow modeling, in particular to a workflow modeling method and a workflow modeling system facing to business objects.
Background
With the rapid development of internet technology and the coming of the global era, a great number of emerging industries with asynchronous collaboration business characteristics, such as crowdsourcing, emerge in the network society. The subtasks in the crowdsourcing flow are dynamically generated according to flow data, and how many subtasks in the flow are unpredictable in advance. In addition, the parent task needs to be informed after the crowdsourcing subtask obtains the solution, the parent task can destroy the subtask and then decompose the subtask under the condition of unsatisfactory decomposition, and the parent task and the subtask cooperate in an asynchronous mode. The process has the characteristics of unfixed steps, unpredictable process ending time and the like, so that the process can be regarded as an asynchronous cooperative business process with dynamic uncertainty. The existing crowdsourcing platform is realized by hard coding, and hard coding of the type of business process brings many difficulties to development and later maintenance. In an environment where the workflow technology is rapidly spread, in order to further automate the business process, the workflow technology is inevitably required to be used.
At present, traditional workflow modeling methods in the workflow field are largely divided into process-centric, data-centric and process object-oriented.
The workflow modeling methods centered on processes mainly include a program language-based method, a graph-based method, an ECA rule-based method, a logic-based method, and an algebraic method. The graph-based approach is mainly used for comparison, and most of them provide a representation method similar to a state transition graph. Workflow net based methods, Petri net based methods, activity graph based methods, state graph based methods, etc. are all graph based methods. The main characteristic of the modeling method is that the control flow of the whole process is concerned, namely, which activities need to be executed and the execution sequence are realized for realizing a business target, and the data context information is ignored. The main drawbacks of the process-centric modeling approach are two: 1) the business process of dynamically generating new steps according to the data in the running process is difficult to support; 2) for complex business processes, the control flows of all data objects in the process are described with one process model, resulting in a process model that is too large and flat.
The most representative of the data-centered modeling methods is an artifact-centered modeling method. The modeling method models around the life cycle of business data, combines the data with flow operation logic, and explicitly points out the dependency relationship between the control flow and the data object in the process. The modeling process roughly needs to go through the following four steps: 1) finding the artifact, 2) analyzing all possible states of the artifact, 3) modeling the task, and 4) defining the relationship between the artifact and the task. The main disadvantage of the data-centric modeling approach is that the way of collaboration between data objects is not comprehensive enough and asynchronous collaboration is not supported.
With the development of object-oriented technology, some workflow modeling methods for process objects are proposed, which decompose a business process into a plurality of process objects and solve the problem of model scale. However, the process objects are petri net-based and do not reflect the relationship of control flow and data flow. Essentially, such process object-oriented methods do not leave the description of the "state" of an object, and state machines are the best tools for expressing the state of things and for reflecting the behavior of things. Extension of state machine action semantics can task or dynamically create new objects when state transitions occur to the objects. Using the event-driven nature of state machines, asynchronous message communication between different objects can occur by sending events or signals. Object-oriented techniques thus offer the possibility of solving the above-mentioned problems.
Disclosure of Invention
Based on the idea of the object-oriented technology and the workflow modeling technology, the invention provides a workflow modeling method for a business object. The workflow modeling method facing the business object integrates the advantages of the existing workflow modeling method and solves the problem that the existing workflow modeling method does not support the modeling of asynchronous collaborative business processes with dynamic uncertainty.
In order to realize the purpose, the technical scheme is as follows:
a workflow modeling method facing to business objects comprises the following steps:
s1, discovering a service object in a service flow;
s2, modeling the service data of the service object;
s3, modeling the business operation for operating the business object;
s4, analyzing all states possibly experienced in the life cycle of the business object, modeling the life cycle of the business object, and associating business operation with state transfer action;
s5, defining the dependency relationship between the business objects;
and S6, completing modeling of the workflow to obtain a service object description file.
Preferably, in the service object description file, the description mode of the service object is defined by a businessclass tag, which is a top-level tag of the service object description file, and the businessclass tag is expressed as follows:
<businessclass name="" initial="" version="" xmlns="">
</businessclass>
wherein, name represents the unique name of the business object, initial represents the default initial state of the business object, version represents the version number of the business object, and xmlns represents the name space.
Preferably, in the service object description file, the description mode of the service data is defined by a datamodel tag, and a sub-tag of the datamodel tag is data and is used for defining an attribute; the data tag is represented as follows:
<datamodel>
<data id="" expr="" ></data>
<data id="" expr="" ></data>
</datamodel>
where id represents a unique identifier for the attribute, expr represents an initial value for the attribute, which may be null, and the datamodel tag may have multiple data sub-tags.
Preferably, in the service object description file, the description mode of the service operation is defined by operations tags, and there are two kinds of sub tags of the operations tags, which are respectively a task tag defining an atomic task and a subprocess tag defining a subprocess; the task tag is represented as follows:
<task id="" name="" type="" agent="" role="" events="">
<param name="" value=""></param>
<param name="" value=""></param>
</task>
the task management method comprises the steps that id represents a unique identifier of a task, name represents the name of the task, type represents the task type and is divided into a manual task and an automatic task, agent represents an allocation strategy of the task, role represents a resource type for executing the task, events represents all possible event name sets sent to a business object instance for receiving a task result after the task is completed, param represents an input parameter of the task, the name attribute in a param tag represents the parameter name, value represents a parameter value, and the task tag can have a plurality of param sub tags;
in the service object description file, the description mode of the sub-process is defined by a sub-process tag, and the sub-process tag is expressed as follows:
<subprocess id="" name="" src="" events="">
<param name="" value=""></param>
<param name="" value=""></param>
</subprocess>
wherein id represents a unique identifier of the sub-process, name represents the name of the sub-process, src represents the path of the process definition file of the sub-process, events represents all possible event name sets sent to a business object instance receiving an execution result after the sub-process is executed, param represents an input parameter of a task, the name attribute in a param tag represents the parameter name, value represents a parameter value, and the subpacess tag can have a plurality of param sub-tags; the operations tag may contain multiple task sub-tags or subpacesses sub-tags.
Preferably, in the service object description file, the description mode of the association between the service operation and the state transition action is defined by a call tag, and the call tag is expressed as follows:
<call name="">
<param name="" value=""></param>
<param name="" value=""></param>
</call>
the call is used for representing the actual calling of the business operation according to the name of the business operation related to the transfer when the state of the business object is transferred, wherein the name attribute corresponds to the business operation name defined in a task tag or a subparocess tag, and the sub tag param represents the actual parameter transferred to the business operation and corresponds to the task tag with the same name value or the param sub tag in the subparocess tag.
Preferably, in the service object description file, the dependency description mode of the service object is defined by a newbo tag, and the newbo tag is expressed as follows:
<newbo src="" instances="">
<param name="" value=""></param>
<param name="" value=""></param>
</newbo>
the newbo label is used for creating a new business object instance, wherein src represents the path of the business object description file, instances represents the number of business objects to be instantiated, param represents parameters passed to the new business object instance, the name attribute in the param label represents the parameter name, value represents the parameter value, and the newbo label can have a plurality of param sub-labels.
The dependency relationship of the business object is embodied in that the current business object depends on the created business object, and an end event must be sent to the business object creating it when the life cycle of the created business object is over.
Preferably, in the service object description file, the communication event sent between different service objects is defined by a send tag, where the send tag is expressed as follows:
<send event="" mode="">
<param name="" value=""></param>
<param name="" value=""></param>
</send>
the send tag is used for sending an event to the self or other business objects, wherein the event attribute represents the name of the event, the mode represents the propagation mode of the event, the param tag specifies the parameter of the event to be transmitted to the target business object instance, the name attribute in the param tag represents the name of the parameter, the value represents the parameter value, and the send tag can have a plurality of param sub-tags.
Meanwhile, the invention also provides a system for operating the service object description file obtained by the method, which comprises a service object analysis engine, a resource allocation service module and an application subsystem. Wherein:
the business object analysis engine is used for analyzing the business object description file into a business object instance, creating an executor for managing the life cycle of the business object instance, maintaining the dependency relationship among the business objects by using a business object instance tree, and forwarding events among different business objects;
the resource allocation service module receives a task allocation request from the engine and allocates the task to a corresponding resource;
the user application subsystem is a man-machine interaction interface provided for a user, receives the information of the engine to determine the execution state of the current business object, retrieves the to-do work list of each resource instance through the resource allocation service module to execute the task instance, and feeds back the execution result to the engine through an event after the execution is finished.
Compared with the prior art, the invention has the beneficial effects that:
the workflow modeling method facing the business object integrates the advantages of the existing workflow modeling method and solves the problem that the existing workflow modeling method does not support the modeling of asynchronous collaborative business processes with dynamic uncertainty. Meanwhile, the operable system for the modeling method provided by the invention supports the execution of the asynchronous collaborative business process with dynamic uncertainty. Crowdsourcing applications developed on this based system can make the crowdsourcing task decomposition, task resolution, and task merging processes more automated. Based on the system, crowdsourcing application developers only need to pay attention to realizing a human-computer interaction interface and designing a good service object life cycle model, and workflow driving, resource allocation and service operation scheduling are managed by the system, so that the development process of crowdsourcing application is greatly simplified, and the expansibility and maintainability of application are improved.
Drawings
FIG. 1 is a flow chart of a business object oriented workflow modeling method.
FIG. 2 is an exemplary diagram of a business object description file.
Fig. 3 is a schematic diagram of the logical structure of the system.
FIG. 4 is a swim lane diagram of a call service operation.
FIG. 5 is a flow chart for creating a business object.
Detailed Description
The drawings are for illustrative purposes only and are not to be construed as limiting the patent;
the invention is further illustrated below with reference to the figures and examples.
Example 1
The business object refers to an information entity with data information and state change in the business process. The business object encapsulates three major parts: (1) business data that is contextually related to the business object, represented using key-value pairs; (2) the business operation of the business object is divided into an atomic task or a sub-process; (3) and the life cycle model describes the state change of the business object under the driving of the business role executing business operation. The object lifecycle model uses the business data and external events to decide which business operation to perform to process the business logic associated with the subject business object or to communicate a corresponding message to inform other business objects to process the corresponding business logic.
As shown in fig. 1, the present invention provides a workflow modeling method for business objects. As shown in FIG. 2, the business object description file provided by the present invention is based on SCXML single state machine semantic standard extension. As shown in fig. 3, the system provided by the present invention includes a business object parsing engine, a resource allocation service module, a database, and an application subsystem. Wherein:
the business object analysis engine is used for analyzing the business object description file into a business object instance, creating an executor for managing the life cycle of the business object instance, and maintaining the dependency relationship between the business objects by using a business object instance tree;
the resource allocation service module receives a task allocation request from the engine and allocates the task to a corresponding resource;
the database is used for storing the service object description file, the service data and the execution log;
the user application subsystem is a man-machine interaction interface provided for a user, receives the information of the engine to determine the execution state of the current business object, retrieves the to-do work list of each resource instance through the resource allocation service module to execute the task instance, and feeds back the execution result to the engine through an event after the execution is finished.
In the service object description file, the description mode of the service object is defined by a businessclass tag, which is a top-level tag of the service object description file, and the businessclass tag is expressed as follows:
<businessclass name="" initial="" version="" xmlns="">
</businessclass>
wherein, name represents the unique name of the business object, initial represents the default initial state of the business object, version represents the version number of the business object, and xmlns represents the name space. When the business object analysis engine analyzes the businessclass tag, the business object is instantiated into a business object instance, and an executor for managing the life cycle of the business object instance is created.
In the service object description file, the description mode of the association between the service operation and the state transition action is defined by a call label, and the call label is expressed as follows:
<call name="">
<param name="" value=""></param>
<param name="" value=""></param>
</call>
the call is used for representing the actual calling of the business operation according to the name of the business operation related to the transfer when the state of the business object is transferred, wherein the name attribute corresponds to the business operation name defined in a task tag or a subparocess tag, and the sub tag param represents the actual parameter transferred to the business operation and corresponds to the task tag with the same name value or the param sub tag in the subparocess tag. The swim lane diagram of the actual invocation of the business operation is shown in fig. 4, and the work of each specific phase can be expressed as follows:
stage one (distribution stage): the engine analyzes the label < call >, extracts the information in the label and packages the information into an HTTP request, the request is sent to the resource allocation Service module in the form of Web Service, and the resource allocation Service module uses a proper algorithm to place the task into a working list of a proper instance of a specified type of resource;
two stages (execution stage): and entering two stages after the resource allocation is finished. The engine sends a refresh request to the application subsystem to inform that the working list of a certain type of resources has been updated at that time. The application subsystem requests a working list of each instance of the type of resources to the resource allocation service module after receiving the refreshing request and informs each resource instance to process a task of the working list;
three phases (commit phase): the three phases are entered when the resource instance of the application subsystem has finished processing the tasks assigned to it. And the application subsystem generates corresponding events according to the task execution result, packages the events into an HTTP request and sends the HTTP request to the engine. The engine receives the event and then puts the event into an event queue of a business object corresponding to the job task, the life cycle model of the business object triggers corresponding state transition according to the event, and the engine informs the resource allocation service module of completion of the task.
In the service object description file, the dependency description mode of the service object is defined by a newbo tag, and the newbo tag is expressed as follows:
<newbo src="" instances="">
<param name="" value=""></param>
<param name="" value=""></param>
</newbo>
the newbo label is used for creating a new business object instance, wherein src represents the path of the business object description file, instances represents the number of business objects to be instantiated, param represents parameters passed to the new business object instance, the name attribute in the param label represents the parameter name, value represents the parameter value, and the newbo label can have a plurality of param sub-labels. The engine uses a tree of business object instances to manage dependencies between business objects. As shown in fig. 5, a business object parsing engine first obtains a business object description file according to the value of the src attribute in the newbo label, then creates a corresponding business object instance and an executor for managing the life cycle of the instance, and then inserts the unique identifier of the instance, the reference of the parent node, the reference vector of the child node, and the business object instance as a whole into the current business object instance tree, that is, the nodes of the instance tree contain the dependency relationship between the business object instances.
In the service object description file, the communication event sent between different service objects is defined by send tags, and the send tags are represented as follows:
<send event="" mode="">
<param name="" value=""></param>
<param name="" value=""></param>
</send>
the send tag is used for sending the event to other business objects, wherein the event attribute represents the name of the event, the mode represents the propagation mode of the event, the param tag specifies the parameter of the event to be delivered to the target business object instance, the name attribute in the param tag represents the name of the parameter, the value represents the parameter value, and the send tag can have a plurality of param sub-tags.
Each business object instance maintains an event queue. When the engine resolves the send tag, the engine extracts the mode attribute information in the send tag and determines the propagation mode of the event, such as sending the event to a child node, a father node, a brother node, an ancestor, a descendant, a broadcast and the like; and then, using a tree search algorithm to obtain the node position of the target business object on the instance tree, and adding the event into an event queue of the target business object. When there is an event that is not triggered in the event queue, the engine will fetch the event and trigger it to effect a state transition of the business object.
It should be understood that the above-described embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the embodiments of the present invention. Other variations and modifications will be apparent to persons skilled in the art in light of the above description. And are neither required nor exhaustive of all embodiments. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the claims of the present invention.
Claims (7)
1. A workflow modeling method facing to business objects is characterized in that: the method comprises the following steps:
s1, discovering a service object in a service flow;
s2, modeling the service data of the service object;
s3, modeling the business operation for operating the business object;
s4, analyzing all states possibly experienced in the life cycle of the business object, modeling the life cycle of the business object, and associating business operation with state transfer action;
s5, defining the dependency relationship between the business objects;
s6, completing modeling of the workflow to obtain a service object description file;
in the service object description file, the description mode of service operation is defined by operation labels, and the number of the sub-labels of the operation labels is two, namely a task label for defining an atomic task and a subprocess label for defining a subprocess; the task tag is represented as follows:
<task id＝""name＝""type＝""agent＝""role＝""events＝"">
<param name＝""value＝""></param>
<param name＝""value＝""></param>
</task>
the task management method comprises the steps that id represents a unique identifier of a task, name represents the name of the task, type represents the task type and is divided into a manual task and an automatic task, agent represents an allocation strategy of the task, role represents a resource type for executing the task, events represents all possible event name sets sent to a business object instance for receiving a task result after the task is completed, param represents an input parameter of the task, the name attribute in a param tag represents the parameter name, value represents a parameter value, and the task tag is provided with a plurality of param sub tags;
in the service object description file, the description mode of the sub-process is defined by a sub-process tag, and the sub-process tag is expressed as follows:
<subprocess id＝""name＝""src＝""events＝"">
<param name＝""value＝""></param>
<param name＝""value＝""></param>
</subprocess>
wherein id represents a unique identifier of the sub-process, name represents the name of the sub-process, src represents the path of the process definition file of the sub-process, events represents all possible event name sets sent to a business object instance receiving an execution result after the execution of the sub-process is completed, param represents an input parameter of a task, the name attribute in a param tag represents the parameter name, value represents a parameter value, and the subpacess tag has a plurality of param sub-tags; the operations tag comprises a plurality of task sub-tags or subpacesses sub-tags.
2. The business object-oriented workflow modeling method of claim 1, wherein: in the service object description file, the description mode of the service object is defined by a businessclass tag, which is a top-level tag of the service object description file, and the businessclass tag is expressed as follows:
<businessclass name＝""initial＝""version＝""xmlns＝"">
</businessclass>
wherein, name represents the unique name of the business object, initial represents the default initial state of the business object, version represents the version number of the business object, and xmlns represents the name space.
3. The business object-oriented workflow modeling method of claim 1, wherein: in the service object description file, a description mode of service data is defined by a datamodel tag, and a sub-tag of the datamodel tag is data and is used for defining attributes; the data tag is represented as follows:
<datamodel>
<data id＝""expr＝""></data>
<data id＝""expr＝""></data>
</datamodel>
wherein id represents a unique identifier of the attribute, expr represents an initial value of the attribute, and is null, and the datamodel tag has a plurality of data sub-tags.
4. The business object-oriented workflow modeling method of claim 1, wherein: in the service object description file, the description mode of the association between the service operation and the state transition action is defined by a call label, and the call label is expressed as follows:
<call name＝"">
<param name＝""value＝""></param>
<param name＝""value＝""></param>
</call>
the call is used for representing the actual calling of the business operation according to the name of the business operation related to the transfer when the state of the business object is transferred, wherein the name attribute corresponds to the business operation name defined in a task tag or a subparocess tag, and the sub tag param represents the actual parameter transferred to the business operation and corresponds to the task tag with the same name value or the param sub tag in the subparocess tag.
5. The business object-oriented workflow modeling method of claim 1, wherein: in the service object description file, the dependency description mode of the service object is defined by a newbo tag, and the newbo tag is expressed as follows:
<newbo src＝""instances＝"">
<param name＝""value＝""></param>
<param name＝""value＝""></param>
</newbo>
the newbo label is used for creating a new business object instance, wherein src represents a path of a business object description file, instances represents the number of business objects to be instantiated, param represents parameters transferred to the new business object instance, the name attribute in the param label represents a parameter name, value represents a parameter value, and the newbo label has a plurality of param sub-labels;
the dependency relationship of the business object is embodied in that the current business object depends on the created business object, and an end event must be sent to the business object creating it when the life cycle of the created business object is over.
6. The business object-oriented workflow modeling method of claim 5, wherein: in the service object description file, the communication event sent between different service objects is defined by send tags, and the send tags are represented as follows:
<send event＝""mode＝"">
<param name＝""value＝""></param>
<param name＝""value＝""></param>
</send>
the send label is used for sending the event to other business objects, wherein the event attribute represents the name of the event, the mode represents the propagation mode of the event, the param label specifies the parameter of the event transferred to the target business object instance, the name attribute in the param label represents the parameter name, the value represents the parameter value, and the send label has a plurality of param sub-labels.
7. A system for operating the service object description file obtained by any one of the methods of claims 1 to 6, characterized in that: the system comprises a business object analysis engine, a resource allocation service module and an application subsystem; wherein: the business object analysis engine is used for analyzing the business object description file into a business object instance, creating an executor for managing the life cycle of the business object instance, maintaining the dependency relationship among the business objects by using a business object instance tree, and forwarding events among different business objects;
the resource allocation service module receives a task allocation request from the engine and allocates the task to a corresponding resource;
the user application subsystem is a man-machine interaction interface provided for a user, receives the information of the engine to determine the execution state of the current business object, retrieves the to-do work list of each resource instance through the resource allocation service module to execute the task instance, and feeds back the execution result to the engine through an event after the execution is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711148590.2A CN107943457B (en) | 2017-11-17 | 2017-11-17 | Workflow modeling method and system for business object |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711148590.2A CN107943457B (en) | 2017-11-17 | 2017-11-17 | Workflow modeling method and system for business object |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107943457A CN107943457A (en) | 2018-04-20 |
| CN107943457B true CN107943457B (en) | 2021-01-15 |
Family
ID=61931857
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711148590.2A Active CN107943457B (en) | 2017-11-17 | 2017-11-17 | Workflow modeling method and system for business object |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107943457B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108920135B (en) * | 2018-06-27 | 2021-09-10 | 杭州贝店科技有限公司 | User-defined service generation method and device, computer equipment and storage medium |
| CN109104297B (en) * | 2018-07-09 | 2022-01-21 | 中国银行股份有限公司 | Business process processing method and device |
| CN109447392A (en) * | 2018-09-11 | 2019-03-08 | 浙江大学 | A kind of operation flow refined method based on Artifact |
| CN109447568B (en) * | 2018-09-21 | 2022-12-02 | 山东中创软件商用中间件股份有限公司 | Asynchronous operation method, device, equipment and storage medium for process activities |
| CN109901818B (en) * | 2018-11-15 | 2022-07-19 | 创新先进技术有限公司 | System and method for software architecture design |
| CN109615319A (en) * | 2018-11-30 | 2019-04-12 | 象山邱工联信息技术有限公司 | Process based on cloud data management constructs system |
| CN109634562A (en) * | 2019-01-30 | 2019-04-16 | 广州影子科技有限公司 | Demand management method and requirement management systems |
| CN112698819A (en) * | 2019-10-22 | 2021-04-23 | 北京信普飞科科技有限公司 | Method, device and storage medium for designing tree-oriented object programming program |
| CN111124695B (en) * | 2019-11-25 | 2023-05-16 | 支付宝(杭州)信息技术有限公司 | Dynamic effect management method, system and equipment |
| CN111240739B (en) * | 2020-01-21 | 2022-04-15 | 烽火通信科技股份有限公司 | Dynamic concurrent distribution method and system for associated attributes of objects |
| CN114138507B (en) * | 2021-11-09 | 2024-05-17 | 中国联合网络通信集团有限公司 | Python program service method, device and computer readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528157A (en) * | 2016-11-17 | 2017-03-22 | 中山大学 | State machine workflow engine based on SCXML standard |
| CN106843835A (en) * | 2016-12-21 | 2017-06-13 | 中国电子科技网络信息安全有限公司 | A kind of application systems software constructing system of meta data customizing, system constituting method |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101364176B (en) * | 2008-08-12 | 2012-09-19 | 北京航空航天大学 | BPEL visualized model building system based on GMF |
| US20170270455A1 (en) * | 2013-09-13 | 2017-09-21 | Google Inc. | Managing A Workflow Of Human Intelligence Tasks Based On Task Performance |
| CN103530724B (en) * | 2013-09-27 | 2017-02-01 | 华侨大学 | Manufacturing capacity servitization method based on workflow model |
| CN103745310A (en) * | 2013-12-25 | 2014-04-23 | 北京邮电大学 | Workflow data modeling method |
| CN105760394A (en) * | 2014-12-19 | 2016-07-13 | 江苏融成嘉益信息科技有限公司 | Workflow modeling method based on XML (extensive markup language) |
-
2017
- 2017-11-17 CN CN201711148590.2A patent/CN107943457B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528157A (en) * | 2016-11-17 | 2017-03-22 | 中山大学 | State machine workflow engine based on SCXML standard |
| CN106843835A (en) * | 2016-12-21 | 2017-06-13 | 中国电子科技网络信息安全有限公司 | A kind of application systems software constructing system of meta data customizing, system constituting method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107943457A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107943457B (en) | Workflow modeling method and system for business object | |
| Zeng et al. | Monitoring the QoS for web services | |
| US10956013B2 (en) | User interface for automated flows within a cloud based developmental platform | |
| CA3003773C (en) | User interface for automated flows within a cloud based developmental platform | |
| US10101972B1 (en) | Data modelling and flow engine for building automated flows within a cloud based developmental platform | |
| CA3017085C (en) | Data modelling and flow engine for building automated flows within a cloud based developmental platform | |
| KR20060087998A (en) | Unified model for authoring and executing flow-based and constraint-based workflows | |
| KR20060087997A (en) | Framework for seamlessly authoring and editing workflows at designe and runtime | |
| JP2006107479A (en) | Framework for modeling cross-cutting behavioral concerns inside work flow region | |
| US20060225042A1 (en) | Virtual threads in business process programs | |
| Bocciarelli et al. | A language for enabling model-driven analysis of business processes | |
| EP1936494B1 (en) | Method for runtime execution of one or more tasks defined in a workflow process language | |
| CN113010598A (en) | Dynamic self-adaptive distributed cooperative workflow system for remote sensing big data processing | |
| US8650568B2 (en) | Method and system for transforming orders for executing them in standard workflow engines | |
| Schuetz et al. | Multilevel modeling for business process automation | |
| CN113225269B (en) | Container-based workflow scheduling method, device and system and storage medium | |
| CN1316408C (en) | Signaling events in workflow management systems | |
| Hentrich et al. | A pattern language for process execution and integration design in service-oriented architectures | |
| Wieland et al. | Context model for representation of business process management artifacts | |
| Geebelen et al. | An open middleware for proactive QoS-aware service composition in a multi-tenant SaaS environment | |
| Dörnemann et al. | DAVO: a domain-adaptable, visual BPEL4WS orchestrator | |
| Obweger et al. | Model-driven rule composition for event-based systems | |
| Louati et al. | RTO-RTDB: A real-time object-oriented database model | |
| Kravtsov et al. | Service-based Resource Brokering for Grid-Based Data Mining. | |
| Kühn et al. | Extending a peer-based coordination model with composable design patterns |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |