![]() |
Page History
Link dataset fields to CDEs
Use Case Number | Init1pm24.pm15.1 |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
| Fit criterion/Acceptance Criterion | 1.
Export annotations for loading
From caIntegrator, the user should be able to query the metadata repository to link dataset fields to CDEs. The data element description should be able to be imported, as well as unique identifiers/links to the CDE. It would be convenient if caIntegrator could query the metadata registry to all possible matches to all dataset fields and present them in batch to the user. | |
Use Case Number | n.n |
Brief Description | |
Actor(s) for this particular use case | Metadata Specialist. |
Pre-condition | A dataset has been created in caIntegrator. |
Post condition | All semantically equivalent CDE's have been mapped. |
Steps to take | 1. |
Alternate Flow |
|
Priority |
|
Associated Links |
| Fit criterion/Acceptance Criterion | 1.
Export XMI
| |
Use Case Number | n.n |
Brief Description |
|
Actor(s) for this particular use case |
|
Pre-condition |
|
Post condition |
|
Steps to take | 1. |
Alternate Flow | It is possible this flow is repeated later when new CDEs may be available for linking. |
Priority | Medium. |
Associated Links | |
Fit criterion/Acceptance Criterion | Further analysis may be needed to determine how a CDE is searched for. |
Export annotations for loading
Use Case |
...
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.
...
Number | Init1pm24.pm15.2 |
Brief Description | For those dataset fields that do not semantically match a CDE in the metadata repository, the user can export a file that has the field annotations that can be used to create new CDEs. Furthermore, it may be possible for the user to export a full XMI (or other file) that describes the dataset in an object-oriented way. |
...
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 | A dataset has been created in caIntegrator and an attempt has been made to match CDEs (see above). |
Post condition | A file describing the dataset fields is created. |
Steps to take |
|
Alternate Flow | None. |
Priority | Low. |
Associated Links | |
Fit criterion/Acceptance Criterion | The resulting file should be standards-based and reusable by the metadata repository in a loading scenario 1. |