1 / 16

The EGOS Modelling Framework

8th November 2005. EGOS Workshop 2005. Slide 2. Outline. OverviewWhy Modelling?ConceptsProcess and ExamplesArtifactsStatus and Future Plans. 8th November 2005. EGOS Workshop 2005. Slide 3. Overview. EGOS Modelling Framework has been developed as part of the XASTRO-2 TRP Study ContractModelling

les
Download Presentation

The EGOS Modelling Framework

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. 8th November 2005 The EGOS Modelling Framework N. Lindman1, A.Walsh2, P. Ellsiepen2 1European Space Agency, European Space Operations Centre, Darmstadt, Germany. 2VEGA IT GmbH, Darmstadt, Germany.

    2. 8th November 2005 EGOS Workshop 2005 Slide 2 Outline Overview Why Modelling? Concepts Process and Examples Artifacts Status and Future Plans

    3. 8th November 2005 EGOS Workshop 2005 Slide 3 Overview EGOS Modelling Framework has been developed as part of the XASTRO-2 TRP Study Contract Modelling of ESA‘s Ground System improve data exchange and software interoperability within ESA and with other organizations Based on the use of Open Standards Open Source Software Part of a wider ESA initiative concerned with the Harmonisation of Ground System Software (EG-SW-TH Phase 1 taken as input) Project is to be completed by the start of 2006

    4. 8th November 2005 EGOS Workshop 2005 Slide 4 Why Modelling? Improve Interoperability Platform Independent Standardise Data Types (Information Viewpoint) Standardise Interfaces / Services (Functional Viewpoint) Manage Complexity Abstraction for Clarity Overview of Interactions Ease of Reuse Improve Communication Visualisation via diagrams and relationships Share and discuss requirements, designs, solutions Enhance Robustness Auto-generate products (apply patterns, avoid manual mistakes) “Single Source“

    5. 8th November 2005 EGOS Workshop 2005 Slide 5 EGOSMF Concepts Based on RM-ODP Apply MDA and use UML Single Source Approach Platform Independent Model (PIM) Platform Mappings Support the Formal Definition of Requirements (Enterprise Viewpoint) Information / Data (Information Viewpoint) Interfaces / Services and Components (Functional Viewpoint) Protocols, Bindings, etc. (Communications Viewpoint) Deployment (Physical Viewpoint)

    6. 8th November 2005 EGOS Workshop 2005 Slide 6 EGOSMF Viewpoints

More Related