This is another update about our project in architecture support for testing. I would like to tell you about a series of workshops we’re running, with the help of others, or participating in, and to invite you to join us.
Practitioners’ Workshop in Architecture-Based Testing, Pittsburgh, February 1-2
On February 1-2, 2011, 13 dedicated individuals braved the Pittsburgh winter to attend an invitation-only workshop on Architecture Support for Testing, run by the SEI’s project team of the same name. Our guests came to us from the U.S. Army, industry, and academia and were chosen because of their practical knowledge of software testing, architecture, or both. Their job was to speak to the needs of software system developers with respect to testing and how architecture can be used to improve testing practices.
The goal of the workshop was to help answer this question:
How can we (better) use architecture to help test our systems?
The output of the workshop was a set of important model problems in architecture-based testing. These are problems that, if solved, would result in a significant decrease in project resources devoted to testing and/or a significant increase in system quality given an expenditure level. Along the way, we also captured descriptions of current architecture-based testing practices, as reported by our participants.
(An output we didn’t expect was a new name for our project. Our participants arrived at a workshop about Architecture-Based Testing, but they departed a workshop about Architecture Support for Testing. They told us our previous name was confusing and implied we were just about testing of architectures. Taking their point, we changed the name.)
In my next post, I’ll show you the full list of model problems and give you the opportunity to vote on the ones you think are most important. And a full report about the workshop is forthcoming.
Meanwhile, I wanted to take this opportunity to tell you about two others that are in the works.
Researchers’ Workshop in Architecture Support for Testing, Pisa, March 29-30
Our Pittsburgh workshop was the result of a collaboration between the SEI and two of the leading researchers in the field of architecture and testing: Henry Muccini of the University of L’Aquila and Antonia Bertolino of the Software Engineering Research Lab at Istituto di Scienza e Tecnologie dell’Informazione A. Faedo. Both attended the Pittsburgh workshop and have agreed to organize and run a partner workshop in Pisa, Italy, in late March.
The Pittsburgh workshop was for practitioners. The Pisa workshop will be for researchers. The idea is to take the model problems produced at the Pittsburgh workshop and lay them before the leading researchers and techologists in this field. The goal is two-fold. First, if any of the model problems can be solved, partially or substantially or completely, by existing technologies, this is a clear win for both communities. Second, researchers are often hungry for real-world problems on which they can unleash their ideas and tools and technologies, and show relevance. The Pittsburgh workshop’s model problems can serve to nudge the research agenda towards areas of real need.
The Pisa workshop, like the Pittsburgh workshop, will be invitation only, but if you’re doing research into the relationship between architecture and testing and would like to be invited, drop Henry Muccini a note at email@example.com
Workshop on Architecture Based Testing and System Validation, WICSA, June 24, Boulder
This year’s Working International Conference on Software Architecture (WICSA) will feature a workshop on architecture and testing. Unlike Pittsburgh and unlike Pisa, this workshop is open to all, and we encourage your attendance.
Unlike most conference workshops, writing a traditional research paper is not the only way to get in. Instead of that, we also solicit the following types of submissions from both researchers and practitioners:
- 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 two pages and are intended 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 industry for the topic of architecture-based testing and system validation. Industrial statement paper should be 2-4 pages long and adopt the template as defined on the website of the workshop.
- Presentations – authors who do not have 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 understanding, provide new insights, or foster discussions regarding the workshop topics.
The organizers of this workshop are Bedir Tekinerdogan, Bilkent University, Turkey; Michel Chaudron, Leiden University, The Netherlands; Henry Muccini, University of L’Aquila, Italy; Andrea Polini, University of Camerino, Italy; Eoin Woods, Artechra, UK; and me. You can find complete details at http://www.cs.bilkent.edu.tr/ABT-2011/.
6th IEEE/ACM International Workshop on Automation of Software Test, at ICSE, Honolulu, May 23-24
This year’s AST workshop, held at the International Conference on Software Engineering, has as its theme “Relating software design to test automation,” which fits perfectly with our interest in using architecture to support testing. Our project has been asked to organize a Charette session for the workshop, which is a panel-like session designed to produce intense discussion about a focused topic. Come and join us! For complete information, visit http://ast2011.isti.cnr.it/index.html .
– Paul Clements, SEI