The following sections provide different use cases for using the Sybase WorkSpace Business Process language.
Top-down Use Case
A business analyst designs a model using the Analysis process language because he wants to have a global perspective on the processes of an enterprise.
Import Existing Services Use Case
A developer recovers a model (either from an Analysis model or from BPEL files) where he wants to automate processes. To do so, he needs services and he knows existing services are available in the WorkSpace environment. At this stage, the developer needs to:
Import EJB or Java Web Services Use Case
A developer designs and generates EJB or Java Web services in an OOM. He then wants to import them as service providers into a BPM in order to reuse them for automating processes in his orchestration BPM, he does not need any other type of services.
Import BPEL Use Case
A developer wants to implement in WorkSpace an already defined orchestration process. He can use PowerDesigner as a bridge for importing BPEL files into the Sybase WorkSpace Business Process. The developer needs to: