Enterprise Architecture Review Process

PURPOSE ▪ SCOPE ▪ PROCESS DESCRIPTION ▪ PROCESS DIAGRAM ▪ PROCESS INPUTS/OUTPUTS ▪ PROCESS RELATIONSHIPS ▪ ROLES AND RESPONSIBILITIES ▪ SUPPORTING DOCUMENTATION ▪ REVISION HISTORY

Process Owner: Manager, IT Strategy and Compliance

Note: An owner must be a PCES-level manager or higher.

This process establishes standard tools and processes for the enterprise architecture review within the Postal Service Technical Environment.

1. PURPOSE

The purpose for the EA Review Process is to ensure the full and proper use of Postal Service information resources and technologies, including IT human resources, IT processes, and infrastructure.  The EA Review Process is integrated with the Technology Solution Life Cycle (TSLC).

2. SCOPE

The EA Review Process applies to all Postal Service personnel and contracted vendors and applies to all projects introducing new or expanded use of IT services, technology solutions, or COTS software.  This review process also applies to projects that require upgrades to software previously approved for inclusion in the IT Tool Kit (ITK).

3. PROCESS DESCRIPTION

The Enterprise Architecture Committee (EAC) must review and approve every new or expanded use of IT services or technology solutions.  The EAC Review activities begin during the Requirements Process of the TSLC.

At each checkpoint within the Enterprise Architecture Review Process, there is a sequence of submit, review, decide, and record outcome.  The EAC Review decisions are conveyed to the project teams through the IT Portfolio Manager sponsoring the project.  Approval by the EAC must be obtained for each checkpoint in the review process.

The Enterprise Architecture Review process includes the following steps:

Step 1:

Submit Enterprise Architecture Project Notification to EAC (Checkpoint 1).

The EAC reviews the Business Needs Statement (BNS) and other TSLC documents and notifies the IT Portfolio Manager sponsoring the project.  Acknowledgement of the project completes Checkpoint 1.
Step 2:

Complete Requirements document.

Upon acceptance of the BNS, the project team completes the Technology Solution Requirements Document.
Step 3:

Initiate Analysis & Design documentation.

The Technology Solution Project Manager initiates the creation of the Technology Solution Design as part of the Analysis & Design Process.
Step 4:

Submit completed Technology Solution Design to EAC for approval.
  4.1 The Project Manager completes the Technology Solution Design document.
    4.1.1 TS Design Document Scope-Usage: The TS Design document is the culmination of analysis conducted and deliverables created by the project team during the TSLC Initiate & Plan and Analysis & Design phases.  This deliverable provides the detailed design structure and context that guides the system developers and implementers.  The document includes sub-system and component specifications and designs; IT services usage; Commercial-Off-The-Shelf (COTS) product specifications; and system development environment specifications.  The TS Design provides the structure, standards, and guidelines to realize the abstract solution described in the Business Needs Statement.  The Functional Requirements Document and the Logical Data Model should accompany this design document.
  4.2 The Project Manager submits the Technology Solution Design document to the EAC.
Step 5:

Approve/defer by EAC (Checkpoint 2).
  5.1 The EAC reviews the design documentation and other TSLC documents before voting to approve/disapprove with conditions/or defer judgment on the proposed technology solution.  The TS Design document should be submitted to the EAC for review prior to significant development or acquisition activities and commitments.
  5.2 The project manager is notified of the EAC’s decision.  Notification of approval or approval with conditions completes Checkpoint 2.

4. PROCESS DIAGRAM

In this section, there is a diagram of the Enterprise Architecture Review process. The process steps are stacked vertically in the center; as each process step is completed, there is a downward arrow to the next process step in the sequence. There are two Inputs on the left side of the process steps, and three Outputs on the right side of the process steps. The first process step is “Submit BNS to EAC (Checkpoint 1)”. The input to this step is “Business Needs Statement”, and the output from this step is “Accepted BNS Document”. The second process step is “Complete Requirements Document”. There are no inputs to or outputs from this step. The third process step is “Initiate Analysis & Design Documentation”. There are no inputs to or outputs from this step. The fourth process step is “Submit TS Design Document to EAC for Approval”. The input to this step is “Detailed Design Document”, and the output from this step is “Analysis & Design Document/Approved”. The fifth process step is “Approve/Defer by EAC (Checkpoint 2)”. There is no input to this step, but there is one output: “EAC Approval Letter”. There are no further steps for this process.

5. PROCESS INPUTS/OUTPUTS

Inputs

Outputs

6. PROCESS RELATIONSHIPS

The following image is the Enterprise Architecture Review process relationships diagram. At the top, the following TSLC (Technology Solution Life Cycle) phases are shown: Initiate & Plan, Technology Solution Requirements, Analysis & Design, Technology Solution Build, Systems Integration Testing (SIT), Customer Acceptance Testing (CAT), and Release Management. There are three swim lanes. From top to bottom they are: TSLC Phases, Portfolio Management, and Enterprise Architecture Committee. In the Initiate & Plan phase, there are three items in the Portfolio Management swim lane: “Conceive Need for Technology Solution”, “Business Needs Statement”, and “Obtain Funding for Requirements/Analysis & Design Phases”. A right directional arrow connects this last item to “Checkpoint 1” in the Enterprise Architecture Committee swim lane in the Requirements phase. There is an upward directional arrow connecting “Checkpoint 1” to “Complete Requirements” in the Portfolio Management swim lane of the Requirements phase. There is a right directional arrow connecting “Complete Requirements” to “Perform Analysis and Finalize Design Document” in the Portfolio Management swim lane in the Analysis & Design phase. There is a downward directional arrow connecting “Perform Analysis and Finalize Design Document” to “Checkpoint 2” in the Enterprise Architecture Committee swim lane of the Analysis & Design phase. There is a left directional arrow labeled “Deferred” connecting “Checkpoint 2” to “Perform Analysis and Finalize Design Document”. There is a right directional arrow labeled “Approved” connecting “Checkpoint 2” to “Acquire/Develop Technology Solution” in the Portfolio Management swim lane of the Build phase. There is a right directional arrow connecting “Acquire/Develop Technology Solution” to “IT Help Desk Service Management Process” in the Portfolio Management swim lane of the SIT phase. There is a right directional arrow connecting “IT Help Desk Service Management Process” to “Implement Solution” in the Portfolio Management swim lane of the Release phase. There is a downward arrow connecting “Implement Solution” to “Operate and Manage Solution” in the Portfolio Management swim lane of the Release phase. There are no items in the CAT phase. There is no additional information in this diagram.

7. ROLES AND RESPONSIBILITIES

8. SUPPORTING DOCUMENTATION

There is no supporting documentation for this process.

9. REVISION HISTORY

Version #1.0
Section(s) Revised:        N/A
Revision Description:      Baseline
Revision Date:               

Version #2.0
Section(s) Revised:        All
Revision Description:     This document was made Section 508 compliant and was converted to HTML.
Revision Date:               FY12/Q3