For Enterprise Architects

FSAM Overview for Enterprise Architects

Enterprise Architects can leverage FSAM to pragmatically develop segment architectures that support the mission and vision of the enterprise. As Enterprise or Segment Architects leverage FSAM for multiple segment architecture development efforts, the consistent approach within FSAM will help Enterprise Architects reconcile the segments into an enterprise-wide view of the architecture. In addition, the strategic drivers and prioritization of segments that are defined by Enterprise Architects provide a key input to the FSAM process.

Why should Enterprise Architects use the FSAM?

Enterprise Architects should use the FSAM as a consistent process to measure and streamline their segment architecture development processes. In many instances, segment architectures are developed using different methods and techniques within the same enterprise. The FSAM will help Enterprise Architects maintain consistency in approach for segment architecture development and use.

What information is relevant?

Enterprise Architects will benefit by leveraging the consistent analytical techniques and artifacts defined and presented within the FSAM process. Specifically, Enterprise Architects can leverage the standard performance, business, data, and services artifacts when developing their enterprise-wide view of the architecture. Additionally, Enterprise Architects can leverage the FSAM's standard transition planning artifacts to develop the Enterprise Transition Plan.

All of the "core" FSAM outputs will help architects compile the required information in order to complete OMB's Enterprise Architecture Segment Report and other reporting requirements for the Enterprise Architecture Assessment Framework (EAAF). In addition, it is important that all segments be in line with the Enterprise Transition Strategy for the organization. Therefore, Chief Architects are a key contributor during the "Validate and Communicate" activities at the end of process steps 2, 3 and 4 within the FSAM.

FSAM Outputs that are core to EAAF Reporting:

Segment Architecture Development Purpose Statement — Activity 1.2 (core FSAM output)

Performance Scorecard — Activity 2.3 (core FSAM output)

Target Business Function Model — Activity 3.3 (core FSAM output)

Target Conceptual Data Model — Activity 3.3 (core FSAM output)

Target Data Steward Assignments — Activity 3.3 (core FSAM output)

Reuse Summary — Activity 4.2 (core FSAM output)

Data Reuse — Activity 4.2 (core FSAM output)

Recommendation Sequencing Milestones — Activity 4.3 (core FSAM outputs)

Segment Mapping — Activity 5.2 (core FSAM output)

Transition Plan Milestones — Activity 5.2 (core FSAM output)

FSAM Outputs that support EAAF Reporting:

Segment Scope - Activity 2.1 (core FSAM output)

Segment Context - Activity 2.1

Performance Gaps — Activity 2.2 (core FSAM output)

Strategic Improvement Opportunities — Activity 2.2 (core FSAM output)

Segment Performance Goals and Objectives — Activity 2.3 (core FSAM output)

As-Is Business Value Chain — Activity 3.1

As-Is Business Function Model — Activity 3.1 (core FSAM output)

As-Is Key Business Process Model — Activity 3.1

As-Is Business Process Swim Lane Diagram — Activity 3.1

As-Is Key Information Sources and Qualitative Assessment — Activity 3.1

Business and Data Architecture Adjustment Profiles — Activity 3.2

Target business value chain diagram — Activity 3.3

Target Key Business Process Model — Activity 3.3

Target Business Process Swim Lane Diagram — Activity 3.3

Target Business Data Mapped to Key Business processes (CRUD) — Activity 3.3

Target Information Sharing Matrix — Activity 3.3 (core FSAM output)

Target Information Flow Diagram — Activity 3.3 (core FSAM output)

Proposed Implementation Recommendations — Activity 5.1

Strategic Systems Migration / Sequencing Overview — Activity 5.2 (core FSAM output)

Recommendation Implementation Sequencing Plan — Activity 5.2

Segment Architecture Blueprint Document (incl. Sequencing Plan) — Activity 5.2 (core FSAM output)