179:
endorsed by DoD and MOD because it was tied to an obsolete version of the DoDAF (DoDAF 1.0) and did not adequately meet DODAF 1.5 or MODAF 1.2 requirements. The OMG Technology
Adoption Process specifically prohibits the kind of scope creep that would have resulted in trying to extend the RFP requirements to address the then current versions of the architecture frameworks. Therefore, the FTF report was not accepted by OMG and an alternative path for creating the specification was followed.
183:
the comment period, a vote to accept the specification is conducted. If accepted, the delivered specification then enters the same finalization process as an RFP-based submission. Immediately following the rejection of the original UPDM FTF Report, a group identified as the UPDM Group was formed. The result of their efforts was an RFC submission in
September 2008 that was accepted by the Domain Technology Committee in December 2008, at which time a new UPDM FTF was chartered.
117:. This request was based on the then current versions of DoDAF (1.0) and MODAF (1.1). While the specification submission development was underway, significant changes were made to the DoDAF and MODAF. Therefore, although a UPDM 1.0 beta 1 specification was adopted by the OMG in 2007, and UPDM 1.0 beta 2 was submitted by an OMG Finalization Task Force in 2008, UPDM 1.0 beta 2 has not been endorsed by the US Department of Defense or the UK Ministry of Defence (MOD).
25:
191:
DoDAF and MODAF are under configuration control, with new versions being released as the user requirement evolves, and therefore the UPDM will evolve to enable accurate modeling of the changes. One intended improvement is a move to align the meta-models of the two frameworks. As of
September 2008,
182:
The OMG Technology
Adaption Process includes an alternative to the RFP-based process called the Request for Comment (RFC). In this process, a completed specification is delivered to the applicable OMG Technology Committee. OMG members are then given time to comment on the specification. Following
178:
In 2007, the OMG organized a
Finalization Task Force (FTF) to finalize the Unified Proposal (a.k.a. UPDM 1.0 beta 1) so that it could be made into a publicly available specification. The UPDM FTF submitted UPDM 1.0 beta 2 to the OMG in March 2008. The UPDM FTF's March finalization report was not
142:
is not suitable for use in DoDAF tools. Differences in vendor implementations have resulted in interoperability issues between tools and additional training requirements for users. Also, the current DoDAF UML implementation guidance is based on a previous version of UML (UML v1.x), and doesn't
174:
The OMG Technology
Adoption Process includes issuing an RFP, responses to that RFP called submissions, resolution of differences between submissions, acceptance of the final submission, and the chartering of a Finalization Task Force that refines the submission into a specification. Competing
150:
Modeling tool vendors are challenged to support a variety of DoDAF and MODAF adaptations, that have been created to meet the unique needs of several nationalities. For example, a UML Profile abstract syntax (extending the UML 2.1 meta-model) has been defined for MODAF to support
120:
The UPDM 1.0 specification, the result of additional work by many members of the original submission teams, is architecturally aligned with DoDAF 1.5 and MODAF 1.2. This version of the specification has been endorsed by both the US DoD and the UK
192:
the UPDM Group engaged with the DoD and MOD to participate in the improvement process. The UPDM Group has begun preparation for UPDM 2.0 with a focus on US DoDAF 2.0, Canada DNDAF, and other features.
155:-based file exchange between tools and repositories. But interoperability with DoDAF tools will be difficult because MODAF made significant changes to some DoDAF products and adds two new viewpoints.
138:. MODAF also provides similar guidance, and its meta-model is specified as a UML profile abstract syntax (i.e. extensions of UML 2.1 metaclasses). MODAF differs from DoDAF however, so the
175:
proposals were submitted to the OMG to satisfy the UPDM RFP., resulting in a
Unified Proposal in March 2007. The Unified Proposal included support for SysML as well as UML.
203:
90:
94:
158:
In addition to supporting DoDAF and MODAF requirements, UPDM is expected to be able to support other frameworks as well, such as the
46:
33:
329:
Information resource dedicated to UPDM as it relates to other architecture frameworks (e.g., DoDAF, MODAF, TOGAF, Zachman).
366:
361:
64:
371:
101:
Profile for DoDAF and MODAF was based on earlier work with the same acronym and a slightly different name - the
163:
135:
213:
152:
126:
The UPDM 2.0 specification was released in
January 2013, and UPDM 2.1 was released in August 2013.
122:
86:
114:
134:
DoDAF v1.5 Volume II includes guidance for representing DoDAF architecture products using
8:
326:
269:
295:
281:
139:
42:
355:
257:"About the Unified Profile for DoDAF and MODAF Specification Version 2.1.1"
233:
89:(OMG) initiative to develop a modeling standard that supports both the USA
244:
340:
336:- Industry consortium group focused on improving the UPDM specification.
200:
OMG Unified
Architecture Framework (UAF) is effectively replacing UPDM.
309:
129:
333:
256:
169:
144:
159:
113:
The UPDM initiative began in 2005, when the OMG issued a
282:"Team Alpha Overview: OMG document syseng/06-09-04"
296:"Team One Overview: OMG document syseng/06-09-05"
353:
302:
147:profile for systems engineering applications.
130:Motivation for unified profile for DoDAF/MODAF
327:UPDM section of Architecture Framework Forum
170:OMG Adoption Process and DoD/MOD endorsement
166:which has an identical meta-model to MODAF.
91:Department of Defense Architecture Framework
143:address the current version (v2.x) or the
95:Ministry of Defence Architecture Framework
65:Learn how and when to remove this message
274:
354:
288:
195:
18:
343:atthew Hause's Presentation on UPDM
13:
16:Product of Object Management Group
14:
383:
320:
97:(MODAF). The current UPDM - the
23:
270:OMG Technology Adoption Process
79:Unified Profile for DoDAF/MODAF
263:
249:
238:
227:
186:
1:
220:
105:Profile for DoDAF and MODAF.
7:
207:
10:
388:
108:
367:Systems Modeling Language
362:Unified Modeling Language
214:Model Driven Engineering
37:may need to be rewritten
372:Enterprise architecture
347:from Integrated EA 2010
162:Architecture Framework
87:Object Management Group
85:) is the product of an
234:Request for Proposal
115:Request for Proposal
93:(DoDAF) and the UK
310:"Unified Proposal"
245:UPDM Group members
196:Transition to UAF
75:
74:
67:
47:lead layout guide
379:
314:
313:
306:
300:
299:
292:
286:
285:
278:
272:
267:
261:
260:
253:
247:
242:
236:
231:
140:MODAF Meta-Model
70:
63:
59:
56:
50:
43:improve the lead
27:
26:
19:
387:
386:
382:
381:
380:
378:
377:
376:
352:
351:
323:
318:
317:
308:
307:
303:
294:
293:
289:
280:
279:
275:
268:
264:
255:
254:
250:
243:
239:
232:
228:
223:
210:
198:
189:
172:
132:
111:
71:
60:
54:
51:
40:
28:
24:
17:
12:
11:
5:
385:
375:
374:
369:
364:
350:
349:
338:
330:
322:
321:External links
319:
316:
315:
301:
287:
273:
262:
248:
237:
225:
224:
222:
219:
218:
217:
209:
206:
197:
194:
188:
185:
171:
168:
131:
128:
110:
107:
73:
72:
32:The article's
31:
29:
22:
15:
9:
6:
4:
3:
2:
384:
373:
370:
368:
365:
363:
360:
359:
357:
348:
345:
344:
339:
337:
335:
331:
328:
325:
324:
311:
305:
297:
291:
283:
277:
271:
266:
258:
252:
246:
241:
235:
230:
226:
215:
212:
211:
205:
204:
201:
193:
184:
180:
176:
167:
165:
161:
156:
154:
148:
146:
141:
137:
127:
124:
123:
118:
116:
106:
104:
100:
96:
92:
88:
84:
80:
69:
66:
58:
48:
45:and read the
44:
38:
35:
30:
21:
20:
346:
342:
332:
304:
290:
276:
265:
251:
240:
229:
202:
199:
190:
181:
177:
173:
157:
149:
133:
125:
119:
112:
102:
98:
82:
78:
76:
61:
52:
41:Please help
36:
34:lead section
187:Future work
356:Categories
334:UPDM Group
221:References
55:June 2022
208:See also
109:History
99:Unified
216:(MDE)
145:SysML
160:NATO
121:MOD.
83:UPDM
77:The
164:NAF
153:XMI
136:UML
103:UML
358::
341:M
312:.
298:.
284:.
259:.
81:(
68:)
62:(
57:)
53:(
49:.
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.