The file's text, extracted by GovTribe without its formatting.
Project Tailoring Plan
Date:
Project Name/Acronym:
Portfolio/Program:
Business Owner:
IT Project Manager:
Information System Security Officer (ISSO):
Architecture Assurance Manager:
Project Description:
Project Work Pattern:
SLM Documentation
| Phase |
| Document Artifact |
| To be Provided (Yes/No) |
| Tailoring Description and Justification |
| Solution Engineering |
| Project Initiation Plan/Authorization Letter |
| Yes |
| Concept of Operations (ConOps) |
| Yes |
| Planning |
| Project Tailoring Plan (PTP) |
| Yes |
| This document |
| Project Management Plan (PMP) |
| Yes |
| Project Schedule |
| Yes |
| Separate from PMP |
| Acquisition Plan |
| Yes |
| Ensure Advanced Acquisition Plan or Statement of Work (SOW) is on file |
| Change Control Board (CCB) Charter |
| Yes |
| Required to establish the CCB |
| Requirements Definition |
| System Requirements Document (SRD) |
| Yes |
| Requirements Traceability Matrix (RTM) |
| Yes |
| System Workload Analysis Document (SWAD) |
| Yes |
| Data Management Plan (DMP) |
| Yes |
| Design |
| Interface Control Agreement (ICA) |
| Verify |
| Required for any interfacing systems |
| Information Technology Change Request (ITCR) |
| Verify |
| Submit ITCR and/or Information Technology Insertions (TI) as appropriate for any new technology not on the ICE TRM or Department TRM respectively |
| SEB Service Level Agreements |
| Verify |
| Only if Web or DBA hosting is required |
| Data Migration Plan |
| Verify |
| If data is being migrated in production |
| Training Plan |
| Verify |
| If end user training is required |
| Development Test Plan (DTP) |
| Yes |
| Present the FQT strategy and approach |
| Disaster Recovery Plan |
| Yes |
| Required for all systems |
| Development |
| Development Test Analysis Report (DTAR) |
| Yes |
| Provide FQT results |
| Version Description Document (VDD) |
| Yes |
| List of CCB approved software changes, CM label and number of files, and installation instructions |
| User Guide |
| Verify |
| Based on Business Owner assessment of end user needs |
| Deployment Plan |
| Verify |
| Provide details about deployment of any software or hardware components |
| Integration and Test |
| System Administration and Operations Manual |
| Verify |
| If ongoing system management required by maintenance personnel and/or operations staff |
| Implementation |
| Transition to Production Operations |
| Verify |
| If transitioning from an engineering project to Operations Division support |
| Operations and Maintenance |
| Notice of Intent to Release (NIR) |
| Yes |
| Required for each release |
| Disposition |
| Disposition Plan |
| Verify |
| Required for any older system being replaced and retired as a result of the deployment of this system |
Information Assurance Document Artifacts:
| Planning |
| FIPS 199 Security Categorization Worksheet |
| Yes |
| System Security Plan (SSP) |
| Yes |
| Security Risk Assessment |
| Yes |
| e-Authentication Assessment |
| Yes |
| Requirements Definition |
| Contingency Plan |
| Yes |
| Design |
| Interconnection Security Agreement (ISA) |
| Verify |
| Required for any interfacing systems |
| Development Security Test and Evaluation (ST&E) Plan |
| Yes |
| Single Sign-On (SSO) Integration Plan |
| Yes |
| Describe how the system plans to integrate SSO |
Privacy Office Document Artifacts:
| Planning |
| Privacy Threshold Analysis (PTA) |
| Yes |
| Requirements Definition |
| Privacy Impact Analysis (PIA) |
| TBD |
| The Privacy Office will provide direction after reviewing the PTA |
| System of Record Notice (SORN) |
| TBD |
| The Privacy Office will provide direction after reviewing the PTA |
| Disposition |
| Privacy Threshold Analysis (PTA) for Dispositioning an ICE System |
| Verify |
| Separate disposition-specific PTA required for any older system being replaced and retired as a result of the deployment of this system |
SLM Gate Reviews
| Gate Review |
| To be Held (Yes/No) |
| Tailoring Description and Justification |
| Preliminary Architecture and Design Review (PADR) |
| Yes |
| Final Architecture and Design Review (FADR) |
| Yes |
| Test Readiness Review (TRR) |
| Yes |
| Release Readiness Review (RRR) |
| Yes |
| Operational Readiness Review (ORR) |
| Yes |
| Held prior to hand-off to operations |
| Post-Deployment Review |
| Yes |
| Disposition Review |
| Verify |
| Required for any older system being replaced and retired as a result of the deployment of this system |
Independent Testing
| Independent Testing |
| To be Conducted (Yes/No) |
| Tailoring Description and Justification |
| System Acceptance Test |
| Yes |
| All applications will be tested independently |
| System Security Test |
| Yes |
| All applications will be tested independently |
| Web Code Review |
| Verify |
| As required by SEB for web enabled systems only |
| Interoperability Testing |
| Verify |
| If system introduces a software or hardware component that potentially conflicts with the existing implementation (could be a script downloaded to the desktop, a new peripheral device, or other) |
| Performance Testing |
| Verify |
| If system processing speed has a potential impact on business service delivery or if system resource usage potentially impacts other systems or the infrastructure |
| Section 508 Compliance Testing |
| Yes |
| All ICE systems with a user interface must be tested for Section 508 compliance |
Project Tailoring Approval Certification
| Certification Question |
| Yes |
| No |
| N/A |
| 1. Is the Project Tailoring Plan attached to this certification? |
| X |
| 2. Does the Project Tailoring Plan identify deliverables for the application appropriate for the system size, complexity, and risk and that fit the particular needs of the project? |
| X |
| 3. Does the Project Tailoring Plan identify SLM gate reviews that will take place during the lifecycle? |
| X |
| 4. Have justifications been provided for the inclusion, exclusion, or combination of deliverables and/or SLM gate reviews as specified in the Project Tailoring Plan? |
| X |
| 5. Does the Project Tailoring Plan identify the types of independent testing that will take place during the lifecycle? |
| X |
| 6. Do the IT Project Manager and Architecture Assurance Manager agree that the tailoring specified in the Project Tailoring Plan is appropriate for the project? |
| X |
Comments:
Concurring stakeholder:
| IT Project Manager |
| (Tab to Enter Name) |
Approving stakeholder:
| Architecture Assurance Manager |
| (Tab to Enter Name) |
PAGE
Immigration and Customs Enforcement