Interaction Flow Modeling Language Avatar
  1. OMG Specification

Interaction Flow Modeling Language — Open Issues

  • Acronym: IFML
  • Issues Count: 3
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Class DomainConcept shoud have multiplicity 0..* with Databinding Class on the model

  • Key: IFML-79
  • Status: open   Implementation work Blocked
  • Summary:

    The way this multiplicity is described on the model does not allow references the same domain concept os different ViewComponents. This way the domain concept on the instances can be referenced only once. The same should be corrected on the diagram 8.18 on page 27.
    The validation to guarantee that, for example, two databindings in the same ViewComponent cannot reference the same domain concept should be implemented with other concept than multiplicity.
    So dataBinding [0..1]: DataBinding - Reference to the DataBinding in a ViewComponent that uses thecurrent DomainConcept.
    Should be replaced by
    dataBinding [0..*]: DataBinding - One DomainConcept can be referenced by many databindings. But one Databinding in a ViewComponent should reference only one current DomainConcept.

  • Reported: IFML 1.0 — Tue, 4 Feb 2020 06:52 GMT
  • Updated: Wed, 5 Feb 2020 16:43 GMT

Metamodel for Events is not clear

  • Key: IFML-78
  • Status: open   Implementation work Blocked
  • Source: Unversitas Indonesia ( Hafiyyan Sayyid Fadhlillah)
  • Summary:

    Dear OMG colleagues,

    I am currently reading about IFML Metamodel for my graduate thesis about Web Code Generator using IFML. I am reading about his particular notation (Events) but I'm having a hardtime reading the metamodel because :

    1. The text isn't clear
    2. Some of class diagram notation isn't clear enough.

    To avoid a misinterpretation, I am hoping that you can give a clarification or a new Metamodel Diagram Image for me so that I can interpret it clearly.

    Thank you for your attention,

    Best Regards,
    Hafiyyan Sayyid Fadhlillah,

    Post-graduate Student,
    Faculty of Computer Science Universitas Indonesia

  • Reported: IFML 1.0 — Tue, 27 Feb 2018 07:48 GMT
  • Updated: Fri, 6 Apr 2018 19:25 GMT

JUMP event type

  • Key: IFML-1
  • Legacy Issue Number: 18940
  • Status: open  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    A new event type should be added, for allowing direct jump from one place in the diagram to another.

  • Reported: IFML 1.0b2 — Tue, 17 Sep 2013 04:00 GMT
  • Updated: Sat, 7 Mar 2015 01:07 GMT