UAF 1.2 RTF Avatar
  1. OMG Issue

UAF12 — UAF Profile should be identified as an Enterprise Modeling Language

  • Key: UAF12-29
  • Status: closed  
  • Source: Aerospace Corporation ( Dr. James Martin)
  • Summary:

    Misunderstanding about whether the UAF Profile can be used in modeling an enterprise architecture. Not uncommon for managers to think that they must use SysML to model their EA since they don't realize that the UAFP is already designed with the semantics for modeling enterprise constructs such as capability, enterprise phase, processes, personnel, operations, services, portfolios, etc. This misunderstanding is largely due to fact that UAFP is called a "profile" and many don't understand what is meant by profile.

    Suggest changing title of UAFP document to something like "UML Profile for UAF-based Enterprise Modeling". Or "UML Profile for UAF: Definition of an Enterprise Modeling Language".

  • Reported: UAF 1.1 — Wed, 11 Dec 2019 00:06 GMT
  • Disposition: Resolved — UAF 1.2
  • Disposition Summary:

    UAFP renamed to UAFML

    The decision has been taken by the group to rename the profile part of the specification to the modelling language following the naming convention of OMG, e.g. UML, SysML, SoaML, RAAML, etc. The change will improve clarity of the purpose of the document as the term "Profile" is not so well understood in non UML modellers community. Plus it is more than just profile. It also brings notation.

  • Updated: Thu, 31 Mar 2022 19:31 GMT