Unified Profile for DODAF/MODAF (UPDM) - ARCHIVE
(FOR HISTORICAL PURPOSES ONLY)
Refer to the following URL for
up-to-date information: http://www.updmgroup.org/index.htm
Newly Formed UPDM
Industry Group Announcement
Refer to
SE DSIG Minutes
from DC meeting March 11-12, 2008 for discussion on previous
UPDM effort.
BACKGROUND ON PREVIOUS UPDM TEAM
UPDM has been
adopted by the OMG.
The Beta UPDM Spec (dtc/07-08-02)
dated August 2007 is available from the OMG Site.
Refer to the minutes and presentations
from the
SE DSIG
Burlingame, Dec 11-12, 07 meeting for updates on
UPDM, DoDAF and MODAF.
UPDM INFORMATION SESSION FOR THE DoDAF V2.0 WORKING GROUP (May 16,
2007)
A UPDM Information Session was held on May 16, 2007 for the DoDAF v2.0
Working Group. The meeting was co-hosted by Brian Wilczynski from DoD
CIO/Architecture & Interoperability and Col. Jack Jibilian from SAF/Enterprise
Architecting and Warfighting Integration Decision and Support Division. Dr.
Fatma Dandashi from Mitre in Mclean Virginia,
coordinated the meeting and provided the facilities.
The purpose
of the session is to provide an opportunity for architects engaged in
architecture development using UML-based tools to:
1. Gain an
overview of the proposed specification and its role in architecture
development.
2. Discuss
issues and provide feedback to the UPDM submission team on the proposed
specification.
3. Discuss
opportunities for leveraging UPDM capabilities in DoDAF 2.0 and for
submission to the DISR as emerging standard for representing DoDAF compliant
architecture descriptions.
The presentations from the meeting are
included below.
Introduction - UPDM Review Session - Col. Jack Jibilian
UPDM Information Session - Brian Wilczynski
UPDM Submission Team Presentation - Lou Varveris (Telelogic), Fred
Mervine (IBM), David Fado (SAIC)
Links to UPDM
Specifications
INCOSE ARCHITECTURE WORKING GROUP REVIEW OF UPDM (April 16, 2007) - NEW
This evaluation entitled,
“A
Review of the Proposed UML Profile for the Department of Defense
Architecture Framework and Ministry of Defense Architecture Framework (UPDM)”
was conducted by the INCOSE Architecture Working Group (AWG). The review was
led by the AWG co-chair, Professor Dimitri Mavris of the Georgia Institute
of Technology.
REVISED UPDM SUBMISSION (March 27, 2007) - NEW
The UML Profile for
DoDAF/MODAF (UPDM) is intended to provide a standard approach for modeling
system of systems and enterprise architectures in support of the Department
of Defense Architecture Framework (DoDAF) and the UK Ministry of Defense
Architecture Framework (MODAF). The goals are to improve interoperability of
architecture data among architecture modeling tools, enhance reuse of
architecture data, and improve communication among DoDAF and MODAF
stakeholders.
At
the last OMG meeting in December 2006, two submission teams presented their
revised submissions to the OMG. Since then, the two submission teams have
merged their efforts into a single unified UPDM Submission Team. At the San
Diego OMG meeting on March 27, 2007, the unified submission was presented to
the joint C4I DTF/SEDSIG. The Team described how their approach integrates
key features from both of the previous submissions. The specification
includes compliance levels that support both a UML and SysML based
implementation. It also includes non-normative extensions that can support
BPMN and IDEF0. This submission represents a key milestone in the
development of the UPDM specification which is expected to begin the vote
for adoption at the next OMG meeting in June, 2007.
New: Refer to DoDAF V1.5 below under References.
Revised Submission
Presentation
Revised UPDM Specification
Presentation to the INCOSE Architecture Working Group
UPDM
Presentation to INCOSE Architecture Working Group by Dwayne Hardy (January
30, 2007)
Architecture Information Session on UPDM (December 6, 2006 OMG
meeting)
The OMG sponsored the
UPDM Information Day on December 6, 2006 to increase awareness of this
initiative across industry. The event included presentations by Brian
Wilczynski representing DoD CIO/ASD NII on the “Evolution of DoDAF in
Support of Net-Centricity”, Major Bryan Canter from U.S. Army TRADOC on
“Using the UML and Object Oriented Methodology to Develop Operational
Architectures for the Warfighter”, and Simon Davis presenting for Ian Bailey
and Jon Keefe as representatives for the UK Ministry of Defense on “MODAF
and UPDM” and the need to support Architectures for Net Enabled
Capabilities. These presentations are included below. In addition, the UPDM
Submission teams gave an overview of their approach. The background
information for the event is provided at:
http://www.omg.org/news/meetings/tc/UML-DoDAF-MODAF-Information-Day.htm
REVISED SUBMISSIONS (presented to C4IDTF at DC meeting on December 7, 2006 OMG
meeting)
At the December OMG
meeting in Washington DC, the two submission teams (Alpha Team and Team 1)
submitted their revised submissions and presented their approach and status
to the C4I DTF. The Team 1 submission is based on UML only and the Alpha
Team submission is based on SysML. In addition, the Alpha Team has included
provisions for including optional compliance points for BPMN and IDEF0
representations. The Alpha Team requested a one meeting cycle extension to
March ’07 which was voted on and passed. Both teams have also agreed to
explore the possibility of merging their submissions into a single revised
submission.
STATUS UPDATE (presentated to C4IDTF at Anaheim meeting on September
27, 2006)
UPDM-TeamAlpha-Submission-Update-060927_Rev_E
UPDM-Team1-Submission-Update-060927
INITIAL SUBMISSIONS (presented to C4IDTF at Boston meeting on June 27, 2006)
http://www.omg.org/cgi-bin/doc?c4i/06-06-01 (ASMG)
http://www.omg.org/cgi-bin/doc?c4i/06-05-02 (UST joint submission team)
http://www.omg.org/cgi-bin/doc?c4i/06-05-03 (IBM)
http://www.omg.org/cgi-bin/doc?c4i/06-05-04 (Telelogic AB)
BACKGROUND PRESENTATION:
UML Profile for
DODAF-MODAF (June 24, 2005) - F. Dandashi
SE DSIG PRESENTATIONS:
SE DSIG April '06 Meeting
Presentations on UPDM
SE DSIG Feb '06 Meeting
Presentations on UPDM
SE DSIG Sept '05 Meeting
Presentations on UPDM
SE DSIG Feb '05 Meeting
Presentations on UPDM
RFP:
UML
Profile for DODAF/MODAF (UPDM) RFP dated Sept 16,
2005 (dtc//05-09012)
- RFP issued at OMG Technical Meeting in Atlanta
RFP SUMMARY:
Based on feedback and strong interest received from OMG
members, this RFP solicits proposals for a UML Profile for the Department of
Defense Architecture Framework (DODAF) products and views, supplemented by the additional
Acquisition and Strategic views as defined by the UK’s Ministry of Defence
Architecture Framework (MODAF).
Problem Statement:
DoDAF v1.0 Volume II [DoDAF] 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 UML v2.0. In addition, tool vendors are
challenged to support a variety of DoDAF adaptations, such as MODAF [MODAF],
that have been created to meet the unique needs of several nationalities.
For example, a UML metamodel is being defined for MODAF (see section 6.4.3)
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 TV-1, OV-1, OV-2, SV-1 and SV-2 products and adds two new
viewpoints. .
The absence of an industry standard makes it difficult to
build, reuse, merge, evolve, exchange or compare architecture models in a
collaborative manner. As a result, current DoDAF representations in UML do
not fully serve their intended purpose 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.
Scope of the RFP:
The scope of UPDM includes representations for modeling a
single architecture consisting of a system’s viewpoint (DoDAF Systems View)
along with associated systems implementation standards (DoDAF Technical
View) within the context of the business or enterprise viewpoint (DoDAF
Operational View). In addition, UPDM should allow the architecture model to
include representation of an enterprise capability and strategic intent (MODAF
Strategic Viewpoint)and the process steps associated with the procurement of
conformant systems (MODAF Acquisition Viewpoint). More details on the
specifics of each of these views and viewpoints are provided in the
references cited in Appendix B.
The intent is to use the UPDM to:
·
model architectures for a broad range of complex systems,
which may include hardware, software, data, personnel, and facility
elements;
·
model consistent architectures for system-of-systems down to
lower levels of design and implementation;
·
support the analysis, specification, design, and verification
of complex systems; and
·
improve the ability to exchange architecture information
amongst related tools that are UML based and tools that are based on other
standards (see section 6.4).
The profile should provide the modeling of operational
capabilities, services activities, nodes, system functions, ports,
protocols, interfaces, performance, and physical properties and units of
measure. In addition, the profile should allow for the modeling of related
architecture concepts such as DoD’s doctrine, organization, training,
materiel, leadership & education, personnel, and facilities (DOTMLPF) and
the equivalent UK Ministry of Defence Lines of Development elements.
References:
[DoDAF]
Department of Defense Architecture Framework
DoD Architecture Framework,
Version 1.5, 23 April 2007
Volume I:
Definitions and Guidelines <http://jitc.fhu.disa.mil/jitc_dri/pdfs/dodaf_v1v1.pdf>
Volume II: Product Descriptions <http://jitc.fhu.disa.mil/jitc_dri/pdfs/dodaf_v1v2.pdf>
Volume III: Architecture Data Description <http://jitc.fhu.disa.mil/jitc_dri/pdfs/dodaf_v1deskbook.pdf>
Previous Version
http://www.defenselink.mil/nii/doc/
http://www.defenselink.mil/nii/doc/DoDAF_v1_Volume_I.pdf
http://www.defenselink.mil/nii/doc/DoDAF_v1_Volume_II.pdf
http://www.defenselink.mil/nii/doc/DoDAF_v1_Deskbook.pdf
[IEEE 1471]
“Recommended Practice for Architectural Description of Software-Intensive
Systems,” IEEE, 2000
ISO Ballot
Version of 1471
[MODAF]
MOD Architectural Framework (MODAF)
MODAF Acquisition Deskbook v0.9, 29th July 2005
MODAF Customer 1 Deskbook Issue v0.9, 22nd July 2005
MODAF Customer 2 Deskbook v0.9, July 2005
http://www.modaf.com
[NATO]
NATO C3 System Architecture Framework (NAF), Version 2, NATO C3 BOARD
(AC/322), To Be Published
Object Management Group, Systems
Modeling Language (OMG SysML™)
Tailoring DODAF for SOA, Fatma Dandahsi, Huei-Wan Ang, 09 Aug 2006
NEW
Using Systems Engineering Standards in an Architecture Framework
Return to SE DSIG
|
