Knowledge Discovery Metamodel Avatar
  1. OMG Specification

Knowledge Discovery Metamodel — Open Issues

  • Acronym: KDM
  • Issues Count: 12
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Are missing constraints to specify clearly Subsystems, Layers, Components, SoftwareSystems, and ArchitectureViews

  • Key: KDM15-14
  • Legacy Issue Number: 13162
  • Status: open  
  • Source: Politecnico di Milano ( Matteo Miraz)
  • Summary:

    Are missing constraints to specify clearly Subsystems, Layers, Components, SoftwareSystems, and ArchitectureViews

  • Reported: KDM 1.0b1 — Mon, 15 Dec 2008 05:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Component should allow one to express exposed and required services

  • Key: KDM15-13
  • Legacy Issue Number: 13161
  • Status: open  
  • Source: Politecnico di Milano ( Matteo Miraz)
  • Summary:

    Component should allow one to express exposed and required services. An entity connection should be also created to manage the connections between them.

  • Reported: KDM 1.0b1 — Mon, 15 Dec 2008 05:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

KDM is missing constraints capabilities to stereotype

  • Key: KDM15-12
  • Legacy Issue Number: 13159
  • Status: open  
  • Source: Politecnico di Milano ( Matteo Miraz)
  • Summary:

    KDM is missing constraints capabilities to stereotype. It is nice to have a metamodel element to express: * a description (in plain english) of the constraint. * the constraint language used (e.g. OCL) * the constraint expression * the severity of the constraing (WEAK / SEVERE)

  • Reported: KDM 1.0b1 — Mon, 15 Dec 2008 05:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

consider having a StorableUnit and CallableUnit, maybe with an explicit kind

  • Key: KDM15-9
  • Legacy Issue Number: 11717
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    For discussion. When transforming procedures to methods KDM objects needs to be changed, it is not as easy as moving
    something to class. We should consider having a StorableUnit and CallableUnit, maybe with an explicit kind.
    This will leave the only distincltion between them in micro actions.

  • Reported: KDM 1.0 — Sat, 1 Dec 2007 05:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Consider Uniform representation of exception object and classes

  • Key: KDM15-8
  • Legacy Issue Number: 11711
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Consider Uniform representation of exception object and classes as they are being thrown
    (check out Ada, it uses an extendable enumerated class)

  • Reported: KDM 1.0 — Sat, 1 Dec 2007 05:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

9.5.1 Semantics: should be expressed in OCL

  • Key: KDM15-7
  • Legacy Issue Number: 11176
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    9.5.1 Semantics: should be expressed in OCL

  • Reported: KDM 1.0 — Mon, 23 Jul 2007 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Need ResolvedMarshalledCall element

  • Key: KDM15-6
  • Legacy Issue Number: 10319
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1211200522 from submitters database Originally raised by Nick Mansourov Introduce ResolvedMarshalledCall from MarshalledService directly to CodeElement

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Need illustration of runtime context

  • Key: KDM15-5
  • Legacy Issue Number: 10306
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 2610200502 from submitters database Originally raised by Nick Mansourov Missing illustration how to represent runtime context for the following situation: (ps | wc -l; ps | grep "root") where the same deployment component is used in two contexts

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Need illustration of logical events

  • Key: KDM15-4
  • Legacy Issue Number: 10293
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1703200611 from submitters database Originally raised by Nick Mansourov Missign example on how to represent a logical event that is implemented as a field in a message (a non-event dirven system, implicit events); also how to handle default handling of implicit events

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Need example for reflection in Java

  • Key: KDM15-3
  • Legacy Issue Number: 10288
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

    Issue 1302200602 from submitters database Originally raised by Alain Picard (CastorTech) Missing example of how to represent reflection mechanisms in Java

  • Reported: KDM 1.0b1 — Sun, 3 Sep 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Need illustration for Platform package

  • Key: KDM15-2
  • Legacy Issue Number: 10135
  • Status: open  
  • Source: KDM Analytics ( Nikolai Mansourov)
  • Summary:

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

  • Reported: KDM 1.0b1 — Wed, 23 Aug 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT

Need traceability for indirect messages

  • Key: KDM15-1
  • Legacy Issue Number: 9995
  • Status: open  
  • Source: International Business Machines ( Howard Hess)
  • Summary:

    Need traceability for indirect messaging relations in Platform package, as per example used in the tutorial.

  • Reported: KDM 1.0b1 — Wed, 26 Jul 2006 04:00 GMT
  • Updated: Tue, 29 Mar 2016 15:21 GMT