FEAF-1 | Core architecture artifacts and the Enterprise Roadmap | 0 |
FEAF-1.11 | Task 1.11 engage and schedule stakeholders | 0 |
FEAF-1.12 | Task 1.12 gather challenges risks and performance | 0 |
FEAF-1.13 | Task 1.13 agree common business challenges | 0 |
FEAF-1.14 | Task 1.14 appoint an authorised sponsor | 0 |
FEAF-1.2-Activity-Outputs | Validated list of stakeholder needs | 0 |
FEAF-1.23 | Confirm needs with stakeholders | 0 |
FEAF-1.3-Activity-Outputs | Target performance metrics | 0 |
FEAF-1.31 | Establish high priority needs | 0 |
FEAF-1.32 | Evaluate impact, value, risk and dependencies | 0 |
FEAF-1.33 | Formulate vision, purpose and planning scope | 0 |
FEAF-1.4-Activity-Outputs | Planning governance structure | 0 |
FEAF-1.43 | Formally engage or initiate governance | 0 |
FEAF-1.44 | Obtain governance approval of planning basis | 0 |
FEAF-10.1 | Exhibit 300 performance reporting with the PRM | 0 |
FEAF-11 | Performance Reference Model touchpoints | 0 |
FEAF-12.1 | Establish line of sight to outcomes | 0 |
FEAF-12.2 | Select a balanced set of Exhibit 300 measures | 0 |
FEAF-13 | Align indicators with goals and categories | 0 |
FEAF-14.1 | Purpose of the Business Reference Model | 0 |
FEAF-14.2 | Structure of the Business Reference Model | 0 |
FEAF-15 | Using the Business Reference Model taxonomy | 0 |
FEAF-15.1 | Identify government-wide shared service opportunities | 0 |
FEAF-15.2 | Reduce duplication using the Business Reference Model | 0 |
FEAF-16 | Business Reference Model touchpoints | 0 |
FEAF-17 | Methods used alongside the Business Reference Model | 0 |
FEAF-17.1 | Business architecture for decision support | 0 |
FEAF-17.2 | Business process modeling as a core practice | 0 |
FEAF-18 | Business Reference Model summary | 0 |
FEAF-19.1 | Purpose of the Data Reference Model | 0 |
FEAF-19.2 | Structure of the Data Reference Model | 0 |
FEAF-2 | Overview of the Collaborative Planning Methodology | 0 |
FEAF-2.1-Activity-Outputs | Organizations and service providers to engage | 0 |
FEAF-2.11 | Identify organizations with similar missions | 0 |
FEAF-2.12 | Identify service providers for priority needs | 0 |
FEAF-2.13 | Research and select engagement targets | 0 |
FEAF-2.2-Activity-Outputs | Partnership risk and benefits analysis | 0 |
FEAF-2.3-Activity-Outputs | Partnership feasibility report | 0 |
FEAF-2.31 | Assess partnership feasibility under constraints | 0 |
FEAF-2.32 | Draft memorandum of understanding | 0 |
FEAF-2.33 | Present leverage recommendation for approval | 0 |
FEAF-20.1 | Comparing data sources across agencies | 0 |
FEAF-20.2 | Building a standardized information exchange | 0 |
FEAF-21 | Data Reference Model touchpoints | 0 |
FEAF-22 | Methods used with the Data Reference Model | 0 |
FEAF-22.1 | Uniform data description and metadata | 0 |
FEAF-22.2 | Categorizing data and keeping an asset catalog | 0 |
FEAF-22.3 | Applying recognized data sharing practices | 0 |
FEAF-23 | Data Reference Model summary | 0 |
FEAF-24.1 | Purpose of the Application Reference Model | 0 |
FEAF-24.2 | Structure of the Application Reference Model | 0 |
FEAF-25.1 | Cutting IT cost through application portfolio mapping | 0 |
FEAF-25.2 | Selecting solutions through the Consolidated Reference Model | 0 |
FEAF-26 | Application Reference Model touchpoints | 0 |
FEAF-27 | Three methods used with the Application Reference Model | 0 |
FEAF-27.1 | Capability modeling and analysis | 0 |
FEAF-27.2 | Service oriented architecture and service mapping | 0 |
FEAF-27.3 | Portfolio management for service and application reuse | 0 |
FEAF-28 | Application Reference Model summary | 0 |
FEAF-29.1 | Purpose of the Infrastructure Reference Model | 0 |
FEAF-29.2 | Structure of the Infrastructure Reference Model | 0 |
FEAF-3 | Step 1: validate needs, sponsor and governance | 0 |
FEAF-3.11 | Identify collaborative planning team members | 0 |
FEAF-3.12 | Charter the collaborative planning team | 0 |
FEAF-3.13 | Develop the planning project plan | 0 |
FEAF-3.14 | Approve team charter and project plan | 0 |
FEAF-3.15 | Establish communication strategy and project website | 0 |
FEAF-3.2-Activity-Outputs | Balanced performance scorecard | 0 |
FEAF-3.23 | Formulate and prioritize strategic improvements | 0 |
FEAF-3.24 | Refine target vision and performance scorecard | 0 |
FEAF-3.25 | Package and approve the refined vision | 0 |
FEAF-3.3-Activity-Outputs | Activity 3.3 output list | 0 |
FEAF-3.31 | Determine planning artefacts and data specificity | 0 |
FEAF-3.32 | Assess the as-is business and data environment | 0 |
FEAF-3.33 | Design the target business and data environment | 0 |
FEAF-3.34 | Assess as-is applications and infrastructure | 0 |
FEAF-3.35 | Design target applications and infrastructure | 0 |
FEAF-3.4-Activity-Outputs | Activity 3.4 output list | 0 |
FEAF-3.43 | Publish plan and update related roadmaps | 0 |
FEAF-3.44 | Issue policy, procedures and guidance | 0 |
FEAF-3.5-Activity-Outputs | Activity 3.5 output list | 0 |
FEAF-30 | Using the Infrastructure Reference Model taxonomy | 0 |
FEAF-30.1 | Building an IT asset management inventory | 0 |
FEAF-30.2 | Finding shared service and consolidation candidates | 0 |
FEAF-31 | Infrastructure Reference Model touchpoints | 0 |
FEAF-32 | Methods and practices for the Infrastructure Reference Model | 0 |
FEAF-32.1 | Fields required in the infrastructure asset inventory | 0 |
FEAF-32.2 | Identify affected organizations and stakeholders | 0 |
FEAF-33 | Infrastructure Reference Model summary | 0 |
FEAF-34.1 | Compare transition options by cost, value and risk | 0 |
FEAF-34.2 | Develop and approve integrated plan | 0 |
FEAF-35.1 | Classifying policy against federal security standards | 0 |
FEAF-35.2 | Deriving controls from policy at agency level | 0 |
FEAF-35.3 | Engage or create execution governance | 0 |
FEAF-36 | Security Reference Model touchpoints | 0 |
FEAF-37 | Build security into the system development lifecycle | 0 |
FEAF-37.1 | Risk based security design | 0 |
FEAF-37.2 | Choose and tailor a risk-reducing control set | 0 |
FEAF-38 | Tie security and privacy into enterprise architecture | 0 |
FEAF-4 | Step 2: research and leverage existing work | 0 |
FEAF-5 | Step 3: define and plan the change | 0 |
FEAF-6 | Step 4: committing the investment and carrying out the plan | 0 |
FEAF-7 | Step 5: perform and measure outcomes | 0 |
FEAF-8 | Consolidated Reference Model overview | 0 |
FEAF-9.1 | Purpose of the Performance Reference Model | 0 |
FEAF-9.2 | Structure of the Performance Reference Model | 0 |
FEAF-A.2.1 | Step 1 at a glance table | 0 |
FEAF-A.2.2 | Tailor core and non-core outputs | 0 |
FEAF-A.2.3 | Activity 1.1 engage sponsor and stakeholders | 0 |
FEAF-A.2.4 | Activity 1.2 validate needs against constraints | 0 |
FEAF-A.2.5 | Formulate the case for priority needs | 0 |
FEAF-A.2.6 | Identify and engage planning governance | 0 |
FEAF-A.3.1 | Step 2 at-a-glance | 0 |
FEAF-A.3.2 | Core artifact tailoring guidance | 0 |
FEAF-A.3.3 | Finding organizations and service providers | 0 |
FEAF-A.3.4 | Analyze opportunities to leverage | 0 |
FEAF-A.3.5 | Determine whether to leverage | 0 |
FEAF-A.4.1 | Integrated plan document | 0 |
FEAF-A.4.2 | Core artifact tailoring for Step 3 | 0 |
FEAF-A.4.3 | Formalize the planning team and launch | 0 |
FEAF-A.4.6 | Formulate integrated plan and roadmap | 0 |
FEAF-A.4.7 | Initiate execution governance | 0 |
FEAF-A.5.1 | Step 4 at a glance | 0 |
FEAF-A.5.2 | Tailor core artefacts to constraints | 0 |
FEAF-A.5.3 | Define funding strategy and investment decision | 0 |
FEAF-A.5.4 | Obtain resources and validate the plan | 0 |
FEAF-A.5.5 | Execute the plan under governance | 0 |
FEAF-A.6.1 | Step 5 at a glance | 0 |
FEAF-A.6.2 | Tailor core artefacts to constraints | 0 |
FEAF-A.6.3 | Operate with new capabilities | 0 |
FEAF-A.6.4 | Measure Performance Against Defined Metrics | 0 |
FEAF-A.6.5 | Analyze Performance and Provide Formal Feedback | 0 |
FEAF-APPENDIX-A | Terms and definitions used in the document | 0 |
FEAF-Application-Reference-Model | Use of the Application Reference Model | 0 |
FEAF-Applications | Summary of the application suite | 0 |
FEAF-Applications-Sub-Architecture-Domain | Applications domain scope and guiding questions | 0 |
FEAF-Architecture-at-Various-Levels-of-Scope | Standard method, principles and artifacts for agency EA | 0 |
FEAF-Authoritative-Reference | EA as the authoritative design reference | 0 |
FEAF-Authoritative-Reference-Verified-configuration | Verified configuration and continuous monitoring | 0 |
FEAF-BASIC-ELEMENTS-OF-FEDERAL-ENTERPRISE-ARCHITECTURE | Eight required EA program elements | 0 |
FEAF-Business-Principles | Business services tied to strategy and security | 0 |
FEAF-Business-Reference-Model | Use of the Business Reference Model | 0 |
FEAF-Business-Services-and-Information-Flows | Business services, information flows and business case | 0 |
FEAF-Business-Sub-Architecture-Domain | Business domain scope and guiding questions | 0 |
FEAF-Configuration-Management | Configuration management of architecture change | 0 |
FEAF-DOCUMENTATION | Six domains and core artifact requirement | 0 |
FEAF-DOCUMENTATION-Business-Services | Business services core architecture artifact | 0 |
FEAF-DOCUMENTATION-Data-and-Information | Data and information core architecture artifact | 0 |
FEAF-DOCUMENTATION-Data-meta-model | Data meta-model for core artifacts | 0 |
FEAF-DOCUMENTATION-Depth-and-harmonization | Documentation depth and artifact harmonization | 0 |
FEAF-DOCUMENTATION-Enabling-Applications | Enabling applications core architecture artifact | 0 |
FEAF-DOCUMENTATION-Host-Infrastructure | Host infrastructure core architecture artifact | 0 |
FEAF-DOCUMENTATION-Security | Security core architecture artifact | 0 |
FEAF-DOCUMENTATION-Strategic | Strategic core architecture artifact | 0 |
FEAF-Data-Reference-Model | Use of the Data Reference Model | 0 |
FEAF-Data-Sub-Architecture-Domain | Data domain scope and guiding questions | 0 |
FEAF-EA-Basic-Element-1-Governance | EA governance roles and decision processes | 0 |
FEAF-EA-Basic-Element-2-Principles | Principles as decision criteria | 0 |
FEAF-EA-Basic-Element-3-Method | EA community of practice and integrated planning method | 0 |
FEAF-EA-Basic-Element-4-Tools | Data-centric EA tools and internal repository | 0 |
FEAF-EA-Basic-Element-5-Standards | Authoritative and non-proprietary standards | 0 |
FEAF-EA-Basic-Element-6-Use | EA used as authoritative planning context | 0 |
FEAF-EA-Basic-Element-7-Reporting | Standardized reporting and annual EA plan | 0 |
FEAF-EA-Basic-Element-7-Reporting-Reference-models | Reference model taxonomies for each domain | 0 |
FEAF-EA-Basic-Element-8-Audit | Periodic EA audits and CIO action | 0 |
FEAF-EA-Program-Budget | EA program budget and total cost of ownership | 0 |
FEAF-EA-Program-Management-Section | Roadmap section on running EA as a program | 0 |
FEAF-EA-Program-Performance-Measures | Measures of EA program effectiveness | 0 |
FEAF-EA-Roles-and-Responsibilities | The Roadmap must document the roles and responsibilities | 0 |
FEAF-Enterprise-Roadmap | Roadmap content, upkeep and annual submission | 0 |
FEAF-Functional-Integration | EA context and standards for interoperability | 0 |
FEAF-Future-Operating-Scenarios | Presenting future operating scenarios | 0 |
FEAF-Governance-and-Use | EA governance and decision flow | 0 |
FEAF-INTRODUCTION | Purpose and scope of the common approach | 0 |
FEAF-IT-Asset-Inventory | Inventory of IT applications, systems and services | 0 |
FEAF-Importance-of-the-Framework | Framework selection characteristics | 0 |
FEAF-Information-Access | Accessible and adaptable information access | 0 |
FEAF-Information-Resource-Management-Strategic-Plan | Agency IRM strategic plan | 0 |
FEAF-Infrastructure | Summary of the hosting infrastructure | 0 |
FEAF-Infrastructure-Reference-Model | Use of the Infrastructure Reference Model | 0 |
FEAF-Infrastructure-Sub-Architecture-Domain | Infrastructure domain scope and guiding questions | 0 |
FEAF-Interoperability-Standards | Conformance to federal-wide standards | 0 |
FEAF-Investment-Support | Architecture-based investment decisions | 0 |
FEAF-LEVELS-OF-SCOPE | Eight levels of architectural scope | 0 |
FEAF-Major-Investment | Major investment determination and budget exhibits | 0 |
FEAF-Modernization | Consolidated modernization and transition plan | 0 |
FEAF-OVERALL-CONCEPT | Shared EA meta-model and building blocks | 0 |
FEAF-PLANS-AND-VIEWS | One roadmap and per-project plan and views | 0 |
FEAF-PRIMARY-OUTCOMES | Four intended EA outcomes | 0 |
FEAF-Performance-Reference-Model | Use of the Performance Reference Model | 0 |
FEAF-Planning-Assumptions | Planning assumptions behind the chosen scenario | 0 |
FEAF-Privacy-Impact-Assessment-PIA | Privacy impact assessments for IT investments | 0 |
FEAF-REFERENCE-MODELS | Six reference models as shared taxonomies | 0 |
FEAF-Reference-Architecture | Definition of a reference architecture | 0 |
FEAF-Resource-Optimization | Evolving EA for resource and investment decisions | 0 |
FEAF-Security-Reference-Model | Use of the Security Reference Model and mandatory protections | 0 |
FEAF-Security-Sub-Architecture-Domain | Security domain scope and guiding questions | 0 |
FEAF-Security-and-Privacy | Security and privacy in the Roadmap | 0 |
FEAF-Segment-Architecture | Adoption of government-wide shared segments | 0 |
FEAF-Shared-Services | Reuse and shared service selection | 0 |
FEAF-Standards | Standards used in architecture development | 0 |
FEAF-Step-1-Identify-and-Validate | Validate needs, metrics and governance | 0 |
FEAF-Step-2-Research-and-Leverage | Research reuse and partnership options | 0 |
FEAF-Step-3-Define-and-Plan | Integrated target-state plan and roadmap | 0 |
FEAF-Step-4-Invest-and-Execute | Investment decision and coordinated execution | 0 |
FEAF-Step-5 | Planners Support Operations During Execution | 0 |
FEAF-Step-5-Perform-and-Measure | Operate, measure and feed back results | 0 |
FEAF-Strategic-Goals-and-Initiatives | Linking resources to strategic goals | 0 |
FEAF-Strategic-Principles | IT strategy aligned with agency strategy | 0 |
FEAF-Strategy-Sub-Architecture-Domain | Strategy domain scope and guiding questions | 0 |
FEAF-Sub-Architecture-Domains | Six architecture domains and cross-cutting security | 0 |
FEAF-Summary-of-Current-Architecture | Integrated summary of the current architecture | 0 |
FEAF-Summary-of-Future-Architecture | Future architecture built on alternative scenarios | 0 |
FEAF-Support-for-Strategy-and-Business | EA support for strategic and business planning | 0 |
FEAF-Table-2 | Strategy domain elective artifact list | 0 |
FEAF-Table-3 | Business domain elective artifact list | 0 |
FEAF-Table-4 | Elective data artifacts for the data domain | 0 |
FEAF-Table-5 | Applications domain elective artifact list | 0 |
FEAF-Table-6 | Infrastructure domain elective artifact list | 0 |
FEAF-Table-7 | Security domain elective artifact list | 0 |
FEAF-Table-A | Required core artifact per domain | 0 |
FEAF-Technology-Adoption | Proven technology and decoupled systems | 0 |
FEAF-Technology-Principles-Data-and-interfaces | Open data exchange and documented interfaces | 0 |
FEAF-Technology-Principles-Host-and-endpoint-compliance | Host, desktop and security compliance | 0 |
FEAF-Technology-Principles-Hosting-and-platforms | Virtualization, open source, cloud and convergence | 0 |
FEAF-Updating-Current-and-Future-Views | Updating current and future views from the top down | 0 |
FEAF-Using-the-Architected-Solution | Design alternatives and authoritative information | 0 |
FEAF-Workforce-Requirements | Workforce knowledge and skill changes | 0 |