NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »

Contents of this Page

Discover vocabulary for use as an external reference in a CDE

Use Case Number

init1hm2.pm22.U0

Brief Description

When defining a CDE with an extensive list of allowable values, it is desirable to be able to directly discover a vocabulary/terminology for reuse.

Actor(s) for this particular use case

Metadata Specialist

Pre-condition
The state of the system before the user interacts with it

A vocabulary of interest exists.

Post condition
The state of the system after the user interacts with it

The vocabulary has been discovered and is associated with the CDE.

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. The Metadata Specialist created a CDE
  2. The Metadata Specialist searches for a vocabulary to reference as a value set
  3. The Metadata Specialist selects the vocabulary and it is associated with the CDE

Alternate Flow
Things which would prevent the normal flow of the use case

None.

Priority
The priority of implementing the use case: High, Medium or Low

High.

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?

The user should be able to query directly from the CDE curation tool for vocabularies, and he should be able to query by keyword and free-text.

Associated Links
The following use cases are also directly relevant and overlapping: Init1hm6.pm18 - CDE service to return enumerations by reference
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?


1.
2...


  • No labels