Incremental Software Architecture: A Method for Saving Failing It Implementations (Hardcover)

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