EGOS Low Level Component and Framework

1
EGOS Low Level Component and Framework

• F. Affiatati (1), C. R. Haddow (1), C. Müller
  (2), Y. Tan (2), G. Villemos (2)
• (1) ESA/ESOC, Robert Bosch Straße 5, 64293
  Darmstadt, Germany.
• (2) Terma GmbH, Europaplatz 5, 64293 Darmstadt,
  Germany

2
Background

• Mission Control Systems at ESOC has been based on
  infrastructure software (SCOS, SLE API, et al.)
• The evolution in the scope of the infrastructure
  has increased the complexity, leading to a
  multi-platform, multi-language, redundant
  implementation of the infrastructure requirements.

3
EGOS Architecture objective

• identify a coherent, standardised architecture
• provide common, core services
• bring together the requirements of the different
  environments
• to provide a unique Infrastructure

4
EGOS LLC and Framework

• consistent set of methodologies
• providing basic components and libraries
• an infrastructure inside the infrastructure
• provides the core elements that will glue
  together the EGOS Architecture
• easy component replacement and interoperability

5
The challenge

• The complexity of a nested infrastructure
• Technology selection
• Cross-organization activity
• Terminology harmonisation
• Re-usability of current developments
• Adopted standards

6
EGOS Framework

• The EGOS Framework has been defined as the
  composition of a framework infrastructure and a
  set of core components
• The framework thereby provides a predefined
  functional template, which is instantiated within
  each application
• The framework Infrastructure provides the
  functionality needed to glue components
  together

7
Framework Infrastructure

• provides the runtime environment for components
• provides the services for assembling components
  into an interconnected system
• provides standard services like service location
  through a service directory, configuration
  access, and event and action routing and
  processing

8
The Component

• encapsulated part of a software system that
  implements a specific service or set of services
• Users only have to consider the component
  interfaces and well-defined external behaviour
• the internal processing is not of concern
• allows replacement of components with a minimum
  of effort

9
The Service Broker

• is a broker of a consumer port
• automate the functionality of service location
• request routing and protocol handling
• hides the details of the connection to the user
• standard way of accessing services

10
Library and API

• The libraries provide a standard set of basic
  types and functionality (but non-EGOS libraries
  can be used)
• The access to libraries and service brokers is
  provided through dedicated APIs.

11
EGOS Framework Infrastructure
12
EGOS Framework Infrastructure

• provides a set of standard services, required to
  connect components within a network.
• Provides an infrastructure for building SOA
  systems.
• Covers the core RM-ODP functionality for ensuring
  distribution transparency.

13
EGOS Framework Infrastructure

• Service Directory provides the services of
  service location
• Configuration Access provides the services of
  reading and writing configuration data
• Security management of enciphering and
  deciphering as well as integrity and
  confidentiality checks

14
EGOS Framework Infrastructure

• Session Manager authentication and user session
  management
• Action Executor executes actions such as logging
  based on events
• Event Distributor distribution of events within
  the system
• Event Publisher interface for subscribing for
  events

15
System Assembly

• Applications consists of components executed
  within a component server.

16
Methodologies
17
EGOS Modelling Methodology

• Complete framework for modelling of Space Domain
  systems.
• Modelling Tool set with UML 2.0 Profile
  (MagicDraw as well as Enterprise Architect).
• Covers all RM-ODP viewpoints.
• Allows creation of technology independent view.
• Document generation tool set.

18
EGOS LLC Service Methodology

• Defines Service, Operation, parameter concepts.
• Operations specified based on standard Message
  Exchange Patterns (MEP).
• Service provisioning defined through standard
  Service Interaction Patterns (SIP).
• Modelled using the EGOSMF.

19
EGOS LLC Interface Methodology

• Closely related to the service methodology.
• Service operation MEPs mapped to functional
  interfaces through standard mapping.
• Defined using standard terminology.

20
EGOS LLC Framework Methodology

• Defines framework concepts.
• Specify the services of the infrastructure.
• Defines the standard features of all elements in
  the architecture.
• Provides development framework for the
  implementation of components.
• Tools for framework and component management to
  be developed.