CN106682873A - Workflow business model based on objective and verification method - Google Patents
Workflow business model based on objective and verification method Download PDFInfo
- Publication number
- CN106682873A CN106682873A CN201611186430.2A CN201611186430A CN106682873A CN 106682873 A CN106682873 A CN 106682873A CN 201611186430 A CN201611186430 A CN 201611186430A CN 106682873 A CN106682873 A CN 106682873A
- Authority
- CN
- China
- Prior art keywords
- task
- target
- artifact
- ats
- workflow
- 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.)
- Pending
Links
Classifications
-
- 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/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a workflow business model based on objective. The workflow business model is centered on artifact and is characterized by comprising a workflow model W centered on artifact, a business objectives set and relationship BR of business objectives in the business objectives set, a random business behavior mapping function H, a random business dependency set D and an acceptable state set ATSs. The other technical scheme is that the verification method of the workflow business model is provided. Demand of top management can be showed from objective model. The invention provides a relaxed custom failure atomicity, the random business behavior, a corresponding effectiveness rule and the verification method.
Description
Technical field
The present invention relates to a kind of workflow transactions model centered on Artifact based on target and the workflow
The verification method of transaction model.
Background technology
In BPM field, it is ensured that flow is reliably performed and completes extremely important, and affairs are guarantee flow can
By the key mechanism of property, to keep the competitiveness of enterprise, affair mechanism must also consider the business objective of enterprise, recover to fail
Retain the target for having obtained during flow as much as possible, and promote flow to complete it and perform, rather than simply stop flow.Therefore,
Need to consider high-level business transactional demands in workflow transactions model, business objective is modeled and by itself and affair mechanism
It is associated, and loosens the failure atomicity of affairs, it is allowed to the correct standard of designer's setting process as needed.
The work for studying high-level business transactional demands is simultaneously few, has some scholars in automatic management towards target Business Stream
Journey, raising flow agility or custom action etc. are studied work.Document D.Greenwood, G.Rimassa,
" Autonomic goal-oriented business process management, " In Proc.3rd Int.Conf.on
Autonomic and Autonomous Systems (ICAS), 2007, pp.43-43. and document B.Burmeister,
M.Amold, F.Copaciu, and G.Rimassa, " Bdi-agents for agile goal-oriented business
Processes, " In AAMAS ' 08, Berger, Burg, Nishiyama eds.2008, pp.37-44. develop it is a kind of towards
The autonomous system LS/ABPM of target, in system, procedural model is defined as the hierarchical structure of target and sub-goal, and problem occurs
When, operation flow can be realized " self is cured " by finding the substitution plan of the target.Document S.Liaskos, M.Litoiu,
M.Jungblut, and J.Mylopoulos, " Goal-based behavioral customization of
Information systems, " In CAiSE 2011, H.Mouratidis, C.Rolland eds.LNCS,
Heidelberg：Springer, 2011, pp.77-92. allow user to specify preference requirement according to target, and these preferences are turned
It is changed to appropriately configured system.But these work are not directed to the reliable executive problem of flow.
It is self-defined failure atomicity workflow transactions model in terms of, major part work allow workflow design person according to
Different demands specifies failure atomicity (such as document S.Bhiri, O.Perrin, and C.Godart, " Ensuring
Required failure atomicity of composite Web services, " In Proc.Int.conf.World
Wide Web (WWW), ACM, Chiba, 2005, pp.138-147. (referred to as documents [1])；Document X.Ding, J.Wei,
T.Haung, " User-defined atomicity constraints：a more flexible transaction model
For reliable service composition, " LNCS, vol.4260, Springer, 2006, pp.168-184. (letters
Referred to as document [2])；Document I.Markov, M.Kowalkiewicz, " Linking business goals to process
Models in semantic business process modeling, " In Proc.12th Int.Conference on
Enterprise Distributed Object Computing (EDOC), 2008, pp.332-338. (referred to as documents
[3]) and document M.Rusinkiewicz, A.Sheth, " Specification and execution of
Transactional workflows, " In Modern Database Systems：The Object Model,
Interoperability, and Beyond.W.Kim Eds., New York：ACM Press and Addison-Wesley,
1995. (referred to as documents [4])).Document [1], document [3], document [4] use acceptable final state set
(Accepted Termination States, ATSs) is failure atomicity, it is allowed to which designer can according to requirement definition affairs
The final state of receiving, the state by each subtransaction state description, the correct standard of affairs of workflow/composite services is by ATSs
Description, how to ensure workflow each running example can meet setting ATSs be still filled with challenge.Document [1] is provided
Ensure that workflow meets the mechanism of the ATSs of setting in design, and a kind of ensure that each flow instance meets setting
The method of ATSs.Document [2] is using the acceptable atomicity for being configured to and loosening, there is provided correct sexual satisfaction sets when forcing operation
The algorithm of the atomicity of meter.But these work all do not solve the problems, such as influence of the business objective to transaction management.
The content of the invention
The technical problem to be solved in the present invention is：The work of existing research high-level business transactional demands is not directed to flow
Reliable executive problem；In terms of the workflow transactions model of self-defined failure atomicity, work on hand does not all solve business mesh
The influence problem to transaction management is marked, i.e., how business objective models and be mapped to transaction model, how the correct standard of flow sets
Fixed, business objective has what influence etc. on flow failure recovery mechanism.
In order to solve the above-mentioned technical problem, a technical scheme of the invention there is provided it is a kind of based on target with
Workflow transactions model TxGEEZ-Flow centered on Artifact, it is characterised in that including the work centered on Artifact
Make relation BR, the affairs behavior mapping letter of task in flow model W, business objective collection B and business objective collection B between business objective
Number H, the transaction dependency collection D of task, and acceptable final state collection ATSs, wherein：
Work flow model W centered on Artifact has carried out parallelization extension on the basis of workflow EZ-Flow,
A workflow EEZ-Flow in Work flow model W includes following element：C, Γ, E, Σ, F, R, L, wherein, C is core
Artifact classes；Γ is auxiliary artifact class set；E is time type set；Σ is set of tasks, including basic task and
Structural type task；R is resources bank set, the resources bank subset R comprising CC, the resources bank subset R of ΓΓ, and external resource storehouse
rext；L is the whistle function set on side；Each task t in ∑ is mapped to (e by Fi；eo), wherein, eiIt is a triggering task t
(∧, the ∨) logical expression comprising event type and logical operation, eoIt is the event type that task t is produced, each event
Type is produced by a task and can trigger one or more tasks, and each task is required for one or more event types to swash
Its execution living；
Each business objective is represented using artifact Attribute expressions in business objective collection B；
Relation BR includes：Force to rely on gr (man, g1, g2), support to rely on gr (sup, g1, g2) and negative-positive goal conversion
Rely on gr (shft, g1, g2), gr (man, g1, g2) represent that if workflow cannot obtain target g2, then its cannot obtain target g1,
Gr (sup, g1, g2) represent target g2Acquisition contribute to target g1Acquisition, if but target g2Failure, it is possible to obtaining mesh
Mark g1, gr (shft, g1, g2) represent target g1By negative target transition for positive goal depends on target g2Acquisition；
The affairs behavior mapping function H of task by each task t in set of tasks Σ be mapped to tuple h (t)=
(type, [(hName, preCond, task, adjRule, pri)]), wherein, the affairs behavior type of type appointed tasks t；
[(hName, preCond, task, adjRule, pri)] describes failure handling mechanism, and hName is processing method, and preCond is
The available condition of processing method, tasks of the task for needed for processing method, adjRule when necessary appointed task t affairs adjust
Whole, pri is the priority in terms of designated treatment.
The transaction dependency collection D of task is specified the tuple d of its transaction dependency by each task t mappings in set of tasks ∑
(t)=(CmtSet, AbtCond, CpsCond, TmtCond, ActCont), wherein, CmtSet is have submission to rely on to task t
Task-set, AbtCond is the event set that can cause task t rollbacks, and CpsCond is the event set that task t can be caused to compensate,
TmtCond is the event set and suspending mode that task t can be caused to stop, and ActCont is activation condition；
Acceptable final state collection ATSs is workflow design person from a designed clerical operations of service needed
The set of all acceptable final state of stream.
Preferably, the parallelization extension is comprised the following steps：
First, artifact is split into multiple disjoint parts so that multiple tasks can be somebody's turn to do with parallel work-flow
Artifact, addition attribute splits mark splitId to record the artifact of fractionation；Secondly, two structure tasks are increased：
AND- bifurcateds and AND- are converged, and AND- bifurcateds task extracts core artifact, is split into some, every partly to have
One new mark and disjoint property set, the mark of its attribute splitId record originals artifact, corresponding AND- are converged
Task is extracted all artifact parts with identical splitId and is recombined into an artifact.
Preferably, the artifact Attribute expressions are the logical expression of business objective triple (artif, op, thr)
Formula, wherein, artif is an attribute of core artifact, and op is comparison operator, and thr is the threshold value for obtaining target.
Another technical scheme of the invention there is provided a kind of verification method of above-mentioned workflow transactions model, its feature
It is to comprise the following steps：
The first step, Transactional Workflows definition
After workflow EEZ-Flow definition is completed, the relation between business objective and business objective, Ran Houtian are defined
Plus affairs behavior and the transaction dependency of task of task, finally define acceptable final state collection ATSs；
Second step, workflow effectiveness checking
Using any one in following two verification methods to workflow to carrying out validation verification, if workflow defining
It is invalid, then adjust affairs behavior, rely on or acceptable final state collection ATSs, until it becomes effective, then dispose, perform；
The first verification method：Using acceptable final state collection ATSs according to the affairs behavior of rule set calculating task,
Then verify whether the affairs behavior for calculating is consistent with the affairs behavior of definition；
Second verification method：Possible final state collection is calculated using affairs behavior, the termination for calculating then is verified
Whether state set is consistent with the acceptable final state collection ATSs of definition；
3rd step, workflow are reliably performed
After effective workflow deployment, task scheduling is carried out, arranges next being performed for task, then perform task,
In task implementation procedure, if there is exception, abnormality processing is carried out, continued executing with according to result or terminated task, often
The final state that is possible in the individual receptible acceptable final state collection ATSs of task t is expressed as ATS (t), then have as follows
Validity rule：
Regular VR1：If state atorted is not belonging to ATS (t), task t can be retried；
Regular VR2：If state compensated is not belonging to ATS (t), task t is crucial；
Regular VR3：If state compensated belongs to ATS (t), ats is set toi, then task t is compensable, and in meeting
One condition of the middle presence of event set CpsCond (t) for causing task t to compensate meets atsi；
Regular VR4：If state ended belongs to ATS (t), ats is set toi, then task t is crucial, and can cause task t
Meet ats in the presence of a condition in event set CpsCond (t) of compensationi；
Regular VR5：If state terminated belongs to ATS (t), ats is set toi, then task t is terminable, and can drawn
One condition of presence meets ats in playing event set TmtCond (t) that task t stopsi；
Regular VR6：If state completed belongs to ATS (t), ats is set toi, then have to task t and submit the task-set for relying on to
All tasks in CmtSet (t) are in atsiIn state all be completed；
Regular VR7：If task t is related target, target g is set to1, and target g1To target g2Turn in the presence of negative-positive goal
Change dependence, then task t is terminable, and with target g2Related task is included in the event set that task t can be caused to stop
In TmtCond (t), and the condition of TmtCond (t) meets in acceptable final state collection ATSs.
The present invention overcomes the deficiencies in the prior art by the following method：(1) in TxGEEZ-Flow, high-rise demand can lead to
Target model tormulation is crossed, object module can be used the description of artifact Attribute domains expression formula, and be linked to transaction management, so as to have
Effect reduces the wide gap between high-level business transactional demands and the correct standard and reliable executive problem of flow；(2) in TxGEEZ-
In Flow, there is provided a kind of self-defined failure atomicity, task affairs behavior loosened, and corresponding validity rule and test
Card method, designer can have been obtained with the acceptable final state set ATSs of self-defined each flow with retaining as far as possible
Business objective, by the way that business objective is linked into task and the affairs behavior type of task is set, solve business objective pair
The influence problem of transaction management, and the business objective delivery rate of flow is improved, validity rule and authentication rule ensure design
ATSs be reasonable, effective.
The invention has the advantages that：
(1) a kind of workflow transactions model centered on Artifact based on target is provided, it is in the model, high-rise
Demand can be expressed by object module, and object module can be used the description of artifact Attribute domains expression formula, and be linked to affairs pipe
Reason, is that follow-up work stream affairs quick response high level demand or service logic change are laid a solid foundation；
(2) a kind of self-defined failure atomicity, task affairs behavior loosened be provided, and corresponding validity rule and
Verification method, designer can have been obtained with the acceptable final state set ATSs of self-defined each flow with retaining as far as possible
The business objective for obtaining, improves the business objective delivery rate of flow, and validity rule and authentication rule ensure that the ATSs of design is
Rationally, effectively.
Brief description of the drawings
Fig. 1 is method of the present invention overview；
Fig. 2 is TxEEZ-Flow system architectures.
Specific embodiment
With reference to specific embodiment, the present invention is expanded on further.It should be understood that these embodiments are merely to illustrate the present invention
Rather than limitation the scope of the present invention.In addition, it is to be understood that after the content for having read instruction of the present invention, people in the art
Member can make various changes or modifications to the present invention, and these equivalent form of values equally fall within the application appended claims and limited
Scope.
The present invention has following feature：
(1) Work flow model uses the Work flow model centered on Artifact, and has carried out parallelization extension；
(2) business objective modeling is carried out to high-level business demand, each business objective uses artifact Attribute expressions
Represent, define the relation between target, mainly include：Force to rely on, support that dependence and negative-positive goal conversion are relied on.Target
Model may link to the task of flow, the artifact property sets that the artifact property sets being related to by target are exported with task
It is associated；
(3) workflow transactions model Work flow model, relational model between business objective and business objective, task
The transaction dependency collection of affairs behavior mapping function, task, and acceptable final state collection ATSs is described, the affairs of support
Behavior includes：Can compensate for, can retry, it is crucial, can stop, the transaction dependency of support includes：Dependence, rollback is submitted to rely on, compensate
Rely on and stop to rely on, give respective transaction and rely on the validity rule for existing；
(4) affairs behavior type according to task, transaction dependency condition and transaction dependency task-set, give clerical operations
The validation verification rule of flow model, can first calculate affairs behavior, then supplement amendment by designer, verify that affairs behavior is afterwards
The no ATSs for meeting setting；Also possible ATSs can be calculated, then is deleted as needed by designer, afterwards checking setting
ATSs validity；
(5) realization of system is based on C#, comprising two core components：Task manager and affairs enforcement engine, the former wraps
Containing affairs definition and transaction validation, the latter includes task dispatcher and task performer, and event communication bus is passed through between component
Communicated.
A kind of workflow transactions model TxGEEZ-Flow centered on Artifact based on target that the present invention is provided
Comprising six parts：Business objective in Work flow model W, business objective collection B and business objective collection B centered on Artifact
Between relation BR, the affairs behavior mapping function H of task, the transaction dependency collection D of task, and acceptable final state collection
ATSs.Illustrate separately below：
1) the Work flow model W centered on Artifact
Work flow model W uses the Work flow model centered on Artifact, and workflow proposes EZ- in Xu and Su et al.
Parallelization extension has been carried out on the basis of Flow, EEZ-Flow has been obtained.Implementation step is：First, artifact is split into
Multiple disjoint parts so as to multiple tasks can with the parallel work-flow artifact, add attribute split mark splitId with
Record the artifact for splitting；Secondly, two structure tasks are increased：AND- bifurcateds and AND- are converged, and AND- bifurcated tasks are carried
Core artifact is taken, some is split into, there is a new mark and disjoint property set per part, its category
Property splitId records original artifact mark, it is all with identical splitId's that corresponding AND- converges task extraction
Artifact parts are simultaneously recombined into an artifact.Workflow centered on artifact has passed through on side
Whistle function naturally support exclusive selection structure.
One workflow EEZ-Flow includes following element：C, Γ, E, ∑, F, R, L, wherein, C is core artifact
Class；Γ is auxiliary artifact class set；E is time type set；∑ is set of tasks, including basic task and structural type are appointed
Business；R is resources bank set, the resources bank subset R comprising CC, the resources bank subset R of ΓΓ, and external resource storehouse rext；L is side
On whistle function set；Each task t in Σ is mapped to (e by Fi；eo), wherein, eiIt is triggering task t comprising thing
Part type and (∧, ∨) logical expression of logical operation, eoFor the event type that task t is produced, each event type is by one
Individual task is produced and can trigger one or more tasks, and each task is required for one or more event types and holds activating it
OK.
2) the relation BR in business objective collection B and business objective collection B between business objective
The present invention is modeled using business objective model to high-level business demand, and each business objective is used
Artifact Attribute expressions represent that the expression formula is the logical expression of business objective triple (artif, op, thr), its
Middle artif is an attribute of core artifact, and op is comparison operator, including==, ＜, ＞, ＜=, ＞=；Thr is
Obtain the threshold value of target.We divide into positive goal (profit) and negative target (initial investment), and negative target has certain risk,
Positive goal can be changed into after some targets are obtained, the priority of target is also may specify.
Relation between target mainly includes：Force rely on gr (man, g1, g2), support rely on gr (sup, g1, g2) and
Negative-positive goal conversion relies on gr (shft, g1, g2), gr (man, g1, g2), and if representing, workflow cannot obtain target g2, its
Target g1, gr (sup, g1, g2) cannot be obtained and represent that the acquisition of target g2 contributes to the acquisition of target g1, if but target g2 mistakes
Lose, represent target g1 by negative target transition for positive goal depends on target it is possible to obtaining target g1, gr (shft, g1, g2)
The acquisition of g2.
Object module may link to the task of flow, what the artifact property sets and task being related to by target were exported
Artifact property sets are associated, and all related to target g to obtain there is provided function getRelatedTasks (g)
Task.After a positive goal task is completed, if flow fails, its side effect should be retained；When negative goal task is complete
After, should try one's best and allow its negative-positive goal conversion dependence task also to complete together.
3) the affairs behavior mapping function H of task
The affairs behavior of this affairs model supports includes：Can compensate for (cp), can retry (r), crucial (p), (t) can be stopped.
When failure occurs, task t is compensable, if its side effect can the semantic revocation after task t submissions；Task t is to retry
, if it can always be successfully completed after being called again several times；Task t be it is crucial, if task t complete after its
Side effect must retain, it is impossible to cancel, and carry out the execution of termination process there is provided the terminating flow of the task；Task t is can
Stop, if can be aborted during its operation.Affairs behavior can be combined, all possible composite set for r, cp, p, t, c,
(r, cp), (r, p), (r, t), (cp, c), (p, c), (t, c), (cp, t, c), (p, t, c) }.We use the side of similar Petri network
Formula gives the semanteme of affairs behavior.
Generally, its affairs behavior of the task of particularly positive goal correlation of target correlation should be modeled as key, so that can
To retain acquired target as far as possible.
The affairs behavior mapping function H of task by each task t in set of tasks Σ be mapped to tuple h (t)=
(type, [(hName, preCond, task, adjRule, pri)]), wherein, the affairs behavior type of type appointed tasks t；
[(hName, preCond, task, adjRule, pri)] describes failure handling mechanism, and hName is processing method, such as retries or mends
Repay, preCond is the available condition of processing method, such as tasks of the task for needed for processing method, compensation task tl, adjRule
The affairs adjustment of appointed task t when necessary, pri is the priority in terms of designated treatment.
4) the transaction dependency collection D of task
One affairs behavior of task, such as submission, rollback or compensation, may influence the affairs behavior of other tasks, this
Plant influence and be transaction dependency.The transaction dependency of this affairs model supports includes：Submit to rely on, rollback rely on, compensation rely on and
Stop to rely on.Notice that these transaction dependencies may depend on the activation between task to rely on.
We represent the activation condition of task t, task t with ActCond (t)2To task t1In the presence of activation rely on only whenE is task t1Terminate the event for producing.
CmtSet (t) is that task t has the task-set submitted to and rely on, task t2To task t1Only work as t in the presence of submitting to rely on1
∈CmtSet(t2).If a task is interchangeable, its submission dependence should be adjusted according to the replacement task.
AbtCond (t) is the rollback event set of task t, task t2To task t1There is rollback dependence and only work as t1.aborted
∈AbtCond(t2)∨t1.terminated∈AbtCond(t2)∨t1.compensated∈AbtCond(t2)。
CpsCond (t) is the compensation event set of task t, task t2To task t1Relied in the presence of compensation and only work as t1.aborted
∈CptCond(t2)∨t1.terminated∈CptCond(t2)∨t1.compensated∈CptCond(t2).When
CptCond(t2) in event when arriving at, task t2If it will be compensated can compensate for, if task t2It is crucial, then flow will be by
Terminate.
Stopping dependence has both of which：Must and may.In necessary pattern, the task of dependence must stop, possible pattern
In, the suspension of task of dependence or execution, depending on business game.Represent task t's with TmtCond (t)=(event, mode)
Break event and dependence pattern, task t2To task t1Only work as t in the presence of stopping to rely on1.aborted∈TmtCond(t2).event
∨t1.terminated∈TmtCond(t2).event。
The related limitation that the activation that above-mentioned transaction dependency should observe between flowage structure and task is relied on, e.g., if task
t2With task t1Positioned at the different branches of exclusive selection structure, then task t2Will not submit to and depend on task t1, etc..According to so
Potential rule, transaction dependency (ALDs) or verify user-defined affairs that workflow EEZ-Flow allows can be calculated
Whether dependence is allowed to, and user-defined transaction dependency should be the subset of ALDs.
The transaction dependency collection D of task is specified the tuple d of its transaction dependency by each task t mappings in set of tasks ∑
(t)=(CmtSet, AbtCond, CpsCond, TmtCond, ActCont), wherein, CmtSet is have submission to rely on to task t
Task-set, AbtCond is the event set that can cause task t rollbacks, and CpsCond is the event set that task t can be caused to compensate,
TmtCond is the event set and suspending mode that task t can be caused to stop, and ActCont is activation condition.
5) it is subjected to final state collection ATSs
Acceptable final state collection ATSs is workflow design person from a designed clerical operations of service needed
The set of all acceptable final state of stream, this transaction model uses ATSs as the correct standard of workflow transactions.ATSs
Must be carefully designed, generally include：(1) all tasks reach completed states；(2) some mission failures, before it
Task has been revoked all of side effect；(3) after mission critical completion, there is mission failure, then it is crucial at last
Task between task and failed tasks is compensated, last mission critical treatment to ended states.
One workflow execution sequence is correctly only when its final state is in ATSs.
ATSs is not arbitrarily devised, and it must be with business objective, affairs behavior, transaction dependency and workflow structure
The transaction dependency for being allowed is consistent, in the absence of contradiction, and ensures that the ATSs of setting is observed in the execution of workflow.
Present invention also offers a kind of business effectiveness verification method.
The execution that must have corresponding affair mechanism to ensure workflow meets the ATSs for specifying.The overview of this method is as schemed
Shown in 1, including three phases：(1) Transactional Workflows definition.After workflow defining is completed, designer defines industry first
Relation between business target and target, then adds affairs behavior and dependence, finally defines ATSs；(2) workflow effectiveness is tested
Card.There is provided two kinds of verification methods：1. then verify what is calculated according to the affairs behavior of rule set calculating task using ATSs
Whether affairs behavior is consistent with the affairs behavior of definition；2. possible final state collection is calculated using affairs behavior, is then verified
Whether the final state collection for calculating is consistent with the ATSs of definition.If workflow defining is invalid, designer need to adjust affairs
Behavior, dependence or ATSs, until it becomes effective, then can just dispose, perform；(3) workflow is reliably performed.Effectively work
After stream deployment, task scheduling is carried out, arrange next being performed for task, then perform task, in task implementation procedure,
If there is exception, need to carry out abnormality processing, continued executing with according to result or terminated task.
To ensure the validity of workflow, it is necessary to verify：(1) reasonability of ATSs.ATSs must be with workflow pattern language
It is adopted consistent；(2) ATSs is consistent, i.e. acceptable final state in ATSs does not conflict；(3) ATSs is effective, ATSs
Have to comply with business objective, affairs behavior and the requirement of transaction dependency.ATSs soundness verifications check for the thing for allowing
Business relies on each ats that can be met in ATSs.The requirement of ATSs consistency checkings：If atsiAnd atsjIn other tasks shape
State all, then the state ats of task ti(t) and atsjT () must be the same, unless atsf(t) or atsjT the state of () is
terminated.Because terminate relying on there is " possible pattern ", the state of task t can be terminated, if terminating bar
Part meets, or other states (such as ended).After the completion of the affairs behavior of task and target-dependent are calculated, can detect
The conflict gone out between different ats.ATSs validation verifications check for meeting the affairs of each ats in ATSs according to
Rely (transaction dependency for including target-dependent introduction), validity rule can be summarized as.
In this method, the transactional attribute of each task t is expressed as：(1) behavior type；(2) transaction dependency condition, including：
Compensation condition CpsCond (t) and end condition TmtCond (t)；(3) transaction dependency task-set：Submit dependence task collection CmtSet to
(t).The final state that is possible in the receptible acceptable final state collection ATSs of each task t is expressed as ATS (t), then
There is following validity rule：
Regular VR1：If state atorted is not belonging to ATS (t), task t can be retried；
Regular VR2：If state compensated is not belonging to ATS (t), task t is crucial；
Regular VR3：If state compensated belongs to ATS (t), ats is set toi, then task t is compensable, and in meeting
One condition of the middle presence of event set CpsCond (t) for causing task t to compensate meets atsi；
Regular VR4：If state ended belongs to ATS (t), ats is set toi, then task t is crucial, and can cause task t
Meet ats in the presence of a condition in event set CpsCond (t) of compensationi；
Regular VR5：If state terminated belongs to ATS (t), ats is set toi, then task t is terminable, and can drawn
One condition of presence meets ats in playing event set TmtCond (t) that task t stopsi；
Regular VR6：If state completed belongs to ATS (t), ats is set toi, then have to task t and submit the task-set for relying on to
All tasks in CmtSet (t) are in atsiIn state all be completed；
Regular VR7：If task t is related target, target g is set to1, and target g1To target g2Turn in the presence of negative-positive goal
Change dependence, then task t is terminable, and with target g2Related task is included in the event set that task t can be caused to stop
In TmtCond (t), and condition in TmtCond (t) meets in acceptable final state collection ATSs.
The present invention devises mission validity verification algorithm algTaskValidity.The algorithm is tested by validity rule
The validity of card task, returns to the useful suggestion of designer, including lack behavior type, rely on and ATSs in it is irrational
Part.Function Check in the algorithm checks the validity of all kinds task：State, thing according to ats, task in ats
The dependence of business dependence, behavior type and permission, verifies whether that the transaction dependency that there is specific transaction dependency and allow can expire
Sufficient ats.If the validation verification result of task is empty set, task is effective, and otherwise, the algorithm will return to adjustment suggestion.
One workflow is effective, if its all task is all effective.
In following algorithm：
Input includes：ATS：The ATSs of designer's design；h(t)：The failure behavior of task t；h(t).type：Task t's
The type of failure behavior；d(t)：The transaction dependency of task t, such as CmtSet, CpsCond etc.；alD(t)：On task t allow according to
Rely, including AlCpsCond, AlTmtCond.
Output includes：val：One character string dimension, val is included：Be represents the behavior type for lacking, and de represents what is lacked
Rely on, atsRs represents irrational part in ATSs.
Then effectiveness of the invention verification algorithm algTaskValidity is as follows：
If 1.AndThen val.be ← val.be ∪ " retriable "
If 2.AndThen val.be ← val.be ∪ " pivot "
3. each receptive phase ats in couple ATS, performs following checking：
If 3.1 ats (t) are compensated, compensation condition is detected：
CpsChk=Check (ats, " compensatable ", d (t) .CpsCond, h (t) .type, alD (t)
.AlCpsCond)
If 3.2 ats (t) are ended, the termination condition of mission critical is checked：
PvtChk=Check (ats, " pivot ", d (t) .CpsCond, h (t) .type, alD (t) .AlCpsCond)
If 3.3 ats (t) are terminated, end condition is checked：
TmtChk=Check (ats, " terminable ", d (t) .TmtCond, h (t) .type, alD (t)
.AlTmtCond)
If 3.4 ats (t) are there is t in completed and d (t) .CmtSetiMeet condition ats (ti) ≠ completed,
Then：
val.atsRs←val.atsRs+″(″+ti+ " → "+t+ ") "+" submit to and rely on destroyed "
If 4. there is shft (getRelatedTasks-1(t), g2), then：
ShftChk=CheckShft2Tmt (ATS, h (t) .type, getRelatedTasks (g2), d (t)
.TmtCond)
5.val←val+cpsChk+pvtChk+tmtChk+shftChk+confChk
6. val is returned.
If the number of receptive phase ats is m in ATSs, the number of tasks in workflow is n, then algorithm
The complexity of algTaskValidity is O (m), and the complexity of the workflow verification is O (m*n).The behavior type of task may
Can suspendable behavior with it is crucial or it is compensable be combined, then its acceptable final state may have 4 kinds, but only stateful
Completed can work on the execution of stream, and other three states are all the final states for performing.In XOR patterns, can connect
It is relevant with its branch's number by status number, it is the product of ordered mode status number and its branch's number.If total XOR branches number is a, then
The scope of m can be estimated as：N ＜ m ＜ a* (3n+1), the complexity of workflow verification is O (n2)。
When the number of tasks of workflow becomes increasing, the ATSs designs of workflow can also become to become increasingly complex,
In this case, ATSs can be calculated according to business objective, affairs behavior, dependence and effectively rule first, workflow design people
Member is filtered and is optimized further according to their specific business to the ATSs for calculating.
The prototype realization of this method is based on C#, and its framework mainly includes two subsystems：Transaction management subsystem and affairs
Engine subsystem, as shown in Figure 2.
Transaction management subsystem is the kernel subsystems of system, and processing module is held comprising affairs definition, checking and affairs, its
Middle transaction validation module verifies workflow effectiveness according to the ATSs of definition, and transaction model ensures that the reliability of workflow is held
OK, all kinds of exceptions occurred during workflow execution can be processed, including：Task termination, execution mistake and realization of goal are lost
Lose.
Transaction engine performs Transactional Workflows, and transaction engine is event driven, comprising two main modulars：Task scheduling
Device and task performer.Task dispatcher arranges next being performed for task according to the event for receiving, and event type includes：
Internal event, external event and the transaction events sent from transaction model, the form of transaction events are as follows：task@
Place, enactment, order and operation set.When scheduler receives transaction events, it send a command to be carrying out appoint
Business performs example, meanwhile, if there is operation in operation set, such as alternative tasks, then scheduler time content is sent to one
New tasks carrying example.Task execution module reliably performs the Transaction task of scheduler distribution, if abnormal occur, performs reality
Regular meeting generates an affairs anomalous event, and shape is such as：Task@place, enactment, Exception Type.After the completion of abnormality processing, hold
Row device can receive the transaction events of scheduler dispatches to continue its execution.After tasks carrying terminates, task status is
Completed, task performer generates corresponding event according to the definition of task.
Claims (4)
1. a kind of workflow transactions model centered on Artifact based on target, it is characterised in that including with
Relation BR in Work flow model W, business objective collection B and business objective collection B centered on Artifact between business objective, appoint
The affairs behavior mapping function H of business, the transaction dependency collection D of task, and acceptable final state collection ATSs, wherein：
Work flow model W centered on Artifact has carried out parallelization extension on the basis of workflow EZ-Flow, work
A workflow EEZ-Flow in flow model W includes following element：C, Γ, E, Σ, F, R, L, wherein, C is core
Artifact classes；Γ is auxiliary artifact class set；E is time type set；Σ is set of tasks, including basic task and
Structural type task；R is resources bank set, the resources bank subset R comprising CC, the resources bank subset R of ΓΓ, and external resource storehouse
rext；L is the whistle function set on side；Each task t in Σ is mapped to (e by Fi；eo), wherein, eiIt is a triggering task t
(∧, the ∨) logical expression comprising event type and logical operation, eoIt is the event type that task t is produced, each event
Type is produced by a task and can trigger one or more tasks, and each task is required for one or more event types to swash
Its execution living；
Each business objective is represented using artifact Attribute expressions in business objective collection B；
Relation BR includes：Force to rely on gr (man, g1, g2), support to rely on gr (sup, g1, g2) and negative-positive goal conversion dependence gr
(shft, g1, g2), gr (man, g1, g2) represent that if workflow cannot obtain target g2, then its cannot obtain target g1, gr (sup,
g1, g2) represent target g2Acquisition contribute to target g1Acquisition, if but target g2Failure, it is possible to obtaining target g1, gr
(shft, g1, g2) represent target g1By negative target transition for positive goal depends on target g2Acquisition；
The affairs behavior mapping function H of task by each task t in set of tasks ∑ be mapped to tuple h (t)=(type,
[(hName, preCond, task, adjRule, pri)]), wherein, the affairs behavior type of type appointed tasks t；[(hName,
PreCond, task, adjRule, pri)] description failure handling mechanism, hName is processing method, and preCond is processing method
Available condition, tasks of the task for needed for processing method, the affairs adjustment of adjRule appointed task t when necessary, pri is
Priority in terms of designated treatment.
The transaction dependency collection D of task by set of tasks Σ each task t mapping specify its transaction dependency tuple d (t)=
(CmtSet, AbtCond, CpsCond, TmtCond, ActCont), wherein, CmtSet is have to submit relying on for task to task t
Collection, AbtCond is the event set that can cause task t rollbacks, and CpsCond is the event set that task t can be caused to compensate, TmtCond
It is event set and suspending mode that task t can be caused to stop, ActCont is activation condition；
Acceptable final state collection ATSs is workflow design person from a designed Transactional Workflows of service needed
The set of all acceptable final states.
2. a kind of workflow transactions model centered on Artifact based on target as claimed in claim 1, its feature
It is that the parallelization extension is comprised the following steps：
First, by artifact split into multiple disjoint parts so as to multiple tasks can with the parallel work-flow artifact,
Addition attribute splits mark splitId to record the artifact of fractionation；Secondly, two structure tasks are increased：AND- bifurcateds
Converged with AND-, AND- bifurcateds task extracts core artifact, is split into some, have per part one it is new
Mark and disjoint property set, the mark of its attribute splitId record originals artifact, corresponding AND- converge task and extract
All artifact parts with identical splitId are simultaneously recombined into an artifact.
3. a kind of workflow transactions model centered on Artifact based on target as claimed in claim 1, its feature
It is that the artifact Attribute expressions are the logical expression of business objective triple (artif, op, thr), wherein,
Artif is an attribute of core artifact, and op is comparison operator, and thr is the threshold value for obtaining target.
4. a kind of verification method of workflow transactions model as claimed in claim 1, it is characterised in that comprise the following steps：
The first step, Transactional Workflows definition
After workflow EEZ-Flow definition is completed, the relation between business objective and business objective is defined, then addition is appointed
The affairs behavior of business and the transaction dependency of task, finally define acceptable final state collection ATSs；
Second step, workflow effectiveness checking
Using any one in following two verification methods, if workflow defining is invalid, adjustment affairs behavior, rely on or can
Receive final state collection ATSs, until it becomes effective, then dispose, perform；
The first verification method：Using acceptable final state collection ATSs according to the affairs behavior of rule set calculating task, then
Whether the affairs behavior that checking is calculated is consistent with the affairs behavior of definition；
Second verification method：Possible final state collection is calculated using affairs behavior, the final state for calculating then is verified
Whether collection is consistent with the acceptable final state collection ATSs of definition；
3rd step, workflow are reliably performed
After effective workflow deployment, task scheduling is carried out, arrange next being performed for task, then perform task, it is in office
In business implementation procedure, if there is exception, abnormality processing is carried out, continued executing with according to result or terminated task, each is appointed
The final state that is possible in the receptible acceptable final state collection ATSs of business t is expressed as ATS (t), then have following effective
Property rule：
Regular VR1：If state atorted is not belonging to ATS (t), task t can be retried；
Regular VR2：If state compensated is not belonging to ATS (t), task t is crucial；
Regular VR3：If state compensated belongs to ATS (t), ats is set toi, then task t is compensable, and can caused
Meet ats in the presence of a condition in event set CpsCond (t) of task t compensationi；
Regular VR4：If state ended belongs to ATS (t), ats is set toi, then task t is crucial, and task t can caused to compensate
Event set CpsCond (t) in meet ats in the presence of a conditioni；
Regular VR5：If state terminated belongs to ATS (t), ats is set toi, then task t is terminable, and is appointed that can cause
Meet ats in the presence of a condition in event set TmtCond (t) that business t stopsi；
Regular VR6：If state completed belongs to ATS (t), ats is set toi, then have to task t and submit the task-set for relying on to
All tasks in CmtSet (t) are in atsiIn state all be completed；
Regular VR7：If task t is related target, target g is set to1, and target g1To target g2In the presence of negative-positive goal conversion according to
Rely, then task t is terminable, and with target g2Related task is included in the event set TmtCond that task t can be caused to stop
T in (), and condition in TmtCond (t) meets in acceptable final state collection ATSs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611186430.2A CN106682873A (en) | 2016-12-20 | 2016-12-20 | Workflow business model based on objective and verification method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611186430.2A CN106682873A (en) | 2016-12-20 | 2016-12-20 | Workflow business model based on objective and verification method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106682873A true CN106682873A (en) | 2017-05-17 |
Family
ID=58869890
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611186430.2A Pending CN106682873A (en) | 2016-12-20 | 2016-12-20 | Workflow business model based on objective and verification method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106682873A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109447392A (en) * | 2018-09-11 | 2019-03-08 | 浙江大学 | A kind of operation flow refined method based on Artifact |
| CN110334907A (en) * | 2019-06-03 | 2019-10-15 | 武汉大学 | A kind of calamity emergency task combined method based on workflow |
| CN112181617A (en) * | 2020-09-17 | 2021-01-05 | 东北大学 | Efficient scheduling algorithm based on specific index structure |
-
2016
- 2016-12-20 CN CN201611186430.2A patent/CN106682873A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109447392A (en) * | 2018-09-11 | 2019-03-08 | 浙江大学 | A kind of operation flow refined method based on Artifact |
| CN110334907A (en) * | 2019-06-03 | 2019-10-15 | 武汉大学 | A kind of calamity emergency task combined method based on workflow |
| CN112181617A (en) * | 2020-09-17 | 2021-01-05 | 东北大学 | Efficient scheduling algorithm based on specific index structure |
| CN112181617B (en) * | 2020-09-17 | 2024-05-17 | 东北大学 | Efficient scheduling algorithm based on specific index structure |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108108878A (en) | Configurable workflow transactions model and its dynamic verification method based on target | |
| Angelopoulou et al. | Industry 4.0: The use of simulation for human reliability assessment | |
| CN102880780B (en) | The system and method for producing the intuitive background for analyze data | |
| US8521570B2 (en) | Integration of distributed business process models | |
| CN106682873A (en) | Workflow business model based on objective and verification method | |
| US20060143611A1 (en) | Distribution of integrated business process models | |
| Colombo et al. | Recovery within long-running transactions | |
| Hamadi et al. | Self-adapting recovery nets for policy-driven exception handling in business processes | |
| Kaur et al. | A review on software maintenance issues and how to reduce maintenance efforts | |
| Shand | User manuals as project management tools. i. theoretical background | |
| Nasirifard et al. | OrderlessChain: A CRDT-based BFT Coordination-free Blockchain Without Global Order of Transactions | |
| Sampathkumaran | Computing the cost of business processes | |
| Rabbi et al. | Compensable workflow nets | |
| CN108564333A (en) | A kind of occupational survey method and system | |
| Bourne et al. | Verifying transactional requirements of web service compositions using temporal logic templates | |
| Gagandeep et al. | An automated metamorphic testing technique for designing effective metamorphic relations | |
| CN110188101A (en) | It is a kind of super most according to list processing method, apparatus, equipment and medium | |
| Ismail et al. | Verification of composite services with temporal consistency checking and temporal satisfaction estimation | |
| CN114692221A (en) | Proposal voting method | |
| JP2009252189A (en) | Work flow server, work flow system, method and program for accessing external data in work flow system, and recording medium recording the program | |
| US7937250B2 (en) | Method and system for addressing non-functional concerns | |
| Lipke | Schedule adherence: A useful measure for project management | |
| Vaz et al. | Towards automated verification of web services | |
| Julia et al. | Functional testing using object workflow nets | |
| Casado et al. | Dependency-based criteria for testing web services transactional workflows |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20170517 |