UAF 1.1 RTF Avatar
  1. OMG Issue

UAF11 — UAFP Inheritance from SysML issues.

  • Key: UAF11-77
  • Status: closed  
  • Source: INCOSE ( Matthew Hause)
  • Summary:

    Section 7 says “UAFP imports the entire SysML profile and contains a set of constraints that specify which SysML stereotypes are applied to the UAFP elements.”. This isn’t true. UPDM was done this way but UAF was done by inheriting from SysML stereotypes instead, so no dual stereotyping and constraints exist.

  • Reported: UAF 1.0 — Thu, 11 Jan 2018 19:41 GMT
  • Disposition: Resolved — UAF 1.1
  • Disposition Summary:

    The text is updated (see description)

    Replace:
    "UAFP imports the entire SysML profile and contains a set of constraints that specify which SysML stereotypes are applied to the UAFP elements. This is intended to provide more seamless integration with system modeling using SysML and to be able to fully leverage the capabilities of SysML in UAFP. An example of this is the integration of Requirements into the UAFP and also the use of Parametric Diagrams and integration of elements based upon instance specifications to allow the assessment of measures within an architecture developed using UAFP."
    with
    "UAFP imports the entire SysML profile and a number of UAFP stereotypes inherit from SysML stereotypes. This is intended to provide more seamless integration with system modeling using SysML and to be able to fully leverage the capabilities of SysML in UAFP. An example of this is the integration of Requirements into the UAFP and also the use of Parametric Diagrams and integration of elements based upon instance specifications to allow the assessment of measures within an architecture developed using UAFP."

  • Updated: Tue, 8 Oct 2019 17:49 GMT