FLEUR SpeAC DISTRIBUTED DESIGN METHODS FOR SPACE APPLICATIONS

1
FLEUR / SpeAC DISTRIBUTED DESIGN METHODS FOR
SPACE APPLICATIONS

• 6th NASA-ESA Workshop on Product Data Exchange-
  Open Standards for Model-Based Development -  
• 22 April 2004
• Roland Müller roland.mueller_at_astrium.eads.net
• EADS Astrium GmbH, Friedrichshafen, Germany

2
Content

• FLEUR Project Framework Goals
• Process Modell for Distributed Design
  Development
• Faster-Better-Cheaper Challenges
• Systems Engineering Approach for Spacecraft
  Development based on ECSS-E-10
• Traditional design vs. Model-based approach
• SoC Engineering Approach based on SystemC
• Ways through Levels of Abstraction
• Data Exchange to SME problems solutions
• Model-based development based on SysML
• FLEUR Pilot Demonstrator

3
Project workframe

• MEDEA is an industry-initiated pan-European
  Programme (2001 2008) for advanced co-operative
  Research and Development in Microelectronics. ?
  labeled within framework of EUREKA (E! 2365)
• SpeAC MEDEA A508 Specification and
  Algorithm/Architecture-Co-Design for Highly
  Complex Applications in Automotive and
  Communication
• Fleur MEDEA A504Flexible and Multidisciplinary
  System Design Approach for Heterogeneous
  System-on-Chip

4
Projects approach

• Analysis of critical areas in actual designs to
  identify expected future problems during design
  verification
• Analyse of state-of-the-art SoC design
  methodologies of all partners
• Support to define a methodology regarding
  heterogeneous tool environment.
• Prove of applicability by use of current designs
  of space systems.
• Consolidating the new SoC design method based on
  the experience derived from design examples.
• Work on the collection and classification of HW
  and SW design languages and EDA environments
• Introduction of pattern based design flow as a
  new approach to configure the design flow

5
Systems are recursive Methods are similar

• Big (satellite) systems
• Medium (equipment) systems
• Small systems (on chip) SoC

6
Process model Distributed Systems Design
7
Project Challenges Issues

• Projects have to handle
• Increased complexity
• Shrinking budgets
• Tightened schedules (Time-to-market)
• Faster Better Cheaper?
• Potential improvements
• Skills
• Processes
• Tools
• Tool Integration

Model basedDevelopment
8
Space Systems Engineering Phase Model
A
B
C
E
D
F
Development Processes
SystemIntegration validation
Transition to Disposal End-of-LiveRe-entranc
e
System Design
Operation
System development
Subsystem Design
Subsystem I V
Subsystem development
Software development
Phase Model based on ECSS-E-10 ESA standard
Hardware development
ASIC/FPGA/MEMS development
Support Processes
Quality Assurance Configuration
Management Project Management Logistic support
9
Development Phases vs Design Data
Feasibility Study
System Design
Development
Verification
Validation
Only extracts are listed from ECSS-E-10 standard
10
Document Driven ApproachApplication Scenario
Documents
Documents
Documents Code Prototype
Documents Code Product
If a code else except Repeat until
010010101010100101110001
A
B
C
E
D
11
Model Based ApproachApplication Scenario
A
B
C
E
D
12
Improvement potential by parallising development
effort
Traditional Timeline
SystemIntegration validation
System Design
System Acceptance Test
Improved Timeline by Model based Approach
System Design
13
Refinement Flow over Levels of Abstraction
Re- quirements DOORS
System Design SysML
Functional Simulation SystemC
Hardware Description VHDL
Physical Description Netlist ? Polygones
14
Systems Engineering
Mission Design
Validation
Phase E
Feasibility
Verification
Phase A
Integration
SystemDesign
Phase B
Assembly
Phase D
DetailedDesign
Phase C
Development
15
SystemC Engineering
Assembly
Detailed Design
SysML ?
? Netlist
Architectural Algorithm Codesign
Post Layout Simulation
UTF (Untimed Transactional Funct.) Model
Hardware Software Codesign
Place Route
TF (Timed Functional) Model
HW SW Refinement
CA (Cycle Accurate) Model
Synthesis
RT (Register Transfer) Level
Development
SystemC ? HDL
16
Codesign methods
Functional Model
UML, SysML Matlab/Simulink
Executable Functional/Architectural Model
Combined Model SystemC
Target Architecture
Real system
Source SpeAC / FLEUR Review Data Package
17
Problems in Intercompany Data Exchange
18
Projects Requests to an Exchange Format

• Covered domains shall comprise
• Requirements
• Functional architecture
• Physical Design
• Traceability
• Process / Management
• Estimation data
• Shall include support of configuration control
  information to ease integration in PDM systems

19
Independent design data representation
Subcontractor A
Prime contractor
Subcontractor B
Subcontractor C
20
Intercompany Collaboration
Engineering Management
21
Projects needs to system modelling

• capable of addressing requirements and
  performance as well as behavior and structure
• Structural modeling (class, component, object,
  package,)
• Behavior modeling (activity, state machine, use
  case,)
• Scenario modeling (interaction, timing,
  sequence,)
• integrable with other disciplines (e.g., SW, HW)
• scalable
• tool independent support

22
Example Model representation (structure diagram)
SC_MODULE(SatelliteControlSystem) sc_in
ltsensor_typegt Sensor sc_out
ltactuator_typegt Actuator sc_inoutltgroundstati
on_typegt GroundStation sc_inoutltuserequipment_typ
egt UserEquipment PowerController
pc AttitudeController ac CommunicationContro
ller cc DataBus db SC_CTOR(SatelliteCon
trolSystem) pc("pc1"), ac("ac1"), cc("cc1")
pc.Bus(db) pc.Actuator(Actuator)
ac.Bus(db) ac.Sensor(Sensor)
cc.Bus(db) cc.GroundStation(GroundStation)
cc.UserEquipment(UserEquipment)
Source SysML Review INCOSE International Workshop
23
Main Issues in Prime contractors role
Model Libraries
Model Iteration
Prime contractor
Model Execution
Design data repository
24
Pilot Demonstration ProjectApplication Scope

• Intention
• Evolving optical instruments simulatenously
  generate huge amount of data (gt100 channels,
  e.g. AVIRIS)
• Lossless compression is a must!
• Idea
• Spectral channels are highly correlated ? 3D-
  Wavelet based Transformation Entropy coding
• Enabling technology to reach CCSDS standard
• Realized as Multiprocessor SoC in a FPGA
• Usage of COTS IP components

25
Pilot Demonstration Project

• Representative example, prototyped on Xilinx FPGA

26
Design Pattern

• Product Requirements
• Reconfigurable during flight
• Change of algorithms
• Optimized for Performance
• Save encryption/encoding

• ?Design Space Exploration
• Software solution with 2 Processors
• Mixed solution with 1 processor and fixed encoder
  block

Applying a pattern to a model gives the way to
realization
27
Implementation and Outlook FLEUR / SpeAC

• Fields of Activities
• Requirement Management Tracing
• ?Doors AP233 interfaces, DoorsNet
• accessible to SME via secure web frontend
• Configuration Management
• ? OpenSource CVS Server
• accessible to SME via secure web client/server
• System Design and Modeling
• ? UML/ SysML
• Refine/extend semantics of modeling elements
• Definition of a UML/SysML profile to map SystemC
  elements to UML
• Model transformation from UML/SysML to SystemC
• ? SystemC
• Execution of models in SystemC
• ? AP233
• Mapping of additional elements

28
Acknowledgements and Activities

• The project is supported by the German government
  (Ministry of Education and Research, BMBF) under
  FLEUR (01M3065) and in the frame of Medea
  project SpeAC (A-508).
• TU Braunschweig project website, (Apr. 2004).
  http//www.ida.ing.tu-bs.de/projects/fleur
• MEDEA SpeAC (A508) project website, (Apr. 2004).
  http//speac.fzi.de
• EADS Astrium contributes to the following
  standardisation bodies
• Consultative Committee for Space Data Systems
  (CCSDS) http//www.ccsds.org
• European Cooperation for Space Standardization
  group (ECSS) http//www.ecss.nl