Architecture-based testing and system validation involves the use of architecture to involve better outcomes to the process of assuring that a delivered system satisfies its requirements. "Better outcomes" can mean shorter validation time, higher confidence results, or less expensive testing (for example, by using architectural analysis to eliminate the need for certain tests). This workshop aims to bring together researchers and practitioners to produce an emerging picture of the state of the practice in architecture-based testing and system validation, promising research approaches, and practical problems that could be solved by directed research. Papers are solicited dealing with topics in the following list:
Using architecture to produce test artifacts aimed at testing code -- e.g., test plans, test cases, etc.
Using analysis of architecture to make certain tests unnecessary
Fault models associated with particular architecture styles or patterns
Architectural design approaches that make systems more testable
Testing implementations for conformance to architecture
Using architectural arguments to shorten the testing for a new version of a fielded system
Using architecture to for predictive analysis about a system
Architectural viewpoints for testing
Model-based testing of/with architecture
Output from the workshop will include a set of model problems in architecture-based testing, as well as a set of "{problem in practice, potential solution from research}" pairs. We encourage both academic researchers and industrial practitioners to submit papers to the conference to share and discuss their ideas and experiences.
We solicit the following types of submissions from both researchers and practitioners in the software architecture community:
Long research papers - should describe original and significant results of research and/or industrial practice in software architecture. Full papers are limited to 8 proceedings pages. Papers must not have been previously published nor submitted or under consideration elsewhere for publication. Accepted papers will be included in the 2nd volume of WICSA proceedings to be published by IEEE Computer Society. Papers should conform to the IEEE Conference Proceedings style.
Extended abstracts - should describe original ideas from research and/or industrial practice, but are not required to show complete/evaluated results. Extended abstract papers should not exceed 2 pages, and are tended to share and discuss ideas in their early stages. Papers must be formatted according to the IEEE Conference Proceedings style.
Industrial
statement paper - should describe problems and
needs of the industrial for the topic of
architecture-based testing and system validation.
Industrial statement paper should be 2-4 pages long,
and adopt this
template.
Presentations - authors who have not got the time to provide one of the above submission types can submit their presentations to be considered at the workshop. These presentations will serve to support the understanding, to provide new insights or to foster discussions regarding the workshop topics.
Each submission will undergo a review by three members of the program committee. At least one of the authors of each accepted paper is required to register for the workshop and to present the paper at the workshop