The work presented in this paper is based on a synergistic approach [1] integrating models of operators' tasks (described using the HAMSTERS notation) with models of the interactive system (described using the ICO notation) they are using. This synergistic approach makes it possible to bring together two usually independent (but complementary) representations of the same world. Even though supported by modeling and simulation tools, previous work in this area was rather theoretic focusing on concepts and principles in order to articulate this synergistic use of the models. The current article extends this line of research to address groupware applications. These extensions are performed on HAMSTERS notation in order to describe activities involving multiple users dealing with information flow, knowledge they are required to master and communication protocol (synchronous or asynchronous). Other extensions are performed on PetShop tool (supporting the ICO notation) in order to model and execute local and distant groupware applications. These extensions have been brought together by a more complex synergistic module bringing the two views together. Lastly, these extensions have been used for the modelling, design, and construction of a groupware system dedicated to collision avoidance of spacecraft with space debris. This case study is used to assess the applicability of the contributions and to identify paths for future work.

No abstract

There is a big semantic "gap" between textual information spread into the many documents (space system manuals, etc.) used in operations and what is really produced (software, hardware, procedures, spacecraft database, etc.) and used for validation (simulators, test beds, failure analysis tools, etc.). Operational user is "taken between" a huge amount of documentation and the very low level information spread into many different specialized formalisms and tools. It is very difficult to get quickly the information necessary to understand how the system works, which is a key point for many operation tasks like the design of operational procedures, alarm or error analysis, etc. A formalized model that captures the system knowledge would not only help designers and operators to catch it much more efficiently rather than in documents, but this may also be used by the computer to ease the many verification and validation tasks to be done, and may enable to keep a more efficient traceability with requirements during the whole system life-cycle. Some attempts to go towards this formalized, global and centralized system view have already been made, for instance with the "Space System Model" from the European ECSS-E-ST-70-31 standard. However, it needs to be much more enriched to take into account all the different views of the system and obtain all the expected benefits. In this paper, we present the results of a CNES R&T study called EGPO done with the help of ATOS Company to go further in this direction, initiating a richer view of the space system, and formalizing it with a customization of the SysML standard to the space domain.

In this paper, we present the Octave platform with its components and applications. Octave platform is a generic Monitoring and Control system partly built from data models. Its service oriented architecture is described with all the mechanisms implemented especially to provide genericity, extensibility and adaptability. Interoperability is also another main asset for Octave thanks to its compliance with standards such as XTCE, CCSDS and SM&C Recommendations. Furthermore, Octave provides portability by the use of Java and free COTS. Thus, Octave appears as a new generation of Monitoring and Control system and is planned to be used to implement the core of the future CNES generic ground platform. NomenclatureAPI = Application Programming Interface BEST = Beyond EAST BPEL = Business Process Execution Language BTG = Banc de Test Générique (Ground Support Equipment) CCSDS = Consultative Committee for Space Data System CNES = Centre National d'Etudes Spatiales CORBA = Common Object Request Broker Architecture M&C = Monitoring & Control OASIS = Outil d'Aide à la Structuration d'Informations Spatiales OCTAVE = Outils et Composants de Traitement, d'Acquisition, de Visualisation pour l 'Exploitation de télémesures OMG = Object Management Group O2PL = Octave Operation Procedure Language SM&C = Spacecraft Monitoring and Control SOA = Service-Oriented Architecture TM = Telemetry TC = Command XIF = Xml InterFace XTCE = Xml Telemetry & Command Exchange 1 Octave CNES project manager, CNES DCT/PS/SGE, evelyne.cortiade@cnes.fr 2 Octave CS project manager, CSSI Toulouse, pierre-alban.cros@c-s.fr 3 Engineer, CNES DCT/PS/SGE,

No abstract