Top-Down and Bottom Up Processes
The process of starting with world objects and modeling using entity-relationship diagrams is referred to as a top-down process. Starting with one large table and functional dependencies using normalization is referred to as bottom-up 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? Top-Down and Bottom Up Processes Top Down Top-Down is deductive reasoning. It can be used in conjunctions with analysis and decomposition. Breaking down a system to gain insight into different elements is the top-down approach. First a total system is developed, and then subsystems are detailed. There may be many different levels until everything is reduced to a whole. To put it in simple terms, top-down approaches start with the big picture. This concept is broken down into smaller segments for ease of understanding and learning. In business top down can be ill