CIS 498 Project Deliverable 3: Database and Programming Design

alflco

Main
Similar Questions

Home >Homework Answsers >Computer Science homework help

Project Deliverable 3: Database and Programming Design

Due Week 6 and worth 150 points

This assignment 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:

Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
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.

Points: 150	Project Deliverable 3: 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 incompletelycreated a database schema that supports the companyâ€™s business and processes.	Insufficiently created a database schema that supports the companyâ€™s business and processes.	Partiallycreated a database schema that supports the companyâ€™s business and processes.	Satisfactorilycreated a database schema that supports the companyâ€™s business and processes.	Thoroughlycreated 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.	Partiallyexplained 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.	Satisfactorilycreated database tables with appropriate field- naming conventions. Satisfactorily identified primary keys and foreign keys. Satisfactorilyexplained how referential integrity will be achieved.	Thoroughlycreated 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).	Thoroughlynormalized 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.	Partiallycreated 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.
Section 2: Revised Gantt Chart / Project Plan
2. Update the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks. Weight: 15%	Did not submit or incompletely updated the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks.	Insufficiently updated the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks.	Partially updated the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks.	Satisfactorily updated the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks.	Thoroughly updated the Gantt chart or project plan (summary and detail) template, from Project Deliverable 2: Business Requirements, with all the project tasks.
3. Clarity, writing mechanics, and formatting requirements Weight: 10%	More than 8 errors present	7-8 errors present	5-6 errors present	3-4 errors present	0-2 errors present