Free Essay

Huffman Fleet Truck Database

In:

Submitted By constantcivil
Words 2654
Pages 11
Planning and Creation of a Fleet Truck Maintenance Database for Huffman Trucking In creating a database, the most vital steps are identifying the table elements. Upon analysis of the Entities and Attributes for Fleet Truck Maintenance form, the elements of the database tables can be identified. In a table, or relation, the entities and attributes of a table define the structure of a database. An entity is an object of importance about which data can be captured. An attribute is the information that describes the entity. When creating the tables for the Huffman Trucking Fleet Truck Maintenance, entities and their relationships must be taken into consideration (Koenke & Auer, 2010).
Selection of Entities and Attributes In the Entities and Attributes for Fleet Truck Maintenance document, the entities and their attributes are clearly defined. The entities are listed in all capital letters. The entity’s respective attributes are listed below the entity. For example, for the entity “Parts_Inventory_Issues”, the attributes listed in the document are: * Transaction ID * Issue Date * Purchase Price * Quantity
In creating the table, the attributes must be examined to ensure that the table is organized logically and contains no chances of redundancy. Because of this, the entities and attributes used in the actual database will be modified from the attributes listed in the document. Repeating attributes will be deleted or reorganized to ensure logical structure. Each table will contain a primary key. The creation of a table will have an added attribute; it will be the table’s primary key. For instance, in the table “Part_Issues”, the primary key will be “Issue_ID.” The attributes “Purchase Price” and “Quantity” will be deleted since that data is present in another table and does not directly relate to part issues. The attribute “Description” will be added in order to be able to document the nature of the part issue. Additionally, the rest of the tables will also be assigned a primary key so that each table has a unique identifier. The chart below shows each table name and its corresponding attributes. Entity | Attributes | Vehicles- The table will display the inventory vehicles that are at Huffmans fleet. | * Vehicle_ID (PK) * VIN * Vehicle_detail * Put_inservice_date * Purchase_invoice * Taken_outservice_date | Vehicle_detail- Will display the specific vehicle information | * Veh_detail_ID (PK) * Vehicle_ID * Mileage * Type_ID * Capacity * Class_code * Gross_weight | Vehicle_Invoices- The table will display the invoices for the vehicles that are purchased. | * Vehicle_Invoice_ID (PK) * Vehicle_ID * Date_Purchased * Price * Shipping * Tax * FOB | Vehicle_Type- a table displaying the types of vehicles. | * Type_ID (PK) * Description | Maintenance_Descriptions- a table with general details of each maintnenace type | * Maintenance_Type_ID (PK) * Level_code * Description * Avg_hours_req * Days_between_rec_maint * Max_days_between_maint | Tire_Maintenance- a table displaying the maintenance record of vehicle tires. | * Tire_Maint_rec_ID (PK) * Part_ID * Vehicle_type * Manufacturer_ID * Put_inservice_date * Rotation_schedule * Last_rotated * Disposal_date | Maintenance_work_order- a table displaying all maintenance work orders for fleet vehicles. | * Work_order_ID (PK) * Vehicle_ID * Maintenance_Type_ID * Vehicle_Part_ID * Assignment_To * Date_Started * Date_complete * Hours | Vehicle_Maintenace_Record- a table displaying the maintenance recorded for each flee vehicle. | * Veh_Maintenance_rec_ID (PK) * Vehicle_ID * Work_orders * Next_scheduled_maint_date * Under_warranty_flag | Parts_Catalog- a table displaying the vehicle parts used in maintenance. | * Part_ID (PK) * Part_Type * Manufacturer * Vendor | Part_Type- a table displaying descriptions of each part type. | * Part_Type_ID (PK) * Description | Part_Invoices- a table displaying invoice detail for each part. | * Part_Invoice_ID (PK) * Date_Purchased * Quantity_Purchased * Order_Quantity * Price * Shipping * Tax * FOB | Part_Issues- a table displaying parts that have been taken out of inventory and why. | * Issue_ID * Part_ID * Issue_Date * Issue_Description | Vendors- a table with information about vendors. | * Vendor_ID (PK) * Vendor_name * Order_Address_ID * Billing_Address_ID * Phone * Fax | Vendor_Addresses- a table displaying vendor addresses. | * Address_ID (PK) * Vendor * Street * City * State * Zip | Chart 1. The entities and attributes chosen for the database are displayed. Creation of the Entity Relationship Diagram The next step in creating the database for the Entities and Attributes for Fleet Truck Maintenance document is to establish the relationships within the database. Relationships between tables can be illustrated in an Entity Relationship Model or ERD. In an ERD, the tables and their attributes are shown and their relationships are demonstrated using lines. In an ERD, there are two main types of relationships (Kroenke & Auer, 2010): 0 Relationship Classes- associations among entity classes 1 Relationship Instances- Associations among entity instances
Their Binary Types can further organize relationships: One-to-One relationships, One-to-Many relationships, and Many-to-Many relationships. The traditional model standards for ERDs call for diamonds representing relationships and rectangles representing classes. However, ERDs are loosely standardized and often look different from one another due to software such as Microsoft Access and MySql Workbench that create ERDs using proprietary applications. When creating the ERD for the Entities and Attributes for Fleet Truck Maintenance form, the relationships and their types must be established. The entities have been established in the chart above. The entities will be organized into tables with their respective attributes displayed below the name of the table. The top attribute will be assigned as a primary key in order to ensure each table has a unique identifier. These primary keys will also serve as foreign keys when inserted into other tables within the ERD. In order to display the relationships, lines will be drawn between each table in the ERD. MySQL Workbech, for instance, creates relationships in each table by having a dotted or solid line connect each table to its relation. MySQL Workbench uses Crows Foot Notation in its diagram creation application. Crows Foot Notation allows for relationships in an ERD to be displayed by their binary type. The types of Crow’s Foot Notation’s and their respective Binary Types are displayed below:

Figure 1. This diagram illustrates the binary types and thier respective Crow's Foot Notation (Interpreting Entity-Relationship Diagrams, n.d.).

In order to create the ERD with the entities and attributes listed in Chart 1, their relationships must be established. For instance, the table “Vehicles” is directly related to the table “Maintenance_Work_Order” which contains the records of maintenance performed on Huffman’s vehicles. The relationship is one-to-many since a single vehicle can have many work orders. The ERD below details each table and its respective relationships along with Crow’s Feet Notation to show binary type. Figure 2. The Huffman Fleet Truck Maintenance ERD shows entity relationships in binary type.

In order to determine the relationships from the ERD, the Crows Feet Notation can be used. As stated before, the “Vehicles” table is related to the “Maintenance_Work_Order” table. The line connects these two tables. The two dashes representing one vehicle can be seen on the line beginning from the “Vehicles” table. The line leads to the Maintenance_Work_Order” and ends with a Crow’s Foot. The specific attributes related are shown as well. In order to properly relate the tables, the primary key from “Vehicles” will be inserted into the table “Miantenance_Work_Order.” Once the primary key is inserted, the “Maintenance_Work_Order” table contains the foreign key “Vehicle_ID” in its table. This foreign key demonstrates the relationship between “Vehicles” and “Maintenance_Work_Order”: one car can have many work orders. It is therefore a one-to-many relationship. The other relationships within the ERD are created similarly.
Database Normalization In databases, the data must be stored logically and efficiently. An entity relationship diagram, or ERD, helps database designers organize the entities in order to logically store the data within the database. The current database Huffman Fleet Truck Maintenance must be normalized from its initial form. In its initial form, the entities and attributes listed in the Entities and Attributes for Fleet Truck Maintenance were at times redundant and unnecessary (Kroenke & Auer, 2010). Creating a database with the entities and attributes listed may have created anomalies within it. Anomalies are inaccuracies within the database that can result from deletion, insertion, or update of data. Normalization ensures that the database contains little or no anomalies. In order to normalize the database, the major types of Normalization should be followed (Stephens, 2009): * First Normal Form (1NF) * Second Normal Form (2NF) * Third Normal Form (3NF) * Boyce-Codd Normal Form (BCNF) * Fourth Normal Form (4NF) * Fifth Normal Form (5NF) * Domain/Key Normal Form (DKNF)
Many databases can be normalized to the Third Normal Form and be free of anomalies. In the case of Huffman’s Fleet Truck Maintenance Database, normalization can stop at Third Normal Form since that level of normalization has eliminated the most anomalies. The database displayed in the ERD is normalized in First Normal Form. Each column has a unique name and a single data type. No two rows within an entity contain identical values. Each column in the database contains a single value and there are no repeating groups within any of the columns. For instance, in the original Entities and Attributes for Fleet Truck Maintenance document of entities and attributes, many of the attributes appeared multiple times in different tables. In order to normalize the database, many of these extra occurrences were deleted. “Transaction_ID” was one of the attributes that appeared multiple times within the database. Through normalization, it was found that most of them were not needed and would only cause anomalies if they were left alone. The ERD follows all the rules of the First Normal Form so it is normalized in 1NF. The database is also normalized in Second Normal Form. The simplest requirement of Second Normal Form is that the database adheres to First Normal Form. Since it has already been established that the above database adheres to the First Normal Form, the only requirement left is that all the non-key fields depend on all of the key fields. The original document Entities and Attributes for Fleet Truck Maintenance almost all of the tables contained attributes that did not depend on the key field. At times, the tables were organized so that several attributes appeared. For example, in the “Vehicles” table, there were far too many attributes. Several attributes that did not depend on the key field were deleted or placed into a new table. The new table is entitled “Vehicle_Detail” and contains attributes about weight, mileage, and capacity while the “Vehicle” table contains vehicle data such as invoice number, date entered into service, and VIN. These tables were then connected through relationships using the primary keys and foreign keys. The other tables were normalized in this manner as well to ensure that the database meets Second Normal Form standards.
Finally, the database is in Third Normal Form. It meets the first requirement of Second Normal Form and also meets the second requirement of Third Normal Form: the database must not contain any transitive dependencies (Stephens, 2009). Every column depends on the primary key. In the “Vehicles” table, all the attributes depend on the “Vehicle_ID” key. There are no columns of data that do not belong. The same is done with the other tables. This means that the database will contain no anomalies due to modification of data.
Structured Query Language and Test Data Once the database is normalized, data is ready to be entered into the tables. This is done with the help of Structured Query Language, or SQL. SQL is a programming language used to manage data in relational databases such as Huffman Fleet Truck Maintenance (Kroenke & Auer, 2010). It can enter, update, or delete data using commands called queries. A database can be created using queries. First, a CREATE DATABASE query is used to create the database. The query written in order to create the Huffman Fleet Truck Maintenance Database MySQL is as follows: delimiter $$ CREATE DATABASE `huffman database` /*!40100 DEFAULT CHARACTER SET latin1 */$$

The query above, when inserted into MySQL, will create the database without any tables present. In order to add the tables, additional CREATE queries must be used. For instance, in order to create the “Vendors” table, the following query is input into MySQL: delimiter $$ CREATE TABLE `vendors` ( `Vendor_ID` int(11) unsigned NOT NULL, `Vendor_name` varchar(20) NOT NULL DEFAULT '', `Order_address_ID` int(11) unsigned NOT NULL, `Billing_address_ID` int(11) unsigned NOT NULL, `Phone` varchar(17) NOT NULL DEFAULT '', `Fax` varchar(17) NOT NULL DEFAULT '', PRIMARY KEY (`Vendor_ID`), KEY `Order_address_ID` (`Order_address_ID`), KEY `Billing_address_ID` (`Billing_address_ID`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1$$ The same is done with the rest of the tables. The additional queries needed to create the table are in the notepad file Huffman Fleet Truck Data Query Database attached with this document. The next step in creation of the database is adding the relationships between the tables. Each table must have a foreign key constraint added in order to create a relationship. In order to do this, input ALTER TABLE followed by the table name. The command ADD CONSTRAINTS is then input as well as seen in the example below:
ALTER TABLE vendors
ADD CONSTRAINT `vendors_ibfk_1` FOREIGN KEY (`Order_address_ID`) REFERENCES `vendor_addresses` (`Address_ID`)
ON DELETE CASCADE ON UPDATE CASCADE;

The ALTER TABLE command above inserts the foreign key into the “Vendors” table thus creating a relationship between “Vendors” and “Vendor Addresses.”
Some of the queries most commonly used are INSERT, SELECT, CREATE, DELETE, and UPDATE (Erack Network, 2008). There are many SQL clients that can help create use these queries to manage data in the database. For example, in order to insert maintenance types into the “Maintenance_Descriptions” table, the following query would be used: UPDATE `huffman database`.`maintenance_description` SET `Maintenance_Type_ID`=1, `Level_code`='Routine', `Description`='Preventive Maintenance', `Avg_hours_req`=8, `Days_between_rec_maint`=1, `Max_days_between_maint`=1 WHERE `Maintenance_Type_ID`='101'; UPDATE `huffman database`.`maintenance_description` SET `Maintenance_Type_ID`=2, `Level_code`='Moderate', `Description`='Fixing of some components', `Avg_hours_req`=24, `Days_between_rec_maint`=3, `Max_days_between_maint`=5 WHERE `Maintenance_Type_ID`='102'; UPDATE `huffman database`.`maintenance_description` SET `Maintenance_Type_ID`=3, `Level_code`='Severe', `Description`='Required replacement of components in order to function', `Avg_hours_req`=48, `Days_between_rec_maint`=5, `Max_days_between_maint`=10 WHERE `Maintenance_Type_ID`='103'; DELETE FROM `huffman database`.`maintenance_description` WHERE `Maintenance_Type_ID`='104';

Figure 3. The Maintenance Description table data inserted with UPDATE queries is present in the table. This query is used in MySQL to set the Maintenance types for the Huffman Fleet Truck Maintenance database. The query also contains an example of the DELETE command that is used to delete data from a table. In this instance, the number 104 was deleted from the “Maintenance_Type_ID” field. The update query is used to update data already within the table. The UPDATE command is very strong, therefore it is wise to use a WHERE condition within the query to ensure that only the targeted data is changed as is seen in the example above. In the “Vehicle_types” table, data concerning the type of vehicle in the fleet is stored. Vehicle types such as large cargo truck, medium cargo truck, and pickup truck are stored. The number of tires or wheels is also listed in the description of this table. The UPDATE commands to change this table are: INSERT INTO `huffman database`.`vehicle_type` (`Type_ID`, `Description`) VALUES (301, 'Large cargo truck, 18 wheels'); INSERT INTO `huffman database`.`vehicle_type` (`Type_ID`, `Description`) VALUES (302, 'Large cargo truck, 16 wheels'); INSERT INTO `huffman database`.`vehicle_type` (`Type_ID`, `Description`) VALUES (303, 'Medium Cargo Truck, 10 wheels, Mack type'); INSERT INTO `huffman database`.`vehicle_type` (`Type_ID`, `Description`) VALUES (304, 'Large Pickup truck, 6 wheels'); INSERT INTO `huffman database`.`vehicle_type` (`Type_ID`, `Description`) VALUES (305, 'Medium Pickup truck, 4 wheels'
Commands for the other tables are built similarly; with the INSERT INTO command followed by the table name followed by the column names. The VALUES section then holds the values being inserted into the table. These commands are useful in creating the data within each table of the database. Figure 4. The data in MySQL is present within the vehicle type table after being inserted via query commands.

Conclusion The creation of the Huffman Fleet Truck Maintenance Database has many steps. This is to ensure that the final database is an accurate, logical, and normalized database with as few anomalies as possible. The entities and attributes were first chosen. The Entity Relationship Diagram was then built. Finally, the ERD was normalized and the queries written. Together, these components make up the final database for Huffman Trucking.

References
Erack Network. (2008) Retrieved June 7, 2012 from http://www.tizag.com/sqlTutorial/sqlqueries.php
Interpreting entity-relationship diagrams. (n.d.). Retrieved from http://www.philblock.info/hitkb/i/interpreting_entity-relationship_diagrams.html
Kroenke, D. M., & Auer, D. J. (2010). Database concepts (4th ed.). Upper Saddle River, NJ: Pearson/Prentice Hall.
Stephens, R. (2009). Beginning database design solutions. Indianapolis, IN: Wiley.

Similar Documents

Free Essay

Database Concepts

...Company Huffman Trucking is a privately owned transportation company that has been in business for 60 years. The company has grown into a multi million-dollar company with over 1,400 employees and hundreds of vehicles. Huffman Trucking needs a better way to track the maintenance on their fleet of tractors, trailer and the roll-on/roll-offs. The fleet has to undergo periodic maintenance. Plan Putting the equipment's maintenance history, the parts used and vendor information into one database will save Huffman Trucking time and money. The database can include parts inventory information, parts catalogue information, the vendors used and their associated information, and parts purchasing history. The database will include all the maintenance history on each piece of equipment, such as the maintenance of the equipment itself, tire maintenance, the type of maintenance and the maintenance work orders. Conclusion Building a database saves money on maintenance by reducing redundant information and improving record keeping. Both the service and accounting departments will be able to utilize this database to keep track of parts purchases and costs. Having all the information in one central database would allow the diverse facilities to use the database. This type of centralization would bring more accuracy in Huffman Trucking's record keeping and would save money, time and manpower. Huffman Trucking Fleet Maintenance Database Solution Introduction Huffman Trucking is a...

Words: 1795 - Pages: 8

Premium Essay

Dbm 380 Week 4 Huffington

...Huffman Trucking Company DBM/380 July 16, 2012 Gaya P. Agrawal Introduction During World War II it was imperative that the United States government find a way to transport products to and from different parts of the United States. Huffman Trucking Company was one of the first companies commissioned by the United States used to assist in this effort. Established in Cleveland Ohio K. Huffman started the company with one tractor-trailer and thanks to the help of the United States government, grew to 16 tractors and 36 trailers by 1945. Today, Huffman Trucking Company has 800 road tractors and 2100 45 foot trailers at its disposal. Although Huffman has been extremely successful, the need to remain competitive by use of information technology has been a challenge. It is the first company that has been recognized to outsource 100% of its information systems support. Due to the large fleet in use by Huffman Trucking through-out its many locations, the need arose for an equipment maintenance tracking system which could be accessed globally. Service Request Requirements Huffman initiated a service request for the development and design of a fleet truck maintenance database with Smith Systems Consulting. Though Smith Systems Consulting developed entities and attributes for the Fleet Truck Maintenance database, the company did not develop the database itself. According to service request SR-HT-003, the expected result of the service request is the creation of Entity-Relationship...

Words: 1864 - Pages: 8

Premium Essay

Huffman Truck

...Planning and Creation of a Fleet Truck Maintenance Database for Huffman Trucking In creating a database, the most vital steps are identifying the table elements. Upon analysis of the Entities and Attributes for Fleet Truck Maintenance form, the elements of the database tables can be identified. In a table, or relation, the entities and attributes of a table define the structure of a database. An entity is an object of importance about which data can be captured. An attribute is the information that describes the entity. When creating the tables for the Huffman Trucking Fleet Truck Maintenance, entities and their relationships must be taken into consideration (Koenke & Auer, 2010). Selection of Entities and Attributes In the Entities and Attributes for Fleet Truck Maintenance document, the entities and their attributes are clearly defined. The entities are listed in all capital letters. The entity’s respective attributes are listed below the entity. For example, for the entity “Parts_Inventory_Issues”, the attributes listed in the document are: • Transaction ID • Issue Date • Purchase Price • Quantity In creating the table, the attributes must be examined to ensure that the table is organized logically and contains no chances of redundancy. Because of this, the entities and attributes used in the actual database will be modified from the attributes listed in the document. Repeating attributes will be deleted or reorganized to ensure logical structure. Each...

Words: 968 - Pages: 4

Free Essay

Critical Information

...Paper Huffman Trucking is a transportation company that was founded in 1936 by K. Huffman. He started this company with one single tractor-trailer. Soon he had developed the need for growth of his company as a result of World War II which caused a huge demand for carrier services from companies in the Midwest to the ports of the East Coast. With Huffman’s main customer being the United States Government he found that by 1945 his fleet had developed an increase in its size from one tractor trailer to 16 tractors and 36 trailers. Besides the government Hoffman also had accounts with automotive parts suppliers, plastic manufacturers, electronics manufacturers, and various other customers that required special material transport needs. Huffman Trucking is a nationally known company with locations in Cleveland Oh, St. Louis Mo, Los Angeles Ca, and Bayonne N.J.. Huffman Trucking now also has 800 tractors, 260 roll on and off units, and 2,100 45 ft trailers. He also now employs 925 drivers and 425 various other staff members. With a company of this size there is much needed responsibility such as keeping track of equipment expenses, mileage, drivers daily logs, and freight. At this point in time each facility is keeping track of their own expenses and records which could be causing a bit of confusion on when the tractors and trailers need their appropriate maintnance done. This issue has brought the maintnance supervisors together to develop a fleet maintenance database that will...

Words: 640 - Pages: 3

Premium Essay

System Inventory

...of the following Virtual Organizations: • Smith Systems Consulting • Huffman Trucking • Kudler Fine Foods Complete the following chart, filling in information for each system used at that Virtual Organization. Add rows to the chart as necessary. |System Name |Brief Description |Department to Use |Purpose of the System |Connects With |Development Details | | | |the System | | | | |Fleet Truck Maintenance |Relational database and |Fleet Maintenance |The DBMS will house |Drivers, Fleet |Ease of use – This DBMS has a | |Database Management |an information | |all the maintenance |Maintenance, and the|familiar Windows ‘look and | |System |management tool that | |data tables for |entire organization.|feel.’ | | |helps you store | |Huffman’s trucks and | | | |Microsoft |information for | |trailers, Tire | |Support – Best-selling desktop| |Access/Microsoft Word |reference, reporting, | |Maintenance, | |database with future support | | |and analysis. Microsoft|...

Words: 650 - Pages: 3

Premium Essay

Entities and Attributes for Fleet Truck Maintenance

...Proposed Purpose for the Database Huffman trucking utilizes this database to maintain and access important data about Huffman Trucking’s fleet vehicles such as vehicle and tire maintenance services, work orders, and unique vehicle identification information. Additional information that can be found in the database is vendor contact, parts inventory, and purchasing history. This database provides an efficient way to track and schedule routine maintenance, track parts inventory which helps prevent slowdowns in production. Parts Inventory Purchases Transaction ID Auto Number Primary Key Purchase Date Date/Time Purchase Price Currency Quantity Numeric Value Rationale of primary key – The Transaction ID should be a unique number which can be tracked back to the parts inventory purchase table and will make a perfect Primary Key. Rationale for foreign key 1 – There will be no foreign keys in this table as no other table for the Fleet Truck Maintenance will be using one of the values as a Primary Key. Rationale for foreign key 2 – There will be no foreign keys in this table as no other table for the Fleet Truck Maintenance will be using one of the values as a Primary Key Parts Inventory Issues Transaction ID Auto Number Foreign Key 1 Issue Date Date/Time Purchase Price Currency Quantity Numeric Value Parts Inventory ID Auto Number Primary Key Rationale of primary key – The parts inventory ID will be used as the primary key for the Parts inventory...

Words: 1514 - Pages: 7

Free Essay

Virtual Organization System Inventory

...Virtual Organization System Inventory Timothy L Welty BSA310 October 27, 2014 Peng Virtual Organization System Inventory Assignment: Select one of the following Virtual Organizations: * Huffman Trucking Complete the following chart, filling in information for each system used at the Virtual Organization. Add rows to the chart as necessary. Huffman Trucking “Huffman trucking is a national transportation company. The company's 1,400 employees work in its logistical hubs located in Los Angeles, California, St. Louis, Missouri, and Bayonne, New Jersey; its central maintenance facility is in Cleveland, Ohio; and as drivers of its 800 road tractors. The company expects to earn revenues during fiscal year 2004 in excess of $600,000,000 (Virtual Organization, 2014).” System Name | Brief Description | Department to Use the System | Purpose of the System | Connects With | Development Details | Finance & Accounting Systems | Application is licensed on an annual per user basis from a vendor specializing in F & A systems for the transportation industry | Finance and Accounting Systems | General ledgerAccounts PayableAccounts ReceivableCash ManagementBilling/InvoicingCredit/CollectionsCostingProperty ManagementAssetsTaxes | Integrated with the Fleet Maintenance System and the Enterprise Transportation Application | Maintenance costingFuel management and costingWarranty managementMaterials inventory managementFixed assets | System Name | Brief Description | Department...

Words: 449 - Pages: 2

Free Essay

Dbm/380 Learning Team Week Final Project

...The Huffman Trucking Company started in Cleveland, Ohio in 1936. The company is privately owned, and began as a single tractor-trailer company. This company is growing is size and acquiring rapid business growth. At present time, the company owns 800 road tractors, 2,100 45' trailers, and 260 “roll A on/roll-off" units. The Huffman Trucking provides logistics services to U.S. Government as well as to the private companies. (Huffman Trucking, 2012). Learning team D’s project is to develop database design documentation for Huffman Trucking for their fleet truck maintenance. Huffman trucking interviewed members of their staff from different departments and proposed entities and attributes for their database. Entities proposed are numerous: Parts Inventory Purchases, Parts Inventory Issues, Parts Catalogue, Vendors, Parts Purchasing History, Vehicle Maintenance, Tire Maintenance, Maintenance Descriptions, Vehicle Types, Vehicles, and Maintenance Work Order. (Apollo Group, 2007). The expected end result from Huffman trucking is documentation showing entity relationship diagrams with referential integrity, data entry forms, SQL table join query code with results, and a normalized database that observes the business rules proposed by Huffman Trucking. Stages of Development In the first stage of development, we took the list of entities and their attributes proposed by our client and acquainted ourselves with their business and processes. The entities proposed by Huffman Trucking...

Words: 2177 - Pages: 9

Premium Essay

Dbm 502 Expert Tutor/ Indigohelp

...DBM 502 Entire Course For more classes visit www.indigohelp.com DBM 502 Individual Assignment: Implementing an Enterprise DBMS DBM 502 Individual Assignment: Comparing Database Software PART 2 OF 2 DBM 502 Individual Assignment: Comparing Database Software PART 1 OF 2 DBM 502 Individual Assignment: Data Dictionary DBM 502 Individual Assignment: Database Security DBM 502 Learning Team Assignment: DBMS Implementation Plan ………………………………………………… DBM 502 Individual Assignment Comparing Database Software PART 1 OF 2 For more classes visit www.indigohelp.com Individual Assignment: Comparing Database Software Create a list of criteria that can be used to compare database software. Create a table that uses the list of criteria to compare and contrast Microsoft® Access, SQL, DB2, and Oracle®. Write a 2- to 3-page paper that discusses Refer to “Standards for Written Work” and “Standards•your results. for Presentations” in your Program Handbook, which can be accessed through the student Web site. ………………………………………………… DBM 502 Individual Assignment Comparing Database Software PART 2 OF 2 For more classes visit www.indigohelp.com Individual Assignment: Comparing Database Software Create a list of criteria that can be used to compare database software. Create a table that uses the list of criteria to compare and contrast Microsoft® Access, SQL, DB2, and Oracle®. Write a 2- to 3-page paper that discusses your results. Refer to “Standards for Written Work...

Words: 537 - Pages: 3

Premium Essay

Dbm 502 Learning Consultant / Tutorialrank.Com

...www.tutorialrank.com DBM 502 Individual Assignment: Implementing an Enterprise DBMS DBM 502 Individual Assignment: Comparing Database Software PART 2 OF 2 DBM 502 Individual Assignment: Comparing Database Software PART 1 OF 2 DBM 502 Individual Assignment: Data Dictionary DBM 502 Individual Assignment: Database Security DBM 502 Learning Team Assignment: DBMS Implementation Plan ---------------------------------------------------------------------------- DBM 502 Individual Assignment: Comparing Database Software PART 1 OF 2 (UOP) For more course tutorials visit www.tutorialrank.com Individual Assignment: Comparing Database Software Create a list of criteria that can be used to compare database software. Create a table that uses the list of criteria to compare and contrast Microsoft® Access, SQL, DB2, and Oracle®. Write a 2- to 3-page paper that discusses Refer to “Standards for Written Work” and “Standards•your results. for Presentations” in your Program Handbook, which can be accessed through the student Web site. ------------------------------------------------------------------- DBM 502 Individual Assignment: Comparing Database Software PART 2 OF 2 (UOP) For more course tutorials visit www.tutorialrank.com Individual Assignment: Comparing Database Software Create a list of criteria that can be used to compare database software. Create a table that uses the list of criteria to compare and contrast Microsoft® Access, SQL, DB2, and Oracle®. Write...

Words: 548 - Pages: 3

Premium Essay

Computer

...Week One: Database Architecture | | Details | Due | Points | Objectives | 1.1 Explain database architectures. 1.2 Define database systems. 1.3 Define relational database architecture. | | | Reading | Read Ch. 1, “Database Systems,” of Database Systems: Design, Implementation, and Management. | 9/24 | | Reading | Read Ch. 2, “Data Models,” of Database Systems: Design, Implementation, and Management. | 9/24 | | Reading | Read Ch. 3, “The Relational Database Model,” of Database Systems: Design, Implementation, and Management. | 9/24 | | Reading | Reference Ch. 1, “Getting Started,” of Database Concepts as a supplemental reading. | 9/24 | | Reading | Read Ch. 1, “Introduction to Access,” of Exploring Microsoft® Office Access 2010 Comprehensive. | 9/24 | | Reading | Read this week’s Electronic Reserve Readings. | 9/24 | | Participation | Participate in class discussion. | All week | 2 | Nongraded Activities and Preparation SkillSoft® Registration | The first time you access SkillSoft®, you need to register.Do the following to register for SkillSoft®: Go to https://uopx.skillport.com Register by clicking on Register. The Register button is in the lower right corner, below the login boxes.Leave the Organization Code field blank.Use your phoenix.edu e-mail address.Use your student website login name as your user ID (the name before the @email.phoenix.edu).Click Submit. | 9/24 | ...

Words: 2242 - Pages: 9

Premium Essay

Bsa 375

... | | |College of Information Systems & Technology | | |DBM/380 Version 9 | | |Database Concepts | | |July 16, 2012 to August 13, 2012 | | |Group KM11BIT13 | Copyright © 2012, 2010, 2008, 2007, 2006, 2005, 2003 by University of Phoenix. All rights reserved. Course Description This course covers database concepts. Topics include data analysis, the principal data models with emphasis on the relational model, entity-relationship diagrams, database design, normalization, and database administration. Policies Faculty and students will be held responsible for understanding and adhering to all policies contained within the following two documents: • University policies: You must be logged into the student website to view this document. • Instructor policies: This document is posted in the Course Materials forum. University policies are subject to change. Be...

Words: 3236 - Pages: 13

Premium Essay

Week 5 Summary

...Week 5 Summary Report DBM/380 February 16, 2015 Devin Dickens Week 5 Summary Report Our learning team is getting off to a great start to our assignment we have created Visio diagrams to design and organize our database. We have also got started with the beginnings of the database by working to set up the tables that we are going to be using. We have also begun work on creating our PowerPoint presentation for the project. It has been a busy week with varied schedules, but we have sectioned the work off and kept in touch this has served us well. We followed the link to Entities and Attributes for the Fleet Truck Maintenance page and have been working on how we are going to incorporate them all into our design. We will use relational links where applicable to tie all the tables together and select appropriate primary keys for our tables. We have also gone through the process of assigning appropriate data types for your fields. All in all, I think that we are off to a good start and are looking forward to adding to our project over the coming weeks. Week 3 Summary Report Our team was required to create documentation that explains the process of creating the entity-relationship diagram (ERD) in the change request for our project. We have three parts for our ERD: Vehicles, Parts, and Maintenance. Part One: Vehicles Our entities for the first part of our ERD are Vehicles, Vehicle Types, and Vehicle Maintenance. Our attributes for the entity Vehicle consist of VIN...

Words: 1227 - Pages: 5

Premium Essay

Indian Automobile Industry

...[pic] CHAPTER 1 INTRODUCTION INTRODUCTION The automobile industry is one of the largest industries in India as in many other countries. It plays a major role in the growth of economy in India. The automobile industry in India is the ninth largest in the world with an annual production of over 2.3 million units in 2008. The industry comprises automobiles and auto component sectors, which encompass passenger cars, two-wheelers, three-wheelers, tractors, commercial vehicles, multi- utility vehicles and components. Today, the Indian automobile industry is the world s largest motorcycle manufacturer, the second largest two-wheeler and tractor manufacturer, the fifth largest commercial vehicle manufacturer and the fourth largest car maker in Asia. Apart from serving the domestic market, the Indian auto sector has also become a sourcing hub for the global auto giants. In 2009, India emerged as Asia's fourth largest exporter of automobiles, behind Japan, South Korea and Thailand. The Government of India has introduced an ambitious project of setting up world-class automotive testing and R&D infrastructure to place India in the USD 6 trillion global automotive business. This book details the current status and factors influencing the growth of the Indian automobile industry; its future prospects and the success stories of some automobile giants in India. It also focuses on the future growth of the industry as a result of the newly adopted technologies and strategies...

Words: 14693 - Pages: 59

Premium Essay

Heath Care Policy Legislation Stage

...***AFF*** ***1AC*** Inherency – 1AC Contention one: Inherency The new FAA bill cut funding for the AIP, which will cripple our airport infrastructure – rapid investment is critical PRINCIPATO ‘12 - president, Airports Council International-North America; M.A. in International Relations from University of Chicago; International Trade and Transportation specialist, Hunton & Williams (Greg, “Why we should invest today in 'Airports Inc.'”. March. http://thehill.com/blogs/congress-blog/labor/218525-faa-why-we-should-invest-today-in-airports-inc) With the latest Federal Aviation Administration (FAA) forecast predicting a doubling of passengers and cargo by 2030, the current funding system is not up to the job of ensuring airports will have the infrastructure they need to handle such dramatic increases in traffic. This will have far-reaching consequences. Commercial airports are powerful economic engines, generating 10.5 million jobs and $1.2 trillion for the U.S. economy, according to a new Airports Council International-North America study. Across the country, workers and businesses count on local airports to attract investment and move people and goods around the world. Since 2001, the total number of jobs associated with airports has increased by more than 50 percent. Despite unprecedented growth and clear evidence of the economic benefits of infrastructure investments, airports expect to have $80 billion in unmet needs through 2015 because of the flawed system...

Words: 41248 - Pages: 165