By analyzing ten examples of buildings that embody the human experience at an extraordinary level, this book clarifies the central importance of the role of function in architecture as a generative force in determining built form. Using familiar twentieth-century buildings as case studies, the authors present these from a new perspective, based on their functional design concepts. Here Grabow and Spreckelmeyer expand the definition of human use to that of an art form by re-evaluating these buildings from an aesthetic and ecological view of function. Each building is described from the point of view of a major functional concept or idea of human use which then spreads out and influences the spatial organization, built form and structure. In doing so each building is presented as an exemplar that reaches beyond the pragmatic concerns of a narrow program and demonstrates how functional concepts can inspire great design, evoke archetypal human experience and help us to understand how architecture embodies the deeper purposes and meanings of everyday life.

This unique book discusses programming, design and building evaluation providing a ‘joined up’ approach to building design. By linking the functional and architectonic qualities of a building, the authors show the practical implications of the utility value of buildings. Starting by looking at how the relationship between form and function has been dealt with by different approaches to architecture from a historical perspective, it goes on to discuss how the desired functional quality and utility value of a building can be expressed in a brief and given a physical form by the architect. Finally, it advises on how to carry out post-occupancy evaluation and provides the architect with methods and techniques for testing whether the intended utility value of a building has been achieved.

The Architecture of Persistence argues that continued human use is the ultimate measure of sustainability in architecture, and that expanding the discourse about adaptability to include continuity as well as change offers the architectural manifestation of resilience. Why do some buildings last for generations as beloved and useful places, while others do not? How can designers today create buildings that remain useful into the future? While architects and theorists have offered a wide range of ideas about building for change, this book focuses on persistent architecture: the material, spatial, and cultural processes that give rise to long-lived buildings. Organized in three parts, this book examines material longevity in the face of constant physical and cultural change, connects the dimensions of human use and contemporary program, and discusses how time informs the design process. Featuring dozens of interviews with people who design and use buildings, and a close analysis of over a hundred historic and contemporary projects, the principles of persistent architecture introduced here address urgent challenges for contemporary practice while pointing towards a more sustainable built environment in the future. The Architecture of Persistence: Designing for Future Use offers practitioners, students, and scholars a set of principles and illustrative precedents exploring architecture’s unique ability to connect an instructive past, a useful present, and an unknown future.

From participatory architecture to interaction design, the question of how design accommodates use is driving inquiry in many creative fields. Expanding utility to embrace people’s everyday experience brings new promises for the social role of design. But this is nothing new. As the essays assembled in this collection show, interest in the elusive realm of the user was an essential part of architecture and design throughout the twentieth century. Use Matters is the first to assemble this alternative history, from the bathroom to the city, from ergonomics to cybernetics, and from Algeria to East Germany. It argues that the user is not a universal but a historically constructed category of twentieth-century modernity that continues to inform architectural practice and thinking in often unacknowledged ways.

This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. 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, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not 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 can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. 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.

Conditional design is the sequel to Operative Design. This book will further explore the operative in a more detailed, intentional, and perhaps functional manner. Spatially, the conditional is the result of the operative. It is not a blind result however. Both terms work together to satisfy a formal manipulation through a set of opportunities for elements such as connections and apertures.

The purpose of large-scale software architecture is to capture and describe practical representations to make development teams more effective. In this book the authors show how to utilise software architecture as a tool to guide the development instead of capturing the architectural details after all the design decisions have been made. * Offers a concise description of UML usage for large-scale architecture * Discusses software architecture and design principles * Technology and vendor independent