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

Create ADR for rev 4/5 tagging approach (source: 18F/fedramp-automation: 615) #275

Open
2 of 15 tasks
danielnaab opened this issue Oct 25, 2022 · 0 comments
Open
2 of 15 tasks

Comments

@danielnaab
Copy link
Member

danielnaab commented Oct 25, 2022

Original issue: 18F#615

Extended Description
As a FedRAMP rule writer, I would like to be able to tag Schematron rules to their corresponding NIST RMF revision, and have them evaluated in the appropriate context.

Acceptance Criteria

  • Architectural decision record written with approach
  • Optionally, one or more initial rules tagged with this approach
  • Optionally, integrated into UI

Definition of Done

  • Acceptance criteria met
  • Unit test coverage of our code > 95%
  • Automated code quality checks passed
  • Security reviewed and reported
  • Reviewed against plain language guidelines
  • Code must be self-documenting
  • No local tech debt
  • Load/performance tests passed – needs to be created/automated
  • Documentation updated
  • Architectural Decision Record completed as necessary for significant design choices
  • PR reviewed & approved
  • Source code merged
@danielnaab danielnaab changed the title Create ADR for rev 4/5 tagging approach - (source: 18F/fedramp-automation: 1309773258) Create ADR for rev 4/5 tagging approach - (source: 18F/fedramp-automation: 615) Oct 26, 2022
@danielnaab danielnaab changed the title Create ADR for rev 4/5 tagging approach - (source: 18F/fedramp-automation: 615) Create ADR for rev 4/5 tagging approach (source: 18F/fedramp-automation: 615) Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants