Correction of cross-layer relationship anomalies
There are a couple of cross-layer relationship anomalies, which stand out when one examines Figures 104 and 105.
-
Fig 104: Every aspect of the Business Layer can be realised by a corresponding aspect in the Application or Technology Layers, except for the Internal Active Structure. I propose that realization be added as appropriate between Internal Active Structures in different Layers.
-
Fig 105: The metamodel shows that is legal for an Application Internal Active Structure to be realised by an Artifact (i.e. a Passive Structure). I suppose this is due to a software developer’s perception that a component is implemented as code.
But it can’t be a true realisation if the thing being realised changes its nature in the process, in this case an Active Structure becomes a Passive one. This would have to continue to be permitted for a while due to backward compatibility issues, but I propose that this relationship should be marked for deprecation and replaced by a realisation between Internal Active Structures.