This avoids one-size-fits-all process of the tar pit with suggestions about how to refine your design business based on the risks you face. It democratizes architecture. This book seeks to create architecture that are relevant to all software developers. Developers must understand how to use obstacles as guiderails which guarantees the desired results, and how apparently small changes can affect the nature of a system. It cultivates declarative knowledge. There is a difference between being able to hit the ball and find out why you can hit, what psychologists refer to as declarative knowledge versus procedural knowledge. This book will make you more aware of what you have done and provide names for concepts. Emphasizes engineering. This book focuses on the technical part of software development and what the developers do to ensure the system works no job title or processes. This illustrates the designers use software techniques to reason about the medium-to large-sized problems and show where you can learn specific techniques in more detail. This gives practical advice. The software architecture design decisions affect and vice versa.