© 2013 oslc steering committee1 what if integration came standard? oslc to be standardized at oasis...

© 2013 OSLC Steering Committee1

What if integration came standard?

OSLC to be standardized at OASIS

Analyst Community Call: 10 AM EDT, 30 May 2013

Open Services for Lifecycle CollaborationLifecycle integration inspired by the web

© 2013 OSLC Steering Committee

Leading today’s call


Mik KerstenCEOTasktopOSLC Steering Committee

Scott McGrathCOOOASIS

Ludmila OhlssonProduct Manager, Software DevelopmentEricsson


Agenda

1. The News

2. Related Background

1. OSLC

2. OASIS

3. What this Means

4. Questions and Discussion


1.The News



OSLC Member Section Created at OASIS


HistoryC

omm

unity

gov

erna

nce

of O

SLC

IBM de facto governance (with community support)

Steering committeeMulti-organization steering committee establishedNew governance model introduced

OASISInternationally recognized independent SDOFormal support from 22 organizations (at launch)Participation governed by established OASIS model

June 2012

May 20132012


Why OSLC and Standardizing at OASIS Matters


The OSLC Member Section Co-Founders


2.1.Background on OSLC



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

http://oslc.co/organizations


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


OSLC: Standardizing the sharing of lifecycle data


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


Aspirations for OSLC


2.2.Background on OASIS

Scott McGrathCOOOASIS

OASIS Background

• Nonprofit consortium, founded 1993 to advance document standards

• Global community5,000+ participants 600+ orgs & individuals in 100+ countries

• Open, democratic, transparent• Home of nine Member Sections and

70+ Technical Committees• Create standards for Cloud, M2M, IoT, security, privacy,

content technologies, energy, eGov, legal, emergency management + other areas identified by members.

16

+ OSLC

OASIS OSLC Co-Founders

17

What criteria did OSLC use in choosing OASIS?

Must Have

Open accredited process— transparent and available to all

Large community of experts that welcomes participants

Level playing field– organizations large and small have same influence

Balance of rules and freedom– permanence and respect of outcomes

18

What happens when OSLC transitions to OASIS?

OASIS OSLC Member Section

OSLC retains its elected governance and brand

OSLC continues to set its own technical agenda

Members form OSLC Technical Committees under OASIS process

OASIS commits to providing OSLC specs freely and permanently

Participation in OSLC expands to existing OASIS member base

OSLC takes advantage of proven OASIS IPR Policy

Ratified OSLC standards may be advanced to ISO, ITU, IEC, ANSI…

19


3.What this Means

Ludmila OhlssonProduct Manager, Software DevelopmentEricsson

EricssonIntegration Framework

Ludmila Ohlsson

Ericsson Internal | 2013-05-20 |

ERICSSON at a glance

30 000 Number of patents

110 255 Number of employees

950MSubscribers in networks that we manage

2.5B Subscribers on Ericsson supported networks

40%Of the world's mobile calls are on Ericsson networks

227.8B SEK, Net sales 2012

180 Countries we operate in


135 years OF INNOVATIONS› 1878 Telegraph to telephone

› 1923 Manual switching to automatic switching

› 1968 Electro mechanics to computer control

› 1981 Fixed communications to mobile communication

› 1991 Analog (1G) to digital (2G) mobile technology

› 1998 Integration of voice and data in mobile networks

› 2001 Launch of WCDMA/3G networks in Western Europe

› 2006 Launch of HSPA mobile broadband globally

› 2009 First commercial LTE network launched

› 2011 Sales of mobile broadband took off

Early automatic switch

Multi-standard radio base station RBS 6000


OPEN standards KEY FOR THE INDUSTRY

› Innovation is an important element of our corporate culture› Early involvement in creating new standards› Largest contributor to open standards› Often first to market with new solutions› 5th largest software supplier in the world


› Support the end 2 end flow– Multiple tools involved - integrations to make information flow

efficient (more than 4000 tools in our IT Catalog!)– Should be as seamless and transparent as possible– Ideally focus on flow, tasks, information – not tools

› Visualization, traceability, dashboards– Cross PDUs, multi-standard features

Why Integrations?


Tools Framework

Design & Implementation

IDE Code generation

Builds

ReviewsCAD

Integration & Verification

Pass or Fail Test Automation

Simulation

SQA

Team & Program

Backlog Anatomy

DashboardResources

Wiki

System & Product

Architecture Use Cases

DefectsModeling

Release

IntegrationPrinciples

IntegrationPrinciples OSLCOSLC Use CasesUse Cases

Test ServiceTest Service Data ModelData ModelReportingService

ReportingService

Ericsson Internal | 2013-05-20 | Page 28

Ongoing activities

› Implementation of OSLC interfaces› PoC of existing interfaces› Discussions with vendors on OSLC implementation› Visualization › Collaboration with similar companies on OSLC › Collaboration with Universities and EU projects› Collection of findings› more

Ericsson Internal | 2013-05-20 | Page 29

Summary

› We need OSLC for cheaper, quicker and better integrations and visualisations

› OASIS OSLC standards will drive new implementations from our many suppliers

› OASIS standardization process will help us drive new scenarios into future OSLC standards


4.Questions and Discussion


BACKUP


The OSLC Steering Committee


Rainer ErschSenior Research ScientistSiemens

David IngramManaging Director

Accenture

Andreas KeisManager, Software EngineeringEADS Innovation Works UK

Mik KerstenCEO

Tasktop

Bola RotibiResearch DirectorCreative Intellect

John WiegandDistinguished Engineer and Chief Architect

IBM Rational(Steering Committee Chairman)

Sean KennedyOSLC StCOperations Coordinator

Steve SpeicherOSLC StC Technical Coordinator

OSLC StC Staff Members:


Roadmap for OSLC at OASIS

OSLC Member Section


To be refined with input from the OSLC Member Section participants.


Approved Standard

Approved Standard

The Vision for OSLC

OASIS 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


OSLC inside OASIS

OSLC Member Section5+ OASIS Members are the founders Other OASIS Members can join when

they choose

OASIS

Steering Committee1

Technical Architecture TC2

Technical Architecture TC2

1. The current OSLC Steering Committee becomes the OASIS OSLC Member Section Steering Committee2. The Core workgroup becomes the Technical Architecture TC (Technical Committee). 3. Domain TCs are created by composing several OSLC domain workgroups. 4. Subcommittees may be created by the Steering Committee for a number of purposes. E.g. scenario development and

prioritization or exploration of new domains ahead of creating a new TC.

Domain TCDomain TCDomain TCDomain TC

Domain TC3Domain TC3

SubcommitteeSubcommittee

Subcommittee4

advises

guides

<relationship>

overseesoversees

© 2013 oslc steering committee1 what if integration came standard? oslc to be standardized at oasis...

Documents

oslc slide

oslc steering committee8

oslc steering committee7

oslc steering committee10

efficientlystandardizing

oslc mission co

software integration

oasis matters software