ESSAY : Database and Programming

 Database and Programming Design

This assignment consists of two (2) sections: a design document and a revised Gantt chart or project plan (I will update Gantt chart).  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.

	Database and Programming Design
Criteria	Unacceptable Below 60% F	Meets Minimum Expectations 60-69% D	Fair 70-79% C	Proficient 80-89% B	Exemplary 90-100% A
Section 1: Design Document
1a. Create a database schema that supports the company’s business and processes. Weight: 10%	Did not submit or incompletely created a database schema that supports the company’s business and processes.	Insufficiently created a database schema that supports the company’s business and processes.	Partially created a database schema that supports the company’s business and processes.	Satisfactorily created a database schema that supports the company’s business and processes.	Thoroughly created a database schema that supports the company’s business and processes.
1b. Explain and support the database schema with relevant arguments that support the rationale for the structure. Weight: 10%	Did not submit or incompletely explained and supported the database schema with relevant arguments that support the rationale for the structure.	Insufficiently explained and supported the database schema with relevant arguments that support the rationale for the structure.	Partially explained and supported the database schema with relevant arguments that support the rationale for the structure.	Satisfactorily explained and supported the database schema with relevant arguments that support the rationale for the structure.	Thoroughly explained and supported the database schema with relevant arguments that support the rationale for the structure.
1c. Create database tables with appropriate field-naming conventions then identify primary keys and foreign keys, and explain how referential integrity will be achieved. Weight: 10%	Did not submit or incompletely created database tables with appropriate field-naming conventions. Did not submit or incompletely identified primary keys and foreign keys. Did not submit or incompletely explained how referential integrity will be achieved.	Insufficiently created database tables with appropriate field-naming conventions. Insufficiently identified primary keys and foreign keys. Insufficiently explained how referential integrity will be achieved.	Partially created database tables with appropriate field-naming conventions. Partially identified primary keys and foreign keys, explained how referential integrity will be achieved.	Satisfactorily created database tables with appropriate field- naming conventions. Satisfactorily identified primary keys and foreign keys. Satisfactorily explained how referential integrity will be achieved.	Thoroughly created database tables with appropriate field-naming conventions. Thoroughly identified primary keys and foreign keys. Thoroughly explained how referential integrity will be achieved.
1d. Normalize the database tables to third normal form (3NF). Weight: 5%	Did not submit or incompletely normalized the database tables to third normal form (3NF).	Insufficiently normalized the database tables to third normal form (3NF).	Partially normalized the database tables to third normal form (3NF).	Satisfactorily normalized the database tables to third normal form (3NF).	Thoroughly normalized the database tables to third normal form (3NF).
1e. Create an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia. Weight: 10%	Did not submit or incompletely created an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Insufficiently created an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Partially created an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Satisfactorily created an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Thoroughly created an Entity-Relationship (E-R) Diagram through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.
1f. Explain your rationale behind the design of your E-R Diagram. Weight: 5%	Did not submit or incompletely explained your rationale behind the design of your E-R Diagram.	Insufficiently explained your rationale behind the design of your E-R Diagram.	Partially explained your rationale behind the design of your E-R Diagram.	Satisfactorily explained your rationale behind the design of your E-R Diagram.	Thoroughly explained your rationale behind the design of your E-R Diagram.
1g. Create a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia. Weight: 10%	Did not submit or incompletely created a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Insufficiently created a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Partially created a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Satisfactorily created a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.	Thoroughly created a Data Flow Diagram (DFD) through the use of graphical tools in Microsoft Visio or an open source alternative such as Dia.
1h. Explain your rationale behind the design of your DFD. Weight: 5%	Did not submit or incompletely explained your rationale behind the design of your DFD.	Insufficiently explained your rationale behind the design of your DFD.	Partially explained your rationale behind the design of your DFD.	Satisfactorily explained your rationale behind the design of your DFD.	Thoroughly explained your rationale behind the design of your DFD.
1i. Create at least two (2) sample queries that will support the organizational reporting needs. Weight: 5%	Did not submit or incompletely created at least two (2) sample queries that will support the organizational reporting needs.	Insufficiently created at least two (2) sample queries that will support the organizational reporting needs.	Partially created at least two (2) sample queries that will support the organizational reporting needs.	Satisfactorily created at least two (2) sample queries that will support the organizational reporting needs.	Thoroughly created at least two (2) sample queries that will support the organizational reporting needs.
1j. Create at least two (2) screen layouts that illustrate the interface that organizational users will utilize. Weight: 5% Â	Did not submit or incompletely created at least two (2) screen layouts that illustrate the interface that organizational users will utilize.	Insufficiently created at least two (2) screen layouts that illustrate the interface that organizational users will utilize.	Partially created at least two (2) screen layouts that illustrate the interface that organizational users will utilize.	Satisfactorily created at least two (2) screen layouts that illustrate the interface that organizational users will utilize.	Thoroughly created at least two (2) screen layouts that illustrate the interface that organizational users will utilize.

SAMPLE SOLUTION

A relational database is an important part of organizational management as it allows organizations to easily find critical information from a detailed pool of data. The database also allows storing and retrieving critical information in an organization. This task looks at the use of relational databases and warehousing, a detailed presentation of the database schema and the data tables with their relevant field naming.
The need for the use of relational databases and warehousing and the Efficiencies gained for the executive oversight
Any data generated by an organization can only make meaning when they are fully interpreted and linked to the desired outcomes. Consequently, it is necessary to incorporate a method that relates the data for the benefit of the organization. A data warehouse is a system which will likely offer the analytical components which are necessary in enhancing process that are important in ensuring that the company is…