Huffman Fleet Truck Maintenance Database Specifications
DATABASE
SPECIFICATIONS
Huffman Fleet Truck Maintenance
Team A
May, 2009
Revision Sheet
Release No.
Date
Revision Description
1
5/2/09
Initial creation of document - Kramer
3
5/3/09
Addition of POC and Abbreviations - McCoy
4
5/4/09
Schema - section 2.5.1
DATABASE SPECIFICATIONS
TABLE OF CONTENTS
Page #
1.0 GENERAL INFORMATION 2
1.1 Purpose 2
1.2 Scope 2
1.3 System Overview 1
1.4 Project References 1
1.5 Acronyms and Abbreviations 1
1.6 Points of Contact 2
1.6.1 Information 2
1.6.2 Coordination 2
1.6.3 Additional Points of Contact 2
1.6.4 Data Owners 2
2.1 Naming Conventions 1
2.2 Database Identification 1
2.3 Systems Using the Database 1
2.4 Relationship to Other Databases 1
2.5 Schema Information 1
2.5.1 Description 2
2.5.2 Physical Design 5
2.6 Data Dictionary 5
2.7 Entity-Relationship Diagrams 5
2.8 References 5
1.0 GENERAL INFORMATION
1.0GENERAL INFORMATION
1.1 Purpose
Our project is to create an Entity - Relationship Diagrams for the Fleet Truck Maintenance database. This will allow hub managers and maintenance supervisors the ability to automatically generate uniformed reports using near real time data to assist in compiling with regulatory requirements or decision planning for a fleet of over 800 trailers and 2100 trailers.
1.2 Scope
Project Justification:
Huffman Trucking has decided to create one set of standardized and uniformed reports for each of its hubs. This will also give hub managers the ability to automatically generate reports using real time data. Our project is to create an Entity - Relationship Diagrams for the Fleet Truck Maintenance database to assist in the development of the database.
Project Product and Services:
Our product is the creation of entity - relationship diagrams. The preliminary expectation is to have 11 to 12 tables and at least 6 queries available to create the necessary reports. Tables will be compiled using the existing reports from all
SPECIFICATIONS
Huffman Fleet Truck Maintenance
Team A
May, 2009
Revision Sheet
Release No.
Date
Revision Description
1
5/2/09
Initial creation of document - Kramer
3
5/3/09
Addition of POC and Abbreviations - McCoy
4
5/4/09
Schema - section 2.5.1
DATABASE SPECIFICATIONS
TABLE OF CONTENTS
Page #
1.0 GENERAL INFORMATION 2
1.1 Purpose 2
1.2 Scope 2
1.3 System Overview 1
1.4 Project References 1
1.5 Acronyms and Abbreviations 1
1.6 Points of Contact 2
1.6.1 Information 2
1.6.2 Coordination 2
1.6.3 Additional Points of Contact 2
1.6.4 Data Owners 2
2.1 Naming Conventions 1
2.2 Database Identification 1
2.3 Systems Using the Database 1
2.4 Relationship to Other Databases 1
2.5 Schema Information 1
2.5.1 Description 2
2.5.2 Physical Design 5
2.6 Data Dictionary 5
2.7 Entity-Relationship Diagrams 5
2.8 References 5
1.0 GENERAL INFORMATION
1.0GENERAL INFORMATION
1.1 Purpose
Our project is to create an Entity - Relationship Diagrams for the Fleet Truck Maintenance database. This will allow hub managers and maintenance supervisors the ability to automatically generate uniformed reports using near real time data to assist in compiling with regulatory requirements or decision planning for a fleet of over 800 trailers and 2100 trailers.
1.2 Scope
Project Justification:
Huffman Trucking has decided to create one set of standardized and uniformed reports for each of its hubs. This will also give hub managers the ability to automatically generate reports using real time data. Our project is to create an Entity - Relationship Diagrams for the Fleet Truck Maintenance database to assist in the development of the database.
Project Product and Services:
Our product is the creation of entity - relationship diagrams. The preliminary expectation is to have 11 to 12 tables and at least 6 queries available to create the necessary reports. Tables will be compiled using the existing reports from all
References: Leszynski, Reddick (1994). Guidelines for Access. Smart Access Journal, August 1994. Retrieved May 2, 2009 from http://www.pacificdb.com.au/Support/CodeFiles/Leszynsk-iReddickGuidelinesForAccess1And2.doc