Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Overview : Process Modeling Methodology

Process Modeling Methodology
Modeling a process can be achieved in several different ways, however the following general approach reflects best practices:
Task A Define the "As is" Process
1.
2.
3.
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.
4.
5.
Task B Define the "To be" Process (Optional)
This is an iterative exercise in which you:
1.
2.
Task C 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.
Task D Hand Over for Implementation (Optional)
If the process is to be executed in a BPM environment, you should do the following:
1.
If it has not already been set, set the appropriate destination environment (this specifies the target environment where the process will be executed).
2.
3.
Task E Deployment
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.
Process Components
Process components represent reusable building blocks that encapsulate the management of a particular item in a business process. The process components form a reusable library that you can call upon in different contexts. For example, you might have an item to "verify the caller’s address/contact details" in the business process for taking out an insurance policy. This could be implemented as a sub-process and this particular process component could be used in the context of renewing an insurance policy.
Example
The following example shows a project and the associated packages and processes used in an insurance environment.
In this example, the Validate Policy process might call a sub-process in another package (for example, the Search Claim History process). This sub-process is in the same project in this example, but it could be located in a different project.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved