[ecoop-info] CfP - Third International Workshop on the Twin Peaks of Requirements and Architecture @ RE 2013

[Matthias Galster]

-------------------------------------------
CALL FOR PAPERS

Third International Workshop on the Twin Peaks of Requirements and
Architecture (TwinPeaks at RE 2013), July 16th, 2013, Rio de Janeiro, Brazil

In conjunction with the 21st IEEE International Requirements Engineering
Conference (RE 2013)

http://re.cs.depaul.edu/twinpeaks/RE13/

-------------------------------------------

TwinPeaks at RE 2013 seeks for contributions on any topic that addresses the
intersection of requirements and architectural design. Examples include:
- Eliciting, specifying, or managing architecturally significant
requirements;
- Modeling of requirements and architecture using common paradigms and
metamodels;
- Capturing, representing and using architectural knowledge as it interacts
with requirements knowledge;
- Assessment techniques and metrics for measuring compliance of architecture
against requirements;
- Processes that support a "twin peaks" co-evolvement of requirements and
architecture;
- Traceability between requirements, architectural solutions and
implementation;
- Relating patterns and best practices to the Twin Peaks model;
- Transforming requirements into architectures in model-driven engineering
processes;
- Tool-support to the various informational and processing needs (e.g.,
visualization of interactions among - architectural and requirements
knowledge);
- Twin Peak practices in specific domains and/or environments, e.g.
safety-critical, complex, agile;
- Industrial studies and empirical studies on relating requirements
engineering and architectural design.

Important Dates
-------------------------------------------
- Paper submission: 29 April 2013
- Notification: 24 May 2013

Submissions
-------------------------------------------
We invite submissions in the following categories:

- Full papers (6-8 pages). Full papers describe and report on the evaluation
of requirements engineering and software architecture design and evaluation
activities. For example, a full paper could describe how in practice,
requirements engineering and software architecture design are performed in
parallel. Case studies of requirements engineering within an
architecture-centric development environment for ultra-large-scale projects
(e.g. a high speed rail line or a new passenger airplane), or in agile
environments, will also be solicited. Survey papers that provide reviews and
critiques are also invited (e.g. a survey of the use of practices in
requirement and architecture co-development). Full papers will be evaluated
based on the originality and significance of the contribution, soundness of
the validation process or quality of the survey procedure, and on the
broader applicability of the results.

- Experience Reports (4-6 pages). Experience papers describe empirical
experiences with a particular requirements engineering or architecture
design practice, pattern or technique on a large scale system or agile
project. Ideally an experience paper will not only report on actual
experience but will also include analysis of the techniques used in the
forms of lessons learned that might be applicable to future projects. An
experience paper might describe how the twin peaks notion has been examined
in a real context, or how iterative development of architecture has been
applied in practice. Experience papers will be evaluated based on the
quality of the experience, significance of the contribution and the broader
applicability and generalizability of the results.

- Position papers (2-4 pages). Position papers could discuss ongoing
research, e.g., highlight new challenges and propose potential directions
and novel solutions. Position papers could present initial experiences with
a particular technique on promoting requirements and architecture
interdependencies, or propose new ways of eliciting, managing and analyzing
requirements for software architecture based development.
Position papers will be evaluated based on their potential for generating
discussion, and on the novelty and originality of the positions expressed.

- Vision papers (2-4 pages). Vision statements state emerging trends or
inspiring new ideas on any of the topics within the scope of the workshop.
Furthermore, vision papers could challenge the state-of-the-art. Also,
similar as position papers, vision statements will be evaluated based on
their potential for generating discussions. In contrast to position papers,
the focus of vision statements is less on research or on presenting new
methodologies, but on presenting thought-provoking ideas or a long-term
vision on the relationship between RE and SA.

- Education and Training papers (4-6 pages). Education and Training papers
describe experiences, approaches, and tools for teaching requirements
engineering and software architecture courses. Such paper will address both
concepts and methods required to teach problem-solution courses.
Education and training papers will be evaluated based on the quality of the
experience, significance of the contribution and the broader applicability
and generalizability of the results.

Workshop format
-------------------------------------------
The format of Twin Peaks will provide attendees with an opportunity to
become familiar with a new topic and establish a good foundation for
discussions about requirements engineering in the overall context of systems
engineering. We intend to make the workshop discussion and interaction
oriented. Paper presentations will be used to provoke dialogue and
participants may break out into small groups for more detailed discussion.
These small groups will be organized around common themes or goals
identified either from the papers, or by the participants during the
workshop. At the end of the day, there will be a plenary session where the
group's report back to the workshop as a whole on the results of their
discussion and future work. Results may be used as a basis for continued
publications.

The target audience of TwinPeaks at RE 2013 includes:
- Requirements engineering and architecture researchers working in the
development of tools, techniques and methods for the fields;
- Practitioners with experience in the adoption of practices, tools,
techniques and methods.

Formatting and Submission Guidelines
-------------------------------------------
All papers must conform, at time of submission, to the IEEE Formatting
Guidelines.

Accepted Contributions
-------------------------------------------
- All authors of accepted papers will be asked to complete an electronic
IEEE Copyright form and will receive further instructions for preparing
their camera ready versions.
- All accepted contributions will be published in the conference electronic
proceedings and in the IEEE Digital Library.

Committees
-------------------------------------------
General Chair
Xavier Franch - Universitat Politècnica de Catalunya, Barcelona, Spain

Program Board
Jane Cleland-Huang - DePaul University, Chicago, US 
Janet E. Burge  - Miami University, Oxford, US 
Matthias Galster - University of Canterbury, Christchurch, New Zealand 
Mehdi Mirakhorli - DePaul University, Chicago, US 
Roshanak Roshandel - Seattle University, Seattle, US 
Carla Silva - Universidade Federal de Pernambuco, Brazil

Program Committee
Muhammad Ali Babar, ITU Copenhagen, Denmark
Len Bass, Software Engineering Institute, USA
Daniel M. Berry, University of Waterloo, Canada
Jan Bosch, Chalmers University of Technology, Sweden
Maya Daneva, University of Twente, Netherlands 
Alexander Egyed, Johannes Kepler University, Austria 
Remo Ferrari, Siemens, USA 
Carlo Ghezzi, Politecnico di Milano, Italy 
Robert Hanmer, Alcatel-Lucent, USA 
Anne Koziolek, Karlsruhe Institute of Technology, Germany 
Philippe Kruchten, University of British Columbia, Canada 
Axel van Lamsweerde, Universite Catholique de Louvain (UCL), Belgium 
Nazim Madhavji, University of Western Ontario, CA 
Patrick Maeder, Johannes Kepler University, Austria 
Sam Malek, George Mason University, USA 
Robert L. Nord, Software Engineering Institute, USA 
Ipek Ozkaya, Software Engineering Institute, USA 
Sam Supakkul, The University of Texas at Dallas, USA 
Richard N. Taylor, University of California, Irvine, USA 
Eoin Woods, Artechra, UK 
Eric Yu, University of Toronto, Canada 
Liming Zhu, NICTA, Australia 
Leyna Zimdars, University of California, Irvine, USA