1. A Database for RoboBoys
MIS405-1301A-01 Database Systems
Phase 1 Individual Project
Sabrina Mergenthaler
Colorado Technical University
Professor Anita Arceneaux
January 14, 2013
2. Brief History
•First conceived by Dr. Edgar F. Codd in
1969
•Solves failing features of earlier database
designs
•Redundancy, integrity of data, over
dependency on physical implementations
Concept of RDBMS
Concept
•Relation of data
•Mathematical disciplines and structure
•Unique language
•User Friendliness
•Features and functions
•Most widely used model for business of all
sizes
4. Features
•Built-in multilevel integrity
to ensure the accuracy of the data; records are not
duplicated; detect missing primary key values; ensure
Validity between tables; and data is accurate in terms of
business rules (Hernandez, 2003).
•Logical &physical data independence
from database applications
assurance that changes made by the user will not
adversely affect applications upon which the database is
built (Hernandez, 2003).
•Guaranteed consistency and accuracy
in data
Data is congruent with the various levels of integrity
imposed within the database (Hernandez, 2003).
•User-friendly design for viewing and
manipulation of data
data can be retrieved from a particular table or from any
number of related tables within the database. Enabling
the user to view information in a variety of ways
(Hernandez, 2003).
Commonplace in Business
•Enterprise resource planning (ERP)
•Human resources management systems
•Accounting
•Customer relationship management (CRM)
•Sales automation
•Online transaction processes
•Business Intelligence
(Relational Database Application for Business, n.d.)
5. Architecture
•Objectives of good design
•Design supports
data/information exchange
•Efficiently constructed
tables
•Data integrity
•Promotes company
growth
•Architecture
•Congruency between
related tables by following
final table lists to define
table sets
6. Grewal, D. & Levy, M. (2012). Marketing (Third Edition ed.). New York, NY: McGraw-
Hill/Irwin.
Hernandez, M. J. (2003). Database Design for Mere Mortals™: A Hands-On Guide to Relational
Database Design (Second ed.). Boston, MA: Addison-Wesley Professional.
Introduction to Databases And Database Design. (n.d.). M.U.S.E. Database Systems. Colorado
Technical University. Retrieved from
https://campus.ctuonline.edu/courses/MIS405/p1/hub1/5119.pdf
Relational Databases. (n.d.). M.U.S.E. Database Systems. Colorado Technical University.
Retrieved from https://campus.ctuonline.edu/courses/MIS405/p1/hub1/3270.pdf
Relational Database for Business Applications. (n.d.). M.U.S.E. Database Systems. Colorado
Technical University. Retrieved from
http://coursebuildercontent.careeredonline.com/Assets/10000/4105.pdf
Editor's Notes
Welcome and Introduction
As RoboBoys has already experienced throughout the course of its life, a strong customer base brews opportunity. More simply put—the bigger your list, the more you are likely to sell (Grewal & Levy, 2012). RoboBoys certainly does not lack a list. However, the company does lack a well-managed system for storing, retrieving, and editing data regarding the members of their list. For this reason, we have focused on the creation of a data management system that works for RoboBoys.
We have briefly discussed the various pros and cons of particular database management systems; and I introduced you to relational database management systems (RDBMS). As the consulting agent for RoboBoys, my recommendation for strengthening the success of the company’s goals is reliant on the implementation of an effective RDBMS that can evolve with RoboBoys. Throughout this presentation I will provide you with an in-depth look at the purpose, function, and structure of a relational database management system that will take RoboBoys beyond their goals and ensure a strong foot in the future (Hernandez, 2003).
Concept Behind the Relational Database
First envisioned by Dr. Edgar F. Codd in 1969, the relational database model was built with the use of mathematical disciplines and structures. This design was in response to solving common problems in database management (Hernandez, 2003). These problems included repetitive, dirty data and database structures which were too dependent upon physical attributes. Built on the concept of relations in data, coupled with the use of a mathematical approach, and evolution in technology, today’s relational database models are the most popular among businesses of all sizes (Introduction, n.d.).
It is important to note that a RDBMS is more than an organized way to hold data. In fact, relational databases are special databases which reflect the understanding that data does not live in a vacuum, but is interconnected in such ways that adjustment to some data may affect other data. For this reason, it is referred to as a relational database for its relation of data across multiple tables (Relational Databases, n.d.).
As you can already tell, a relational database is reliant on user understanding, and good design. That is, the formulation of the database should be congruent with the intended functions, otherwise there is no means for manipulating it accordingly (Introduction, n.d.). Using relational database management system (RDBMS) software programs we can develop, use, and manage a relational database that fits the needs of RoboBoys. However, as it requires a full comprehension of terminology, structure, and function—let us focus on those components for a moment (Hernandez, 2003). Relational database design—just as any other skill—has a language of its own (Introduction, n.d.).
Terminology
Ultimately, relational databases management systems are used to manage the design, storage, and maintenance of large volumes of data into records. It allows for complex inquiries, manipulation of data, and services a wide variety of industries with more specific features (Relational Database for Business Applications, n.d.). Before we can begin discussing those features, though, it is important to familiarize ourselves with the terminology behind the structure and features of the RDBMS. Understanding these terms is important, because they are used to express ideas and concepts upon which the relational database model is built. As they are also used to express database-design processes, it becomes clearer and much easier to understand once you are familiar with the terms. Fortunately, these terms are standard throughout the world of database management (Hernandez, 2003). The terms of a RDBMS are divided into four categories: value-related, structure-related, relationship-related, and integrity-related—with each term holding significant meaning in the relational database world (Introduction, n.d.).
Value-related terms include data, information, and null. An analogy that aids in understanding these terms is to look at a book. When we look at the value-related terms such as data, information, and null, we identify data as the values stored in the database. In relating this idea to a book, data is like letters. These letters are meaningless until combined into words. Information derives from data. It is the sense that is made of data to make it meaningful and useful to the user. In a book, this is where your letters (or the data) are turned into words. Thus, from data comes information. Nulls are simply the term for missing data. Not to be confused with a zero, or any text value—a null, when used properly is crucial to correcting erroneous data (Hernandez, 2003).
In looking at the structure-related terms (table, field, record, view, keys, and index), a relational database holds data (which are in turn information) in fields (such as first/last name, address, state, city, etc). Fields are combined to create a record. These records are then compiled into a table of similar records. Joined together by their relationships, these tables form a database. The relationships are simply representations of the rules of the particular company. These rules, along with their relationship types, are generally outlined in a schema to record the structure of the database (Relational Database, n.d.).
Using the functions of the database opens a wide opportunity in businesses—when used effectively. A crucial component of using a database means maintaining data integrity (that is, the accuracy, up-to-datedness, and consistency) across varying levels of integrity (Relational Database, n.d.). These include:
Table-level integrity (which ensures no repetition throughout records within the table and that fields of each record within the table are unique and never null);
Field-level integrity (which assures the structure of fields are sound; values are valid, consistent, and accurate; while ensuring that fields of the same type are consistently identified throughout the database); and,
Relationship-level integrity (which certifies the relationship between tables is sound and the records within the tables are synchronized as data altered within the table) (Hernandez, 2003).
Features of a Relational Database Management System
Relational database management systems are commonplace throughout nearly every industry, from front to back, due to their ability to identify and provide solution to many business problems (Relational Database Application for Business, n.d.). Above, you can see just some of the industries in which these programs have had a great impact. Their significance to business, requires that certain features be available across the span of available programs. Such features include:
Built-in multilevel integrity
Logical and physical data independence from database applications
Guaranteed consistency and accuracy in data
User-friendly design for viewing and manipulation of data (Hernandez, 2003)
These are described above.
Architecture
To reduce errors, the relational database model is designed on mathematical theories and structure, thus making the relational model architecturally sound and reliable. This type of theory describes the foundation used to create a relational database, and identifies the rules on how it should be set up. The objectives of good design involve assuring that the design supports data information requests, contains efficiently constructed tables, imposes data integrity at multi-levels, supports the rules of business, and most importantly—lends to the growth of the company (Introduction, n.d.).
Most relational databases are large and accordingly constructed and stored on servers. This is often referred to as a client/server architecture in which users can connect to servers (where the database is stored) with the use of a username and password. While logged on, users can perform inquiries and make any necessary changes (Relational Databases). Designers must maintain congruency throughout the development of the program by using a series of lists, such as the preliminary table list, which help build data tables, linking tables, subset tables, and validation tables. Using these tables and lists to maintain a consistent index allows for the complex inquiries of the user (Hernandez, 2003).
Conclusion
Without a doubt, RoboBoys is progressing beyond imagine. That is no reason to let it get away from us, though. With the right data management system in place, RoboBoys can begin functioning as a fully automated facility, with you at the head—doing what you love to do: build robots. A relational database management system will not only give you the ability to store information about your clients and customers, but it will allow you to build upon that customer base by adding value to your list, and capabilities to what you can do with that list. Additionally, the right program in place will not only alleviate many of the burdens that come with a business, but it will allow RoboBoys to grow progressively. RoboBoys is ready to take the next step into expanding the empire, and through the implementation of a strong data management system, you are well on your way.