EA Zone

EA Zone

Your source for architecture related materials and resources!


The EA Zone is an increasingly deep and rich body of free access to Enterprise Architecture links, glossary, papers, alumni symposium events, and other use resources. If you are a FEAC CEA or ACEA you already have access to the complete holdings.  If you are not a FEAC CEA or ACEA you can get access to a limited set of our holdings simply by registering on the site under the LOG IN tab at the top of the web page.  

We have arranged the holdings into three categories: Reports, Templates & Toolkits; Frameworks and Modeling Guidance; Links of Interest; and Podcasts. Use the links below to help you narrow your search for resources.  

 

 

BEA Architecture Product Guide

The BEA Architecture Product Guide (APG) was initially developed for the internal use of the architects, analysts and modelers on the BEA Development Team as a guide to describe the methods, rules, and modeling conventions to be used for the development of the models that comprise the Business Enterprise Architecture (BEA). The BEA is the enterprise level architecture for the Department of Defense (DoD) Business Mission Area (BMA) in support of the warfighter.

Although the APG is directed mainly to architectural models included in the DoD Architectural Framework (DoDAF), it also provides guidance and model descriptions for non-DoDAF models that are part of the BEA to help in understanding these models and their relationships to other DoDAF models.

Common Approach Document to Federal Enterprise Architecture

Framework and Modeling Guidance

This document provides guidance for a common approach to the practice of Enterprise Architecture (EA) throughout the Executive Branch of the U.S. Federal Government. Federal law and policy require Agency Heads to develop and maintain an agency-wide enterprise architecture that integrates strategic drivers, business requirements, and technology solutions.1 2 The Common Approach to Federal Enterprise Architecture promotes increased levels of mission effectiveness by standardizing the development and use of architectures within and between Federal Agencies.3 4 This includes principles for using EA to help agencies eliminate waste and duplication, increase shared services, close performance gaps, and promote engagement among government, industry, and citizens.

DoD Architecture Framework (DoDAF) Version 1.5 Volume 1

Framework and Modeling Guidance

DoD Architecture Framework (DoDAF) Version 1.5, 23 April 2007.

Volume 1: Definitions and Guidelines

Enterprise Architecture Statement of Work (SOW) Template

Reports, Templates & Toolkits

Here is a functional template in Microsoft Word to help you develop your Enterprise Architecture Statement of Work (SOW).

Federal Enterprise Architecture (FEA) Framework Version 2

Framework and Modeling Guidance

Enterprise Architecture (EA) supports planning and decision-making through documentation and information that provides an abstracted view of an enterprise at various levels of scope and detail. The Common Approach to Federal Enterprise Architecture, released in May 2012 as part of the federal CIO’s policy guidance and management tools for increasing shared approaches to IT service delivery, presents an overall approach to developing and using Enterprise Architecture in the Federal Government. The Common Approach promotes increased levels of mission effectiveness by standardizing the development and use of architectures within and between Federal Agencies. This includes principles for using EA to help agencies eliminate waste and duplication, increase shared services, close performance gaps, and promote engagement among government, industry, and citizens.

FIPS 183 IDEF0

Framework and Modeling Guidance

Federal Information Processing Standards Publications (FIPS PUBS) are issued by the National Institute of Standards and Technology after approval by the Secretary of Commerce pursuant to Section 111(d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235.

Name of Standard. Integration Definition for Function Modeling (IDEF0).

Category of Standard. Software Standard, Modeling Techniques.

FIPS 184 IDEF1X

Framework and Modeling Guidance

Federal Information Processing Standards Publications (FIPS PUBS) are issued by the National Institute of Standards and Technology after approval by the Secretary of Commerce pursuant to Section 111(d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235.

Name of Standard.  Integration Definition for Information Modeling (IDEF1X).

Category of Standard.  Software Standard, Modeling Techniques.

GAO Report: A Framework for Assessing and Improving Enterprise Architecture Management (V2.0)

Reports, Templates & Toolkits

This GAO Executive Guide, August 2010 for Organizational Transformation is a A Framework for Assessing and Improving Enterprise Architecture Management (Version 2.0).

Why GAO Did This Study:

Effective use of an enterprise architecture (EA) is a hallmark of successful organizations and an essential means to achieving a desired end: having operations and technology environments that maximize institutional mission performance and outcomes. Among other things, this includes realizing cost savings through consolidation and reuse of shared services and elimination of antiquated and redundant mission operations, enhancing information sharing through data standardization and system integration, and optimizing service delivery through streamlining and normalization of business processes and mission operations. Not using an EA can result in organizational operations and supporting technology infrastructures and systems that are duplicative, poorly integrated, unnecessarily costly to maintain and interface, and unable to respond quickly to shifting environmental factors.

To assist organizations in successfully developing, maintaining, and using an EA, GAO is issuing this major update to its Enterprise Architecture Management Maturity Framework. Its purpose is to provide a flexible benchmark against which to plan for and measure EA program maturity. To develop the update, GAO solicited comments from 27 federal departments and agencies, as well as representatives from the private sector, state governments, and academia, and it leveraged its prior experience in applying the framework.

 

GAO Report: Enterprise Architecture Value Needs to Be Measured and Reported

Reports, Templates & Toolkits

In this GAO report to Congressional Committees, September 2012 on Organizational Transformation, this report discusses the need for Enterprise Architecture value assessment through measurability and reporting.

Why GAO Did This Study:

According to OMB, the federal executive branch plans to spend at least $75 billion on information technology (IT) investments in fiscal year 2012. In response to a statute which mandates that GAO identify duplicative activities within federal agencies, GAO previously identified enterprise architecture as a mechanism for reducing duplication and overlap in investments. An architecture is a “blueprint” that describes how an organization operates in terms of business processes and technology, how it intends to operate in the future, and how it plans to transition to the future state. Knowing whether architecture outcomes are being achieved requires defining the architecture’s goals, establishing a method and metrics to measure architecture outcomes, and periodically measuring and reporting these outcomes. To assess agencies’ use of architecture as a mechanism for reducing duplication and overlap, GAO committed to determine the extent to which agencies are measuring and reporting architecture outcomes and benefits. To do this, GAO reviewed relevant documentation from 27 major federal agencies, reviewed the results of a GAO survey on the benefits of using architecture, and interviewed agency officials.

What GAO Recommends:

GAO is making recommendations to the agencies and OMB to improve measurement and reporting of architecture outcomes. In commenting on a draft of this report, OMB and most of the agencies generally agreed with the findings and recommendations.

Guide to the Systems Engineering Body of Knowledge (SEBoK) v1.4

Reports, Templates & Toolkits

This new version features changes to respond to publication of ISO/IEC/IEEE. 15288:2015 Systems and Software Engineering - System Life Cycle Processes and the INCOSE SE Handbook v4.0, 2015. Over the last 12 months the BKCASE Editorial Board has made significant efforts to become more involved in activities within our sponsoring organizations on key topics such as model based systems engineering (MBSE), systems of systems, systems engineering leadership, etc. You will begin to see the impact of this in v1.4 of the SEBoK, with further updates in v. 1.5, planned for Autumn 2015.

John Zachman 2017 Interview

Podcasts

Cort Coghill of The FEAC Institute Interviews John Zachman, author of The Zachman Framework and Founder of Zachman International.

Selected Agencies’ Experiences Illustrate Good Practices in Managing Risk

Reports, Templates & Toolkits

In this GAO Report to the Committee on Oversight and Government Reform, House of Representatives, December 2016, they look at Enterprise Risk Management.

Why GAO Did This Study:

Federal leaders are responsible for managing complex and risky missions. ERM is a way to assist agencies with managing risk across the organization. In July 2016, the Office of Management and Budget (OMB) issued an updated circular requiring federal agencies to implement ERM to ensure federal managers are effectively managing risks that could affect the achievement of agency strategic objectives.

GAO’s objectives were to (1) update its risk management framework to more fully include evolving requirements and essential elements for federal enterprise risk management, and (2) identify good practices that selected agencies have taken that illustrate those essential elements.

GAO reviewed literature to identify good ERM practices that generally aligned with the essential elements and validated these with subject matter specialists.

GAO also interviewed officials representing the 24 Chief Financial Officer (CFO) Act agencies about ERM activities and reviewed documentation where available to corroborate officials’ statements. GAO studied agencies’ practices using ERM and selected examples that best illustrated the essential elements and good practices of ERM.

GAO provided a draft of this report to OMB and the 24 CFO Act agencies for review and comment. OMB generally agreed with the report. Of the CFO act agencies, 12 provided technical comments, which GAO included as appropriate; the others did not provide any comments.