|
BPEL |
|
Business Process Execution Language (BPEL) for Web services is an XML-based language designed to enable task-sharing in a distributed computing environment (including multiple organizations) using a combination of Web services. Using BPEL, a developer formally describes how a business process will take place so that any other cooperating organization can perform one or more steps in the process the same way. Using a supply chain process as an example, BPEL might be used to describe the protocol of information comprising a product order, as well as the exceptions that may arise.
|
|
Translator |
Metastorm ProVision includes a Translator, which enables you to export or import notebook contents (including objects and their properties, if applicable) in any of the following formats:
- MS Excel (form or tabular format)
- MS Word (form or tabular format)
- Comma-separated format (.csv or tabular format)
- XML (tabular format)
With Metastorm ProVision you can export object information to a formatted table with no specific data (only template headings for the object and property types), or in a file populated with the objects and properties you selected. You can import tabular-formatted object information or choose to place the imported data in a specific model or into inventory, which enables you to use it in whatever models/objects you choose.
|
|
VisioExchange |
The Visio Exchange function provides a direct interface with Visio. This interface makes it possible to populate Metastorm ProVision models from Visio diagrams.
Since Visio is a diagramming tool, not a modeler, its objects do not carry significant meaning. This requires the user to be more actively involved in mapping Visio objects into Metastorm ProVision objects. The mapping is accomplished in three key steps:
- Select Source and Target: Visio Exchange will ask the user to select a Visio diagram and then select how the diagram is to be interpreted. In effect, it asks the user to select a Metastorm ProVision modeler to map the diagram into.
- Map Objects: Visio Exchange will map the diagram objects into the objects which apply in the selected modeler. This detailed object-by-object mapping is then presented to the user. This saves the user from mapping each object one-by-one.
- Refine Mapping: The user may now go through each mapping decision and modify on an object-by-object basis. This provides the user object-by-object
|
|
RoseExchange |
The Rose Exchange function provides a direct interface with Rational Rose. This interface makes it possible to populate Metastorm ProVision from Rational Rose and, similarly, to populate Rational Rose from Metastorm ProVision.
The intended purpose of this interface is to enable a two-way data exchange between Metastorm ProVision and Rational Rose. It consists of two major functions:
- Import enables the more technical objects expressed by Rose to be incorporated into the more business-like repository of Metastorm ProVision. This provides, among other things, a way to use Rose data as the seed for developing robust business models.
- Export enables Metastorm ProVision to be used as a source for populating Rose diagrams. One very common use of Export is as part of a lifecycle handoff. Business and Analytical models developed in ProVision can be exported to Rose for technical development (detailed design and code generation). These capabilities are all accomplished by the Rose Exchange function.
These capabilities are all accomplished by the Rose Exchange function.
|
|
Together |
|
The Together Exchange function provides a direct interface with Together. This interface makes it possible to populate Metastorm ProVision from Together and, similarly, to populate Together from Metastorm ProVision.
|
|
ERwinExchange |
The ERwin Exchange function provides a direct interface with ERwin. This interface makes it possible to populate Metastorm ProVision from ERwin and, similarly, to populate ERwin from Metastorm ProVision.
The intended purpose of this interface is to enable a two-way data exchange between Metastorm ProVision and ERwin. It consists of two major functions:
- Import enables the more technical objects expressed by ERwin to be incorporated into the more business-like repository of Metastorm ProVision. This provides, among other things, a way to use ERwin data as the seed for developing robust business models.
- Export enables Metastorm ProVision to be used a source for populating ERwin diagrams. One very common use of Export is as part of a lifecycle handoff. Business and Analytical models developed in Metastorm ProVision can be exported to ERwin for technical development (detailed design and code generation).
These capabilities are all accomplished by the ERwin Exchange function.
|
|
MSProjectExchange |
|
The benefits of the MS Project Exchange applies when the user has built workflow models that express (conceptually) tasks and dependencies. The MS Project Exchange will automatically populate MS Project and enable the full functionality of that tool to be applied. The Exchange includes tasks (activities), dependencies (workflow links), cost and timing information and resource utilization.
|
|
DDLExchange |
The DDL Exchange function provides an interface with most relational database management systems that meet ANSI/ISO SQL 92 standards. This interface makes it possible to populate Metastorm ProVision from DDL scripts and, similarly, to generate DDL scripts from Metastorm ProVision.
The intended purpose of this interface is to enable a two-way data exchange between Metastorm ProVision and DDL. It consists of two major functions:
- Generation enables Metastorm ProVision to be used as a source for generating database schema in the form of DDL scripts
- Reverse engineering enables database schema in the form of DDL scripts to be brought into Metastorm ProVision to be represented as object models.
These capabilities are all accomplished by the DDL Exchange function.
|
|
C++ |
|
The C++ exchange function enables you to specify the design options for generating C++ components from class model components.
|
|
XMI |
|
The XMI Exchange function uses XML Metadata Interchange (XMI) to interface with other business modeling and reporting tools via Extended Markup Language (XML). This makes it possible to populate Metastorm ProVision from such external software that recognizes the XML format and to populate the software from Metastorm ProVision.
|
Features
