This book constitutes the refereed proceedings of the tracks and workshops which complemented the 14th European Conference on Software Architecture, ECSA 2020, held in L''Aquila, Italy*, in September 2020. 

The 30 full papers and 9 short papers presented in this volume were carefully reviewed and selected from 72 submissions. Papers presented were accepted into the following tracks and workshops: ECSA 2020 Doctoral Symposium track; ECSA 2020 Tool Demos track; ECSA 2020 Gender Diversity in Software Architecture &Software Engineering track; CASA - 3rd International Workshop on Context-aware, Autonomous and Smart Architecture; CSE/QUDOS -  Joint Workshop on Continuous Software Engineering and Quality-Aware DevOps; DETECT - 3rd International Workshop on Modeling, Verication and Testing of Dependable Critical Systems; FAACS-MDE4SA - Joint Workshop on Formal Approaches for Advanced Computing Systems and Model-Driven Engineering for Software Architecture; IoT-ASAP - 4th International Workshop on Engineering IoT Systems: Architectures, Services, Applications, and Platforms; SASI4 - 2nd Workshop on Systems, Architectures, and Solutions for Industry 4.0; WASA - 6th International Workshop on Automotive System/Software Architecture.

*The conference was held virtually due to the COVID-19 pandemic.

This handbook exploits the profound experience and expertise of well-established scholars in the empirical software engineering community to provide guidance and support in teaching various research methods and fundamental concepts. A particular focus is thus on combining research methods and their epistemological settings and terminology with didactics and pedagogy for the subject. The book covers the most essential contemporary research methods and philosophical and cross-cutting concerns in software engineering research, considering both academic and industrial settings, at the same time providing insights into the effective teaching of concepts and strategies.

To this end, the book is organized into four major parts. In the first part, the editors set the foundation with two chapters; one laying out the larger context of the discipline for a positioning of the remainder of this book, and one guiding the creation of a syllabus for courses in empirical software engineering. The second part of the book lays the fundamentals for teaching empirical software engineering, addressing more cross-cutting aspects from theorizing and teaching research designs to measurement and quantitative data analysis. In the third part, general experiences and personal reflections from teaching empirical software engineering in different settings are shared. Finally, the fourth part contains a number of carefully selected research methods, presented through an educational lens. Next to the chapter contributions themselves that provide a more theoretical perspective and practical advice, readers will find additional material in the form of, for example, slide sets and tools, in an online material section.

The book mainly targets three different audiences: (1) educators teaching empirical software engineering to undergraduate, postgraduate or doctoral students, (2) professional trainers teaching the basic concepts of empirical software engineering to software professionals, and (3) students and trainees attending such courses.

Why have a book about the relation between requirements and software architecture? Understanding the relation between requirements and architecture is important because the requirements, be they explicit or implicit, represent the function, whereas the architecture determines the form. While changes to a set of requirements may impact on the realization of the architecture, choices made for an architectural solution may impact on requirements, e.g., in terms of revising functional or non-functional requirements that cannot actually be met.

Although research in both requirements engineering and software architecture is quite active, it is in their combination that understanding is most needed and actively sought. Presenting the current state of the art is the purpose of this book. The editors have divided the contributions into four parts: Part 1 “Theoretical Underpinnings and Reviews” addresses the issue of requirements change management in architectural design through traceability and reasoning. Part 2 “Tools and Techniques” presents approaches, tools, and techniques for bridging the gap between software requirements and architecture. Part 3 “Industrial Case Studies” then reports industrial experiences, while part 4 on “Emerging Issues” details advanced topics such as synthesizing architecture from requirements or the role of middleware in architecting for non-functional requirements. The final chapter is a conclusions chapter identifying key contributions and outstanding areas for future research and improvement of practice.

This book constitutes the refereed proceedings of the tracks and workshops which complemented the 14th European Conference on Software Architecture, ECSA 2020, held in L''Aquila, Italy*, in September 2020. 

The 30 full papers and 9 short papers presented in this volume were carefully reviewed and selected from 72 submissions. Papers presented were accepted into the following tracks and workshops: ECSA 2020 Doctoral Symposium track; ECSA 2020 Tool Demos track; ECSA 2020 Gender Diversity in Software Architecture &Software Engineering track; CASA - 3rd International Workshop on Context-aware, Autonomous and Smart Architecture; CSE/QUDOS -  Joint Workshop on Continuous Software Engineering and Quality-Aware DevOps; DETECT - 3rd International Workshop on Modeling, Verication and Testing of Dependable Critical Systems; FAACS-MDE4SA - Joint Workshop on Formal Approaches for Advanced Computing Systems and Model-Driven Engineering for Software Architecture; IoT-ASAP - 4th International Workshop on Engineering IoT Systems: Architectures, Services, Applications, and Platforms; SASI4 - 2nd Workshop on Systems, Architectures, and Solutions for Industry 4.0; WASA - 6th International Workshop on Automotive System/Software Architecture.

*The conference was held virtually due to the COVID-19 pandemic.

This handbook exploits the profound experience and expertise of well-established scholars in the empirical software engineering community to provide guidance and support in teaching various research methods and fundamental concepts. A particular focus is thus on combining research methods and their epistemological settings and terminology with didactics and pedagogy for the subject. The book covers the most essential contemporary research methods and philosophical and cross-cutting concerns in software engineering research, considering both academic and industrial settings, at the same time providing insights into the effective teaching of concepts and strategies.

To this end, the book is organized into four major parts. In the first part, the editors set the foundation with two chapters; one laying out the larger context of the discipline for a positioning of the remainder of this book, and one guiding the creation of a syllabus for courses in empirical software engineering. The second part of the book lays the fundamentals for teaching empirical software engineering, addressing more cross-cutting aspects from theorizing and teaching research designs to measurement and quantitative data analysis. In the third part, general experiences and personal reflections from teaching empirical software engineering in different settings are shared. Finally, the fourth part contains a number of carefully selected research methods, presented through an educational lens. Next to the chapter contributions themselves that provide a more theoretical perspective and practical advice, readers will find additional material in the form of, for example, slide sets and tools, in an online material section.

The book mainly targets three different audiences: (1) educators teaching empirical software engineering to undergraduate, postgraduate or doctoral students, (2) professional trainers teaching the basic concepts of empirical software engineering to software professionals, and (3) students and trainees attending such courses.

Why have a book about the relation between requirements and software architecture? Understanding the relation between requirements and architecture is important because the requirements, be they explicit or implicit, represent the function, whereas the architecture determines the form. While changes to a set of requirements may impact on the realization of the architecture, choices made for an architectural solution may impact on requirements, e.g., in terms of revising functional or non-functional requirements that cannot actually be met.

Although research in both requirements engineering and software architecture is quite active, it is in their combination that understanding is most needed and actively sought. Presenting the current state of the art is the purpose of this book. The editors have divided the contributions into four parts: Part 1 “Theoretical Underpinnings and Reviews” addresses the issue of requirements change management in architectural design through traceability and reasoning. Part 2 “Tools and Techniques” presents approaches, tools, and techniques for bridging the gap between software requirements and architecture. Part 3 “Industrial Case Studies” then reports industrial experiences, while part 4 on “Emerging Issues” details advanced topics such as synthesizing architecture from requirements or the role of middleware in architecting for non-functional requirements. The final chapter is a conclusions chapter identifying key contributions and outstanding areas for future research and improvement of practice.