Page History
...
Use Case Number | Init1bes9.pm11.4 |
Brief Description | A common form development tool would allow users a unified way to select metadata from the repository, add forms information, build a persistence backend, and a simple front-end. |
Actor(s) for this particular use case | Forms Author |
Pre-condition | CDEs exist in the metadata repository |
Post condition | A data collection tool is created |
Steps to take |
|
Alternate Flow | None. |
Priority | Low |
Associated Links | |
Fit criterion/Acceptance Criterion | The tooling should be common and reusable. |
Fetching Forms Data
Use Case Number | Init1bes9.pm11.5 |
Brief Description | Some tools rely heavily on fetching forms and form data programmatically. In order to make this process efficient, it is desirable to fetch entire object graphs that includes the entire form, data element information, and, where applicable, the data itself. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | A form exist in the metadata repository |
Post condition | The form and (if applicable) data is entirely fetched |
Steps to take |
|
Alternate Flow | None. |
Priority | Low |
Associated Links |
|
Fit criterion/Acceptance Criterion | None. |
Form Data Mining
Use Case Number | Otherhm1.pm12.1 |
Brief Description | A common set of tooling should work out-of-the-box for performing mining and analytics on CDE-based forms data. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | Data has been collected through a common forms collection mechanism. |
Post condition | Data mining analytical results are available |
Steps to take |
|
Alternate Flow | None. |
Priority | Low |
Associated Links | |
Fit criterion/Acceptance Criterion | The tooling should be common and reusable. |