Open Technology for an Open Lifecycle Sean Kennedy, OSLC Community Development Leader @seanpk8 A look at the challenges facing today’s organizations and an open (libre) solution to an open (unsolved) problem. 1 1 1 1

Better, Cheaper, Faster Delivery Lifecycle Client Expectations Competitive Pressures Regulatory Requirements Industry Trends

Improved Process and Technology Should Help … Agile Lean DevOps Technology Analytics Big Data Cloud Mobile Social These industry trends can help us achieve our goals, but they also add complexity and change into our delivery lifecycle. … but they’re not enough

The Integration Problem 4 The Integration Problem Point-to-point integrations don’t scale Product-specific integrations lock you in Over time, the costs of the current set of integrations goes up, as does the cost of making changes time So what exactly is so wrong with how integrations are handled today? First, integrations are typically an afterthought of product development. Vendors start out trying to solve a specific and relatively narrow part of the overall lifecycle needs and deliver a point-product. Examples include compilers for code development, SCM tools for version management, automated testing tools for Quality Management, etc. Once these tools do their particular job well, vendors other tools with which they need to integrate. But by then, the tools are disparate—they provide vendor-specific Application Program Interfaces (API) that generally don’t match up with APIs from other tools. Nonetheless, two tools can be integrated one way or another. And that’s how things start out: point-to-point. The problem then is that, as more and more tools need to interact, the combinations grow exponentially. Developers quickly find that point-to-point integrations done with conventional approaches simply don’t scale. They are hard to develop, and even harder to maintain. Customers become quickly disenchanted with the results and eventually give up on trying to make such a solution work across any broad scale of deployment. More importantly, customers that do stick it out with these integrations find themselves locked into not only the vendor-specific lifecycle tools but also their integrations. This results in tremendous inflexibility for the customer to respond to changing business conditions. Consequently, over time, the cost of maintaining their ALM lifecycle tool solution grows significantly with no abatement in sight. More limited ability to respond to change: Constrained by exhausted IT budget and lower productivity End-user productivity suffers: Either stuck with the wrong tool, stuck doing manual integration, or both Integrations consume more and more of the IT budget: Integration failures are the top 2 causes of software project delays* * Source: Commissioned study conducted by Forrester Consulting on behalf of IBM

A Simple, Standards-based, Solution Organizations can collaborate across their delivery lifecycle (complex and fragile synchronization schemes not required) Automation Monitoring Architecture of the Web Standard Interfaces Linked Data “Just Enough” integration Increased reuse Increased traceability You do this everyday! Web browser example. + single web page, data sourced from many places … ads, videos, pictures, tweets, comments, content, more links Linking to application lifecycle data where it is created, instead of copying and synchronizing between tools, is the key insight of OSLC. Doing so using standard interfaces, on top of a proven architecture, has helped many realize the value of OSLC already. With OSLC, instead of worrying about integrating specific tools, we focus on composing a set of capabilities. Animations (OSLC is …): Approach to integrations Philosophy of specification development Set of specifications that tell you what and how to integrate various capabilities It is also the open community where all this happens 4. Read This has benefits to professional users (5), business leaders (6) and creators of integrations (7) Decreased maintenance costs Better visibility OSLC is an open and scalable approach to lifecycle integration. It simplifies key integration scenarios across heterogeneous tools

Better, Cheaper, Faster Open Lifecycle Process Technology Agile Lean DevOps Technology Analytics Big Data Cloud Mobile Social Open Lifecycle Client Expectations Competitive Pressures Regulatory Requirements Industry Trends An open lifecycle is more adaptive and responsive. It helps you more easily improve your processes and incorporate disruptive technologies into your delivery lifecycle. By addressing the integration problem directly, we enable the delivery of higher quality, higher value, products to the market in less time than ever before.

Learn More & Collaborate oslc-community.org eclipse.org/lyo