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

[DESIGN] Mock-up PRA compliance feature #473

Open
21 tasks
racheledelman opened this issue Feb 11, 2025 · 0 comments
Open
21 tasks

[DESIGN] Mock-up PRA compliance feature #473

racheledelman opened this issue Feb 11, 2025 · 0 comments
Labels
story User story

Comments

@racheledelman
Copy link

Overview

As a form builder, I would like to add an OMB number and track if my form is cleared, so that I can comply with the PRA.

Context

PRA clearance is required for most forms that collect information from the public. If an already cleared form is being digitized, it will require an OIRA review at a minimum. Depending on the changes, it may need a new clearance.

We should should provide inputs for the OMB number and expiration date. Providing a cleared/not cleared flag will also help builders/organizations understand if their form is ready for publication. We anticipate that many builders will not be familiar with PRA requirements, so it will be prudent to offer some guidance as well.

  • [ ]

Acceptance Criteria

Required outcomes of the story

  • [ ]

Research Questions

  • Optional: Any initial questions for research

Tasks

Research, design, and engineering work needed to complete the story.

  • [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

  • Behavior
    • Acceptance criteria met
    • Implementation matches design decisions
  • Documentation
    • ADRs (/documents/adr folder)
    • Relevant README.md(s)
  • Code quality
    • Code refactored for clarity and no design/technical debt
    • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
    • Code is reviewed by team member
    • Code quality checks passed
  • Security and privacy
    • Automated security and privacy gates passed
  • Testing tasks completed
    • Automated tests pass
    • Unit test coverage of our code >= 90%
  • Build and deploy
    • Build process updated
    • API(s) are versioned
    • Feature toggles created and/or deleted. Document the feature toggle
    • Source code is merged to the main branch

Decisions

  • Optional: Any decisions we've made while working on this story
@racheledelman racheledelman added the story User story label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story User story
Projects
None yet
Development

No branches or pull requests

1 participant