![]() |
Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Unified Harmonization Process
...
Use Case Number | The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. n.n | Init1bes9.pm11.1 | |
---|---|---|---|
Brief Description | Common data elements can be entered into the metadata repository through a variety of different tools, including a UML loader, manual curation through the web interface, and forms development. There must be a common harmonization mechanism enforced by the metadata repository such that all mechanisms by which CDEs are entered can be reused by all types of users. | Brief Description | |
Actor(s) for this particular use case | Metadata Specialist | ||
Pre-condition | None. | ||
Post condition | CDEs are harmonized in the system | ||
Steps to take |
1. 2. .. | ||
Alternate Flow | None. | ||
Priority | High. | ||
Associated Links | |||
Fit criterion/Acceptance Criterion | 1.
Use Case - Descriptive Name
The Metadata Specialist should be notified or forced in some manner to harmonize the CDEs. |
Unified CDE Reuse
Use Case Number | Init1bes9.pm11.2 |
---|---|
Brief Description | Regardless of the mechanism by which a CDE was registered (automated UML, forms creation, or manual curation), CDEs should be available for reuse by any type of tooling. |
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | CDEs have been registered and harmonized via a variety of mechanisms. |
Post condition | CDEs are reused. |
Steps to take |
2. |
Alternate Flow | None. |
Priority | High. |
Associated Links |
|
Fit criterion/Acceptance Criterion | 1.
Use Case - Descriptive Name
Regardless of the mechanism by which a CDE has been registered, it must be reusable by any application. |
Association of Form Details to CDEs
Use Case | Use Case Number | n Init1bes9.pm11.n 3 |
---|---|---|
Brief Description | When CDEs are registered for reuse specifically in forms, there should be a way to associate form structure, form behavior, etc. | |
Actor(s) for this particular use case | Forms Author | |
Pre-condition | None. | |
Post condition | CDEs are registered with forms details associated. | |
Steps to take |
2. | |
Alternate Flow | None. | |
Priority | Medium. | |
Associated Links |
| |
Fit criterion/Acceptance Criterion | 1. |
Use Case - Descriptive Name
None. |
Common Form Development Tool
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. |
Use Case Number | n.n |
Brief Description | |
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 |
2. |
Alternate Flow | None. |
Priority | Low |
Associated Links |
|
Fit criterion/Acceptance Criterion | 1 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. |
Use Case Number | n.n |
Brief Description | |
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 |
1. 2. |
Alternate Flow | None. |
Priority | Low |
Associated Links | |
Fit criterion/Acceptance Criterion | 1. The tooling should be common and reusable. |
Scrollbar | ||
---|---|---|
|