Anatomy of Model Based Testing
Keerthi Kumar Narayan1, Sharan Kumar Paratala Rajagopal2

1Keerthi Kumar Narayan, Senior Member Technical Staff, Bangalore, India.
2Sharan Kumar Paratala Rajagopal, Senior Manager, Capgemini America, Inc., Dallas, Texas, USA.

Manuscript received on May 25, 2020. | Revised Manuscript received on June 29, 2020. | Manuscript published on July 30, 2020. | PP: 999-1002 | Volume-9 Issue-2, July 2020. | Retrieval Number: B4053079220/2020©BEIESP | DOI: 10.35940/ijrte.B4053.079220
Open Access | Ethics and Policies | Cite | Mendeley
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC BY-NC-ND license (

Abstract: In a typical Software Development Life Cycle (SDLC), the software testing life cycle consists of reviewing of the requirements, test planning for design, development and execution. Test designing phase is considered as the most vital and foundational in deriving the test cases against the software or the application to be validate. The known fact is that in order to derive an effective test suite generally consumes a lot of manual efforts and good amount of expertise as well. [1] When the testers validate an application for its correct and required behavior, then that system is known as System Under Test (aka SUT), the most common term used in software testing process. Since, this is purely based on a manual approach and testers may not be able to validate all the possible and required scenarios, there may be risk of putting the system for validation. Because, the application may break under a particular use case. This can be overcome by applying Model Based Testing (MBT).
Keywords: MBT, Model Based Testing, Testing, Model Based Design.