1 / 10

Migration of information along the Onion diagram

Migration of information along the Onion diagram. F. Torelli CCSDS Fall Meeting 2013 28/10/2013. Outline. Onion diagram and SOIS EDS use cases Need different EDS structures? Need horizontal transformations between layers?. Credit for the onion diagram: S. Fowell.

aurora
Télécharger la présentation

Migration of information along the Onion diagram

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Migration of information along the Onion diagram F. TorelliCCSDS Fall Meeting 201328/10/2013

  2. Outline • Onion diagram and SOIS EDS use cases • Need different EDS structures? • Need horizontal transformations between layers? Credit for the onion diagram: S. Fowell

  3. Onion diagram and SOIS EDS use cases

  4. Onion diagram and SOIS EDS

  5. SOIS EDS use and users • Who produces EDS • Device and equipment manufacturer • Types & terms • Raw data • Comm. Protocol services • Behaviour • Bus protocols • Internal equipment functions • Who produces EDS • Middleware designer • Types & terms • Raw data • Engineering data • SOIS services • Behaviour • DAP • DACP • Who produces EDS • ASW designer • Types & terms • Raw data • Engineering data • Messages • Behaviour • MTS • SW Bus • Custom functions • Who produces EDS • AIT & Operations • Types & terms • Raw SDB parameters • Engineering SDB parameters • TM/TC packets • Behaviour • PUS • Operational procedures • Test sequences

  6. Do we need different EDS structures?

  7. EDS structure and content EDS of different layers have in common • Raw data (when used) • Engineering data (when used) • Distinction between interface data description and access method EDS of different layers don’thave in common • Access method • Process description (behaviour) • Level of standardisation for interface, protocols and access methods

  8. Consistency problem Data calibration Data aggregation Data re-aggregation Could be different from MTS Could be different from PUS No standard protocol • EDS of each layer should be fully specified • For a given device, if EDS for different layers exist, consistency among them should be guaranteed

  9. Do we need horizontal transformations between layers?

  10. Open points EDS of each layer should be fully specified • EDS schema and DoT to be more general and powerful • Problem when there is not a supporting standard protocol to rely on EDS consistency along the layers • Transformation between layers to be specified • Naming and terminology for each layer to be defined Extended scope overlaps with other SW methodologies • Model driven engineering • Component based design

More Related