Database design process

Abstract

Database Systems has a practical, hands-on approach that makes it uniquely suited to providing a strong foundation in good database design practice. Database design is more art than science. While it's true that a properly designed database should follow the normal forms and the relational model, you still have to come up with a design that reflects the business you are trying to model. This paper shows describes design process of database project.

The importance of Completing the Design Process

An important point to keep in mind is that the level of structural integrity and data integrity is in direct proportion to how thoroughly the design process is followed. The less time spent on the design process, the greater the risk of encountering problems with the database. While thoroughly following the database design process may not eliminate all of the problems you may encounter when designing a database, it will greatly help to minimize them. Also in an RDBMS software program a well-designed database is easier to implement than a poorly designed database. (Michael J. Hernandez, 1996)

Key database Design Concepts

Before a design effort can proceed full speed ahead, the designer must first take time to understand the business. Understanding the business involves understanding the entities, data, and rules within an organization, and then converting these attributes of the business into a business model. Then, the designer must have a solid comprehension of the proposed database model. Finally, the designer will convert the business model into a database model, using a design methodology, whether automated or a manual process.

(Ryan Stephens & Ronald Plew, 2002)

General Design Process

Following table list general steps of database design

Step Description

1 Requirements collection and analysis

2 Conceptual database design

3 Choice of a DBMS

4 Data model mapping (also called logical database design)

5 Physical database design

6 Database system implementation

(Elmasri, Ramez, & Navathe, Shamkant B., 1994)

Creating the application is the last step¡ªnot the first! Many developers take an idea for an application, bu...

... middle of paper ...

... levels of normalization, but the primary levels are the first, second, and third normal forms. Each level has a rule or two that must be followed. Following all of the rules will help ensure that your database is well organized and flexible.

To take an idea from inception through to fruition, you should follow a design process. This process essentially says "think before you act." Discuss rules, requirements, and objectives, and then create the final version of your normalized tables.

Reference

1. Elmasri, Ramez, & Navathe, Shamkant B., Fundamentals of Database Systems, Second Edition, Addison-Wesley Publishing Company, 1994, ISBN 0-8053-1748-1, pages 450-452.), retrieved from website http://www.ibiblio.org/faint/finosaur/db/ , Feb 06, 2005

2. Michael J. Hernandez, Database Design For Mere Mortals, Chapter 4, 1996, retrieved from UOP resource safari Tech Books Online website, Feb 06,2005

3. Ryan Stephens & Ronald Plew, Key database design concepts, 2002, retrieved from website http://searchdatabase.techtarget.com/originalContent/0,289142,sid13_gci812028,00.html, Feb 06, 2005