Database Design and Implementation Using MS Access

Requirements

1. Model
• The model must be relational with at least 4 different relations (tables)
• Each relation must be identified using suitable primary key
• The relations must be described using suitable attributes (columns)
• The attributes could be constrained using suitable constraints (i.e., unique, not null, equal/not equal to, greater/smaller than, later/earlier than, etc.)
• The relations could be interlinked using suitable pairing of foreign keys/unique keys
• The model must be illustrated using suitable diagram (i.e., entity-relationship diagram or data diagram produced using a graphical editor or directly using MS Access)

2. Data Dictionary
• The data dictionary must specify the entire schema of the database
• Each table specification must describe its columns using information about the name, data type and constraints as well as its role in the table (i,e., primary key, unique key, foreign key, indexed field, hashed field, etc.)
• The data dictionary must be presented in a suitable format (you can draw a table using Word or other editors, or you can take a screenshot in Design View of Access)

3. Database
• The database must be stored in a single MS Access file named using combination of the code of the workshop group, the name of the group and the Student ID (i.e., W1-A-123456789)
• The database must include both the database tables of the database designed by the group and the individual database forms and database reports created by the student

4. Test data
• Each table in the database must include at least 5 records of data in it
• The test data in each student database must be different from the data of the other members of the same group

5. Queries
• Each student in the group must design at least one query for entering data and implement at least one form for entering data into one table
• The queries and the forms of the students in each group must be different for each member of the same group

6. Database forms
• Each student in the group must design at least one query for storing data and implement at least one form for entering data into one or more tables
• The queries and the forms of the students in each group must be different for each member of the same group

7. Database reports
• Each student in the group must design at least one query for retrieving information from one or more tables and implement at least one report for presenting it
• The queries and the reports of the students in each group must be different for each member of the same group

8. Written Group Report
• Each group must prepare one written report to present the data model, data dictionary and database implementation
• The group report must by made available to all members of the group and must be submitted together with the individual report
• The group report must be named using the name of the workshop group and the name of the group (i.e, W1-A.pdf)

9. Written Individual Report
• Each student must prepare one written report to present the test database data and the implementation of the database forms and reports
• The individual report must include a reflection on the group work (distribution of the work amongst the members of the group, log of the meetings of the group, evaluation of the work of the group and self-evaluation)
• The individual report must be named using the ID of the student (i.e, 123456789.pdf)

Introduction
The aim of this report is to present the database model, data dictionary and database implementation details for the Bike Shop Database. There will be a brief description of the Bike Shop database for better understanding of the context of the database. For simplicity of the database, a simple database for the Bike Shop has been considered. The scope is limited only within shipment of orders for bikes by different courier service providers.
Brief Description of the Bike Shop Database
Bike Shop is a small biker cycle shop. It sources bikes from multiple bi-cycle makers when they gets an order from a customer. Then they checks the bikes and ships the same to customers once the customer clears the payment otherwise the bikes are kept in stock until they get another order or the previous order is fulfilled. Once, an order is shipped successfully, the details of the shipment and order is entered into the database.
The scope of the database is limited to,
• Keeping records of the employees
• Keeping records of all bikes sold or in stock
• Keeping records of all successful shipment of orders
• Keeping details of the shipping partners
The owner is interested to,
• Have a single interface for entering all shipment details using forms
• Enter details of a new employee or records of orders handled by the employees using forms
• Find all details of shipments when the shipping partner’s name is given
• Find cases of delayed shipping when shipping takes more than 15 days from the order date and generating a report on that.
• Get a report on the Total shipping cost for all shipments
• Find details of bikes still in stock...

This is only a preview of the solution. Please use the purchase button to see the entire solution