Incremental Software Architecture. A Method for Saving Failing IT Implementations

  • ID: 3387126
  • Book
  • 272 Pages
  • John Wiley and Sons Ltd
1 of 4


Incremental Software Architecture is the only guide you need to proactively root out and repair failing software systems, while mitigating the impact to a company′s system, budget, and future risk.

The wrong software system increases a company′s risk of failure so much, it′s a question of when, not if, something goes catastrophically wrong. This practitioner′s guide gives you all the strategies and methods used by industry leaders for designing custom–fit software systems, along with cautionary advice on how to avoid developing systems destined to fail. Engineer with confidence using the step–by–step approach that enables you to design and test your software system through every sector of the enterprise. You′ll turn to this cutting–edge resource again and again for its:

  • Proven best practices for developing software systems that reduce business risk
  • A revealing collection of case studies illustrating how and why software systems underperform
  • Refreshing perspective and tactics for gaining a competitive edge by operating with smaller, more adaptable management and technical groups

If it′s broken, fix it right with Incremental Software Architecture.

Note: Product cover images may vary from those shown
2 of 4



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


Note: Product cover images may vary from those shown
3 of 4


4 of 4
Michael Bell
Note: Product cover images may vary from those shown
5 of 4
Note: Product cover images may vary from those shown
Order Online - visit: