Explore BrainMass
Share

Bottom-up vs Top-down Database Design

This content was STOLEN from BrainMass.com - View the original, and get the already-completed solution here!

I need detailed (elaborate) help with the following question with all cites duly referenced.

Question
The process of starting with world objects and modelling using entity-relationship diagrams is referred to as a bottom-up process. Starting with one large table and functional dependencies using normalization is referred to as top-down development. What are the advantages and disadvantages of each method? Are there any inherit dangers with either method? Which would you prefer to use? Is it really an either-or situation?

© BrainMass Inc. brainmass.com October 25, 2018, 9:52 am ad1c9bdddf
https://brainmass.com/computer-science/databases/bottom-up-vs-top-down-database-design-589409

Solution Preview

Dear Student,

Entity-relationship diagram (ERD) approach was introduced by Chen (Chen, 1976). Lewis et.al. say it is a design methodology and not a data model. The main components of ERD are entity and relationship. Entity models the objects that are involved in an enterprise. Relationship models the connections among the entities.
ERD remains that they enjoy comparatively little by way of a solid ...

Solution Summary

A brief but detailed introduction to database design. The process of starting with world objects and modelling using entity-relationship diagrams is referred to as a bottom-up process. Starting with one large table and functional dependencies using normalization is referred to as top-down development.

$2.19
See Also This Related BrainMass Solution

Database management system for an EHR and design strategies used.

If you were building an EHR, discuss the database management system you would use. Give an explanation of the design strategies used.

View Full Posting Details