| 1.1 |
Open-source |
Yes (GitHub) |
Yes (C2 implementation, in GitHub) |
No |
No |
Yes (GitHub) |
Yes (GitHub) |
| 1.2 |
Technical documentation |
Yes |
Yes |
No |
No |
Yes |
Yes |
| 1.3 |
Demo/training |
Yes (OpenSatKit) |
Yes (there is a demo in C2) |
No |
No |
Yes (KubOS SDK) |
Yes (NMF SDK) |
| 2 |
Flight heritage |
Yes |
No (ESA’s CHEOPS to be launched in 2019) |
No |
Yes (PicSat launched in Jan 2018) |
No (TBC) |
No (ESA’s Ops-Sat to be launched in 2019) |
| 3 |
Small footprint |
Yes |
Yes |
Yes |
Yes |
Yes |
No (Java implementation requires a powerful OBC) |
| 4.1 |
Reliability |
Yes |
Yes |
Not found |
Not found |
Yes |
Not found |
| 4.2 |
Formal specification |
Partially compliant (no centralized cFS architectural rules document.Rules are spread through documentation) |
Yes (The CORDET framework C2 implementation - user requirements) |
Partially compliant (framework claims to be fully compliant withCCSDS SOIS and ECSS PUS) |
Partially compliant (framework claims to be compliant with some ECSSPUS services) |
Partially compliant (no KubOS architectural rules document. Rules arefound through API’s documentation) |
Partially compliant (no centralized NMF architectural rules document.But, framework claims to be fully compliant with CCSDS 520.0-G-3) |
| 4.3 |
Well-defined semantics |
Partially compliant (there is no semantics model or document. Thereis a cFS sample app which contains the basic API calls and a developers user’s guide) |
Yes (CORDET C1 framework profile) |
Not found |
Yes (GERICOS UML Profile) |
Partially compliant (there is no semantics model or document. Thereare some template Mission applications which contains the basic KubOS API calls) |
Partially compliant (there is no semantics model or document. Thereis a NMF app development guide) |
| 4.4 |
Requirements traceability |
Partially compliant (cFE and cFS suite requirements exist, but arenot traced to the code) |
Yes (documented in the CORDET framework C2 implementation - userrequirements) |
Not found |
Not found |
Not found |
Partially compliant (a very short list of NMF software requirementsexist, but are not traced to the code) |
| 4.5 |
Modularity (component-based design) |
Yes |
Yes |
Not found |
Yes |
Yes |
Yes |
| 4.6 |
Portability (to several RTOS and processor cards) |
Yes (cFS OSAL allows that) |
N/A (C2 implementation goes on top of a non-defined message-passingmiddleware) |
Yes (according to the CCSDS CAST architecture documentation says so) |
Yes (GERICOS::CORE allows that) |
Yes (portability to FreeRTOS, Linux and to some CubeSat OBC’s) |
Yes (due to Java capabilities) |
| 5 |
Long-term support |
Yes (NASA support) |
Yes (ESA support) |
Yes (CAST support) |
Yes (LESIA support) |
Yes (KubOS company support) |
Not found (no explicit mention in ESA’s documentation) |
| 6 |
User-community collaboration |
Yes (through GitHub tickets) |
Yes (because CORDET C2 implementation is in GitHub) |
No |
No |
Yes (through GitHub tickets) |
Yes (through GitHub tickets) |
| 7 |
CCSDS standardization |
Yes |
Yes |
Yes |
No |
No |
Partially (Not standardized as a reference architecture by specificworking group, but it is a spin-off of CCSDS 520.0-G-3 standard) |
