• Describe expected reader. (You will expect mostly technical reader but also a super user, who is a system user but has some knowledge of the data. They may use this in the future to help ask for reports. They will also be able to make sure all the information they expected is being captured in the system.
  

• Version History (empty at this point perhaps)

• Copy System intro from your requirements spec
• Add a paragraph at the top explaining that this is the database design and that you will be defining tables and database administration strategy.

• Define any terms a user or programmer may need to know to read this. (Remember both read this.)

• Database type (most will choose mysql)
• How many servers?
• How many databases?
• Will you use replication to store a database copy locally for transaction use or just for reporting?
• Databases outside your system that you will be interfacing to, if any

• Entity Relationship Diagram
  

For each table:

• Table name
• Short table description
• Column names with type and length and if necessary, a short description
• Table Primary Key
• At least 2 lines of sample data.

(Note: If you prefer to just create the table and include the create table statement, that is okay for this class.)