07.01.2013 Views

Lecture Notes in Computer Science 3472

Lecture Notes in Computer Science 3472

Lecture Notes in Computer Science 3472

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

440 Wolfgang Prenn<strong>in</strong>ger, Mohammad El-Ramly, and Marc Horstmann<br />

<strong>in</strong> the test model, otherwise the derived test cases may be significantly flawed.<br />

Together with an equally formal test specification, where the selection criteria<br />

of how to choose test cases is covered, the automatic generation of test cases<br />

can be performed. After that, a concretization of test cases has to be done. This<br />

is because the derived test cases are on the same abstraction level as the test<br />

model but have to be executed on concrete System Under Test (SUT) level. At<br />

last, the test evaluation is done either on SUT level or on abstract test case level.<br />

System Development/Concretisation<br />

Abstraction<br />

level 1<br />

Abstraction<br />

level 2<br />

Abstraction<br />

level ...<br />

System Requirements/Specification<br />

Development Models<br />

Special Test Models<br />

Test Model<br />

System under Test<br />

Test<br />

Specification<br />

Test Case<br />

Generation and<br />

Concretisation<br />

Test Case Execution<br />

Fig. 15.1. The Abstract Process of Model-Based Test<strong>in</strong>g<br />

Test Evaluation<br />

Test Result<br />

SUT response<br />

abstraction<br />

Fig. 15.1 shows the different activities and results of model based test<strong>in</strong>g <strong>in</strong><br />

the context of the SUT development process. The arrow at the left side symbolizes<br />

the progress <strong>in</strong> development and concretization of the SUT, where different<br />

abstraction layers can exist between the system requirements specification and<br />

the SUT. The test model can either be based on the requirement specification<br />

by build<strong>in</strong>g a special test model or it can be derived out of a certa<strong>in</strong> abstraction<br />

level <strong>in</strong> case that a suitable model exists. A second <strong>in</strong>terface between system development<br />

and model based test<strong>in</strong>g is the test purpose that should be def<strong>in</strong>ed <strong>in</strong><br />

the requirement specification and has to be formalized <strong>in</strong>to a test specification.<br />

After generation and concretization of test cases the third <strong>in</strong>terface is given by<br />

apply<strong>in</strong>g the test cases to the SUT and execut<strong>in</strong>g them. In the follow<strong>in</strong>g paragraphs<br />

the activities and results of model based test<strong>in</strong>g will be described <strong>in</strong> an<br />

abstract manner before the other sections will expla<strong>in</strong> them <strong>in</strong> more detail.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!