Enterprise Architecture Review Process
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.
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).
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:
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.
Complete Requirements document.
Upon acceptance of the BNS, the project team completes the Technology Solution Requirements Document.
Initiate Analysis & Design documentation.
The Technology Solution Project Manager initiates the creation of the Technology Solution Design as part of the Analysis & Design Process.
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.|
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.|
There is no supporting documentation for this process.
Section(s) Revised: N/A
Revision Description: Baseline
Section(s) Revised: All
Revision Description: This document was made Section 508 compliant and was converted to HTML.
Revision Date: FY12/Q3