The present invention relates to a workflow management device and a workflow management system that can circulate information using a computer among personnel in an organization. The present invention also relates to a test scenario generation method that is used to test a workflow processing in the workflow management system.
Conventionally, a workflow management system has been proposed that manages and automates a flow of documents, information, and tasks to be delivered among staffs following a business process definition, when the staffs work using a network in an organization such as an enterprise (for example, see Patent Literature 1).
Patent Literature 1: Japanese Patent Application Laid-Open Publication No. 2002-215856
According to a conventional workflow management system, there are plural flow patterns of documents, information, and tasks depending on combinations of contents processed by staffs. For a business process including a flow branch and waiting, the number of patterns of a flow route further increases. In carrying out a system test of an operation application that operates in the workflow management system, it is necessary to sort out test cases covering all such flow routes, manually deliver each one document, and confirm whether a predetermined operation is carried out at each point on the flow route. Particularly, for a large-scale or complex operation application, much work time and labor are consumed for this system test because documents managed by the workflow management system cannot hold the same status depending on a flow transition. In other words, a flow route to carry out a system test cannot be generated from only history information of a document stored at each point on the flow route generated in the past.
The present invention has been achieved in view of the above problems. It is an object of the present invention to provide a workflow management device and a workflow management system that can automatically test a workflow processing of an operation application that operates on the workflow management system. It is another object of the present invention to provide a test scenario generation method for generating a test scenario used to test a workflow that is executed by the workflow management system.
To achieve the above object, a workflow management device according to the present invention includes a document generating unit that sets the following definitions based on a request from a client computer of a person within an organization, and generates a circular document, the definitions including: a flow definition for setting an approval route, having a set sequence of persons within the organization to whom a circular is to be circulated, to a prototype held by an operation application for generating the circular, and for changing the set approval route following an input item definition; an e-mail transmission definition for notifying presence of a circular document to a client computer of a next approver on the approval route; and the input item definition for setting application contents of the circular; a flow control unit that selects the next approver based on the flow definition and sets the selected approver to the e-mail transmission definition, when an earlier approver on the approval route completes reading of the circular; and an e-mail transmitting unit that notifies presence of the circular document to a client computer of the next approver based on the e-mail transmission definition, the workflow management device further comprising a proxy unit that records requests concerning the circular document transmitted from the client computer during the circulation of the circular document, and generates a test scenario that has the requests disposed in the order of the approval route. The workflow management device tests a workflow of the operation application, using the test scenario based on an instruction from the client computer.
According to the present invention, a workflow in a workflow management system can be tested using test scenarios collected by a proxy unit or appropriating or using the test scenario, and the labor of generating requests to carry out a workflow processing one by one in an approval route to be tested can be eliminated.
1 Workflow management system
2 Client computer
3 Server
4 Network
21, 31 Communication units
22 Web browser
23, 35 Data storages
24 Test tool
32 Authentication processor
33 Workflow engine
34 Proxy function unit
36 Control unit
241 Display processor
242 Store processor
243 Transmission processor
244 Reception processor
245 Action analyzer
331 Workflow processor
332 Document generating function
333 Flow control function
334 E-mail transmitting function
335 Proxy function setting unit
336 Test scenario managing unit
341 Request processor
342 Filtering unit
343 Data format converter
344 Data store processor
Exemplary embodiments of a workflow management device, a workflow management system, and a test scenario generation method according to the present invention will be explained in detail below with reference to the accompanying drawings.
In the following explanation, the workflow management system is applied to an organization such as an enterprise, and a circular is taken an example of a workflow. A route for circulating a document (an approval route or flow) differs depending on a kind of document such as an inquiry about a purchase of software, application of an e-mail address, a trip report, and settlement of traveling expenses. Even when documents are of the same kind, a circulation route and the order of circulating these documents differ depending on the amount to be approved, for example. In other words, when the same staff of the same department circulates documents, approval routes of the documents differ depending on the kind and the contents of the documents.
The outline of a workflow processing in the workflow management system is explained first.
The server 3 includes a workflow processor 331 and a data storage 35. The workflow processor 331 has a prototype called a business process definition for each operation application to generate a document (circular) corresponding to a kind of document. The workflow processor 331 has a document generating function 332 of generating a document (circular) from contents that are input to the business process definition, a flow control function 333 of transmitting the document to the next user based on an approval route that is set in the generated document, and an e-mail transmitting function 334 of notifying the next user that the document is circulated to this user based on an e-mail transmission definition 303 that is set in the generated document. The document generating function 332 corresponds to a document generating unit in the claims, the flow control function 333 corresponds to a flow control unit in the claims, and the e-mail transmitting function 334 corresponds to an e-mail transmitting unit in the claims.
In the flow definition 301, an approval route as the order of circulating a document set by a user is defined. The user can input this definition. Alternatively, the approval route can be set using user information including a post or a department of the user in the organization prepared in advance, or the approval route can be selected from among plural approval routes prepared in advance. The flow definition 301 includes a flow transition condition 302 which includes an approval route corresponding to the contents (application contents) of the input item definition 304, flexibility in the order of circulating a document within the approval route, and a definition that a person set in a certain input item value becomes the next approver.
The e-mail transmission definition 303 is related to the flow definition 301. In the e-mail transmission definition 303, a destination of the next user to whom a message that the circulation arrives is informed and a transmission source of this notice are defined based on the contents of the flow definition 301. For example, when circulating a document in the order of A, B, D, and I in the example shown in
The input item definition 304 concerns the application contents that are input to the document (circular). The contents that are input to the input item definition 304 are used as determination information in the flow transition condition 302 within the flow definition 301 at the time of determining whether it is necessary to change the contents of the flow definition 301.
The business process definition 300 can further include an access control definition 305 for determining whether a user who requests for reading the circular can read the document. As explained above, when a user who generates a new circular (hereinafter, “an issuer”) inputs data to a predetermined definition item of the business process definition 300, a document (circular) having a unique document ID is generated.
The document generating function 332 has a function of generating a new document having a uniquely identifiable document ID, when the issuer sets the assigned operation application (a kind of document (circular)) and the approval route, or when the issuer or the next user on the approval route (hereinafter, “an approver”) inputs the application contents into the document.
The flow control function 333 has a function of setting the e-mail address of the next approver and the e-mail address of a transmitter (an issuer or an approver) who transmits a document, into the e-mail transmission definition 303 based on the approval route of the document, when the document having a new document ID is generated. With this arrangement, the flow of the document based on the approval route is controlled. The flow control function 333 also has a function of comparing a determined document into which the application contents are input by the issuer or the approver, with a flow transition condition, determining whether the approval route needs to be changed, and changing the approval route when the change is necessary. For example, in the circulation of the purchase application in the organization shown in
The e-mail transmitting function 334 has a function of transmitting an e-mail to the next approver defined in the e-mail transmission definition 303, when a user (an issuer or an approver) on the approval route confirms and determines the application contents. This e-mail has a standard format of informing the next approver that the circular has arrived. For example, the e-mail describes a URL (uniform resource locator) that indicates a location of the circulation.
When the approval route setting screen is displayed in the client computer 2 of the issuer (step S14), the issuer sets an approval route to the flow definition 301 in the business process definition 300 (step S15). The approval route can be automatically set based on personal information of the issuer and organizational information. Alternatively, users to whom a circulation is made can be selected from a list of approvers defined in advance in the business process definition 300. When the approval route is set, the set contents are transmitted to the server 3.
The workflow processor 331 of the server 3 sets the e-mail transmission definition 303 based on the set contents (the approval route) of the flow definition 301 (step S16), or sets the e-mail address of the next approver as a destination and sets the e-mail address of the issuer as a transmission source, and generates a document as a circular (step S17). A document ID to uniquely identify the document is attached to this document. The generated document is transmitted to the issuer (step S18).
When the document is displayed in the client computer 2 of the issuer (step S19), the issuer inputs the application contents into the document thereby determining the contents (step S20), and the determined contents are transmitted to the server 3. The server 3 checks the contents input by the issuer, personal information of the issuer, and information of the organization to which the issuer belongs, and determines whether it is necessary to change the flow definition 301 (step S21). The server 3 determines whether it is necessary to change the approval route, based on the flow transition condition 302 set in advance that describes a relationship between the input item and the approval route for various operation applications. When it is necessary to change the flow definition 301 (Yes at step S21), the approval route is changed based on the flow transition condition 302 (step S22). When it is not necessary to change the flow definition 301 (No at step S21), the server 3 determines from the approval route whether the next approver is present (step S23). When the next approver is present (Yes at step S23), the server 3 transmits an e-mail to this next approver (step S24).
When the next approver receives the e-mail (step S25), the approver transmits a circulation read request to the URL included in the e-mail (step S26). This circulation read request includes the document ID. The server 3 retrieves the data storage 35 for the document corresponding to the document ID included in the circulation read request (step S27), and transmits the extracted document to the client computer 2 of the approver (step S28). When the document is displayed in the client computer 2 of the issuer (step S29), the approver inputs application contents to a necessary part of the document, and determines the contents (step S30). When the contents are determined, the contents of the document are transmitted to the server 3, and are written onto the document of the same document ID, thereby storing the document in the data storage 35 (step S31). The process proceeds to step S21, and the above processing is repeated until when the document reaches the last approver. When the next approver is not present as a result of check at step S23 (No at step S23), the workflow processing ends.
The workflow management system on which the test mode function is mounted according to the present embodiment is explained next. The workflow management system 1 has a network configuration which is the same as that shown in
The server 3 includes: a communication unit 31 that transmits and receives data to and from the client computers 2 and other communication devices connected to the network 4; an authentication processor 32 that determines whether a user is a user of this system, and that determines whether the user has manager authority when the user is the system user; a workflow engine 33 that carries out a workflow processing in the client computer 2 belonging to a predetermined organization; a proxy function unit 34 that records an access of each client computer 2 to the server 3, and generates a text scenario; and the data storage 35 that stores data such as test scenario data and operation applications.
The authentication processor 32 has a function of checking whether a user is a user of this system, and checking whether the user has manager authority when the user logs-in using an account of the manager authority. According to the present embodiment, only a user having manager authority can set a test mode. A system manager can set the manager authority account in advance. The authentication can be carried out according to a form authentication using an ID/password, or a biometrics authentication, or an IC (integrated circuit) card authentication.
The data storage 35 consists of a recording medium such as a hard disk, and stores a document (circular) generated by the workflow processing, test scenario data including a proxy setting condition and a test scenario, user personal information or user information including a post information within the organization that is used to set the flow definition 301 in the business process definition 300, and operation applications that operate on the workflow management system 1. The operation application refers to individual applications to generate a document (circular) of an inquiry about a purchase of software, an application for an e-mail address, a trip report, a settlement of traveling expenses, and the like. The application is prepared for each kind of document (circular). The document data, the test scenario data, the user information, and the operation application that are stored in the data storage 35 can be separately stored in hard disks and hardware of the server. Alternatively, a plurality of pieces of information can be combined together to be stored in one unit of hardware, and the combined information can be separately stored in plural units of hardware.
The workflow engine 33 includes: the workflow processor 331 that carries out a normal workflow processing; a proxy function setting unit 335 that sets a condition to the proxy function unit 34 to collect requests; and a test scenario managing unit 336 that manages the test scenario data stored in the data storage 35, based on an instruction from the client computer 2. The workflow processor 331 carries out the processing explained above with reference to
The proxy function setting unit 335 is a processor that carries out a setting to make the proxy function work for each operation application. The proxy function setting unit 335 has a function of transmitting to the client computer 2 a manager page to which the setting is carried out based on a request from a user having manager authority, and setting the contents set in the manager page to the proxy function unit 34. The proxy function setting unit 335 corresponds to a proxy function setting unit in the claims.
In the manager page 700, the “setting of the proxy function” link 730 changes to a page for setting the proxy function in the operation application to be tested that is selected in the list box 710. When the “set” button 740 is pressed while the test mode is ON, the contents set in the manager page 700 and in the “setting of the proxy function” link 730 are stored, and the proxy function is operated in the set contents. When the “set” button 740 is pressed while the test mode is OFF, the proxy function is stopped when the proxy function is working at present.
The port number 810 is necessary to record a request transmitted from the client computer 2. A port number of a proxy server that is set at a web browser of the client computer 2 needs to be matched with this port number. The request to be recorded 820 and the request not to be recorded 823 are used to set access destinations of a request to be recorded or not be recorded, among requests from the client computers 2. Either the request to be recorded 820 or the request not to be recorded 823 is set. The request to be recorded 820 and the request not to be recorded 823 can be added or deleted using “add” buttons 821 and 824 or “delete” buttons 822 and 825 that are disposed below the respective list boxes.
A “set” button 831 functions to store the contents that are input to the proxy function setting screen 800, and return to the manager page 700 shown in
When a “reference” button 832 is pressed, a test scenario list screen is displayed. The test scenario list screen displays a list of test scenario data recorded in the past by the operation application selected in the list box 710 of the manager page 700 shown in
The test scenario managing unit 336 has a function of carrying out a management processing of test scenario data stored in the data storage 35, based on an instruction from the user. For example, the test scenario managing unit 336 retrieves and extracts test scenario data indicated by the user, makes the client computer 2 display the list of the test scenario data, transmits the test scenario data selected by the user to the client computer 2, and deletes the test scenario data.
The proxy function unit 34 has a function of collecting requests based on setting contents of the proxy function setting screen 800 shown in
The request processor 341 has a function of temporarily obtaining a request transmitted from the client computer 2 to operate the operation application, when the test mode is ON.
The filtering unit 342 has a function of reading filter information, comparing this filter information with the obtained request, and determining whether to record the filter information into the data storage 35 as data constituting the test scenario data. Specifically, the filtering unit 342 determines whether a path of the HTTP request obtained by the request processor 341 corresponds to any one of the request to be recorded 820 and the request not to be recorded 823 on the proxy function setting screen 800 shown in
The data format converter 343 has a function of converting a request that is determined to be recorded as data constituting the test scenario data by the filtering unit 342, into data of a data format that can be recognized according to a test rule 24 of the client computer 2. For example, the data format converter 343 converts the request into a data format of XML (eXtensible Markup Language) and CSV (Comma Separated Values). The data format converter 343 corresponds to a data format converting function in the claims.
The data store processor 344 has a function of storing a request converted by the data format converter 343, into the data storage 35. In this case, a request having the same document ID as a parameter as shown in
The proxy function unit 34 in the server 3 can realize a proxy function as a module, and can be operated on a web application server that carries out a workflow processing. Alternatively, a web application server that carries out a workflow processing and a web server having a proxy function can be provided.
The data storage 23 includes a recording medium such as a hard disk, and stores test scenario data downloaded from the server 3.
The test tool 24 is called when the user generates test scenario data and executes a test scenario, and has a function of generating test scenario data and executing a test scenario. The test tool 24 includes a display processor 241, a store processor 242, a transmission processor 243, a reception processor 244, and an action analyzer 245. The test tool 24 corresponds to a test unit in the claims.
The display processor 242 has a function of displaying necessary screens on the web browser 22 based on an instruction from the action analyzer 245, and notifying an input from the user via the web browser 22 to the action analyzer 245. For example, the display processor 241 displays components necessary to carry out a test and data contents analyzed by the action analyzer 245, on the web browser 22 based on an instruction from the action analyzer 245, and transmits an action made by the user on the web browser 22 to the action analyzer 245. While the test tool 24 is the web application in the present example, the test tool 24 can be a client application. In this case, the processing on the web browser in the web application becomes the processing on the screen for the client application, not on the web browser 22.
The store processor 242 has a function of storing data into the data storage 23 based on an instruction from the action analyzer 245. For example, when receiving an instruction to urge the storing of test scenario data from the action analyzer 245, the store processor 242 stores the test scenario data into the data storage 23.
The transmission processor 243 has a function of transmitting data to a predetermined communication device via a communication unit 21 based on an instruction from the action analyzer 245. For example, as a result of analysis by the action analyzer 245, there is a necessary action to transmit a request to the server 3, out of set values of a test scenario input by the user via the display processor 241. In this case, the transmission processor 243 transmits a request including this action as request data, to the server 3 via the communication unit 21. When receiving an action to urge the obtaining of test scenario data from the action analyzer 245, the transmission processor 243 transmits a request including this action as request data, to the server 3.
The reception processor 244 has a function of receiving data transmitted via the communication unit 21, and delivering the data to the action analyzer 245. For example, the reception processor 244 receives from the server 3 a response in reply to a request transmitted from the transmission processor 243, and delivers the received response to the action analyzer 245. When a response to the action to urge the obtaining of test scenario data is received, the reception processor 244 delivers the received response to the action analyzer 245.
The action analyzer 245 has a function of analyzing an action delivered from the display processor 241 or the reception processor 244, and instructing each processor to carry out a processing based on this action. For example, when an action to urge the execution of a test scenario is received via the web browser 22, the action analyzer 245 transfers the instruction to the transmission processor 243 to transmit the request based on the test scenario. When receiving an action to urge the storing of test scenario data, the action analyzer 245 transfers the instruction to the store processor 242 to store the test scenario data. When receiving an action to call the test scenario management function of the server 3, the action analyzer 245 transfers to the transmission processor 243, the instruction to call a test scenario setting page held by the test scenario managing unit 336. While the test tool 24 is the web application in the present example, the test tool 24 can be the client application. In this case, the processing on the web browser 22 in the web application becomes the processing on the screen for the client application, not on the web browser 22.
The operation processing procedure of the workflow management system 1 in the test mode is explained below with reference to a flowchart. According to the present embodiment, only a user who has the account of manager authority can set and cancel the test mode. Therefore, the processing of determining whether a user has the account of manager authority is explained first.
First, when the user requests for a call of the manager page 700 as shown in
When the user is not the eligible user as a result of the determination, (No at step S56), the process returns to step S54 again, and the login screen is displayed. The authentication processor 32 carries out the authentication processing repeatedly. In this case, the number of times of displaying the login screen can be set to an optional number. When the user is authenticated as the eligible user (Yes at step S56) or when the user is authenticated at step S52, the authentication processor 32 checks whether the logged-in user has the account of manager authority (step S57). When the accessed user does not have an account of manager authority (No at step S57), the authentication processor 32 displays an error screen in the client computer 2 (step S59), and ends the processing. When the accessed user has the account of manager authority (Yes at step S57), the proxy function setting unit 335 transmits the manager page 700 as shown in
The proxy function setting screen 800 is displayed in the client computer 2 (step S85), and the user inputs data. When the user presses the reference button (the reference button at step S86), the proxy function setting unit 335 of the server 3 retrieves the data storage 35 for test scenario data of the operation application selected at step S81 (step S87), generates the test scenario list screen 900 as shown in
When the user selects one test scenario data from the test scenario list screen 900 (the OK button at step S91), the proxy function setting unit 335 of the server 3 closes the test scenario list screen 900, and sets a proxy setting condition of the selected test scenario data to the proxy function setting screen 800 (step S92). Thereafter, when a cancel button is selected on the test scenario list screen 900 at step S91 (the cancel button at step S91), the proxy function setting unit 335 closes the test scenario list screen 900 (step S93), and the process returns to step S85.
When the user manually inputs data at step S86 (manual input at step S86), the user manually inputs a proxy setting condition to a predetermined position of the proxy function setting screen 800 or edits the screen called by pressing the reference button (step S94). For example, when the user does not use the past proxy setting condition, the user inputs a new proxy setting condition. When the user uses the past proxy setting condition, the user edits only the part which requires a change. When the user presses the set button after inputting a proxy setting condition (the set button at step S95), the proxy function setting unit 335 of the server 3 stores the input proxy setting condition (step S96). Thereafter, when the user presses the cancel button at step S95 or when the user presses the cancel button at step S86, the proxy function setting unit 335 closes the proxy function setting screen 800 (step S97), and displays the manager page 700 (step S98).
Thereafter, when the “setting of the proxy function” link 730 is not selected (No at step S83) at step S83 and when the “setting of the proxy function” link 730 is selected (setting of the proxy function at step S99), the process returns to step S84 again, and the above processing is repeated. When the “set” button 740 on the manager page 700 is pressed (the set button at step S99), the contents (including the contents of the proxy function setting screen 800) that are input to the manager page 700 are transmitted to the server 3. The proxy function setting unit 335 sets the contents to the server 3. In other words, when the test mode is ON at step S100, the proxy function is started (step S101). When the test mode is OFF at step S100, the proxy function is stopped (step S102). Thereafter, the proxy function setting unit 335 closes the manager page 700 (step S103), and ends the proxy function setting processing. The test mode setting processing ends.
In parallel with the processing at steps S122 to S126, the workflow processor 331 of the server 3 carries out a normal workflow processing of a received request. In other words, the workflow processor 331 processes the received request (step S131), generates, updates, or deletes the document data following the request (step S132), generates a response of a result of the processing (step S133), and transmits the response to the client computer 2 (step S141). Thereafter, the client computer 2 displays the response from the server 3, and ends the request reception processing.
The client computer 2 displays the received test scenario management page 1000 (step S165), and the user selects test scenario data (step S166). Thereafter, when the user selects the “download” button 1012 on the test scenario management page 1000 (download at step S167), the test scenario managing unit 336 retrieves the data storage 35 for the checked test scenario data on the test scenario management page 1000 (step S168), and transfers the retrieved test scenario data to the client computer 2 (step S169). Upon receiving the test scenario data (step S170), the client computer 2 stores the received test scenario data into the data storage 23 of the own device (step S171), and ends the processing.
When the “delete” button 1013 on the test scenario management page 1000 is selected at step S167 (the delete button at step S167), the test scenario managing unit 336 retrieves the data storage 35 for the checked test scenario data on the test scenario management page 1000, deletes the test scenario data (step S172), and ends the processing.
When the “cancel” button 1014 on the test scenario management page 1000 is selected at step S167 (the cancel button at step S167), no processing is carried out, and the processing ends.
On the other hand, when the user selects the use or a citation of a test scenario generated in the past (No at step S201), the action analyzer 245 retrieves the data storage 23 of the own device for test scenario data (step S204). The display processor 241 displays a list of test scenario data (step S205). The client computer 2 reads the test scenario data selected, from the list of the test scenario data, by the user from the data storage 23, and displays the read test scenario data (step S206).
Thereafter, when the user edits the test scenario data after step S203 (Yes at step S207), the user edits the test scenario.
The test scenario edit screen 1800 shown in
The user edits the component or the request that is necessary to carry out a test, for each item within the component contents display area 1820, on the test scenario edit screen 1800 shown in
Thereafter, when the test scenario data is not edited at step S207 (No at step S207), the user determines whether the test scenario data is to be stored (step S209). When the test scenario data is to be stored (Yes at step S209), the store processor 242 stores the test scenario data (step S210), and ends the edit processing of the test scenario data. In this case, a test scenario data storing position can be assigned, and a recognizable data storing format (for example, the XML format or the CSV format) can be selected using the test tool. When it is determined at step S209 that the test scenario data is not stored (No at step S209), the test scenario edit processing ends.
In the addition of a component at step S202 and in the editing of test scenario data at step S208, the test tool 24 prepares components to carry out addition or deletion of a request, addition, change, or deletion of a request parameter, setting of a load pattern, repetition processing, setting of a delay time, and test result processing. By combining these parameters, a further detailed test scenario can be customized.
Thereafter, when receiving the response from the server 3 in response to the request (step S224), the client computer 2 analyzes the response (step S225), and displays a result of the analysis in the web browser 22 via the display processor 241 (step S226). The user confirms the displayed test result, and confirms whether the test is successfully carried out based on the test scenario. Confirmation contents of the test result include a confirmation of whether the server 3 correctly transmits an e-mail to the client computer 2 of the approver defined in the e-mail transmission definition 303, a confirmation of whether the server 3 correctly displays a document (circular) to the client computer 2, and a confirmation of whether scheduled persons are extracted as per the flow definition 301 and set to the e-mail transmission definition 303 in the document (circular) transmitted to the client computer 2 of the approver, for example. The user confirms whether the processing is carried out to match the contents of the request to be executed in the test scenario, by checking the display contents. The action analyzer 245 determines whether other requests are present in the test scenario (step S227). When other requests are present (Yes at step S227), the process returns to step S223. When other requests are not present (No at step S227), the test scenario execution processing ends.
According to the present embodiment, a workflow in the workflow management system can be tested efficiently. For example, conventionally, in testing a workflow in each of the approval routes of a route A, B, D, and I, a route A, B, D, and J, a route A, B, E, and K, and the like, a request for carrying out the test in each approval route is manually generated. On the other hand, according to the present embodiment, when the test mode is set to ON and when a test scenario of the route A, B, D, and I is generated, for example, the test of the workflow in this approval route A, B, D, and I can be executed using this scenario. To test the workflow in the approval route A, B, D, and J, the test scenario of the approval route A, B, D, and I can be used, by only editing the last approver “I” to change to “J”. To test the workflow in the approval route A, B, E, and F, the part “A, B” of the test scenario of the route A, B, D, and I can be used. To test a workflow in a complex approval route having a return part such as an approval route A, B, D, I, D, and J, the collected test scenarios of the route A, B, D, and I can be used. As explained above, when the workflows actually processed in the workflow management system are collected in the form of a test scenario, the labor of the user who carries out the test can be saved in executing the test of the workflow.
According to the present embodiment, a prototype called a business process definition is prepared for each operation application. Therefore, when the collected scenarios are used to change the application contents in testing the workflow, the approval route can be automatically changed according to the changed application contents. Consequently, the same test scenario can be used to test a workflow by changing the approval route according to the application contents.
When a new workflow management system is to be introduced in a certain organization, test scenarios already used in another organization having a similar structure or in another organization having a similar workflow rule can be collected and used for the test processing of the workflow in the workflow management system to be newly introduced in this organization, thereby decreasing the test load of a testing person.
As described above, the workflow management system according to the present invention is useful for an organization that carries out a workflow processing such as a reading of a circular and a testing of a workflow by using a computer.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/JP05/01213 | 1/28/2005 | WO | 00 | 9/14/2006 |