-
Key: UAF14-127
-
Status: open
-
Source: Eclectica Systems Ltd ( Nic Plum)
-
Summary:
p158 9.1.4 Domain Metamodel::Operational - Operational Architecture, Figure 9:187
OperationalArchitecture is defined as:
'A type used to denote a model of the Architecture, described from the Operational perspective.'1) We incorrectly have a model of the architecture being a type of architecture (OperationalArchitecture specialises Architecture).
2) The description of the 'operational architecture' is the set of operational node elements and relationships (forming triples), perhaps augmented by some standards - it is incorrect then to have a concrete single element representing the same thing.
It isn't really any different as a type from Architecture - it seems to be purely a mechanism to show relationships with different operational elements. It isn't a distinct concept in what is supposed to be an abstract metamodel.
So what then is the relationship between 'OperationalArchitecture' and the description of an operational architecture (if the element really is 'architecture' and not 'architecture description'? It ought to conform to ISO 42010 ie something like 'expresses' or in the reverse sense 'is described by'
-
Reported: UAF 1.2 — Wed, 24 Apr 2024 12:04 GMT
-
Updated: Fri, 20 Dec 2024 14:57 GMT
UAF14 — OperationalArchitecture - an AD by Definition Specialises OperationalAgent and Architecture?
- Key: UAF14-127
- OMG Task Force: Unified Architecture Framework (UAF) 1.4 RTF