Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Create new data elements at runtime
Use Case Number | Init1hm2.pm6.1 |
---|---|
Brief Description | Users of systems that are designed to collect data items may need to collect data elements that were not previously described by metadata. In this case, it is necessary that the user is able to create the metadata necessary to begin data capture. |
Use Case - Descriptive Name
...
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
...
Brief Description
...
...
Actor(s) for this particular use case
...
...
Pre-condition
The state of the system before the user interacts with it
...
...
Post condition
The state of the system after the user interacts with it
...
...
Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function
...
1.
2.
..
...
Alternate Flow
Things which would prevent the normal flow of the use case
...
...
Priority
The priority of implementing the use case: High, Medium or Low
...
...
Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.
...
...
Fit criterion/Acceptance Criterion
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?
...
Use Case - Descriptive Name
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case | Metadata Specialist |
---|---|
Pre-condition | Metadata for a data element does not exist |
Post condition | Metadata for the data element exists and data can be captured |
Steps to take |
2. |
Alternate Flow | None. |
Priority | High |
Associated Links | |
Fit criterion/Acceptance Criterion |
...
The data element is stored locally for reuse in local cancer center systems. It contains all the necessary metadata for sharing data (next use case). |
Share data elements at runtime
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 | Init1hm2.pm6.2 | |
---|---|---|---|
Brief Description | Once data elements are dynamically created for local use in data capture, it is necessary to publish the metadata for data sharing. It may be necessary to harmonize the metadata with other systems, but it is desirable that the metadata be managed at least locally. | Brief Description | |
Actor(s) for this particular use case | Metadata Specialist | ||
Pre-condition | The data element is locally available. | ||
Post condition | The data element is shared with other organizations in a distributed fashion and contains all metadata necessary for data sharing. | ||
Steps to take |
2. | ||
Alternate Flow | None. | ||
Priority | High. | ||
Associated Links | | ||
Fit criterion/Acceptance Criterion | 1. |
...
| The data elements are available to other researchers for reuse, and all metadata necessary for data sharing is available. |
---|
Reuse data elements at runtime
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 | Init1hm2.pm6.3 | |
---|---|---|---|
Brief Description | Data elements that have been created dynamically locally and shared should be reusable by other researchers and organizations. Users should be able to browse for, select, and reuse them in their data collection forms. | Brief Description | |
Actor(s) for this particular use case | Metadata Specialist | ||
Pre-condition | Data elements are shared by other users in other organizations. | ||
Post condition | Shared data elements are reused for data collection. | ||
Steps to take |
1. 2. | ||
Alternate Flow | None. | ||
Priority | High. | ||
Associated Links | |||
Fit criterion/Acceptance Criterion | 1.
...
Data elements are reused, data can be captured, and data can be shared based on reused metadata. |
Load and retrieve entire models
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 | Init1hm2.pm6.4 | |
---|---|---|---|
Brief Description | It is often more convenient to pull back or push entire models rather than single elements at a time. This is especially important for systems that are using models to build queries and allow for the extension of models. | Brief Description | |
Actor(s) for this particular use case | Metadata Specialist | ||
Pre-condition | None. | ||
Post condition | The entire model is fetched from the repository. | ||
Steps to take |
2. | ||
Alternate Flow | It is not necessary that a tool enter a model in its entirety in order for it to be retrieved in its entirety. | ||
Priority | High | ||
Associated Links | | ||
Fit criterion/Acceptance Criterion | 1 None. |
Scrollbar | ||
---|---|---|
|