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.0- 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 - concepts exists in caDSR

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 matching VM
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

- No matching Value Meaning based on the concept code is found - Create New Value Meaning - See Init1dbw10.u1.1 
- No concept is associated with the Value Meaning (uml attribute) in the model.  Create Value Meaning without Concept code. See use case Init1dbw10.u1.2 for details. 
- 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 the model.  Do nothing.  The PV in the model is an arbitrary token for storing a representation of the concept in a database.  The concept name and the PV name do not have to match.
- More than one VM is found that is based on the concept code. See Init1dbw10.u1.3

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.

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.1

Brief Description

No existing matching Value Meaning object is found in caDSR.

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. No matching Value Meaning is found to exist for the concept associated with a permissible value (uml attribute in a LVD sterotyped class).

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

New Value Meaning is created based on the concept code and associated 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 but does not find one
4. UML Loader creates a new Value Meaning object in caDSR based on the concept code
 Value Meaning long name = EVS preferred name
Value Meanign preferred name = Value Meaning public id and versioon
Value meaning preferred definition = EVS preferrred definition
5. UML Loader associated the value meaning with the permissible value in the newly created Value domain 

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

u1.1.1 - no concept code is found in caDSR

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

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.2

Brief Description

Create a Value Meaning that is not associated with a Concept code

Actor(s) for this particular use case

UML Loader

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

No concept is associated with the attribute

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

Value Meaning without a concept is associated to the attribute

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. Loader detects that there is no concept associated with the attribute
2. Loader searches and finds no Value Meanings with a long name that matches the attribute name
3.  Loader creates a new VM based on the attribute name.  Value Meaning Long Name = attribute name, Permissible Value = attribute name, Value Meaning preferred definition = attribute name.

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

One VM with a matching long name is found. Create VM based on exisitng VM.
u1.6 More than one VM with a matching long name is found.

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 value meaning is created or resused that is = to the attribute name, the attribute is used to create a permissible value set where the value and value and value meaning are equal

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

Init1dbw10.u1.4

Brief Description

More than one matching Value Meaning object is found in caDSR based on the concept code associated with the attribute.

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 found.
5. UML loader associates the value meaning with the permissible value in the newly created Value domain

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

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

Init1dbw10.u1.6

Brief Description

Create a Value Meaning from an existing VM that is not associated with a concept code - more than one matching VM is found based on the VM long name

Actor(s) for this particular use case

UML Loader

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

No concept is associated with the attribute, more than one VM is found in caDSR where the long name and the attribute name match - and no concept is associated with the concept.  The test for a match is case insensitive.

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

Value Meaning without a concept is associated to the first matching VM where the attribute name and VM long name match, the public id of the matching VM is listed in teh log report with a message that more than one matching VM existed.

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. Loader detects that there is more than one VM where long name matches attribute name (case insensitive)
2. No concept code is associated with the VM
3. Loader associates the VM with attribute to create a PV
4. Message is printed in the log that more than one matching VM was found, the public id and version of the VM that was reused listed

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 value meaning is resused that is = to the attribute name, the attribute is used to create a permissible value set where the permissible value and value and value meaning are equal to the attribute name