-
Notifications
You must be signed in to change notification settings - Fork 123
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
Create a very basic example to trace one control through the OSCAL models. #141
Comments
Since we are still working on this, and partially putting it through its paces in a conference talk case study, it seems we are still working on this in the new sprint. Moving to Sprint 61. @Compton-NIST, feel free to correct or we can discuss unassigning this one and throwing it into the backlog for now. |
We need to revisit this in the context of the case study: keep it separate, roll it in, how to align that work with this. AJ will try to plan a meeting with @Compton-NIST in the beginning of Sprint 63 in February to determine next steps and whether to move this forward. |
@Compton-NIST and I were unable to sync this past week because of my tardiness on this, we will sync on this when he is available. Tentatively moving to Sprint 63 in the interim, possibly moving to backlog if we have prior priorities at the moment (seems we do!). |
I talked with Chris today and we agreed that this is important, but not an urgent priority, and we will move it to the backlog. We will need to sync up at a later date, perhaps in the next few weeks.
We need to keep addressing these key concerns and then plan the road ahead, but later once we review the backlog and reorganize it a little. So into the backlog we go with this issue for now. :-) |
At the 11/9 Triage Meeting: we could make the Blossom example as an example...possible create a page on OSCAL Pages to explain. |
User Story:
As an OSCAL user, I would like an example that demonstrates how a single control is depicted in the OSCAL models.
Goals:
Using AC-8, System Use Notification, develop model content and documentation.
A minimal application script may accompany this content if needed. (Hello, World-style application)
Dependencies:
This example is based on initial workflow research in the BloSS@M project.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: