Systems Architecture & Design Lecture 3 Architecture Frameworks Brian E. White, Ph.D. 27 April 2010 Version 2 (v2) 1

Outline Department of Defense Architecture Framework (DoDAF) The Open Group Architecture Framework (TOGAF) The Zachman Framework Federal Enterprise Architecture (FEA) Reference Models What do you think is the underlying purpose behind all these frameworks and models?

DoD Architecture Framework One Architecture – Three Views Refer to Notes Page Operational View The Operational View (OV) describes and interrelates the operational elements, tasks and activities, and information flows required to accomplish mission operations. The Systems View (SV) describes and interrelates the existing or postulated technologies, systems, and other resources intended to support the operational requirements. Systems View The operational view (OV) is a description of the tasks and activities, operational elements, and information exchanges required to accomplish DoD missions. The systems view (SV) is a set of graphical and textual products that describes systems and interconnections providing for, or supporting, DoD functions. The technical [standards] view (TV) is the minimal set of rules governing the arrangement, interaction, and interdependence of system parts or elements. Each view is described through a set of “products”, i.e., diagrams, tables, graphics, and narratives. Each of the 26 products contains “data” that characterize some aspect of the architecture. Technical View The Technical View (TV) describes the profile of rules, standards, and conventions governing systems implementation and forecasts their future direction.

DoD Architecture Framework Products Refer to Notes Page OPERATIONAL (OV) 1: High-Level Operational Concept Graphic* 2: Operational Node Connectivity Description* 3: Operational Information Exchange Matrix* 4: Organizational Relationships Chart 5: Operational Activity Model* 6a: Operational Rules Model 6b: Operational State Transition Description 6c: Operational Event/Trace Description 7: Logical Data Model SYSTEMS (SV) 1: Systems Interface Description* 2: Systems Communications Desc.* 3: Systems-Systems Matrix 4: Systems Functionality Description 5: Operational Activity to System Function Traceability Matrix 6: Sys Data Exchange Matrix* 7: Sys Performance Parameters Matrix 8: Systems Evolution Description 9: Systems Technology Forecast 10a: Systems Rules Model 10b: Systems State Transition Desc. 10c: Systems Event/Trace Desc. 11: Physical Data Model TECHNICAL (TV) 1: Technical Standards Profile* 2: Technical Standards Forecast ALL (AV) Overview & Summary* Integrated Dictionary* The Products comprise 2 AVs, 9 OVs, 13 SVs, and 2 TVs. * Denotes critical products CADM: Core Architecture Data Model (common way of representing architectures) Spreadsheets Static Models & Graphics Text Dynamic Models

Remember our discussion of multiple perspectives during Lecture 1? Principles “Complete” architectural descriptions require multiple views, each of which conveys different architectural aspect DoDAF defines Operational Views (OVs) depict what is going on in the real world that is to be supported or enabled by systems represented in the architecture. Activities performed as parts of DoD missions and the associated information exchanges among personnel or organizations are the primary items modeled in operational views. The operational view reveals requirements for capabilities and interoperability. Systems Views (SVs) describe existing and future systems and physical interconnections that support the DoD needs documented in the OVs. Technical (Standards) Views (TVs) catalog standard (Commercial/ Government Off-the-Shelf [COTS/GOTS)] system parts or components and their interconnections. This view augments the SVs with technical detail and forecasts of standard technology evolution. All Views (AVs) augment the other views by providing context, summary or overview-level information, and an integrated dictionary to define terms. Remember our discussion of multiple perspectives during Lecture 1?

Organization DoDAF is organized into three volumes Volume I–Provides general guidance on need for and use of architecture descriptions in DoD contexts Volume II–Provides detailed definitions of 26 products contained in 3 types of views Operational, Systems, and Technical [Standards] (plus All) views Volume III (Deskbook)–Provides examples of compliant architectures, approaches to architecture development, and information on reference resources

The Three Views and Their Major Linkages

Systems View The SV Comprises set of graphical and textual products that describe systems and interconnections providing for, or supporting, DoD functions Includes both war fighting missions and business functions Associates systems resources to OVs. These support operational activities and facilitate exchange of information among operational nodes

System Views SV-1 Systems Interface Description Identification of systems nodes, systems, and system items and their interconnections, within and between nodes SV-2 Systems Communications Description Systems nodes, systems, and system items, and their related communications lay-downs SV-3 Systems-Systems Matrix Relationships among systems in a given architecture; can be designed to show relationships of interest, e.g., system-type interfaces, planned vs. existing interfaces, etc. SV-4 Systems Functionality Description Functions performed by systems and the system data flows among system functions SV-5 Operational Activity to Systems Function Traceability Matrix Mapping of systems back to capabilities or of system functions back to operational activities SV-6 Systems Data Exchange Matrix Provides details of system data elements being exchanged between systems and the attributes of that exchange SV-7 Systems Performance Parameters Matrix Performance characteristics of Systems View elements for the appropriate time frame(s) SV-8 Systems Evolution Description Planned incremental steps toward migrating a suite of systems to a more efficient suite, or toward evolving a current system to a future implementation SV-9 Systems Technology Forecast Emerging technologies and software/hardware products that are expected to be available in a given set of time frames and that will affect future development of the architecture SV-10a Systems Rules Model One of three products used to describe system functionality—identifies constraints that are imposed on systems functionality due to some aspect of systems design or implementation SV-10b Systems State Transition Description One of three products used to describe system functionality—identifies responses of a system to events SV-10c Systems Event-Trace Description One of three products used to describe system functionality—identifies system-specific refinements of critical sequences of events described in the Operational View SV-11 Physical Schema Physical implementation of the Logical Data Model entities, e.g., message formats, file structures, physical schema

SV-1 Systems Interface Description (1/3)

SV-3 Systems-Systems Matrix