Data Conversion Requirements <Project #>-DC-1. This section identifies the <Project #>-DC-2. requirements, if any, needed to convert data from old systems to Etc. the new system being developed and/or deployed. Backup & Recovery Requirements <Project #>-BR-1. This section identifies details of back up and recovery <Project #>-BR-2. requirements. If software is identified as mission essential a Etc. continuity of operations plan must be developed. Failover & Redundancy <Project #>-FR-1. Requirements <Project #>-FR-2. This section identifies details of failover and redundancy Etc. requirements. Archival Requirements This section identifies the <Project #>-AC-1. requirements, if any, related to <Project #>-AC-2. length of time data needs to be retained within the application; Etc. level of difficulty to retrieve archived data, etc. Availability Requirements This section identifies the requirements, if any, related to <Project #>-AV-1. support (e.g., 24x7 ) and up-time (e.g., 99.9%). These requirements <Project #>-AV-2. tie into how critical the solution is to the business. Requirements Etc. may also include a manual backup process in case the application fails.
Data Conversion Requirements This section identifies the requirements, if any, needed to convert data from old systems to the new system being developed and/or deployed. <Project #>-DC-1. <Project #>-DC-2. Etc. Backup & Recovery Requirements This section identifies details of back up and recovery requirements. If software is identified as mission essential a continuity of operations plan must be developed. <Project #>-BR-1. <Project #>-BR-2. Etc. Failover & Redundancy Requirements This section identifies details of failover and redundancy requirements. <Project #>-FR-1. <Project #>-FR-2. Etc. Archival Requirements This section identifies the requirements, if any, related to length of time data needs to be retained within the application; level of difficulty to retrieve archived data, etc. <Project #>-AC-1. <Project #>-AC-2. Etc. Availability Requirements This section identifies the requirements, if any, related to support (e.g., 24x7 ) and up-time (e.g., 99.9%). These requirements tie into how critical the solution is to the business. Requirements may also include a manual backup process in case the application fails. <Project #>-AV-1. <Project #>-AV-2. Etc.
4-Technical-Design-Specification-Requirements-2dlu5l0.docx