Report

Report requirement:

· Literature review:

Instructions: Provide summary of related work similar to the project. Your related work summary should capture the purpose for the project and the outcome/recommendations

· Design Decision:

Instructions: Utilizing the following subsections, describe decisions made that impact the proposed database design. This should include the platform and database management system (DBMS) chosen for the project. Include any other information relevant to the database design decisions (e.g., Data Conversion Plan, Service Level Agreements (SLAs)). The Design Decisions section is written at a higher level than the subsequent Detailed Database Design section, and provides an understanding and rationale for the content in the Detailed Database Design section. If any of the information in this section is provided in the SDD, ICD(s), or other documents (e.g., Data Conversion Plan), they may be referenced within this section as appropriate.

· Key Factors Influencing Design:

Instructions: Describe key functional or non-functional requirements that influenced the design. If all such decisions are explicit in the requirements, this section shall so state. Design decisions that respond to requirements designated as critical (e.g., those for performance, availability, security, or privacy) shall be placed in separate subparagraphs. If a design decision depends upon system states or modes, this dependency shall be indicated. If some or all of the design decisions are described in the documentation of a custom or commercial DBMS, or in the SDD, they may be referenced in this section. Design conventions needed to understand the design shall also be presented or referenced.

· Functional Design decision:

Instructions: Describe decisions about how the database will behave in meeting its requirements from a user's point of view (i.e., functionality of the database from an application perspective), ignoring internal implementation, and any other decisions affecting further design of the database. Include decisions regarding inputs the database will accept and outputs (displays, reports, messages, responses, etc.) it will need to support, including interfaces with other systems. Describe the general types of processing (sequential versus random for inserts, updates, deletes and queries) required both for data entering the database, and data most frequently accessed. If any of this information is provided in ICD(s) or other documents, they may be referenced. Describe selected equations/algorithms/rules, disposition, and handling of un-allowed inputs. Also include decisions on how databases/data files will appear to the user.

· Performance and Maintenance Design decisions:

Instructions: Describe how performance and availability requirements will be met. Examples include:

· Describe design decisions on database distribution (such as client/server), master database file updates and maintenance, including maintaining consistency, establishing/ reestablishing and maintaining synchronization, enforcing integrity and business rules.

· Describe design decisions to address concurrence issues (e.g., how the data are partitioned or distributed to support multiple applications or competing update functions, if applicable).

· Describe design decisions to support Service Level Agreements (SLAs) for key functions supported by the database.

· Describe design decisions on backup and restoration including data and process distribution strategies, permissible actions during backup and restoration, and special considerations for new or non-standard technologies such as video and sound. Describe the impact this maintenance will have on availability.

· Describe design decisions on data reorganization (i.e., repacking, sorting, table and index maintenance), synchronization, and consistency, including automated disk management and space reclamation considerations, optimizing strategies and considerations, storage and size considerations (e.g., future expansion), and population of the database and capture of legacy data. Describe the impact this maintenance will have on availability.

· Describe design decisions to support purging and/or archiving of data to ensure performance and storage objectives are met. Describe the impact this maintenance will have on availability. Describe any needs to recall archived data back into the database.