System Requirements and Design defining the technical approach, developing the – functional and technical detailed system designs, and evaluating the donor code base. Development/Modification/Conversion of System Software Code developing, – modifying, and converting child support system software; and installing operations hardware and software. Data Conversion planning for the legacy conversion, converting the data, and – testing the data conversion. Testing and Acceptance testing the hardware and software (e.g., system testing, – integration testing, testing”, and regression testing; performance and load “smoke testing; and user acceptance testing). Ensure data is production quality in all environments. All production data must be masked and cleansed in environments. Non-production environment must be of sufficient capacity, with enough data to ensure that testing will expose production level issues. Training training operational readiness, end users, and site support staff. – System Implementation converting data for rollouts, decommissioning the child – support portion of NOMADS (the old system), and rolling out the pilot region and all regions. Initial Maintenance and Operation maintaining and operating the system during – system warranty. System Certification planning and preparing for federal system certification. – Transition for Maintenance training state technical and help desk staff for – long-term maintenance and operation of the new system. Project Closeout planning for project closeout to ensure all artifacts are archived, – vendors are released, and accounts are settled. SYSTEM REQUIREMENTS VENDOR RESPONSE TO SYSTEM REQUIREMENTS The Implementation Contractor will prepare the RTM deliverable to document each of the baseline requirements, the changes that adjusted or expanded the requirements, the system components that implemented each requirement and the that verified them. The Implementation Contractor will maintain the RTM on an ongoing basis. The QA contractor will review the RTM on a periodic basis to ensure that all entries conform to project requirements. The Implementation Contractor will purchase the RTM software tool, subject to the Program’s approval of the tool. The Program’s staff, the PMO contractor, and the QA contractor will have copies of this tool so they can read and review the RTM. Functional designs, technical designs, test case development, code construction and unit testing, test execution, and training materials will address all requirements.
System Requirements and Design – defining the technical approach, developing the functional and technical detailed system designs, and evaluating the donor code base. Development/Modification/Conversion of System Software Code – developing, modifying, and converting child support system software; and installing operations hardware and software. Data Conversion – planning for the legacy conversion, converting the data, and testing the data conversion. Testing and Acceptance – testing the hardware and software (e.g., system testing, integration testing, “smoke testing”, and regression testing; performance and load testing; and user acceptance testing). Ensure data is production quality in all environments. All production data must be masked and cleansed in environments. Non-production environment must be of sufficient capacity, with enough data to ensure that testing will expose production level issues. Training – training operational readiness, end users, and site support staff. System Implementation – converting data for rollouts, decommissioning the child support portion of NOMADS (the old system), and rolling out the pilot region and all regions. Initial Maintenance and Operation – maintaining and operating the system during system warranty. System Certification – planning and preparing for federal system certification. Transition for Maintenance – training state technical and help desk staff for long-term maintenance and operation of the new system. Project Closeout – planning for project closeout to ensure all artifacts are archived, vendors are released, and accounts are settled. SYSTEM REQUIREMENTS VENDOR RESPONSE TO SYSTEM REQUIREMENTS The Implementation Contractor will prepare the RTM deliverable to document each of the baseline requirements, the changes that adjusted or expanded the requirements, the system components that implemented each requirement and the that verified them. The Implementation Contractor will maintain the RTM on an ongoing basis. The QA contractor will review the RTM on a periodic basis to ensure that all entries conform to project requirements. The Implementation Contractor will purchase the RTM software tool, subject to the Program’s approval of the tool. The Program’s staff, the PMO contractor, and the QA contractor will have copies of this tool so they can read and review the RTM. Functional designs, technical designs, test case development, code construction and unit testing, test execution, and training materials will address all requirements.
RFP%203462%20Child%20Support%20Enforcement%208-3-17%20Final.docx