Unified Profile for DoDAF and MODAF Avatar
  1. OMG Specification

Unified Profile for DoDAF and MODAF — Open Issues

  • Acronym: UPDM
  • Issues Count: 3
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Figure 7.8: <> should be changed to <>

  • Key: UPDMRTF-2
  • Legacy Issue Number: 17206
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Steve Cook)
  • Summary:

    Figure 7.8 uses <<metaproperty>> where it means <<metaconstraint>>

  • Reported: UPDM 2.0 — Thu, 1 Mar 2012 05:00 GMT
  • Updated: Thu, 11 Apr 2024 13:10 GMT

Views should be Normative

  • Key: UPDMRTF-8
  • Legacy Issue Number: 17430
  • Status: open  
  • Source: Independent ( Leonard Levine)
  • Summary:

    While the proper implementation of a UPDM 2.0 Profile assures successful exchange of data models, the exact content of the VIEWS remain non-normative. There needs to be a definition of the minimum data elements to support each view as well as optional data elements. The UPDM RTF Group needs to discuss whether all (52?) Views need to be made NORMATIVE, how to support Optional data, and how to support the required USER-DEFINED VIEWS.

  • Reported: UPDM 2.0 — Thu, 14 Jun 2012 04:00 GMT
  • Updated: Thu, 11 Apr 2024 13:10 GMT

PV1 (DoDAF) Attributes Needed

  • Key: UPDMRTF-9
  • Legacy Issue Number: 18509
  • Status: open  
  • Source: omg.org ( OMG System User)
  • Summary:

    In the current DoDAF Project Viewpoints (PV1) the project element has a start date and an end date. Those attributes are not sufficient for the US JCIDS process. In the incremental development process described by JCIDS, we have increments, blocks and spirals. In the main we don't measure our programs in absolute start and stop dates but rather where they fall in the relative JCIDS process, priority and lifecycle. Start dates are usefull but with a 20-30 year lifecylce, the stop date is not as useful. Having these attributes (increment:string, block: int and spiral:int) in the Project Element would allow us to trace requirements and capability sets to the proper increment, block or spiral.

  • Reported: UPDM 2.0.1 — Wed, 27 Feb 2013 05:00 GMT
  • Updated: Thu, 11 Apr 2024 13:10 GMT