Appendix_B_Deliverables_and_Content_Requirements.docx
DOCX document 27 KB Posted
- Solicitation number
- USM-HQ-13-0018
About this file
Appendix B - Deliverables and Content Requirements
View the file
Other files
Show all 32
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
APPENDIX B: Deliverables and Content Requirements In accordance with Section 6 of the SOO, the Contractor shall propose deliverables in accordance with the proposed PWS. The deliverables proposed by the Contractor shall address the following content objectives for the PWS Tasks. The Contractor will not be authorized to progress from logical design, to physical design, to operations and maintenance without the following exit criteria approved by the Government.
Program Management Program Management
| Content Objectives |
| Objective Description |
| Examples of Common Artifacts |
| Exit Criteria Requirements |
| Transition Out |
| Documents organizational responsibilities required to transition the system, dependencies and/or risks, transition stakeholders, and any other stakeholders. Includes all activities necessary to transition operations to another provider. Should include how various sites will be transitioned, how the data will be provided and details on its content and format, and how the inventory will be packaged, accounted for, and provided. |
| · Transition Out Plan |
| N/A |
Logical Design Phase (Analysis and Design) Logical Design Phase (Analysis and Design)
| Content Objectives |
| Objective Description |
| Examples of Common Artifacts |
| Exit Criteria Requirements |
| Project Planning and Monitoring |
| Establishes the project management approach and high-level process expectations (e.g., surveillance, progress reporting, etc.). Includes roles and responsibilities, a detailed integrated master schedule (including USM resources), the methods of ensuring and verifying the quality of work products, and issue and risk resolution. |
| · Project Management Plan |
· Detailed Project Schedule
· Integrated Master Schedule
· Quality Management Plan
· Risk Management Plan Government approved project management approach, roles and responsibilities, schedule, quality control, and risk management plan.
| Requirements |
| These may be expressed as use cases, “shall” statements, business needs, or other. They should be allocable to high-level test cases and must consider all areas of potential requirements: functional (processes, organization, location, and business performance), information system (data, system performance, interface, privacy, and security), operational (automation, manual operations), and programmatic (regulatory, contractual, and other). |
The requirements are of critical importance as an input into Government acceptance testing.
· Gap Requirements
· Gap Requirements Analysis
· System Requirements Government approved requirements.
| Architecture |
| Typically includes architecture principles and methodology, subsystem and component views and decomposition, component traceability, proposed configuration Items, data models, and the logical design of the system technical infrastructure, internal and external interfaces, security considerations, privacy considerations, web considerations, and performance engineering considerations. |
| · Systems Architecture |
· Logical Design Government approved architecture.
| Interface Control |
| Records the interface overview (purpose, description, and responsibilities), infrastructure and security requirements, boundary conditions (data, communication methods, protocols, performance considerations, security considerations, and privacy considerations), and interface processing (functionality, business rules, controls, error handling, security measures, access control, audit and accountability, and identification and authentication). Used to control both sides of an interface. |
| · Interface Control Documents |
| Government approved interface control. |
| Test Planning |
| Records the overall verification and validation effort, roles and responsibilities for the Government and solution Contractors, expectations for preparing for each test phase, and expectations for exiting each test phase. |
It is critical that this content make very clear the Government’s expectations for sufficient and complete acceptance testing.
· Master Test Plan
· System Validation and Verification Plan
· Requirements Traceability Matrix (to test cases) Government approved test plans.
| IT Security and Privacy Planning and Certification |
| Identify the appropriate regulatory and policy expectations for security as well as the expectations as to how they will be met and verified during the program. Establish roles and responsibilities among the Government and the solution Contractor. |
Identify whether the solution contains any PII and whether the security planning and certification will be sufficient to address any privacy issues.
· Security Risk Assessment
· Privacy Impact Assessment
· System Security Plan
· Information Technology Contingency Plan Government approved security and privacy planning and certification.
| Accessibility Planning and Certification |
| Identify the applicable provisions and the expectations for meeting them. Establish roles and responsibilities among the Government and the solution Contractor for meeting the provisions and verifying that the provisions have been met. |
| · Section 508 Accessibility Package |
| Government approved accessibility planning and certification. |
| Transition Planning |
| Documents organizational gaps, transition dependencies and/or risks, transition stakeholders, receiving organizations, developing organizations, and any other stakeholders. Includes all activities necessary to transition operations. Also includes a plan that breaks down the user population and the training needs of the various segments of that population as well as the methods used and knowledge delivered to that population that will enable them to effectively use the system. |
If needed, documents the business impacts (process, organization, location) from the implementation of the system, how those impacts will be addressed by the USM, and the stakeholders involved in implementing the changes.
Should include how various sites will be prepared and how the Government will determine its acceptance of the site's readiness for Government data or inventory.
· Organizational Change Management Plan
· Transition Management Plan
· Data Migration Plan
· Warehouse Migration Plan
· Call-Center Stand-up Plan
· Cutover Plan
· Training Strategy
· Warehouse and Call Center Physical Security Plan Government approved transition plans
Physical Design Phase (Configuration and Implementation) Physical Design Phase (Configuration and Implementation)
| Content Objectives |
| Objective Description |
| Examples of Common Artifacts |
| Exit Criteria Requirements |
| Project Planning and Monitoring |
| If necessary, revises the project management approach and high-level process expectations (e.g., surveillance, progress reporting, etc.). Includes roles and responsibilities, a detailed schedule, the methods of ensuring and verifying the quality of work products, and issue and risk resolution. |
| · Updated/revised Logical Design Phase work products |
| Government approved project management approach, roles and responsibilities, schedule, quality control, and risk management plan. |
| Operations Planning |
| A detailed guide for system maintainers to understand how to execute and monitor normal system operations, troubleshoot and resolve abnormal system operations, and prepare for system outages or necessary recovery actions. This is necessary only for the Government side of the interfaces. |
| · Operators Manual |
| Government approved operations plan. |
| Interface Control |
| Revisions based on configuration, implementation, and test. |
| · Updated/revised Logical Design Phase work products |
| Government approved interface control. |
| Test Planning and Execution |
| Includes confirmation of the testing approach and what constitutes acceptance, further development of test cases and business scenarios, and the development of scripts for test execution. |
Capturing and recording test results.
· Systems Integration Test Plan and Scripts
· Government Acceptance Test Plan and Scripts
· Test Reports
· Updated Requirements Traceability Matrix Government approved test planning and execution strategy.
| IT Security and Privacy Planning and Certification |
| Planning and preparing for security testing and certification. |
Capturing and recording test results.
· Updated/revised Logical Design Phase work products
· Security Test and Evaluation Plan
· Certification and Accreditation Results Government approved security, privacy planning and certification.
| Accessibility Planning and Certification |
| Capturing and recording test results. |
| · Section 508 testing results |
| Government approved accessibility plan and certification |
| Transition Planning and Execution |
| Revisions based on configuration work, implementation, and test. |
Includes detailed training preparations.
Includes final physical security audit and audit findings resolution.
· Updated/revised Logical Design Phase work products
· Training Plan
· User Documentation and Training Materials Government approved transition planning and execution strategy
File details come from the government source that posted it. Updated .