Use Cases

  1. Actors and Their Roles
  2. bexee Business Process users
  3. bexee Business Process deployers
  4. bexee Business Process administrators
  5. bexee administrators

Actors and Their Roles

The bexee actors can be grouped in three different groups:

  • bexee Business Process users The users which may use deployed Business Processes. Those users trigger the instantiation of a Business Processes by calling a start activity of a process.

    In the following sections, those actors will be named bexee user s.
  • bexee Business Process deployers Before a Business Process can be instantiated, its blueprint must be deployed. These actors are responsible for deployment.

    In the following sections, those actors will be named bexee deployer s.
  • bexee Business Process administrators It must be possible to manage (start, suspend, restart, stop, delete, etc.) running instances of Business Processes. These actors are responsible for the management of running Business Process instances. In the following sections, those actors will be named bexee process admins s.

    Warning! Functionality related with these actors will not be implemented within the scope of this diploma project.

  • bexee administrators The bexee BPEL Execution Engine must be configurable as well as it must be possible to manage the bexee user s and the bexee deployer s. The actors responsible for these tasks.

    In the following sections, those actors will be named bexee admin s.

bexee Business Process users

bexee users UseCase

Use Cases description:

Get available Business Processes

  • Precondition: Some Business Processes have been deployed and activated by a bexee deployer .
  • Trigger: A list with Business Processes has been requested by a bexee user .
  • Action: The system retrieves a list of all available and activated Business Processes and renders it.
  • Postcondition: The bexee user has obtained a list of all available and activated Business Processes.
  • Variation 1: Not Business Processes are available and activated.
  • Postcondition: The bexee user receives an empty list of Business Processes.
Get the BPEL document for a Business Process
  • Precondition The Business Process for which the BPEL document has been requested is deployed and activated.
  • Trigger: A bexee user has requested the BPEL document for an available Business Process.
  • Action: The system retrieves the BPEL document of a Business Process and returns it to the bexee user .
  • Postcondition: The bexee user has obtained the BPEL document of a Business Process.
Get the WSDL document for a Business Process
  • Precondition: The Business Process for which the WSDL document has been requested is deployed and activated.
  • Trigger: A bexee user has requested the WSDL document for an available Business Process.
  • Action: The system retrieves the WSDL document for a Business Process and returns it to the bexee user .
  • Postcondition: The bexee user has obtained the WSDL document for a Business Process.
Execute a Business Process
  • Precondition: The Business Process is deployed and activated.
  • Trigger: A bexee user triggered the instantiation of a Business Process. This by calling an activity of the Business Process (e.g. Pick) which starts a new instance of the process. Such an activity is visible to the user as a Web Service.
  • Action: The system creates a new instance of a Business Process and runs it.
  • Postcondition: A new instance of a Business Process is created and run.
Check Business Process state
  • Precondition: An instance of a Business Process has been created.
  • Trigger: A bexee user requests information about the state of a Business Process instance. Within such a request, the user gives a unique identification which will identify uniquely a process instance.
  • Action: The system retrieves the state of a uniquely identified Business Process instance.
  • Postcondition: The bexee user has obtained the information about the state of a Business Process instance.
Get Business Process result
  • Precondition: An instance of a Business Process has been created and is terminated. Within such a request, the user gives a unique identification which will identify uniquely a process instance.
  • Trigger: A bexee user requests the result of a terminated Business Process instance.
  • Action: The system retrieves the result of a uniquely identified Business Process instance.
  • Postcondition: The bexee user has obtained the result of a terminated Business Process instance.

bexee Business Process deployers

bexee deployers UseCase

Use Cases description:

Get a list of deployed Business Processes

  • Precondition: Some Business Processes have been deployed.
  • Trigger: A list with Business Processes has been requested by a bexee deployer .
  • Action: The system retrieves a list of all available Business Processes and renders it.
  • Postcondition: The bexee deployer has obtained a list of all available Business Processes.
  • Variation 1: Not Business Processes are available.
  • Postcondition: The bexee deployer receives an empty list of Business Processes.
Get the BPEL document for a Business Process
  • Precondition: The Business Process for which the BPEL document has been requested is deployed.
  • Trigger: A bexee deployer has requested the BPEL document for an available Business Process.
  • Action: The system retrieves the BPEL document of a Business Process and returns it to the bexee deployer .
  • Postcondition: The bexee deployer has obtained the BPEL document of a Business Process.
Deploy a Business Process blueprint
  • Precondition: A version of a Business Process has not yet been deployed.
  • Trigger: A bexee deployer requests the deployment of a Business Process in the system. The Business Process is specified by a BPEL document.
  • Action: The Business Process is being validated and deployed in the system.
  • Postcondition: The Business Process has been deployed. The bexee deployer received a deployment confirmation
  • Variation 1: The corresponding BPEL document of a Business Process is not valid.
  • Postcondition: The Business Process has not been deployed. The bexee deployer receives an error message.
Deploy a new version of a Business Process
  • Precondition: A previous version of a Business Process has been deployed.
  • Trigger: A bexee deployer requests the deployment of a new version of a Business Process in the system.
  • Action: A new version of a Business Process is being validated and deployed in the system.
  • Postcondition: The new version of a Business Process has been deployed.

    The bexee deployer received a deployment confirmation.
  • Variation 1: The corresponding BPEL document of a new version of a Business Process is not valid.
  • Postcondition: The new version of a Business Process has not been deployed. The bexee deployer receives an error message.
Remove a Business Process
  • Precondition: A Business Process has been deployed.
  • Trigger: A bexee deployer requests the removal of a Business Process.
  • Action: The Business Process is being removed from the system.
  • Postcondition: The Business Process has been removed from the system. Removed Business Process can not be instantiated any more. Running instances of removed processes are allowed to continue until termination.
Activate/deactivate a Business Process
  • Precondition: A Business Process has been successfully deployed.
  • Trigger: A bexee deployer requests the activation/deactivation of a Business Process.
  • Action: The Business Process is activated/deactivated.
  • Postcondition: The Business Process is activated/deactivated. Deactivated Business Process can not be instantiated any more. Running instances of deactivated processes are allowed to continue until termination.

bexee Business Process administrators

bexee Business Process admins UseCase

Use Cases description:

manage running processes

The bexee process admin s can start, stop, suspend, resume, and delete running Business Process instances.

manage Business Processes

The bexee process admin s can activate, deactivate, and delete Business Processes.

bexee administrators

bexee admins UseCase

Use Cases description:

Start/stop/restart bexee

The administrator can start, stop and restart the bexee system.

Configure bexee

The administrator can configure the bexee system.

Warning! This use case can not be defined at this moment.

Manage bexee users

Create, delete update bexee user s

Manage bexee deployers

Create, delete update bexee deployer s

Manage bexee process admins

Create, delete update bexee admin s

Manage bexee admins

Create, delete update bexee admin s