Incremental Software Architecture

Book description

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

  1. Cover
  2. Title Page
  3. Copyright
  4. Dedication
  5. Acknowledgments
  6. About the Author
    1. Chapter 1: The Need for Incremental Software Architecture
      1. End-State Enterprise Architecture: A Risky Proposition
      2. Focus on Incremental Software Architecture
      3. Can Modeling and Simulation Substitute for Incremental Software Architecture?
      4. Platform for Change
      5. Incremental Software Architecture Process
      6. Finally, What Is a System?
      7. Notes
  7. Part One: Why Do Enterprise Systems Fail?
    1. Chapter 2: What Is a Failing Enterprise System? Is It Management's Fault?
      1. Can We Learn from Other Failures?
      2. Characterization of System Failures
      3. Notes
    2. Chapter 3: Technological System-Level Failures
      1. Notes
  8. Part Two: End-State Architecture Discovery and Analysis
    1. Chapter 4: System Fabric Discovery and Analysis
      1. Discover and Analyze System Fabric Patterns
      2. Notes
    2. Chapter 5: Application Discovery
      1. Application Discovery Instances
      2. Continuous Application Discovery
      3. What Can Be Revealed with Application Discovery Tools?
      4. Application Identity Discovery
      5. Application Architecture Discovery
      6. Discovery of Application Performance and Resource Utilization
      7. Network Infrastructure Discovery: Is an Application Production Ready?
      8. Asset Management Discovery
      9. Notes
    3. Chapter 6: Application Mapping
      1. Application Logical and Physical Topology Mapping
      2. Mapping Application Dependency
      3. Application and Supporting Environment Cataloging
      4. Notes
  9. Part Three: End-State Architecture Decomposition
    1. Chapter 7: End-State Architecture Structural Decomposition through Classification
      1. Identifying Architecture Perspectives
      2. Keystone Architecture Structure Classification and Decomposition Diagram
      3. Discovering and Classifying Sub-Architectures
      4. Note
    2. Chapter 8: Business Analysis Drives End-State Architecture Structural Decomposition
      1. Pursuing Business Analysis to Discover Sub-Architectures
      2. Group Business Services to Discover Candidate Sub-Architectures
      3. Employ Business Analysis to Discover Sub-Architectures
      4. Pursue Business Analysis to Classify Sub-Architectures
      5. Grand-Scale Architecture Structure Classification and Decomposition: A Unified Business Perspective
      6. Capturing End-State Architecture Generations
    3. Chapter 9: Technical Analysis Drives End-State Architecture Structural Decomposition
      1. A Quick Guide to Discovering Sub-Architectures
      2. Enterprise End-State Architecture Technical Case Study
      3. Carry Out Technical Profiling to Discover Architecture Capabilities
      4. Grouping Architecture Capabilities to Discover Sub-Architectures
      5. Grand-Scale Architecture Structure Classification and Decomposition: A Unified Technical Perspective
      6. Notes
    4. Chapter 10: Business Views Drive End-State Architecture Decomposition
      1. End-State Architecture Decomposition Driven by Business Formations
      2. Decomposing End-State Architecture into Volatile Business Segments
      3. Note
    5. Chapter 11: Environment Behavior Drives End-State Architecture Decomposition
      1. End-State Architecture Environment Behavior Decomposition
      2. End-State Architecture Environment Behavior Levels
      3. Component-Level Behavior Decomposition
      4. Application-Level Behavior Decomposition
      5. System-Level Behavior Decomposition
      6. Environment Behavior Drives End-State Architecture Decomposition
      7. Finally, End-State Architecture Decomposition: A Segmentation Process
  10. Part Four: End-State Architecture Verification
    1. Chapter 12: Design Substantiation
      1. A Shift from Software Development to Design Substantiation
      2. Pursuing Architecture Substantiation by Cross-Functional Contracts
      3. RACI Chart
      4. Notes
    2. Chapter 13: Introduction to End-State Architecture Stress Testing
      1. Scales of Environment Pressures
      2. Architecture Structural Pressures
      3. Behavioral Pressures
      4. Induced Pressures by Volatile Architecture Areas
    3. Chapter 14: End-State Architecture Stress Testing Driven by Pressure Points
      1. The Justification for Inserting Pressure Points
      2. Inserting Pressure Points in an End-State Architecture
      3. Methods of End-State Architecture Stress Testing
    4. Chapter 15: Enterprise Capacity Planning for End-State Architecture
      1. End-State Architecture Artifact Studies
      2. Data Collection
      3. Data Analysis
      4. Enterprise Capacity Planning Modeling
      5. An Enterprise Capacity Plan for an End-State Architecture
      6. Notes
    5. Index
  11. End User License Agreement

Product information

  • Title: Incremental Software Architecture
  • Author(s): Michael Bell
  • Release date: February 2016
  • Publisher(s): Wiley
  • ISBN: 9781119117643