100%(1)1 out of 1 people found this document helpful
This preview shows page 11 - 12 out of 12 pages.
modified at this stage, and any problems identified are fixed. This isdone by the use of normal forms. A normal form is a specific set of rulesthat can be used to test a table structure to ensure that it is sound andfree of problems.The database design process is summarized as follows:1. Determine the purpose of the database2. Gather and organize the information required such as product namesand order information3. Divide the information into tables or major entities such as productsand orders4. Turn the information or items into columns by deciding on whatinformation to be stored in each table, with each item becoming a field5. Specify primary keys for each table to uniquely identify each row. Forexample product ID or order ID6. Set up table relationships by deciding how data on one table is relatedto the data in other tables or create new tables to clarify relationships.7. Refine the design by analyzing the design for errors and makingadjustments as needed.8. Apply the normalization rules to ensure that the tables are structuredcorrectly.The design method used need not be complicated and should not bedifficult to understand. The process should be presented in astraightforward manner and each concept clearly explained.ConclusionDatabases are shared resources that are used by many units within anorganization and require significant investment to build. They howeverbring significant benefits to an organization. Computer analyst andprogrammers may also use them in ways not originally envisioned.Therefore database designs must meet current organizationalrequirements and must be adaptable to future requirements andexpansion.
ReferencesWhitten, J., & Bentley, L. (2007). Systems analysis and design methods:2008 custom edition(7th ed.). Dubuque, IA: McGraw-Hill.Hernandez, M.J. (2008). Database Design for mere mortals (2nf Edition).A hands-on guide to the relational database design. Addison-Wellesley.DatabasedesignRetrievedNovember1st,2011fromDavidson, L. (2007). Ten common database design mistakes. RetrievedNovember 1st, 2011 from -administration/ten-common-database-design-mistakes/