Waterfall Methodology: Build Process

PURPOSESCOPEPROCESS DESCRIPTIONPROCESS INPUTS/OUTPUTSSUPPORTING DOCUMENTATIONREVISION HISTORY

Process Owner: Manager, Business Relationship Management

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

This document establishes standard processes for the Technology Solution Life Cycle (TSLC) Waterfall Build phase within the Postal Service Technical Environment.

PURPOSE

The Build process develops the technology components specified in the Technology Solution Design document, which may include acquisition.

The objectives of the Technology Solution Build process are:

SCOPE

This process applies to all:

PROCESS DESCRIPTION

This process is composed of the following subprocesses:

  1. Follow the Certification and Accreditation Process.
  2. The Business Relationship Management Program Manager (BRM PM) coordinates this task.

    For security-related processes and artifacts, follow the Certification and Accreditation Process as described in the Handbook AS-805A, Information Resource Certification and Accreditation Process.

  3. PCI In-Scope Only: Develop and Maintain Secure PCI In-Scope Systems and Applications.
  4. The BRM PM coordinates this task.

    Ensure that all requirements listed and referenced in the Develop and Maintain Secure PCI In-Scope Systems and Applications are met.

  5. Develop Build Plan.
  6. Each service provider will develop its own build plan that maps to the tasks that were developed in the Analysis and Design phase.

  7. Develop and Unit Test Technology Solution.
  8. The Technology Solution Coordinator (TSC) coordinates this process.

    This process develops and independently tests individual components necessary to deliver the technology solution.  Individual components may include procured items such as COTS. The extent of integration testing of the components at this phase is dependent on the TSC.

  9. Upload Documents to the TSLC Artifacts Library.
  10. The BRM PM ensures that the following artifacts are uploaded to the TSLC Artifacts Library in the appropriate folders:

  11. Validate and Approve Build.
  12. This quality assurance (QA) process validates that technology solution components are built according to specification and that proper software version and infrastructure hardware are installed prior to progressing to the SIT phase. Upon validation by all Technology Solution Provider stakeholders, configuration management records are updated to reflect the technology solution.

PROCESS INPUTS/OUTPUTS

Baseline artifacts are mandatory and must be uploaded prior to release to production unless the project is following the Tollgate process. If Tollgate, documents from the Tollgate must be uploaded within 10 business days. Baseline artifacts are indicated in this document by an asterisk (*).

Inputs

Outputs

SUPPORTING DOCUMENTATION

Access supporting documentation from ITWEB (Internal):

Access Supporting Documentation from USPS.com (external):

REVISION HISTORY

Version
Date
Description of Change
1.0 N/A Initial release.
1.1 02.22.2012 Title, Supporting Documentation:
Added “Waterfall.”

Introduction:
Updated Process Owner to: Manager, Solutions Development and Support, to reflect current organization.

Process Description, Process Diagram, Process Relationships:
Added indicators and text for baseline artifacts.

Process Diagram, Process Relationships:
Added text in non-displayable format for Section 508 compliance.
1.2 FY12/Q3 This document was made Section 508 compliant and was converted to HTML.
2.0 05.10.2013 Updated for Tollgates, PCI, and general compliance; ownership of TSLC processes transferred from Manager, Solutions Development and Support, to Manager, Business Relationship Management.
2.1 08.16.2013 Scope:
Updated to clarify that the Requirements must be approved, not the Requirements Traceability Matrix document.
2.2 03.18.2014 Process Inputs/Outputs:
Updated "baseline artifacts" statement to clarify that they must be uploaded prior to release unless the project is following the Tollgate process. If Tollgate, required Tollgate artifacts must be uploaded within 10 business days.
2.2.1 06.15.2015 The annual review for functional accuracy and current PCI DSS requirements has been completed: No changes. CR 81805
2.2.2 06.26.2015 Non-substantive update: Update CR for annual review. Remove link and version of PCI DSS.
2.2.3 03.14.2016 Annual Review: No changes. The annual review for functional accuracy and current PCI requirements has been completed. CR 154951
2.2.4 10.31.2016 Annual Review: The annual review for functional accuracy and current PCI requirements has been completed. CR 223948
Powered By OneLink