UPDM 2.0 FTF Avatar
  1. OMG Issue

UPDM2 — Section 8.2.1

  • Key: UPDM2-16
  • Legacy Issue Number: 17027
  • Status: closed  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    8.2.1 states that UPDM L1 " imports parts of SysML - Requirements and
    ModelElements namely." However that does not seem consistent with section 2.1 or the diagram

  • Reported: UPDM 2.0 — Fri, 20 Jan 2012 05:00 GMT
  • Disposition: Resolved — UPDM 2.0.1
  • Disposition Summary:

    section 2.1.1 has the following text
    Figure 2.2 illustrates that UPDM 2.0 Compliance Level 0 is an implementation of UPDM extending UML 2 and importing several SoaML stereotypes – namely Expose, Attachment, RequestPoint, ServicePoint, MessageType, Property. In order for a tool to be considered as compliant with L0, the following must be true:

    This is in contradiction to section 8.2.1 which says
    UPDM L0 contains all the Core, DoDAF, and MODAF elements, and imports parts of SysML - Requirements and ModelElements namely. This compliance level is primarily based on UML and reuse of a minimum of SysML elements. This includes Requirements and Views/Viewpoints. As one of the core principles is reuse, cloning/recreating of these existing SysML structures was considered as inappropriate.

    We will change section 8.2.1 to say
    UPDM L0 contains all the Core, DoDAF, and MODAF elements, reuses UML and imports parts of SoaML. This compliance level is primarily based on UML 2 and the import of a minimum of SoaML stereotypes. The SoaML stereotypes imported are Capability, ServiceInterface, Expose, Attachment, Request, Service, MessageType, Property, ServiceChannel and Participant.

  • Updated: Fri, 6 Mar 2015 20:59 GMT