document title / titre du document TRP W ORK PLAN ... - emits - ESA
document title / titre du document TRP W ORK PLAN ... - emits - ESA
document title / titre du document TRP W ORK PLAN ... - emits - ESA
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>TRP</strong> Work Plan 2005-2007<br />
Description of Activities<br />
TEC-SB/7935/dc<br />
12/Feb/09<br />
<strong>TRP</strong> Reference:<br />
Title:<br />
T607-12SW<br />
System of Systems analysis and design environment<br />
The boundaries of system design for space systems have changed significantly in the recent years. If it has been sufficient to<br />
provide single well defined pro<strong>du</strong>cts with a dedicated system in the past, the expectations of users shift towards services and<br />
support, with an entire functional chain required to provide these services. A system design needs to take into account various<br />
and partially divergent functions, to be implemented with space systems, processing and coordination functions on ground and<br />
service provision for the end user – who is not primarily interested in how a service is being established.<br />
This contextual approach requires integrating indivi<strong>du</strong>al systems originally designed for specific purposes, in order to get an<br />
optimal synergy between these elements. Examples are Earth Observation systems (geographical context and surveillance<br />
functions), communication networks (with space and ground components) as well as navigation services (with their respective<br />
spatial and potential local increment components). In the extreme we find systems like Global Earth Observation System of<br />
Systems (GEOSS) and the future Human Security SoS. In order to be able to enable a global analysis and trade-off of<br />
parameters, it is required to enhance existing development methods and tools on (indivi<strong>du</strong>al) system level to make them<br />
suitable to this system of systems.<br />
This activity shall define a methodology for the analysis and design of a system of systems. The required tools shall be<br />
prototyped and demonstrated for a multi-level system such as the combined GMES, Galileo and communication systems.<br />
The methodology needs to address hierarchical analysis approaches, based on proven and demonstrated methods from the<br />
classical system engineering domain. Languages such as UML/SysML and advanced approaches such as the “Virtual<br />
Spacecraft Design” need to be enhanced to be able to capture the increased complexity of such systems. A reference<br />
architecture for such a system shall be established.<br />
Supporting tools need to be prototyped. These tools need to support existing engineering and simulation paradigms as well as<br />
meta-modelling paradigms required for the methods identified above. The explicit support to performance modelling at the<br />
SoS level needs to be enabled with the proposed development, by providing elementary performance analysis blocks for the<br />
indivi<strong>du</strong>al systems.<br />
Deliverables:<br />
Three main types of deliverables are expected form this activity:<br />
1) A well <strong>document</strong>ed methodology for the analysis and design of a system of systems, addressing performance issues:<br />
Formal methods for system-level design and verification; Reference architecture.<br />
2) A support environment for this methodology, to establish relevant system and performance budgets and provide the<br />
elements for system-level trade-offs: System-level performance model building blocks; Architectural design tool for complex<br />
systems; ... .<br />
3) A demonstration prototype for an identified reference system.<br />
Current TRL: - Target TRL: Prototype Application Need/Date: SW operational >=2009<br />
Application/Mission: Security, GMES, GEOSS Contract Duration: 18 months<br />
SW Clause : - Dossier0 Ref.: New rqmt<br />
Consistency with Harmonisation<br />
Roadmap and Conclusions:<br />
Not directly linked to harmonised technology.<br />
Page 173 of 227