Specialist Professional Services Consulting. Technology. Managed Solutions Our Understanding of ETICS II ETICS 2 Kick-Off Meeting March 2008

What is the role of VEGA in ETICS II The aim of VEGA's engagement in ETICS II from our understanding is: to assist in the adaptation of the system to requirements, as they are needed for the development of industrial software. In this context VEGA can take responsibility for the following key activities: to identify related business models in the aerospace domain; to demonstrate the profitability of ETICS to be used as an instrument for commercial software development, based on a sample application; to motivate the participation of private sector organisations in terms of a future expansion of the system; to aid to disseminate and to promote the ETICS Grid Quality Certification Model in the aerospace domain.

What applications are suited to demonstrate the usability of ETICS? Applications in our understanding should fulfil the following requirements: They should have a certain degree of complexity and should demonstrate some demands in the actual building framework which justifies the migration to the ETICS framework; They should (ideally) be multi platform applications; They should have (ideally) high building times to legitimate the use of the parallel building framework; They should be subject of further development or maintenance activities and should not have reached the end of their life cycle.

Applications proposed Two applications could serve as models for being integrated into ETICS: The ESOC Space Link Extension API (developed by VEGA); implements and provides a set of services that enable space missions to send and receive space link data units to and from a spacecraft; is used by a set of space related telemetry and telecommand systems from various commercial companies and space agencies. SCOS-2000 is: the generic mission control system software of ESA; Is originally developed to support ESA missions; is now being promoted as a software product and licenses are being granted in the fields of space research and technology. VEGA takes part of the SCOS maintenance in the context an ITIL based 1 st and 2 nd level service desk.

Specification of the applications SLE-API ~ lines of code ~ 250 classes Platforms: Solaris 8, 10 SLES , 64 bit Windows 2003 server Tools: C++, ASN.1 Python, lex, Yacc MSVC 7.0 SCOS 2000 ~ lines of code ~ 4000 classes Platforms: Solaris 8, 10 SLES bit Tools: C++ Java Perl MySQL / PHP

Build process of the SLE API

Maintenance of SCOS at ESOC

To Dos Identified restrictions of our user applications which currently may prevent the migration from customers to the ETICS framework are: License restrictions: how to deal with hardware node locked licenses in a remote and shared build environment? Disclosure of projects: how to deal with projects which are including intellectual property rights? This is typically the case in commercial applications; Licensed code: how to deal with license protected code in a shared software repository? Platform dependent code: how to deal with code which is specific to certain platforms?

Thank you for your attention... Uwe Mueller-Wilm Specialist Professional Services Consulting. Technology. Managed Solutions