Semantics of a Foundational Subset for Executable UML Models Avatar
  1. OMG Specification

Semantics of a Foundational Subset for Executable UML Models — All Issues

  • Acronym: FUML
  • Issues Count: 3
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

Correction to the resolution to issue FUML14-10

  • Key: FUML14-21
  • Status: closed  
  • Source: Model Driven Solutions ( Ed Seidewitz)
  • Summary:

    The resolution to issue FUML14-10 added code to ExecutionFactory::instantiateVistor to instantiate CentralBufferNodeActivation and DataStoreNodeActivation. However, since DataStoreNode is a kind of CentralBufferNode, and the test for CentralBufferNode comes before DataStoreNode, the test for CentralBufferNode needs to also test that the element being visited is not a DataStoreNode, in order to avoid incorrectly instantiating a CentralBufferNodeActivation for a DataStoreNodeActivation. The resolution to FUML14-10 neglects to do this.

  • Reported: FUML 1.3 — Thu, 10 May 2018 02:28 GMT
  • Disposition: Resolved — FUML 1.4
  • Disposition Summary:

    Correct resolution to issue FUML14-10

    Correct the error in FUML14-10 regarding the instantiation of DataStoreNodeActivation.

  • Updated: Wed, 3 Oct 2018 14:20 GMT

Migrate fUML to UML 2.5.1

  • Key: FUML14-9
  • Status: closed  
  • Source: Model Driven Solutions ( Ed Seidewitz)
  • Summary:

    Subclause 6.2 Changes to Adopted OMG Specifications of the Precise Semantics for UML State Machines (PSSM) Beta 1 specification document (ptc/17-04-04) states:

    The PSSM syntax is a subset of the UML 2.5.1 abstract syntax metamodel, and the required functionality formalized in PSSM is taken from that specified in UML 2.5.1. However, PSSM is also semantically based on fUML and PSCS. But the current versions of these standards, fUML 1.2.1 and PSCS 1.0 are based on UML 2.4. In order to avoid inconsistency, particularly given the sweeping reorganization of the UML abstract syntax metamodel adopted in UML 2.5, the fUML and PSCS syntax and semantics models have been migrated to UML 2.5.1 for use with PSSM, but with no change to their functionality. In addition, the fUML and PSCS models have been updated to use an approach for identifying and constraining their syntax subsets that is consistent with that used in PSSM.

    In adopting this specification, the fUML RTF was directed to update the fUML specification consistent with the migration of fUML syntax and semantics models top UML 2.5.1. Since the adoption of PSSM, fUML 1.3 has been approved as the current version of fUML, so the fUML 1.4 RTF now needs to carry out the migration of fUML 1.3 to UML 2.5.1 for fUML 1.4.

  • Reported: FUML 1.3 — Tue, 26 Dec 2017 23:05 GMT
  • Disposition: Resolved — FUML 1.4
  • Disposition Summary:

    Migrate fUML to UML 2.5.1

    Migrating fUML to UML 2.5.1 and adopting the new approach for identifying and constraining their syntax subsets (but with no change to fUML functionality), requires the following updates to the fUML specification document:

    • Remove the reflection of UML conformance levels in fUML and any references to the infrastructure/superstructure separation.
    • Update the normative references to UML 2.5.1 and the latest versions of the MOF, OCL and XMI specificatiopns.
    • Update subclause 6.1 Changes to Adopted Specifications to reflect the semantic clarifications in UML 2.5.1.
    • Update Clause 7 Abstract Syntax to reflect the UML 2.5.1 package structure and the new approach for specifying the fUML abstract syntax subset.
    • Update Clause 8 Execution Model to reflect the UML 2.5.1 package structure.

    The normative syntax and semantics XMI also need to be updated to reflect the new approach for specifying the abstract syntax subset and for the UML 2.5 reorganization.

  • Updated: Wed, 3 Oct 2018 14:20 GMT
  • Attachments:

The ExecutionFactory class descriptions need to be updated in the specification for CentralBufferNode and DataStoreNode

  • Key: FUML14-10
  • Status: closed  
  • Source: Model Driven Solutions ( Ed Seidewitz)
  • Summary:

    The resolution to Issue FUML13-4 added CentralBufferNode and DataStoreNode to the fUML abstract syntax subset for fUML 1.3. However, the revised text in the resolution neglected updating the description of the ExecutionFactory instantiateVisitor operation in order to instantiate the corresponding CentralBufferNodeActivation and DataStoreNodeActivationClasses. However, in the normative fUML_Semantics.xmi file for the execution model, the code for the operation LociL2::ExecutionFactoryL2::instantiateVisitor actually has been updated to instantiate CentralBufferNodeActivation and LociL3::ExecutionFactoryL3::instantiateVisitor has been updated to instantiate DataStoreNodeActivation. This needs to be reflected in the corresponding descriptions for these operations in the specification document.

  • Reported: FUML 1.3 — Mon, 19 Feb 2018 17:58 GMT
  • Disposition: Resolved — FUML 1.4
  • Disposition Summary:

    Update ExecutionFactory for CentralBufferNode and DataStoreNode

    Update the specification for ExecutionFactory as necessary.

  • Updated: Wed, 3 Oct 2018 14:20 GMT