Architect of Quality


Book Description

The world's leading authority on quality in business/manufacturing.




The Software Architect Elevator


Book Description

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company’s structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company’s technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what’s worked and what hasn’t in large-scale transformation




Design It!


Book Description

Don't engineer by coincidence-design it like you mean it! Filled with practical techniques, Design It! is the perfect introduction to software architecture for programmers who are ready to grow their design skills. Lead your team as a software architect, ask the right stakeholders the right questions, explore design options, and help your team implement a system that promotes the right -ilities. Share your design decisions, facilitate collaborative design workshops that are fast, effective, and fun-and develop more awesome software! With dozens of design methods, examples, and practical know-how, Design It! shows you how to become a software architect. Walk through the core concepts every architect must know, discover how to apply them, and learn a variety of skills that will make you a better programmer, leader, and designer. Uncover the big ideas behind software architecture and gain confidence working on projects big and small. Plan, design, implement, and evaluate software architectures and collaborate with your team, stakeholders, and other architects. Identify the right stakeholders and understand their needs, dig for architecturally significant requirements, write amazing quality attribute scenarios, and make confident decisions. Choose technologies based on their architectural impact, facilitate architecture-centric design workshops, and evaluate architectures using lightweight, effective methods. Write lean architecture descriptions people love to read. Run an architecture design studio, implement the architecture you've designed, and grow your team's architectural knowledge. Good design requires good communication. Talk about your software architecture with stakeholders using whiteboards, documents, and code, and apply architecture-focused design methods in your day-to-day practice. Hands-on exercises, real-world scenarios, and practical team-based decision-making tools will get everyone on board and give you the experience you need to become a confident software architect.




How to Architect


Book Description

The basics of the profession and practice of architecture, presented in illustrated A-Z form. The word "architect" is a noun, but Doug Patt uses it as a verb—coining a term and making a point about using parts of speech and parts of buildings in new ways. Changing the function of a word, or a room, can produce surprise and meaning. In How to Architect, Patt—an architect and the creator of a series of wildly popular online videos about architecture—presents the basics of architecture in A-Z form, starting with "A is for Asymmetry" (as seen in Chartres Cathedral and Frank Gehry), detouring through "N is for Narrative," and ending with "Z is for Zeal" (a quality that successful architects tend to have, even in fiction—see The Fountainhead's architect-hero Howard Roark.) How to Architect is a book to guide you on the road to architecture. If you are just starting on that journey or thinking about becoming an architect, it is a place to begin. If you are already an architect and want to remind yourself of what drew you to the profession, it is a book of affirmation. And if you are just curious about what goes into the design and construction of buildings, this book tells you how architects think. Patt introduces each entry with a hand-drawn letter, and accompanies the text with illustrations that illuminate the concept discussed: a fallen Humpty Dumpty illustrates the perils of fragile egos; photographs of an X-Acto knife and other hand tools remind us of architecture's nondigital origins. How to Architect offers encouragement to aspiring architects but also mounts a defense of architecture as a profession—by calling out a defiant verb: architect!




Design for Good


Book Description

The book reveals a new understanding of the ways that design shapes our lives and gives professionals and interested citizens the tools to seek out and demand designs that dignify.




Software Architecture in Practice


Book Description

This is the eagerly-anticipated revision to one of the seminal books in the field of software architecture which clearly defines and explains the topic.







Deciding about Design Quality


Book Description

In the past few years the image of tender procedures in which Dutch public clients selected an architect has been dominated by distressing newspaper headlines. Architects fear that the current tender culture will harm the quality of our built environment due to a potential lack of diversity, creativity and innovation in architectural design. Due to potential risks clients often allow legal requirements to overrule their actual wishes. This PhD research addresses the origin of the problems as currently experienced by public commissioning clients in architect selection and proposes pragmatic implications for future practice. It is therefore of interest for commissioning clients, management consultants, policy makers and legal advisors but also for designers and researchers in the field of architecture and decision making.




Kirtland Cutter


Book Description

In the early years of the twentieth century, Spokane was singled out for praise in the West for the quality of its architecture and the impressive way it had rebuilt after the devastating fire of 1889. Major credit for the city's distinctive character was extended to Kirtland Kelsey Cutter for his "rare architectural force and genius for design." His remarkable career, stretching from the Gilded Age to the Great Depression, allows a fascinating study of the evolution of an eclectic form of architecture that was an inevitable response to rich regional and historical influences during a time of transition from frontier settlements to modern city. Cutter's influence was felt beyond Spokane--in Seattle, other areas of Washington, and in Oregon, Idaho, and Montana. He was also responsible for buildings in the East and even for one in England. After financial problems ended his career in the Northwest, he began anew at age sixty-three in southern California, and worked there as an architect until his death in 1939 at age seventy-nine. Henry Matthews presents a comprehensive study of the whole body of Cutter's work, with ample photographs and illustrations. The book is based on exhaustive research in both the Northwest and California, revealing the influences on Cutter and his associates, the processes at work in the design and construction of the buildings, and the relations between the architect and the many people who commissioned his work. Particularly useful to Matthews's research was a collection of 290 sets of drawings, as well as office accounts, letters, and books from Cutter's library--materials acquired by the Eastern Washington State Historical Society. He also was able to interview former assistants and clients, who provided valuable insights on the architect and the way Cutter worked. In addition, many of the architect's residences, hotels, clubs, and commercial buildings are still standing. This book adds significantly to an understanding of Western urban and regional history. But Cutter's experimentation in many styles and the imaginative nature of his work make for a study that goes beyond regional limits and sheds light on national trends. Winner of the 1999 Washington State Book Award




Just Enough Software Architecture


Book Description

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.