UPDM: Difference between revisions
m robot Adding: fr:UPDM |
Shiftmain7 (talk | contribs) redirected link |
||
| Line 1: | Line 1: | ||
== UML Profile for DoDAF/MODAF == |
== UML Profile for DoDAF/MODAF == |
||
The [[Unified Modeling Language|UML]] Profile for [[DoDAF]]/[[MODAF]] ('''UPDM''') provides an industry standard [[Unified Modeling Language|UML]] representation for DoDAF architecture products and MODAF views through the [[Object Management Group|OMG]] <ref>[http://syseng.omg.org/syseng_info.htm] OMGs [[System Engineering]] DSIG sponsoring group for UPDM</ref> standardization process based on a [[model-driven architecture]] (MDA) approach to specification. Refer to the UPDM site at http://syseng.omg.org/UPDM.htm for additional information. |
The [[Unified Modeling Language|UML]] Profile for [[DoDAF]]/[[MODAF]] ('''UPDM''') provides an industry standard [[Unified Modeling Language|UML]] representation for [[DoDAF architecture]] products and MODAF views through the [[Object Management Group|OMG]] <ref>[http://syseng.omg.org/syseng_info.htm] OMGs [[System Engineering]] DSIG sponsoring group for UPDM</ref> standardization process based on a [[model-driven architecture]] (MDA) approach to specification. Refer to the UPDM site at http://syseng.omg.org/UPDM.htm for additional information. |
||
Utilizing a common modeling language in support of the [[architecture framework]] will significantly enhance the quality, productivity, and effectiveness associated with architecture and system of systems modeling; improve tool interoperability and communications between stakeholders; and reduce re-training requirements for different tools and projects. |
Utilizing a common modeling language in support of the [[architecture framework]] will significantly enhance the quality, productivity, and effectiveness associated with architecture and system of systems modeling; improve tool interoperability and communications between stakeholders; and reduce re-training requirements for different tools and projects. |
||
Revision as of 04:31, 28 December 2007
UML Profile for DoDAF/MODAF
The UML Profile for DoDAF/MODAF (UPDM) provides an industry standard UML representation for DoDAF architecture products and MODAF views through the OMG [1] standardization process based on a model-driven architecture (MDA) approach to specification. Refer to the UPDM site at http://syseng.omg.org/UPDM.htm for additional information.
Utilizing a common modeling language in support of the architecture framework will significantly enhance the quality, productivity, and effectiveness associated with architecture and system of systems modeling; improve tool interoperability and communications between stakeholders; and reduce re-training requirements for different tools and projects.
DoDAF v1.0 Volume II includes guidance for representing DoDAF architecture products using UML. However, this guidance is not sufficiently precise or complete to ensure consistent and interoperable implementations by UML tool vendors and interpretations by architects and users of architecture models produced by these tools. Different vendor implementations result in interoperability issues between tools and impose additional training requirements for users. Also, the current DoDAF UML implementation guidance is based on a previous version of UML and does not take advantage of emerging support for system of systems modeling, which is based on SysML and UML v2.0.
In addition, tool vendors are challenged to support a variety of DoDAF adaptations, such as MODAF, that have been created to meet the unique needs of several nationalities. For example, a UML Profile abstract syntax (extends the UML 2.0 meta-model) has been defined for MODAF to support XMI-based file exchange between tools and repositories. But interoperability with DoDAF tools will be difficult because MODAF made some minor changes to DoDAF products and adds two new viewpoints.
An industry standard makes it feasible to build, reuse, merge, evolve, exchange or compare architecture models in a collaborative manner. UPDM intends to support communications among all stakeholders and facilitate architecture-based analyses. With growing interest in force planning for coalition operations, the ability to share and relate architecture information developed by different nations using an industry architecture framework standard is becoming increasingly important. UPDM will help improve this situation.
Proposed Solutions
Team Alpha [2]
This team, let by Telelogic, Raytheon, Lockheed Martin, Adaptive, Inc., Artisan Software, BAE Systems, No Magic, Sparx Systems, and Thales Group as well as other vendors and contractors is proposing a SysML-based solution that also incorporates some of BPDM where appropriate.
Team One [3]
This team, led by IBM, SAIC, CSCI, Northrop Grumman, EmbeddedPlus, as well as other vendors and contractors, is proposing a UML-based solution.
Unified Proposal [4]
Team Alpha and Team 1 submitted a unified proposal in March 2007. Two levels of compliance are proposed: they correspond to supporting a UML-based profile and a UML+OMG SysML™ profile.