© 2013 oslc steering committee1 proposal to create oslc affiliated technical committees oslc...

© 2013 OSLC Steering Committee1

Proposal to Create

OSLC Affiliated Technical Committees

OSLC Steering Committee Meeting: 1 PM EDT, 8 July 2013

Open Services for Lifecycle CollaborationLifecycle integration inspired by the web

© 2013 OSLC Steering Committee

STARTING POINTi.e. what was communicated at the kickoff meeting

3Q 2013• Election of the

7th Steering Committee member• OSLC Core 3 to

be contributed to OASIS to launch the OSLC Core TC


Roadmap for OSLC 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.


Timeline for OSLC Core Transition

Activity Target End Date Comments

Submit Core TC Charter to OASIS

2 August 2013 Proposed charter submitted to OASIS TC administrator.

Officially Launch Technical Committee

15 October 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 2014

1st round Committee Spec Public Review Ends

30 April 2014 Collect comments from Member Section.

Phase 2: Addressing Public Review feedback

31 July 2014 Update Committee Spec, take to 2nd round review.

2nd round Committee Spec Public Review Ends

31 August 2014 Address review’s comments.(Assume no further review required.)

Finalize Committee Specification

30 September 2014 No implementation or test case requirements.

Phase 3: OASIS Standard Review period & voting Ends

30 November 2014 60 review period, 14 day vote period. Requires 3 statements of use.

OASIS Standard 15 December 2014

All dates subject to change.


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 and Quality Management TC

Core TC

Integrated Service Management TC

Automation TC

1

2

A

B

C

D

Example Domain TC Content & Creation Phases

Requirements Management 3.0

Other TCs based on other OSLC WGs, OSLC UGs, existing external initiatives, Member interest, or a combination of.

E

OSLC UGOSLC UG

OSLC UG

Unordere

d

External InitiativeExternal

InitiativeExternal Initiative

Member InterestMember InterestMember

InterestMember InterestMember

InterestMember Interest


PLAN CHALLENGESi.e. concerns and perceived problems with this plan


Q&A Based on Our Current Plan

What TC(s) comes after Core?

– We’re not really sure. It depends on OSLC 3 specification progress and community interest.

If we knew what was next, when would it happen?

– We’re not really sure. Sometime after we’ve learnt from the experience of creating the Core TC … maybe before the end of 2013 …

How are MS members supposed to get value out of their membership?

– Election … be a founder for the Core TC … mailing list … open-services.net … ???

Why would new organizations join the MS?

– ???


PLAN ELABORATIONi.e. augment the plan so that we can give better answers


TC Creation Pipeline

Prioritization & Preparation

TC Charter Creation & TC Co-founder Recruiting

TC Charter Submission & OASIS Process

OASIS Approval & 1st TC meeting

Core TC Done Jul 2013 Aug-Sep 2013 Oct 2013

1st Domain TC(s)

Jul-Aug 2013 Aug-Sep 2013 Sep-Nov 2013 Nov 2013

2nd Domain TC Wave

Sep-Oct 2013 Nov 2013 Dec-Jan 2014 Feb 2014

3rd Domain TC Wave

Nov 2013 - Jan 2014

Feb 2014 Mar-Apr 2014 May 2014

Jul ‘13 Jun ‘14Oct ‘13 Feb ‘14

Core

1st Domain TC’s

2nd Domain TC Wave

3rd Domain TC Wave


Pipeline Comments

As Core passes through each phase we can apply the learnings to the 1st Domain TC(s)

– And similarly for the 2nd and 3rd waves

– To learn the most from our first time through, we should apply those lessons ASAP

Which Domain TC(s) we create after Core should be determined by a number of factors

– Interest from the Member Section

– Progress of the version 3 specification at open-services.net

– Perceived maturity of scenarios and scope (for new domains, or any existing spec that has reason to start at OASIS based on its version 2 documents plus new scenarios)

The 2nd and 3rd waves may be more conceptual than actual … at that point, creation of new TCs may be driven by the Members more than regimented by the Steering Committe


Q&A Based on the Proposed Plan

What TC(s) comes after Core?

– We’re not really sure. It depends on OSLC 3 specification progress and community interest. If there is strong interest in one or two, we can start working on the Charter(s) as early as August 2013.

If we knew what was next, when would it happen?

– Given sufficient interest and energy from the community, the first domain TC(s) could be up and running as early as November 2013.

How are MS members supposed to get value out of their membership?

– Express your PoV and contribute your energy to choose and create, and start work in, the Core TC and domain TCs too.

Why would new organizations join the MS?

– It is a vibrant and dynamic community working to standardize how tools share data in, and across, a number of domains, including … Member contributions are encouraged.


BACKUP


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 proposal to create oslc affiliated technical committees oslc...

Documents