# Database Design

Instructions:   
Describe the design of all database management system (DBMS) files and non-DBMS files associated with the system.

  

Provide a comprehensive data dictionary showing data element name, type, length, source, validation rules, maintenance (create, read, update, delete (CRUD) capability), data stores, outputs, aliases, and description. 

### Data Objects and Resultant Data Structures

Instructions: For each functional data object, specify the data structure(s) which will be used to store and process the data. Describe any data structures that are a major part of the system, including major data structures that are passed between components. List all functions and function parameters. For functions, give function input and output names in the description. Refer as appropriate to the decomposition diagrams.

### File and Database Structures

Instructions: Using the Logical Data Model (LDM), create a physical data model that describes data storage and manipulation in the systems architectural setting. Describe file structures and their locations. Explain how data may be structured in the selected DBMS, if applicable. For networks, detail the specific distribution of data. Note any changes to the LDM that occur because of software or hardware requirements.

### Database Management System Files

**Instructions**: Provide the detailed design of the DBMS files. Generally, this information should be documented in a separate data dictionary document that should be referenced within this section.

### Non-Database Management System Files

**Instructions**: Provide the detailed description of all non-DBMS files and include a narrative description of the usage of each file that identifies if the file is used for input, output, or both, and if the file is a temporary file. Also provide an indication of which modules read and write the file and include file structures (refer to the data dictionary). As appropriate, the file structure information should include the following:

*   Record structures, record keys or indexes, and data elements referenced within the records
    
*   Record length (fixed or maximum variable length) and blocking factors
    
*   Access method (e.g., index sequential, virtual sequential, random access, etc.)
    
*   Estimate of the file size or volume of data within the file, including overhead resulting from file access methods
    
*   Definition of the update frequency of the file (If the file is part of an online transaction-based system, provide the estimated number of transactions per unit of time, and the statistical mean, mode, and distribution of those transactions.)
    
*   Backup and recovery specifications
