Init1dbw10.u1.0 - Load Value Meaning
Use Case Number |
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 |
UML Model serialized in XMI containing a local value domain with enumerations - concepts exists in caDSR |
Post condition |
a new value domain is created or an existing value domain is reused |
Steps to take |
1. Using the UML attribute mapped concept code, search caDSR for matching VM |
Alternate Flow |
u1.1 No matching Value Meaning based on the concept code is found - Create New Value Meaning |
Priority |
High |
Associated Links |
Related GForge Tracker in Semantic Integration Tools Project |
Fit criterion/Acceptance Criterion |
|
Init1dbw10.u1.1 - Create New Value Meaning
Use Case Number |
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 |
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 |
New Value Meaning is created based on the concept code and associated with the PV for the new value domain. |
Steps to take |
1. UML Loader searches for a concept matching the mapped concept code |
Alternate Flow |
u1.1.1 - no concept code is found in caDSR |
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Init1dbw10.u1.2 - Create Value Meaning without Concept code
Use Case Number |
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 |
No concept is associated with the attribute |
Post condition |
Value Meaning without a concept is associated to the attribute |
Steps to take |
1. Loader detects that there is no concept associated with the attribute |
Alternate Flow |
One VM with a matching long name is found. Create VM based on exisitng VM. |
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
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 |
Init1dbw10.u1.4 - More than one VM is found based on the matching concept code
Use Case Number |
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 |
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 |
Value Meaning is reused with the PV for the new value domain. |
Steps to take |
1. UML Loader searches for a concept matching the mapped concept code |
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 |
|
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Init1dbw10.u1.6 - More than one VM is found with matching long name
Use Case Number |
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 |
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 |
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 |
1. Loader detects that there is more than one VM where long name matches attribute name (case insensitive) |
Alternate Flow |
|
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
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 |