it 240 final project
240 final/IT240 Example Project Proposal.docx
IT240 Example Project Proposal: Definition/Description
Project Description
My work at Wedgewood Pacific requires me to track computer assignments to all employees, maintain a list of locations where each computer should be found, and audit the equipment assignments and verify location periodically.
The basis for most of my work is a simple spreadsheet table, attached below.
This computer assignments spreadsheet is the only source of information about who has been issued which equipment, or if the equipment has been reissued, or if it has gone to 'SURPLUS'.
When employees report equipment problems, I have to use this table to begin to identify where they are located, the appropriate departmental codes needed to charge for the support ticket. This information is located in two other tables, one (EMPLOYEE) containing information on the employees and their locations, and another (DEPARTMENT) holding the departmental charging codes. Currently these tables are not linked together, so they must be searched by hand in order to identify important information.
For this project I plan to attempt to normalize the WPC Computer Assignments table into two or more relational tables, to test linking these new tables to our existing enterprise database, and to test query designs for tracking current assignments, equipment locations and budget codes for use in support/help desk incident charges.
Wedgewood Pacific Corporation
WPC Computer Assignments
SerialNumberMakeModelProcessorTypeProcessorSpeedMainMemoryDiskSizeAssigned ToDateAssigned ToDate
9871234HP Pavilion 500-210qe Intel i5-4530 3.006.0 GBytes 1.0 TBytes James Nestor15-Sep-14George Smith21-Oct-14
9871245HP Pavilion 500-210qe Intel i5-4530 3.006.0 GBytes 1.0 TBytes Rick Brown15-Sep-14Ken Numoto21-Oct-14
9871256HP Pavilion 500-210qe Intel i5-4530 3.006.0 GBytes 1.0 TBytes Tom Caruthers15-Sep-14
9871267HP Pavilion 500-210qe Intel i5-4530 3.006.0 GBytes 1.0 TBytes Heather Jones15-Sep-14
9871278HP Pavilion 500-210qe Intel i5-4530 3.006.0 GBytes 1.0 TBytes Tom Jackson15-Sep-14
9871289HP Pavilion 500-210qe Intel i5-4530 3.006.0 GBytes 1.0 TBytes George Jones15-Sep-14
6541001Dell OptiPlex 9020 Intel i7-4770 3.408.0 GBytes 1.0 TBytes James Nestor21-Oct-14
6541002Dell OptiPlex 9020 Intel i7-4770 3.408.0 GBytes 1.0 TBytes Rick Brown21-Oct-14
6541003Dell OptiPlex 9020 Intel i7-4770 3.408.0 GBytes 1.0 TBytes Mary Jacobs21-Oct-14
6541004Dell OptiPlex 9020 Intel i7-4770 3.408.0 GBytes 1.0 TBytes Rosalie Jackson21-Oct-14
6541005Dell OptiPlex 9020 Intel i7-4770 3.408.0 GBytes 1.0 TBytes Richard Bandalone21-Oct-14
6541006Dell OptiPlex 9020 Intel i7-4770 3.408.0 GBytes 1.0 TBytes Mary Abernathy21-Oct-14
Note:Computer reassignments are shown in the second set of "Assigned To" and "Date" Columns. If another reassignment is made, add another set of these columns.
Note:When a computer is retired from server, shown "Assigned To" as "Surplus"
240 final/IT240FinalProjectSpecs.docx
IT-240 Spring 2020 Final Project: Applied Database Prototype Project
Project Overview and Description of Deliverables:
The final project is accomplished in four sequential stages; each stage contributes to final report:
1. Project Definition - Describe the type of problem you wish to address with a database:
a. Describe the concern or problem you will try to address with a small database
b. Provide examples of the current (possibly hypothetical) approach - include actual or mock-ups of relevant forms, reports, lists, etc.
c. Discuss how your approach should eliminate Delete/Update/Insert problems and help manage this issue in the future
2. Entity-Relationship/Data Modeling - Use the Vertabelo online tool for design work:
a. Develop appropriate conceptual, logical and physical models;
b. Document your efforts with appropriate diagrams and explanations for the final approach you have chosen
c. Provide examples of the create table SQL appropriate to each stage
3. Create Database Prototype - Test your final Physical Model from ER/Data Modeling:
a. Implement the tables structures you identified in ER/Data Modeling
b. Populate these tables with suitable amounts of illustrative data
c. Test your database application with relevant SQL queries
4. Summary: Results and Recommendations - Review and summarize your project results, recommendations; describe next steps, if any; be sure to address questions like:
a. Did your modeling work? Could you create a useful database prototype?
b. What went wrong? What did you fix, what didn't you fix?
c. What would be any next steps if you wanted to take this further?
Final Document Summary:
Finally, please create a 5 page (e.g. pages bulleted w/ screen caps) document summarizing the project; could be the basis for a short report in a staff/management meeting. Requested pages are:
1. Project Definition
2. Final 'Physical' ER/Data-Model
3. The Prototype Database & Tables
4. Test Results (SQL and Query results)
5. Recommendations and Next Steps
Deadlines:
1. Project Definition: End of Week 7
2. ER/Data Modeling appended to #1: End of Week 8
3. Database Prototype and Testing appended to #2: End of Week 9
4. Project Summary Document (Week 10) appended to #3: Last Day of Class
240 final/Zihan Wang Final Project Part 1 .docx
Zihan Wang
Place the name of the project here
I. Introduction
This section describes the company, what it does, what employees do, et.
Use the case studies from the textbook as examples.
II. Project Description
A. Concern/Problem to be addressed
Phrase your discussion in terms of
Delete:
Update:
Insert:
B. Examples of the current approach
[include actual or mock-ups of relevant forms, reports, lists, etc. ]
C. Resolution of the issues
Discuss how your approach should eliminate the specific problems you identified in II.A.
Phrase your discussion in terms of
Delete:
Update:
Insert:
My Final project will make a database about the Veterinary. There will be several sources about the assignment, including Owner Information, Pet Information, Pet Procedures, Pet Supplies, etc.
There was extremely limited data given initially. We have added Supplies and Procedures tables with many-to-many relationship with Pet Information table. Since a Pet can have more than one Procedure and a procedure can be performed on more than one pet, there has to be an associative table to hold this relationship. Similarly, Pet can get more than one supply and one supply can be supplied to more than one, there is another associative table to hold this relationship.