Huffman Trucking Service Request Sr-Ht-003

According to Service Request SR-ht-003, We were to develop a design for a fleet truck maintenance database, located on the Huffman Trucking IT Service Requests site.

This paper will talk about how our team completed the Change Request that was on the Huffman Trucking Service Request. First our team will talk about how Microsoft Access was used to create these tables by Huffman Trucking Database. Then how we used the tables with made up information to be tested on. Then on how we used forms in the maintenance database system.

While the creation of relationships and normalization is explained in the process of using queries to search the database (University of Phoenix, 2007). Tables In Change Request 2, Huffman Trucking had Team B to create the entities and attributes for a brand new maintenance database. And also our team has been asked to create these tables for the items it asked for. Our team used Microsoft Access, which is a database tool. First through access we created the tables we needed for the entities, then we gathered the tables with the attributes .

An example of a table is called “Maintenance Work Orders”, and in that table there would be attributes like “Part ID” or “Vehicle”. In this table we know exactly of what’s on there like the Work Order number, vehicle, part ID, and etc. Test Data and Entity-Relationship Diagrams In Change Request 3 we were to link the tables and to create tables for the Fleet Truck Maintenance database with ten records of test data. By putting these ten records of test data, the database can be tested to see if possible “bugs” or if anything is missing in the data system.

Another thing we used in the testing and development of this database is use of an entity relationship . Entity Relationship Diagrams are a major data modeling tool and will help organize the data in your project into entities and define the relationships between the entities. This process has proved to enable the analyst to produce a good database structure so that the data can be stored and retrieved in a most efficient manner ("Developing Entity Relationship Diagrams (erds) ", n. d. ). Normalization Normalization is the process of successfully organizing data in a database.

It has two goals in the process.First, by getting rid of the same data that’s in more than one table, and making sure data dependencies is correct. Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored ("Database Normalization Basics", 2013). Normal Forms The database community has developed a series of guidelines for ensuring that databases are normalized ("Database Normalization Basics", 2013).

They are also called normal forms and are numbered from one (1NF) through five (5NF). The first form is (1NF), is pretty easy to apply and understand because there are no repeating steps.The first normal form, each column should contain just a name, single value, single data type, and must not have no repeating groups. The next form (2NF), attempts to reduces the amount of data in a table, by placing it in new table and creating relationships between those tables. The third form (3NF) must meet all requirements of 2NF, and it removes all columns that aren’t dependent on the primary key.

The Next forms are 4NF, 5NF, and BCNF. They are used when the database becomes more detailed . Queries and Reports In the next change request in the SR-ht-003 form asked the team to make some queries.Queries are an easy way of locating and finding data from one or more tables. Basically running a query is just like asking it a question. Select queries are by far the most common and useful type of query in Access; however, there are other types of queries that are also important (“Temple University Queries”, 2010).

On the next change request we were asked to make reports. The use of reports is to view, format, and summarize data. Reports provide a way to distribute or archive snapshots of your data, either by being printed out, converted to PDF or XPS files, or exported to other file formats ("Introduction To Reports", 2013).