Model based testing is a derivative of Unified Modeling Language (UML) concepts. Usually state machine diagram, interaction diagram etc are used to represent the behavior of system. ATM, Elevator, Vending machines are popular examples for deriving these diagrams. I think these examples are easy to represent in UML diagrams because they contain states and transition. What about other examples which doesn't have explicit state or transition? Like triangle program, sorting problem or search program etc. How can I represent them with state machine?
Hello
dear Muhammad
when we model behavior of a program, mechanism, algorithm or approach, we should design all of stats of a mechanism.
sometimes, the state diagram of a mechanism or algorithm can have 3 or 4 part. because designing behavior of the complicate mechanisms is hard. for avoiding mistake and easy to modeling, you should divide behavior to 2 or 3 or 4 section.
for example you can see a case study in our paper that we use to ArgoUML for modeling behavior of a case study by state diagram and Kripke Structure in below link:
http://www.sciencedirect.com/science/article/pii/S0957417413009627
best regard
The state model is used for special cases that have nature of moving from one state to other each state needs a certain time and input to change to another state , for other kind problem with more data and inputs like sorting and searching are more appropriate to be done by sequence diagram , if intelligent factors added to decide AUML ( see ARL Theory) my be used.
Use state machine to represent flow of chontrol of your algorithm, such as the sorting algorithm. In other other words, flow charts are state machines:-)
A state machine (from UML or others such as SysML or SDL that is more 'formal') is no more than a set of states and transitions. In your case, a state can be seen as a vector of the valuated parameters of your program. Transitions like actions that make this vector changes. Then, you have your FSM!
This is the way we used in our papers: Ana R. Cavalli, Stéphane Maag, Gerardo Morales: Regression and Performance Testing of an e-Learning Web Application: dotLRN. SITIS 2007: 369-376, and Gerardo Morales, Stéphane Maag, Ana R. Cavalli, Wissam Mallouli, Edgardo Montes de Oca, Bachar Wehbi: Timed Extended Invariants for the Passive Testing of Web Services. ICWS 2010: 592-599
Well, the Triangle program, or a sorting program, behave more like mathematical functions. These things do not have a concept of state; so a state machine is not a sensical way to model their behavior. Indeed, they may have internal state (e.g. the value of some local variables at some point in their statement), but their progress from one internal state to another is not something you can control from its interface; to point out that a state machine is not an appropriate way to drive their testing.
Model-based testing (MBT) is a testing paradigm. State model is just one of the many models. Depending on the system under consideration different modeling notation or approach needs to be chosen. Its not one size fits all, depending on system appropriate and applicable modeling notation and approach needs to be chosen.
May be helpful:
Model-Based Design Verification for Embedded Systems through SVOCL: An OCL Extension for SystemVerilog”, Design Automation for Embedded Systems, Vol. 21, No. 1, February 2017.
- Badges
- Science topic
- Similar topics
- Geoscience
- Cartography
- Mapping