Call for Papers

 pdf flyer

Research, position, and experience papers are invited on any topic that addresses the intersection of requirements and architectural design. Examples might 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,

Submissions

We invite submissions in the following categories:

Position papers (2-4 pages)

Short papers state the emerging trends, inspiring new ideas, and ongoing research on any of the topics within the scope of the workshop. For example, position papers could challenge the state-of-the-art; represent initial experience with a particular technique on promoting requirements and architecture interdependencies. The paper might propose new ways of eliciting, managing and analysing 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.

Full papers (6-7 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 performed together. Case studies of requirement engineering within an architecture centric development on one or more mega-projects (e.g. a high speed rail line) or complex products (e.g. a new passenger airplane), or more focused systems and agile environments. Survey papers that review and critique the range of and/or use requirements engineering 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 (up to 7 pages)

Experience papers describe empirical experiences with a particular RE and/or, architecture design practice, pattern or technique on a large scale system or agile project. Ideally an experience paper not only reports on the actual experience must includes an 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 notions have been examined in a real context or laboratory scenario, or how iterative development of architecture has been applied in practice.

Pedagogical papers (up to 7 pages)

Techniques, lesson plans, and assignments for teaching RE/SA topics.

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 are:

  • 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 (LaTeX users, please use the "Option 2" style). All submissions must be in PDF format. Please visit the Formatting and Submission Guidelines page for paper requirements.

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 both ACM Digital Library and IEEE Digital Library.