revise and extend SysML specification

[kiniry]

• bump our SysML v2 Pilot Implementation version to the January 2022 release
• revise scenarios to reflect final design and V&V (see revise scenario specifications to reflect final system under V&V #45)
• revise events to reflect final design and V&V (see revise events specifications to reflect final system under V&V #44)
• write definitions for all Project Glossary concepts that are incomplete
• further refactor and collect Project Glossary terms into sub-packages
• alphabetize Project Glossary, per-sub-package, per-package
• complete Physical Architecture by wiring up parts using cables and channels
• complete RTS Implementation Artifacts specification by defining dataflow on provided items
• encode Cryptol state machine into SysML state machine
• core ASM specification in SysML (depends on revise events specifications to reflect final system under V&V #44 for event specs)
• specify model normal behavior and exceptional behaviors, lifted from the Cryptol model, using Occurences, Time Slices, and Snapshots, mapping Occurences to Messages on device driver actions
• ensure that the appropriate invariants of the ACSL model are lifted to SysML Constraint
• figure out the appropriate means by which to lift and express ACSL models and contracts into the SysML model
• transliterate FRET requirements into SysML requirements
• transliterate NRC characteristics into SysML requirements
• add any necessary traceability properties and annotations that are not implicitly covered by our methodology
• after Lando/Lobot feature model is complete, lift that model into SysML as a variability model
• itemize necessary architecture view and generate beautiful renderings of every view for presentations and report

[kiniry]

This issue is ready to be owned by @abakst and @podhrmic as they lean into learning SysML and evolving the system specification.

[kiniry]

As covered in #40, many of these subtasks are immaterial to the initial implementation, thus I'm moving this issue to Task 2 and we'll complete these secondary specification tasks during V&V.

[kiniry]

I have started the transliteration of FRET and Lando requirements into SysML. See the new elements in the Requirements package. To complete the relevant task, the remaining/missing requirements from the FRET model need to be added to the SysML model, and model elements necessary to formally express said requirements in FRET have to be lifted to the SysML model. Doing so permits one to specify the necessary attributes and constraint expressions. See 5dbaf30.

[kiniry]

Behaviors that use SysML Occurances &c are refined from our event/action specs once they are complete.

[kiniry]

Per my message on ~HARDENS, I'm going to take ownership of this issue to drive all revisions of the SysML model to completion. I'm going to open a top-level branch on this.

[kiniry]

All of the above tasks are nice-to-haves at this point, and we can take them on again as we revise the SysMLv2 model in future IR&D or project work. As such, I'm moving this back to a Someday issue with no milestone.