Explain how the bottom-up design approach differs from the top-down design approach—database
Explain how the bottom-up design approach differs from the top-down design approach—database development using the bottom-up approach or the top-down bottom according to its complexity. The bottom-up approach begins with essential attributes towards the relationships of those attributes. In contrast, the top-down approach starts with developing models that contain a higher level of entities and relationships towards the lower ones. The bottom-up approach is when transferring a database from one physical database to another. Simultaneously, the other is used when developing a new database at a logical level and later applying the objects to physical database design. For instance, using the bottom-up approach to migrate the Oracle database, which falls under the relational database management systems to IBM DB2, which needs changes in the data types. The bottom-up approach modules require interaction between the fundamental attributes for combination purposes while the top-down approach does not require communication. Besides, the bottom-up approach uses the concept of abstraction, which involves hiding the implementation details while sub-models are separately processed. Another key difference is that developers and database administrators utilize bottom-up in testing.…