Page History

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.

Init1dbw10.u1- Load value Meaning

Brief Description

a model is being loaded into caDSR containing enumerations for an attribute in the model.  The Uml loader needs to create a new value domain in caDSR, or reuse a Value Domain, with the correct Permissible Value Set associated with it.  

Actor(s) for this particular use case

UML Loader

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

UML Model serialized in XMI containing a local value domain with enumerations

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

a new value domain is created or an existing value domain is reused

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. Using the UML attribute mapped concept code, search caDSR for match
2. traverse the caDSR concept associated items for existing Value Meaning
3. a Value Meaning object administered item based on the concept code is found in caDSR
4. the loader reuses the existing value meaning in caDSR as the semantic basis for the PV (UML attribute) in the model
5. the PV = "Short", the VM name = EVS Preferred Name, VM definition = EVS preferred defnition. 

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

u1.1 No matching Value Meaning based on the concept code is found - Create New Value Meaning


u1.2 No concept is associated with the Value Meaning (uml attribute) in the model.  Create Value Meaning without Concept code. See that use case for details.  Value Meaning Long Name = attribute name, Value = attribute name, value Meaning preferred definition = attribute name.

u1.3 Matching VM is found based on the concept code, but the name of the VM is not the same as the name of the PV in teh the model.  Do nothing.  The PV in teh the model is an arbitrary token for storing a representation of the concept in a database.  The concept name and hte the PV name do not have to match.

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.

Related GForge Tracker in Semantic Integration Tools Project

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

1. There are 2 concepts in EVS and caDSR, both have concept name "Short".
C25249:Short
C73939:Short
User has a model 1 with one LVD, one of the PV has name "Short", mapped to C25249:Short.
UML Loader should create new Local Value domian (LVD)
If no Value Meaning exists mapped to C25249, a new VM is created. The new VM long name is the EVS preferred Name, its definition is the EVS preferred definition.  The VM is associated with the PV "Short" in the new Value Domain.


2. Create model 2 with one LVD, one of the PV has name "Short", mapped to C73939:Short.
UML loader shoudl create a new LVD if not LVD exists with one PV mapped Value = "Short" mapped to concept C73939.
If no Value Meaning exists mapped to C73939, new VM should be created and used in the new local value domain.  The VM name = EVS preferred name, concept =C73939, definition = EVS preferrred Definition.