IBM Podcast [ MUSIC ] MATHENY: Welcome to this IBM podcast. UPDM 2.0, a UML SysML implementation of DoDAF 2.0 and MODAF 1.2 for military architectures. I'm Angelique Matheny with IBM. Over the past few years, system architects have often used UML and SysML to capture various architectural frameworks. Without guidance of a well-defined standard, many of these attempts have resulted in ad hoc and one-time solutions. The unified profile for DoDAF and MODAF UPDM specifies a standard for using UML SysML for capturing MODAF DoDAF views. This podcast will help you understand how UPDM helps enable national and international interoperability interchange and a complete lifecycle from enterprise architecture through software architecture. And joining today's discussion is Graham Bleakley, Rational Solution architect for Aerospace and Defense. And Brian Nolan, Market Manager for Aerospace and Defense Rational Systems Marketing. Hi, Graham; hi, Brian. Welcome to the podcast. Thanks for joining us today. BLEAKLEY: Thank you. -1- NOLAN: Thanks very much Angelique. We're glad to be here. As the title says, the unified profile, or DoDAF and MODAF or UPDM, it's what we're here to talk about today. Graham, give us some context is a little bit more detail on what UPDM is. BLEAKLEY: Okay. As it shows in the box, UPDM is Unified Profile for MODAF and DoDAF. The idea has been that the way to interchange models or architectures between MODAF and DoDAF and this is something that is becoming much more common or a need that's becoming much more common given the international nature of a lot of program development in the military world. The other reason why UPDM was developed was that in previous versions of DoDAF, a lot of the tool vendors were building proprietary versions or proprietary protocols for MODAF and DoDAF. And because there was no formal [master] model behind DoDAF, the way that they were doing it, well, they were all slightly different and so there's no ability to interchange models between the different source. And also, there was no standard way to go about representing the different artifacts and how standard workloads about how my might be produced. So, UPDM is, to some degree, an architecture towards this. It certainly gives a standard -2- interchange and a standard format for representation of elements. NOLAN: Thank you Graham. So, DoDAF 1.0, 1.5, 2.0. Then, we have UPDM 1.0 and now 2.0. What has changed in DoDAF? And why has UPDM 2.0 come out so soon after UPDM 1.0? BLEAKLEY: That's a very good question, Brian. It goes back to versions of UPDM...I'm sorry. The versions of DoDAF that were around when UPDM was initially conceived. In this version, in UPDM 1, where you actually supported DoDAF 1.5 and MODAF 1.2. MODAF 1.5 had slightly operational views, system views, technical and the old views. But [also INAUDIBLE]. MODAF 1.2 added another couple of views onto this, and these were the strategic view and it allowed you to develop capability taxonomies and show how they related to organizations and how they could be deployed. And also, an acquisition view, which is about program and product management. This is what was happening in UPDM Version 1. At around the same time or shortly after UPDM 1 came out, DoDAF 2 came out. We couldn't sync up with it at that particular time. And so, UPDM 2 is a different kettle of fish to DoDAF 1.5 for a number of reasons. -3- One, it's based around something called IDEA and this needs to match into EML for UPDM, which is a task that we carried out. The other things is DoDAF 2 also had extra views involved with it. So, within DoDAF 2 now, we have a capability view, which is very similar to the strategic view in MODAF. And we also have a project view, which is similar to the acquisition view in MODAF. Because of this it means that we can do some work in UPDM 1 to help support DoDAF 2 users while UPDM 2 was being developed. And UPDM 2 should be or will be coming out very, very shortly. We're just going through the final stages, which is the OMG will go through its acceptance of the architectural board and it should be coming out as a standard very shortly. NOLAN: Okay. We forgot to mention in our introduction that Graham, you are on the OMG committee for UPDM. Is that correct? BLEAKLEY: Yes. I've been working on it for the past three years. I'm co-chair and one of the architects or lead architect for the architecture team that's been working on UPDM 2. NOLAN: Great. I wanted to get that in. It's important, in terms of the details that we're talking about. -4- And now, you and I have talked about what you just mentioned. One of the motivators for UPDM is to provide the interchangeability between models and tools and architecture. But there's another kind of interchangeability that we have talked about, in terms of in the defense community there's kind of an acquisition group who figures out where the capabilities are needed. And then, there's a group that, in essence, implements those capabilities. So, we've called that the upstream and downstream, in terms of enterprise architecture. How does UPDM and the Rational solutions help bridge what could be a gap between the upstream and downstream communities? BLEAKLEY: I think a lot of it has to do with the requirements of the needs of the different groups carrying out these tasks. Typically, within the upstream community, which is the high-level defense agencies or the high levels of those defense agencies, these tasks have particularly been carried out with system architect, and there's a DoDAF 2 implementation systems architect, so they can carry on working within that world. But typically what happens when we get down to the tier one and the systems integrated, they normally need a lot more -5- detail or they need to flesh out a lot more detail to their development to understand exactly what the agencies are requiring. So, taking it from an operational context down to a systems, or a systems of systems view is very important for these big defense contractors. And they typically take the vague ideas and concepts from the agencies and they start to flesh them out and put a lot more detail on to them. And this is what we mean by downstream engineering. The value that these people are getting from this is because UPDM is based upon a SysML, which is based upon a UML it means that they can transfer these models down the chain from UPDM through SysML and down to UML, where they can develop software. In terms of the integration between upstream and downstream, we can either link artifacts together through some of our Jazz technology or we can start to translate information from system architect down or transfer it into Rhapsody, depending upon what artifacts are available and what work needs to be done. NOLAN: The need really here, as I understand it, is for the ability to trace in essence from the very top levels of the concepts and the concepts of operations, perhaps that is defined at the top level of the community, down to the actual implementation how the architecture which lies -6- underneath that pulls it all together. That's what UPDM helps address. The tools that we have on the Jazz Platform really help make that traceability easier, right? BLEAKLEY: That's correct. I mean, we're not dealing with single models or big monolithic single models and repositories that exist in one space. We're talking about multiple models that live in the different spaces that can be joined up so that you can do traceability all the way down from high-level capabilities, down through the operational activities that start to realize, down to the systems that do realize all the services that are going to realize. And then, even further down to implementation software. NOLAN: So, conceptually UPDM will provide that framework from the very top to the very bottom, right? Without having to jump from one language to another. BLEAKLEY: Yes. It provides the missing glue that sits between what has typically been the agency space in the tier one systems integrators, which is where [INAUDIBLE] the proprietary tools. It's also worth mentioning that UPDM is really a practical and pragmatic approach to doing modeling with DoDAF 2.0. NOLAN: Right. Okay. Well, Graham, I think we've -7- covered what we wanted to cover. So, thanks very much. We have some information that Angelique is going to pass on to close this out. BLEAKLEY: Okay. Thank you very much, Brian. It was a pleasure talking to you. NOLAN: As always, pleasure talking to you Graham. MATHENY: Yes, Graham and Brian, thank you so much for sharing your time today. It was a great discussion to listen to, and we really appreciate it. That was IBM's Graham Bleakley and Brian Nolan discussing UPDM 2.0, a UML SysML implementation of DoDAF 2.0 and MODAF 1.2 for military architectures. To share this podcast with your colleagues or if you're interested in more podcasts like this one, check out the Rational Talks To You podcast page at www.ibm.com/rational/podcasts.