...
| Expand | ||
|---|---|---|
| ||
Briefly describe the approach you’re taking to solve this problem. Provide enough information for the reader to imagine possible solution directions and get a rough sense of the scope of this proposal. The approach is to start with “left-hand” side of the automation process where compliance content is captured from a small set of sources. Authority Documents, Citations, and Glossaries are extracted from those documents, transformed into the Common Data Format specification, and loaded into the UC platform. Automation tools and AI will be used to accelerate the end-to-end process within human assistance to review and approve most steps in the process. |
| Expand | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
What does success look like? What metrics can we effect and why it is important to affect those metrics?
|
Scope and Requirements
| Expand | ||
|---|---|---|
| ||
The intent of this section is for the following: Scope Definition: defines the scope of the proposed product (or features), including what will and will not be included helping manage expectations and focus development efforts. Guideline for Development: provides detailed information on the product’s features, functionalities, user flow, and interface to guide the development team in building the product. Framework: provides high-level evaluation criteria for alternative solutions (build, buy, partner) to evaluate different routes to success. |
...