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. Bottom – up design method. The bottom-up approach begins with the specific details and moves up to the general. This is done by first identifying the data elements (items) and then grouping them together in data sets. In other words, this method first identifies the attributes, and then groups them to form entities.
Nov 27, · Bottom-up. The Bottom-up approach starts with the particular points of interest and climbs to the general, higher level views later down the line. To start a bottom-up plan, the designer will assess every one of the interfaces that the database has, checking tables, relationships and views. Jan 25, · When the database design is for a small organization or a section of a large organization, we employ bottom -up approach. Here we have fewer number of entities, attributes, and relationships to manage. The volume of data may also be less. Bottom -up approach first defines the data elements (attributes) See below figure. Bottom Up Approach.
The application approach is a bottom-up design because it focuses primarily on how data will be viewed (either on screen or in reports or other special documents) and only secondarily on how it will be organized. In other words, the database is designed to fit the application. In contrast, bottom-up approaches view database design as proceeding from an initial analysis of lower-level conceptual units, such as attributes and functional dependencies and then moving towards an acceptable logical data model through logical groupings of .