1 / 13

eODL and SDL in combination for components

eODL and SDL in combination for components. Harald Böhme Prof. Joachim Fischer. Overview. Motivation Mission Used modeling technologies Development Architecture Mappings Outlook. Motivation. Component development: Abstract methods Code-generation Model Driven Architecture (MDA)

vanya
Download Presentation

eODL and SDL in combination for components

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eODL and SDL in combination for components Harald Böhme Prof. Joachim Fischer

  2. Overview • Motivation • Mission • Used modeling technologies • Development Architecture • Mappings • Outlook

  3. Motivation • Component development: • Abstract methods • Code-generation • Model Driven Architecture (MDA) • Separation of aspects related and unrelated to a specific platform • Platform Independent Model (PIM) • UML 2.0 • eODL in combination with SDL • Problems with Z.130 mapping • Different component platforms  New eODL-SDL mapping

  4. Mission • Define development architecture following the MDA approach with eODL-SDL as PIM • Select a target component platform • Use Meta-Modeling as far as possible

  5. Used modeling technologies • Model Driven Architecture (MDA) • Meta Object Facility (MOF) • Mapping rules • Try to establish relation between source and target model • Implementation language mapping • “traditional” English Text

  6. eODL computational concepts 2 1 SDL 3 implementation concepts 4 5 7 PSM 6 8 Software product Development Architecture PIM CCM C++ Executable

  7. Meta-Models • eODL • Full Meta-Model, all view points are covered • SDL • Ongoing work, diploma thesis, structural aspects • CCM • Full Meta-Model for computational and implementation aspects • So far none for deployment and target environment • C++ • None

  8. computational concepts implementation concepts eODL 2 1 SDL 3 PIM 4 7 PSM C++

  9. eODL to SDL mapping • CO-Type • SDL-Agent-Type • Interface • SDL-Interface • Boost the concept Interface in SDL • Provided Port • SDL-Gate • Used Port • SDL-Interface-Variable • Interaction elements

  10. Enrichment of mapped SDL • Only structural aspects from eODL • Behavioral aspects have to be added • Provision of all Interaction elements • RPC, transitions for consumed signals • Use of environment functionality via Interface-Variables • Call to and output to • Sub-structuring of Agent-Type possible

  11. SDL to C++/CCM mapping • CCM implementation Qedo (C++) • CCM to IDL 2.6 mapping • Implementation Skeletons for business code • User sections • Integration of generated C++ code • Using the user sections • Data type mapping • Direct invocation of procedures not possible • Signal exchange, for preservation of SDL-semantic

  12. Outlook • Deployment view point mappings • SDL, CCM • Completion of Meta-models • SDL, CCM • Tools

  13. Discussion

More Related