Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

revise events specifications to reflect final system under V&V #44

Open
kiniry opened this issue Dec 18, 2021 · 3 comments
Open

revise events specifications to reflect final system under V&V #44

kiniry opened this issue Dec 18, 2021 · 3 comments
Assignees
Labels
architecture documentation Issues that relate to documentation about the system, including user and developer docs, source code ENHANCEMENT New feature or request Lando/Lobot Issues related to our Lando or Lobot specifications. On Deck Someday Issues that are not required by our current contract, but we'd like to attend to someday. specifications Issues that relate to system specifications, whether of models, code, protocols, or otherwise. SysML Issues related to our SysML specifications, or use thereof.
Milestone

Comments

@kiniry
Copy link
Member

kiniry commented Dec 18, 2021

During Task 2 we must revise our events specifications (in Lando and SysML) to reflect those events that exist in the Cryptol model and the demonstrator implementation. Like our final SysML<->Cryptol model revisions at the end of Task 1, this often means small changes on both ends of the refinement relation, but usually amounts to just some renaming to make the refinement plain.

@kiniry kiniry added documentation Issues that relate to documentation about the system, including user and developer docs, source code ENHANCEMENT New feature or request specifications Issues that relate to system specifications, whether of models, code, protocols, or otherwise. architecture On Deck Lando/Lobot Issues related to our Lando or Lobot specifications. SysML Issues related to our SysML specifications, or use thereof. labels Dec 18, 2021
@kiniry
Copy link
Member Author

kiniry commented Dec 20, 2021

Note that scenarios and events are specified using Actions in SysMLv2.

@kiniry kiniry self-assigned this Jan 5, 2022
@kiniry
Copy link
Member Author

kiniry commented Jan 15, 2022

I have sketched out the necessary revisions of the RTS system events in events.lando and in the SysML model in commit 8b37cee. What is missing from my sketch is internal events that are critical to the ASM specification and system behavior but are not yet expressed in Lando or SysML. Those still need to be added, but we can do that when we capture the ASM. Based upon this sketch I believe that @abakst should be able to finish the spec.

@kiniry
Copy link
Member Author

kiniry commented Feb 19, 2022

I have cherry-picked all commits on the branch 44-revise-events-specifications-to-refle into #70, so I'm going to remove the remote branch associated with this issue and continue the work over in feature/30-revise-and-extend-sysml-specification.

@kiniry kiniry removed this from the Task 2: Validation and Verification milestone Oct 28, 2022
@kiniry kiniry added the Someday Issues that are not required by our current contract, but we'd like to attend to someday. label Oct 28, 2022
@kiniry kiniry added this to the SysML milestone May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture documentation Issues that relate to documentation about the system, including user and developer docs, source code ENHANCEMENT New feature or request Lando/Lobot Issues related to our Lando or Lobot specifications. On Deck Someday Issues that are not required by our current contract, but we'd like to attend to someday. specifications Issues that relate to system specifications, whether of models, code, protocols, or otherwise. SysML Issues related to our SysML specifications, or use thereof.
Projects
None yet
Development

No branches or pull requests

1 participant