Fakruddin Khan

Mar 30th, 2012

The top-down method starts from the general and moves to the specific. Basically, you start with a general idea of what is needed for the system and then ask the end-users what data they need to store. The analyst will then work with the users to determine what data should be kept in the database. Using the top-down method requires that the analyst has a detailed understanding of the system. The top-down method also can have shortcomings. In some cases, top-down design can lead to unsatisfactory results because the analyst and end-users can miss something that is important and is necessary for the system.

The bottom-up approach begins with the specific details and moves up to the general. To begin a bottom-up design, the system analyst will inspect all the interfaces that the system has, checking reports, screens, and forms. The analyst will work backwards through the system to determine what data should be stored in the database.