Librería Portfolio

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.



Table of Contents

ACKNOWLEDGMENTS ix

ABOUT THE AUTHOR xi

CHAPTER 1 The Need for Incremental Software Architecture 1

PART ONE-Why Do Enterprise Systems Fail? 11

CHAPTER 2 What Is a Failing Enterprise System? Is It Management's Fault? 13

CHAPTER 3 Technological System-Level Failures 23

PART TWO-End-State Architecture Discovery and Analysis 35

CHAPTER 4 System Fabric Discovery and Analysis 39

CHAPTER 5 Application Discovery 55

CHAPTER 6 Application Mapping 67

PART THREE-End-State Architecture Decomposition 83

CHAPTER 7 End-State Architecture Structural Decomposition through Classification 85

CHAPTER 8 Business Analysis Drives End-State Architecture Structural Decomposition 103

CHAPTER 9 Technical Analysis Drives End-State Architecture Structural Decomposition 119

CHAPTER 10 Business Views Drive End-State Architecture Decomposition 145

CHAPTER 11 Environment Behavior Drives End-State Architecture Decomposition 161

PART FOUR-End-State Architecture Verification 179

CHAPTER 12 Design Substantiation 181

CHAPTER 13 Introduction to End-State Architecture Stress Testing 197

CHAPTER 14 End-State Architecture Stress Testing Driven by Pressure Points 223

CHAPTER 15 Enterprise Capacity Planning for End-State Architecture 235

INDEX 253