Avancier Copyright Avancier Limited 2013 Avancier Methods (AM) EA framework history You may show this slide show provided you commend avancier.website to your audience
Avancier
Copyright Avancier Limited 2013
Avancier Methods (AM) EA framework history
You may show this slide show
provided you commend avancier.website to your audience
Avancier Around 1980
► The aim was to align information systems with business needs.
► The focus was planning how best to support business roles and
processes with information systems.
► To begin with, there was no network - only an enterprise mainframe
no business people ever saw.
► Nevertheless ,the term EA referred to a holistic enterprise-level,
enterprise-wide view of business processes and information
Copyright Avancier Limited 2013
Data
Avancier EA development has continued into the 21 century
20th century sources
► Business Systems Planning , IBM
► PRISM paper
► The Zachman Framework
► EA Model, NIST
► EA Planning, Spewak
► IT Management Reform Act (Clinger Cohen Act)
21st century sources
► Federal EA Framework, Federal CIO council
► Enterprise edition of TOGAF, The Open Group
► Integrated Architecture Framework (IAF), Cap Gemini
► “EA as Strategy”, Ross, Weill and Robertson
► Avancier Methods, Avancier Ltd
► E&SA reference model, The British Computer Society
Copyright Avancier Limited 2013
► Other sources
■ Hierarchical, Input, Process, Output (HIPO)
■ Structured Analysis and Design Technique (SADT)
■ Integration Definition Language (IDEF)
Avancier
Copyright Avancier Limited 2013
In 1980: Business System Planning
► a method for analyzing and designing
► an organisation’s information architecture
► goals:
■ understand the issues and opportunities with the current applications and
technical architecture
■ develop a future state and migration path for the technology that supports
the enterprise
■ provide business executives with a direction and decision making framework
for IT capital expenditures
■ provide information system (IS) with a blueprint for development
(After Wikipedia and Robinson College of Business, Georgia State University.)
Zachman sought (1982) to raise it to the “enterprise level”.
Data
Avancier
Copyright Avancier Limited 2013
The process in BSP - for study and presentation of plan
► 1 Preparation ■ 1.1 Obtain authorization for the study
■ 1.2 Study preparation
■ 1.3 Study beginning
► 2 Analytical ■ 2.1 Define the business strategy
■ 2.2 Define the business processes
■ 2.3 Define the data classes
■ 2.4 Analyse current information support
■ 2.5 Discuss the analysis results with management
■ 2.6 Issue the analysis results
► 3 Final part ■ 3.1 Define the information architecture
■ 3.2 Establish priorities for IS development
■ 3.3 Verify the impact of study to IS managing
■ 3.4 Next procedure proposal
■ 3.5 Results presentation
■ 3.6 Next procedure (implementation)
No mention of Technology
In 1980, the
mainframe was taken for granted.
Note business process-orientation.
Data
Avancier 1982 reference to EA by John Zachman of IBM
► "Although many popular information systems planning
■ methodologies,
■ design approaches, and
■ various tools and techniques
► do not preclude or are not inconsistent with enterprise-level
analysis,
► few of them explicitly address or attempt to define EAs.”
Copyright Avancier Limited 2013
Avancier
Copyright Avancier Limited 2013
c1985: "Information Engineering" (IE) James Martin and others.
► IE concepts and techniques (especially “structured analysis”) are
embedded in EA Frameworks
► Though the classic business function hierarchy is now called a
business capability map.
Product and service delivery
Manage and support the business
Vendor management Finance Business management Business support
Proposition management
Distribution and sales
Channel strategy
Panel management
Channel management
Lead management
Quotes and agreements to buy
On sell and retention
Sales performance management
Distribution support
Avancier
In 1986, the PRISM report
► “Dispersion and Interconnection: Approaches to Distributed
Systems Architecture”
► divided enterprise-level architecture into four architecture domains
► Organization ► The people and [business] structures that make it all work.
► Data ► The information assets of the organization [surely means the data processed by
application software]
► Application software ► The code which processes data for the organization, including acquired as well
as internally developed programs.
► Infrastructure ► The underlying technological platform which supports data and applications,
including hardware, systems software, and communications networks.
Copyright Avancier Limited 2013
Data
Avancier Also four architecture “types”
► “Principles
■ A statement of the organization's philosophy of information systems
expressed in terms of objectives and goals in each domain area
► Standards
■ Specific rules or guidelines for implementing the models [including
technology standards]
► Inventory
■ A snapshot of the current state showing the architectural items in place
today and their relationships [think baseline]
► Models
■ Pictures of the desired state, with emphasis on what goes where, and
how it is all connected [think target]”
Copyright Avancier Limited 2013
Avancier 1987 reference to EA by John Zachman of IBM
► “The cost and the success of the business
► depending increasingly on its information systems
► require a disciplined approach to the management of those systems.”
► “It is not hard to speculate about, if not realize, very large, very complex
systems implementations,
► extending in scope and complexity to encompass an entire
enterprise.”
Copyright Avancier Limited 2013
Avancier In 1989, The NIST Enterprise Architecture Model
► A five-layer reference model that
► illustrates the interrelationship of
■ business functions
■ information systems
■ platform technologies.
► promoted in U.S. federal gov.
Copyright Avancier Limited 2013
Stored data
I/O data flows
Avancier
In 1992, “Extending and formalising the information systems architecture framework” Sowa and Zachman
► proposed how to describe “the overall information system and how it
relates to the enterprise and its surrounding environment.”
► “a framework for information systems architecture (ISA) that has been
widely adopted by systems analysts and database designers.”
Copyright Avancier Limited 2013
Avancier In 1993, “EA Planning” by Stephen Spewak
► defined a data-centric architecture planning process
► “defining architectures for the use of information in support of the
business and the plan for implementing those architectures”.
Copyright Avancier Limited 2013
► EAP is “the process of defining architectures for the use of information in
support of the business and the plan for implementing those architectures”.
■ The business mission is the primary driver.
■ Then the data required to satisfy the mission,
■ Then the applications built to store and provide that data
■ Finally the technology to implement the applications.
► to improve data quality, access to data, adaptability to changing
requirements, data interoperability and sharing, and cost containment.” ► After Wikipedia
Data
Avancier
Copyright Avancier Limited 2013
The process in EAP (Spewak)
The first well-known process for
enterprise architecture.
1. Planning Initiation
2. Principles
3. Business Modelling
4. Current Systems & Technology
5. Data Architecture
6. Applications Architecture
7. Technology Architecture
8. Implementation/Migration Plans
9. Planning Conclusion
Stopped short of implementation
and change management.
Planning Initiation
Principles
Business Modelling
Current Systems &
Technology
Data Architecture
Apps Architecture
Implement. Migration
Plan
Planning Conclusion
Technology Architecture
Data
Avancier In 1996, The “IT Management Reform Act”
► This “Clinger Cohen Act”
► directed that a US federal government agency’s investment in IT
must be mapped to identifiable business benefits.
► made each federal agency’s CIO responsible for “developing,
maintaining and facilitating the implementation of a sound and
integrated IT architecture for the executive agency.”
Copyright Avancier Limited 2013
Avancier By 1997: Zachman had refocused his ISA framework as an EA framework.
► A classification scheme for artefacts: plans, technical details, lists,
charts and natural language statements.
► Describes the what, how, who, where, when and why of information
systems across the enterprise - at several levels of abstraction.
► Can be simply represented thus:
► Zachman has always said his framework is not a process
Copyright Avancier Limited 2013
Question
Stakeholder
What How Where Who When Why
Planner
Owner
Designer
Builder
Subcontractor
Operations
Abstraction
Avancier In 1998, The Federal CIO Council began developing FEAF
► “The architecture team generates
► a sequencing plan for the transition of
► systems, applications, and associated business practices
► predicated upon a detailed gap analysis [between baseline and target].”
► The Federal Enterprise Architecture Framework
► A process - reflecting priorities of the Clinger-Cohen Act 1. Initiate EA program
2. Define an Architecture Process & Approach
3. Develop the EA
4. Use the EA
5. Maintain the EA
■ Continuously Control & Oversee the EA Program
Copyright Avancier Limited 2013
Avancier
Establish Capability
Copyright Avancier Limited 2013
Define an Architecture Process & Approach Define the Intended Use of the Architecture Define the Scope of the Architecture Determine the Depth of the Architecture Select Appropriate EA Products Select Products that Represent the Business Select Products that Represent Technical Assets Evaluate & Select a Framework • Federal EA Framework • DoD CISR Architecture Framework • Treasury EA Framework Select an EA Toolset
Develop the EA (1) Collect Information Generate Products & Populate EA Repository Essentials in Building the Baseline Architecture Essentials in Building the Target Architecture Review, Validate, & Refine Models
Continuously Control & Oversee the EA Program Ensure Necessary EA Program Management Controls Are In
Place & Functioning Identify EA Program Expectations Not Being Met Take Appropriate Actions to Address Deviations Ensure Continuous Improvement
Develop the EA (2) Develop the Sequencing Plan Identify Gaps Define & Differentiate Legacy/Migration/New Systems Planning the Migration Approve
Maintain the EA Maintain the EA as the Enterprise Evolves Reassess the EA Periodically Manage Products to Reflect Reality Continue to Consider Proposals for EA Modifications
Initiate EA Program Obtain Executive Buy-in & Support Ensure Agency Head Buy-in & Support Issue an Executive EA Policy Obtain Support from Senior Exec. & Business Units Establish Management Structure & Control Establish a Technical Review Committee Establish a Capital Investment Council Establish an EA Exec. Steering Committee Appoint Chief Architect Establish an EA Program Management Office EA Program Activities & Products Develop EA Marketing Strategy & Communications Plan Develop an EA Program Management Plan Initiate Development of the EA
Federal Enterprise Architecture Framework (FEAF) - the process
Use the EA (2) Execute the Integrated Process Initiate New & Follow-on Projects Execute the Projects Complete the Project Other Uses of the EA Use the EA (1) Integrate the EA with CPIC & SLC Processes Train Personnel Establish Enforcement Processes & Procedures
Avancier 2001: FEAF: the US Chief CIO council
► “A practical guide to Federal Enterprise Architecture”, starts
► “An enterprise architecture (EA) establishes
► the Agency-wide roadmap to achieve
► an Agency’s mission through
► optimal performance of its core business processes within an
► efficient information technology (IT) environment.”
Copyright Avancier Limited 2013
Avancier 2003: Zachman listed 10 key points for EA, including
► “If it gets so complex that you can’t remember everything all at the same
time, you have to write it down (Architecture).
► Then, if you want to change it (whatever it is), you start with what you wrote
down (Architecture), the baseline for managing change.
► … The broader you define the analytical target, the better leverage you
are going to get on integration, reusability, interoperability, etc…
► If you draw the boundary more narrowly than your jurisdictional control, you will
disintegrate your Enterprise, that is, you will build a “legacy.”
► If you are not observing the engineering design principles…, you are not going
to realize the engineering design objectives of alignment, integration,
reusability, interoperability, flexibility, reduced time-to-market, etc., etc.
► … you are never going to appreciably reduce time-to-market until you have
something in inventory before you get the order.
► If you are not building (and storing, managing and changing) primitive
models, you are not doing Architecture. You are doing implementations.
Copyright Avancier Limited 2013
Avancier In 2006, "EA as Strategy” by Ross, Weill and Robertson
► "companies excel because they've [decided] which processes they
must execute well, and have implemented the IT systems to digitise
those processes."
► Work by MIT’s Center for Information System Research) led authors to
encourage enterprise architects to engage business managers using an
“operating model” to explore how far a business seeks integration and/or
standardisation of core processes.
Copyright Avancier Limited 2013
“Operating model” Integration and/or standardisation of core business processes
High integration Integrated Coordinated
Low integration Diversified Replicated
Low standardisation High standardisation
Avancier
Copyright Avancier Limited 2013
The process in “Enterprise Architecture as Strategy”
For ► “C-level executives determined to get IT right” ► delivering “a road map for the CIO and IT organisation to follow”. ► "improving strategy execution and lowering IT costs" and ► "creating a foundation for business execution”
The process
1. Analyse your foundation for execution 2. Define your Operating Model 3. Design your Enterprise Architecture 4. Set Priorities 5. Design and implement an IT Engagement Model 6. Exploit your foundation* for execution for growth
* Foundation = “an IT infrastructure and digitised processes that implement your
company's core capabilities.”
Explained in Practitioner-only
training
Avancier In 2011, TOGAF version 9.1
► published by The Open
Group as an Architecture
Framework that promotes
and encourages EA
► refers to operating model
concept from “EA as
Strategy”
► The core is a process, the
ADM
► For “transforming the
enterprise from a baseline
architecture to a target
architecture.”
Copyright Avancier Limited 2013
Explained in Intermediate
training
Govern
Plan
Initiate
Develop
Data
Avancier In the 21st century
► Aligning IT with business needs remains a primary aim of EA.
► A difference from 1980 is that IT is networked; so
■ employees carry devices and
■ customers connect from remote locations.
■ business managers have to worry more about availability and security of
business data.
► That doesn't mean EA has become IT centric
► EA is still about planning how best to support business roles and
processes with information systems.
► While recognising the business processes now depend on a more
pervasive, invasive and complex IS and IT estate.
Copyright Avancier Limited 2013
Avancier Cross-organisational aims of EA today
► To optimise business systems and increase agility
■ Tidy up the mess of duplicated and overlapping systems
by standardisation and integration.
► To help understanding and change impact analysis
■ Maintain an abstract description of business roles and
processes and the systems they use
► To minimise business risks and maximise
opportunities
■ Keep an eye on information system & technology
evolution, and produce road maps where needed
► To improve business systems,
■ Improve business data quality, relevance and use.
Copyright Avancier Limited 2013
“Operating model”
Integrated Coordinated Unified
Diversified Replicated
Standardised
““the EA is permanent and
manages the EA artefacts
delivered by projects.” TOGAF
Avancier Most modern EA frameworks share some premises
1. EA views the enterprise as a system, it is cross-organisational -
rather than localised.
2. EA is strategic and abstract – in comparison to more tactical and/or
concrete solution architecture.
3. EA joins up business, IS and IT domains – rather than addresses one
domain in isolation.
4. EA starts with the holistic view of a system, what services it delivers –
before how it is organised internally.
5. EA documents system descriptions, at least at an abstract level –
rather than leave systems undocumented.
Copyright Avancier Limited 2013
Avancier
Copyright Avancier Limited 2013
There are now countless EA frameworks
► Wikipedia lists some frameworks under these headings
■ Consortia-developed frameworks
■ Open-source frameworks
■ Proprietary frameworks
■ Defense industry frameworks
■ Government frameworks
► The list is only a fraction of what is out there
► Some are not really EA frameworks
► Some are out of date and/or not updated
Avancier
Copyright Avancier Limited 2013
A small fraction of EA framework history
US Federal Gov
Armed Forces
TAFIM
TOGAF v8
2003
FEA
MoDAF
NAF
(NATO)
DoDAF 1
2004
SAP
EAF
DoDAF
v2
Zachman
EAV3 20011
TOGAF
v9
AM
Introduced in the course.
See web site
Introduced in the course.
See web site
C41SR
1999
FEAF
1999
TOGAF v7
2001
Atos
BMS
SAM
(NCC)
JTA Standards
For acquisition
Of info systems
TOGAF v1
1995
CC Act
1996
EA Planning
Spewak
Zachman
ISAV1 1987
IDEF
POSIX
Catalyst
(CSC)
Information
Engineering
SSADM
Principles explained in the course
Introduced in the course
UPDM DoD
TRM
Avancier
Copyright Avancier Limited 2013
Among the frameworks
► TOGAF - The Open Group
► Avancier Methods (AM) – Avancier Ltd
► Zachman Framework – John Zachman
► Integrated Architecture Framework (IAF) – from CapGemini
► CLEAR Framework for Enterprise Architecture – Atos Origin
► Enterprise Architecture Framework - SAP
Avancier
Copyright Avancier Limited 2013
What does a modern EA framework contain? (ref. 14)
► PRODUCTS
■ Deliverables
● Documents, Reports
■ Artifacts (aka models)
● Lists, Matrices, Diagrams
■ Arch. Entities
● Architectural Entities (POLDAT etc.)
■ Taxonomies e.g.
● Zachman Framework
● Enterprise Continuum
► PEOPLE
■ Architect roles and responsibilities
■ Governance
► Guidance on
► PROCESSES
■ Initiate
■ Architect
■ Plan
■ Govern
Avancier HLD directs and constrains LLD
► Higher level designers direct and constrain lower level designers
■ They set targets that lower level designers must aim to reach.
■ They create abstract and idealised designs that lower level
designers must elaborate and realise.
■ They set general principles, patterns and standards that lower level
designers should apply in specific cases.
Copyright Avancier Limited 2013
Avancier
Copyright Avancier Limited 2013
Architecture processes feature several process threads
Higher level design (architecture) Design
dimension Lower level design
Long-term road maps Time horizon Shorter term sprints and deadlines
Broader goals, longer processes and
coarser-grained subsystems Decomposition
Narrower requirements, shorter
process steps and finer-grained
components
Behaviour (processes) Construction (ArchiMate)
Structure (components)
External (services delivered via interface) Realisation (ArchiMate & UML)
Internal structure (processes and
components)
Human needs and idealised descriptions Reification (Zachman)
Physical technology solutions
Generic principles, patterns, reference
models and standards Specialisation
Application of principles, patterns,
reference models and standards
Design process
Avancier In some or all of these ways
► Enterprise architects direct and constrain solution architects
► Solution architects direct and constrain software architects and
other technical specialists
► Software architects direct and constrain software developers
Copyright Avancier Limited 2013
Higher level design (architecture) Design dimension Lower level design
Long-term road maps Time horizon Shorter term sprints and deadlines
Broader goals, longer processes and coarser-grained
subsystems Decomposition
Narrower requirements, shorter process steps and
finer-grained components
Behaviour (processes) Construction
(ArchiMate) Structure (components)
External (services delivered via interface ) Realisation
(ArchiMate & UML) Internal structure (processes and components)
Human needs and idealised descriptions Reification
(Zachman) Physical technology solutions
Generic principles, patterns, reference models and
standards Specialisation
Application of principles, patterns, reference models
and standards
Avancier
Copyright Avancier Limited 2013
You need more than EA processes
An architecture process map
Enterprise architecture
“EA as Strategy”
TOGAF, Zachman
Change
management
Governance Solution architecture
Solution implementation
What you choose to do for cross-organisational
benefit
Avancier
Copyright Avancier Limited 2013
You need also Solution Architecture processes
An architecture process map
Enterprise architecture Change
management
Governance Solution architecture
Methods geared towards
Solution Architects and those
working for systems
integrators.
Avancier Methods
Solution implementation
What you have to do to define good
solutions
Initiate
Architect Manage
Plan
Govern Review initiation products
Design the target
Manage requirements
Manage business case
Plot migration path
Monitor the portfolio(s)
Establish directions....
Get vision approved
Govern migration/delivery
Complete delivery plan
Clarify NFRs
Chart road map
Scope the endeavour
Initiate (re)construction Manage readiness & risks
Avancier
Copyright Avancier Limited 2013
E.g. AM for SA (ref. 15)
Initiate
Architect Manage
Plan
Govern
Understand the baseline
Review initiation products
Design the target
Manage stakeholders
Manage requirements
Manage business case
Select suppliers
Plot migration path
Respond to oper'l change
Monitor the portfolio(s)
Establish directions....
Get vision approved
Govern migration/delivery
Complete delivery plan
Establish capability
Clarify NFRs
Chart road map
Scope the endeavour
Initiate (re)construction Manage readiness & risks
Avancier
Copyright Avancier Limited 2013
And solution implementation processes
An architecture process map
Enterprise architecture Change
management
Governance Solution architecture
Solution implementation
Waterfall, Iterative & Agile
What you have to do to deliver
solutions
Avancier The V Model (1980s) matches level of design to levels of testing
Validation
by inspection of design
www.msameer.info - by Mohammed Sameer
Verification
by testing of building
Copyright Avancier Limited 2013
Later, iterative (e.g. RUP) and
agile (e.g. SCRUM) methods
Avancier
Copyright Avancier Limited 2013
And processes to manage architecture
An architecture process map
Enterprise architecture Change
management
See chapter in
Practitioner
training manual
Governance See chapter in
Practitioner training manual
Solution architecture
Solution implementation
React to change
Monitor compliance
Avancier
Copyright Avancier Limited 2013
You have to stitch methods together
Operate Design Plan and Build
Building
Block
Transition
Architecture
Imp/Mig
Plan
*
* Work
Package
Project
Programme
[Portfolio]
*
*
* *
Capability
Increment
Capability
*
*
*
Capability
Dimension *
Capability-Based
Planning
Prog/Project
Management
ITSM
The ITIL (IT Infrastructure Library) is the
largest
(http://www.itil.co.uk)
Microsoft Operations Framework, or MOF
(www.microsoft.com)
COBIT (Control Objectives for Information
Technology;
www.isaca.org/cobit), and
Business Information Services Library, or
BISL
(www.bita-center.com/bisl2
Architecture
Method(s) ITSM
Processes
Avancier Enhancing TOGAF with Avancier Methods
TOGAF’s ADM is a management framework
that promotes the role of architects AM gives architects more specific processes
and documentation artefacts
A Architecture
Vision
Preliminary
E Opportunities And solutions
G Implementation
Governance
H Architecture
Change Management
B Business
Architecture
C IS
Architecture
D Technology Architecture
F Migration Planning
Copyright Avancier Limited 2013
Initiate
Architect Manage
Plan
Govern Understand the baseline
Review initiation products
Design the target
Manage stakeholders
Manage requirements
Manage business case
Select suppliers
Plot migration path
Respond to oper'l change
Monitor the portfolio(s)
Establish directions....
Get vision approved
Govern migration/delivery
Complete delivery plan
Establish capability
Clarify NFRs
Chart road map
Scope the endeavour
Initiate (re)construction Manage readiness & risks
Avancier
Copyright Avancier Limited 2013
Avancier Methods – architecture work space
Business view Information/data view Applications view Infrastructure Platform
view Enterprise/Business
Standardisation & integration
of business roles & processes
Business function/capability hierarchy
Business products & services catalogue
Business processes and roles
Etc.
Enterprise/Data
Data standardisation & integration
Data store & data flow catalogues
Maps data to business functions
Business data model & views of it
Canonical data model(s)
Core business data entity life cycles
Etc.
Enterprise/Apps
Business app standardisation &
integration
Business app portfolio/catalogue
Maps business apps to business functions
Business app life cycles and road maps
Etc.
Enterprise/Platform
Platform standardisation & integration
Platform technology portfolio/catalogue
Platform services portfolio/catalogue
(TRM)
Platform technology life cycles and road
maps
Etc.
Solution/Business
For a required system/solution:
Business services
Business processes and roles
Mappings to goals & locations
Requirements catalogues
Use case diagrams and definitions
Outline UI (or other I/O) designs
Etc.
Solution/Data
For a required system/solution:
Maps data to processes and roles
Logical data models
CIA requirements
Data qualities/meta data
Etc.
Solution/Apps
For a required system/solution:
Maps use cases to processes and roles
Maps business apps to use cases
Design for NFRs
Coarse-grained app components
Coarse-grained sequence diagrams
Etc.
Solution/Platform
For a required system/solution:
Maps platform to business apps
Platform technology definitions
Client & server node definitions
Design for NFRs
Outline deployment diagrams
Outline network diagrams
Etc.
Software/Business
Detailed use case definitions
Detailed UI designs
Governs UI implementation
Etc.
Software/Data
Detailed database design
Detailed message design
Governs database administration
Etc.
Software/Apps
Detailed (fine-grained) software design
Governs software development
Etc.
Software/Platform
Detailed deployment diagrams
Detailed network diagrams.
Governs platform and network
configuration
Etc.
EA joins up Business, IS and IT
Data
Avancier
Copyright Avancier Limited 2013
Methods and resources
► Avancier Methods
are useful with all
architecture
frameworks that share
similar ends and
means
► http://avancier.co.uk Avancier Methods
BCS E&SA reference model
TOGAF
The Open Group
IBM’s view EA
“EA as Strategy”
MIT authors
CSC’s domains of change (POLDAT)
ArchiMate
Language Framework
Avancier References
► See avancier.website for a list of references
Copyright Avancier Limited 2013
Avancier
Copyright Avancier Limited 2013
FYI only: Defense industry frameworks
► DoDAF – the US Department of Defense Architecture Framework
► MODAF – the UK Ministry of Defence Architecture Framework
► NAF – the NATO Architecture Framework
► AGATE – the France DGA Architecture Framework
► DNDAF – the DND/CF Architecture Framework (CAN)
C4ISR
Architecture
Framework
v1.0
C4ISR
Architecture
Framework
v2.0
DoDAF
v1.0
MODAF
v1.0
1996
1997
2003
2005
DoDAF
v1.5
2007
MODAF
v1.1
2007
NAF
v1.0
2005
Scope of “Unified
Profile for
DoDAF and
MODAF” (UPDM)
approved
Dec 2008
MODAF
Meta-Model (M3)
expressed using
UML Notation
MODAF
v1.2
2008
NAF
v3.0
2007