Driving School Database ‘Skill-busters’ Access Task

Driving School Database

‘Skill-busters’ Access Task

A driving school currently use a paper-based system for their records.

When a customer books a lesson, their record card at the driving school is updated.



An example of a record card is shown:



An example of a record card is shown:



The driving school also has record cards for its vehicles and instructors.



The driving school also has record cards for its vehicles and instructors. The record card for each vehicle has information about its registration mark, make, model, year of registration, manual/automatic, availability and notes. The vehicle is either available or unavailable for use by the driving instructors at any one time. Notes for the vehicle are kept about its service history and any damage that is caused.



The driving school also has record cards for its vehicles and instructors. The record card for each vehicle has information about its registration mark, make, model, year of registration, manual/automatic, availability and notes. The vehicle is either available or unavailable for use by the driving instructors at any one time. Notes for the vehicle are kept about its service history and any damage that is caused. The record card for each instructor has information about the instructor’s name, date of birth, gender, date of first employment, date left (if appropriate) and National Insurance number.



The driving school also has record cards for its vehicles and instructors. The record card for each vehicle has information about its registration mark, make, model, year of registration, manual/automatic, availability and notes. The vehicle is either available or unavailable for use by the driving instructors at any one time. Notes for the vehicle are kept about its service history and any damage that is caused. The record card for each instructor has information about the instructor’s name, date of birth, gender, date of first employment, date left (if appropriate) and National Insurance number. The driving school have decided to use a database.



The driving school also has record cards for its vehicles and instructors. The record card for each vehicle has information about its registration mark, make, model, year of registration, manual/automatic, availability and notes. The vehicle is either available or unavailable for use by the driving instructors at any one time. Notes for the vehicle are kept about its service history and any damage that is caused. The record card for each instructor has information about the instructor’s name, date of birth, gender, date of first employment, date left (if appropriate) and National Insurance number. The driving school have decided to use a database. Four entities are to be used INSTRUCTOR, CUSTOMER, VEHICLE and LESSON.

Tasks

Tasks 1. Using standard notation show:

• the primary keys of each table,• the name of each data item (field / attribute) for each table,• the foreign key(s) that will be used to link the tables together.



Standard notation:

STUDENT(StudentID, Forename, Surname, Street, Town, County, Postcode …..)



2. Draw an entity-relationship diagram for the database indicating the degree of the relationships between the entities







Tasks 3. Draw and complete validation tables for each of the entities containing:

Tasks 3. Draw and complete validation tables for each of the entities containing:

Validation1. Data type

2. Field length

3. Format (Input mask)

4. Range (Validation rule)

5. Lookup (foreign keys or select from list)

Format• usually via an Input mask

• e.g. LL99LLL for car registration– L = letter– 9 = digit– A = letter or digit– ……– see the Input Mask sheet on the website for more

• sometimes a validation rule is used in a combination:

– Left([TelephoneNumber],1)=0• checks that ……???

Range• usually via a Validation Rule

• DateDiff(“yyyy",[DOB],Date()) > =21– checks that person is over 21– [DOB] is the date of birth field– Date() refers to today’s date




3. Draw and complete validation tables for each of the entities.

4. Draw and complete data structure tables for each of the entities indicating:

• the primary key• the name of each attribute • a description of the attribute• the data type for each attribute • foreign key(s) • examples of the data to be stored in each attribute

4. Build a database table structure for the driving school containing:• at least 11 instructors,• at least 10 customers, • at least 20 lessons, • at least 5 vehicles. [8]


5. The driving school want to be able to print various lists about the data.



(a) Produce a report to show all future lessons for Nicola Long, including the finishing time of each lesson which is not stored in the database. Include

at least three lessons on the list. Identify clearly the date the report was printed. [3]





(b) Produce a report to show all lessons on 29 June 2005 for Merrick Woodward who is one of the driving instructors. There should be at least five lessons. [2]





(b) Produce a report to show all lessons on 29 June 2005 for Merrick Woodward who is one of the driving instructors. There should be at least five lessons. [2]

(c) Produce a report to show all future lessons grouped by driving instructor. There should be at least 20 lessons. Identify clearly the date the report was printed. [2]

Evidence

1. Standard notation listing for each entity

2. Entity Relationship Diagram (showing degrees)

3. (a) ‘4-column’ table for each entity

(b) Validation table for each entity

4. (a) Screenshot of design view in Access for each entity

(b) Screenshot showing requisite data in each entity

5. Reports as detailed in the task

Documents

Driving School Database ‘Skill-busters’ Access Task