| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Application-Reference-Model | Use of the Application Reference Model | Agencies must use the ARM to categorise systems, applications and related standards and technologies in the applications... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Applications | Summary of the application suite | The Roadmap must explain how current application artifacts support the information flows that program activities need, a... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Architecture-at-Various-Levels-of-Scope | Standard method, principles and artifacts for agency EA | Federal agencies should create and update architectures using the five-step method, the design principles, and the core... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Authoritative-Reference | EA as the authoritative design reference | Agencies should treat the enterprise architecture as the authoritative reference for designing and documenting systems a... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Authoritative-Reference-Verified-configuration | Verified configuration and continuous monitoring | Agencies should maintain an ongoing verified configuration covering infrastructure, hosts, systems, applications and wor... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-BASIC-ELEMENTS-OF-FEDERAL-ENTERPRISE-ARCHITECTURE | Eight required EA program elements | Every agency EA program must include all eight elements, from governance and principles through reporting and audit, and... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Business-Principles | Business services tied to strategy and security | Agency business activities should meet strategic objectives, services should use common standards within and across agen... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Business-Reference-Model | Use of the Business Reference Model | Agencies must use BRM version 3.0 for analysis and reporting on the business services view, mapping lines of business an... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Business-Services-and-Information-Flows | Business services, information flows and business case | The Roadmap must list the main lines of business with their key business services and the information flows within every... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Configuration-Management | Configuration management of architecture change | The Roadmap must describe the configuration management sub-process by which architecture changes are handled and standar... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Business-Services | Business services core architecture artifact | The agency must produce and maintain the business services core artifact, describing mission and support services, their... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Data-and-Information | Data and information core architecture artifact | The agency must produce and maintain the data and information core artifact, defining data entities, information exchang... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Data-meta-model | Data meta-model for core artifacts | To support cross-organization service interoperability, the agency must define a detailed data meta-model that specifies... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Depth-and-harmonization | Documentation depth and artifact harmonization | How much documentation is produced should depend on the detail required to answer questions about requirements, standard... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Enabling-Applications | Enabling applications core architecture artifact | The agency must produce and maintain the enabling applications core artifact, documenting application components, interf... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Host-Infrastructure | Host infrastructure core architecture artifact | The agency must produce and maintain the host infrastructure core artifact, documenting hosting environments, networks,... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Security | Security core architecture artifact | The agency must produce and maintain the security core artifact, documenting risk-adjusted controls that cut across the... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-DOCUMENTATION-Strategic | Strategic core architecture artifact | The agency must produce and maintain the strategic core artifact, documenting strategic goals, drivers and outcomes that... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Data-Reference-Model | Use of the Data Reference Model | Agencies must use the DRM as the data foundation of the architecture, answering which information can be shared and reus... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-1-Governance | EA governance roles and decision processes | The agency must establish governance that defines who plans, decides, oversees, verifies, versions, uses and sustains th... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-2-Principles | Principles as decision criteria | The agency must adopt principles that serve as the criteria for weighing investment and architecture decisions, covering... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-3-Method | EA community of practice and integrated planning method | The agency should establish a community of practice for EA and a standard method set that lets it reuse lessons from oth... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-4-Tools | Data-centric EA tools and internal repository | Agency EA tools must support architecture documentation and analysis, be data-centric and meet stakeholder information n... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-5-Standards | Authoritative and non-proprietary standards | Architectural standards should come from authoritative, non-proprietary sources and should include national and internat... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-6-Use | EA used as authoritative planning context | The agency should use the EA as the authoritative context for enterprise-wide planning and design, so architecture work... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-7-Reporting | Standardized reporting and annual EA plan | The EA program should provide regular standardized reporting, including dashboards on capabilities and options, and must... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-7-Reporting-Reference-models | Reference model taxonomies for each domain | The EA program must maintain a set of reference models with taxonomies that classify architecture information the same w... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Basic-Element-8-Audit | Periodic EA audits and CIO action | The agency must conduct periodic internal and external audits of architectures and the EA program, using methods consist... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Program-Budget | EA program budget and total cost of ownership | The Roadmap must record the EA program and project budget by fiscal year and across the full lifecycle so total cost of... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Program-Management-Section | Roadmap section on running EA as a program | The Roadmap must contain a section describing how EA is run as an ongoing management program that supports policy develo... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Program-Performance-Measures | Measures of EA program effectiveness | The Roadmap must state how the EA program's effectiveness and efficiency will be measured, using outcome measures that t... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-EA-Roles-and-Responsibilities | The Roadmap must document the roles and responsibilities | The Roadmap must document the roles and responsibilities of EA stakeholders, following the example in Table H, including... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Enterprise-Roadmap | Roadmap content, upkeep and annual submission | The agency must maintain one Roadmap that maps strategic goals to business services and technology solutions and records... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Functional-Integration | EA context and standards for interoperability | The EA should provide the shared context and the standards that programs, systems and services need to interoperate, inc... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Future-Operating-Scenarios | Presenting future operating scenarios | The Roadmap must present the future operating scenarios with a narrative that explains their purpose and the range of en... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Governance-and-Use | EA governance and decision flow | The Roadmap must set out how EA policy and decisions are made, state the program principles, and include a flow showing... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-IT-Asset-Inventory | Inventory of IT applications, systems and services | The Roadmap must include an inventory of every IT application, system and service in the agency, using the definitions g... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Importance-of-the-Framework | Framework selection characteristics | An EA framework chosen for federal use should be comprehensive, integrated and scalable, covering current and future str... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Information-Access | Accessible and adaptable information access | EA solutions should give citizens, businesses, agencies and other stakeholders diverse ways to reach government informat... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Information-Resource-Management-Strategic-Plan | Agency IRM strategic plan | Agencies must develop and maintain an IRM strategic plan under section 3506(b)(2) of title 44 U.S.C., conforming to the... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Infrastructure | Summary of the hosting infrastructure | The Roadmap must discuss the mobile, video, data and voice hosting environments and how well the cable plants, systems a... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Infrastructure-Reference-Model | Use of the Infrastructure Reference Model | Agencies must use the IRM to categorise network and cloud related standards and technologies in the hosting infrastructu... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Interoperability-Standards | Conformance to federal-wide standards | Agencies should ensure that EA solutions meet federal-wide standards wherever possible, so that strategic direction, bus... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Investment-Support | Architecture-based investment decisions | Agencies must base investment decisions on architectural solutions that show how technology and other resources will ach... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Major-Investment | Major investment determination and budget exhibits | Agencies should confirm with the relevant OMB budget officer which investments count as major, since each major investme... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Modernization | Consolidated modernization and transition plan | The Roadmap must summarise the transition plans produced by the various architecture projects and record the tasks, mile... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Performance-Reference-Model | Use of the Performance Reference Model | Agencies must use the PRM when analysing and reporting on the strategy view, applying its shared performance vocabulary... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Planning-Assumptions | Planning assumptions behind the chosen scenario | The Roadmap must explain what the scenario assumptions mean for agency priorities, including the new capabilities and re... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Privacy-Impact-Assessment-PIA | Privacy impact assessments for IT investments | Agencies must carry out and make publicly available privacy impact assessments for every new or substantially altered IT... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Resource-Optimization | Evolving EA for resource and investment decisions | The agency's architecture should evolve continuously so its views become more complete, consistent and coherent, and so... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Security-Reference-Model | Use of the Security Reference Model and mandatory protections | Agencies must apply the SRM across every sub-architecture view, as a taxonomy for controls and as a risk based method th... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Security-and-Privacy | Security and privacy in the Roadmap | The Roadmap must describe how the agency handles IT security and data privacy at every level of the framework, and secur... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Segment-Architecture | Adoption of government-wide shared segments | Agencies should plan to adopt the approved government-wide shared segments as the target architecture, because segments... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Shared-Services | Reuse and shared service selection | Agencies should choose reusable and shareable services and products for mission or support functions, and should standar... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Standards | Standards used in architecture development | The Roadmap must document the business standards that apply to mission services and support services, and the technical... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Step-1-Identify-and-Validate | Validate needs, metrics and governance | Planners must work with leadership, stakeholders and operational staff to identify, validate and prioritize needs and ch... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Step-2-Research-and-Leverage | Research reuse and partnership options | Planners should search internal and external service catalogues and comparable organizations for existing solutions, ass... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Step-3-Define-and-Plan | Integrated target-state plan and roadmap | Planners must analyse current capabilities and design the target state across all six architecture domains, then produce... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Step-4-Invest-and-Execute | Investment decision and coordinated execution | Leadership and governance must decide on the investment and implement the planned changes as a coordinated team, while a... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Step-5-Perform-and-Measure | Operate, measure and feed back results | The agency must operate the new capabilities and measure performance against the identified metrics, then use the result... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Strategic-Goals-and-Initiatives | Linking resources to strategic goals | The Roadmap must show how specific resources and the EA program back the strategic goals and initiatives of the agency,... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Strategic-Principles | IT strategy aligned with agency strategy | Agency IT strategy and the enterprise roadmap should be prepared alongside the agency's wider strategic planning, follow... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Summary-of-Current-Architecture | Integrated summary of the current architecture | The Roadmap must give an integrated overview of current business activities and the technology that supports them so the... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Summary-of-Future-Architecture | Future architecture built on alternative scenarios | The future architecture part of the Roadmap should rest on several alternative operating scenarios, because no agency ca... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Support-for-Strategy-and-Business | EA support for strategic and business planning | The Roadmap must show that the EA program supports and improves strategic and business planning and pinpoints performanc... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Technology-Adoption | Proven technology and decoupled systems | Agencies should select and implement proven market technologies, decouple systems to preserve flexibility, and adopt new... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Technology-Principles-Data-and-interfaces | Open data exchange and documented interfaces | Data and information exchange should rely on open standards, interfaces should be well documented and built on non-propr... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Technology-Principles-Host-and-endpoint-compliance | Host, desktop and security compliance | Host solutions must comply with federal policy and standards such as PIV authentication, IPv6 routing and Trusted Intern... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Technology-Principles-Hosting-and-platforms | Virtualization, open source, cloud and convergence | Application platforms should be virtualized where possible, open-source options should be included in alternatives analy... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Updating-Current-and-Future-Views | Updating current and future views from the top down | Planned changes must be documented from the top down, beginning with strategic goals and initiatives and moving through... |
| us-federal-enterprise-architecture-framework-version-2-feaf-v2::FEAF-Workforce-Requirements | Workforce knowledge and skill changes | The Roadmap must describe the changes in knowledge and skill requirements, and human capital plans must set out the trai... |