Integration of SEDS in F´ #1173
Replies: 3 comments 2 replies
-
I am going to make this a discussion, as it seems to be a conversation. |
Beta Was this translation helpful? Give feedback.
-
Since my post, I have learned that the SEDS standard is part of the International Deep Space Interoperability Standards (https://www.internationaldeepspacestandards.com/) applicable to the software engineering domain (https://nasasitebuilder.nasawestprime.com/idss2/wp-content/uploads/sites/45/2020/10/software baseline final 9-2020.pdf page 13). I take the liberty of extracting the important elements below, in case the hyperlink is broken in the future.
These standards are used in NASA's Artemis program, which is supported by several international agencies (ESA, JAXA,...), as well as by other international private partners. At the ESA MBSE 2021 workshop (https://indico.esa.int/event/386/timetable/), we can see how the large systems integrator Thales Alenia Space has implemented this adherence to the SEDS standard for its Gateway modules (https://indico.esa.int/event/386/contributions/6237/attachments/4276/6467/1715%20-%20Extending%20the%20Scale%20of%20Our%20Modelling%20Environments%20with%20CFS%20and%20SEDS.pdf). |
Beta Was this translation helpful? Give feedback.
-
I'm wondering if a framework should include this type of technology stack as well. If not, the mission should be able to incorporate it when using the framework. If I correctly interpret Uncle Bob's Clean Architecture (https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html), the SEDS stack would be part of the "Interface Adapters" layer rather than the "Frameworks & Drivers" layer. |
Beta Was this translation helpful? Give feedback.
-
Feature Description
Integrate the SEDS (SOIS-EDS - Spacecraft Onboard Interface Services Electronic Data Sheet) of the CCSDS (Consultative Committee for Spacecraft Data Systems) into the F´ framework.
An EDS [1] is an unambiguous XML representation of the functional interfaces offered by all protocols used to access data interfaces for hardware and software components.
To paraphrase @skliper [2], the main benefits of SEDS are:
The exchange of unambiguous interface definitions in a standard format between organizations/partners
Automatic generation of interface code, system models, system tests and mission operational databases
Runtime support for plug-and-play systems.
Rationale
According to the reports of the European working group SAVOIR-SAFI [3], the SW-ICDs in proprietary (company-specific) paper format of the unit suppliers will disappear and be homogenized/standardized in electronic format.
An integration of SEDS is still ongoing in the Goddard Space Flight Center cFS framework [4].
The integration of this feature in F´ would be very interesting to promote its use for primes but also for unit suppliers Flight Software.
According to @timcanham, in a discussion on the F' Community Group [5], the modification would not result from an XML change at the level of F´, but from the way we compose the packets that are sent to the Ground System.
References
Other interesting links:
Beta Was this translation helpful? Give feedback.
All reactions