Jump to: navigation, search

Difference between revisions of "STP/IM Component/Transformations"

(New page: In order to provide its goal of serving as bridge between different model editors which make part of the SOA Tools Platform, the STP-IM component has to provide model transformations from ...)
 
Line 1: Line 1:
 
In order to provide its goal of serving as bridge between different model editors which make part of the SOA Tools Platform, the STP-IM component has to provide model transformations from and to these notations. The following is a list of the currently implemented transformations; in some cases they contain more than one approach, depending on the specific use case they were built for.
 
In order to provide its goal of serving as bridge between different model editors which make part of the SOA Tools Platform, the STP-IM component has to provide model transformations from and to these notations. The following is a list of the currently implemented transformations; in some cases they contain more than one approach, depending on the specific use case they were built for.
  
* [[STP/IM Component/Transformation_Approaches_From_BPMN | Approaches to transform from BPMN to STP-IM]]
+
* [[STP/IM Component/Transformation_Approaches/From_BPMN | Approaches to transform from BPMN to STP-IM]]
* [[STP/IM Component/Transformation_Approaches_From_SCA | Approaches to transform from SCA to STP-IM]]
+
* [[STP/IM Component/Transformation_Approaches/From_SCA | Approaches to transform from SCA to STP-IM]]
* [[STP/IM Component/Transformation_Approaches_To_SCA | Approaches to transform from STP-IM to SCA]]
+
* [[STP/IM Component/Transformation_Approaches/To_SCA | Approaches to transform from STP-IM to SCA]]

Revision as of 01:42, 29 May 2008

In order to provide its goal of serving as bridge between different model editors which make part of the SOA Tools Platform, the STP-IM component has to provide model transformations from and to these notations. The following is a list of the currently implemented transformations; in some cases they contain more than one approach, depending on the specific use case they were built for.