open group RA IT4IT
-
Upload
alain-garsoux -
Category
Documents
-
view
133 -
download
1
Transcript of open group RA IT4IT
![Page 1: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/1.jpg)
RA IT4ITFeedback from Open Group conference
Alain GarsouxEnterprise Architect
27/04/2016
London April 2016
![Page 2: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/2.jpg)
Table of contents
2
• IT4IT positioning
• IT4IT content
• How to use this RA ?
![Page 3: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/3.jpg)
IT4IT positioning
Copyright Open Group 2014
![Page 4: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/4.jpg)
ITIL positioning in detail
ITIL IT4ITPositioning Framework describing functions/capabilities/disciplines. Information model driven reference architecture, supportive
of multiple process frameworks.
Origins “Best” or “good” practice origins intended for broad audience of executives, managers, and individual contributors.
Originated out of needs identified by enterprise architects and IT managers for clearer implementation and integration guidance
Methodology Primarily unstructured narrative. “Process” (similar to what enterprise architects would term function) is the primary unit of analysis.
Structured consistently with TOGAF and Archimate. Value stream, capability, data, system views.
Orientation Oriented to practitioner education rather than solution Solution orientation
Value approach Oriented to deep discussion of individual silo functions/processes. Beyond overall service lifecycle, does not emphasize longer lived value flows.
Focused on the end to end flow of four high level IT value streams (Strategy to Portfolio, Requirement to Deploy, Request to Fulfill, Detect to Correct) across IT capabilities.
Internal consistency Ambiguous and overlapping terminology in places Mutually exclusive and comprehensive, rigorously avoiding ambiguity and overlap in its architectural catalogs
Level of detail Not sufficiently detailed to be of utility to planners and architects attempting to integrate IT management infrastructure.
Precise representation of data and integration patterns in complex IT management domain
Agile Implicit waterfall, top-down planning orientation. Explicit coverage of Agile and DevOps trends.
Maintenance process Long term history of proprietary ownership. Multi-year revision cycle
Open development process
![Page 5: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/5.jpg)
RA IT4IT answers problem that every company has with IT.
5
![Page 6: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/6.jpg)
• The IT4IT Reference Architecture provides a “standard, repeatable model” for creating anIT management ecosystem, set in the context of a value-chain-based IT operating model.
• It is intended to help organizations adapt to changes in technology, process and methodswithout having to re-factor the management architecture to accomodate every shift.
• https://www.youtube.com/watch?v=1oz6P3OqJfc
What is the RA IT4IT?
6
![Page 7: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/7.jpg)
Table of contents
7
• IT4IT positioning
• IT4IT content
• How to use this RA ?
![Page 8: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/8.jpg)
5 architecture levels
8
Level 2 : Value-Stream Documentation
Level 1 : End-to-End Overview
Level 3 : Vendor-independent Architecture.
Level 4 : Vendor-specific RefinentArchitecture
Level 5 : Solution Architecture
Simplified class model andinformal notation tointroduce and explainconcepts.Idea: to be understood bynon-architects.
Audience: architects-> formal notation is the prefered means of communicating.
Documenting &Governing the concepts.
Controlled byproduct andservice providers or other forums-> RA providesexamplarguidance.
![Page 9: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/9.jpg)
Concepts at Level 1 : End-to-End Overview
9
Value Stream
Functional Components
Service Backbone Data Object
Lifecycle Data Object
Relationship
1
*
1 1…* 2
*
![Page 10: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/10.jpg)
Concepts at Level 1 : End-to-End Overview
10
Value Stream
Functional Components
Service Backbone Data Object
Lifecycle Data Object
Relationship
1
*
1 1…* 2
*
S2P: Strategy to PortfolioR2D : Requirements to DeployR2F : Request to FulfillD2C : Detect to Correct
The smallest unit of technologythat can stand on its own and beuseful as a whole to an IT pratitioner (or IT service provider)
Represents data that annotate or model an aspect of the service being offered by IT.
![Page 11: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/11.jpg)
IT4IT information model comprises a set of service data objectsand their relationships.
11
Key data objects describe aspects of “how” services are created.
Sub-class of key data objects describe“what” IT delivers to consumers.
Auxiliary data objects provide context forthe “why, when, where, etc.” They do notplay a vital role in managing the service lifecycle.
Legend
![Page 12: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/12.jpg)
Level 2 : Value Stream documentation. It expands level 1.
12
Functional Component
Value Stream
Lifecycle Data Object1
*
1..*
SoR
Integration
Capability Discipline
*
*
**
Relationship*
22
0..1
1
1
Service Backbone Data ObjectData Flow
2
*
SoEIntegration
![Page 13: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/13.jpg)
Level 3 : Vendor-Independent Architecture
13
Functional Component
Value Stream
Lifecycle Artefact1
*
1..*
SoR
Integration
Capability Discipline
*
*
**
Relationship*
22
0..1
1
1
Service Backbone Artefact
SoEIntegration
Scenario
1
*
*
1
*
Attribute1*
* *
* Multiplicity
1
2
EpicTheme
![Page 14: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/14.jpg)
• Vendor extensions.
• Owned and controled by suppliers of IT management products and service.
• RA IT4IT has no direct control over defining and/or approving content at these abstraction layers.
Level 4 & 5
14
![Page 15: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/15.jpg)
15
![Page 16: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/16.jpg)
16
![Page 17: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/17.jpg)
R2D : Requirement to Deploy
17
![Page 18: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/18.jpg)
18
![Page 19: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/19.jpg)
R2F: Request to Fulfill
19
![Page 20: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/20.jpg)
20
![Page 21: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/21.jpg)
D2C: Detect to Correct
21
![Page 22: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/22.jpg)
22
![Page 23: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/23.jpg)
Supporting Activities: details to come in a future release of RA IT4IT.
23
![Page 24: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/24.jpg)
Table of contents
24
• IT4IT positioning
• IT4IT content
• How to use this RA ?
![Page 25: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/25.jpg)
• Use it as any reference.
• Assign some architects to specific “functional components”. Request them to develop a vendor independent architecture and map it wiht current (vendor) specific solutions.• Organize a workshop to collect outcomes and defines potential future IT investments.
Ideas
25
![Page 26: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/26.jpg)
Thanks for your attention!
![Page 27: open group RA IT4IT](https://reader036.fdocuments.us/reader036/viewer/2022062412/58739e5e1a28ab85438b7127/html5/thumbnails/27.jpg)
External resources
27
What Where
Positioning of IT4IT from OpenGroup https://www.youtube.com/watch?v=x9MIzusZm4Y