Architecture manifests as a space of concealment and unconcealment, lethe and alêtheia, enclosure and disclosure, where its making and agency are both hidden and revealed. With an urgency to amplify narratives that are overlooked, silenced and unacknowledged in and by architectural spaces, histories and theories, this book contends the need for a critical study of hiding in the context of architectural processes. It urges the understanding of inherent opportunities, power structures and covert strategies, whether socio-cultural, geo-political, environmental or economic, as they are related to their hidescapes – the constructed landscapes of our built environments participating in the architectures of hiding. Looking at and beyond the intentions and agency that architects possess, architectural spaces lend themselves as apparatuses for various forms of hiding and un(hiding). The examples explored in this book and the creative works presented in the interviews enclosed in the interludes of this publication cover a broad range of geographic and cultural contexts, discursively disclosing hidden aspects of architectural meaning. The book investigates the imaginative intrigue of concealing and revealing in design processes, along with moral responsibilities and ethical dilemmas inherent in crafting concealment through the making and reception of architecture.

What are the ingredients of robust, elegant, flexible, and maintainable software architecture? Beautiful Architecture answers this question through a collection of intriguing essays from more than a dozen of today's leading software designers and architects. In each essay, contributors present a notable software architecture, and analyze what makes it innovative and ideal for its purpose. Some of the engineers in this book reveal how they developed a specific project, including decisions they faced and tradeoffs they made. Others take a step back to investigate how certain architectural aspects have influenced computing as a whole. With this book, you'll discover: How Facebook's architecture is the basis for a data-centric application ecosystem The effect of Xen's well-designed architecture on the way operating systems evolve How community processes within the KDE project help software architectures evolve from rough sketches to beautiful systems How creeping featurism has helped GNU Emacs gain unanticipated functionality The magic behind the Jikes RVM self-optimizable, self-hosting runtime Design choices and building blocks that made Tandem the choice platform in high-availability environments for over two decades Differences and similarities between object-oriented and functional architectural views How architectures can affect the software's evolution and the developers' engagement Go behind the scenes to learn what it takes to design elegant software architecture, and how it can shape the way you approach your own projects, with Beautiful Architecture.

As a software architect you work in a wide-ranging and dynamic environment. You have to understand the needs of your customer, design architectures that satisfy both functional and non-functional requirements, and lead development teams in implementing the architecture. And it is an environment that is constantly changing: trends such as cloud computing, service orientation, and model-driven procedures open up new architectural possibilities. This book will help you to develop a holistic architectural awareness and knowledge base that extends beyond concrete methods, techniques, and technologies. It will also help you to acquire or expand the technical, methodological, and social competences that you need. The authors place the spotlight on you, the architect, and offer you long-term architectural orientation. They give you numerous guidelines, checklists, and best practices to support you in your practical work. "Software Architecture" offers IT students, software developers, and software architects a holistic and consistent orientation across relevant topics. The book also provides valuable information and suggestions for system architects and enterprise architects, since many of the topics presented are also relevant for their work. Furthermore, IT project leads and other IT managers can use the book to acquire an enhanced understanding of architecture. Further information is available at www.software-architecture-book.org.

THE NEW YORK TIMES BESTSELLER! "A gripping page-turner...a riveting reminder of sacrifices made by history's most unlikely heroes." —Kristina McMorris, New York Times bestselling author of Sold on a Monday and The Ways We Hide An extraordinary book about a gifted architect who reluctantly begins a secret life of resistance, devising ingenious hiding places for Jews in World War II Paris. In 1942 Paris, architect Lucien Bernard accepts a commission that will bring him a great deal of money – and maybe get him killed. All he has to do is design a secret hiding place for a Jewish man, a space so invisible that even the most determined German officer won't find it while World War II rages on. He sorely needs the money, and outwitting the Nazis who have occupied his beloved city is a challenge he can't resist. Soon Lucien is hiding more souls and saving lives. But when one of his hideouts fails horribly, and the problem of where to conceal a Jew becomes much more personal, and he can no longer ignore what's at stake. Book clubs will pore over the questions Charles Belfoure raises about justice, resistance, and just how far we'll go to make things right. Also by Charles Belfoure: The Fallen Architect House of Thieves

This is the digital version of the printed book (Copyright © 2000). Derek Hatley and Imtiaz Pirbhai-authors of Strategies for Real-Time System Specification -join with influential consultant Peter Hruschka to present a much anticipated update to their widely implemented Hatley/Pirbhai methods. Process for System Architecture and Requirements Engineering introduces a new approach that is particularly useful for multidisciplinary system development: It applies equally well to all technologies and thereby provides a common language for developers in widely differing disciplines. The Hatley-Pirbhai-Hruschka approach (H/H/P) has another important feature: the coexistence of the requirements and architecture methods and of the corresponding models they produce. These two models are kept separate, but the approach fully records their ongoing and changing interrelationships. This feature is missing from virtually all other system and software development methods and from CASE tools that only automate the requirements model. System managers, system architects, system engineers, and managers and engineers in all of the diverse engineering technologies will benefit from this comprehensive, pragmatic text. In addition to its models of requirements and architecture and of the development process itself, the book uses in-depth case studies of a hospital monitoring system and of a multidisciplinary groundwater analysis system to illustrate the principles. Compatibility Between the H/H/P Methods and the UML: The Hatley/Pirbhai architecture and requirements methods-described in Strategies for Real-Time System Specification -have been widely used for almost two decades in system and software development. Now known as the Hatley/Hruschka/Pirbhai (H/H/P) methods, they have always been compatible with object-oriented software techniques, such as the UML, by defining architectural elements as classes, objects, messages, inheritance relationships, and so on. In Process for System Architecture and Requirements Engineering, that compatibility is made more specific through the addition of message diagrams, inheritance diagrams, and new notations that go with them. In addition, state charts, while never excluded, are now specifically included as a representation of sequential machines. These additions make definition of the system/software boundary even more straightforward, while retaining the clear separation of requirements and design at the system levels that ...

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 models Guidance for documentation in an Agile development environment Deeper treatment of documentation of rationale, reflecting best industrial practices Improved templates, reflecting years of use and feedback, and more documentation layout options A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system Reference guides for three important architecture documentation languages: UML, AADL, and SySML

Our longing for simplicity, clarity, and retreat often leads us into nature. Hide and Seek showcases a range of charming and elegant hideouts that satisfy this yearning.