Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date: 2015-01-19.

Slides:

Advertisements

Similar presentations

Technical Plenary From: oneM2M TP leadership Source: Meeting Date: Agenda Item:

Advertisements

TP#2 Election Process Group Name: TP Source: Victoria Gray, ETSI, Meeting Date: Agenda Item: 6.3,

Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:

4.6 Creation of 3GPP 4.7 How does 3GPP Operate? 4.11 Beyond 3GPP Release ’99.

Project Management Session 7

TST WG Progress Report at TP 15 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Miami, USA Agenda.

DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.

Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

TST WG Progress Report at TP 18 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP18,

TST WG Progress Report at TP 17 Group Name: TST WG Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to , Sapporo, Japan Agenda.

Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, Meeting Date:

ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

WG-2 - ARC TP #16 Status Report Group Name: oneM2M TP #16 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

3GPP Rel-13 Interworking discussions

Recommendations for transfer from TISPAN to 3GPP SP For information Source: Goran Engstrom: TISPAN WG1 chairman Stephen Hayes: 3GPP SA Chairman.

Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.

Work Programme Management Ad hoc Group Report Group Name: one M2M TP9 Source: Convenor WPM Joachim Koss, Gemalto M2M,

Timeline for the oneM2M Partnership Project Timeline and Milestones [Joachim Koss, ETSI] Contribution to oneM2M plenary, 05 Mar 2012 Doc: Source: ETSI.

MoW&M&P Report Group Name: TP19 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

Setting oneM2M’s Market direction

Guidelines for: Release Maintenance, Small Enhancement and Feature Work Items Group Name: TP15 Source: Mow Convenor, (Scarrone Enrico, Telecom Italia)

WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.

Targets for project progress 2015: graduation review – clear documentation and PoC implementation specify general framework and API requirements gap analysis.

Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.

Component 8 Installation and Maintenance of Health IT Systems Unit 4 Structured Systems Analysis and Design This material was developed by Duke University,

Workshop on How to Publish Data in VO ESAC, June 25-June Tips & tricks by the Ivoa Document Coordinator Bruno Rino

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Technical questions on oneM2M certification Group Name: TST Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda.

Timeline for the oneM2M Partnership Project Timeline and Milestones [Steve Barclay, ATIS] [Joachim Koss, ETSI] Contribution to oneM2M-Cons#4, 28 Mar 2012.

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

MCC 3GPP Work program Database Ian Doig, MCC. 3GPP Work program Database Request by Partner Organisations for a common 3G Work program Database. Based.

WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

Discussion for the next oneM2M release Group Name: TP Source: JaeSeung Song, KETI, Jaeho Kim, KETI,

MoW&M&P Report Group Name: TP18 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

3GPP Rel-13 Interworking discussions

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

Planning for the test event Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.

SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:

WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Meeting Date: TST #21 Document.

TST WG Progress Report at TP 18 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP18, Item.

A discussion on Release duration TP #14 Source: JaeSeung Song, KETI (TTA), Meeting Date: TP Discussion_on_Release_duration.

WG2 - ARC TP #20 Status Report Group Name: oneM2M TP #20 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.

MoW Report Group Name: TP21 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

ATS code development workflow Group Name: TST WG Source: Mahdi Ben Alaya, TST WG vice chair, SENSINOV, Miguel.

WPM ad-hoc group report TP#20 Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Discussion on Certification Group Name: TST WG Source: JaeSeung Song, WG6 Chair, Meeting Date: TST #21.

Sauder Unlimited presents… Corporate Development 101 Corey Wong President of BizTech ( )

Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.

TST MBT_for_test_suites_development Use of MBT for test suites development- discussion Group Name: TST WG Source: Easy Global Market (EGM) Meeting.

MoW Report Group Name: TP20 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

MoW&M&P Report Group Name: TP19 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

Status of Active Work Items Level of Completeness

Software Project Configuration Management

Documentation control

Software Configuration Management

WG1 status report to TP#15 Group Name: oneM2M TP15

WPM ad-hoc group report TP#25

Proposed Review Cycle to

Presentation transcript:

Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date:

Recall: Why oneM2M has WI? Assure that there is a sufficient member support for a specific technical activity (that’s why there is a minimum number of supporting companies) Assure that the proposed work is relevant for oneM2M and there is consensus to develop it in oneM2M (that’s why consensus is required to approve it ) © 2014 oneM2M Partners 2

Recall: Why oneM2M has WI? Assure that a clear-as-possible common understanding of the work to be developed and the related timeframe (that’s why description and objectives are very important) Trace the progress of oneM2M technical work. There is a strict relation between the Work Items and the Work Program. © 2014 oneM2M Partners 3

WI: What are about The Working Procedures and the Method of Work give a relevant flexibility (not exhaustive list): a WI can be a new specification, a set of new specifications A CR to a specification, a set of CR to one or more specifications. The specifications targeted by a single WI may pertain to one or more WG. «Rules are for the wise people to be used not for the fools to be abused» © 2014 oneM2M Partners 4

WI: What are about The Working Procedures and the Method of Work give a relevant flexibility (not exhaustive list): a WI can be a new specification, a set of new specifications A CR to a specification, a set of CR to one or more specifications. The specifications targeted by a single WI may pertain to one or more WG. «Rules are for the wise people to be used not for the fools to be abused» © 2014 oneM2M Partners 5

CR process The CR process foresees that only changes needs to be approved to specification after first approval of a specification. So a new version of a specification implementing approved CRs is automatically approved. CR are associated to WI to keep a link among the changes related to a specific feature, for tracing and rollback purposes. © 2014 oneM2M Partners 6

Best practices: specification life cycle Existing specifications and new releases need: Maintenance of past releases versions (correction) Correction and refinement of the technical document in the new release Addition of new technical content in the new release The Work Program traces the new technical content development © 2014 oneM2M Partners 7

So for Release 2……. A set of WI are required to maintain each specification: 1 for Maintenance of Release 1 version 1 for correction and minor technical enhancements in Release 2 version. Minor means something that have a very small technical impact and can be done typically in one CR focalized on a specific existing technical feature © 2014 oneM2M Partners 8

Plus….a set of new R2 Work Items A new work item for each new feature/functionality and for each major enhancement of a new feature/functionality These WI are focalized on the feature, so are typically targeting CRs to a specification or to the set of specifications impacted by the feature (potentially engaging typically more WGs) The work program trace the development of the feature, not the development of the specification © 2014 oneM2M Partners 9