Incremental software architecture : a method for saving failing IT implementations

Incremental software architecture a method for saving failing IT implementations

"This book will depict rare insights into actual failed-to-perform software systems, followed by comprehensive root-cause analyses identifying the reasons for their unsuccessful execution in production. Remedies will be provided that offer strategies to tackle the chief issues. Last, architectu...

Descripción completa

Detalles Bibliográficos
Otros Autores: Bell, Michael, 1951- author (author)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Hoboken, New Jersey : Wiley 2016.
Edición:1st ed
Colección:THEi Wiley ebooks.
Materias:
Software failures.
Evolutionary programming (Computer science)
Continuous improvement process.
Software architecture.
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009849106006719
Tabla de Contenidos:
  • Cover
  • Title Page
  • Copyright
  • Contents
  • Acknowledgments
  • About the Author
  • Chapter 1 The Need for Incremental Software Architecture
  • End-State Enterprise Architecture: A Risky Proposition
  • Focus on Incremental Software Architecture
  • Can Modeling and Simulation Substitute for Incremental Software Architecture?
  • Platform for Change
  • Incremental Software Architecture Process
  • Finally, What Is a System?
  • Notes
  • Part One Why Do Enterprise Systems Fail?
  • Chapter 2 What Is a Failing Enterprise System? Is It Management's Fault?
  • Can We Learn from Other Failures?
  • Characterization of System Failures
  • Notes
  • Chapter 3 Technological System-Level Failures
  • Notes
  • Part Two End-State Architecture Discovery and Analysis
  • Architecture Discovery and Analysis Scenarios
  • Attend to Architecture Discovery and Analysis Prerequisites
  • Chapter 4 System Fabric Discovery and Analysis
  • Discover and Analyze System Fabric Patterns
  • Notes
  • Chapter 5 Application Discovery
  • Application Discovery Instances
  • Continuous Application Discovery
  • What Can Be Revealed with Application Discovery Tools?
  • Application Identity Discovery
  • Application Architecture Discovery
  • Discovery of Application Performance and Resource Utilization
  • Network Infrastructure Discovery: Is an Application Production Ready?
  • Asset Management Discovery
  • Notes
  • Chapter 6 Application Mapping
  • Application Logical and Physical Topology Mapping
  • Mapping Application Dependency
  • Application and Supporting Environment Cataloging
  • Notes
  • Part Three End-State Architecture Decomposition
  • Note
  • Chapter 7 End-State Architecture Structural Decomposition through Classification
  • Identifying Architecture Perspectives
  • Keystone Architecture Structure Classification and Decomposition Diagram
  • Discovering and Classifying Sub-Architectures.
  • Note
  • Chapter 8 Business Analysis Drives End-State Architecture Structural Decomposition
  • Pursuing Business Analysis to Discover Sub-Architectures
  • Group Business Services to Discover Candidate Sub-Architectures
  • Employ Business Analysis to Discover Sub-Architectures
  • Pursue Business Analysis to Classify Sub-Architectures
  • Grand-Scale Architecture Structure Classification and Decomposition: A Unified Business Perspective
  • Capturing End-State Architecture Generations
  • Chapter 9 Technical Analysis Drives End-State Architecture Structural Decomposition
  • A Quick Guide to Discovering Sub-Architectures
  • Enterprise End-State Architecture Technical Case Study
  • Carry Out Technical Profiling to Discover Architecture Capabilities
  • Grouping Architecture Capabilities to Discover Sub-Architectures
  • Grand-Scale Architecture Structure Classification and Decomposition: A Unified Technical Perspective
  • Notes
  • Chapter 10 Business Views Drive End-State Architecture Decomposition
  • End-State Architecture Decomposition Driven by Business Formations
  • Decomposing End-State Architecture into Volatile Business Segments
  • Note
  • Chapter 11 Environment Behavior Drives End-State Architecture Decomposition
  • End-State Architecture Environment Behavior Decomposition
  • End-State Architecture Environment Behavior Levels
  • Component-Level Behavior Decomposition
  • Application-Level Behavior Decomposition
  • System-Level Behavior Decomposition
  • Environment Behavior Drives End-State Architecture Decomposition
  • Finally, End-State Architecture Decomposition: A Segmentation Process
  • Part Four End-State Architecture Verification
  • Chapter 12 Design Substantiation
  • A Shift from Software Development to Design Substantiation
  • Pursuing Architecture Substantiation by Cross-Functional Contracts
  • RACI Chart
  • Notes.
  • Chapter 13 Introduction to End-State Architecture Stress Testing
  • Scales of Environment Pressures
  • Architecture Structural Pressures
  • Behavioral Pressures
  • Induced Pressures by Volatile Architecture Areas
  • Chapter 14 End-State Architecture Stress Testing Driven by Pressure Points
  • The Justification for Inserting Pressure Points
  • Inserting Pressure Points in an End-State Architecture
  • Methods of End-State Architecture Stress Testing
  • Chapter 15 Enterprise Capacity Planning for End-State Architecture
  • End-State Architecture Artifact Studies
  • Data Collection
  • Data Analysis
  • Enterprise Capacity Planning Modeling
  • An Enterprise Capacity Plan for an End-State Architecture
  • Notes
  • Index
  • EULA.

Ejemplares similares