Cover Image

Incremental software architecture : a method for saving failing IT implementations /

Show other versions (1)
Bibliographic Details
Main Author: Bell, Michael, 1957 June 22- (Author)
Corporate Author: EBSCOhost
Format: eBook
Language:English
Published: Hoboken, New Jersey : John Wiley & Sons, Inc., 2016.
Subjects:
Software failures.
Evolutionary programming (Computer science)
Continuous improvement process.
Software architecture.
Electronic books.
Online Access:Connect to the full text of this electronic book
Table of Contents:
  • Machine generated contents note: ch. 1 The Need for Incremental Software Architecture
  • pt. ONE Why Do Enterprise Systems Fail?
  • ch. 2 What Is a Failing Enterprise System? Is It Management's Fault?
  • ch. 3 Technological System-Level Failures
  • pt. TWO End-State Architecture Discovery and Analysis
  • ch. 4 System Fabric Discovery and Analysis
  • ch. 5 Application Discovery
  • ch. 6 Application Mapping
  • pt. THREE End-State Architecture Decomposition
  • ch. 7 End-State Architecture Structural Decomposition through Classification
  • ch. 8 Business Analysis Drives End-State Architecture Structural Decomposition
  • ch. 9 Technical Analysis Drives End-State Architecture Structural Decomposition
  • ch. 10 Business Views Drive End-State Architecture Decomposition
  • ch. 11 Environment Behavior Drives End-State Architecture Decomposition
  • pt. FOUR End-State Architecture Verification
  • ch. 12 Design Substantiation
  • ch. 13 Introduction to End-State Architecture Stress Testing
  • ch. 14 End-State Architecture Stress Testing Driven by Pressure Points
  • ch. 15 Enterprise Capacity Planning for End-State Architecture.