You are on page 1of 25

Integrating TOGAF, Zachman and DoDAF Into A Common Process

Rolf Siegers Senior Principal Software Systems Engineer November 2003

Customer Success Is Our Mission

Topics
• • • • •
Definitions Why Architecture? Building Blocks of an Architecture Process Unifying the Standards Summary

strategies.Definitions • Architecture – “The fundamental organization of a system embodied in its components. their relationships to each other and to the environment. and the principles guiding its design and evolution. business processes. goals. applications and technical components • Enterprise Architecture – A blueprint (set of models) that depicts how various business and technical elements work together as a whole • Enterprise – “e” – “E” : the highest level of a system or system of systems : a Department or Agency of the government . information flows. and the supporting organizational structure • Technical Architecture – Perspectives of the overall architecture reflecting the enterprise’s data. business drivers.” (IEEE 1471-2000) • Architecture Framework – A resource that guides the development or description of an architecture • Business Architecture – A perspective of the overall architecture reflecting enterprise mission.

Why Architecture? Customer Success Is Our Mission .

Why Architecture? • • • • • • Government Customer Expectations Industry Competition Academia Our Future .

ITMRA 1996) Defense Science studies of early 1990s 2003 2003 2002 2002 2001 2000 1999 1996. 1997 1996 .Why Architecture? – Government: Background • The US Government has clearly established their direction and expectation for how complex systems of the future will be developed and integrated… through architecture. • Spans all Departments and Agencies • Not the tech or process trend du jour – this is traceable back over a decade – Department of Defense Architecture Framework – Federal Enterprise Architecture Service Component & – – – – – – – – – Technical Reference Models Federal Enterprise Architecture Business Reference Model Federal/DoD Enterprise Architecture Certification Institute Federal Enterprise Architecture Program Management Office Treasury Enterprise Architecture Framework Federal Enterprise Architecture Framework C4ISR Architecture Framework Establishment of CIO Council by Executive Order 13011 Congressional acts (GPRA 1993. FASA 1994.

the data should also qualify for the FEA reference models.000 agency officials have attended seminars the office conducts on how to prepare business cases. and if components are collecting the data needed to meet DOD architecture requirements. Federal Computer Week. Government Computer News.‖ [Note: Article titles above are hyperlinks] . but developers of the framework have checked. [Mitre] said. single information system with an enterprise architecture called the Net-Centric Enterprise Service…[SAIC] last month received a $50 million. 4/7/03 – ―The message from the Office of Management and Budget to agency managers is loud and clear: No enterprise architecture. 3/31/03 – ―Agency spending on enterprise architectures is expected to increase to more than $1 billion this year according to OMB…‖ • Feds work on melding architectures. Federal Computer Week. 2/10/03 – ―The Defense framework is probably the farthest removed from the FEA.‖ • Architecture due diligence. Government Computer News. no funding. ‖ • Get down to business with an architecture.Why Architecture? – Government: Sound Bites • OMB: Business cases must relate to enterprise architectures for 2005. 4/4/03 – ―…the grid will be a globally connected. 5/22/03 – ―Agencies should include with their business case submissions a copy of their architecture framework and an explanation of how it relates to the federal blueprint…more than 2.‖ • DoD lays out enterprise architecture plans. Government Computer News. five-year contract from the Office of the Joint Chiefs of Staff to plan and develop the grid.

Why Architecture? – Government: Sound Bites – OMB looks to extend architecture to DOD.jhtml?articleID=6504197 .‖ If you only read one article on the importance of this topic.T. intelligence. Government Computer News.com/shared/printableArticle.informationweek. http://www. Nov 11 2002 One Nation. please read Information Week. Under I. 9/13/02 • ―The Office of Management and Budget is beginning to figure out how to integrate the federal enterprise architecture with the Defense Department and intelligence agencies systems.

Piecing The Puzzle Together: What’s Needed In An “Architecting Process”? • • • • • Architecting Method Architectural Products Product Formats Architecture Validation Collaboration METHOD C O L L A B O R A T I O N PRODUCTS FORMATS VALIDATION .

Building Blocks • • • • • Architecting Method Architectural Products Product Formats Architecture Validation Collaboration The Open Group Architecture Framework (TOGAF) Version 8.0 Enterprise Edition Architecture Development Method (ADM) .

Overlays can show cost. connectivity and information exchange needlines between nodes Information exchanged between nodes and the relevant attributes of that exchange Organizational. role. intended users. or other pertinent information One of the three products used to describe operational activity sequence and timing . Functions performed by systems and the information flow among system functions Mapping of systems back to operational capabilities or of system functions back to operational activities Provides details of systems data being exchanged between systems Performance characteristics of each system(s) hardware and software elements. or other relationships among organizations Operational Activities.identifies business process responses to events One of three products used to describe operational activity sequence and timing . analytical findings Data repository with definitions of all terms used in all products High-level graphical/ textual description of operational concept Operational nodes. can be designed to show relationships of interest.traces actions in a scenario or sequence of events and specifies timing of events Documentation of the data requirements and structural business process rules of the Operational View.g.Building Blocks (cont’d) Applicable View All Views All Views Framework Product AV-1 AV-2 OV-1 OV-2 Framework Product Name Overview and Summary Information Integrated Dictionary High-Level Operational Concept Graphic Operational Node Connectivity Description Operational Information Exchange Matrix Organizational Relationships Chart Operational Activity Model General Description Scope. for the appropriate timeframe(s) Planned incremental steps toward migrating a suite of systems to a more efficient suite. within an appropriate set of timeframes • • • • • Architecting Method Architectural Products Product Formats Architecture Validation Collaboration Operational Operational Operational Operational Operational OV-3 OV-4 OV-5 Operational OV-6a Operational Rules Model Operational OV-6b Operational State Transition Description Operational Event-Trace Description Logical Data Model Systems Interface Description Systems Communications Description Systems-Systems Matrix Operational OV-6c Operational Systems Systems Systems OV-7 SV-1 SV-2 SV-3 Systems Systems SV-4 SV-5 Systems Functionality Description Operational Activity to Systems Function Traceability Matrix Systems Data Exchange Matrix Systems Performance Parameters Matrix Systems Evolution Description Systems Technology Forecast Systems Rules Model Systems Systems Systems SV-6 SV-7 SV-8 Systems SV-9 Systems SV-10a Systems Systems SV-10b SV-10c Systems State Transition Description Systems Event-Trace Description Physical Schema Technical Standards Profile Technical Standards Forecast Systems Technical SV-11 TV-1 TV-2 The Department of Defense Architecture Framework (DoDAF) Final Draft Version 1. inputs and outputs.0 Technical . message formats. planned vs. e. physical schema Extraction of standards that apply to the given architecture Description of emerging standards that are expected to apply to the given architecture. within and between nodes Systems nodes and their related communications lay-downs Relationships among systems in a given architecture. environment depicted..System-specific refinements of critical sequences of events and the timing of these events Physical implementation of the information of the Logical Data Model. relationships among activities. existing interfaces.identifies business rules that constrain operation One of three products used to describe operational activity sequence and timing . and that will affect future development of the architecture One of three products used to describe systems activity sequence and timing—Constraints that are imposed on systems functionality due to some aspect of systems design or implementation One of three products used to describe systems activity sequence and timing—Responses of a system to events One of three products used to describe systems activity sequence and timing -. Identification of systems and system components and their interconnections.. e. performing nodes. operational activities performed at each node. file structures. or toward evolving a current system to a future implementation Emerging technologies and software/hardware products that are expected to be available in a given set of timeframes.g. etc. purpose. system-type interfaces.

Building Blocks (cont’d) • Architecting Method • Architectural Products – Supplementing the DoDAF • Product Formats • Architecture Validation • Collaboration The Zachman Framework For Enterprise Architecture .

Final Draft Version 1.0 • • • • • Architecting Method Architectural Products Product Formats Architecture Validation Collaboration • DoDAF Templates • Unified Modeling Language (UML) • Integrated Computer-Aided Manufacturing (ICAM) DEFinition (IDEF) .Building Blocks (cont’d) DoDAF.

g. Colored Petri Nets) University of Aarhus CS Department .Building Blocks (cont’d) • • • • • Architecting Method Architectural Products Product Formats Architecture Validation Collaboration Software Engineering Institute • Software Engineering Institute’s Architecture Tradeoff Analysis MethodSM • Quality Attribute Assessment Techniques (e..

Building Blocks (cont’d) • • • • • Architecting Method Architectural Products Product Formats Architecture Validation Collaboration .

existing interfaces. system-type interfaces. inputs and outputs.. physical schema Extraction of standards that apply to the given architecture Description of emerging standards that are expected to apply to the given architecture. and that will affect future development of the architecture Systems SV-9 Five Activities of Architecture Process Inter-Activity Iteration Intra-Activity Iteration Activity II Architecture Planning Systems SV-10a Systems Rules Model One of three products used to describe systems activity sequence and timing—Constraints that are imposed on systems functionality due to some aspect of systems design or implementation One of three products used to describe systems activity sequence and timing—Responses of a system to events Systems Systems SV-10b SV-10c Systems State Transition Description Systems Event-Trace Description Physical Schema Technical Standards Profile Technical Standards Forecast One of three products used to describe systems activity sequence and timing -. operational activities performed at each node.REAP: A Unification of Standards • Raytheon Enterprise Architecture Process (REAP) Applicable View All Views All Views Framework Product AV-1 AV-2 Framework Product Name Overview and Summary Information Integrated Dictionary High-Level Operational Concept Graphic Operational Node Connectivity Description Operational Information Exchange Matrix Organizational Relationships Chart Operational Activity Model General Description Scope. etc. file structures. e.identifies business process responses to events One of three products used to describe operational activity sequence and timing . purpose. connectivity and information exchange needlines between nodes Information exchanged between nodes and the relevant attributes of that exchange Organizational. or other relationships among organizations Operational Activities. e. within an appropriate set of timeframes Activity IV Technical Architecting Software Engineering Institute Activity III Business Architecting . environment depicted. analytical findings Data repository with definitions of all terms used in all products High-level graphical/ textual description of operational concept Operational nodes. relationships among activities. Overlays can show cost. or other pertinent information One of the three products used to describe operational activity sequence and timing . role. message formats..g. – I Enterprise Understanding – II Architecture Planning – III Business Architecting – IV Technical Architecting – V Architecture Validation Operational Operational OV-1 OV-2 Operational Operational Operational OV-3 OV-4 OV-5 Operational OV-6a Operational OV-6b Operational OV-6c Operational Systems Systems Systems OV-7 SV-1 SV-2 SV-3 Systems Systems Operational Rules Model Operational State Transition Description Operational Event-Trace Description Logical Data Model Systems Interface Description Systems Communications Description Systems-Systems Matrix Activity I Identification of systems and system components and their interconnections.identifies business rules that constrain operation One of three products used to describe operational activity sequence and timing .traces actions in a scenario or sequence of events and specifies timing of events Documentation of the data requirements and structural business process rules of the Operational View. can be designed to show relationships of interest. or toward evolving a current system to a future implementation Emerging technologies and software/hardware products that are expected to be available in a given set of timeframes. Functions performed by systems and the information flow among system functions Mapping of systems back to operational capabilities or of system functions back to operational activities Provides details of systems data being exchanged between systems SV-4 SV-5 Systems Functionality Description Operational Activity to Systems Function Traceability Matrix Systems Systems Systems SV-6 SV-7 SV-8 Activity V Architecture Validation Systems Evolution Description Systems Technology Forecast Systems Data Exchange Matrix Systems Performance Parameters Matrix Performance characteristics of each system(s) hardware and software elements. within and between nodes Enterprise Understanding Systems nodes and their related communications lay-downs Relationships among systems in a given architecture. performing nodes. for the appropriate timeframe(s) Planned incremental steps toward migrating a suite of systems to a more efficient suite.g. planned vs. intended users.System-specific refinements of critical sequences of events and the timing of these events Systems Technical Technical SV-11 TV-1 TV-2 Physical implementation of the information of the Logical Data Model.

and the problem space • Subprocesses – – – – Customer-focused architecting Requirements analysis Operational/Business analysis Quality attribute analysis • TOGAF Relationship – ADM: Phase A Activity I Enterprise Understanding • Inputs – Customer vision. & requirements documents – Domain expertise – Industry & government standards • Outputs – DoDAF AV-1. Overview & Summary Information – DoDAF AV-2. Technical Standards Profile . needs. High Level Operational Concept Graphic – DoDAF TV-1.Activity I: Enterprise Understanding • Goals – Set context for architecture and architecting activities – Common understanding with customer on the [E/e]nterprise. the architecting initiative. Integrated Data Dictionary – DoDAF OV-1.

AV-2. configuration & consolidation of architectural products Form/train Architecture Team • TOGAF Relationship – ADM: Preliminary Phase. & requirements documents – DoDAF AV-1. TV-1 – Quality attribute-based requirements • Outputs – Architecture principles – Architecture schedule – Enhanced DoDAF AV-1. Phase A Activity II Architecture Planning • Inputs – Customer vision. formats and – – – – – the supporting Zachman cells Define product relationships / dependencies Define schedule Select tool(s) Plan concordance. needs. OV-1.Activity II: Architecture Planning • Goal – Establish a plan for the upcoming architecting activities. Overview & Summary Information – Architecture engineering environment . the goals of the architecture and the architectural outputs • Subprocesses – Identify stakeholders – Define architecture principles – Identify architectural products.

OV-1 Architecture engineering environment . & • Outputs – Business/Mission Scenarios within DoDAF OV-5.Activity III: Business Architecting • Goal – Model the customer’s view • Subprocesses – Collect Zachman Framework ―primitives‖ for Row 2 • Produce mapping matrices as needed – Model Business/Mission Scenarios • TOGAF Relationship – ADM: Phase B Activity III Business Architecting • Inputs – Customer vision. AV-2. Operational Activity Model – Catalogued information from Zachman Framework Row 2 Cells – – – – requirements documents Domain expertise Architecture principles DoDAF AV-1. needs.

OV-1. needs. AV-2. & requirements documents – Domain expertise – Architecture principles – DoDAF AV-1. TV-1 (and its referenced standards) • Outputs – Architecture Baseline Package – Executable model . D Activity IV Technical Architecting • Inputs – Business Architecture – Customer vision.Activity IV: Technical Architecting • Goal – Produce the remaining architectural descriptions of the enterprise from a variety of views • Subprocesses – Develop/mature the defined DoDAF view products – Develop the defined additional architectural products – Ensure concordance between architectural products – Iteratively evolve an executable model • TOGAF Relationship – ADM: Phases C. OV-5.

Activity V: Architecture Validation • Goal – Ensure the architecture is ready to be implemented • Subprocesses – Architecture checklist – ATAMSM – Quality attribute assessments Activity V Architecture Validation • Inputs – Architecture Baseline Package – Executable model • Outputs – Completed architecture checklist – Simulation results – SEI’s Architecture Tradeoff Analysis Method results – Validated architecture SM .

0 for Systems Engineering OMB’s Federal Enterprise Architecture Reference Models CMMI and IEEE-1471 Mappings Standardized supplemental views Agile Modeling Open Systems Architectures Certification Programs .Other Analysis Efforts • • • • • • • • • Enterprise Architecting Tools Object Management Group’s Model-Driven Architecture UML 2.

strategic goals.Summary • There are established industry and government standards to help us address enterprise-wide architectural alignment between customer mission. application systems. data. Unification is necessary to complete the picture. and technology. business rules. • No one standard or framework addresses all the aspects of the architecting process. . organization.

Questions? Rolf Siegers Raytheon Intelligence and Information Systems Garland.5169 Customer Success Is Our Mission .com 972. Texas rolf_siegers@raytheon.205.

0 – http://www.defenselink.sei.com • Software Engineering Institute’s Architecture Evaluations – http://www. Version 1. but no formal release statement has been issued yet) • Zachman Framework for Enterprise Architecture – http://www.com – http://www.Reference Links • The Open Group Architecture Framework. Version 2. final draft is currently out.mil/nii/org/cio/i3/AWG_Digital_Library/index.0 – http://www.zachmaninternational. Version 8.0 – (intermittent drafts appears on Mitre’s web site.org/architecture/togaf8/index8.htm • Department of Defense Architecture Framework.html .edu/ata/ata_eval.htm • C4ISR Architecture Framework.opengroup.cmu.zifa.