Böcker i SEI Series in Software Engineering-serien

Over time, technical debt affects virtually every significant software project. As software systems evolve, earlier design or code decisions prove to be ?not quite right,? gradually becoming impediments that slow down the evolution of the system, or even grind it to a halt. Most software practitioners have experienced this phenomenon, but many feel helpless to address it. In this guide, three leading software engineering experts introduce empirically validated principles and practices for managing and mitigating technical debt in any software system.Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. Next, they introduce a palette of proven approaches, strategies, methods, and tools for: Identifying sources of technical debt in any software system Assessing the magnitude of technical debt Limiting the introduction of technical debt in the first place Reducing the impact of technical debt over timeAs software systems mature, the challenge of technical debt has grown, and it has become increasingly urgent for software professionals and their managers to address it head-on. Managing Technical Debt shows them how.

"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-in other words, is not well documented-the project cannot be deemed a complete success. This revision of Documenting Software Architectures 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 use, maintain, and build 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 documentation for new architectural styles, such as service-oriented architectures, multi-tier architectures, and architectures for aspect-oriented systems Guidance oriented to documentation in an Agile development environment Deeper treatment of the systematic 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