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).
  • Attach the process-relevant data at key points (for example, at decision points or certain activities).

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

  • Propose optimizations (process changes and new automation of existing processes).
  • 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)

You should do the following:

  • 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.