Incremental Software Architecture: A Method for Saving Failing IT Implementations

The best-practices solution guide for rescuing broken software systems

Devised to rescue failing IT implementations, Incremental Software Architecture presents an advanced approach for designing durable, flawless, and elastic software systems to enable business growth. This is a practical-solutions manual with complete guidance, abundance of hands-on instruction, and powerful remedies formulated to save software malfunction. Such software architecture failure typically hinders organizational response to commerce trends, growing consumer demands, changes to business strategies, and technological evolution.

You’ll learn how to avoid developing software systems that are destined to fail and rescue under-performing software implementations that have already deployed to production. These methods and practices will help you circumvent the business losses that cause companies to flounder.

• Mitigate risks of software development projects
• Accurately assess technological feasibility and viability
• Increase return on investments (ROI)
• Provide effective tools to assess technological achievability and viability
• Introduce software design best practices for enterprise architecture efforts
• Identify actual software construction value proposition
• Foster software assets reuse and consolidation
• Accelerate time-to-market

On the software architecture front, 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 pressure on existing network infrastructure. As technology evolves, these increasingly complex computing landscapes become more expensive and difficult to maintain. Incremental Software Architecture shows you how to revamp the architecture to effectively reduce production environment burden, cost, and the chance of failure.

Table of Contents

Chapter 1: The Need for Incremental Software Architecture
Part One: 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 Two: End-State Architecture Discovery and Analysis
Chapter 4: System Fabric Discovery and Analysis
Chapter 5: Application Discovery
Chapter 6: Application Mapping

Part Three: End-State Architecture Decomposition
Chapter 7: End-State Architecture Structural Decomposition through Classification
Chapter 8: Business Analysis Drives End-State Architecture Structural Decomposition
Chapter 9: Technical Analysis Drives End-State Architecture Structural Decomposition
Chapter 10: Business Views Drive End-State Architecture Decomposition
Chapter 11: Environment Behavior Drives End-State Architecture Decomposition

Part Four: End-State Architecture Verification
Chapter 12: Design Substantiation
Chapter 13: Introduction to End-State Architecture Stress Testing
Chapter 14: End-State Architecture Stress Testing Driven by Pressure Points
Chapter 15: Enterprise Capacity Planning for End-State Architecture