ATHENA Model-Driven Interoperability (MDI) Framework
Datasheet
Solution data | |
Name | ATHENA Model-Driven Interoperability (MDI) Framework |
Result type |
|
Description/functionality | Model-driven development (MDD), and in particular OMG’s Model Driven Architecture (MDA), is emerging as the state of practice for developing modern enterprise applications and software systems. The MDD paradigm provides us with a better way of addressing and solving interoperability issues compared to earlier non-modelling approaches. |
Benefits to interoperability | The ATHENA Model-Driven Interoperability (MDI) Framework provides guidelines for how model-driven development (MDD) approaches can be applied in developing interoperable enterprise software systems. A reference guide that documents the purpose and concepts behind the model-driven interoperability results from ATHENA A5 and A6 in particular, and how to apply them. The reference guide does not cover the usage of the ATHENA A5 and A6 tools, but focuses on principles and methods. The MDI framework aims at providing guidelines for the following topics:
|
Supported models/methodologies | - |
Supported input interfaces | - |
Supported output interfaces | - |
Validation/demonstration | MDI is used internally within A6 to develop the PIM4SOA models and tools. Results of SOI has been tested in the AIDIMA e-procurement scenario. |
Standards compliance | - |
Availability | - |
License | - |
Status | - |
Requirements/dependencies | - |
Web references |
|
Composed of the following solutions | |
Conceptual | - |
Applicative | - |
Technical | - |
ATHENA metadata | |
Contact person | Brian Elvesæter, SINTEF |
Contributors | ESI, SINTEF, IBM, DFKI |
Provided by project/activity |
|
Deliverables representing result |
|
Contribution to key result |
|
Used in pilot | - |
Deliverable providing evaluation |
|