© 2013 OSLC User Group for Communications OSLC Member Section at OASIS present state and outlook, 6 September 2013 Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web

OASIS OSLC Co-Founders 2

© 2013 OSLC User Group for Communications Looking back at our look ahead June 2013 Roadmap 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. These clouds are links to more info, such as the kickoff recording

© 2013 OSLC User Group for Communications Aspirations for OSLC Foundational technology for integration The household name for integrations Natural choice for standardizing loosely- coupled integrations in new domains From the OSLC Steering Committee

© 2013 OSLC User Group for Communications The Technical Vision for OSLC (no change) 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

© 2013 OSLC User Group for Communications Approved Standard The Organizational Vision for OSLC OSLC Member Section (MS) at OASIS Steering Committee (StC) Technical Committees (TC) open-services.net 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 (UG) Subcommittees (SC) Show me more! Foundation for OSLC 3.0

© 2013 OSLC User Group for Communications OSLC at OASIS Progress (6 September) Goal: all OSLC specification will have transitioned to OASIS by the end of Q 2013 Election of the 7 th Steering Committee member OSLC Core 3 to be contributed to OASIS to launch the OSLC Core TC Mark Schulte of Boeing elected to the 7 th StC seat (July 31) OSLC Core TC Charter submitted for comment (September 3) (OSLC Core 3 specification work continues at open-services.net until the OSLC Core TC is created) Who are the other StC Members?

© 2013 OSLC User Group for Communications More details of the OSLC Core Timeline ActivityTarget End DateComments Submit Core TC Charter to OASIS 30 August 2013Proposed charter submitted to OASIS TC administrator. Officially Launch Technical Committee 15 November 2013 Minimum 5 eligible people from at least 2 OASIS organizational members. Core 3 Spec to be initial TC Working Draft. Phase 1: Producing first Committee Specification Draft 31 March st round Committee Spec Public Review Ends 30 April 2014Collect comments from Member Section. Phase 2: Addressing Public Review feedback 31 July 2014Update Committee Spec, take to 2nd round review. 2nd round Committee Spec Public Review Ends 31 August 2014Address review’s comments. (Assume no further review required.) Finalize Committee Specification 30 September 2014No implementation or test case requirements. Phase 3: OASIS Standard Review period & voting Ends 30 November review period, 14 day vote period. Requires 3 statements of use. OASIS Standard15 December 2014 All dates subject to change.

© 2013 OSLC User Group for Communications OSLC at OASIS Progress (8 November update) Goal: all OSLC specification will have transitioned to OASIS by the end of 2014 OSLC Core TC to have its first meeting on November 12 Preparing to submit a Charter for an OSLC Change and Configuration Management TC Drafting a Charter and recruiting co- proposers for an OSLC Automation TC 4Q 2013 Existing OSLC domain specs are contributed to create affiliated TCs New domain work to start as affiliated TCs Who are the Members of the OSLC Core TC?

© 2013 OSLC User Group for Communications OSLC Member Section Scope Draft Converge Final Core 3.0 Change Management 3.0 Configuration Management Asset Management 3.0 Quality Management 3.0 Architecture Management 3.0 Estimation and Measurement PLM/ALM Automation 3.0 Performance Monitoring 3.0 Resource Reconciliation 3.0 Change and Configuration Management TC Requirements, Architecture, and Quality Management TC Core TC Integrated Service Management TC Automation TC 1 2 A B C D Timing and Mission of OSLC Domain TCs, TBD Requirements Management 3.0 Other TCs based on other OSLC WGs, OSLC UGs, existing external initiatives, Member interest, or a combination of. E OSLC UG Unordered External Initiative Member Interest Active specification work continues at open-services.net until those specs are contributed to an affiliated TC at OASIS Current spec progress?

© 2013 OSLC User Group for Communications OSLC MS Affiliated TC Creation Pipeline Prioritization & Preparation with MS members TC Charter Creation & TC Co-submitter Recruiting TC Charter Submission & OASIS Process OASIS Approval & 1 st TC meeting Core TC Done  12 Nov 2013 OSLC CCM TC Done  Sep-Nov 2013Nov-Dec 2013Jan 2014 OSLC Automation TC Done  Nov-Dec 2013Dec-Jan 2014Feb 2014 OSLC RAQ Mgmt TC  Nov Jan 2014 Feb 2014Mar-Apr 2014May 2014 Jul ‘13Jun ‘14Oct ‘13Feb ‘14 Core Change and Configuration Mgmt Automation Requirements, Architecture, and Quality Mgmt

© 2013 OSLC User Group for Communications How to Participate in OSLC Today Join the OSLC Member Section at OASISJoin the OSLC Member Section at OASIS (if you haven’t already) Participate in affiliated TCs Join the OSLC Core TC when it launches Be a co-proposer of a 1 st wave TC Start discussing your ideas and voicing your opinions On the OSLC Member Section mailing listOSLC Member Section mailing list On the OSLC ForumsOSLC Forums Get active at open-services.netopen-services.net Complete a Members Agreement and get listed on the Organizations pageMembers AgreementOrganizations page Join a User Group to help define scenariosUser Group Join a Work Group to help define the version 3 specificationsWork Group

© 2013 OSLC User Group for Communications BACKUP

© 2013 OSLC User Group for Communications 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:

© 2013 OSLC User Group for Communications OSLC: Standardizing the sharing of 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

© 2013 OSLC User Group for Communications OSLC inside OASIS OSLC Member Section 22 OASIS Members are the foundersOther OASIS Members can join when they choose OASIS Steering Committee 1 Technical Architecture TC 2 1.The current OSLC Steering Committee becomes the OASIS OSLC Member Section Steering Committee 2.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 TC Domain TC 3 Subcommittee Subcommittee 4 advises guides oversees