E-market architecture for supporting multiple roles and reconfigurable business porcesses

• US 20020032590A1
• Filed: 03/27/2001
• Published: 03/14/2002
• Est. Priority Date: 03/28/2000
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Perez, Carlos, Gottemukkala, Vibby, Jhingran, Anant, Kumar, Manoj, Cohen, Mitchell A., Mohan, Rakesh, Sairamesh, Jakka, Seetharaman, Karthikeyan, Anand, Rangachari
• Application Number:
  US09/818,719
• Publication Number:
  US 20020032590A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A method for allowing flexible creation and alteration of business processes within a commerce system includes using state machines to describe the actions that can be taken by particular roles at particular points in a process. The state machines are used by a commerce system to enforce validity of user actions, to track the execution of actions within an instance of the business process, to provide the user interface with a list of actions available to a user working on an instance of the business process, to provide coordination between state machines, and to allow different organizations to have varied business processes.

Claims

1. A method for representing a business process within a computing system, comprising the steps of:

defining the business process using a state-machine based representation where transitions of the state machine represent roles and actions, and states of the state machine represent stages in the business process where the commerce system is waiting for an event to occur;

identifying the actions that participants with particular roles can perform at particular stages of the business process by corresponding state in the state machine and out-going transitions from that state.

2. The method of claim 1, further comprising altering the business process by changing its state-machine based representation.

3. The method of claim 1, wherein attributes of a state-machine based representation are tailored to a particular user.

4. The method of claim 1, wherein the state-machine based representation includes means for validating that actions taken by a user are allowed by the state machine description so as to ensure that the user has a role that can perform the requested action at that state.

5. The method of claim 1, wherein the business processes and their state-machine based representations can be synchronized with other business processes by passing messages between state machines.

6. A method for executing a business process represented as a state machine running on a computing system, where transitions of the state machine represent roles of participants in the business process and actions that can be taken as part of the business process, and states of the state machine represent stages in the business process where the business process is waiting for an event to occur, the method comprising:

receiving from a user a command representing a desired action to be performed as part of the business process;

checking the role of the user within the business process and a context in which the command occurs;

if the command is allowable by a user with the role within the context, executing the command.

7. The method of claim 6, further comprising the step of displaying to users a list of possible commands to be issued by the user as part of the business process.

8. The method of claim 7, where the displayed commands are selected for display based on the user'"'"'s role within the business process, the context of the business process, and the state of the business process.

9. The method of claim 6, wherein different versions of a business process represented as different state machines share software for actions common in the different state machines, and share user interfaces by generating a means of user interaction based on the state machine descriptions.

10. The method of claim 6, where the execution of different instances of a particular business process are handled by storing a current state for each instance of the business process

11. A system for executing a business process represented as a state machine running on a computing system, where transitions of the state machine represent roles of participants in the business process and actions that can be taken as part of the business process, and states of the state machine represent stages in the business process where the business process is waiting for an event to occur, the system comprising:

means for receiving from a user a command representing a desired action to be performed as part of the business process;

means for checking the role of the user within the business process and a context in which the command occurs;

means for, if the command is allowable by a user with the role within the context, executing the command.

12. A computer program product in a computer readable medium for representing a business process within a computing system, the computer program product comprising:

first instructions for defining the business process using a state-machine based representation where transitions of the state machine represent roles and actions, and states of the state machine represent stages in the business process where the commerce system is waiting for an event to occur;

second instructions for identifying the actions that participants with particular roles can perform at particular stages of the business process by corresponding state in the state machine and out-going transitions from that state.

13. A computer program product in a computer readable medium for executing a business process within a computing system, the computer program product comprising:

first instructions for receiving from a user a command representing a desired action to be performed as part of the business process;

second instructions for checking the role of the user within the business process and a context in which the command occurs;

third instructions for, if the command is allowable by a user with the role within the context, executing the command.