Message-ID: <2135401799.38383.1425386994590.JavaMail.confluence@ece-vmapps> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_38382_792704020.1425386994589" ------=_Part_38382_792704020.1425386994589 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
One suggestion at METIS 2013 was to include relationships in the= glossary.
One could use rules like: always include inheritance and subtypes, consi= der including components and aggregates, can include other associations.
Alternatvely one could have always mention the nearest neighbours o= f any information object in the explanatory text.
Description of the relationships should include the text and notation of= the UML diagrams and these should be maintained in a consistent fashion.= p>
If the UML text on the association doesn't work in the glossary, then th= e UML text should be changed.
Mandatory relationship to= unit?!
|10||Representation (to be renamed to Presentation)<= /td>||No attributes|
Need to make it a subtype= of Business Service
Review relationships a= nd attributes
(there are no attributes)
Need to make Disseminatio= n Service a subtype
Review relationships and attributes
review proposed relationships a= nd attributes
add relationship to logical record
|13||Unit||review relationships and att= ributes following removal of subtypes|
|13||Population||review relationships and att= ributes following removal of subtypes|
|28||Business Process &n= bsp;and = Process Step Instance||relationship between these objects= ?|
|30||Question and *Mu= ltiple Question Item (to be removed)||Pending outcome of 35, these will = become subtypes of a new abstract question object|
|36||Exchange Channel||Following removal of subtypes, nee= d to implement relationship changes|
|#8||Level||Add new diagrams to include Level = in the next release|
Classification (Classification = Series),
Classification Scheme(Statistical Classification)
|Revise relationships according to = proposal|
Index (Classification Index)
Index Entry (Classification Index Entry)
|Ensure only have relationships to = Classification objects and not to nodesets.|
|Data Point||Mandatory relationship to unit but data point is= abstract?|
|Enumerate Value Domain||Relationship to Code List described as "is&= quot; - should be something like "takes value from"|
Ins= tance Variable
|Currently all reference a concept, population. D= o they all need these relationships?|
|Rule||Text says that there should be a self referentia= l relationship (nested rules) but there is no relationship|
Attributes Table (did not have permission to add it in the Attributes Pa= ge: please move)