Page History
Wiki Markup |
---|
{scrollbar:icons=false} |
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Init1bes4.PM10.U1 - Assist in Terminology Mappings
Use Case Number | Init1bes4.pm10.U1 |
---|---|
Brief Description | correct concepts from the correct terminologies can be a time consuming and error prone process. Tooling should be integrated with the metadata modeling process to facilitate the reuse of standard semantics when reusing standard information models or common data elements. This is especially important when deriving a model from a Domain Analysis Model (DAM). |
Actor(s) for this particular use case | Information Modeler |
Pre-condition | A model has been created and reuses one or more common data elements and/or is derived from a standard analysis model. |
Post condition | The "correct" semantic concepts are selected for reused data elements. |
Steps to take |
|
Alternate Flow | None. |
Priority | Medium |
Associated Links | |
Fit criterion/Acceptance Criterion |
|
Init1bes4.pm10.U2 - Restrict Terminology Mappings
Use Case Number | Init1bes4.pm10.U2 |
---|---|
Brief Description | In addition to providing initial suggestions based on reused metadata, it may also be desirable to restrict the available terminologies for concept selection. For example, specific domains may have terminologies that may be more appropriate than others, and different terminology services may be more appropriate for use when deriving from Domain Analysis Models (DAMs). |
Actor(s) for this particular use case | Information Modeler |
Pre-condition | A model has been created and reuses one or more common data elements and/or is derived from a standard analysis model. |
Post condition | The "correct" semantic concepts are selected for reused data elements. |
Steps to take |
|
Alternate Flow | The Information Modeler is able to broaden his search to other terminologies or terminology services if desired |
Priority | Medium |
Associated Links | |
Fit criterion/Acceptance Criterion |
|
Init1bes4.pm10.U3 - Review Terminology Mappings
Use Case Number | Init1bes4.pm10.U3 |
---|---|
Brief Description | While it is desirable for Information Modelers to have concept selection more easily facilitated, it is also desirable for Compatibility Reviewers to have review of reused concepts and terminologies more easily facilitated. Tooling should exist that performs side-by-side automated and manual comparison of concept reuse. |
Actor(s) for this particular use case | Information Modeler |
Pre-condition | An Information Modeler has created an information model, associated terminologies and concepts, and registered the model. |
Post condition | The Compatibility Reviewer completes his assessment of terminology and concept reuse. |
Steps to take |
|
Alternate Flow | None. |
Priority | Medium |
Associated Links | |
Fit criterion/Acceptance Criterion | 1. |
Wiki Markup |
---|
{scrollbar:icons=false} |