Can Model Based Testing reduce silo between different resource group with in project.

Silo in SDLC

In the current traditional practice, manual tester initially understands requirement either by discussing with the analyst or customer or through the specification documents; subsequently he waits till application prototype is ready. Once prototype is completed, tester uses prototype as a reference and starts writing test cases with his understanding. Once test cases are ready, they undergo review. As test cases are written with tester’s understanding, (1) it is difficult to validate an individuals understanding, because of which most of the bugs logged are rejected. (2) Sometimes developer also understands few requirements differently and implement accordingly; this gets detected only testing phase. Later, it takes lot of efforts to convince developer to make understand his mistake and then fix that issue, which is very much time consuming.

 Is there a way to resolve the silos between developer and the tester?

MBT reduces silo in SDLC

Yes, Model Based Testing has capabilities to solve or reduce this silo. In Model based testing, tester understands the requirements and creates a model of his understanding. With this model, reviewer can easily understand his level of understanding by walking through the model and suggest or correct his mistakes. Also there are high chances of correcting requirements related issue.

Once the model is reviewed and approved, this model can be sent to the developer as a reference to understand the specification. This gives clarity and synchronize requirement understood across development and test phase resources.