1. 1 OSLC User Group for Communications, 2013 OSLC Spring 2013 Update What if integration came standard?

2. 2 OSLC User Group for Communications, 2013 THE BACKGROUND OSLC Why, What, How, and Where

3. 3 OSLC User Group for Communications, 2013 More limited ability to respond to change Constrained by exhausted IT budget and lower productivity More limited ability to respond to change Constrained by exhausted IT budget and lower productivity Integrations consume more of the IT budget: integration failures are the top 2 causes of software project delays* Integrations consume more of the IT budget: integration failures are the top 2 causes of software project delays* The Integration Problem Point-to-point Integrations don’t scale Monocultures lock you in Maintenance, management, and change costs go up over time Creating new integrations is unpredictable Ongoing and unexpected costs drain resources Past choices restrict present action and future vision End-user productivity suffers: Either stuck with the wrong tool, stuck doing manual integration; often stuck doing both End-user productivity suffers: Either stuck with the wrong tool, stuck doing manual integration; often stuck doing both * Commissioned study conducted by Forrester Consulting on behalf of IBM.

4. 4 OSLC User Group for Communications, 2013 The Basics: What is OSLC, and why should I care? OSLC is an open community building practical specifications for integrating software Tool Maker create software using reusable and open assets that will interoperate with other tools both inside and outside your influence providing time and cost savings Tool Manager reduce the complexity and risk of increasingly complex software infrastructures, and improve the value of software across a broader set of internal and external stakeholders Tool User choose the best tools for your job and have them interact seamlessly to achieve traceability and visibility with the rest of your organization Systems Integrator focus energy and resources on higher-value customizations, deliver more business value to your clients, and increase client satisfaction OSLC is beneficial to many stakeholders Contributing Organizations: http://oslc.co/organizationshttp://oslc.co/organizations

5. 5 OSLC User Group for Communications, 2013 The Executive Summary: OSLC’s Simple Solution Automation Monitoring Increased traceability Architecture of the Web Linked Data Increased reuse Standard Interfaces Better visibility “Just Enough” integration Decreased maintenance costs Users can work seamlessly across their tools (complex and fragile synchronization schemes not required) OSLC is an open and scalable approach to lifecycle integration. It simplifies key integration scenarios across heterogeneous tools

6. 6 OSLC User Group for Communications, 2013 OSLC: Standardizing how tools share lifecycle data Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web Linked Data Platform Working Group Inspired by the web Proven Free to use and share Open Changing the industry Innovative OSLC: Generally applicable: specs available for many domains covering ALM, DevOps, ISM, and PLM Leading choice for strategic integration technology Scenario-driven & Solution-oriented OSLC Member Section The Resource for OSLC Implementers Based on and Shaping the Future of Internet Architecture Open and Independent Governance and Leadership

7. 7 OSLC User Group for Communications, 2013 THE NEWS Past, Present, and Future 7

8. 8 OSLC User Group for Communications, 2013 OSLC Establishes Itself at OASIS December 2012 OSLC Steering Committee approves plan to standardize OSLC domain specs at OASIS May 2013 OASIS Board unanimously approves creation of the OSLC Member Section co- founded by 22 organizations June 2013 First OSLC Member Section Steering Committee meeting Election announced to fill remaining Steering Committee seat 3Q 2013 OSLC Core 3.0 spec to be contributed to OASIS to launch the OSLC Core Technical Committee 4Q 2013 – 2014 OSLC 3.0 domain specs are contributed to OASIS as they reach finalization OSLC Member Section Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web To be refined with input from the OSLC Member Section participants.

9. 9 OSLC User Group for Communications, 2013 Broad Support: OSLC Member Section Co-Founders Accenture Bank of America Boeing Creative Intellect EADS Eclipse Foundation EricssonFujitsuIBM JPMorgan Chase Kovair Software KTH Royal Institute of Technology Mentor Graphics National Instruments Persistent Red HatSiemensSodiusSoftware AGTasktop Universidad Politécnica de Madrid WSO2

10. 10 OSLC User Group for Communications, 2013 OSLC Specification Highlights OSLC Performance Monitoring OSLC Reconciliation OSLC Configuration Management New Workgroups OSLC Tracked Resource Set (defines what a service must provide to enable indexing)OSLC Tracked Resource Set OSLC Partial Update (guidance on using HTTP PATCH)OSLC Partial Update New Contributions OSLC Asset Management V2 OSLC Automation V2 OSLC Reconciliation V2 OSLC Performance Monitoring V2 Finalized Specifications OSLC Core and many domain specs working towards V3 W3C Linked Data Platform 2 nd Editor’s Draft published Ongoing Specification Work

11. 11 OSLC User Group for Communications, 2013 OSLC User Groups Launched  Primary goal: To make it easier for you to make non-technical contributions to OSLC  Examples:  Describing and defining the key integration scenarios for your organization  And even driving those scenarios into future OSLC standards  Collaborating on experience reports, best practice white papers, and other assets  Leading and participating in community marketing, promotion, recruiting, and more  3 User Groups exist already … YOU can join them, or propose new ones  Communications Communications  To discuss, plan and execute communications about the work of the OSLC community.  Embedded Systems Embedded Systems  To explore issues in embedded systems across a broad variety of application domains.embedded systems  Mobile Mobile  To explore and understand the integration scenarios that make Mobile painful for organizations, and to drive these scenarios into OSLC standards.

12. There are more than enough hurdles to achieving enterprise mobility … What if integration came standard? OSLC User Group for Mobile It all starts with scenarios. http://bit.ly/OSLC-UG-Mobile

13. Rocket science is hard enough … Shouldn’t integration come standard? OSLC User Group for Embedded Systems It all starts with scenarios. http://bit.ly/OSLC-UG-EmbSys

14. 14 OSLC User Group for Communications, 2013 Eclipse Lyo: http://eclipse.org/lyo http://eclipse.org/lyo  Eclipse project created with the goal of providing tools to enable adoption of OSLC specifications.  Content includes  Code libraries (Java, Perl, others under development)  Give developers tools to ease OSLC implementations  Reference implementations of specifications  Provide a starting point for new integrations  Test suites and test reporting. Covers OSLC Core, CM, QM, RM and Asset today.  Accelerate and assess development  Samples, tutorials and documentation  Working samples of OSLC integrations with Bugzilla, Excel, Jazz tools and more. .NET developers, see also the OSLC4Net project on CodePlex  https://oslc4net.codeplex.com/ https://oslc4net.codeplex.com/

15. 15 OSLC User Group for Communications, 2013 Approved Standard The Vision for OSLC OASIS OSLC Member Section Steering Committee Technical Committees open-services.net Forums ~~~ ~~..~~ Forums ~~~ ~~..~~ Implementer’s Expo News Resources and Tutorials Eclipse Lyo OSLC4Net LibrariesTest Suites Samples and Examples Reference Implementations W3C LDP WG Use what you need, share what you can. User Groups Subcommittees