Knowledge Discovery Metamodel Avatar
  1. OMG Specification

Knowledge Discovery Metamodel — Closed Issues

  • Acronym: KDM
  • Issues Count: 160
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
KDM-160 Section: 15.10 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-159 Section: 12.11 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-154 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-155 Section: 12.8 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-158 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-156 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-157 Section: 10 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-153 Section: 13.6 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-150 StorableElement should be able to own actions KDM 1.0b1 KDM 1.0 Resolved closed
KDM-148 Remove prototype unit KDM 1.0b1 KDM 1.0 Resolved closed
KDM-151 Section: 10 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-152 Section: 11 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-149 Rename CodeAssembly to Package KDM 1.0b1 KDM 1.0 Resolved closed
KDM-69 Section: 19.11 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-68 Unnecessary abstract classes for relationships in Platform package KDM 1.0b1 KDM 1.0 Resolved closed
KDM-66 Section: 15.3 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-70 Section: 21.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-64 Section: 13.3 page 76 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-62 Section: 13.7 page 85 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-67 Section: 14 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-63 Section: 13.7 page 85 Creates relationship KDM 1.0b1 KDM 1.0 Resolved closed
KDM-65 Section: 12.17 page 65 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-71 Section: 22.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-61 Section: 13 pages 75 - 95 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-60 Section: 12.13 page 59 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-56 Section: 12.19 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-54 Section: 12.14 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-57 Section: 9.7 page 23 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-59 Section: 10.5 page 34 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-53 Section: 12.14 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-58 Section: 9.7 page 23 (TaggedValue) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-55 Section: 11.4.1 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-51 Section: 12.24 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-52 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-46 Section: 9.7 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-47 Section: 12.17 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-49 Section: 12.9 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-50 Section: 12.23 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-48 Section: 12,13 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-44 Section: 19 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-43 Section: 9.6.1 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-45 Section: 19.6 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-42 Section: 12.19-12.20 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-41 Section: 12.21 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-38 Section: 12.18 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-36 Section: 12.12-12.17 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-40 Section: 12.18 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-37 Section: 12.16 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-39 Section: 9.6.1 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-35 Section: 12.12 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-33 Section: 12.11 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-34 Section: 12.12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-32 Section: 12.10 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-31 Section: 12.10 (issue # 3) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-30 Section: 12.10 (issue # 2) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-27 Section: 12.6 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-29 Section: 12.10 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-28 Section: 12.8 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-26 Section: 12.8 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-25 Section: 12.7 (iisue # 2) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-23 Section: 12.6.6 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-24 Section: 12.7 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-22 Section: 12.6.1 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-21 Section: 12.5 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-20 Section: 9.7.1 (issue # 2) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-17 Section: 9.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-19 Section: 9.7.1 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-15 Section: 11.3 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-18 Section: 9.5 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-16 Section: 11.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-14 Section: 10.5 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-13 Section: 10.3, 10.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-146 Add optional kind attribute to StorableUnit VariableKind KDM 1.0b1 KDM 1.0 Resolved closed
KDM-144 Allow ActionElement to own storable elements KDM 1.0b1 KDM 1.0 Resolved closed
KDM-145 Make AggregatedRelationship a subclass of KDMRelationship KDM 1.0b1 KDM 1.0 Resolved closed
KDM-143 ActionElements can not be added directly to CodeModel KDM 1.0b1 KDM 1.0 Resolved closed
KDM-147 add type attribute to CallableUnit KDM 1.0b1 KDM 1.0 Resolved closed
KDM-142 Change name of attribute in Annotation from "note" to "text" to reflect sem KDM 1.0b1 KDM 1.0 Resolved closed
KDM-141 Make ValueElement a subclass of StorableElement KDM 1.0b1 KDM 1.0 Resolved closed
KDM-140 Missing attribute length for all StorableElements KDM 1.0b1 KDM 1.0 Resolved closed
KDM-133 Wrong text for Calls class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-135 Wrong text for DataRelation class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-136 Wrong text for PrototypeRelation class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-137 Remove several remaining backward navigable links to groups KDM 1.0b1 KDM 1.0 Resolved closed
KDM-139 Allow multiple SourceRef elements for a given Code element KDM 1.0b1 KDM 1.0 Resolved closed
KDM-138 Lack of fidelity for advance flow analysis KDM 1.0b1 KDM 1.0 Resolved closed
KDM-134 Wrong text for UsesCallable class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-132 Wrong text for CallableRelations class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-126 Wrong text for EntryFlow class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-130 Wrong text for ControlFlow class (04) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-128 Wrong text for ControlFlow class (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-131 Missing specification detail for ControlFlow class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-129 Wrong text for ControlFlow class (03) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-123 Wrong text for 12.10.2 TemplateParameter Class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-125 Wrong text for ControlFlow class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-124 Wrong text for DerivedTypeElement class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-127 Wrong text for ControlFlow class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-119 Section: 21.3 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-118 Section: 17 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-120 Section: 9 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-114 Section: 12.13 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-122 Need additional attribute for SourceFile element to specify encoding KDM 1.0b1 KDM 1.0 Resolved closed
KDM-121 Insufficient specification of KDMAggregatedRelationship class KDM 1.0b1 KDM 1.0 Resolved closed
KDM-115 Section: 12.17 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-116 Section: 13 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-113 Section: 12.9 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-117 Section: 13 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-111 Section: 12.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-108 Section: 10.4 page 32 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-109 Section: 9 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-106 Section: 10.3 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-110 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-107 Section: 10.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-112 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-103 Section 93. KDM 1.0b1 KDM 1.0 Resolved closed
KDM-104 Section: 9.6.1 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-105 Section: 9 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-101 Section: 19 pages 149 - 169 (07) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-102 Section: 19 pages 149 - 169 (09) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-95 Section: 19 pages 149 - 169 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-98 Section: 19 pages 149 - 169 (04) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-100 Section: 19 pages 149 - 169 (06) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-96 Section: 19 pages 149 - 169 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-97 Section: 19 pages 149 - 169 (03) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-93 Section: 19 pages 149 - 169 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-94 Section: 19 pages 149 - 169 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-92 Section: 19 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-99 Section: 19 pages 149 - 169 (05) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-91 Section: 20 pages 171 - 183 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-90 Section: 20 pages 171 - 183 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-88 Section: 18 pages 137 - 148 (09) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-86 Section: 18 pages 137 - 148 (07) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-89 Section: 18 pages 137 - 148 (10) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-85 Section: 18 pages 137 - 148 (06) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-87 Section: 18 pages 137 - 148 (08) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-83 Section: 18 pages 137 - 148 (04) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-84 Section: 18 pages 137 - 148 (05) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-81 Section: 18 pages 137 - 148 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-80 Section: 18 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-82 Section: 18 pages 137 - 148 (03) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-78 Section: 13.4 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-76 Section: 12, page 41-74 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-73 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-79 Section: 17 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-74 Section: 12 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-75 Section: 12, page 41-74 KDM 1.0b1 KDM 1.0 Resolved closed
KDM-77 Section: 12, page 41-74 (04) KDM 1.0b1 KDM 1.0 Resolved closed
KDM-72 Section: 12.18 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-290 Section: 17 pages 131 - 136 (02) KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-291 Section: 19 pages 149 - 169 (10) KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-294 Section: 16 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-293 Section: 18 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-295 Section: 15 (Data package illustrating extraction of xml file elements ) KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-292 Section: 17 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-298 Section: 22 KDM 1.0b1 KDM 1.0 Closed; No Change closed
KDM14-296 Section: 15 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-297 Section: 15 (extraction of record database elements ) KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-300 Section: 21 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-301 Section: 12 KDM 1.0b1 KDM 1.0 Resolved closed
KDM14-299 Section: 19 (03) KDM 1.0b1 KDM 1.0 Resolved closed

Issues Descriptions

Section: 15.10

  • Key: KDM-160
  • Legacy Issue Number: 10466
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Collision of the role name "attribute" in Data package This issue has been raised by Alain Picard from Benchmark Consulting. The role name "attribute" of the association between class XMLComplexType and SimpleTypeElement (from Code) (in the Data package) collides with the role name of the association between class Element and class Attribute. Recommendation is to rename the role in the Data package to "xmlAttribute"

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Sat, 7 Mar 2015 21:54 GMT

Section: 12.11 (02)

  • Key: KDM-159
  • Legacy Issue Number: 9984
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Element TemplateInstance is redundant, as TemplateUnit can contain only a single class or method. The instance of the template therefore consists of that class or method (properly instanciated), and no additinal housekeeping is required. The instance can be the endpoint for the "Instantiates" relation. Suggestion - remove this element to simplify the metamodel, and correct model for instantiates relation to go from CodeResource to TemplateUnit at Figure 12.9. This also elimintaes the need to distinguish between InstanceOf and Instanciates relationships. Relationship InstanceOf can be elimitated to further simplify the metamodel

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    duplicate of issue 9983

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Section: 12

  • Key: KDM-154
  • Legacy Issue Number: 10793
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    The clear separation of KDM into Infrastructure, Program Elements, Resources and Abstractions layers shows that the current design is overly complex. Currently each package defines own “abstractions” capabilities (an arbitrary container and group). I suggest concentrating all containers and groups in the Abstractions layer. In the long run, this makes the whole KDM architecture more consistent.

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.8

  • Key: KDM-155
  • Legacy Issue Number: 10794
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Current KDM has duplication between prototype relations (UsesPrototype and PrototypedBy) and interface relations (Implements, ImplementationOf, and CompliesTo). I suggest removing the prototype relations and use Interface relations.

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM-158
  • Legacy Issue Number: 10797
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Currently the “encapsulated relationship” pattern requires that relationship are owned by the element which is the origin of the relationship. There is a constraint for that. However, the multiplicity of the owned relationship in the xxxModel diagrams is 0..1 (at the owner side) It should be tightened to 1

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM-156
  • Legacy Issue Number: 10795
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Diagram ExceptionFlow should be moved to Code package in order to comply to the encapsulated relations meta-model pattern in KDM. This is a Code relations, since the from-endpoint is a code element

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10

  • Key: KDM-157
  • Legacy Issue Number: 10796
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Corrections to the text of the KDM package section, clarifying semantics

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13.6

  • Key: KDM-153
  • Legacy Issue Number: 10792
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Some corrections are required to the CallableRelations to align with microKDM to differentiate between calls to static procedures and methods, regular methods, calls to procedures via pointers and calls to virtual methods. micro KDM provides operations to achieve this. More differentiation in the CallableRelations is required. “Invokes” relation conflicts with the ISO usage of the term. KDM uses “Calls” instead “Invokes’, leaving both will be confusing. “Invokes” can be changed into “Addresses” which can be generalized to work with a common parent of ControlElements and StorableElements

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

StorableElement should be able to own actions

  • Key: KDM-150
  • Legacy Issue Number: 10730
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    StorableElement should be able to own actions. This is required for initialization purposes, according to the Datatype reform. Currently the ownership is restricted to Datatype. Constraint should be added, restricting ownership to Datatype and Action.

  • Reported: KDM 1.0b1 — Tue, 13 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Remove prototype unit

  • Key: KDM-148
  • Legacy Issue Number: 10715
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Remove prototype unit, since it is not an independent model element, but either a signature or callable unit or a storable unit with external is true. If later it is substituted with a real definition, the calls or reads/writes relations will go to the internal definition, and UsesPrototype relationship will go to the external one. The internal definition is related to the external one by PrototypedBy relationship. Usually the external definition lives in a SahredUnit. This should be clarified in the spec. Note, there exists an issue about example ralated to this.

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10

  • Key: KDM-151
  • Legacy Issue Number: 10767
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Make extensibility mechanism more general by changing the from-endpoint of the extended relation to the most generic element in the model (currently it is at the extended element).

  • Reported: KDM 1.0b1 — Thu, 15 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 11

  • Key: KDM-152
  • Legacy Issue Number: 10791
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Inventory model as part of the Source package instead of Build There is one flaw in the current architecture of KDM: SourceRegion elements are part of the L0 compliance point, however the SourceFiles are defined in Build package, which is in L1. It would be much better to consolidate SourceFile elements and alike into a special “Inventory model” (the list of elements representing all artifacts as first class KDM citizens), right in the L0, for example as part of the Source package. In fact, all implementers so far are doing just that: they are aiming at supporting L0 with “limited support for Build”. Everybody seems to have an inventory model, and it makes perfect sense to have it right in the L0. The Build package makes sense on its own right as the place where we represent the “Engineering view” of the software system, i.e. the transformations between the artifacts (for example, files A.c, B.c, and C.c as well as the library GGG.lib are compiled into the executable XYZ.exe, where file A.c is provided by supplier S1, and the GGG.lib is provided by supplier S1, and the transformation requires tool T1 and is described in file “makefile”).

  • Reported: KDM 1.0b1 — Wed, 28 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Rename CodeAssembly to Package

  • Key: KDM-149
  • Legacy Issue Number: 10716
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Rename CodeAssembly to Package and use it to represent logical containers for code elements

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19.11

  • Key: KDM-69
  • Legacy Issue Number: 10137
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing description of the class UsesResource in section 19.11 (correspondign to Figure 19.9

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Unnecessary abstract classes for relationships in Platform package

  • Key: KDM-68
  • Legacy Issue Number: 10136
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Unnecessary abstract classes for relationships in Platform package. Platform package defines 3 unnecessary abstract classes for KDM relationships: TechnologyRelationship, ExternalRelationship and ResourceRelationship. Originally, these classes were introduced as potential extension hotspots. However they are required to be abstract, so they became unnecessary. Recommendation: to remove these unnecessary classes to simplity the KDM metamodel. This does not affect KDM XMI. Usages of these relationships should be promoted to PlatformRelationship class.

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 15.3

  • Key: KDM-66
  • Legacy Issue Number: 10125
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    abstract element ProgramElement should be subclassed by DataElement and CodeElement (rather than only CodeResource), since it is necessary to allow ActionElement to be included into definition of ConceptualGroup

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 21.4

  • Key: KDM-70
  • Legacy Issue Number: 10148
  • Status: closed  
  • Source: Princeton Blue, Inc. ( Vitaly Khusidman)
  • Summary:

    Inability to create relationships between ConceptualElements. This issue manifests itself in a context of transferring information from a code mining tool to a rules management (analysis) tool. Mining tool has information on mapping (e.g. based on computational dependency) between ConceptualElements (i.e. TermUnits and FactUnits). This is vital information for an analyst working with rules management tool that helps to determine whether a specific TermUnit or FactUnit has business significance and to define the correspondent Term or Fact in the Business Rules Model. However, KDM does not provide means to define a relationship between ConceptualElements.

  • Reported: KDM 1.0b1 — Thu, 31 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13.3 page 76

  • Key: KDM-64
  • Legacy Issue Number: 10122
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Unnecessary abstract classes for relationships in Action package. Action package defines 4 unnecessary asbstract relationships: CallableRelationship, MacroRelationship, ImportRelationship and DataRelationship. Originally they were introduced as potential extension hotspots, but later they were made abstract because of the overall KDM pattern and CMOF, so they are now completely redundant. Removing them will simplify KDM. This does not affect existing KDM XMI. Recommendation to promote CallableRelationship and DataRelationship to ActionRelationship and other two - to CodeRelationship (with the possibility for their from-endpoint to own them in order to achieve better encapsulation of the model).

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13.7 page 85

  • Key: KDM-62
  • Legacy Issue Number: 10120
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Destroys relationship is not needed since it is simply a call to a destructor method. It should be removed from Figure 13.5

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 14

  • Key: KDM-67
  • Legacy Issue Number: 10132
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the Build package illustrating extraction of various elements and their representation as KDM XMI instances

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13.7 page 85 Creates relationship

  • Key: KDM-63
  • Legacy Issue Number: 10121
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Creates relationship is is a relationship to a TypeElement (ClassUnit), rather than to a variable of that class. This is also different from the call to a particular constructor of that class. Example (C++): A x=new A(1); Pseudo KDM (ClassUnit name="A" id=id0 MethodUnit name="A" id=id3)) (IntegerUnit name="1" kind=constant id=id1) (NamedClassUnit name="x" kind=variable id=id4) (HasType from=id4 to=id0) (ActionElement id=id2) (Creates from=id2 to=id0) (Reads from=id2 to=id1) (Calls from=id2 t=id3) (Writes from=id2 to=id4)

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.17 page 65

  • Key: KDM-65
  • Legacy Issue Number: 10124
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need better support for virtual methods. Recommendation: special call action and a special MethodKind

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 22.4

  • Key: KDM-71
  • Legacy Issue Number: 10149
  • Status: closed  
  • Source: Princeton Blue, Inc. ( Vitaly Khusidman)
  • Summary:

    Inability to create relationships between BehaviorElements and ConceptualElements. This issue manifests itself in a context of transferring information from a code mining tool to a rules management (analysis) tool. Mining tool has information on mapping from BehaviorElement (e.g. RuleUnit) to ConceptualElements (i.e. TermUnits and FactUnits). This is vital information for an analyst working with rules management tool that helps to determine whether a specific RuleUnit has business significance and to define the correspondent Rule in the Business Rules Model. However, KDM does not provide simple means to define a relationship between BehaviorElements and ConceptualElements.

  • Reported: KDM 1.0b1 — Thu, 31 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13 pages 75 - 95

  • Key: KDM-61
  • Legacy Issue Number: 10119
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Merge UsesType, UsesCallable and UsesData into a single more generic relationship Uses. This relationship is sufficient for tracking dependencies between components, without making fine distinction between the exact semantics of the usage, which can be further derived from the kind of the entity at the to-endpoint. There is not need to duplicate this information in the kind of the relationship

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.13 page 59

  • Key: KDM-60
  • Legacy Issue Number: 10118
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need to add void type to PredefinedTypeElement. This is needed to represent C/C++ casting to void*, and also will make signature more uniform

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.19

  • Key: KDM-56
  • Legacy Issue Number: 10111
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Rename Interface class to InterfaceUnit. Section 12.19, page 67 defines class Interface. However the rest of the specification uses suffix xxxUnit for concrete model elements. Suggestion to rename Interface to InterfaceUnit

  • Reported: KDM 1.0b1 — Thu, 17 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.14

  • Key: KDM-54
  • Legacy Issue Number: 10109
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need special attribute to RefinementUnit to represent the actual refinement. Currently there is no special special modeling element for representing the actual refinement of a data type (for example, the actual range in Ada) as it may be declared in the existing source code artifact. This gap has to be mitigated, for example, by introducing a special attribute for representing the refinement in RefinementUnit. This information is required in several queries against KDM models and is required for transformations of existing systems.

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.7 page 23

  • Key: KDM-57
  • Legacy Issue Number: 10115
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Allow multiple stereotypes for ModelElement Currently Figure 9.5 allow not more than one stereotype to be associated with each ModelElement. It is more convenient to have multiple stereotypes, so that extension can be split. This will avoid duplication in defining extensions. To resolve, corresponding multiplicty has to be changed from 0..1 to 0..*

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10.5 page 34

  • Key: KDM-59
  • Legacy Issue Number: 10117
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Typo in the attribute author of Audit class Spelled "duthor" instead of "author"

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.14

  • Key: KDM-53
  • Legacy Issue Number: 10108
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need special attribute to ArrayUnit to represent the size of the array. Currently there is no special special modeling element for representing size of the array as it may be declared in the existing source code artifact. This gap has to be mitigated, for example, by introducing a special attribute for representing the size of the array. This information is required in several queries against KDM models and is required for transformations of existing systems.

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.7 page 23 (TaggedValue)

  • Key: KDM-58
  • Legacy Issue Number: 10116
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Allow TaggedValue that can refer to other KDM ModelElements Currently Figure 9.5 allow only TaggedValues with a String value. For some extensions it is convenient to add TaggedValues that contain a reference to other ModelElements. Resolution suggestion: introduce a supertype with two sublclasses, one - current TaggedValue with String value, another one, for example TaggedRef, with an association to ModelElement

  • Reported: KDM 1.0b1 — Tue, 22 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 11.4.1

  • Key: KDM-55
  • Legacy Issue Number: 10110
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing description of additional properties for SourceRef in SourceRegion diagram Section 11.4.1. SourceRegion class Diagram misses description of additional properties that are defined for class SourceRef (association from SourceRef to SourceRegions).

  • Reported: KDM 1.0b1 — Thu, 17 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.24

  • Key: KDM-51
  • Legacy Issue Number: 10106
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of Visibility relationship in section 12.24

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM-52
  • Legacy Issue Number: 10107
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need special modeling element to represent initialization of data items. Currently there is no special special modeling element for initialization. This can be represented by ActionElements and Initializaes relationship. However, this solution proves to be not particularly readable and rather verbose. Introducing a special element for initialization will improve readability of KDM XMI instances.

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.7

  • Key: KDM-46
  • Legacy Issue Number: 10100
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Move Extension and Annaotation diagrams from Core to Kdm package. Management of KDM packages can be optimized, if the Extension and Annotations diagrams are moved from the Core package into the Kdm package. This way, the Core package will contain abstract classes that define the meta-level facilties of KDM, and determine the meta-level API to KDM instances. The Kdm package, on the other hand, will contain concrete classes that are part of each KDM instance.

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.17

  • Key: KDM-47
  • Legacy Issue Number: 10102
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Definition of ClassUnit should be flattened. Definition of ClassUnit (Figure 12.15) should be flattened, so that ClassUnit contains a single association to CodeResource. This will make Classunit more generic, for example, allow to use PrototypeUnit as a contained element, and will allow to make contents of ClassUnit ordered

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.9

  • Key: KDM-49
  • Legacy Issue Number: 10104
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of MacroUnit and its usages in section 12.9

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.23

  • Key: KDM-50
  • Legacy Issue Number: 10105
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of CommentUnit and its usages in section 12.23

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12,13

  • Key: KDM-48
  • Legacy Issue Number: 10103
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Improve encapsulation of KDM models by associating KDM relationships with the from-endpoint. Encapsulation of KDM models can be improved by placing most KDM relationships into the elements that are the from-endpoints of these relationships, instead of associating these relationships with the whole model. Particularly, ActionRelationships should be owned by ActionElements; CodeRelationships should be owned by CallableElements. Currently, only FlowRelationships follow this principle (they are already owned by CallableElements). This will significantly reduce the number of KDM relationships that are contained directly by the each KDM model. The proposed revision will dramatically improve the readability of KDM instances in XMI (otherwise, each model is "flooded" by a flat set of KDM relationships).

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 (02)

  • Key: KDM-44
  • Legacy Issue Number: 9996
  • Status: closed  
  • Source: International Business Machines ( Howard Hess)
  • Summary:

    Need to relate platform activations and bindings to UI triggers

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.6.1

  • Key: KDM-43
  • Legacy Issue Number: 9994
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Representation of data types and storable elements in KDM (aka "compressed data type representation") has a disadvantage: it is difficult to implement a query that lists all variables in a Code Model. KDM does not explicitly represent varibles. Instead, it represented various typeUnits with a additional kind attribute (of InstanceKind data type) that distinguishes for example, global variable, local variables, fields of a record, members of a class, formal parameters of a procedure, etc. In order to get the list of variables, one needs to iterate over all subtypes of a TypeElement (quite a few), and check the kind attribute. Suggestion: to "uncompress" the representation a little, by introducing an explicit StorableUnit element with attribute type that provides a reference to the corresponding type. This will still satisfy most of the goals of the "compressed representation", for example, low cost of representing complex derived types, and not tracking usages to predefined types through KDM relations (only relations to NamedTypes). This suggestion originates from an external reviewer, who is implementing KDM.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19.6

  • Key: KDM-45
  • Legacy Issue Number: 9998
  • Status: closed  
  • Source: International Business Machines ( Neta Aizenbud-Reshef)
  • Summary:

    DataResource is the same as DataManager, Figure 19.4

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.19-12.20

  • Key: KDM-42
  • Legacy Issue Number: 9993
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of Interface and corresponding relations as KDM instance

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.21

  • Key: KDM-41
  • Legacy Issue Number: 9992
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of HasType relation as KDM instance

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.18

  • Key: KDM-38
  • Legacy Issue Number: 9989
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Signature should have an (optional) association to the returned type, instead of ownership, since returned types are defiend elsewhere, and signature does not define a special name for it.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.12-12.17

  • Key: KDM-36
  • Legacy Issue Number: 9987
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing examples of data types and their representations as KDM instances

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.18

  • Key: KDM-40
  • Legacy Issue Number: 9991
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of CallableElements and their Signatures as KDM instance, illustrating corresponding KDM relations.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.16

  • Key: KDM-37
  • Legacy Issue Number: 9988
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    CompositeTypeElement should own an ordered list of fields.

    {ordered}

    is now missing in Figure 12.14

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.6.1

  • Key: KDM-39
  • Legacy Issue Number: 9990
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Move InstanceKind enumeration data type from Core package to Code package, since it is only used in Code package. This will simplify development of class factories per each package.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.12 (02)

  • Key: KDM-35
  • Legacy Issue Number: 9986
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need new subclass of DerivedTypeElement to represent "synonym types", for example, in C: typedef int x;

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.11

  • Key: KDM-33
  • Legacy Issue Number: 9983
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Element TemplateInstance is redundant, as TemplateUnit can contain only a single class or method. The instance of the template therefore consists of that class or method (properly instanciated), and no additinal housekeeping is required. The instance can be the endpoint for the "Instantiates" relation. Suggestion - remove this element to simplify the metamodel, and correct model for instantiates relation to go from CodeResource to TemplateUnit at Figure 12.9. This also elimintaes the need to distinguish between InstanceOf and Instanciates relationships. Relationship InstanceOf can be elimitated to further simplify the metamodel.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.12

  • Key: KDM-34
  • Legacy Issue Number: 9985
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing general description of type representation in KDM, embracing sections 12.12-12.22

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.10

  • Key: KDM-32
  • Legacy Issue Number: 9982
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of a TemplateUnit for class and method as KDM instance. Related to Figure 12.8

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.10 (issue # 3)

  • Key: KDM-31
  • Legacy Issue Number: 9981
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    TemplateParameterowned by TemplateUnit should be ordered

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.10 (issue # 2)

  • Key: KDM-30
  • Legacy Issue Number: 9980
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Association templateElement between TemplateUnit and CodeResource at Figure 12.8. is too general. It says 0..*, but TemplateUnit can contain a single class or method.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.6

  • Key: KDM-27
  • Legacy Issue Number: 9977
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing examples of various CallableElements as KDM instances

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.10

  • Key: KDM-29
  • Legacy Issue Number: 9979
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM defines TemplateParameter as a subclass of CodeResource, but it should be a subclass of TypeElement in order to get correct usage relations. Figure 12.8.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.8

  • Key: KDM-28
  • Legacy Issue Number: 9978
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing examples of PrototypeUnit and its usages as KDM instance

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.8

  • Key: KDM-26
  • Legacy Issue Number: 9976
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM defines PrototypeUnit as CodeResource. However it should be moved into the TypeElement hierarch, so that it can be owned by ClassUnits. Figure 12.6

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.7 (iisue # 2)

  • Key: KDM-25
  • Legacy Issue Number: 9975
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM defines Module (and its subclasses) as a subclass of CodeContainer, which does not enforce that semantically all individual code elements are supposed to be owned by some module. Suggestion - change the inheritance hierarchy Figure 12.5 and 12.2

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.6.6

  • Key: KDM-23
  • Legacy Issue Number: 9973
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM defines OperatorUnit as a special subclass of CallableElement, together with CallableUnit, BlockUnit, MethodUnit and ConstructorUnit. There is little value in this element compared to a regular CallableUnit or a MethodUnit. The difference seems more syntactic. Suggestion - to eliminate this element in order to simplify the metamodel.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.7

  • Key: KDM-24
  • Legacy Issue Number: 9974
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM defines Module (and its subclasses) as a subclass of CodeContainer, which means they inherit SourceRef association. However, this element is not defined at this level. It is only applicable to individual elemetns inside the Module.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.6.1

  • Key: KDM-22
  • Legacy Issue Number: 9972
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM text mentions incorrect superclass for CallableUnit, BlockUnit, MethodUnit, (KDM text describes this a CodeElement, while it is in fact CallableElement, as defined in Figure 12.4).

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.5

  • Key: KDM-21
  • Legacy Issue Number: 9971
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM defines unnecessary abstract classes for relations, for example, CodeRelationship, PrototypeRelationship, Interfacerelationship, TypeRelationship, TemplateRelationship (figure 12.3). This is a consistent pattern, repreated at other packages. The intention was to provide additional extension points, however, these relationships are defined as abstract classes, so they cannot be instanciated. They cannot be made concrete either for the reasons of compatibility with EMF. They make the metamodel unnecessary complex without adding any value. They do not affect the KDM instance XMI. The suggestion is to simplify the metamodel by removing these unnecessary relations. This suggestion was also given by ASG representative.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.7.1 (issue # 2)

  • Key: KDM-20
  • Legacy Issue Number: 9970
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM requires a named association from Stereotype to the ModelElement (called extendedElement in Figure 9.5). While useful for certain cross-referencing queries (usage of a given stereotype), this feature makes KDM instance XMI very inflexible and complicated (as information is essentially duplicated). Suggestion to define this as an operation, or remove to be implemented internally to KDM tools, if needed

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.4

  • Key: KDM-17
  • Legacy Issue Number: 9967
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM requires navigabable associations from KDMEntity to KDMRelationship (in the Core KDM these are named outbound and inbound, see Figure 9.2). While useful for certain type of cross-referencing queries (e.g. who is using the given entity), these associations make KDM instance XMI extremely inflexible and hard to modify (as information abut relations is essentially duplicated). It is better to eliminate these associations, and leave only the from and to associations in the KDMRelationship element. The outbound and inbound associations can be changed into operations, or implemented internally by particular KDM tools, if needed.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.7.1

  • Key: KDM-19
  • Legacy Issue Number: 9969
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of KDM Stereotype as KDM instance (with tag definitions, as part of an Extension family).

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 11.3

  • Key: KDM-15
  • Legacy Issue Number: 9965
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of SourceRef element as a KDM instance

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.5

  • Key: KDM-18
  • Legacy Issue Number: 9968
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    KDM requires navigabable associations from KDMEntity to KDMAggregatedRelationship (in the Core KDM these are named inAggregated and outAggregated, see Figure 9.3). While useful for certain type of cross-referencing queries (e.g. who is using the given entity), these associations make KDM instance XMI extremely inflexible and hard to modify (as information abut relations is essentially duplicated). It is better to eliminate these associations, and leave only the from and to associations in the KDMAggregatedRelationship element. The inAggregated and outAggregated associations can be changed into operations, or implemented internally by particular KDM tools, if needed.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 11.4

  • Key: KDM-16
  • Legacy Issue Number: 9966
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of SourceRegion element as a KDM instance. It would be good to illustrate alternative organization with and without the BuildModel for representing files, as well as various overrides for language attribute

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10.5

  • Key: KDM-14
  • Legacy Issue Number: 9912
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of usage of the Audit element

  • Reported: KDM 1.0b1 — Mon, 10 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10.3, 10.4

  • Key: KDM-13
  • Legacy Issue Number: 9911
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example of KDM Framework as KDM Instance

  • Reported: KDM 1.0b1 — Mon, 10 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Add optional kind attribute to StorableUnit VariableKind

  • Key: KDM-146
  • Legacy Issue Number: 10713
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Add optional kind attribute to StorableUnit VariableKind with values

    {global, local, static, unknown}
  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Allow ActionElement to own storable elements

  • Key: KDM-144
  • Legacy Issue Number: 10711
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Allow ActionElement to own storable elements (for example, for temporary variables and values).

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Make AggregatedRelationship a subclass of KDMRelationship

  • Key: KDM-145
  • Legacy Issue Number: 10712
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Make AggregatedRelationship a subclass of KDMRelationship so that they can occur in KDM XMI, add a concept of an AggregatedRelationship Filter (as a set of relationship type names or "all" ) and add a filter attribute to Aggregated relationship

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

ActionElements can not be added directly to CodeModel

  • Key: KDM-143
  • Legacy Issue Number: 10710
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    ActionElements can not be added directly to CodeModel. Currently CodeModel allows ActionElements (for example, to represent scripts), but does not allow Flow relations. Suggestion to disallow free standing ActionElements, and to use BlockUnit instead, because BlockUnit is a CallableElement, and therefore allows FlowRelations. In order to implement, modify owned elements of CodeModel to become Module

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

add type attribute to CallableUnit

  • Key: KDM-147
  • Legacy Issue Number: 10714
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    add type attribute to CallableUnit, to specify Signature to be consistent with ISO Lnaguage Independent datatypes and with StorableElement

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Change name of attribute in Annotation from "note" to "text" to reflect sem

  • Key: KDM-142
  • Legacy Issue Number: 10709
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Change name of attribute in Annotation from "note" to "text" to reflect semantics

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Make ValueElement a subclass of StorableElement

  • Key: KDM-141
  • Legacy Issue Number: 10708
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    ValueElement has to be compatible with StorableElement in order for Reads relationship to work Suggestion: Make ValueElement a subclass of StorableElement. This is a bit of an overspecialization, so we need to add some constraints. Add constraint to ValueElement that it can not have owned elements; it can only be the target of Reads relationship (and not of Addresses, Writes or Initializes). add constraint to Writes, Addresses, Initializes relationships that it can not use ValueElement as target.

  • Reported: KDM 1.0b1 — Mon, 12 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Missing attribute length for all StorableElements

  • Key: KDM-140
  • Legacy Issue Number: 10654
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing attribute length for all StorableElements (as used in the Data item representation examples)

  • Reported: KDM 1.0b1 — Wed, 7 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for Calls class

  • Key: KDM-133
  • Legacy Issue Number: 10462
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.6.1
    Severity: minor
    Nature: clarification

    13.6.1 Calls Class The Calls class is a subtype of CodeRelationship and provides linkages between ActionElement and CallableInterface for the situations when an ActionElement performs a call to the CallableElement.

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for DataRelation class

  • Key: KDM-135
  • Legacy Issue Number: 10464
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.7
    Severity: minor
    Nature: clarification

    13.7 DataRelations Class Diagram The DataRelations class diagram collects together classes and associations of the Action package. They provide basic meta-model constructs to define data specific CRUD like relationships between ActionElement and DataInterface.
    What is a DataInterface and where is it defined?

    This should be StorableElement.

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for PrototypeRelation class

  • Key: KDM-136
  • Legacy Issue Number: 10465
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.8
    Severity: minor
    Nature: clarification

    13.8 PrototypeRelations Class Diagram The PrototypeRelations class diagram defines basic meta-model constructs to model prototype relationships between ActionElement and CodeElement.
    Diagram shows extension of PrototypeRelationship, KDM shows extension of CodeRelationship

    CodeElement should be a PrototypeUnit

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Remove several remaining backward navigable links to groups

  • Key: KDM-137
  • Legacy Issue Number: 10468
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Remove several remaining backward navigable links to groups Several backward navigation links have been left unnoticed in the resolution to issue 10412; and need to be removed. StructureGroup -> CodeResource ResourceDefinition -> CodeResource DeployedSoftwareSystem -> SoftwareSystem DeployedComponent -> CodeAssembly DeployedResource -> ResourceElement DeployedResource -> ResourceInstance DeployedResource -> ResourceProvider "Backward navigability" should be removed

  • Reported: KDM 1.0b1 — Mon, 20 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Allow multiple SourceRef elements for a given Code element

  • Key: KDM-139
  • Legacy Issue Number: 10653
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Allow multiple SourceRef elements for a given Code element

  • Reported: KDM 1.0b1 — Wed, 7 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Lack of fidelity for advance flow analysis

  • Key: KDM-138
  • Legacy Issue Number: 10652
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    The current KDM allows for the representation of flow information through various action elements, but the current representation is too vague and lacks the full fidelity needed to provide detailed static analysis “grade” representations, especially when we are being asked to produce this in a standard compliant fashion. Currently, an action element is underspecified: it can be one statement, or more than one statement, or less than one statement. If it is too coarse grained, we are loosing precision regarding the semantics of the Reads and Writes and operations performed and access to complex data structures. What we need is either a finer-grained model or at least a specification that would standardize the way the current elements should be used in order to create a compliant KDM model with “instruction-level” fidelity. Maybe this new “micro-KDM” compliance point becomes part of the optional L1 categories, so that we at least can all agree and understand how to process this kind of information.

  • Reported: KDM 1.0b1 — Wed, 7 Feb 2007 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for UsesCallable class

  • Key: KDM-134
  • Legacy Issue Number: 10463
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.6.2
    Severity: minor
    Nature: clarification

    13.6.2 UsesCallable Class
    The UsesCallable is an association class to provide linkages between ActionElement and CodeElement for any references
    to a CallableElement, other than performing a call.
    Should talk about UsesCode instead

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for CallableRelations class

  • Key: KDM-132
  • Legacy Issue Number: 10461
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.6
    Severity: minor
    Nature: clarification

    13.6 CallableRelations Class Diagram

    The CallableRelations diagram describes the following types: o CodeRelationship - an association class subtyping KDMRelationship.

    o Calls - an association class representing a call type relationship between an ActionElement and a CallableInterface .

    CallableInterface should be CallableElement

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for EntryFlow class

  • Key: KDM-126
  • Legacy Issue Number: 10455
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.2
    Severity: minor
    Nature: clarification

    13.5.2 EntryFlow Class
    The ControlFlow is an association class representing the control flow between ActionElements.
    Superclass ActionRelationship

    Doesn't look like the right description and superclass (believe it should be FlowRelationship)?

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for ControlFlow class (04)

  • Key: KDM-130
  • Legacy Issue Number: 10459
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.8
    Severity: minor
    Nature: clarification

    13.5.8 GuardedFlow Class (abstract)
    The ImportRelationship class represents the family of relations corresponding to import of declarations between modules.
    Superclass
    ActionRelationship
    wrong description, not abstract and their superclass is ControlFlow

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for ControlFlow class (02)

  • Key: KDM-128
  • Legacy Issue Number: 10457
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.6
    Severity: minor
    Nature: clarification

    13.5.6 TrueFlow Class (abstract)
    The ImportRelationship class represents the family of relations corresponding to import of declarations between modules.
    Superclass
    ActionRelationship
    wrong description, not abstract and their superclass is ControlFlow

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Missing specification detail for ControlFlow class

  • Key: KDM-131
  • Legacy Issue Number: 10460
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.8
    Severity: minor
    Nature: clarification

    Missing specification on how to represent default flow when representing a switch construct using GuardedFlow. The semantics of FalseFlow should be made more generic as a default case, then it can be used to represent both the conditional flows as wells as GuardedFlows

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for ControlFlow class (03)

  • Key: KDM-129
  • Legacy Issue Number: 10458
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.7
    Severity: minor
    Nature: clarification

    13.5.7 FalseFlow Class (abstract)
    The ImportRelationship class represents the family of relations corresponding to import of declarations between modules.
    Superclass
    ActionRelationship
    wrong description, not abstract and their superclass is ControlFlow

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for 12.10.2 TemplateParameter Class

  • Key: KDM-123
  • Legacy Issue Number: 10452
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Section 12.10.2
    Severity: minor
    Nature: clarification

    12.10.2 TemplateParameter Class The TemplateParameter is a CodeElement and is a parameter for TemplateUnit.
    In the KDM, TemplateParameter is a specialization of TypeElement more specifically.
    The text mentions CodeElement, while the diagram mentions CodeResource.

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for ControlFlow class

  • Key: KDM-125
  • Legacy Issue Number: 10454
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.1
    Severity: minor
    Nature: clarification

    13.5.1 ControlFlow Class The ControlFlow is an association class representing the control flow between ActionElements.
    Superclass ActionRelationship
    Doesn't look like the right superclass, believe it should be FlowRelationship

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for DerivedTypeElement class

  • Key: KDM-124
  • Legacy Issue Number: 10453
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 12.14.1
    Severity: minor
    Nature: clarification

    12.14.1 DerivedTypeElement Class The DerivedTypeElement is a meta-model element that represents user-defined types that are derived from a certain base type. In the meta-model the RefinementType is a subclass of TypeContainer. It is associated with the corresponding base type. This class is subclassed by several more specific KDM classes.

    The text mentions RefinementType, but the diagram mention DerivedType.

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong text for ControlFlow class

  • Key: KDM-127
  • Legacy Issue Number: 10456
  • Status: closed  
  • Source: Benchmark Consulting ( Alain Picard)
  • Summary:

    Section 13.5.5
    Severity: minor
    Nature: clarification

    13.5.5 Flow Class (abstract) The ImportRelationship class represents the family of relations corresponding to import of declarations between modules.
    Superclass ActionRelationship
    wrong description, not abstract and their superclass is ControlFlow

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 21.3

  • Key: KDM-119
  • Legacy Issue Number: 10408
  • Status: closed  
  • Source: Princeton Blue, Inc. ( Vitaly Khusidman)
  • Summary:

    The diagram in the Figure 21.2 incorrectly shows that ConceptualElement is a specialization of KDMGroup (from Core). It is also inconsistent with the diagram in the Figure 22.2 (Behavior Package). The correct way to show Conceptual Inheritances is: ConceptualGroup is a specialization of KDMGroup (from Core) and ConceptualElement is a specialization of KDMGEntity (from Core)

  • Reported: KDM 1.0b1 — Thu, 12 Oct 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 17

  • Key: KDM-118
  • Legacy Issue Number: 10338
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Add state as an explicit entity (suggested by Larry Hines in Boston)

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9

  • Key: KDM-120
  • Legacy Issue Number: 10412
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    This is another occurence of "backward navigation" references in the KDM Core. KDM requires navigable associations from KDMEntity to KDMGroup (in the Core KDM this association is named group, see Figure 9.1). While useful for certain type of cross-referencing queries (e.g. to which groups does the given entity belong), these associations make KDM instance XMI extremely inflexible and hard to modify (as information abut relations is essentially duplicated). Also, as this element is subsetted by various groups, children of KDMEntity get funny collections of such associations (e.g. UIGroup, CodeGroup associations, etc). It is better to eliminate all these associations, and leave only the association from the KDMGroup to the KDMEntity element. The group association can be changed into an operation, and implemented internally by particular KDM tools.

  • Reported: KDM 1.0b1 — Wed, 18 Oct 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.13

  • Key: KDM-114
  • Legacy Issue Number: 10333
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Consider adding a special extensibility attrbiute to Predefined classes (since they have to be extended in most cases by adding more precise language specific constraints). This will be a shortcut to adding a Stereotype

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Need additional attribute for SourceFile element to specify encoding

  • Key: KDM-122
  • Legacy Issue Number: 10451
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Section 11.4
    Severity: minor
    Nature: clarification

    KDM assumes that a source file is a sequence of lines, identified by a linenumber. Each line is a sequence of characters, identified by a position within the line. Whitespace characters like tabulation are considered to be a single character.

    What is the definition of character in regards to the KDM? Is it a byte, 2 bytes, UTF-8 or ????, What about special characters such as in Java \u0234. How should that work?
    Are both line numbers and position, 1 based?

    An additional attribute to specify encoding is needed for the element SourceRegion and SourceFile.

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Insufficient specification of KDMAggregatedRelationship class

  • Key: KDM-121
  • Legacy Issue Number: 10450
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Section 9.5.1
    Severity: minor
    Nature: clarification

    9.5.1 KDMAggregatedRelationship Class The KDMAggregatedRelationship represents the set of aggregated relationships of the given entity. The set of derived relationships consists of the primitive relationships of the current entity and of all primitive relationships of the entities that are recursively contained in the current entity.
    What is the difference between aggregated and derived relationships?
    Can you shed light with an example on the recursive nature of relationship, is this related to group and container type entities?

  • Reported: KDM 1.0b1 — Sat, 18 Nov 2006 05:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.17

  • Key: KDM-115
  • Legacy Issue Number: 10334
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Add attribute

    {public, private, etc.}

    to members of the class

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13

  • Key: KDM-116
  • Legacy Issue Number: 10335
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Consider adding (an optional) ActionRelation for detailed tracking of the usages of operations in the language (like "+", "*", etc.). Size of the model needs to be taked into consideration.

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.9

  • Key: KDM-113
  • Legacy Issue Number: 10332
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing parameters to the MacroUnit

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13

  • Key: KDM-117
  • Legacy Issue Number: 10337
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Consider optimizing the usage of Flow relations by making them

    {ordered}

    . This would lead to more efficient handling of the basic blocks, and Flow relation will be only needed for goto constructs. The xmi file will remain very readable.

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.4

  • Key: KDM-111
  • Legacy Issue Number: 10330
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    CodeContainer is redundant, since it can not be instanciated

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10.4 page 32

  • Key: KDM-108
  • Legacy Issue Number: 10327
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Add capability to add Stereotypes to Models (currently, Stereotypes can only be added to ModelElements, not to Elements, since ModelElements represent artifacts of existing systems, and Elements are part of the metamodel infrastructure).

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9

  • Key: KDM-109
  • Legacy Issue Number: 10328
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Need generic extensible entity and relationship. Currently, this is somewhat limited because of abstract classes tat can not be instanciated.

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10.3

  • Key: KDM-106
  • Legacy Issue Number: 10325
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Move association "Segements" from Root to ModelRoot, so that Segements can contain Segments, and kdm framework is more flexible.

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM-110
  • Legacy Issue Number: 10329
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Add model elements to represent exceptions (try blocks, exception types, catch with formal parameters, throw), for example in Java and in C++.

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 10.4

  • Key: KDM-107
  • Legacy Issue Number: 10326
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Try to decouple kdm package from other packages, for example by introducing "extensible" kdm model and removing explicit associations with models. Complexity of queries needs to be taken into consideration

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM-112
  • Legacy Issue Number: 10331
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing

    {ordered}

    specifications for some elements, such as CodelElement in CallableElement, in MacroUnit; TemplateParameters, EnumeratedLiterals in EnumeratedUnit, ActionRelations, fields in CompositeUnit, all members in ClassUnit

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section 93.

  • Key: KDM-103
  • Legacy Issue Number: 10322
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Suggestion to make diagram at figure 9.1 more "balanced" (mutually exclusive subtypes) by introducing an extra subclass "KDMElement" as a subtype of KDMEntity and changing other diagrams accordingly

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9.6.1

  • Key: KDM-104
  • Legacy Issue Number: 10323
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    add more elements to the InstanceKind: -member -signature -unknown

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 9

  • Key: KDM-105
  • Legacy Issue Number: 10324
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Add an entity id into the Core model, to be used in reasoning about KDM entities, for example, to make a statement that two variables are the same

  • Reported: KDM 1.0b1 — Tue, 5 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (07)

  • Key: KDM-101
  • Legacy Issue Number: 10318
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200521 from submitters database Originally raised by Nick Mansourov Introduce strongly typed MarshalledCall relation between MarshalledService and instance of MarshalledResource

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (09)

  • Key: KDM-102
  • Legacy Issue Number: 10320
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1910200501 from submitters database Originally raised by Nick Mansourov Need to perform unification of triggers and platform bindings

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169

  • Key: KDM-95
  • Legacy Issue Number: 10312
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200501 from submitters database Originally raised by Nick Mansourov Review backward navigation from ResourceInstance to ResourceElement

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (04)

  • Key: KDM-98
  • Legacy Issue Number: 10315
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200523 from submitters database Originally raised by Nick Mansourov Consider renaming PlatfromRelations to ResourceRelation

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (06)

  • Key: KDM-100
  • Legacy Issue Number: 10317
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issues 1211200518,1211200519,1211200520 from submitters database Originally raised by Nick Mansourov Rename Activation to ActivationService Rename Registration to NamingService Rename MarshalledCall to MarshalledService

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (02)

  • Key: KDM-96
  • Legacy Issue Number: 10313
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200502 from submitters database Originally raised by Nick Mansourov Optional ownership of ResourceElement & ResourceInstance by ResourceType

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (03)

  • Key: KDM-97
  • Legacy Issue Number: 10314
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200506 from submitters database Originally raised by Nick Mansourov inverse platform activations relations

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169

  • Key: KDM-93
  • Legacy Issue Number: 10310
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2610200507 from submitters database Originally raised by Howard Hess (IBM) relate platform activations and bindings to UI triggers This is similar to issue 1901200601 review platform element as a special form of binding; maybe need a more generic mechanism to support integration of models.

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (02)

  • Key: KDM-94
  • Legacy Issue Number: 10311
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 3110200504 from submitters database Originally raised by Nick Mansourov DataManager is a deployment resource. Should it be moved to RunTime view? Missing association to Data model elements

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19

  • Key: KDM-92
  • Legacy Issue Number: 10309
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 0410200501 from submitters database Originally raised by Mike Smith (EDS) Environment relations should be related to triggers, dataports, etc.

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (05)

  • Key: KDM-99
  • Legacy Issue Number: 10316
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1903200602 from submitters database Originally raised by Nick Mansourov relation or group association from external actor to triggers

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 20 pages 171 - 183 (02)

  • Key: KDM-91
  • Legacy Issue Number: 10308
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200517 from submitters database Originally raised by Nick Mansourov Rename RunTimeRelations to RunTimeRelationship so that its name is uniform with other generic relation elements

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 20 pages 171 - 183

  • Key: KDM-90
  • Legacy Issue Number: 10307
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200508 from submitters database Originally raised by Nick Mansourov Review role names for Machine and DeployedComponent and DeployedResource, and the need for backward navigability

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (09)

  • Key: KDM-88
  • Legacy Issue Number: 10304
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2103200601 from submitters database Originally raised by Nick Mansourov UI package should define actions corresponding to UI things

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (07)

  • Key: KDM-86
  • Legacy Issue Number: 10302
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200610 from submitters database Originally raised by Nick Mansourov Consider DisplayUnit as a group for its data, rather than a relationship to data: in BMS the data definition is autogenerated as a copybook, with two parts, one suffixed with "I" for input and another - with "O" for output; In Visual Basic Control elements are objects with data fields In Web there is a JavaBean

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (10)

  • Key: KDM-89
  • Legacy Issue Number: 10305
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2103200602 from submitters database Originally raised by Nick Mansourov UI package should define code elements corresponding to UI things

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (06)

  • Key: KDM-85
  • Legacy Issue Number: 10301
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200607 from submitters database Originally raised by Nick Mansourov Endpoint of Displays relation is like a resource instance in Platform; needs review

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (08)

  • Key: KDM-87
  • Legacy Issue Number: 10303
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1903200605 from submitters database Originally raised by Nick Mansourov UI package should define its own Event UIEvent

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (04)

  • Key: KDM-83
  • Legacy Issue Number: 10299
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200605 from submitters database Originally raised by Nick Mansourov Change CallableElement to ActionElement in Displays relation in UI package

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (05)

  • Key: KDM-84
  • Legacy Issue Number: 10300
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200606 from submitters database Originally raised by Nick Mansourov Add capability to represent receiving data from DisplayUnits

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148

  • Key: KDM-81
  • Legacy Issue Number: 10296
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200601 from submitters database Originally raised by Nick Mansourov DisplayUnits should be groups for Triggers

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18

  • Key: KDM-80
  • Legacy Issue Number: 10295
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1410200504 from submitters database Originally raised by Nick Mansourov introduce precise actions for UI

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18 pages 137 - 148 (03)

  • Key: KDM-82
  • Legacy Issue Number: 10298
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200604 from submitters database Originally raised by Pete Rivett (Adaptive) UIContainer should be a Group for triggers

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 13.4

  • Key: KDM-78
  • Legacy Issue Number: 10290
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 0302200602 from submitters database Originally raised by Nick Mansourov Action Containers are missing

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12, page 41-74 (02)

  • Key: KDM-76
  • Legacy Issue Number: 10287
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 0602200602 from submitters database Originally raised by Adam Neal (Klocwork) Role names "class", 'interface' and 'package' are reserved Java keywords. They introduce conflicts during JMI generation

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM-73
  • Legacy Issue Number: 10284
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 0308200503 from submitters database Originally raised by Mike Smith (EDS) Add a general "depends" relationship between two CodeEntities

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 17

  • Key: KDM-79
  • Legacy Issue Number: 10292
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1410200505 from submitters database Originally raised by Nick Mansourov introduce precise actions for triggering

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12 (02)

  • Key: KDM-74
  • Legacy Issue Number: 10285
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1309200505 from submitters database Originally raised by Nick Mansourov consistency of models wrt source ref in case of macros (links to fully expanded macro and source of macros).

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12, page 41-74

  • Key: KDM-75
  • Legacy Issue Number: 10286
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2009200501 from submitters database Originally raised by Nick Mansourov representation of variants (conditional compilation

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12, page 41-74 (04)

  • Key: KDM-77
  • Legacy Issue Number: 10289
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200603 from submitters database Originally raised by Nick Mansourov Review the semantics and usages of CodeGroup. Missing examples of the usage of CodeGroup.

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12.18

  • Key: KDM-72
  • Legacy Issue Number: 10283
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 0510200504 for submitters database Originally raised by Larry Hines (EDS) Distinguish parameter passing variants Add attributes to Signature parameters, like ParameterKind with values ByName, ByValue. This will provide a capability to distinguish various forms of parameter passing.

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 17 pages 131 - 136 (02)

  • Key: KDM14-290
  • Legacy Issue Number: 10294
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2610200506 from submitters database Originally raised by Howard Hess (IBM) Missing example on how to represent a trigger without an explicit activation

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Data package contains a combined example related to this. See file kdm_1.0.2_changes.pdf.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 pages 149 - 169 (10)

  • Key: KDM14-291
  • Legacy Issue Number: 10321
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2610200504, 2610200505 from submitters database Originally raised by Howard Hess (IBM) Missing example, illustrating a DataResource. Illustrate representation of a JDBC

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Example to Data package contains illustration of JDBC. See file kdm_1.0.2_changes.pdf.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 16

  • Key: KDM14-294
  • Legacy Issue Number: 10131
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the Structure package illustrating extraction of susbystems, layers and components and their representation as KDM XMI instances

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Example added. Had to do some followup on issue 10712 to allow concrete from and to
    properties to AggregatedRelationship instead of derived properties. See file
    kdm_1.0.2_changes.pdf

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 18

  • Key: KDM14-293
  • Legacy Issue Number: 10134
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the UI package illustrating extraction of various elements and their representation as KDM XMI instances

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Example of UI representation is provided in combination with Conceptual model example. See file
    kdm_1.0.2_changes.pdf attached.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 15 (Data package illustrating extraction of xml file elements )

  • Key: KDM14-295
  • Legacy Issue Number: 10130
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the Data package illustrating extraction of xml file elements

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Data package contains 2 example of structured content representation in KDM. ContentElements
    diagram slightly modified to align with datatype representation in CodeModel (explicit type
    association for content elements). See file kdm_1.0.2_changes.pdf

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 17

  • Key: KDM14-292
  • Legacy Issue Number: 10133
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the Event package illustrating extraction of various elements and their representation as KDM XMI instances

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Example of combined usage of Code, Data, Platform and Event packages was provided in Data
    chapter (illustrating RecordFile manipulation in Cobol). See file kdm_1.0.2_changes.pdf attached.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 22

  • Key: KDM14-298
  • Legacy Issue Number: 10127
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for Behavior pacakge illustrating the extraction and usage of ScenarioUnit, BehaviorUnit, RuleUnit and other elements as KDM instance XMI

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Closed; No Change — KDM 1.0
  • Disposition Summary:

    Behavior package has been merged with Conceptual package.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 15

  • Key: KDM14-296
  • Legacy Issue Number: 10128
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the Data package illustrating extraction of relational database elements

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Data package contains example of relational database schema representation in KDM. 2
    diagrams were slightly modified to makes them follow uniform Resource Layer pattern.
    See kdm_1.0.3_changes.pdf file attached.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 15 (extraction of record database elements )

  • Key: KDM14-297
  • Legacy Issue Number: 10129
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example(s) for the Data package illustrating extraction of record database elements

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Example of RecordFile manipulation in Cobol is provided. Also, example of IMS representation is
    provided. 2 diagrams of the Data package were made more extensible, following the uniform
    Resource layer pattern. See file kdm_1.0.2_changes.pdf.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 21

  • Key: KDM14-300
  • Legacy Issue Number: 10126
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing example for Conceptual package illustrating the extraction and usage of TermUnit, FactUnit and other elements as KDM instances in XMI

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Resolved. One diagram was updated to reflect the uniform Resource and Abstractions Layer
    pattern. See kdm_1.0.2_changes.pdf file attached.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 12

  • Key: KDM14-301
  • Legacy Issue Number: 10101
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing descriptions of associations in Code package. Specification is missing descriptions of some associations: section 12.4.4. Codegroup class section 12.8.2 Prototype class 12.8.3. Code Element (additional properties) 12.9.1. MacroUnit 12.10.1 templateUnit 12.11.1 Instantiates class 12.11.2 InstanceOf 12.11.3 CodeResource (additional properties) 12.20.3 CodeResource (additional properties) 12.20.4 Interface(additional properties) 12.20.5 Signature(additional properties) 12.21.2. CodeResource (additional properties)

  • Reported: KDM 1.0b1 — Tue, 15 Aug 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Multiple descriptions of associations and missing semantic notes added. See
    kdm_1.0.2_changes.pdf file attached.

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Section: 19 (03)

  • Key: KDM14-299
  • Legacy Issue Number: 9997
  • Status: closed  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Missing comprehensive example for Platform package as KDM instance, like the one used in KDM tutorial

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Disposition: Resolved — KDM 1.0
  • Disposition Summary:

    Example of combined usage of CodeModel, DataModel, PlatformModel and EventModel is
    provided (illustrating RecordFile manipulation in Cobol), DataModel chapter.
    When validating the example, 3 diagrams of the Platform package were slightly modified for that
    they follow the uniform Resource Layer pattern. See kdm_1.0.2_changes.pfd file attached.

  • Updated: Fri, 6 Mar 2015 20:57 GMT