|
Big-Bang Strategy
Glossary of Software QA/Testing
(Continued from previous question...)
Big-Bang Strategy
Big-Bang approach is very simple in its philosophy where basically all the modules or builds are constructed and tested independently of each other and when they are finished, they are all put together at the same time.
The main advantage of this approach is that it is very quick as no drivers or stubs are needed, thus cutting down on the development time.
However, as with anything that is quickly slapped together, this process usually yields more errors than the other two. Since these errors have to be fixed and take more time to fix than errors at the module level, this method is usually considered the least effective.
Because of the amount of coordination that is required it is also very demanding on the resources.
Another drawback is that there is really nothing to demonstrate until all the modules have been built and integrated.
(Continued on next question...)
Other Interview Questions
| 