NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 11

changes.mady.by.user Unknown User (wileyal)

Saved on

compared with

New Version 12

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use Case Number
The author-assigned number to refer to each specific use case.

Init1dbw10.u1.3

Brief Description

Due to duplicate VMs in caDSR at current time, it is possible that more than one matching Value Meaning object is found in caDSR based on the concept code(s) associated with the attribute. The VM duplication will be cleaned up/merged in with a caDSR cleanup script and the items associated with each VM will be merged.

Actor(s) for this particular use case

UML Loader

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

Model is being loaded into caDSR with an enumerated value domain. More than one matching Value Meaning is found to exist for the concept associated with a permissible value.

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

Value Meaning is reused with the PV for the new value domain.

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. UML Loader searches for a concept matching the mapped concept code
2. UML Loader finds a concept code in caDSR that matches
3. UML Loader looks for a Value Meaning object associated with the Concept code and finds more than one
4. UML loader reuses the first Value Meaning object in caDSR it finds.
5. UML loader associates the value meaning with the permissible value in the newly created Value domain
6. UML Loader prints a message in the log that more than one VM was found that matched, the public Id and version of the reused VM is printed in the log with a message that it was used.

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

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? 


1. a new value meaning is created in caDSR based on the EVS concept and used in the local value domain

...