جستجوی مقالات مرتبط با کلیدواژه « uml state machine » در نشریات گروه « برق »

This paper proposes a new method for automatic generation of test cases using model based testing. As test model, class and state diagrams are used, and constraints are expressed using OCL. First, the state machine is converted into a mathematical representation in AMPL. Then, using a search algorithm and based upon coverage criteria, the abstract paths are selected from state machine. Second, using symbolic execution, the generated abstract path along with the constraints on this path is converted into the data of generated mathematical model. Third, the generated mathematical problem is solved with solvers that have interface with AMPL, and the test data is produced for each abstract test case. Finally, the generated test data and abstract paths are transformed into executable test cases. All-Transitions and All-States coverage criteria are used for conduct search algorithm, as well as the criteria for evaluate the quality of generated test cases. To validate the work, by utilizing various solvers, the test cases are generated for various problems.
The proposed technique is implemented as a tool, named MoBaTeG. The tool shows good result in terms of test case generation execution time, test goals satisfaction rate, source code instructions coverage, and also boundary values generation.

An adaptive process consists of dynamic elements, and management rules which govern their run-time behaviors. The WS-CDL describes collaborative business processes between service consumers and providers. Adapting the processes to runtime changes becomes a demanding challenge, because the WS-CDL has static technology-dependent structure, and does not support the separation of concerns. Here, we propose a model-driven approach to transform WS-CDL into UML state machine (behavioral and protocol models), and subsequently into implementation code. Besides separating the business logic from the implementation, the state machine has a dynamic structure which is verifiable and adaptable. As a result, we can easily modify the process flow or change the management rules at run-time, and reflect their effects on the running process instances. We present an ‘itinerary purchase’ case study for prototyping the transformation rules.