240 final/IT240 Example Project Proposal x
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 x
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 x
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.
FinalProjectSpecs 2020 x
IT-240 Intro to Databases Final Project: Applied Database Prototype Project
Project Overview and Description of Deliverables
The final project is accomplished in five sequential stages; each stage contributes to a final report:
1. Ideation – Identify the subject area, the business or organizational area of interest:
a. Describe the subject area briefly; no more than a few sentences should be necessary.
b. Use the case studeies in the texbook as examples
2. 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
Use the case studies as examples.
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
3. Entity-Relationship/Data Modeling – Use the Vertabelo online tool for design work:
a. Develop appropriate conceptual model
b. Develop appropriate logical model
c. Develop appropriate physical model for implementation in Access
i. normalize the tables; provide the functional dependencies, PKs, and FK
ii. identify the constraints
d. Document your efforts with appropriate diagrams and explanations for the final approach you have chosen.
e. Provide examples of the create table SQL appropriate to each stage
4. 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
5. 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?
Outline Template FinalProjectSpecs 2020 x
Do NOT include any text in red; they are prompts.
[Name of Project]
[Your Full Name]
Ideation – this is an introduction to the business Identify the subject area, the business or organizational area of interest:
Describe the subject area briefly; no more than a few sentences should be necessary.
Use the case studies in the textbook as examples
Project Definition – Describe the type of problem you wish to address with a database:
Problems and concerns to be addressed
Identify the problems and frame them them in terms of Delete/update/insertion issues
Examples of the current approach – include actual or mock-ups of relevant forms, reports, lists, etc.
The new approach Discuss how your approach should eliminate Delete/Update/Insert problems and help manage this issue in the future
Entity-Relationship/Data Modeling – Use the Vertabelo online tool for design work:
Conceptual model brief discussion of the model/intro
i. The model
ii. SQL for the model
Logical model brief discussion of the model/intro
i. The model
ii. SQL for the model
Physical model for implementation in Access brief discussion of the model/intro
i. Function dependencies and the normalized tables
ii. Constraints, assumptions, and relations include a realtionship table
iii. Physical model and SQL
Database Prototype – Test your final Physical Model from ER/Data Modeling:
Implement the tables structures you identified in ER/Data Modeling
Populate these tables with suitable amounts of illustrative data
Test your database application with relevant SQL queries
Provide a brief discussion of the prototype.
Mention that it is attached.
Summary: Results and Recommendations – Review and summarize your project results, recommendations; describe next steps, if any; be sure to address questions like:
The DB Prototype Did your modeling work? Could you create a useful database prototype?
Issues with the model What went wrong? What did you fix, what didn’t you fix?
Next Steps What would be any next steps if you wanted to take this further?
IT240 Example Project Proposal x
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”
Table of Contents.html
INTRODUCTION TO DATABASES – 2019-2020 Spring – Final Project
1. IT240FinalProjectSpecs
2. Outline Template FinalProjectSpecs 2020
3. IT240 Example Project Proposal
Hawkins Soccer Club Database Design
Zihan Wang
I. Ideation
Hawkins Soccer Club is a community-based soccer club for youth aged 15 to 35 years. The club is managed by a team manager with the help of several other technical personnel. The technical team includes the head coach, assistant coach, and goalkeeper coach who trains the goalkeeper. The club has a well thought program of recruiting its players. The players undergo medical tests including blood pressure test, heartbeat rate, assess previous medical history, plus other key physical examinations. Players are signed up according to the position they play in line with standard soccer game formation. In its daily operations, Hawkins Soccer Club records the matches attended, match captain, player substitutions, goals scored, penalty shootouts, disciplinary cards issued, and injuries incurred during matches. The numerous records need to be stored in a logical and consistent structure. Thus, the need for a relational database. Relational database’s design goal is to meet the ACID properties effectively. ACID is the abbreviation for A – atomicity, C – consistency, I – isolation, and D – durability. The properties in conjunction with integrity constraints accuracy, and validity of stored data. Comment by Evelyn Lulis: This does not belong here; perhaps in the next phase of the project when you normalize the data
II. Problem Definition – I NO PRONOUNS wish to solve the problem of data redundancy and inconsistencies associated with data manipulation anomalies. Hence, the aim is to organize and structure Hawkins Soccer Club data for efficient and consistent management.
A. Problems and concerns to be addressed
Update:
Insert:
Delete:
Data manipulation of unstructured data can lead to inconsistencies called data anomalies. Inconsistencies are common in related tables where the main table, called parent table, has a dependent reference table, called child table. There are three data anomalies that I will address: insertion anomaly, modification anomaly, and deletion anomaly. Insertion anomaly occurs when a new record is added to a child table but whose record does not exist in its referenced parent table. Deletion anomaly occurs when a record in the parent table is deleted without its related records in the referenced child tables. As such, both insertion anomalies and deletion anomalies result in orphan child tables. On the other hand, modification anomaly can occur when updating records in a database. Records can be updated in a main table but leave out the referenced tables and vice versa. Comment by Evelyn Lulis: This is in the general; you need to address your specific data as we did in class
B. Examples of the current approach
The current approach involves entry of data in spreadsheets using Microsoft Excel. Workbooks exist that contain various worksheets of data. The data is organized in tables and columns that describe the rows of data inserted. Information stored include biodata of the players, matches, and individual player performance. Comment by Evelyn Lulis: You need sample data so can address the issues n parts 2a and 2c
C. The new approach Comment by Evelyn Lulis: This belongs in Part 2 when you normalize the data.
You might be able to extract the info you need to address the Update/Insert/Delete issues.
Update:
Insert:
Delete:
My approach will make use of integrity constraints to guarantee accuracy, consistency, and validity of data stored. Integrity constraints utilized in the Hawkins Soccer Club database include the following: required data, attribute domain constraints, multiplicity, entity integrity, referential integrity, and general constraints. Required data constraint is a type of integrity constraint suitably applied on attributes whose fields must hold valid values but never contain null values. Attribute domain constraint is a type of integrity constraint ideally enforced on attributes that should only accept defined set of values. For example, a marital status attribute can be set to accept either single or married as the only valid values. Multiplicity constraint is a type of integrity constraint defined on specific relationships that exist between data in a relational database. It is commonly applied in a one-to-many relationship. For example, a soccer team can have many players, but a soccer player can be legally signed to only one soccer team. As such, multiplicity constraint would ensure that no soccer player exists in more than one soccer team. Entity integrity is a type of integrity constraint that is enforced on primary keys of attributes to ensure that they hold valid values which must be unique always. It also ensures that primary key attribute fields do not hold null values. Referential integrity constraint is defined on two related tables. If a foreign key in the first table references a primary key in the second table, then each value of the foreign key in the first table must either be available in the second table or be null. This ensures that no orphan records exist, that is, records existing in the first table with a foreign key that does not match a primary key in the second table. The first table is thus considered the child table while the referenced table is referred to as the parent table. Finally, general constraint is a type of integrity constraints that limits permissible range of values to be entered in an attribute field. Comment by Evelyn Lulis: No pronouns
Hawkins Soccer Club DB Design
Zihan Wang
I. Ideation
Hawkins Soccer Club is a community-based soccer club for the youth aged 15 to 35 years. The club is managed by a team manager with the help of several other personnel. The team includes the head coach, assistant coach, and goalkeeper coach who specially trains the goalkeeper. The club has a well thought program of recruiting its players. The players undergo medical tests including blood pressure test, heartbeat rate, assess previous medical history, plus other key physical examinations. Players are signed up according to the position they play in line with standard soccer game formation. In its daily operations, Hawkins Soccer Club records the matches attended, match captain, player substitutions, goals scored, penalty shootouts, disciplinary cards issued, and injuries incurred during matches.
The purpose of this study is to design a relational database management system for Hawkins Soccer Club. The database would be developed procedurally from conceptual model, logical model, physical model in MS Access, and eventually testing with real-world data to ascertain conformance to relational Standard Query Language rules.
II. Problem Definition
Wish to solve the problem of data redundancy and inconsistencies associated with data manipulation anomalies. Hence, the aim is to organize and structure Hawkins Soccer Club data for efficient and consistent management.
A. Problems and concerns to be addressed
Insert: When inserting new records into the current Excel sheet, there is risk of mismatch between excel rows and the column headers. As such, inconsistencies exist between highly segmented Excel tables. For example, when adding new players; player address information can be mixed up with player personal information.
Update: Data modification in Excel is achieved by search and replace method. It can be done per workbook, worksheet, or per column containing specific information. The problem is the columns are not interlinked with related data. Hence either part of the records is updated, or wrong records updated.
Delete: Since several tables have been created in a single Excel sheet, deletion of specific information is tedious and time consuming. Caution has to be exercised not to delete records in other tables lying in the same Excel sheet row.
Below is attached spreadsheet table sampled from the current Hawkins Soccer Club data, it forms the basis of this study.
B. Examples of the current approach
The current approach involves entry of data in spreadsheets using Microsoft Excel. Workbooks exist that contain various worksheets of data. The data is organized in tables and columns that describe the rows of data inserted. Information stored include biodata of the players, matches, and individual player performance.
C. The new approach
The new approach will organize existing data into six entities namely: players, player details, addresses, matches, match captains, and goals. The players table would store basic information about player including name, joining date, and player position. Players table is linked to player details that further stores more detailed biodata related to each player. Moreover, every player has got specific address information that is stored in the address table. The attached sample data describes segmentation and relation of the three tables.
PLAYERS(PlayerID, LastName, FirstName, JoinDate, PlayerPosition) Comment by Evelyn Lulis: Use this format, do nto copy and paste from Access
PLAYER_DETAILS( ALL of the fields here belong in the player table
Who are the address for?
Try:
The PLAYER table should include all the info ab out a player.
Not certain Position should be in this table
Players( PlayerID, LastName, FirstName, JoinDate, PlayerPosition, DOB, gender, martital status, etc.
You need more info.
Perhaps a table of COACH, billing/fee info such as Account,
Final Part 3/prototype x
Final Project Prototype
Submit:
— The Word document you have been building for this project
with this assignment appended to it.
–Your prototype DB in SQLite3, or Access.
Part 3.
To help users evaluate your database vision and its usability, you generally create prototype queries and views (reports) to illustrate your specific design and its features. Create example queries and views (reports) in SQL; employing some sample data, verify your ER model(s) will support those use cases, or accomplishments, or activity, etc. demanded by your chosen area of application.
You may use SQLite3, or Access, to create your prototype.
Also, the included datatemplate.csv file shows how you might use the list from the San Juan SBC example to generate mock or made-up data for your project.
Do use made-up data.
Do not use data from a company you work for.
Make certain this section of your documentation includes:
1. The SQL for the tables you created
2. If you use Access, a copy of the Relationship
3. Copies of the SQL and results for all queries clearly identified as in this example:
Access
top 3 artists by playlist tracks (appearance)
top 3 artists by playlist tracks (appearance)
CountOfArtist
Artist
32
80s Chartstarz
12
Sam Cooke
5
Beach Boys
5
Bebe Rexha
SELECT Count(ARTIST.Artist) AS CountOfArtist, ARTIST.Artist
FROM ARTIST INNER JOIN TRACK ON ARTIST.ArtistID = TRACK.ArtistID
GROUP BY TRACK.ArtistID, ARTIST.Artist
ORDER BY Count(ARTIST.Artist) DESC;
4. A working copy of your DB in SQLite3, or Access,
Final Part 3/SJSBC_Data_List_datatemplate.csv
BoatName Make Model Length OwnerLastName OwnerFirstName OwnerPhone Address City State ZIP CharterDate Amount CustomerName
Far Horizon Catalina Morgan 38 Princeton Darryl 206-543-6677 2345 15th NE Seattle WA 98115 21-Jun-12 $5,000.00 Smith, Sally
Ebb Tide Hunter 38 38 Tulsa Bill 503-486-8786 1324 24th NE Portland OR 97215 21-Jun-12 $5,500.00 Sailors, Mike
Far Horizon Catalina Morgan 38 Princeton Darryl 206-543-6677 2345 15th NE Seattle WA 98115 28-Jun-12 $5,000.00 Tully, Jason
Far Horizon Catalina Morgan 38 Princeton Darryl 206-543-6677 2345 15th NE Seattle WA 98115 4-Jul-12 $5,000.00 Atkins, Merle
Foreign Shores Hans Christian 38 MK II 38 Berkely George 425-765-4455 4567 35th W Bellevue WA 98040 4-Jul-12 $6,000.00 Smith, Sally
Seafarer V Endeavour 37 37 Tulsa Bill 503-486-8786 1324 24th NE Portland OR 97215 4-Jul-12 $4,500.00 Travis, Chet
Seafarer V Endeavour 37 37 Tulsa Bill 503-486-8786 1324 24th NE Portland OR 97215 18-Jul-12 $4,500.00 Watson, John
Midnight on the Water Sabre 32 32 Oxford Kelly 503-578-7574 2435 36th SE Astoria OR 97103 18-Jul-12 $4,000.00 Renborn, “Doc”
Ebb Tide Hunter 38 38 Tulsa Bill 503-486-8786 1324 24th NE Portland OR 97215 27-Jul-12 $5,500.00 Sailors, Mike
Foreign Shores Hans Christian 38 MK II 38 Berkely George 425-765-4455 4567 35th W Bellevue WA 98040 27-Jul-12 $6,000.00 Tully, Jason
Stuff Produced by Purchases Someone
Rollerskates Owned by Rents Buyer
Books Rates Renter
Courses Buys Consumer
Concert Attendance Guests
name date capacity date count names geolocation
Courses/Services Staffed By Registers Members
Name genre Name Position/Specialty Date Fee Name Age Gender