Identify controls, components, and tasks to show in demo

[suzanne-gray]

Overview

The demo will work with a limited number of controls and components in order to show how they interact. We need to figure out which ones we want to showcase and where the variables will show up in the product.

Background

The demo needs to show:

• set a variable at the agency profile that affects the control narrative.
• agency profile variables affect multiple controls and components.

Controls
We know we want to use the control for password length, 1A-5.1.
Do we need to use all the sub-controls or just some of them?

Components
We know we will use the Drupal component as an example.
Do we need to include anything else?

User Tasks
What questions does the user need to answer in order to implement the controls?
Where in the demo do these questions get answered? (agency profile vs. project profile vs. component detail)

Steps

• export component description to google doc

References

Working doc with control info

Acceptance Criteria

• Document which password sub-controls to include in the demo
• Document which controls to include in the demo
• Document user tasks for each component and sub-control
• Document where each user task will appear in the demo

Team

🌀 Unknown/TBD/Other