ISDS 3110 Final Project
Spring 2013
Due Date: Monday April 22nd by NOON
You should complete this project in groups of 2 -4 students (NO MORE THAN 4!).This is a group project but each group is to work
on the project individual of any other group (i.e. no two groups should turn in the same work). There are many different ways to
develop the E-R diagram and implement this database. There is no ONE right answer. The project requirements are as follows:










You will create a logical E-R model for a database to meet the business requirements of a car dealership, Quality Imports.
Information about Quality Imports’ business, data, and reporting requirements is provided in the business case attached. You
should draw this model using Crow’s Foot methodology.
The E-R model should contain all of the major entities that are required to support the operations of the business. Make sure to
include connectivities (both min and max) and resolve all M-N relationships. Attributes for each table should be shown as we
did in class or you can create a relational schema. Make sure to indicate primary keys and foreign key links.
You will implement this database using Access. In Access, you should create all the tables necessary for this database
indicating primary keys and enforcing referential integrity through relationships. You can set the cascade options as you feel
necessary.
Information about required tables, forms, reports and queries follows the case information. (Please note that the forms
mentioned may not be enough to run the entire database. I have not included all forms necessary to help keep the project from
becoming too overwhelming.)
Your database should include a switchboard for easy navigation through all forms, reports, AND queries.
Make sure all tab order is correct on forms, reports.
Make sure all labels and data are readable when forms/reports/queries are opened.
Use list boxes and combo boxes on forms where appropriate
Create buttons on forms which aid users in completing tasks such as print, next record, etc. instead of relying on the built in
navigation of access. Novice access users won’t know about the built in navigation.
Although some example data is included, you will definitely need to make up more information! You should populate your
database to test the forms and queries.
Since every group will complete the same project, there is some competition. Keep that in mind when creating your database, reports,
queries, etc.. Little things add up!!
What should be turned in?
1. A paper copy of the COMPLETE E-R Diagram and table structures with a cover sheet.
2. A working version of your database uploaded to Moodle.
Presentation Requirements:
Each group will be required to present their final project to me during a scheduled meeting. The presentations will be no more than 15
minutes in length and should include the following:
» You should show your relationships window in access and discuss the relationships and integrity
» A run through of your Access database. You should have some sample data to enter during the presentation. Your database
should also already contain data so your queries can be tested
» Time for questions
If you miss your actual presentation, your grade for the project will be lowered by an additional 10 points.
Each student will “rate” his or her own group members based on the work performed. This rating will be averaged and used to
determine the percentage of the project grade you will receive. For example, if everyone in your group gives you a 100%, you will get
a 100% of the grade your group earned. If you receive an 80%, 90%, and 100%, this averages to a 90%. In this case you would only
receive 90% of the grade your group earned. (So if your group earned an 80% on the project, your grade would calculate to a 72%.) I
have included the team member evaluation form so everyone will be aware of what their teammates will be using as a rating guide.
If you have a group member who is not participating at all on the project, you must have a meeting with all of your group members
and me to clear up the situation immediately.
Team Member Evaluation Form
Take a few minutes to carefully evaluate each member of your project team. Focus on their project performance and team
contribution. Try to ignore personality conflicts. This evaluation is confidential but results (not names) will be available if necessary
to group members since project final grades may be affected. Evaluate team member’s performance, including your own over the full
term of the project. You will be asked to rate each team member’s overall performance and contribution to the project on a scale of 0100. Assume the following grading scale for this evaluation:
90-100
80-89
70-79
60-69
0-59
A
B
C
D
F
Excellent Contribution
Above Average Contribution
Average Contribution
Below Average Contribution
What Contribution?
List the team members, including yourself alphabetically
Member 1: _____________________________________________________________
Member 2: _____________________________________________________________
Member 3: _____________________________________________________________
Member 4: _____________________________________________________________
Now, rate each team member on a scale from 0-100 on each of the following questions:
TM1
TM2
TM3
TM4
____
____
____
____
____
____
____
____
____
____
____
____
____
____
____
____
____
____
____
____
5. This person completed his/her assignments on schedule.
____
____
____
____
6. This person completed his/her assignments with little or no
assistance
____
____
____
____
7. This person attended team meetings and arrived on time.
____
____
____
____
8. This person was well prepared for team meetings.
____
____
____
____
9. I would like to work with this person on future project.
1. This person did his/her fair share of the work.
2. When required to do so, this person cooperated with other team
members.
3. This person is competent in the analysis and design techniques that
were taught in this course.
4. This person accepted his/her fair share of team responsibilities
when asked to do so.
Please take a moment and average each team members’ score and place the final average below:
TM1 ______________
TM2 ________________
TM3_______________
TM4______________
Now print this evaluation form and place it in a sealed envelope with your name printed on the front of the envelope. This evaluation
counts as a homework assignment so I have to have some way of knowing you completed it and turned it in.
Quality Imports Database
REQUIREMENTS
Quality Imports is an automobile dealership located on the “auto mile” (a strip of four-lane, nondivided
highway where approximately 12 dealerships are located in a blue collar suburb of a major Midwestern city.
Quality Imports is owned by Gary Newburg, its general manager, and two brothers, Paul and Frank Queen.
Quality Imports sells Mazdas, Fiats, Lancias, and the Lancia Strada line of vehicles (primarily passenger cars,
but also some light trucks). The company is only 6 years old, so it does not yet have a well-established
customer base. Buyers of these types of imported vehicles tend to be very particular and will search nationally
for the car of their choice. For example, one of Quality Imports’ customers flew from Chicago in his private
airplane just to buy a white fiat X19.
Quality Imports keeps basic information on both its salesmen and its customers. A salesman earns 1.5%
commission on each sale they make. Keep in mind their earn this percentage on the net amount of a vehicle
sale. So the amount after the options are added in and the trade-in and discounts are subtracted out.
Information about each car in inventory must also be stored. Basic information about the car will be kept along
with the date it was purchased, the amount it was purchased for, if it is new or used, and the price the dealer will
ultimately list it for when selling (list price). This list price is the starting price when a sales person negotiates
with a customer. Quality Imports realizes every customer wants a ‘deal’. So the list price will always be above
the purchase price. That way, a sales person has some wiggle room to give ‘discounts’ to the customer to make
them feel like they are getting a good deal.
Basically there are two working documents now used for a vehicle sale. The first is the Sales invoice (see
figure in FORMS), where the specifics of base price, trade-in, salesperson, add-on options, and the like are
detailed. This document is first handwritten by the salesperson while she or he is talking to a prospective
customer; it is frequently changed as preferences change and as ‘deals’ are made. After the customer and
salesperson agree on the deal, the invoice is typed, printed, and signed by both the buyer and the salesperson.
Note that undercoating, tinting, sunroofs and other items are also considered options for the purposes of
preparing the sales invoice and calculating the salesperson’s commission.
The second working document is the Vehicle Inventory Record (see figure in FORMS). This document is used
to describe vehicles in stock at Quality Imports and is prepared only after receipt of a vehicle (either from a
manufacturer or a trade-in); vehilces on order or being considered as trade-ins in sales being negotiated are not
recorded here.
Gary is certain that periodic mailed reminders to drivers will not only generate service business but will also
foster new sales as customers come into the dealership. One problem with tracking customers via sales only is
that the buyer and the owner are often not the same person. Parents may buy cars for children, and customers
actively trade or sell cars elsewhere. Consequently, although tracking service customers to increase the service
business (which is very active without much effort) could produce some marginal income, service visits are a
more important source of information on current owners of vehicles.
FORMS
 Minimally, you should create the following FORMS (for data entry):
o Basic Data entry forms for customer and employee tables.
o Vehicle Inventory Record (to add a new vehicle to inventory – see below)
o Sales Invoice (to sell a car to a customer by an employee – see below)
 The information for those forms is made up by your group members. There should be adequate data in
your database to provide for testing of forms, reports, and queries!! Please be aware that your forms DO
NOT need to look like the ones in the case…they just need to provide the same ‘service’. I provided
examples to help you understand what attributes should be kept in your database. Remember, not all
attributes are stored…some are derived at the time of form/report creation.
REPORTS
Minimally, you should create the following reports:
1. A report listing all AVAILABLE inventories. Do not include any inventory which has been sold.
2. A printable invoice for a GIVEN sale. I do not want a report which lists ALL sales. The report
should display a single invoice.
Total Price:
Trade in and Discounts:
Net
:
Commission:
$25,000.00
$5200.00
$19,800.00
$300.00
QUERIES
 Minimally, you should create the following queries (for data reporting):
o A listing in zip code order of the names and addresses of people who have bought cars from a
specified salesperson.
o A listing of the more popular makes/models sold. In order for a make/model to be included in
the result, it should appear in at least 4 sales. Make sure you have appropriate data in your
database to test this query (i.e. makes/models which appear in less than 4 sales as well as
makes/models which appear in more than 4 sales!).
o The average amount spent on options per sale.
o TWO additional queries of your choice – make them something your user would appreciate!