D.5.3 Provide a high-level architecture diagram, including logical and C physical components. D.5.4 System documentation must describe error logging and how to C access the error logs. D.5.5 System documentation must describe any batch processing C requirements for the application. D.5.6 A detailed network/server diagram must be provided illustrating C the relative architecture of the proposed system. It must include: Network security zones and firewalls; Server and network components (e.g., switches); Ports and protocols used to cross security zones; How users will access the system; and Clustering of servers D.5.7 Provide conceptual and logical application data-flow models. C D.5.8 Provide a technology roadmap for the proposed system showing a C five (5) year plan for new software version releases, support window, and sun setting. D.6 Conversion D.6.1 Must describe their strategy and approach for data conversion, C including descriptions of prior similar projects. D.6.2 Must provide conversion of data from the current benefits system C into the proposed system is sufficient to provide a historical record of participation episodes based on federal requirements. D.7 Security and Recovery D.7.1 Must describe how the system security supports role security C and protects access to sensitive data. D.7.2 Must provide a recovery plan for restoring services in the of a C disaster including system and data restoration.
D.5.3 Provide a high-level architecture diagram, including logical and physical components. C D.5.4 System documentation must describe error logging and how to access the error logs. C D.5.5 System documentation must describe any batch processing requirements for the application. C D.5.6 A detailed network/server diagram must be provided illustrating the relative architecture of the proposed system. It must include: Network security zones and firewalls; Server and network components (e.g., switches); Ports and protocols used to cross security zones; How users will access the system; and Clustering of servers C D.5.7 Provide conceptual and logical application data-flow models. C D.5.8 Provide a technology roadmap for the proposed system showing a five (5) year plan for new software version releases, support window, and sun setting. C D.6 Conversion D.6.1 Must describe their strategy and approach for data conversion, including descriptions of prior similar projects. C D.6.2 Must provide conversion of data from the current benefits system into the proposed system is sufficient to provide a historical record of participation episodes based on federal requirements. C D.7 Security and Recovery D.7.1 Must describe how the system security supports role security and protects access to sensitive data. C D.7.2 Must provide a recovery plan for restoring services in the of a disaster including system and data restoration. C
0A1208_Supplement1_UIST%20Project.docx