1. Convert the following requirements to a data flow diagram DFD. DFD should include levels 0, 1, and 2 diagrams. 2. Translate DFD to a system hierarchy diagram.
E-Discovery System
1. Extractiona. No catalog files are available for recovery of tapesb. Extraction metricsi. Number of tapes processed successfullyii. Tapes initially reporting problemsiii. Tapes that are subsequently sent to "Problem Tape Data Recovery"c. The Extraction processi. Managed by recording1. The box the tape was delivered in2. The source tape barcode3. Result of Extraction a. completedb. re-readc. sent to Problem Tape Data Recovery (Special Case Media)4. Support the evidentiary chain of custody5. Support the tape problem resolution (e.g., whether bad tapes are from a specific box, system, archive tool or tape type). ii. Evidentiary audit trail that allows for all data that resides in the E-Discovery system1. traced back to source data2. not duplicate dataiii. Recover all tape data and files with the exception of system and non-user filesiv. Preserve all original source datad. Ingesti. The evidentiary chain created in the Extraction step will continue in the Ingest step. ii. The lineage of files will continue to be sourced back to the tape of origin and box of tapes. iii. Ingest metrics will include number of files provided from Extraction to Ingest iv. Identify1. Identify the number of files that are relevant2. Identify the number and types of files that are not currently addressed in current file rulesv. The system will keep all data unless it is clear that it is not a relevant data type vi. If Ingest rules are incorrect, the Ingest can be re-run on the stored filesvii. The relevant file store1. The basis for the De-Duplication2. Acts as the Ingest data protection point. viii. The contractor shall ingest these files into an archival storage system.ix. De-duplication1. Will be performed as part of the Ingest process2. The duplicate will be stored on the E-Discovery system. 3. The De-Duplication actions will be recorded and used for both confirmation and a metric to anticipate growth for the final evidence data extraction system configuration. 4. De-Duplication metrics will include number of files provided by Ingest, number of files archived (ingest number minus duplicates) and the file type-to-duplicate ratio. 5. De-duplicate all files with the exception of Operating System and non-user files2. Data storage a. Complete and accurate collection of all files for user search and use b. Data storage for an evidence data extraction system also includes archive and backup of the system and data. c. Metrics for data storage shall includei. total space availableii. space used for intermediate storageiii. space used for final file storageiv. space used for index storaged. On approximately 7,000 tapes the contractor shall i. restore all file dataii. de-duplicate the files that are on e. Ability to implement access control measures on all dataf. Additional tapesi. expected to result1. at a rate of approximately 200 a month2. until the E-Discovery system is installedii. need to be incorporated into the E-Discovery system.3. Data Indexing a. The contractor shall maintain an index capability that includes i. but is not limited to1. emails2. attachments3. audio4. video5. images6. affiliated metadata ii. a full boolean phrase searchb. The contractor shall provide capabilities to keep both the Ingest mission running and the search performance effectivei. Initialii. Incrementaliii. Re-indexing. 4. Data Queries a. The contractor shall provide a solution with a single user web interface between the production and tape data restoration environment. b. The web-based interface will provide multi-variable boolean searches returning ranked results. c. All data require media metadata extractioni. Emailii. Videoiii. Audioiv. Still imagesv. Other Electronically Stored Information (ESI) d. The contractor shall be required to provide the captured metadata associated with the above-defined files in a fully searchable index. e. The contractor shall be required to provide full integration of image metadata into the fully searchable index. 5. Special Case Media Recovery a. All bad, damaged, or erroneous data will be treated as a separate processing thread. b. This separate thread is to be segregated so as not to interrupt the ongoing workflow, and the efficiency of the standard processing of the rest of the tapes in the collection. c. The actual fault with the media will be identified, the likelihood of success for recovery will be established, an estimation of the degree of effort required for recovery will be made, and a report will be generated so that the customer can determine whether the restoration effort should be executed. d. Successful recovery will be documented and, to the extent possible, unrecoverable information will be logged. e. Data that has been successfully recovered will then be moved into the standard recovery processing chain fori. de-duplicationii. ingestioniii. indexing.f. The tape recovery process for special case media involves salvaging data from inaccessible storage tape. g. There may be physical tape failure caused byi. media flaws and a loss of media alignment ii. logical tape errors caused by 1. internal data corruption2. damaged catalog dataiii. an application-related error due to the software utilized during the backup routine. h. The contractor shall identify the actual fault with the mediai. identification of the specific type of error (type of issue encountered)ii. the extent of the errors or damage to the mediaiii. minimal handling