This book constitutes the refereed proceedings of the 12th European Conference on Software Architecture, ECSA 2018, held in Madrid, Spain, in September 2018. The 17 full papers presented together with 7 short papers were carefully reviewed and selected from 96 submissions. They are organized in topical sections as follows: Self-Adaptive Architectures, IoT Architectures, Embedded and Cyber-Physical Systems, Microservices Architectures, Service-Oriented Architectures, Architectural Design Decisions, Software Architecture in Practice.

A major challenge for modern software systems is to become more cost-effective, while being versatile, flexible, resilient, energy-efficient, customizable, and configurable when reacting to run-time changes that may occur within the system itself, its environment or requirements. One of the most promising approaches to achieving such properties is to equip the software system with self-adaptation capabilities. Despite recent advances in this area, one key aspect that remains to be tackled in depth is the provision of assurances. Originating from a Dagstuhl seminar held in December 2013, this book constitutes the third volume in the series "Software Engineering for Self-Adaptive Systems", and looks specifically into the provision of assurances. Opening with an overview chapter on Research Challenges, the book presents 13 further chapters written and carefully reviewed by internationally leading researchers in the field. The book is divided into topical sections on research challenges, evaluation, integration and coordination, and reference architectures and platforms.

This book presents the thoroughly refereed and revised post-workshop proceedings of the 17th Monterey Workshop, held in Oxford, UK, in March 2012. The workshop explored the challenges associated with the Development, Operation and Management of Large-Scale complex IT Systems. The 21 revised full papers presented were significantly extended and improved by the insights gained from the productive and lively discussions at the workshop, and the feedback from the post-workshop peer reviews.

This book constitutes the refereed proceedings of the Second International Conference on Coordination Models and Languages, COORDINATION '97, held in Berlin, Germany, in September 1997.
The 22 revised full papers and 6 posters presented in the book were carefully reviewed and selected from a total of 69 submissions. Also included are three invited papers. The papers are devoted to an emerging class of languages and models, which have been variously termed coordination languages, configuration languages, and architectural description languages. These formalisms provide a clean separation between software components and their interaction in the overall software organization, which is particularly important for large-scale applications and open systems.

""This new edition is brighter, shinier, more complete, more pragmatic, more focused than the previous one, and I wouldn't have thought it possible to improve on the original. As the field of software architecture has grown over these past decades, there is much more to be said, much more that we know, and much more that we can reflect upon of what's worked and what hasn't--and the authors here do all that, and more.""--From the Foreword by Grady Booch, IBM Fellow Software architecture--the conceptual glue that holds every phase of a project together for its many stakeholders--is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system's architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed. "Documenting Software Architectures, Second Edition, " provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition: Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data modelsGuidance for documentation in an Agile development environmentDeeper treatment of documentation of rationale, reflecting best industrial practicesImproved templates, reflecting years of use and feedback, and more documentation layout optionsA new, comprehensive example (available online), featuring documentation of a Web-based service-oriented systemReference guides for three important architecture documentation languages: UML, AADL, and SySML

This book teaches risk-driven architecting and describes a way to do just enough architecture. It avoids the one-size-fits all process tarp pit with advice on how to tune your design effort based on the risks you face. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes. This book focuses on the technical parts of software development and what developers do to ensure the system works-not the job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you learn specialized techniques in more detail. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.