2012 First IEEE International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks), pp. 27–30
September 2012 · DOI: 10.1109/TwinPeaks.2012.6344557
Model-based testing is a well known technique to generate automatically highly qualitative tests for a given system based on a simplified testing model. Test-driven development is an established development practice in the agile development projects, which implies firstly the partial specification of a system by using tests, and after this, the development of the system. In test driven development the system implementation is continuously checked against the tests in order to assess its correctness with respect to the specification. In this paper we investigate how can these two methods be combined such that the advantages of these two approaches can be leveraged: highly qualitative test-cases used as specification of requirements and support of a continuous checking of architecture. We propose to formalize sub-sets of requirements into models that are amenable to generate tests by using automatic techniques well-known from model based testing. These tests can then be used to check the system architecture specification against the requirements in a continuous manner.
Stichworte: automatic programming, formal specification, object-oriented programming, program testing, program verification, software architecture, software prototyping, AutoFOCUS3, MIRA, model-based requirements engineering, model-based systems engineering, MbSE