WORKSHOP TOPICS AND GOALS
The increasing use of software and the growing system complexity, in size, heterogeneity, autonomy, and physical distribution make focussed software system testing a challenging task. Recent years have seen an increasing industrial and academic interest in the use of models for designing and testing software. Success has been reported using a range of types of models using a variety of specification formats, notations and formal languages, such as UML, SDL, B and Z. A-MOST 08 will bring together researchers and practitioners interested in the topic of Model Based Testing (MBT).
The use of models for designing and testing software is currently one of the most salient industrial trends with significant impact on the development and testing processes. Model-based tools and methods from object-oriented software engineering, formal methods, and other mathematical and engineering disciplines have been successfully applied and continue to converge into comprehensive approaches to software and system engineering.
The execution of software using test-cases or sequences derived in a manual or automatic manner from models, often referred to as MBT, is an encouraging scientific and industrial trend to cope with growing software system complexity. Modelling requires a substantial investment, and practical and scalable MBT solutions can help leverage this investment. The testing models may have been adapted from system design models or might have been devised specifically to support MBT. Naturally, the greatest benefits are often obtained when test generation is automated, but many practitioners report that the modelling process itself is of value, often highlighting requirements issues.
The use of industrial scale software demands the model-based construction of software and systems as compositions of independent and reusable actors. In this engineering paradigm, complex system functionality arises out of the composition of many component services. For these systems, model based testing may significantly improve component acceptance and move component integration testing towards a canonical validation and certification of complete systems.
Automation of software development and software testing on the basis of executable models and simulation promises significant reductions in fault-removal cost and development time. As a consequence of automating MBT, changes in requirements analysis, development and testing processes are needed that demand combined efforts from research and industry towards a broadly accepted solution.
A-MOST will focus on three main areas: the models used in MBT; the processes, techniques, and tools that support MBT; and evaluation. Here evaluation includes the evaluation of software using MBT and the evaluation of MBT. These areas can be further broken down into the following topics.