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
- Language:eng
- Publication Date:2016
Notes
Includes index
The Physical Object
- Description:xi, 260 sider : : ill
Edition Identifiers
- ISBN:9781119117643, 111911764X
- oclc:ocn945917055
- LC Classification:QA76.76.F34
- Dewey Decimal:005
Table of Contents
Acknowledgments -- About the autor -- Chapter 1: The need for incremental software architecture. PART ONE: Why do enterprise systems fail? -- Chapter 2: What is a faliling enterpris system? Is it management's fault? -- Chapter 3: Technological system-level faliures. PART TWO: End-state architecture discovery and analysis -- Chapter 4: System fabric discovery and analysis -- Chaper 5: Applicaton 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: Enviroment 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 arcitecture stress testing driven by pressure points -- Chapter 15: Enterprise capacity planning for end-state archi…
Read More ↓Subjects
Writers
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
Rate & Review