United Architecture Framework Avatar
  1. OMG Specification

United Architecture Framework — Open Issues

  • Acronym: UAF
  • Issues Count: 1
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Issues Descriptions

UAF extensions of CallBehaviorAction should also support CallOperationAction

  • Key: UAF13-8
  • Status: open  
  • Source: Department of Navy ( James Ciarcia)
  • Summary:

    SysML allows the use of CallOperationAction as an alternate means of mapping Behaviors (via Operation->Method metaproperty).
    UAF 1.1 includes OperationalActivityAction, ProjectActivityAction, ServiceFunctionAction, FunctionAction or SecurityProcessAction which all extend CallBehaviorAction.
    UAF 1.1 also includes OperationalMethod, ServiceMethod, ResourceMethod, which extend Operation, and even has metaconstraints requiring appropriately UAF stereotyped Activity used as the Method.

    We recommend allowing CallOperationAction to also be stereotyped by the UAF extensions to CallBehaviorAction listed above.
    We also recommend creating ProjectMethod and SecurityMethod as extentions to Operation to be consistent with other Domains.
    This would facilitate it's use in Operational::Connectivity, Operational::Processes and Security Processes, Project Processes, Personnel Processes, Resource Processes and Resources Connectivity Diagrams and Tables.
    This is especially useful to visualize and take advantage of CallOperationAction target pin and method resolution per UML 2.5 13.2.3.5 Behavioral Features and Methods. It is also useful for fUML 1.2.1 Polymorphic Operation Dispatching ability to execute method resolution during simulation and analysis. Thus a tighter integration of UAF with UML method resolution semantics and executability can be achieved both visually and from a simulation and analysis perspective.

  • Reported: UAF 1.1b1 — Wed, 2 Jun 2021 17:08 GMT
  • Updated: Fri, 14 Jan 2022 21:16 GMT