Betz Architecture and Patterns for IT Service Management, Resource Planning, and Governance

Making Shoes for the Cobbler's Children
2. Auflage 2011
ISBN: 978-0-12-385018-8
Verlag: Elsevier Science & Techn.
Format: EPUB
Kopierschutz: Adobe DRM (»Systemvoraussetzungen)

E-Book, Englisch, 480 Seiten

Information technology supports efficient operations, enterprise integration, and seamless value delivery, yet itself is too often inefficient, un-integrated, and of unclear value. This completely rewritten version of the bestselling Architecture and Patterns for IT Service Management, Resource Planning and Governance retains the original (and still unique) approach: apply the discipline of enterprise architecture to the business of large scale IT management itself. Author Charles Betz applies his deep practitioner experience to a critical reading of ITIL 2011, COBIT version 4, the CMMI suite, the IT portfolio management literature, and the Agile/Lean IT convergence, and derives a value stream analysis, IT semantic model, and enabling systems architecture (covering current topics such as CMDB/CMS, Service Catalog, and IT Portfolio Management). Using the concept of design patterns, the book then presents dozens of visual models documenting challenging problems in integrating IT management, showing how process, data, and IT management systems must work together to enable IT and its business partners. The edition retains the fundamental discipline of traceable process, data, and system analysis that has made the first edition a favored desk reference for IT process analysts around the world. This best seller is a must read for anyone charged with enterprise architecture, IT planning, or IT governance and management. - Lean-oriented process analysis of IT management, carefully distinguished from an IT functional model - Field-tested conceptual information model with definitions and usage scenarios, mapped to both the process and system architectures - Integrated architecture for IT management systems - Synthesizes Enterprise Architecture, IT Service Management, and IT Portfolio Management in a practical way

Charles Betz is the Research Director for IT Portfolio Management for Enterprise Management Associates, with extensive practitioner experience as an enterprise architect for large scale IT operations in retail and financial services.

Autoren/Hrsg.

Betz, Charles T.

Leseproben

List of Figures

Figure 1.1 Systems thinking (from Weinberg)  7

Figure 1.2 The two axes of product value  12

Figure 1.3 The two axes of IT value  12

Figure 1.4 The dynamic tension of IT service  14

Figure 1.5 “TPS House” for Lean IT  26

Figure 2.1 Architectural primitives (the catalogs)  34

Figure 2.2 Computer  35

Figure 2.3 Inside the computer  35

Figure 2.4 Servers  35

Figure 2.5 End-to-end computing  36

Figure 2.6 Transactional value across the stack  37

Figure 2.7 Service lifecycle and transactional value  37

Figure 2.8 Service Lifecycle and Delivery  38

Figure 2.9 IT Service Derived  38

Figure 2.10 IT Service (UML representation)  38

Figure 2.11 Basic architectural elements supporting a business  39

Figure 2.12 Architecture by lines of business  39

Figure 2.13 Enterprise support capabilities  39

Figure 2.14 The IT service organization produces IT services!  40

Figure 2.15 A factory that makes factories?  40

Figure 2.16 The IT value stream produces IT services for itself  41

Figure 2.17 Chevrons  44

Figure 2.18 Relative scale of value chains, streams, processes  45

Figure 2.19 IT as a business: system context  48

Figure 2.20 “Inspire to retire” IT value chain  48

Figure 2.21 Decomposed IT value chain  54

Figure 2.22 The lifecycles are not synchronized  54

Figure 2.23 Application and infrastructure services  55

Figure 2.24 Lean work/wait  58

Figure 2.25 “Four-O” model  59

Figure 2.26 Four-O model to scale  60

Figure 2.27 Base technology  61

Figure 2.28 Servers are instances of the technology product  61

Figure 2.29 Choose application server and license it  61

Figure 2.30 Completed hosting service  62

Figure 2.31 Hosting service and development tooling  62

Figure 2.32 Complete application service  63

Figure 2.33 Asset liability  64

Figure 2.34 Things and activities  64

Figure 2.35 Lifecycles and processes  65

Figure 2.36 An incident over the value streams  67

Figure 2.37 Function  76

Figure 2.38 IGOE model  76

Figure 2.39 Process crossing functions  77

Figure 2.40 Functional framework  88

Figure 2.41 Simple data model  97

Figure 2.42 Data modeling key  100

Figure 2.43 Lifecycle and process entities  101

Figure 2.44 IT enablement conceptual model  102

Figure 2.45 Many to many  104

Figure 2.46 Resolved many to many  104

Figure 2.47 Role model  107

Figure 2.48 Escalation  109

Figure 2.49 Partitioning data across systems  109

Figure 2.50 IT Process, CI, and Event  112

Figure 2.51 Basic data model  113

Figure 2.52 Skwish™ toy—network example  113

Figure 2.53 Indefinite-depth tree  114

Figure 2.54 Tree data model  115

Figure 2.55 Fixed-depth (level) tree  115

Figure 2.56 Network (no longer a tree)  116

Figure 2.57 Network data model  116

Figure 2.58 MRP and dual axis  123

Figure 2.59 ERP for IT and dual axis  124

Figure 2.60 Example system interaction diagram  126

Figure 2.61 System domains  129

Figure 2.62 IT management systems architecture  131

Figure 2.63 Simple application architecture  132

Figure 2.64 Enterprise application architecture  133

Figure 2.65 Dependencies are basis for matrix  138

Figure 2.66 Graphical representation of process/data create/use  143

Figure 3.1 Core Demand Management  155

Figure 3.2 Demand management as governing process  158

Figure 3.3 Demand as precursor  159

Figure 3.4 Various demand routings  160

Figure 3.5 Restore-Resolve-Release  160

Figure 3.6 Restore-Resolve-Demand-Release  160

Figure 3.7 Demand-Restore-Resolve-Release  161

Figure 3.8 Demand Management system integration  164

Figure 3.9 Project management system integrations  169

Figure 3.10 Release management integration  172

Figure 3.11 ITIL® representation of Change/Project/Release  175

Figure 3.12 Alternate representation of Project/Release/Change  176

Figure 3.13 Change Justification  178

Figure 3.14 CI-based risk management  180

Figure 3.15 Configuration and metadata risk management  181

Figure 3.16 Metadata-based Risk management detail  182

Figure 3.17 Change impact (simple)  183

Figure 3.18 Change impact (complex)  183

Figure 3.19 Drift, Incident, and Change  185

Figure 3.20 Change Management System Context  186

Figure 3.21 Service Semantics  188

Figure 3.22 Service chain  189

Figure 3.23 Integrated Service Request Management  192

Figure 3.24 Core transactional systems in context  195

Figure 3.25 Service management system domain  196

Figure 3.26 Core configuration management  199

Figure 3.27 Appropriate data capture level  207

Figure 3.28 Business case for inventory (CMS) consolidation  209

Figure 3.29 Inefficient dependency entry  210

Figure 3.30 Efficient dependency entry  211

Figure 3.31 Configuration iteration 1  213

Figure 3.32 Configuration iteration 2  213

Figure 3.33 Configuration iteration 3  214

Figure 3.34 Configuration iteration 4  214

Figure 3.35 Knowledge management  217

Figure 3.36 Security and configuration management  224

Figure 3.37 Configuration Audit role  226

Figure 3.38 Configuration Audit process  227

Figure 3.39 Configuration Audit and discovery  228

Figure 3.40 IT financial management system context  229

Figure 3.41 Integrated Incident Management  232

Figure 3.42 Capacity Management system context  234

Figure 3.43 Risk Management system context  236

Figure 3.44 Continuous improvement integration  238

Figure 3.45 Service retirement integration  240

Figure 4.1 Value stream key  243

Figure 4.2 The Application Service Lifecycle  245

Figure 4.3 Application Alias and ID  252

Figure 4.4 Reconciliation model  254

Figure 4.5 Application service semantic context  257

Figure 4.6 Project, release, and application  262

Figure 4.7 Project/application direct relationship  262

Figure 4.8 Effort tracking based on portfolio entries  263

Figure 4.9 Metadata Management System Context  267

Figure 4.10 Enterprise architecture portfolio representation  268

Figure 4.11 Simple application association  271

Figure 4.12 Interface system  271

Figure 4.13 System interactions carrying Application and/or...