توضیحاتی در مورد کتاب Incremental Software Architecture: A Method for Saving Failing It Implementations
نام کتاب : Incremental Software Architecture: A Method for Saving Failing It Implementations
عنوان ترجمه شده به فارسی : معماری نرم افزار افزایشی: روشی برای صرفه جویی در اجرای شکست آن
سری :
نویسندگان : Bell, Michael
ناشر : Wiley
سال نشر : 2016
تعداد صفحات : 275
ISBN (شابک) : 9781119117643 , 111911764X
زبان کتاب : English
فرمت کتاب : pdf
حجم کتاب : 7 مگابایت
بعد از تکمیل فرایند پرداخت لینک دانلود کتاب ارائه خواهد شد. درصورت ثبت نام و ورود به حساب کاربری خود قادر خواهید بود لیست کتاب های خریداری شده را مشاهده فرمایید.
فهرست مطالب :
Cover......Page 1
Title Page......Page 5
Copyright......Page 6
Contents......Page 9
Acknowledgments......Page 11
About the Author......Page 13
Chapter 1 The Need for Incremental Software Architecture......Page 15
End-State Enterprise Architecture: A Risky Proposition......Page 16
Focus on Incremental Software Architecture......Page 17
Can Modeling and Simulation Substitute for Incremental Software Architecture?......Page 20
Platform for Change......Page 21
Finally, What Is a System?......Page 23
Notes......Page 24
Part One Why Do Enterprise Systems Fail?......Page 25
Chapter 2 What Is a Failing Enterprise System? Is It Management\'s Fault?......Page 27
Can We Learn from Other Failures?......Page 28
Characterization of System Failures......Page 30
Notes......Page 35
Chapter 3 Technological System-Level Failures......Page 37
Notes......Page 48
Part Two End-State Architecture Discovery and Analysis......Page 49
Attend to Architecture Discovery and Analysis Prerequisites......Page 50
Discover and Analyze System Fabric Patterns......Page 53
Notes......Page 67
Application Discovery Instances......Page 69
What Can Be Revealed with Application Discovery Tools?......Page 70
Application Identity Discovery......Page 71
Application Architecture Discovery......Page 72
Discovery of Application Performance and Resource Utilization......Page 75
Network Infrastructure Discovery: Is an Application Production Ready?......Page 77
Asset Management Discovery......Page 78
Notes......Page 80
Application Logical and Physical Topology Mapping......Page 81
Mapping Application Dependency......Page 84
Application and Supporting Environment Cataloging......Page 91
Notes......Page 95
Part Three End-State Architecture Decomposition......Page 97
Note......Page 98
Chapter 7 End-State Architecture Structural Decomposition through Classification......Page 99
Identifying Architecture Perspectives......Page 100
Keystone Architecture Structure Classification and Decomposition Diagram......Page 105
Discovering and Classifying Sub-Architectures......Page 115
Note......Page 116
Pursuing Business Analysis to Discover Sub-Architectures......Page 117
Group Business Services to Discover Candidate Sub-Architectures......Page 118
Employ Business Analysis to Discover Sub-Architectures......Page 119
Pursue Business Analysis to Classify Sub-Architectures......Page 122
Grand-Scale Architecture Structure Classification and Decomposition: A Unified Business Perspective......Page 128
Capturing End-State Architecture Generations......Page 131
Chapter 9 Technical Analysis Drives End-State Architecture Structural Decomposition......Page 133
Enterprise End-State Architecture Technical Case Study......Page 134
Carry Out Technical Profiling to Discover Architecture Capabilities......Page 136
Grouping Architecture Capabilities to Discover Sub-Architectures......Page 142
Grand-Scale Architecture Structure Classification and Decomposition: A Unified Technical Perspective......Page 152
Notes......Page 158
Chapter 10 Business Views Drive End-State Architecture Decomposition......Page 159
End-State Architecture Decomposition Driven by Business Formations......Page 160
Decomposing End-State Architecture into Volatile Business Segments......Page 170
Note......Page 174
Chapter 11 Environment Behavior Drives End-State Architecture Decomposition......Page 175
End-State Architecture Environment Behavior Levels......Page 176
Component-Level Behavior Decomposition......Page 179
Application-Level Behavior Decomposition......Page 181
System-Level Behavior Decomposition......Page 184
Environment Behavior Drives End-State Architecture Decomposition......Page 186
Finally, End-State Architecture Decomposition: A Segmentation Process......Page 190
Part Four End-State Architecture Verification......Page 193
A Shift from Software Development to Design Substantiation......Page 195
Pursuing Architecture Substantiation by Cross-Functional Contracts......Page 199
RACI Chart......Page 209
Notes......Page 210
Chapter 13 Introduction to End-State Architecture Stress Testing......Page 211
Scales of Environment Pressures......Page 212
Architecture Structural Pressures......Page 215
Behavioral Pressures......Page 228
Induced Pressures by Volatile Architecture Areas......Page 232
The Justification for Inserting Pressure Points......Page 237
Inserting Pressure Points in an End-State Architecture......Page 238
Methods of End-State Architecture Stress Testing......Page 241
Chapter 15 Enterprise Capacity Planning for End-State Architecture......Page 249
End-State Architecture Artifact Studies......Page 250
Data Collection......Page 252
Data Analysis......Page 254
Enterprise Capacity Planning Modeling......Page 256
An Enterprise Capacity Plan for an End-State Architecture......Page 262
Notes......Page 266
Index......Page 267
EULA......Page 275