Incremental software architecture

Incremental software architecture: a method for saving failing IT implementations

by Bell, Michael

Type Book
Rate 0.0 /5

"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, architecture and design best practices will conclude the discussion. The book will assist users to: Mitigate risks of software development projects Increase return on investments (ROI) Provide effective tools to as…

Read More ↓

Title Statements

  • Full title :Incremental software architecture : a method for saving failing IT implementations / Michael Bell.

Summary

"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, architecture and design best practices will conclude the discussion. The book will assist users to: Mitigate risks of software development projects 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 "--

Read More ↓

Edition Statements

  • Publication Date:2016.

Publication Statements

  • Publisher(s):John Wiley & Sons, Inc
  • Place of Publication:Hoboken, New Jersey
  • Language:eng
  • Publication Date:2016.

Notes

Includes index.

The Physical Object

  • Description:1 online resource

Edition Identifiers

  • ISBN:9781119213680, 1119213681, 9781119213697, 111921369X
  • oclc:ocn928136923
  • LC Classification:QA76.76.F34
  • Dewey Decimal:005

Table of Contents

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.

Read More ↓

Subjects

Writers

Rate & Review

0.0/5
(0 people Voted)

No reviews yet. Be the first to rate this work.

Files & Downloads

  • Incremental Software Architecture: A Method for S…

    PDF · 4.1 MB · updated
  • Incremental Software Architecture: A Method for S…

    PDF · 6.6 MB · updated