Dbm 280 Huffman Truck Maintenance Database

Huffman Fleet Truck Maintenance Database

DBM/380

September 5, 2011

Paul Worthey

Executive Summary

Huffman Trucking further referred to as "the company" IT project manager published a service request identified as Service Request SR-ht-003 specifically requesting development of a Fleet Truck Maintenance database. IT development team D with information provided by Smith Systems Consulting prepared the database, subsequent change requests, and conjoining documentation satisfying the company IT project manager's service request.

The service request and subsequent change requests employ IT development team D to create a relational database supplying effective maintenance information for authorized users. Documentation prepared for this project summarizes the process of using entities and attributes for the fleet truck maintenance database. The documentation furthermore explains the process of creating the entity-relationship diagrams, database relationships, and the database model normalization process.

Creating the database IT development team D identifies in the tables configuration of primary and foreign key relationships. Structuring the company fleet trucking maintenance database designates formation of opening switchboard guidance admittance, practical form creation, and relevant queries.

Huffman Fleet Truck Maintenance Database

Creating the database IT development team D uses the fields identified by Smith Systems Consulting and creates the required tables. Once the tables were created each table was analyzed to determine the data types making sure that entities used in calculations were defined properly before data was input. That text fields were identified as such with the zip code and phone number fields formatted with an input mask for each accordingly. All date fields were formatted with the short date option, and all monetary fields identified with a currency data type. . The team has also allowed for indexing on the tables. This allows certain information to have one entry.

Primary and Foreign Key

After each table is created a primary key is identified in the tables' configuration and foreign keys are defined by the relationships. A primary key is the unique identifier for each record in the table. The main purpose of the primary key is to relate records to additional data stored in other tables (Tech Republic, 2011). A foreign key is a column or combination of columns that is used to establish and enforce a link between the data in two tables (Microsoft.com, 2011).

ERD

To aide this process IT development team D uses an ERD to visually display the tables and show the relationships between the primary key and the foreign key in the created tables. Once the ERD is developed and the relationships established on the ERD they are then implemented in the database. If changes are needed in the database after data is entered and queries are created the ERD is then updated to reflect the changes.

From the twelve tables defined forms have been created to allow entering and maintaining the data for ease of use. The form gives the user a graphical user interface that does not make adding information to the database mundane.