/Final_Database_Project_CSCI52

Periodic Table of Elements Repository

Primary LanguageSQLPL

Final_Database_Project_CSCI52

Periodic Table of Elements Repository


each of the large subheadings represents a directory container for SQL code


general tasks

compiling final sql db creation script (RJ-- in progress)
testing the final sql db creation script (RJ-- in progress)
intro statement
data normalization page (RJ-- in progress)
description of each of the components in the script
put final files together
write readme with instructions for professor
submit project

project_design

description:

files from our design submission

contains:

erd.jpg

data_definition_language

description:

any tables / views in the db should have a ddl statement in this directory

contains:

data_definition_language.sql

requirements to fulfill:

SQL Joins, Views, subqueries including nested subquery techniques (15 points), RJ -- in progress

Data elements design including gathering requirements (15 points)

Database entities definition including attributes of the objects, data types, and constraints/restrictions on the attributes (15 points)

completed tables (data and ddl):

table name , person responsible for data

block , RJ

categories , RJ

element_category , RJ

main , MZ

elec_config_mapping, RJ

physical_properties, RJ MZ

atomic_properties, RJ MZ

electron_configuration, RJ

period, RJ

natural occurence, RJ

tables that need building:

table name , person responsible for data

group

data_control_language (this section complete RJ)

description:

we should write some statements to create user roles to grant / restrict privileges. RJ

contains:

data_control_language.sql RJ

requirements to fulfill:

Database security and administration to the extent covered in chapter 6 (5 points) RJ

data_manipulation_language

description:

any statements to do with the following actions on data in the db: retrieve, add, modify, or delete.

contains:

data_manipulation_language.sql

requirements to fulfill:

Use of UDT, UDF/procedures, and transactions (15 points)

Below are other project requirements that need to be organized into tasks:

Triggers or other database concepts to the extent these later topics can be covered in class toward the end of the semester (5 points).

Other– overall quality of the report (5 points)