Summary
As the computer is widely used in daily work, many of people have done on a computer, while the various types of information systems are also widely used to support these work. But these systems are basically independently run. There is a lack of necessary interaction, collaboration and perception, so that they have coordinated a number of people's activities to collaborate to complete a common task. This is also a serious deficiencies. This is also the workflow management system WFMS since the 1990s It attracts important reasons from the extensive attention from research institutions and industrial communities.
This paper first conducted an overview of workflow technology development, summarizing the current development trend of workflow technology, introducing the reference model of the workflow management system. For a workflow modeling tool, a workflow modeling tool is used for a workflow. In terms of workflow modeling, a flexible working fluid model is proposed by extending the model elements in the traditional activity network map model, joining the delay node, parallel module, service, and modification modules, and proposes a flexible working fluid model. It is well solved the original Problems such as synchronization, multi-active instance, service type activity, and running time process modeling. Examples show that the meta model has the advantages of strong description ability, flexible modeling method, clear structure and simple structure, suitable for corporate business process management.
Keywords: workflow, meta model, workflow management system, reference model
Abstract
In routine, with the widespread application of computer much work has been finished by computer. At the same time, those work has been support by all kinds of information system. But basically, these information system are run independently, among these information systems, they lack of the necessary interaction, cooperation, inter-perception. It result in a serious shortage in cooperating to finish some common task when they must coordinate many people's activities. This is the reason that why workflow management system has attract the wide attention from research institute And Industry Field.
Workflow technology, supported by information technology, provides a whole framework to facilitate the analysis, establishment, management, simulation and enactment of process models for the actual business processes, and becomes one of the crucial technologies for contemporary enterprises in implementing the management and control of business processes. In order to further advance the applicability of workflow technology, this thesis focused on topics about workflow modeling, enactment and exception handling, and contributes the theory approaches and implementation methods as a result. The research is meaningful for the improvement of the application Of Information Technology and The Kernel Competences for Enterprise IN Our Country.Key Words: Workflow, Meta-Model, Workflow Management System, Reference Model
table of Contents
Chapter 1 Workflow Technology Overview. 1
1.1 Workflow management system. 1
1.1.1 Application of Workflow Management System. 1
1.1.2 Development trend of workflow technology. 2
1.2 Workflow Management System Reference Model. 3
1.2.1 Workflow management system architecture. 4
1.2.2 Workflow model. 5
1.2.3 Workflow execution service. 7
1.3 The main content of each part of the paper. 8
Chapter 2 Application of XML Technology in Workflow System. 9
2.1 XML meaning. 9
2.2 XML basic characteristics. 9
2.3 Process definition language in the workflow. 10
2.3.1 Process Meta Model 12
2.3.2 Extended Process Meta Model 13
2.3.3 Package Meta Model 13
2.3.4 Elements overview () 14
2.4 Process Definition Language Business Description. 14
Chapter 3 System Analysis of Modeling Tools. 15
3.1 Working Element Model. 15
3.1.1 Transition. 15
3.1.2 Activity (Activity). 15
3.1.3 Tag Node (Symbol). 16
3.1.4 Connection Node (Connector). 16
3.1.5 Sub Process. 17
3.2 Analysis of requirements. 18
3.3 Summary design. 20
3.4 Summary. 22
Chapter IV Details of JBMOD. 23
4.1 Design mode. 23
4.2 System data structure design. 24
4.3 Program Design Notes. 28
4.3.1 View. 28
4.3.2 Documentation. 34
4.3.3 Model data object. 36
4.3.4 Document reading and saving. 38
4.4 I have not been solved. 39
Chapter 5 Conclusions and Prospects. 40
5.1 Summary of this article. 40
5.2 Future Prospects. 40
Thanks. 41
References. 42
Chapter 1 Workflow Technology Overview
Workflow technology provides a complete framework from model analysis, establishment, management, simulation to operation through information technology, is a critical technology to implement business process management and control. At present, in a global scale, the research of workflow technology and related products have entered a prosperous phase, more updated technology is integrated, Internet services, database, email, mobile computing, file management, etc. It has been accommodated to the workflow management system. With the continuous expansion and maturity of the technology under the integration framework of the workflow, the workflow system will become an indispensable software platform in the enterprise information environment, and will eventually become overwritten over all kinds of desktop and network operating systems. Business Operating System BOS (Business Operating System) brings a revolution in the operating system. The emergence and rapid development of workflow technology provides important technical support for the implementation of the company's advanced manufacturing strategy. In-depth research on workflow technology is very important for further improving the level of informationization in my country, and enhancing the core competitiveness of enterprises. 1.1 Workflow Management System
"Workflow management system is a software system that completes the definition and management of workflows, and performs execution of workflow instances in advance in computer pre-defined workflow logic."
1.1.1
Workflow management system application
Typically, the workflow management system refers to a software system for defining, implementing and managing workflow running on one or more software called a workflow. It interacts with workflow executers (people, applications) Advance the execution of workflow instances and monitor the operating state of the workflow. Under the support of the workflow management system, the support of the business process can be completed well by integrating specific business applications and operator interface operations.
The workflow management system can maximize the existing information resources of the enterprise, realize the full use of resources, improve the degree of standardization of enterprise management, shorten the processing time of business process, reduce management cost, improve work efficiency, better Upstream and downstream enterprises form a supply chain network in the fast response market. Since the workflow management system has better flexibility and openness, it can ensure that the information system of the company can smoothly expand to meet the changing market environment. In addition, since the workflow management system is running on the business process of the enterprise based on the workflow model, this is analogy -> model analysis -> process optimization -> model implementation -> Implementation of the business Procedure -> Optimized the implementation of the company's operations laid a solid foundation for successfully implementing the enterprise information system.
1.1.2
Development trend of workflow technology
Today, the research on workflow technology is increasingly paying attention to workflow technology is also conducted in a deeper level. Workflow technology research is mainly divided into two aspects: First, the problem of workflow model and semantic formation means for workflow models; second, explore from workflow realization technology Advanced technology improves the performance and reliability of the workflow management system. The following mainly discusses the development trend of workflow realization technology.
Distributed system: Distributed systems allow distributed computing resources to be efficiently utilized, balance system load, and reduce the loss of system failures. The distributed sub-process or activity can operate independently on the distributed system assembly and the status of data and processes between components. Distributed design not only considers communication problems between system distribution components, but more importantly, gives the rules of process distribution, so that the resource utilization of the entire system reaches optimal.
Component design, enhanced system scalability: An important feature of advanced workflow management systems is the basic idea of allowing system evolution in design and implementation. To realize the fast restructuring of the business process, the company's application system needs to build or transform according to the components. After the component-designed system design and object-oriented workflow model, user interface components, workflow management components, and workflow processes can be customized and reuse, so they can quickly adapt to applications in different fields.
Based on event: Events provide an efficient mechanism for asynchronous communications and interoperability between components (distributed) components in the workflow management system. With this mechanism, the combination of components can be loosened. A higher requirement for event-based design is that components or users can customize their own time message types that they want to receive, not always not being born. Web: Participants in future business workflows not only include companies 'decision makers and employees, will also include companies' suppliers, customers, and other partners on the supply chain, they are not only geographically distributed, not used Platform and each has its own work mode and schedule. These participants will construct a virtual working group through access to the common workflow, connected by the workflow management system. WWW provides a cross-platform, consistent, simple data access method using intranet and Internet. Support Dynamic Modeling: Workflow management systems need to adapt to changing environments, and the changing environment often causes abnormalities. During the execution of the long process, the optimization of the workflow model will cause a modification of the process model, reassign the task in the execution of the process, or provide more options in the work mode in the work mode for timely Adopt the most effective resource and staff deployment solution. The new workflow system needs to adapt the dynamic modification in the process, and maintain the consistency of the process model.
Abnormal handling and error recovery problem: For a complex application system such as manufacturing, there is very normal cases of abnormalities and errors. For workflow management systems, it is not only required to play a role in normal conditions, but more importantly, it is required to be able to Flexible processing of various exceptions, and can ensure that the entire system does not crash when an error occurs in a node.
Integration into the transaction management concept: Integration in workflow management concept and model method can significantly improve the ability of workflow management system to handle large-scale business applications, and this work has received many researchers.
Application integration and openness: The workflow management system itself is a software system that completes process modeling and process management, but in order to get effective applications in the actual business of the company, it must be implemented with other or purchased products The software implements integrated, through integration, improves the application level and application efficiency of the entire enterprise. The workflow management system is an open system that provides an interface to access the components of each level of its internal levels, which ensures that the system can be integrated in the future.
Generality and mobility: Future computer environments will allow users to access information anytime, anywhere, as needed. With the popularity of information terminals and notebooks such as PDA, pager, desktop computer and other communication facilities, more and more workflow information will be sent through these channels and mechanisms, and some workflow systems have begun to support low-bandwidth mobile devices. At the same time, more research is carried out on workflow line operation, synchronous control and coordination.
Support offline operation: There are many work in actual enterprise services to be offline, supporting offline operation workflow management systems can effectively reduce the maintenance cost of enterprise data consistency, and truly close to the actual situation of enterprise applications.
Customized interface: Task interfaces and representations for end users are important to support across organizations with different capabilities and experience. The workflow management system hides complex representations and after the familiar charts and abstractions, does not require users to learn new usage.
1.2 Workflow Management System Reference Model
The type of workflow products on the market is growing, and the workflow technology has also been continuously improved. In practical applications, people need to integrate various different tools to model, archive, and analyze workflows. In order to adapt to the demand for product integration of workflow management system, Workflow Management Coalition, referred to as WFMC, proposes some specification about the workflow management system [2], defines the structure of the workflow management system and its application The application programming interface between management tools and other workflow management systems is to achieve the standardization and openness of workflow technology, thus support interoperability between heterogeneous workflow management systems and products, and other Fast and effective integration of applications. Here we will introduce the architecture of the workflow management system as an example. 1.2.1
Workflow management system architecture
Figure 1.1 shows the WFMC proposed workflow reference model. In this workflow system reference model, a five types of interfaces are defined as the core as the core, and the specific description is as follows:
Interface 1, workflow service and workflow modeling tool intergenet, including interpretation and reading and writing operations of workflow model;
Interface between interface 2, workflow services and customer applications, this is the most important interface specification, which contemplates all customer-based applications and workflow services;
Direct interface between interface 3, workflow and directly calling applications;
Interface 4, interoperability interface between workflow management systems;
Interface 5, between workflow and workflow management tools.
Figure 1.2 Architecture diagram of the workflow reference model proposed by WFMC. The architecture of this reference model gives the functional components and interfaces of the abstract workflow management system. It can meet the main features of the workflow management system and the product, which can be interoperable between workflow products. Provide a public foundation.
1.2.2
Workflow model
The workflow model is an abstract representation of the workflow, that is, abstract representation of the business process. The work current model contains all the information required to describe a process that can perform a service software system by a workflow. The ideal workflow model can clearly define the workflow in any case and can adapt to the various requirements of the user in the modeling process.
The Workflow Management Alliance defines a metamodial model for a workflow process. The maximum level of model entity attributes in the workflow process is defined in the meta-mode, and the contacts thereof also define multiple different processes in a workflow model, and sharing the same data between different processes and different models. rule. The highest level element in the meta model is shown in Figure 1.3, which is below for some important elements in the figure.
l Workflow process definition: The workflow process definition constitutes the main part of the workflow model, which contains the workflow process's own attribute, such as the ID, text description, etc., all activities and transfer information that make up the workflow process.
l Workflow activity: A workflow process is made up of one or more workflow activities, each of which is a reasonable, stand-alone work unit. Each workflow activity is a collection of work and / or automatic applications of a set of resources, which may be the smallest independent unit, or a subsystem consisting of a series of smaller independent units.
l Transfer information: During the workflow, the connection between the activity is achieved by defining the control transfer arc. Each transfer arc contains the basic information of the pre-drive activity, successive activity, and transfer conditions.
l Workflow Participants Definition: Workflow participants are elements in the organizational model, they or to perform some part of the workflow or to be responsible.
l Workflow application definition: Workflow application definition is a list of IT applications and tools that will be activated or called in the execution of the workflow. The parameters required to activate an application will be described in the definition.
l Workflow Related Data Type: The workflow related data type defines a collection of simple or complex data names that are used in workflow-related data. l Workflow related data: Workflow related data defines all variables that need to be created and used at the time of workflow instances.
1.2.3
Workflow execution service
Workflow execution services are the core of the workflow management system, in fact it is a task scheduler for the business process, and is still a certain extent, an enterprise resource distributor. The business process of the company is running under its management, monitoring and dispatching, so the performance and reliability of the workflow execution service system directly determines the operational efficiency and security of the business process. The workflow execution service consists of one or more workflows (composed of multiple workflows in the distribution environment), which provides the operating environment executed by the process instance, mainly complete the following features:
Instantiation and execution process model: Explain the process definition of the business process, based on the initial conditions and execution parameters required by the process, run the process instance and manage its running procedure. Here, it is important to point out a process model, a template that is actually a business process, which can be executed multiple times, or multiple instances related to this process model can be run at the same time.
Navigation for the execution of processes and activities: Navigate for the operation of process instances based on process definitions and workflow related data, such as starting and terminating a process instance based on the process of entering and exiting the process; depending on the relationship and activity The implementation conditions determine that the parallel or serial execution of subsequent activities; provide the user with the workflow task item information you need to operate; or start the corresponding application according to the required application information.
Completing various activities with external resources: Workflow execution services Complete interaction with external resources and users through two ways: customer application interface and direct call application interface mode. For customer application, the workflow is managed by the execution of the application via the task item list manager. Task Item List Manager provides a task item list for users to select and record the completion of the supervision work item. The user completes the corresponding task items in the task item list provided by the task item list manager, and call the application tool to complete the execution of the corresponding task when needed. After the task is executed, the user needs to modify the state of the relevant task item, Complete the logo for the task item list manager. For activities that are directly launched by the workflow, the workload directly calls the corresponding application, which also requires the appropriate pre-defined application to perform the completion of the process feedback to the workflow. The application of the workflow automatic call is primarily for the application based on the server-free application, ie automation activities.
Maintain workflow control data and workflow related data: Workflow to maintain internal status information of different processes and activity instances during execution, and various check data and recovery / recovery information for coordination and recovery, including users The necessary related data transmitted.
1.3 Main contents of each part of the paper
Based on the theoretical research and practical application of current workflow technology, especially in the development and application of workflow products at present, this paper will start with the utility performance of workflow technology, at work. In-depth research in terms of flow modeling, implementation, etc., proposed relevant theoretical programs and implementation strategies. The second chapter of the paper introduces the application of XML technology in the workflow system, introduces the process definition language XPDL, and its application in workflow. The third chapter starts from the workflow model, introduces the overall modeling tool System analysis, demand analysis, summary design, etc. The fourth chapter introduces the implementation method of JBMOD1.0 workflow modeling tool, which explains the design mode, design ideas, and specific implementation methods. The fifth chapter has summarized the entire workflow management system and made a further prospect for workflow technology related research work.
Chapter 2 Application of XML Technology in Workflow System
2.1 XML meaning
In 1996, the World Wide Web Association began to design an extensible marker language that combines SGML flexibility and powerful functions with HTML that has been widely used. This language later turned into XML inherited the specification of SGML, and actually a subset of the latter. Starting from SGML allows the design team to concentrate on simplifying existing results. SGML has provided a language that can be extended, which allows anyone to expand according to their needs. The XML is more simplified than SGML. It is largely for ease of use: people should use existing, simple and universal tools for markers, while we should also simplify computer pairs And data exchange processing. Due to too many optional functions, SGML becomes too complicated, so that it is difficult to write a general interpreter for this language, while XML interpreters are much simpler. In addition, XML makes existing Internet protocols and software more coordinated to simplify data processing and transmission. As a nice SGML subset, XML also maintains downward compatibility for existing SGML systems, so that data marked with XML can still be used in these systems, saving SGML-based industries. The renovation of the big pen, and the combination with WE B also makes them easier for access. XML is a simple and standard way to define text data. It was once called "AS CII code on the web." It is like you can use your favorite programming language to create any data structure, and then share with others in other languages used in other computing platforms. The XML tag is used to illustrate the concept you describe, and the attribute is used to control their structure. So you can define your own grammar and share it with others. XML's data description mechanism means it will become a powerful way to share information on the Internet because:
l It is open; XML can exchange data between different users and programs, regardless of its platform.
l Its self-description makes it a valid choice for B2B and corporate internal network solutions.
l No need to coordinate in advance, we can share data between procedures. Behind We will see that the XML mechanism allows us to find a structure of a class of XML documents.
2.2 XML basic characteristics
XML is a simple way to use tag tag content to transmit information. The marker is used to define the content, while the syntax of X M L allows you to define any complexity of any complexity. All this is to use ordinary text, not binary data format, which is really a very good solution for cross-platform exchange data. In fact, each common operating system (as long as it is not embedded) can handle text in some way. This is also the reason why HTML can be popular in a short period of time. XML increases this advantage to an updated level because of its own needs to arbitrarily expand XML. Since this expansion mechanism is standardized, this type of extended information can be automatically passed to any person or machine read data.
Self-description data defining the marker of the XML content is named give each element in the defined data. In tags, we will also find specific properties that provide some additional information for the described elements.
The reason why the data is self-described, and each of them has its own name, and this name is closely related to a particular content involved in the real world described in the document. So far, what we understand is very similar to HTML. Although the meaning of HTML tags is also W
3C
Organized. Take a look at the same content, HTML and XML expression methods are different:
The two forms described are both a person's name and age. In the first form implemented with XML, we can associate each of them with the concept of people in the real world. We are bound to all parts of the name, we know which one is name. As long as we understand some of the information about people, the meaning of the data is very clear for us. Instead, the HTML form formats the data into a table, but there is no clear way to explain that the content we handle is about a person's information. One of the tissue information - age-also is also as a content rather than the structure is hidden, the computer does not understand this in this description. The term "extension" in XML refers to the standard mechanism for defining new tags and their purposes. Since this is standardized, we have a fixed way to describe these new markers and communicate with other XML users. This is true for the properties we used in tags. Most of most of the XML tag sets that define the documentation are for metadata-data about data - they are used to communicate with information in a particular XML document family. Not only our data is self-explanatory, but the data about the data is also self-explanatory.
2.3 Process definition language in the workflow
Process definition (also known as workflow model) is an abstract representation of the business process, including all necessary information that makes the business process can be executed by the workflow execution service. WFMC gives a workflow process definition element model (see figure), describes the activities, workflow related data, participants, called external applications, transitions and other top elements, and inter-elements. Among them, activities are a logical work unit in the business process, which can be automatic activity that calls external applications, and the artificial activities that need to be artificially engaged, nested the sub-process activities of other independent processes or cycles, routing, etc. Active data reference will drive the data stream of the driver process, and the control flow between the activity is described by the transition, and the transition describes the scheduling relationships between the two activities and their trigger control conditions. The activities of JOIN and SPLIT transition constraints refer to the prerequisite control conditions for triggering activities and follow-up activity scheduling after the activity execution, and multiple JOIN or SPLIT transitions exist. And or OR relationships. Only all and_join jumps are triggered before they can start the execution of the activity, and as long as any OR_JOIN transition is triggered, it can trigger the execution of the active execution; after the execution is completed, it will first trigger all the transition conditions as true and_split jump, but only triggered the first one. The condition is true or_split jump, and the transition trigger is a convergent purpose activity.
Process definition language must have enough description capabilities to express the above workflow elements and relationships and require easy processing. At the same time, in order to adapt to the current distributed WFMS requirements, the process definition language must also improve distributed processing. Process definitions can be in form languages, object relationship models, text, graphics, etc., such as PLISP, WFDL, Petri Net, and BML.
XML is a data organization method. Its maximum feature is that there is no fixed format, allowing the developer defining the tag required by the program and specifying the tag of the tag, usually using the DTD Document Type Declaration, Document Type Declaration) to illustrate a class XML document. Syntax (ie label set and its organization mode). Using XML Description Workflow Process Model has the following advantages: (1) Element nested function of XML makes it a strong complex structure description capability, which can express complex workflow models, especially complex data types; (2) Direct utilization A variety of general, open, and free XML parsing processors and construction tools from XML data to corresponding data structures, greatly simplifying the implementation and cost of workflow systems; (3) Developers can flexibly change the process definition language, Most XML parsers check and process XML documents according to DTD, so changes in process definition languages may not affect program code using XML, with high scalability and flexibility; (4) XML is similar to HTML And more readily understood, more convenient for the user to construct its process model; (5) Using Java-based XML parser and; Java superior graphics support function, can construct a graphical modeling tool for the user; (6) ) Use normal text XML documents independently of platform and language, more adapt to use in heterogeneous and distributed environments; (7) Add the necessary elements or properties support process model distributed processing and execution. Although the XML process definition language applied to the actual system is currently very rare, WFMC has released its own XPDL0.03 draft in May 2001. Since the draft emphasizes the compatibility and interoperability of the existing system, there is an entity that is too refined and the complex model processing complex, so the actual system may need to make the necessary modifications according to the application requirements, such as the XPDL given XPDL. Includes sub-elements or properties that use applications and participants as active entities, cancel anonymity data types, add domain properties to process and active entities to support distributed processing, increase implicit start and end activity identifiers, etc. A large number of modifications, eventually get the DTD description of the XPDL used in the system, respectively implement the definition of the relationship between the processes, data types, workflow related data, activity sets, and jumping sets, and the relationship between them.
Regarding the standard grammatical format of XPDL, including basic data, attributes, definition methods of various workflow model entities, and give an example of using XPDL to describe the actual business process to deepen the definition language based on this XML-based workflow process definition language. understanding.
2.3.1 P
Rocess
Meta
MODEL
The meta description includes a top entity within a process definition, their relationships and attributes (including some of the monitoring and simulation purposes). At the same time, it also defines the rules that become a model set, and the use of public definition data across different processes or models. The meta model identifies the basic collection of elements and attributes for process definition exchange.
Workflow process definition element model elements and properties:
1. Workflow Process Definition
2. Workflow Process Activity
3. Transition Information
4. Workflow Participant Declaration
5. Resource Repository
6. Workflow Application Declaration
7. Workflow Relevant Data
8. System and Environmental Data
9. Data Types and Expressions
For a process definition, or in the process definition level, or by inheritance, or from the reference in the package, the following elements must be defined: Workflow Process Activity
Transition Information
Workflow Participant Specification
Workflow Application Declaration
Workflow Relevant Data
2.3.2
Extended Process
Meta
MODEL
In XPDL, a Join, a Split structure structure, and its constraints (AND, OR, XOR) instructions are embedded inside the activity (Activity), and these structures and constraints define structural relationships between activities and constraint. Since they are an integral part of the activity, the dynamic changes of the business process are very common, so the changes in structures and constraints will inevitably causing the activity definitions. In addition, the process model defined in WPDL is static, and it does not provide a mechanism for dynamically modifying any process model. In order to shield the side effects, the principle of introducing problem separation (Separation of Concerns) is not necessary. Problem is a core principle of software engineering, ie the principles that are cured, usually the ability of each part of the index, package, and operational software, one of which is related to a particular concept, objective, task or purpose. The reason why software decomposes and organizations is smaller, more easily managed and understood, and the concern of the problem is the most fundamental motivation. Each part focuses on one or more questions. Appropriate problem separation can reduce the complexity of software and improve understandability; facilitate multiplexing, non-invasive adaptation, customization, and evolution; simplifying components. Based on the principle of problem separation, this paper makes appropriate modifications and expansion for the workflow process formulated by the Workflow Management Alliance, and extracts the aggregation, branch structure and the description of their constraints (and, or xor). Introduced a new meta-model element "connect" (Connector), independent of all control information, separately encapsulated, which makes the impact of change, which is conducive to workflow model dynamics modify.
2.3.3 P
Ackage
Meta
MODEL
Multiple process definitions can be bound in a model definition. Package as a container, the purpose is to put if
Dry stand-alone process definitions and associated element data integrate, become shared resources in the package. Package element model
This includes the following types:
Workflow Process Definition
Workflow Participant Specification
Workflow Application Declaration
Workflow Relevant Data
Package dollar model is an element and attribute that identifies the process model for exchange or storage. It defines different sets
Rule, put a separate process definition with participants, application declarations, and workflow related data, etc.
Link. Some may only be defined in the package (ie model level) without the need to be defined in the process grade.
2.3.4
Elements overview
2.4 Process Definition Language Business Description
Chapter 3 System Analysis of Modeling Tools
Workflow technology is a key technique for realizing management and control of enterprise business. At present, workflow technology has become an important research direction of computer applications, and is gradually applied to the fields of service and manufacturing. However, with the continuous complexity and variation of business processes, traditional workflow models are lacking flexibility in the description and implementation of the actual business process. So we analyze and designed to enhance their support mode.
3.1 Working Circular Model
The working fluid model is based on the traditional activity network graph model. In the workflow mode diagram, the process activity and tasks are indicated by nodes, and the arc indicates the task sequence control process. Figure 3.1 shows graphical representation of each modeling element. 3.1.1
Transition
The transfer describes the simple sequential relationship between two nodes to indicate arrow arcs. In addition to starting markings, end tags, aggregate nodes, and branch nodes, one node has an input transfer and an output transfer. Or the output transfer of the branch node and the branch node can be conditional, at which point the black spot is represented in the arc line. Unlike traditional working fluid models, these conditions are defined as node properties rather than transferring properties, which is convenient for unified operations when model dynamic modifications. Considering that data transfer is invalid on the basis of no control flow, we do not define data transfer.
3.1.2
Activity
Active representative is a job that implements a business process goal, activity is implemented by an executor using resources. The activity is atomic and independent. Activity property includes a trigger business event, priority, time limit, description, etc., some attributes can be defined as expressions and are determined at runtime. The activities are divided into artificial activities and automatic activities. Automatic activity is performed by workflow enable IT applications, which can be applied by the workflow execution system control. Artificial activities are performed by an organizational unit, and some IT tools may be used during execution. Activity can issue an event, such a different process instance, and an external system can communicate.
3.1.3
Mark Node (Symbol)
Start Symbol Start tag is the start point of the process model, module or sub-process. Start tag unproved tasks, there is a subsequent task (multiple subsequent tasks use branch nodes).
End Symbol end tag is the termination point of the process model, module or sub-process. End marks have a pre-drive task (multiple pre-prodrug tasks use converge nodes), no post tasks. When a process instance runs to the end tag, the instance will complete the run, still running the active instance will be canceled, and the executor is notified.
3.1.4
Connecting Node (Connector)
In many working fluid models, such as WPDL, the logical relationships between tasks, such as aggregate, branches, synchronization, etc., which are defined in the active definition, which results in a change in the logical relationship. In our workfinder model, this logical relationship is achieved by adding a connection node between tasks, achieving separation of control flow and activity definitions, thereby avoiding modifications to the active definition when changing logical relationships. Connecting nodes and transfer together constitute the control flow in the process model.
JOIN Connector This node represents the convergence relationship during the business. Converged nodes have multiple pre-drive tasks and a subsequent task. Convergence nodes can be divided into the "and" and "AND-JoinConnector" and "and" and "and" all the pre-drive activities are required to activate the successor. Or the Converged Node OR-JOINCONNECTOR or the converged node has an or-join-end condition that will be judged after each pre-drive activity is completed, and "true" or "false" is returned. When the return value is "True", the subsequent activity is activated. Thereafter, if there is still some pre-drive activities, the successor will not be activated again. OR-JOIN-END conditions can be defined quite complicated.
Split Connector This node represents the branch relationship during the business. The branch node has a pre-drive task and multiple successive tasks. The branch node can be divided into: branch node and-splitconnector and branch nodes activate all successive activities after the forefront activity is complete. Or branch node OR-SPLITCONNECTOR This node achieves selective activation The function of the event. Or the branch node has a binary condition list that corresponds to the condition of its output transfer. After the current drum is completed, it is judged that all conditions will be activated. The different or branch node XOR-SPLITCONNECTOR is a special or branch node that allows only one subsequent activity to be activated. In terms of implementation, since it is quite difficult to judge multiple conditions, if multiple conditions returns "True", only the first activity is activated. Further, an abnormal process can be solved by this problem. Wait Connector Waiting Node is a class of time-consuming model elements, achieving the data condition satisfies, time, or time period arrives, and the waiting function occurred. Waiting nodes have a wait-end condition that will always be judged until "True" is returned, and then activates the followback node. Waiting nodes can be used to implement active synchronization functions between different process instances. Considering that Wait-End conditions may never be met, all of the best time limit is added to this condition.
3.1.5
Sub Process
The sub-process is a modeling element that supports the hierarchical process model and the top downward modeling method. Sub-process definitions have a lot of similarities with process models, both of which consist of a set of activities and connection nodes and have certain transaction semantics and abnormal behavior. Different, it is generally considered that the child process cannot be directly instantiated, and can only be used in the process model. The sub-process defines a clear public interface (input and output parameters) and public destination (function description), so that the slave process can be reused in different process models.
3.1.6
Module (Block)
1) The concept of normal module (Block) module is similar to the sub-process, which can be considered a sub-process that cannot be reused. The module does not have the same public interface as the child process, but the input and output data properties are defined as the activity.
2) The Iteration Block cycle module is used to describe a multi-active instance that requires sequential execution. On the basis of the normal module definition, the loop module adds the REPEAT-UNTIL loop condition to dynamically determine the number of internal processes. The execution of the circulation module is shown in Figure 2.3.
The input output data of the circulation module is created as the global data of the module at the first execution, and will be used by all internal module instances. For example, considering a document approval process, the document preliminary draft is an input data, a constant review, and modify the final formal document. At runtime, the loop module creates a document as global data, which is readable to all internal module instances until the REPEAT-UNTIL condition determination returns "OK".
3) Parallel Block parallel module is used to describe a plurality of the same tasks that require parallel and the number of tasks can only be determined at runtime. The parallel module contains a parallel-End condition to determine the completion of the parallel module, although there may still be an internal module instance that is still running. The execution of the parallel module is shown in the figure. Obviously, the input and output data of the parallel module should be defined as a list of data. At runtime, the number of instances of the internal module is determined by the dimension of the input data list, and the dimension of the output data is the same as the actual number of internal modules actually completed. The actual properties of joining the parallel module in Parallel-End conditions will make it a stronger expressive ability.
4) Modification Module (Modification Block) As the business environment is constantly being intensified, it is difficult to establish a determinated model for each step before running. Activity definition in the process model and the relationship between them need to be determined at runtime. The modification module provides a mechanism to allow the user to be rough in the modeling phase, while in which the moderator is notified in a work term. After the modeling person is submitted, the process instance will continue to run from the beginning marker of the modification module. Typically, modifications only affect the operation of existing instances, in some cases, modelers can also apply modifications to process models. The specific modification method is given in the following sections. The modification module is especially suitable for the following two environment: the test process, cannot predetermine the model path, the relationship between tasks must be dynamically determined; self-learning process, the process model is blank, the process model needs to be gradually improved by repeated operation. 3.2 Demand Analysis
Demand analysis is a very important link in software engineering, which is divided into the following steps: demand acquisition, demand analysis, write specifications, and demand verification.
1) Drawing the associated map: Drawing System Association Diagram is a simple model for defining the boundaries and interfaces between system and system external entities. At the same time, it also clarifies the information flow and material flow through the interface.
2) Creating a development prototype: Creating a user interface prototype When a developer or user cannot determine a demand, a user interface prototype is developed, which makes many concepts and possible things more decent. The user will make the project participant to better understand the problems to be solved by evaluating prototypes. Note To find out all the conflicts between demand documents and prototypes. 3) Analysis Feasibility: Analysis of the feasibility of demand in the permissible cost, performance requirements, analyze the feasibility of each demand implementation, clear the risk of interlinking each demand, including conflicts with other needs, external factors Dependence and technical barriers. 4) Determine the demand priority: Determine the priority application analysis method of the demand to determine the priority of the use of instances, product features, or single requirements. Determine which features or which type of product will be included based on priority. When the requirements are allowed, each change is added in a particular version and the required changes are made in that version plan. 5) Establish models for demand: The graphical analysis model for building model needs is an excellent supplementary instructions for software demand specifications. They provide different information and relationships to help find incorrect, inconsistent, missing and redundant needs. Such models include data flow diagrams, entity relationship diagrams, state transform diagrams, dialog boxes, object classes, and interactions. 6) Write a Data Dictionary: Creating a Data Dictionary Data Dictionary is defined for all data items and structures used by the system to ensure that developers use unified data definitions. In the demand phase, the data dictionary should at least define the customer data item to ensure that the customer and the development team are consistent definitions and terms. Analysis and design tools typically include data dictionary components. 7) Application Quality Function Formation: Using Quality Function Functional Function Function By a Advanced System Technology, it will link product features and properties to the importance of customers. This technology provides an analysis method to clarify those characteristics that are the most concerned.
3.3 Summary Design
1. Functional structure design:
l Use graphical methods to design or modify workflows, graphically dragging and dropping the workflow model
l rich process graphic elements, diverse activity types can adapt to different business handling requirements
l Process elements positioning, copy, paste, delete operation
l Model file unified storage, safety management
l Graphic output of the model file
l extended WPDL-XML model file storage
Data type function:
l Define model variables, process variables, activity variables, and workflow related data in the model.
Control class function:
l Provides a rich process logical expression (workflow mode), which can represent complex processes
l Support subflow design
l Support built-in block design
l Setting the workflow period L to support the combination of participants in the workflow process in an expression
Tool class features:
l and form development design tools JBFRM combined with easy settings of each process step to be executed
l Combine with the organization modeling tool JBORG to easily and accurately select the participants performed by each activity.
l Model legitimacy check
Process modeling tool JBMOD function tree view.
l file
1 New (file): Create a new workflow model.
The core part of WPDL - Definition of metallographic elements. It is these meta-model elements that form a complete workflow model. Multiple processes can be defined in a workflow model that share the same tools and participants. However, the Workflow Management Alliance wants the user to establish a workflow model including all necessary processes, related tools, and workflow participants for each business process. (The workflow model data structure is detailed in the data structure section, the model file is "extended WPDL-XML" file format)
2 Open (file): Open a workflow model file saved locally.
3 Save (file): Save a workflow model file to the local.
4 Close (file): Close a workflow model file being edited.
The file is published to the workflow engine. Implementation methods may be Java Socket programming. The client gives the server IP address. After uploading to the server, the server module is responsible for receiving and stores the file stored in the extended WPDL-XML format to the Workflow Engine Template database.
l Editor
1 Undo: Undo the previous step action.
2 Repeat: Repeat the previous step.
3 cutting / copy: cutting / copy process graphic elements
4 Paste / delete: Paste / delete process graphic elements
l process
1 New (Procedure): Create a new process.
2 Open (Procedure): Open a process saved locally.
3 Save (Procedure): Save a workflow process.
4 Close (Procedure): Close a process being edited
5 Property (Procedure): Open Process Attribute
2. Architecture design
JBMOD is a multi-document-view structure. The main modules and their functions are as follows:
n View: Includes tissue tree view, process element tree view, drawing area view, display organization information view.
n Documentation: Includes process documentation and organization documentation.
n Model Data Object: Data objects for saving process models and organization models.
n Model Syntax Check: Check the syntax and consistency errors included in the workflow model.
n File Read and Save: Responsible for reading file information from disk to model data object; and saving information in the model data object to disk files.
N Workflow Model Import and Export: By using the interface with the workflow engine, the editing and modified workflow model is exported to the database where the workflow engine is located; at the same time, the workflow model in the database in the workflow engine can also be imported. Edit and modify.
3.4 small knot
Supporting flexible modeling and dynamic modification is necessary to enhance the practicality of the workflow management system. The system analysis of the modeling tools proposed in this chapter has been detailed in detail, and the summary design has made detailed discussion, and provides a good model structure and modeling method. This meta model is suitable for modern enterprise business processes that are constantly complicated and more variable.
Chapter 4, the specific implementation of JBMOD
4.1 Design mode
The workflow modeling tool JBMOD is based on the MVC-View-Controller mode. Model: In the case of an external display content and form, the internal abstraction of software processing problem logic, encapsulates the core data, logic, and functionality of the problem.
View: Display the model data and logical relationships and status information to the user in a specific form. It gets information from the model.
Controller: It is handled by interacting between users and software. Its responsibilities are to control any changes in the model to ensure that the user interface is associated with the model; it accepts the user's input, and the input feedback to the model, and then implement it The calculation of the model is a component that works to coordinate the model and view. Usually a view has a controller.
The specific design mode of the workflow modeling tool JBMOD is shown in Figure 5. The structural relationship between MVC is shown in Figure 6.
Figure 5 Design mode of workflow modeling tool JBMOD
Figure 6 MVC structure relationship
4.2 System Data Structure Design
1, model
Multiple processes can be defined in a workflow model that share the same tools and participants. However, the Workflow Management Alliance wants the user to establish a workflow model including all necessary processes, related tools, and workflow participants for each business process. The definition format of the workflow model is as follows, and it also gives the definition structure of the entire model.
Model
[
[
[
[
[
[
[
End-model
In the workflow model header, the model is included in the model, for example, the version number of WPDL used, the model provider ID number, etc., the complete definition format is as follows:
WPDL_VERSION
Vendor
Created
[Name
[Description
[
[Documentation
[Priority_Unit
[COST_Unit
In the header definition of the workflow model, a part is a redefining header, which can not only appear in the header definition of the workflow model, but also any of the processes contained in the model. In the first definition, its format is as follows:
[Author
[Version
CharacterSet
[CODEPAGE
[Country_key
[Responsible
[Status
Consistency declarations are mainly used to describe the consistency types in the model. Consistency is the workflow management alliance to identify the software of all workflow software vendors and accept it to confirm whether it meets a level of classification of WFMC standards. Since the workflow models based on workflow software are not necessarily consistent with the metamodes defined by the Workflow Management Alliance, the Workflow Management Alliance is calibrated by setting different consistency types. The consistent class declaration defined by WPDL is as follows:
Conformance-Class
Full-blocked list
Loop-blocked loop restriction
Non-blocked unlimited
Non-Blocked has no restrictions on the defined model structure, including cyclic, branch; loop-blocked does not allow cyclic in the model, and can only be implemented by multiple executions for activities that require loop; FullBlocked There is a more stringent limit, in addition to loop-blocked to non-self-riding requirements, each branch (SPLIT) or a JOIN) point must correspond to the corresponding converge or branch point, thereby constituting a similar Module of Begln-end. In addition, for "AND-SPLIT" does not allow setting any condition, no defined transfer results are allowed for "XOR-SPLIT", that is, must guarantee one The successor activity is activated.
2, process
The workflow process definition constitutes the main part of the workflow model because it contains all activities and transfer information of the constituent model. The complete definition format is as follows:
Workflow
[In_parameters
[OUT_PARAMETERS
[
[
[
[
[
[]
[]
[
END_WORKFLOW
[Create
[Name
[Description
[Priority
[Classification
[
[Documentation
3, activity class
Begin Activity - Starting activities
End Activity - End Activity
Activity List - Active list
Subflow List - Subflow list
Block List - block list
4, connect
Connector List - List of Connector
5, transfer
Transition Information List - Transfer Information List
6, data class
Data Flow List - Data Stream List
Data Classes - Data class list
4.4 Issues I have not solved
Workflow model import and export.
Process model consistency check.
Process model printing.
Process model view of the process model.
Chapter 5 Conclusions and Prospects
5.1 Summary of this article
The emergence of workflow technology and the rapid development of the development of the company's advanced manufacturing strategy
Technical support. This article starts from the utility performance of workflow technology, modeling, executing
And the three aspects of exception handling in-depth research, these research have further improved workflow
Surgery, especially the development of workflow related products and the application in the process of actual enterprise business
It is very important. The main research conclusions of this article include:
The proposed distributed workflow modeling tool design framework, with the MVC design mode, through the three-layer structure, well-being implemented, logic, data, and view separation, making the system in scalability, Reliability and practicality have good performance. The JBMOD in the JBFlow Workflow Management system developed as prototype is well compatible with the design of the workflow engine. In the actual preliminary application, the system uses the different type of business process by analyzing the business process of enterprises. Realistic corporate activities are described in form, and strictly define the behavioral characteristics of various types of elements that make up the map, thereby expressing the mapping mechanism of the business process to the workflow model. Make it to form a complete application with the company's existing application Process system.
5.2 future outlook
System Workflow Management As an interdisciplinary research area. In addition to the technical fields involved in this article, he must consider soft sciences such as organizations and management of organizations, institutions, in order to effectively improve operational efficiency. From an application perspective, WFMS has a critical meaning of the management and improvement efficiency, and it will also become a basic part of the company's information facility: from the perspective of research, WFMC can be developed into a consistently synergistic application. Development environments Develop a variety of types of applications to support various types of collaborations or mutual organizations within the organization. References
[1] Fan Yushun, "Workflow Management Technology", Tsinghua University Press, Shiplin Publishing House, 2001
[2] Hollingsworth D. Workflow Management Coalition: The Workflow Reference Model.Document Number WFMC-TC00-1003,
Brussels
1994
[3] Zhao W, Hu wh, zhang ZX,
Zhang
SK
, WANG LF. Study and Application of Workflow Meta-Model. Journal of Software, 2003
[4] WFMC. Workflow Management Coalition Specification: Terminology & Glossary. Document Number WFMC-TC-1011,
Brussels
1996
[5] R. Alsop, "Workflow Automation Integration Requires A Large Technology Toolkit and A Structured Approach," Computer Technology Review, 1994.
[6] T. Smith, "The Future Of Work Flow Software," Inform, April 1993.
[7] WFMC. The Workflow Reference Model (TC00-1006). Workflow Management
Coalition, 1995
[8] WFMC. Interface 1: Process Definition Interchange Process Model (WFMC
TC-1016-P). Workflow Management Coalition, 1999
[9] Zhang Zhijun. A flexible workflow meta-model supporting Dynamic Modification. International Conference On Agile Manufacturing (ICAM2003),
2003 FAN YUSHUN. Workflow Modeling Method Based on Coordination THEORY.
[10] Proceedings of the ished interNational Conference-Intelligent Systems and Control,
2001: 238-241
[11] WFMC. Workflow Process Definition Interface - XML Process Definition LANGUAGE
(WFMC-TC-1025). Workflow Management Coalition, 2002
