Inference rules not used, and not needed for completeness, should be removed

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

The specification should cover all ActivityNodes used in bUML. It should be added declarative definition for ActivityFinalNode because it is used in annex A.3.1, and A.3.2, pages 401, and 402. However, it should be evaluated the replacement of this node to FlowFinalNode. For the last, a proposal is defined

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

It should not define constraints for Actions outside the bUML: AcceptEventAction and ReadIsClassifiedObjectAction. In the other way around, it should be evaluated if these actions should be included in bUML. The java statement instanceof is used from page 98 to page 328, therefore the ReadIsClassifiedObjectAction should be added to bUML.

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

Base Semantics should declare the PSL version used to define it.

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

It should be made available a computer-readable version of the Base Semantics, as a CLF file. The place would be the OMG site where other files defined by this specification were available, such as, XML Metadata Interchange (XMI).

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

There were found 42 issues, 5 of them were enhancements proposals, and 37 were defects.

The main issues concerning defects were:
1. The Base Semantics had a defect in the section 10.4.8.3 (pg. 383). There was missing a forall construction, which did not allow to parse entire definition.
2. After applied the necessary remedy actions to the definition, a model finder (EPROVER) was used to check if the fUML definition together with PSL definition - psl_outer_core - was satisfiable. The fUML Base Semantics together with PSL was unsatisfiable.
3. A model finder (EPROVER) also was used to check if the Base Semantics alone (without PSL) was satisfiable. The fUML Base Semantics was unsatisfiable.

I have been made available a file with all analyzed files at the following address:

http://es.cs.uni-kl.de/people/romero/fUMLOMGIssue20130630.zip

This file can help to recognize the defects.

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

Specification: Semantics of a Foundational Subset for Executable UML Models, FTF Beta 3 (ptc/10-03-14)

The submission team for the Alf action language felt that it was important that the action language be able to support exceptions, since existing class models in UML may include operations that raise exceptions and it should be possible to use the action language to specify methods for such operations without having to change how errors are reported. However, without exceptions being included in the fUML subset, the mapping of the raising and handling of exceptions in the action language to fUML was too complicated and probably semantically questionable.

Therefore, support for the raising and handling of exceptions should be included in the fUML subset so that it can properly be included in the surface action language notation.

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

Specification: Semantics of a Foundational Subset for Executable UML Models, FTF Beta 2 (ptc/09-10-05)

The specification should have an annex describing the normative serialization of the fUML syntax, semantics and foundational library models, similar to Annexes G and H of the UML 2.3 superstructure specification.

Defer

Resolution of this issue is deferred, because the focus of the fUML 1.4 RTF is on migrating fUML to UML 2.5.1.

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.

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.

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.

Correct resolution to issue FUML14-10

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

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.

Update ExecutionFactory for CentralBufferNode and DataStoreNode

Update the specification for ExecutionFactory as necessary.