Difference between Top down approach and bottom down approach

The difference between the Top-down approach and bottom down approach is:-

 Top-down Approach

- Top-down estimating method is also called Macro Model. Using the top-down estimating method, overall cost estimation for the project is derived from the global properties of the software project, and then the project is partitioned into various low-level components.

 - This method is more applicable to early cost estimation when only global properties are known. In the early phase of software development, It is very useful because there is no detailed information available. This approach starts at a system level. The estimator starts by examining the overall functionality of the product and how that functionality is provided by interacting subsystems. 


Advantages

  • It focuses on system-level activities such as integration, documentation configuration management, etc, many of which may be ignored in other estimating methods and it will not miss the cost of system-level functions.
  • It requires minimal project detail, and it is usually faster, easier to implement

Disadvantages

  • It often does not identify difficult low-level problems that are likely to escalate costs and sometimes tends to overlook low-level components.
  • It provides no detailed basis for justifying decisions or estimates.



Bottom-up  Approach

Using the bottom-up estimating method, the cost of each software component is estimated and then combines the results to arrive at an estimated cost of the overall project. It aims at constructing the estimate of a system from the knowledge accumulated about the small software components and their interactions. The leading method using this approach is COCOMO's detailed model.


Advantages

  • It permits the software group to handle an estimate in an almost traditional fashion and to handle estimate components for which the group has a feel.
  • It is more stable because the estimation errors in the various components have a chance to balance out.


Disadvantages

  • It may overlook many of the system-level costs (integration, configuration management, quality assurance, etc.) associated with software development,
  • It may be inaccurate because the necessary information may not available in the early phase.



Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

Discuss classification or taxonomy of virtualization at different levels.