-
Key: UAF13-50
-
Status: open
-
Source: Aerospace Corporation ( Dr. James Martin)
-
Summary:
Capability is defined as an "ability to do something". As such, a capability cannot desire some state or some effect. Only things with "agency" can desire something. Agency is defined as the "means or mode of acting". Operational agents and resource performers have the "means of acting" while a capability does not possess this quality. Only some kind of "action" can lead to effects or state changes. See briefing slides.
Add relationships Operational Activity <leads to> Actual State and Function <leads to> Actual State (and same for Service Function). Remove Capability as a Desirer but link it to Actual State directly with <enables> relationship. Make Capability Configuration <exhibits> Capability.
See attached slides.
-
Reported: UAF 1.2 — Wed, 1 Jun 2022 13:22 GMT
-
Updated: Mon, 2 Sep 2024 01:00 GMT
-
Attachments:
- V13 Issue2 Architecture and Performers.pptx 1.56 MB (application/vnd.openxmlformats-officedocument.presentationml.presentation)
UAF13 — Capability has no agency, therefore cannot desire a state
- Key: UAF13-50
- OMG Task Force: Unified Architecture Framework (UAF) 1.3 RTF