The Integration Problem Point-to-point integrations don’t scale Vendor-specific integrations lock you in Over time, the costs of the current set of integrations goes up, as does the cost of making changes Integrations consume more and more of the IT budget: Integration failures are the top 2 causes of software project delays* End-user productivity suffers: Either stuck with the wrong tool, stuck doing manual integration, or both More limited ability to respond to change: Constrained by exhausted IT budget and lower productivity time * Source: Commissioned study conducted by Forrester Consulting on behalf of IBM

Automation Monitoring OSLC’s Simple Solution Increased traceability Architecture of the Web Linked Data Link to where the data lives as opposed to copying and synchronizing Increased reuse Standard Interfaces Better visibility “Just Enough” integrationDecreased maintenance costs Users can work across the integration without leaving their favorite tool

Leverage the growing industry impact of OSLC Integrate over 40 tools natively and through third-party adaptersFoundation for major interoperability projectsDeepening and expanding scopeLeading choice for Strategic Integration Technology Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web Lyo makes OSLC integrations easier SDK, test suites, and reference implementations Java (OSLC4J) library + recent Perl contributions Pending community contributions for.NET OSLC4J + Test Suites for OSLC Core, CM, QM, & AS OSLC Steering Committee Founding members: Accenture, Creative Intellect, EADS, Siemens, Tasktop, and IBM Open Governance & Community Direction Standardizing part of the OSLC Core specification Co-submitters: IBM, DERI, EMC, Oracle, Red Hat, SemanticWeb.com, and Tasktop 41 participants from 24 organizations 1 st Editor’s Draft already released LINKED DATA PLATFORM WORKING GROUP Linked Data & OSLC #1 & #2 standards for “greater collaboration, social business interaction and cloud computing” open-services.net

Identify Scenarios Iterate on working drafts Call it a spec Gain technical consensus  Minimalist/additive approach  Not a “complete” definition for a given area  Scenario driven scope  Co-evolve spec and implementations  Open participation around active core group Iterative Specification Authoring OSLC Lifecycle integration inspired by the web

Linked Lifecycle Data  The data is the thing Resources and relationships Tools operate on the data Tools execute the process Tools expose their data in a common way (REST)  Lifecycle integration = tracing, indexing, analyzing the web of lifecycle data where it lives  Utilizes architecture of the internet All data are resources with HTTP URIs Open standards Loosely coupled Technology neutral Scalable, extensible