The emphasis on new and changing technologies and process models in today s software development obscures the fact that software engineering is still primarily a human-based activity and that the success of a software project largely depends on the decisions made by humans during engineering. Rationale management is concerned with making these design and development decisions explicit to all stakeholders involved.

Dutoit, McCall, Mistrik and Paech begin their book with a historical survey of different rationale approaches. It is followed by four parts describing: the fundamental problems and possible solution approaches in rationale management, rationale management during requirements engineering, rationale management during software architecting, and rationale management for organizing reusable bodies of knowledge.

The result is a detailed summary of research on design rationale. It provides researchers with an excellent state-of-the-art overview, and professional software engineers will find many examples, resources and incentives to enhance their ability to make decisions during all phases of the software lifecycle.

Allen Dutoit, Ray McCall, Ivan Mistrik and Barbara Paech have done an excellent job of this in "Rationale management in software engineering." The chapters in this volume show how design rationale can be incorporated into the heart of the software development process - into requirements engineering, software architecture, and code design. (John M. Carroll, Edward M. Frymoyer Professor of Information Sciences and Technology, Penn State University, USA, ACM CHI Lifetime Achievement Award)

Wearepleasedtopresenttheproceedingsofthe14thMontereyWorkshop, which tookplaceSeptember10-13,2007inMonterey, CA, USA. Inthispreface, wegive the reader an overview of what took place at the workshop and introduce the contributions in this Lecture Notes in Computer Science volume. A complete introduction to the theme of the workshop, as well as to the history of the Monterey Workshop series, can be found in Luqi and Kordon's "Advances in Requirements Engineering: Bridging the Gap between Stakeholders' Needs and Formal Designs" in this volume. This paper also contains the case study that many participants used as a problem to frame their analyses, and a summary of the workshop's results. The workshop consisted of three keynote talks, three panels, presentations of peer-reviewed papers, as well as presentations of various position papers by the participants. The keynote speakers at this year's workshop were Daniel Berry, Aravind Joshi, and Lori Clarke. Each of their talks was used to set the tone for the p- sentations and discussions for that particular day. Daniel Berry presented an overview of the needs and challenges of natural language processing in requi- ments engineering, with a special focus on ambiguity in his talk "Ambiguity in Natural Language Requirements. " Aravind Joshi provided an overview of current natural language processing research in discourse analysis in the talk "Some Recent Developments in Natural Language Processing. " Finally, Lori Clarke showed how to combine formal requirements speci?cation with natural language processing to cope with the complex domain of medical information processes in "Getting the Details Right.

The 14th Working Conference on Requirements Engineering: Foundation for SoftwareQuality(REFSQ 2008)willbe held inthe beautiful city ofMontpellier, France, June 16-17, 2008. The main topic was ?tness of requirements engineering. Our economic p- ductivityandwell-beinginevery-daylifestronglyhingesoninformationtechn- ogy, and thus software quality. In most systems, quality is determined through the development process. With the spread of service-oriented and autonomic systems, software quality is continuously negotiated and adapted at run-time. Requirements Engineering sets the stage for quality, both at development- and run-time. In spite of the constant emergence of new technologies and devel- mentparadigms, basicissuessuchase?ectivecommunicationbetweenstakeho- ersorcorrectness, consistencyandcompletenessoflargerequirementsdocuments are the dominant issues in industry. Seventeenpaperswrittenbyauthorsfrom13di?erentcountriesaddressthese topics, with particular focus on elicitation, innovative systems and empirical studies, as well as industrial experiences and maturing research. Within these themes, the work presented spans a wide range of application domains such as public health, aeronauticsand the automotive industry. It also involvesa variety of requirements engineering techniques, from the most established (such as use cases or feature models) to the most innovative (such as search-based software engineering or negotiation constellations). As in the previous years, the proceedings serve as a record of REFSQ 2008, butalsopresentanexcellentsnapshotofthestateoftheartofresearchandpr- tice. As such, we believe it is of interest to the whole requirements engineering community, from students embarking on their PhD to experienced practiti- ers, researchers and teachers interested in emerging knowledge, techniques and method

This book constitutes the refereed proceedings of the 13th International Working Conference on Requirements Engineering: Foundation for Software Quality, REFSQ 2007, held in Trondheim, Norway in June 2007.

The 27 revised full papers presented together with 1 keynote lecture were carefully reviewed and selected from numerous submissions for inclusion in the book. The papers are organized in thematic sections on goal-driven requirements engineering (RE), products and product-lines, value-based RE and the value of RE, requirements elicitation, requirements specification, industrial experience of RE, and requirements quality and quality requirements. Within these themes, the work presented spanned a range of application domains from business systems to air traffic management, used techniques that varied from ethno-methodology to formal specification and delivered requirements for both custom systems and software product lines.

The emphasis on new and changing technologies and process models in today s software development obscures the fact that software engineering is still primarily a human-based activity and that the success of a software project largely depends on the decisions made by humans during engineering. Rationale management is concerned with making these design and development decisions explicit to all stakeholders involved.

Dutoit, McCall, Mistrik and Paech begin their book with a historical survey of different rationale approaches. It is followed by four parts describing: the fundamental problems and possible solution approaches in rationale management, rationale management during requirements engineering, rationale management during software architecting, and rationale management for organizing reusable bodies of knowledge.

The result is a detailed summary of research on design rationale. It provides researchers with an excellent state-of-the-art overview, and professional software engineers will find many examples, resources and incentives to enhance their ability to make decisions during all phases of the software lifecycle.

Allen Dutoit, Ray McCall, Ivan Mistrik and Barbara Paech have done an excellent job of this in "Rationale management in software engineering." The chapters in this volume show how design rationale can be incorporated into the heart of the software development process - into requirements engineering, software architecture, and code design. (John M. Carroll, Edward M. Frymoyer Professor of Information Sciences and Technology, Penn State University, USA, ACM CHI Lifetime Achievement Award)

Informations- und Kommunikationstechnologie pragen zunehmend unsere Wirtschaft und Gesellschaft. Ihre weite Verbreitung erfordert eine Softwareentwicklung, die nicht nur auf die Technologie, sondern auch auf die Besonderheiten der Anwendungsgebiete ausgerichtet ist. Das vorliegende Buch behandelt die Gestaltung von Softwaresystemen und ihren Umgebungszusammenhangen mit der Methode der Objekt- und Aufgabenorientierten Software-Entwicklung (OASE). Der Vorstellung der wesentlichen Konzepte folgt eine systematische Darstellung der vorhandenen Modellierungstechniken. Typische Methoden aus der Betriebswirtschaft, den Sozial- und Arbeitswissenschaften, der Softwareergonomie und des Software Engineering werden daraufhin untersucht, welchen Beitrag sie zur integrierten Modellierung und Gestaltung von Softwaresystemen leisten. OASE greift wesentliche Elemente dieser Methoden auf und vervollstandigt sie zu einer durchgangigen Modellierung eines Anwendungs-, Nutzungs- und Softwaresystems.

Der dritte Workshop "Software Engineering im Unterricht der Hochschulen (SEUH)" findet am 24. und 25. Februar 1994 in Munchen statt. Nach zwei SEUH- Workshops (1992 Stuttgart, 1993 Hamburg), in denen ein Erfahrungsaustausch auf breiter Basis im Vordergrund stand, behandelt dieser Workshop zusatzlich zu der Diskussion uber didaktische Konzepte das Schwerpunktthema "Anforderungen an SEUH aus Sicht der Industrie". Um dieses Thema kompetent diskutieren zu koennen, wurden Referenten aus verschiedenen Firmen eingeladen, die Erfahrungen mit der Integration von Hochschulabsolventen in die betriebliche Prws haben (W. Altrnann (K&A), U. Bittner (START), R. Haggenmuller (SNI), G. Mathy (Allianz), J. Wolle (Rohde & Schwarz)). Weitere wichtige Themen werden in zwei Arbeitsgruppen behandelt, denen auf diesem Workshop viel Zeit eingeraumt wird. Ziel der Arbeitsgruppen ist es, einen Entwurf eines Software-Engineering-Curriculums und Handlungsempfehlungen zum Einsatz von CASE-Werkzeugen in der Lehre zu erarbeiten. In beiden Fallen ist das Ergebnis der Diskussion als Grundlage fur eine kontinuierliche Zusammenarbeit uber den Workshop hinaus gedacht. Dieser Tagungsband enthalt zu beiden Arbeitsgruppen jeweils eine "Agenda", die als Diskussionsgrundlage dienen soll sowie schriftliche Ausarbeitungen von Kurzvortragen in der jeweiligen Gruppe. Den organisatorischen Rahmen dieses Workshops bildeten wieder die GI- Fachgruppen 2.1.1 (Software Engineering) und 4.3.1 (Requirements Engineering) sowie das German Chapter of the ACM. Mitglieder des Programmkomitees waren: H. Hussmann (TU Munchen), E. Jaus (Ploenzke Informatik), B. Paech (TU Munchen), J. Raasch (FH Hamburg), G.