“I bought this guide a few days ago to prepare for my interview with Oracle. Many of the questions they asked me were from this guide. I found this book absolutely great!”
Top-down programming may complicate testing, since nothing executable will even exist until near the end of the project.
Bottom-up programming may allow for unit testing, but until more of the system comes together none of the system can be tested as a whole, often causing complications near the end of the project
An electronics engineer will wish to employ bottom up analysis…and then:
Create a series of drivers to ‘control’ the hardware
A sofware engineer will emply top down analysis…think about things a little…drink some coffee…and then:
Create a set of drivers that force the hardware to do what he/she wants
Top Down Programing: Break a large program in to smaller components and build the system in this way in top to down manner.
Usually done in C,C++ Java etc where a function is split into subfunctions etc.
Bottom Up Programing : Build up the smaller constructs like operators and functions first and then construct the complex programing using these smaller constructs. Stop when the task under consideration is completed.
Usually done in functional programing languages like Lisp.
In S/w testing,Integration testing have the types top down approch & bottom up approch.
In top down approch we test the product form top (start product) towards down.
In bottom up approch the testing will be from bottom (endproduct) towards up side.
One more type of integration testing is big bang approch
Bottom up approach: build components first, test, and then put them together to build up functionality of an application. Like Extreme Programing.
Top down: plan out and architect functionality of the application first, subdivide the problem into parts, and then implement components within a greater planned framework.
In bottom up approach,the software testing is performed from low level to high level
In top down approach, the testing is performed from high level to low level
Refer software engineering by Roger .S.Pressman
Top-down programming may complicate testing, since nothing executable will even exist until near the end of the project.
Bottom-up programming may allow for unit testing, but until more of the system comes together none of the system can be tested as a whole, often causing complications near the end of the project
Typically:
An electronics engineer will wish to employ bottom up analysis…and then:
Create a series of drivers to ‘control’ the hardware
A sofware engineer will emply top down analysis…think about things a little…drink some coffee…and then:
Create a set of drivers that force the hardware to do what he/she wants
Question was just about approach. I suppose.
Top Down: Start from root and go to the end products.
Bottom Up: Start from products or result and going to the root
Top Down Programing: Break a large program in to smaller components and build the system in this way in top to down manner.
Usually done in C,C++ Java etc where a function is split into subfunctions etc.
Bottom Up Programing : Build up the smaller constructs like operators and functions first and then construct the complex programing using these smaller constructs. Stop when the task under consideration is completed.
Usually done in functional programing languages like Lisp.
In S/w testing,Integration testing have the types top down approch & bottom up approch.
In top down approch we test the product form top (start product) towards down.
In bottom up approch the testing will be from bottom (endproduct) towards up side.
One more type of integration testing is big bang approch
Bottom up approach: build components first, test, and then put them together to build up functionality of an application. Like Extreme Programing.
Top down: plan out and architect functionality of the application first, subdivide the problem into parts, and then implement components within a greater planned framework.
Each as its advantages.
Top down approach is like the overview of the system, but bottom-up approach is like the individual element of the system in details.
Leave an Answer/Comment