Title: XASTRO2 EGOS 2004 15th June 2004 N' Lindman1, A'Walsh2, P' Ellsiepen2, S' Spacey2, A' Crowson3, M' D
1XASTRO2EGOS 200415th June 2004 N.
Lindman1, A.Walsh2, P. Ellsiepen2, S. Spacey2, A.
Crowson3, M. Dyck31European Space Agency,
European Space Operations Center, Darmstadt,
Germany.2VEGA IT GmbH, Darmstadt,
Germany.3Anite Systems GmbH, Darmstadt, Germany
2Presentation Outline
- Background
- Overview
- Objectives
- Technical Solution
- Reference Architecture
- Relation with CCSDS RASDS
- Example Model
- Challenges
- Conclusion
3Background
- ESA/ESOC Study Contract
- Following on from XASTRO-1 study (2002-2003)
- Modelling of ESAs Ground System to improve data
exchange and software interoperability - Part of a wider ESA initiative concerned with the
harmonisation of Ground System Software - Project started in January 2004 and scheduled to
run into early 2005
4Overview XASTRO-1 Study
- Objective Investigate if the open standard
technologies ofUML XML can be used to model a
space system and its data - Motivation improve data exchange between
customers, contractors and suppliers - Context XASTRO-1 was executed under ESAs
Innovative Technology Programme - Focus Primarily on space segment, although the
same principles would be applicable to other
segments. - Outcome available at http//www.vega.de/xastro1/
5Overview XASTRO-2 Study
- Apply same modelling approach adopted by XASTRO-1
- Focus is on the modelling of ESAs Ground System
- ESA TRP Study
- Analysis phase
- Identify requirements on framework and tools
- Development Phase
- Framework and Tools
- Ground System Models
- Coordinated with parallel XASTRO-2B study, which
focuses on modelling and applications
6Objectives
- Improve Interoperability between Ground Systems
through the formal definition of Ground System - Information
- Services
- Reference Architecture
- Requirements
- Ground Systems Architecture formalised
specification - Promote Automation in Ground System Operations
- Ground System Configuration
- Documentation Production
7Technical Solution
- Modelling Framework and Tools
- Modelling Language (Meta-model)
- Modelling Tools (Editors)
- GSIM Ground System Information Model
- Standard Types (Services and Data Models)
- MIM Mission Information Model
- CryoSat (reference mission)
- GOSIF Ground Operations Systems Information
Framework - Model Storage
- Applications (Generators/Translators, Special
Editors)
8Framework Modelling Language
- Based on MDA modelling approach and aligned with
upcoming UML 2.0 standard - Separation of concerns via viewpoints
- Hierarchical decomposition of components
- Separation of Types Instances (re-use of
building blocks) - GSIM (Types)
- MIM (Instances)
- Information and service modelling
- Requirements modelling
- External References (documents, behaviour etc.)
9Framework Viewpoints
Standardised Data Models
Information Viewpoint
Standardised Services
XASTRO-2 Framework
Functional Viewpoint
Enterprise Viewpoint
Physical Viewpoint
Communications Viewpoint
10Framework Platform Independence
- MDA supports platform independent models (PIM)
and platform specific models (PSM) - Separation of model from technology
- XASTRO-2 supports platform independence
- XASTRO-2 defines following mappings between PIM
and PSMs - XML Schema
- CORBA IDL
PIM
PSM
PSM
PSM
11Ground System Information Model
A library of reusable ground system services,
components and information types
12Mission Information Model
Mission instance of a Ground System
13Framework, Models and Applications
GOSIF Applications (XML Server)
XASTRO-2 Framework Applications (Editor)
Applications
XASTRO-2 Framework
GSIM
MIM
Framework Models
14Relationship with UML 2.0
- UML 2.0 is currently being finalised by OMG
- UML 2.0 and supporting tools not yet mature
- UML 2.0 identified as suitable modelling language
for XASTRO-2 once it is mature - Industry acceptance
- Excellent tool support
- Profile would have to be developed to incoperate
all XASTRO-2 viewpoint concepts - Translation of models between UML 2.0 and
XASTRO-2 languages should be possible - SysML, a daughter language of UML 2.0, has been
identified as even more suitable, but less mature
15Ground System Reference Architecture
- Formalise the services and information provided
by the ground systems - Promotes interoperability by formalised
definition of services to allow software
interface generation - Promotes plug play of ground system components
- Communicate the architecture unambiguously to all
stakeholders. - To understand the BIG picture!
16Reference Architecture Systems
- Systems to be considered
- MCS Kernel including Web-remote monitoring and
Telemetry Data Retrieval System - Network Interface System (NCTRS including SLE
Services) - Ground Station Back-end System (TMTCS, STC, MCM)
- Flight Dynamics System
- MCS Ancillary system Mission Planning System,
Generic Data Distribution, Generic File Transfer,
External Interfaces.
17Information Model XTCE PIM Example
18Information Model XTCE PSM
19Relationship with CCSDS RASDS
- The CCSDS System Architecture Working Group
(SAWG) defining a reference architecture for
space data systems (RASDS) - Based on an adapted version of RM-ODP
- RASDS defines a set of viewpoints specialised for
space data systems - XASTRO-2 working with SAWG and aligned with RASDS
- XASTRO-2 to provide language and tools for
developing RASDS models
20Challenges
- This is a huge undertaking
- Large and complex systems
- Large number of information types and services
with a ground system - Many different domains
- Need to focus on subset of systems
- Need to find right architecture granularity
- Need to collaborate, in particular with the
European Ground Software Technology Harmonisation
and the CCSDS. Collaboration web site deployed at
http//portal.vega.de/xastro
21Conclusions
- There is a need to harmonise ground systems from
a development, maintenance, operations and
configuration aspect - There is a need to standardize the ground systems
services and data models - There is a need to improve the information
exchange within the ground systems - This study tries to answer above needs by
providing a ground systems reference architecture
and information framework
22Thank You For Your AttentionAny Questions?