Individual: Database Normalization

MEMORANDUM

TO: Professor Sanford Schram

FROM: Learning Team A

DATE: February 2, 2017

SUBJECT: Learning Team Status Update

The team discussed week assignment leaders, the drafting of the assignment templates and date for submitting individual assignment sections to weekly team lead.

Learning Team A has been in communications with each other in order to identify the types of databases available for incorporation into week four and five assignment. Rendezvous time and dates were scheduled for the team to meet at the downtown San Diego Library to continue discussing assignments. The next scheduled dates will solidify the needed database and review the skeleton powerpoint.

Learning Team A’s progress is satisfactory. (Dennis, James, Leonard, Nicolas) have communicated regarding the Art Museum Course of Action (COA) SQL server scripts and Queries 1-6. Each team member is works diligently to keep other team members appraised of status while balancing other class requirements: participation, reading, discussion and weekly individual assignments. We will continue to coordinate our collaborative efforts.

Week 2:

• Introduce new member and add to team Charter. – 2/2/2017 personal introductions are needed

• Analyze requirements needing to be met. – Completed

• Slide Templates created. – Completed

The presentation to the CEO should include information on the database development life cycle which includes:

• • An ERD.

  • How you approached normalization.

  • Any decisions that were made around keys, data types, constraints, etc.

  • Considerations that were made around the creation of the physical database

  • The value of queries included in the project. 

• Identify the area requiring a database. – Completed

  • Identify a POS database to support the identified Art subsystem:  Invoicing, Inventory Management, Customer Management, and Employee Management.

  • Include a primary key and a minimum of five attributes using appropriate data types.

  • Included database must be normalized to at least the 3rd Normal Form.  Foreign keys must be set up with constraints and relationships established between entities.

  • The database will need to be populated with test data.  At least ten records for each subsystem.

  • Minimum of four queries created to provide management insight into each subsystem.  Two of these queries must join data from one or more other entities.

Week 3:

• Define the SQL database. – In Progress

• Create SQL database account query. – TBD

• Create SQL database insert account query. – TBD

• Load the SQL database with the data from the Chart of Accounts spreadsheet from the script. -TBD

• Test Chart of Accounts report. – TBD

• Prepare and load test data into the SQL database. - Require week three steps.

• Submit the data load script into the learning team assignments tab. – Require week 3 steps.