ent consists of two (2) sections: a design document and a revised Gantt chart or project plan. You must submit both sections as separate files for the completion of this assignment. Label each file name according to the section of the assignment for which it is written. Additionally, you may create and / or assume all necessary assumptions needed for the completion of this assignment.

One (1) of the main functions of any business is to transform data into information. The use of relational databases has gained recognition as a standard for organizations and business transactions. A quality database design makes the flow of data seamless. The database schema is the foundation of the relational database. The schema defines the tables, fields, relationships, views, indexes, and other elements. The schema should be created by envisioning the business, processes, and workflow of the company.

Section 1: Design Document

1. Write a five to ten (5-10) page design document in which you:

a. Create a database schema that supports the company’s business and processes.

b. Explain and support the database schema with relevant arguments that support the rationale for the structure. Note: The minimum requirement for the schema should entail the tables, fields, relationships, views, and indexes.

c. Create database tables with appropriate field-naming conventions. Then, identify primary keys and foreign keys, and explain how referential integrity will be achieved.

d. Normalize the database tables to third normal form (3NF).

e. Create an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia. Note: The graphically depicted solution is not included in the required page length but must be included in the design document appendix.

f. Explain your rationale behind the design of your E-R Diagram.

g. Create a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia. Note: The graphically depicted solution is not included in the required page length but must be included in the design document appendix.

h. Explain your rationale behind the design of your DFD.

i. Create at least two (2) sample queries that will support the organizational reporting needs.

j. Create at least two (2) screen layouts that illustrate the interface that organizational users will utilize.

Your assignment must follow these formatting requirements:

This course requires use of Strayer Writing Standards (SWS). The format is different than other Strayer University courses. Please take a moment to review the SWS documentation for details.

Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.

Include charts or diagrams created in MS Visio or Dia as an appendix of the design document. All references to these diagrams must be included in the body of the design document.

Section 2: Revised Gantt Chart / Project Plan

Use Microsoft Project or an open source alternative, such as Open Project, to:

2. Update the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks.

The specific course learning outcomes associated with this assignment are:

Describe the various integrative functions and processes within the information systems area, including databases, systems analysis, security, networking, computer infrastructure, human computer interaction, and Web design.

Demonstrate the ability to evaluate organizational issues with integrative technological solutions.

Apply integrative information technology solutions with project management tools to solve business problems.

Use technology and information resources to research issues in information technology.

Write clearly and concisely about strategic issues and practices in the information technology domain using proper writing mechanics and technical style conventions.