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

Component Definition Completion Planning #328

Closed
3 tasks
brian-ruf opened this issue Mar 18, 2019 · 0 comments
Closed
3 tasks

Component Definition Completion Planning #328

brian-ruf opened this issue Mar 18, 2019 · 0 comments
Labels
Scope: Modeling Issues targeted at development of OSCAL formats User Story

Comments

@brian-ruf
Copy link
Contributor

User Story:

As an OSCAL developer, I need to understand what tasks the NIST OSCAL Team must accomplish to have a complete OSCAL component specification.

Goals:

  • Identify tasks that must be accomplished to achieve a viable specification.
  • Identify dependencies and sequencing.
  • Create the discrete issues (tasks) necessary to reach the viable specification.

Dependencies:

This directly supports issue #216.

Acceptance Criteria

@david-waltermire david-waltermire added this to the OSCAL 1.0 M2 milestone May 8, 2019
@david-waltermire david-waltermire added the Scope: Modeling Issues targeted at development of OSCAL formats label May 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Modeling Issues targeted at development of OSCAL formats User Story
Projects
None yet
Development

No branches or pull requests

2 participants