The IT4IT reference architecture

by Andrew Josey, Van Haren Publishing (Editor)

This Pocket Guide provides a concise introduction to the IT4IT™ Reference
Architecture, Version 2.0, an Open Group Standard. The IT4IT standard provides a
vendor-neutral, technology-agnostic, and industry-agnostic reference architecture for managing the business of IT, enabling insight for continuous improvement.

This Pocket Guide is based on the IT4IT Reference Architecture Version 2.0. What’s more, it’s authoritative with material derived from the official IT4IT documentation and contributions from members of the IT4IT Forum.

The audience for this Pocket Guide
• Individuals who require a basic understanding of the IT Value Chain and IT4IT
Reference Architecture
• IT Professionals who are responsible for delivering services in a way that is
flexible, traceable, and cost-effective
• IT Professionals / Practitioners who are focused on instrumenting the IT
management landscape
• IT leaders who are concerned about their operating model
• Enterprise Architects who are responsible for IT business transformation

Topics covered
• An introduction to the IT4IT Reference Architecture, the structure of the IT4IT standard, and the positioning of the IT4IT standard in the standards landscape
• The IT Value Chain and IT4IT Reference Architecture concepts, including Value
Streams
• The Strategy to Portfolio (S2P) Value Stream
• The Requirement to Deploy (R2D) Value Stream
• The Request to Fulfill (R2F) Value Stream
• The Detect to Correct (D2C) Value Stream
• A summary of the differences between the IT4IT Reference Architecture and
ITIL

152 pages, Kindle Edition

Published October 26, 2015

Reviews

[Tom · Rating 2 out of 5]

I really like the idea of having a more lightweight framework than TOGAF. Unfortunately even Version 2.0 is still scratching on the surface. There is a lot more work to do, the current level concept is missing the interesting part. Level 3-5 is still not really described, this doesn't give you a clear idea how to deal with the corresponding processes.
I like the holistic approach to depict the IT in end-2-end value streams and the mapping to the needed information objects. Still I am afraid that the tool vendors and developers will not stick to that model, resulting in a limbo to get the framework mapped.