The document presents a comprehensive overview of the Unified Profile for DoDAF and MODAF (UPDM), detailing its role in architecture development across enterprise and systems engineering phases. It emphasizes viewpoint commonality, mapping relationships between different frameworks, and the integration of UPDM with SysML and UML for interoperability among various agencies. The document also outlines workflows and key relationships essential for effective architecture implementation and requirements management.

1. © Copyright IBM Corporation 2014
A pattern based approach to the development of
UPDM Architectures
Graham Bleakley Ph.D., IBM
graham.bleakley@uk.ibm.com

2. 2 © Copyright IBM Corporation 2014
Agenda
! This presentation will cover
! What is UPDM ?
! Viewpoint commonality
! Identify the main viewpoints relevant for the Enterprise Architecture and
Systems Engineering phases of development
! Show the patterns across the views and viewpoints
! Generic workflow
! Relating UPDM architectures to SysML and UML

3. 3 © Copyright IBM Corporation 2014
What is UPDM ?
! Unified Profile for DoDAF and MODAF
! It is not a new a framework
! It is the implementation in UML/SysML of the information model that
underpin DoDAF, MODAF and NAF
! The intent being to help interoperability between
! Architectures
! Government agencies
! Military agencies
! Customers and Suppliers
! Provides a common standard to express the architectures used in these
domains
! Relating Enterprise Architecture to Solution Architecture to
Systems Architecture to Software
! I am aware that it is not perfect !

4. 4 © Copyright IBM Corporation 2014
How does UPDM deal with commonality ?
! Uses a common core information model with some
specialisations for DoDAF and MODAF
! Approximately 90 % is core
! Provides a mapping table between elements for the different
frameworks
! Presentation layer is kept separate i.e. the views
! Provides a mapping between the common DoDAF, MODAF
and NAF views
! People get caught up with the names of the views
and elements rather than what they are trying to do
! They do not look behind the covers

5. 5 © Copyright IBM Corporation 2014
Viewpoint commonality
! Capability, Strategic Viewpoint:- Capture the capabilities that the enterprise is
expected to realise, defines them and shows how they are deployed to
organizations
! Operational Viewpoint:- Contains the views required to describe the
Operational, Organisational and high level functional aspects of the architecture
! Service (Orientated) Viewpoint:- Captures the views required to specify of the
Services (i.e. interface, no implementation) required to support the Operational
objectives of the architecture
Service (Orientated)Viewpoint
Operational Viewpoint
Capability Viewpoint (DoDAF,NAF)
Stategic Viewpoint (MODAF)

6. 6 © Copyright IBM Corporation 2014
Viewpoint commonality
! Systems Viewpoint:-Captures the specification of the Systems that are
required to be implemented or that already exist that help achieve the
operational objectives
! Project, Programme and Acquisition Viewpoint:- Maps the enterprises to
the projects and organisations that will realise the capabilities through the
development of systems and services
System Viewpoint
Service (Orientated)Viewpoint
Operational Viewpoint
Project,Acquisition
ProgrammeViewpoint
(DoDAF,MODAF,NAF)
Capability Viewpoint (DoDAF,NAF)
Stategic Viewpoint (MODAF)

7. 7 © Copyright IBM Corporation 2014
Viewpoint commonality
! Technical/Standards Viewpoint:-Contains all the information relating to
the standards that constrain the other 3 viewpoints
! Data and Information Viewpoint:- Refactoring of views that already
existed, used to define data and information concepts used in the other
viewpoints
! All Viewpoint:- Contains the summary information about the architecture
being developed including the data dictionary
AllViewpoint
DataandInformation
Viewpoint(DoDAF,NAF)
Tehcnical/Standards
Viewpoint
System Viewpoint
Service (Orientated)Viewpoint
Operational Viewpoint
Project,Acquisition
ProgrammeViewpoint
(DoDAF,MODAF,NAF)
Capability Viewpoint (DoDAF,NAF)
Stategic Viewpoint (MODAF)

8. 8 © Copyright IBM Corporation 20148
Model Element interaction Across Views (NAF)
Separation of Elements and Views/Viewpoints
! Some elements seen in multiple views
! Some views ties the viewpoints together e.g. SV-5

9. 9 © Copyright IBM Corporation 2014
View and Viewpoint interrelationships (DODAF)
! The Viewpoints are not
independent and are heavily
interrelated
! Each face of Cube
represents a viewpoint
! Each window a separate view
or product
! Model Elements internal to
cube used by multiple views
! Views can act as
! Filters on the information
in the architecture (OV-3,
SV-5)
! Diagrams allowing you to
create the information
that populates the
architecture (SV-1, OV-2)
Capability Views
Operational Views
CV-2
CV-6
OV-5
OV-1
OV-2
OV-3

10. 10 © Copyright IBM Corporation 2014
Viewpoint
relationships
! These are AFs are a set
of traceability matrices
! Systems and Services
support and implement
Operational elements
! Services expose
capabilities (service as
an interface)
! Operational elements
(activities) map to
capabilities
! Capabilities are
delivered by Projects
! Systems and Services
are the realized by
projects
! Everything constrained
by standards
! These relationships are
captured in the various
matrix views
All Viewpoint, encompasses summary information
and all data definitions in the architecture
Strategic/
Capability
Viewpoint
Data and Information Viewpoint, captures
data models at different level of abstraction
Systems
Viewpoint
Service
(Orientated)
Viewpoint
Operational
Viewpoint
Project/
Program/
Acquisition
Viewpoint
Exposes
Implements
Supports
Maps to
Delivered by
Technical/StandardsViewpoint
Constrained by
Implemented
by

11. 11 © Copyright IBM Corporation 2014
Systems Engineering and Architecture
Harmonization and Efficiency
System
O
&
M
System
Valida0on
System
Verifica0on
Subsystem
Verifica0on
Component
Verifica0on
Component
Design
System
Design
Prototyping
MSA
CBA
Valida0on
&
Verifica0on
Build
Acquisi0on
Model
Decisions
&
Milestones
CMMI
Process
Areas
Requirements
Development
(RD)
Requirements
Management
(REQM
Technical
Solu0on
(TS)
Product
Integra0on
(PI)
Verifica0on
(VER)
Valida0on
(VAL)
TEMPcapabili0es
TEMPopera0onal
TEMPsystem
StdV
AV
CV
DIV1
OV
DIV2
DIV3
StdV
DIV2
Unit
Test
SwDD;
IDD;
DBDD
SvcV
SV
SvcV
SV
SwRS;
IRS
SDD
RD
REQM
TS
VER
VAL
PI
MS-­‐A
SRR
SFR
MS-­‐B
CDR
TRR
SVR
MS-­‐C
Typical
Systems
Engineering
Work
Products
• System
Requirements
Document
(SRD)
/
Technical
Requirements
Document
(TRD)
/
System
Segment
Specifica0on
(SSS)
• System
Design
Document
(SDD)
/
System
Segment
Design
Document
(SSDD)
• SoVware
Requirements
Specifica0on
(SwRS)
• SoVware
Design
Document
(SwDD)
• Interface
Requirements
Specifica0on
(IRS)
• Interface
Control
Document
(ICD)
/
Interface
Design
Document
(IDD)
• Data
Base
Design
Document
(DBDD)
• Test
and
Evalua0on
Master
Plan
(TEMP)
PDR
Technology
Development
(TD)
Engineering
&
Manufacturing
Development
(E&MD)
Capabili0es
Based
Assessment
(CBA)
Material
Solu0ons
Analysis
(MSA)
System
Engineering
Technical
Reviews
System
Requirements
Reviews
(SRR)
System
Func0onal
Reviews
(SFR)
Preliminary
Design
Reviews
(PDR)
Cri0cal
Design
Reviews
(CDR)
Test
Readiness
Review
(TRR)
System
Verifica0on
Review
(SVR)
DoDAF
Viewpoints
All
(AV)
Capabili0es
(CV)
Opera0onal
(OV)
Data
/
Informa0on
(DIV)
Systems
(SV)
Services
(SvcV)
Standards
(StdV)
JCIDS
Documents
Ini0al
Capabili0es
Doc
(ICD)
Capabili0es
Design
Doc
(CDD)
Capabili0es
Produc0on
Doc
(CPD)
Informa0on
Support
Plan
(ISP)
SRD
CDDfinal;
ISPfinal
CDDprelim;
ISPprelim
CPD
ICD
Notional Systems Development “V”
! Slide Courtesy DoD

12. 12 © Copyright IBM Corporation 2014
Enterprise Views
Used by
! Planning
! JCIDS
! Operations
! Portfolio management
For
! Capability
management
! Operations Planning
! Develop High level
requirements for
prime suppliers
Still need the
! All view,
! Standards view
! Parts of the Data and
Information view
All Viewpoint, encompasses summary information
and all data definitions in the architecture
Strategic/
Capability
Viewpoint
Data and Information Viewpoint, captures
data models at different level of abstraction
Systems
Viewpoint
Services
(Orientated)
Viewpoint
Operational
Viewpoint
Project/
Program/
Acquisition
Viewpoint
Exposes
Implements
Supports
Maps to
Delivered by
Technical/StandardsViewpoint
Constrained by
Implemented
by

13. 13 © Copyright IBM Corporation 2014
Solution Architecture
Systems Engineering
Views
Used by
! Portfolio management
! Operations planning
! Defense Acquisition
System
! Systems Engineering
teams
– In forces
– Primes/Tier ones
! Provides requirements
to engineering teams
Still need the
! All view,
! Standards view
! Parts of the Data and
Information view
All Viewpoint, encompasses summary information
and all data definitions in the architecture
Strategic/
Capability
Viewpoint
Data and Information Viewpoint, captures
data models at different level of abstraction
Systems
Viewpoint
Service
(Orientated)
Viewpoint
Operational
Viewpoint
Project/
Program/
Acquisition
Viewpoint
Exposes
Implements
Supports
Maps to
Delivered by
Technical/StandardsViewpoint
Constrained by
Implemented
by

14. 14 © Copyright IBM Corporation 2014
Key relationships for Systems Engineering
• Resources exchanged
through information and
data exchanges
! Resource is almost anything
in the architecture
EnterprisePhase
Service/
Service
Interface
Performer/Node
System/
Capability
Configuration
Activity
(System Function)
Activity
(Operational)
Capability
Resources
Activities
Performs
Produces/
Consumes
Performs
Exchanges
Exchanges
Implements
Supports
Trace to
Expose
Exhibits
Implement

15. 15 © Copyright IBM Corporation 2014
View Patterns in the Framework (DoDAF)
OV-5 SvcV-4SV-4
OV-3 SvcV-3/6SV-3/6
CV-6/7 SvcV-5aSV-5a/b
OV-6b SvcV-10bSV-10b
OV-6c SvcV-10cSV-10c
Capability
Operational Systems Services
OV-2 SvcV-1/2SV-1/2
Structure (definition, instance)
( BDDs & IBDs)
Behaviour
(activity diagrams)
Behaviour
(statemachines)
Behaviour
(sequence diagrams)
Data exchange Summaries
(Table/Matrix views)
Traceability matrices
Represented in UPDM
(using SysML) as

16. 16 © Copyright IBM Corporation 2014
View Patterns in the Framework (MODAF)
OV-5 SoV-5SV-4
OV-3 SV-3/6
StV-6 SoV-3SV-5a SV-12
OV-6b SoV-4bSV-10b
OV-6c SoV-4cSV-10c
Capability
Operational Systems Services
OV-2 SoV-1/2SV-1/2
Structure (definition, actual)
( BDDs & IBDs)
Behaviour
(activity diagrams)
Behaviour
(statemachines)
Behaviour
(sequence diagrams)
Data exchange Summaries
(Table/Matrix views)
Traceability matrices
Represented in UPDM
(using SysML) as

17. 17 © Copyright IBM Corporation 2014
Trace
matrices
Key View dependencies for systems engineering (DoDAF)
CV-4
CV-2
CV-1
Environment
SV-1/2
SV-4
SV-3/6
SV-10c
SV-5a/b
CV-7
SvcV-5
OV-2/4
OV-5
OV-3
OV-6c
SvcV-1
SvcV-3/6
SvcV-4SvcV-10c
• Solid arrows show
• Source where element is shown
• Target where the element is defined/referenced
from
• Dashed lines show trace references
• Traceability matrices CV-6, CV-7,
SV-5a/b, SvcV 5
• Structure OV-2, SV-1, SVCV-1
• Behaviour OV-5,SV-4,ScvV-4
• Sequence Diagrams, OV6,
SV-10c,SvcV-10c
• Info exchanges
OV-3,SV-3/6,SvcV-3/6
CV-6

18. 18 © Copyright IBM Corporation 2014
Trace
matrices
Key View dependencies for systems engineering (MODAF)
StV-4
StV-2
StV-1
Environment
SV-1/2
SV-4
SV-3/6
SV-10c
SV-5a/b
SoV-3
SV-12
OV-2/4
OV-5
OV-3
OV-6c
SoV-1
SoV-5SoV-4c
• Solid arrows show
• Source where element is shown
• Target where the element is defined/referenced
from
• Dashed lines show trace references
• Traceability matrices StV-6, SoV-3,
SV-5a/b, SV 12
• Structure OV-2, SV-1/2, SoV-1
• Behaviour OV-5,SV-4,SoV-5
• Sequence Diagrams, OV6,
SV-10c,SoV-4c
• Info exchanges OV-3,SV-3/6
StV-6

19. 19 © Copyright IBM Corporation 2014
High level workflow (core)
• Develop capability views
• Enterprise visions
• Capability hierarchy and
dependencies
• Develop Operational views
• Behavior, structure,
• Derive data exchange matrices
• Trace back to capabilities
• Develop systems/service
views
• Behavior, structure,
• Derive data exchange matrices
• Trace back
• Systems to operations that they
implement
• Trace back Services to the
• Operations they support
• Capabilities they expose
Develop Capability views, CV-2, CV-4. CV-1
Develop Operational views, OV-1,OV-5,OV-2,OV-4,OV-6s,OV-3
Trace back Activities (Operational) to Capabilities (CV-6)
Trace back Systems
and
Activities(SystemFuncti
ons) to Operational
Views (SV-5a/b)
Develop System View
SV-4s, SV-1/2, SV-3,
SV-6
Develop System View
ScvV-4s, ScvV-1,
Trace back
Activities(ServiceFuncti
ons) to Operational
Views (SvcV-5) and
Capabilities (CV-7)

20. 20 © Copyright IBM Corporation 2014
The generic workflow applied to the OVs
OV-6c
OV-5
OV-3
Step-1 BlackBox behavior
Step-2 Define Structure
Step-3 Allocate behavior
to structure (WhiteBox)
OV-2/4
Left off OV-1 as it is developed
differently in MODAF and DoDAF

21. 21 © Copyright IBM Corporation 2014
The generic workflow applied to the OVs
OV-6c
OV-5
OV-3
OV-2/4
Step-3 Allocate behaviour
to structure (WhiteBox)
Step-5 Define
Information
Exchanges
Step-4 Define Scenarios
Step-6 generate OV-3
Information exchange summary

22. 22 © Copyright IBM Corporation 2014
Architecture and
Implementation workflow
Test Scenarios
(Sub-)System
Integration & Test
(Sub-)System
Integration & Test
System
Acceptance
System
Acceptance
Module
Integration & Test
System
Analysis & Design
System
Analysis & Design
SW
Analysis & Design
SW
Analysis & Design
SW Implementation
& Unit Test
SW Implementation
& Unit Test
Software
Engineering
Systems
Engineering
Requirements
Analysis
Requirements
Analysis
Model/RequirementsRepository
System Architecture
Baseline
Implementers: Tier1/Tier2 Systems/Software Engineering
Systems
PV/Acv
Views
CV/StV
Views
Operational
Views
System
Views
Specifier:DoD/ MOD/Agencies/Tier 1
Actual Delivery Timescales
Expected
Delivery Timescales

23. 23 © Copyright IBM Corporation 2014
Relating UPDM and SysML models
! Handling requirements
! In UPDM requirements driven from the level above
! Non functional requirements captured as constraints
! Also work with Parametric diagrams
! Drive the trade-off decisions
! It is possible to bring requirements into UPDM models and tie them into any
of the levels
! Tend to treat the level above as requirements for the next level
down
! Loose coupling between the layers
! Single source of truth
! Use referenced models or link across architectures
! Can be supported by OSLC across different tools

24. 24 © Copyright IBM Corporation 2014
Relating UPDM and SysML models (simple example)
! Reference UPDM elements
from SysML models
! Maintain the consistency of the
UPDM model
! Maintain the patterns of the UPDM
structure in the SysML model
! Trace between SysML and UPDM
easily
! End up with a number of Branch
SysML models that reflect the lower
level system structure
! Cannot use the UPDM elements as
they are read only (Advantage)
SV-1/2
SV-4
(Activity)
SV-3/6
SV-10c
Sequence/State
machines
Activity
Tables/
matrix
views
BDDs/IBDs
UPDM
Systems
Reference
model
SysML
Systems
Model

25. 25 © Copyright IBM Corporation 2014
© Copyright IBM Corporation 2014. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind,
express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have
the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM
software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities
referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature
availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines
Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
www.ibm.com/software/rational

26. 26 © Copyright IBM Corporation 2014
Relating UPDM and SysML models
! Handling requirements
! In UPDM requirements driven from the level above
! Non functional requirements captured as constraints
! Also work with Parametric diagrams
! It is possible to bring requirements into UPDM models and tie them to
Capabilities
! 3 main options
! Keep SysML models as part of UPDM models
! Import parts of UPDM models directly into a SysML model
! Reference UPDM elements from SysML models
! Separate UPDM and SysML models and trace through using requirements
! Best option is single source of truth
! Use referenced models or link across architectures
! Can be supported by OLSC across different tools

27. 27 © Copyright IBM Corporation 2014
Viewpoint commonality
! Technical/Standards Viewpoint:-Contains all the information relating to
the standards that constrain the other 3 viewpoints
! Data and Information Viewpoint:- Refactoring of views that already
existed, used to define data and information concepts used in the other
viewpoints
! All Viewpoint:- Contains the summary information about the architecture
being developed including the data dictionary
AllViewpoint
DataandInformation
Viewpoint(DoDAF,NAF)
Tehcnical/Standards
Viewpoint
System Viewpoint
Service (Orientated)Viewpoint
Operational Viewpoint
Project,Acquisition
ProgrammeViewpoint
(DoDAF,MODAF,NAF)
Capability Viewpoint (DoDAF,NAF)
Stategic Viewpoint (MODAF)