BACM 1.0b2 FTF Avatar
  1. OMG Issue

BACM — Eliminate same named association with common src transformation rule

  • Key: BACM-100
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. James Rhyne)
  • Summary:

    Section 7.2 identifies a case where same named associations with identical src end types are to be treated as a single association with dst end types that are a union of the end types of the designated associations. This can be eliminated by substituting an abstract class that is a superclass of the class to be unioned and having the dst type be this superclass. This change simplifies the transformation program and eliminates possible misunderstanding of the specification.

  • Reported: BACM 1.0a1 — Thu, 27 Apr 2023 17:52 GMT
  • Disposition: Resolved — BACM 1.0b2
  • Disposition Summary:

    Add abstract superclass and terminate single association in superclass

    UML does not provide a way to specify multiple types for association ownedEnds or a semantic that would interpret this case as a union. Change the UML model to add an abstract superclass in the three cases where this occurs in the model and terminate a single association at this superclass. Add generalization arrows from the classes to be unioned to this superclass. Then delete 7.2.6 from the specification document. The new superclasses are JSTP in the ValueFit diagram, APCICB in the OutsourcedServiceOfferingDiagram and VSVSS in the Process diagram.

  • Updated: Mon, 2 Oct 2023 12:56 GMT
  • Attachments: