Incremental Software Architecture: A Method for Saving Failing IT Implementations

The best–practices solution guide for rescuing broken software systems Incremental Software Architecture is a solutions manual for companies with underperforming software systems. With complete guidance and plenty of hands–on instruction, this practical guide shows you how to identify and analyze the root cause of software malfunction, then identify and implement the most powerful remedies to save the system. You?ll learn how to avoid developing software systems that are destined to fail, and the methods and practices that help you avoid business losses caused by poorly designed software. Designed to answer the most common questions that arise when software systems negatively impact business performance, this guide details architecture and design best practices for enterprise architecture efforts, and helps you foster the reuse and consolidation of software assets. Relying on the wrong software system puts your company at risk of failing. It?s a question of when, not if, something goes catastrophically wrong. This guide shows you how to proactively root out and repair the most likely cause of potential issues, and how to rescue a system that has already begun to go bad. Mitigate risks of software development projects Increase ROI and accelerate time–to–market Accurately assess technological achievability and viability Identify actual software construction value propositions Fierce competition and volatile commerce markets drive companies to invest heavily in the construction of software systems, which strains IT and business budgets and puts immense strain on existing network infrastructure. As technology evolves, these ever–more–complex computing landscapes become more and more expensive and difficult to maintain. Incremental Software Architecture shows you how to revamp the architecture to effectively reduce strain, cost, and the chance of failure. INDICE: Acknowledgments .About the Author .Chapter 1: The Need for Incremental Software Architecture .Part 1: Why do Enterprise Systems Fail? .Chapter 2: What is a Failing Enterprise System? Is it Management s Fault? .Chapter 3: Technological System–Level Failures .Part 2: End–State Architecture Discovery and Analysis .Chapter 4: System Fabric Discovery and Analysis .Chapter 5: Application Discovery .Chapter 6: Application Mapping .Part 3: End–State Architecture Decomposition .Chapter 7: End–State Architecture Structural Decomposition through Classification .Chapter 8: Business Analysis Drive End–State Architecture Structural Decomposition .Chapter 9: Technical Analysis Drive End–State Architecture Structural Decomposition .Chapter 10: Business Views Drive End–State Architecture Decomposition .Chapter 11: Environment Behavior Drive End–State Architecture Decomposition .Part 4: End–State Architecture Verification .Chapter 12: Design Substantiation .Chapter 13: End–State Architecture Stress Testing Environment .Chapter 14: End–State Architecture Stress Testing Driven by Pressure Points .Chapter 15: Enterprise Capacity Planning for End–State Architecture .Index

• ISBN: 978-1-119-11764-3
• Editorial: John Wiley & Sons
• Encuadernacion: Cartoné
• Páginas: 288
• Fecha Publicación: 17/02/2016
• Nº Volúmenes: 1
• Idioma: Inglés