IT4IT 3 Foundation flashcards
IT4IT 3 Foundation · Build recall with a focused review session.
31 cards. Read the term and the definition here. The deck at the top of this page is optional.
- IT4IT
- A vendor-neutral reference architecture published by The Open Group for managing the business of IT, built from a service model, four value streams, functional components, and data objects.
- Four architecture levels
- Level 1 is the IT Value Chain, Level 2 the value streams, Level 3 the functional components, and Level 4 the data objects and their relationships.
- Value stream
- An end-to-end sequence of functional components that together deliver measurable value to a stakeholder, defined by its trigger, components, and outcome rather than by organizational boundaries.
- Service model
- The central IT4IT concept describing how services are offered, contracted, and consumed; the four value streams create, deliver, and maintain this model.
- Vendor neutrality
- IT4IT prescribes required data objects and interfaces, not specific products, so any conforming tool set can realize the architecture without redesign.
- IT4IT Version 3.0
- The current release of the standard, published in 2022, which refined the 2.1 version and added guidance on digital product management and sustainability.
- Functional component
- A Level 3 logical grouping of capabilities that produces and consumes defined data objects; it is technology-independent and may be realized by one or several tools.
- IT Value Chain
- The Level 1 view that frames IT as capabilities turning demand into services and outcomes, organized around the four value streams S2P, R2D, R2F, and D2C.
- Strategy to Portfolio
- The value stream covering demand, strategy, portfolio, and investment decisions; it determines what IT should fund and passes approved demand into Requirement to Deploy.
- Requirement to Deploy
- The value stream covering requirements, design, build, test, release, and deployment; it produces deployable services that are then offered through Request to Fulfill.
- Request to Fulfill
- The value stream covering catalog, order, fulfillment, and consumption; it delivers services to consumers and generates usage and incident data for Detect to Correct.
- Detect to Correct
- The value stream covering monitoring, event, incident, problem, and change; it restores service and feeds improvement data back to Strategy to Portfolio and Requirement to Deploy.
- Value stream trigger
- The initiating event that starts a value stream, such as a new business demand for S2P or a service outage for D2C; it defines when the stream runs.
- Concurrent value streams
- The four streams are not sequential lifecycle phases; they run in parallel and exchange data continuously, so D2C change records can inform R2D releases.
- S2P data objects
- Idea, Demand, Proposal, Portfolio Item, Initiative, and Investment; together they trace a concept from capture through funding to an approved initiative.
- R2D data objects
- Requirement, Service Design, Build, Test Case, Defect, Service Release, and Deployment; they describe what is built and how it is released into production.
- R2F data objects
- Service Catalog Entry, Service Offering, Service Contract, Order, Subscription, and Fulfillment Request; they describe what consumers can request and receive.
- D2C data objects
- Event, Incident, Problem, Known Error, Change, and Service Level; they describe what is detected, diagnosed, corrected, and measured in operations.
- Shared data objects
- Objects such as Service, Service Offering, Service Contract, and Configuration Item that appear in more than one value stream and must stay consistent across tools.
- Data object lifecycle
- Each Level 4 data object has defined states and transitions, and the architecture governs their integrity as objects move between functional components.
- Component interface
- The defined set of data objects a functional component consumes and produces; specifying interfaces by data object allows tool substitution without redefining the value stream.
- Data object relationships
- Level 4 also defines how objects link, for example a Defect relating to a Build, or an Incident relating to a Configuration Item, enabling traceability across components.
- Value-stream assessment
- A first adoption step that maps existing tools and data flows onto the four streams to expose gaps, overlaps, and broken data handoffs.
- Authoritative data source
- A single designated system of record for each shared data object, established early in adoption to eliminate duplication and conflicting versions across tools.
- Tool rationalization
- Using IT4IT component mapping to find tools with overlapping data objects for consolidation and missing components for acquisition, reducing portfolio sprawl.
- Per-stream metrics
- S2P measures investment alignment and time-to-fund, R2D cycle time and release quality, R2F fulfillment time, and D2C mean time to restore service.
- Value-stream governance
- Decision rights assigned along the streams: portfolio investment decisions in S2P, release approval in R2D, and service restoration authority in D2C.
- IT4IT and ITIL
- Complementary: IT4IT supplies the architectural and data model, while ITIL supplies process practice; neither replaces the other in an operating model.
- IT4IT and DevOps
- Complementary: DevOps contributes delivery culture and automation practice, while IT4IT contributes the data and component model that integrates tooling end to end.
- Component-level maturity
- Assessing maturity per functional component and per data object, which enables targeted improvement instead of one enterprise-wide maturity score.
- Integration by data object
- Specifying integrations through required data objects rather than vendor APIs, so a tool can be replaced without redefining the surrounding value stream.