Download This Paper

Development, Style

Running head: HUFFMAN TRUCKING Huffman Transportation: Database Design and Development Huffman Trucking started out like a single owner, single pick up truck and trailer, operating in the Cleveland Kentkucky area in 1936 carrying out local agreement hauls. Today, Huffman Transportation is a National carrier with 1, 500 employees, 800 tractors, 2, 100 trailers, and 260 roll-on/roll-off products, operating via 3 logistical hubs located in Los Angeles, California, St . John, Missouri, and Bayonne, Nj and its central maintenance facility located in Cleveland Ohio (Apollo Group Inc.

, 2005).

Together with the growth over time, Huffman Transportation has managed their competition by being a market leader in leveraging technology to the optimum to provide customer service and business efficiencies (Apollo Group Incorporation., 2005). In the means to keep this competition, Huffman Transportation hired Johnson Systems Talking to to develop a written report of agencies and attributes that will be required for a Fleet Truck Repair Database. Upon receipt of Smith’s statement detailing the entities and attributes necessary, our THIS Manager published a Service Request SR-ht-003 to create a Navy Truck Protection Database.

In this posting LTA is going to discuss the database structures briefly and first keys, which usually play a vital role in an Entity-Relational Database. The discussions in the different types of mistakes that are made in the design phase that led to a poor repository design are usually discussed. Faults include the not enough careful planning, proper normalization of data, poor naming conferences, lack of sufficient documentation and extensive assessment. The ERD for the database will be revealed combined with choice of this program to manage the database and allow for versatility for several platforms, applications, and features.

Huffman Trucking’s fleet pickup truck maintenance documents are pretty straight-forward, consequently , a basic repository design structure is recommended to start with in the entrance of information, and importing of current databases records into the new basic database. By simply starting straightforward, this repository can be upgraded over time, while the company grows and the fleet grows. The important items to consider when designing a fresh database include: ease of use pertaining to the users, the availability of issue reporting, and also financial data, parts orders, maintenance data, and purchase rders. “A very good model and a proper repository design constitute the foundation of an info system. Building the data level is often the first critical step towards implementing a fresh system, and getting it proper requires awareness of detail and a whole lot of careful preparing. A databases, like any computer system, is a type of a small bit of the real world. And, like any version, it’s a slim representation that disregards most of the complexity in the real thing (Malone, 2007). A primary important, which is a record or an attribute, distinctively identifies a table.

Primary keys help to make mapping relational data basic, in order to uniquely identify every entry inside the database. The concept of some sort of unique value is common in database developing ” using account amounts to identify parts, vendor figures, and protection work requests. These are also called natural tips, common entities that are used to uniquely determine objects. Generally, if the data that is getting modeled contains a decent normal key, or identifier, that information should not be used as a primary crucial.

Natural secrets should not be utilized as major keys, because the purpose of the principal key is to uniquely discover a value within a database record. Several primary key characteristics are the principal key must be able to discover each row in a table. The primary crucial should not identify the characteristics in the entity. An important part number ID of “2566 is usually preferred over “Air Filter.  The value of , the burkha key should not change. Changing a primary important value means changing the identity of the entity. Changing the identity is not advised. Non-intelligent keys are preferred since they are less likely to alter.

For example , the business number 2566 for an Air Filter for just one model of vehicle, and the item number of 2560 would be a great Air Filter another model of vehicle. To have just a part number of “Air Filter would be also ambiguous, and could result in lost time planning to locate the correct air filter for the specific type of truck. These part numbers, generally speaking would more than likely never change over time, consequently , are best for primary important factors in a databases of parts. Primary important factors should have the tiniest number of features possible.

It truly is easier to take care of unique keys that are numeric. Items to Consider During Style Phase Several things that are easy to overlook throughout the database style process include design and planning with the database, normalization of data, insufficient naming exhibitions, documentation, and testing. A brief run-down of such common mistakes during the design phase of a database shows up below. By simply listing all of them now, you can use it as a powerful guideline to adhere to when designing the database intended for Huffman Trucking’s Fleet Repair. Design and Planning in the Database

Very good databases managed with careful believed, and with the proper care and interest given to the needs of the data that is part of this. Since a carefully created database are at the cardiovascular system of every organization project, not enough planning and detailing with the needs with the project could cause the whole job to lose their direction and purpose. Additionally , by not really taking the time at the beginning, any modifications in our database structures that may be needed to be made in the future could cause disastrous consequences generally speaking project, and greatly improve the likelihood of the project schedule slipping.

If the planning period is rushed, problems can inevitably arise, and because in the lack of appropriate planning and design, there exists usually little time to go back and fix any issues correctly. “That is definitely when the ‘hacking’ starts, with the veiled assurance to return and fix items later, something that happens in rare cases indeed (Davidson, 2007). Normalization of Data Normalization defines some standards to be able to down tables into their fundamental parts until each table represents only one thing, and its particular columns totally describe that the desk represents.

Normalizing the Huffman Trucking’s info is important to make sure proper functionality and easy future development projects. Insufficient Naming Events Naming events are many the important distinctive line of documentation for almost any application. What is important to consider is the significance of consistency. Labels should be retained simple while at the same time, identifying their particular purpose for the data becoming entered. Documents Not only will a well-designed database comply with certainly top quality tandards, it will also contain definitions and illustrations about the tables, so that its purpose is clear to everyone how the dining tables, columns and relationships usually are meant to be used. The objective of proper documentation should be to give enough information for the support programmer to find any kind of bugs and fix them easily. Testing Numerous Information Technology professionals know, the initial thing to be blamed when a organization system starts running slow is basically because the database can get bogged down with fragmented data, or a lot of information.

Deep knowledge of the program is the best way to eliminate this notion Unfortunately, testing is the usually one of the things to visit in a project when time starts to be depleted. What is important to consider in this kind of whole method is that deep system assessment is done to make sure that the design is definitely implemented correctly. The first actual test is made for any data source is in order to goes into development, and users attempt to carry out real operate. And if the device does not work fast enough, or contains pests when it goes live, in that case more function will have to carried out on a live system, which could inherently cause the loss of revenue of any business.

By requiring on tight testing as an important aspect of database creation, then possibly the day can come when the repository will not be the very first thing to be mentioned when the program slows down. In order to accomplish the purpose of establishing a functional database that Huffman can use now in addition to the future to effectively manage their info, it is recommended that Huffman Trucking choose MySQL. There are many great things about MySQL, including the reality MySQL is very popular among web applications and acts as a database for a multitude of platforms.

A few of these platforms consist of FreeBSD, BSDi, AIX, HP-UX, Linux, Novell NetWare, OS/2 Warp, Solaris, i5/OS, House windows 95, Solaris, Windows 98, SunOS, House windows ME, House windows 2000, Windows XP, and Glass windows Vista. MySQL is well-liked by open source code and bug tracking tools such as Bugzilla as well. MySQL is drafted in C and C++. Libraries that are used to access MySQL databases can be found in many of modern-day programming ‘languages’ by using dialect specific API’s. There is also a Database On-line (ODBC) that enables additional encoding languages to communicate with MySQL, including ColdFusion or ASP.

MySQL features options which are not in many different RDBMSs. One particular feature which is not included in a large number of RDBMSs can be multiple storage engines. This feature allows for a user to select the most effective storage area engine for each table inside the application. Good feature that MySQL gives is indigenous storage search engines. These are storage area engines which can be developed by MySQL and are maximized for certain application storage area domain. They provide data warehousing, data storage, high availability clustering, and many more features. MySQL recently designed a new advanced transactional storage area engine referred to as Falcon.

Falcon was designed pertaining to modern day businesses and web applications that makes it perfect for Ryan Trucking. 1 feature to not be forgotten is the availability of Partner-developed safe-keeping engines. Search engines that are partner developed happen to be developed acquire outside companies, but they are then highly examined by MySQL in order to make sure workability and compatibility with MySQL. MySQL also has free programmers that are independent and develop storage space engines. These are used as well, but simply after they go MySQL rigorous inspection and testing.

Buyers are even growing and creating community storage space systems. Make grouping is actually a MySQL feature that allows pertaining to the gathering of multiple transactions. This really is done from a multitude of connections in order to improve the number of does per second. Conclusion In summary the Fast Truck Routine service Database will be easy to use, provide effective tracking of funds, maintenance, and queries. The principal key(s) found in the database will have the next characteristics: certainly be a single attribute, uniquely determine an entity, be non-intelligent, not alter over time and become numeric.

This will likely ensure the ease of normalizing the database during the design period to prevent upgrade anomalies once database is implemented. LTA discussed a number of mistakes that occur through the design phase in order to avoid the same mistakes. These types of mistakes consist of poor design/planning, ignoring normalization, poor identifying standards, insufficient documentation and testing. The DBMS of preference for Huffman Trucking is usually MySQL. MySQL will efficiently manage each of our data while allowing many different platforms to interact with the database.

MySQL is written in C and C++. However , MySQL offers much versatility in programming different languages by using dialect specific API’s or ODBC to allow added programming languages such as ASP or Coldfusion. MySQL has many options that other RDBMSs do not any possess including multiple storage engines, open source programmers, devote grouping and more. Bottom line is the fact MySQL provides versatility intended for our repository to allow for ongoing growth, revisions and within our company’s needs. Recommendations Apollo Group Inc. (2005). Huffman Trucking.

Retrieved Oct 1, 08, from Huffman Trucking Intranet: https://ecampus. phoenix. edu/secure/aapd/CIST/VOP/Business/Huffman/HuffmanHome002. htm DavidsonL., (2007). Ten Common Database Design and style Mistakes. Simple-Talk. com. RetrievedSeptember29, 2008, fromhttp://www. simple-talk. com/sql/database-administration/ten-common-database-design-mistakes/ MaloneM, (2007). I’m Mike. Database Design and style: Choosing A Principal Key. RetrievedOctober1, 2008, fromhttp://immike. net/blog/2007/08/14/database-design-choosing-a-primary-key/

Need writing help?

We can write an essay on your own custom topics!