DRAFT_HSHQDC-17-R-000xx_RPM_RP_RFP-2016-10-07_Atch5_System_Architecture_Update_Plan.pdf
PDF 37 KB Posted
- Attached to
- FINAL RFP HSHQDN-17-R-0002 DNDO RPM RP
- Solicitation number
- DRAFT_RFP_HSHQDN-17-R-000XX_RPM-RP
About this file
ATTACHMENT 5 SYSTEM ARCHITECTURE UPDATE PLAN
View the file
Other files
Show 40 more
Latest 50 of 54 listed here. See the rest on GovTribe.
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
Attachment 5: System Architecture Updates
The System Architecture Update Plan will provide the Government with an understanding of how Offeror intends to manage updates, such as updates required to (1) respond to changes in the Government Enterprise Architecture, (2) repair identified security flaws, and (3) repair system deficiencies identified during testing and use. The following are examples of appropriate details the Government would expect the plan to contain:
• Diagram of the RPM system architecture to the functional level
• Diagram of the Offeror’s system architecture update process
• Diagram of Offeror’s system architecture update development and deployment team structure
• Description of team management
• How the functional changes to the system architecture will be identified
• How enterprise-architecture-driven changes will be handled
• How flaw remediation will be handled
• How the changes to the system architecture will be planned and briefed before starting the development process
• Which system architecture standards, such as NIST 800-53, will be implemented
• How architecture standards will be implemented in the planning and development phase
• What process will be utilized to make changes at the functional and code level
• How the changes to the system architecture will be documented
• How the changes to the system architecture will be briefed to the Government
• How the integrity of the system configuration management will be addressed during the change process
• How the changes to the system architecture will be verified
• How the changes to the system architecture will be tested for effectiveness
• How the changes’ potential side effects to system performance will be identified and tested
• How the system security assessment will be conducted on the proposed updated security architecture
• How evidence of the execution of the security assessment and its results will be documented and transmitted to the Government
• How failures at any stage of the process be will handled; how the Government will be notified of the consequences
• How risks associated with the updating process will be identified, managed, and briefed to the Government
• How lessons learned from implementation of the process will be captured and utilized to improve the system architecture change process
| Attachment 5: System Architecture Updates |
| The System Architecture Update Plan will provide the Government with an understanding of how Offeror intends to manage updates, such as updates required to (1) respond to changes in the Government Enterprise Architecture, (2) repair identified securit... |
| Diagram of the RPM system architecture to the functional level |
| Diagram of the Offeror’s system architecture update process |
| Diagram of Offeror’s system architecture update development and deployment team structure |
| Description of team management |
| How the functional changes to the system architecture will be identified |
| How enterprise-architecture-driven changes will be handled |
| How flaw remediation will be handled |
| How the changes to the system architecture will be planned and briefed before starting the development process |
| Which system architecture standards, such as NIST 800-53, will be implemented |
| How architecture standards will be implemented in the planning and development phase |
| What process will be utilized to make changes at the functional and code level |
| How the changes to the system architecture will be documented |
| How the changes to the system architecture will be briefed to the Government |
| How the integrity of the system configuration management will be addressed during the change process |
| How the changes to the system architecture will be verified |
| How the changes to the system architecture will be tested for effectiveness |
| How the changes’ potential side effects to system performance will be identified and tested |
| How the system security assessment will be conducted on the proposed updated security architecture |
| How evidence of the execution of the security assessment and its results will be documented and transmitted to the Government |
| How failures at any stage of the process be will handled; how the Government will be notified of the consequences |
| How risks associated with the updating process will be identified, managed, and briefed to the Government |
| How lessons learned from implementation of the process will be captured and utilized to improve the system architecture change process |
File details come from the government source that posted it. Updated .