1 oslc user group for communications, 2013 oslc spring 2013 update what if integration came...
TRANSCRIPT
1 OSLC User Group for Communications, 2013
OSLC Spring 2013 Update
What if integration came standard?
2 OSLC User Group for Communications, 2013
THE BACKGROUNDOSLC Why, What, How, and Where
3 OSLC User Group for Communications, 2013
More limited ability to respond to changeConstrained by exhausted IT budget and lower productivity
More limited ability to respond to changeConstrained 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 ProblemPoint-to-point Integrationsdon’t scale
Monocultureslock you in
Maintenance, management,and change costs go up over time
Creating newintegrations isunpredictable
Ongoing and unexpectedcosts drain resources
Past choicesrestrict present
action andfuture 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 byForrester Consulting on behalf of IBM.
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
OSLC is beneficial to many stakeholdersContributing Organizations: http://oslc.co/organizations
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 OSLC User Group for Communications, 2013
OSLC: Standardizing how tools share lifecycle data
Open Services for Lifecycle CollaborationLifecycle integration inspired by the web
Linked Data Platform Working Group
Inspired by the web
ProvenFree to use and share
OpenChanging the industry
InnovativeOSLC:
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 OSLC User Group for Communications, 2013
THE NEWSPast, Present, and Future
7
8 OSLC User Group for Communications, 2013
OSLC Establishes Itself at OASIS
OSLC Member Section
Open Services for Lifecycle CollaborationLifecycle integration inspired by the web
To be refined with input from the OSLC Member Section participants.
9 OSLC User Group for Communications, 2013
Broad Support: OSLC Member Section Co-Founders
10 OSLC User Group for Communications, 2013
OSLC Specification Highlights
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 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.
There are more than enough hurdles to achieving enterprise mobility …
What if integration came standard?OSLC User Group for MobileIt all starts with scenarios. http://bit.ly/OSLC-UG-Mobile
Rocket science is hard enough …
Shouldn’t integration come standard?OSLC User Group for Embedded SystemsIt all starts with scenarios. http://bit.ly/OSLC-UG-EmbSys
14 OSLC User Group for Communications, 2013
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 OSLC User Group for Communications, 2013
Approved Standard
Approved Standard
The Vision for OSLCOASIS OSLC Member Section
Steering Committee
Technical CommitteesTechnical
Committees
open-services.net
Forums
~~~~~..~~
Forums
~~~~~..~~
Implementer’s Expo
News
Resources and Tutorials
Eclipse Lyo
OSLC4NetLibraries Test SuitesSamples
and Examples
Reference Implementations
W3C LDP WG
Use what you need,share what you can.
User GroupsUser Groups
SubcommitteesSubcommittees