1 / 15

OSLC Spring 2013 Update

OSLC Spring 2013 Update. What if integration came standard?. OSLC Why, What, How, and Where. The Background. The Integration Problem. Point-to-point Integrations don’t scale. Monocultures lock you in. Maintenance, management, and change costs go up over time. Ongoing and unexpected

padillae
Download Presentation

OSLC Spring 2013 Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSLC Spring 2013 Update What if integration came standard?

  2. OSLC Why, What, How, and Where The Background

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

  4. The Basics: What is OSLC, and why should I care? OSLC is an open community building practical specifications for integrating software OSLC is beneficial to many stakeholders Contributing Organizations: http://oslc.co/organizations

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

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

  7. Past, Present, and Future The News

  8. OSLC Establishes Itself at OASIS Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web To be refined with input from the OSLC Member Section participants. OSLC Member Section

  9. Broad Support: OSLC Member Section Co-Founders

  10. OSLC Specification Highlights

  11. 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 • To discuss, plan and execute communications about the work of the OSLC community. • Embedded Systems • To explore issues in embedded systems across a broad variety of application domains. • 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. Eclipse 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/

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

More Related