Process Modeling Methodology

Modeling a process can be achieved in several different ways, however the general approach described in this topic reflects best practices.

Define the "As is" Process
  • Interview business end users about their current practices.
  • Capture the process flow (either on paper first or directly in modeling tool).
  • Capture the process relevant data (either on paper first or directly in modeling tool).
    Tip: Set the appropriate destination environment on the process (this specifies the runtime environment where the process will be executed). This can be done either when first creating the process, or at any time prior to implementation. Setting the destination environment when the process is first created avoids error messages and warnings associated with modeling constructs that cannot be executed in the runtime environment.
  • Attach the process-relevant data at key points (for example, at decision points or certain activities).
  • Simulate and analyze to ensure that the "As is" process is an accurate representation of the current process.

Define the "To be" Process (Optional) This is an iterative exercise in which you:

  • Propose optimizations (process changes and new automation of existing processes).
  • Simulate to validate changes or to quantify estimated savings.
  • Define the Business Object Model and Organization Model (Optional)
  • Define a business object model that defines key business terms specific to your corporate environment (for example, in an insurance environment, a claim, claimant, and so on). This can be used as an analysis tool.
Hand Over for Implementation (Optional)
Note: If you have been using Studio for Analysts to create the process, you must switch to Studio for Designers to complete the implementation.

If the process is to be executed in a BPM environment, you should do the following:

  • If it has not already been set, set the appropriate destination environment (this specifies the target environment where the process will be executed).
  • Check the Problems view for any warnings or errors in the process.
  • Hand the process off to the solution engineer for implementation. The solution engineer will underpin the process with the necessary details (such as calls to web services and so on) that will enable the process to execute in the specified destination environment.

Result

Deployment is part of the software development cycle (design, deploy, execute). After preparing the software, some transformation, packaging, physical delivery, configuration and initialization takes place. All of these, some of which may be optional, are aspects of deployment.

For more information about deployment, see the destination-specific implementation guide.