EKA to PIM4SOA Transformation Feature for Eclipse
Datasheet
Solution data | |
Name | EKA to PIM4SOA Transformation Feature for Eclipse |
Result type | Model transformation. |
Description/functionality | Transformation from EKA metamodel (ecore) to PIM4SOA (ecore) metamodel using MTF. There is ongoing work on this issue. In this project we have adopted a MDA vision to enterprise architectures as well as systems architectures to build model based systems to avoid or reduce the loss of information between the enterprise models and the ICT systems focussed on SOA. Within A6, the POP* to PIM4SOA transformation work has been focused on defining transformations of the POP* process models. Preliminary consideration has been given to service and information model transformations; their completion is subject to future work. |
Benefits to interoperability | Bridging this gap using model based transformations techniques we ensure the separation of concerns providing flexibility and traceability. This transformation does not produce a complete PIM4SOA model. This is mainly caused by two reasons. The first one is due to the fact that the current state of the POP* profile does not includes all aspects (process, organisation, product, etc.). And finally we cannot generate all PIM4SOA elements. Therefore this transformation generates in terms of PIM4SOA elements a skeleton with the following elements: documents (sketched), collaborations, collaborationUses, roles and their relationships. |
Supported models/methodologies | - |
Supported input interfaces | - |
Supported output interfaces | - |
Validation/demonstration | INTRACOM scenario. |
Standards compliance | - |
Availability |
|
License | |
Status | Prototype |
Requirements/dependencies | |
Web references |
|
ATHENA metadata | |
Contact person | Gorka Benguria, European Software Institute (ESI) |
Contributors | - |
Provided by project/activity |
|
Deliverables representing result | - |
Contribution to key result |
|
Used in pilot | - |
Deliverable providing evaluation | - |