Skip to Content

Changes for page 10 Constraints

Last modified by Artur on 2025/09/10 11:19
From version 3.1
edited by Helena
on 2025/05/22 10:34
Change comment: There is no comment for this version
To version 6.3
edited by Helena
on 2025/05/22 12:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -= {{id name="_Toc371061"/}}10 Constraints =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == {{id name="_Toc371062"/}}10.1 Scope ==
4 4  
... ... @@ -16,6 +16,8 @@
16 16  
17 17  === {{id name="_Toc371064"/}}10.2.1 Class Diagram of Constrainable Artefacts - Inheritance ===
18 18  
21 +[[image:1747904390682-586.png]]
22 +
19 19  **Figure 37: Inheritance class diagram of constrainable and provisioning artefacts**
20 20  
21 21  === {{id name="_Toc371065"/}}10.2.2 Explanation of the Diagram ===
... ... @@ -40,6 +40,8 @@
40 40  
41 41  === {{id name="_Toc371067"/}}10.3.1 Relationship Class Diagram – high level view ===
42 42  
47 +[[image:1747904434659-835.png]]
48 +
43 43  **Figure 38: Relationship class diagram showing constraint metadata**
44 44  
45 45  === {{id name="_Toc371068"/}}10.3.2 Explanation of the Diagram ===
... ... @@ -59,8 +59,12 @@
59 59  
60 60  === {{id name="_Toc371069"/}}10.3.3 Relationship Class Diagram – Detail ===
61 61  
68 +[[image:1747904480223-768.png]]
69 +
62 62  **Figure 39: Constraints - Key Set Constraints**
63 63  
72 +[[image:1747904523939-355.png]]
73 +
64 64  **Figure 40: Constraints - Cube Region and Metadata Target Region Constraints**
65 65  
66 66  ==== 10.3.3.1 Explanation of the Diagram ====
... ... @@ -69,10 +69,7 @@
69 69  
70 70  A //Constraint// has a choice of two ways of specifying value sub sets:
71 71  
72 -1. As a set of keys that can be present in the DataSet (DataKeySet) or MetadataSet
73 -
74 -(MetadataKeySet). Each DataKey or MetadataKey specifies a number of ComponentValues each of which reference a //Component// (e.g. Dimension, TargetObject). Each ComponentValue is a value that may be present for a //Component// of a structure when contained in a DataSet or MetadataSet. The MetadataKeySet must also identify the MetadataTarget as there can be many of each of these in a MetadataStructureDefinition. For the DataKeySet the equivalent identification is not necessary as there is only one DimensionDescriptor and one AttributeDescriptor.
75 -
82 +1. As a set of keys that can be present in the DataSet (DataKeySet) or MetadataSet (MetadataKeySet). Each DataKey or MetadataKey specifies a number of ComponentValues each of which reference a //Component// (e.g. Dimension, TargetObject). Each ComponentValue is a value that may be present for a //Component// of a structure when contained in a DataSet or MetadataSet. The MetadataKeySet must also identify the MetadataTarget as there can be many of each of these in a MetadataStructureDefinition. For the DataKeySet the equivalent identification is not necessary as there is only one DimensionDescriptor and one AttributeDescriptor.
76 76  1. As a set of CubeRegions or MetadataTaregetRegions each of which defines a “slice” of the total structure (MemberSelection) in terms of one or more MemberValues that may be present for a //Component// of a structure when contained in a //DataSet// or MetadataSet.
77 77  
78 78  The difference between (1) and (2) above is that in (1) a complete key is defined whereas in (2) above the “slice” defines a list of possible values for each of the// Component//s but does not specify specific key combinations. In addition, in (1) the association between //Component// and DataKeyValue or MetadataKeyValue is constrained to the components that comprise the key or identifier, whereas in (2) it can contain other component types (such as attributes). The value in ComponentValue.value and MemberValue.value must be consistent with the //Representation// declared for the //Component// in the DataStructureDefinition or MetadataStructureDefinition. Note that in all cases the “operator” on the value is deemed to be “equals”. Furthermore, it is possible in a MemberValue to specify that child values (e.g. child codes) are included in the constraint by means of the cascadeValues attribute.
1747904390682-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +16.9 KB
Content
1747904434659-835.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +37.4 KB
Content
1747904480223-768.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +41.6 KB
Content
1747904523939-355.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +43.6 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +11