$25.00 MS Access Huffman trucking ERD
- This tutorial was purchased 4 times and hasn't been rated yet.
- Posted on May 09, 2009 at 01:00:31PM
A:
Preview: ... obtained by first analyzing the key subjects, entities, and attributes. The key subjects are the following: Parts Inventory Purchases, Parts Inventory Issues, Parts Catalogue, Vendors, Parts Purchasing History, Vehicle Maintenance, Tire Maintenance, Maintenance Descriptions, Vehicle Types, Vehicles, and Maintenance Work Orders along with several entities to support each of the subjects. The tables were then normalized to third normal form (3NF). Accordingly, each of the tables will be joined by a series of primary and foreign keys thereby creating relationships among them. This approach will allow the design to be broken into smaller pieces, thus focusing on one entity at a time. Eventually, these smaller designs were merged into a cumulative design for the entire database.<br> If this project is not implemented, it will not be possible to automatically share data for each of the trucking hubs. Parts ordering and settlement will continue to be done in an inefficient and decentralized way. Parts inventory will not be able to be shared between hubs and maintenance schedules will be inconsistent between hubs. There will be several opportunities that will grow from this project. In the future, analysis of this data will lead to even more improvements in the maintenance program here at Huffman. <br><br> <br>Relational Database Rationale<br> The entity relationship diagram our D Team has constructed is for a relational database. Relational databases are composed of multiple tables that contain both fields and attributes which share a specific relationship with one another. These relationships are sometimes referred to as parent-child relationships. The way it works is the primary key for one table will be used as the foreign key in a relating table thus accounting for the relationship. The table containing the primary key is known as the parent table and the opposite table housing the foreign key is the child table. Two other types of databases that we have discussed are flat file databases and data warehouses. A flat file database is made up of only one table which contains all the data gathered in separate fields on that one table. Flat file databases can be equated with spreadsheets like the type found in MS Excel. Formulas can be computed and reports can be generated, but data entry will be restricted to that one table. Like relational databases, warehouse database systems can be normalized; however, they are usually the result of a combination of several different ...
The full tutorial is about 1974 words long .
