Testing without Requirements
In this presentation I present a case study on what to do when you are asked to test but requirements are NOT available.
The classical approach assumes requirements form the basis for testing bug reality is a lot of Development is done without written documentation. What is the test basis in this case? Should you wait or are other techniques or approaches available to start your testing activities.
I present an approach based upon a function tree and P-diagrams from mechanical engineering.