capture NASA profiles #108
Description
Maybe a structure like this to include class as well but not directly compared?
Include B, C and D - Most commercial companies would benefit from a comparable at these levels. A would be a whole other engagement directly with a space organization.
NASA Class A
summarize statement from - https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=7150&s=2D
Flight control system on a vehicle with humans
| Product Aspect(s) | Details | Notes |
|---|---|---|
| Operational duration: | Variable | |
| Userdata update cycle: | Variable | |
| Platform update cycle: | Variable | Likely NO OS update, but variable |
| Software Level/Class: | A | |
| Security: | Layered + Lifecycle rigor | Minimize footprint with interface and API verification focus. |
| App Capability: | Product-focused custom apps, parsing ARINC data | |
| System Constraints: | Deterministic, simple, radiation hardened, reliability | |
| Protocols: | NA | |
| IO: | ||
| Dataload/fieldload: | ||
| OS standards: | ||
| OS footprint: | ||
| Languages: | C, ADA | (B and below C++?) |
| Storage: | ||
| Memory: | ||
| CPU frequency: | ||
| CPU cores: | ||
| Tool Qualification: |
NASA Class B
NASA Class C
NASA Class D
Originally posted by @matthew-l-weber in #107 (comment)