Requirements Overview Group Name: Technical Plenary (TP19) Source: Shelby Kiewel, iconectiv, Meeting Date: 2015-09-07 Agenda Item:

Slides:

Advertisements

Similar presentations

Session 321 An Implementation Strategy: Identifies who is responsible for which actions Identifies what funding mechanisms and other resources are available.

Advertisements

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

WG5 - MAS Progress Report at TP #16 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

App-ID Ad-Hoc Technical Issues TP AppID R02 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,

Financials 9.1 Upgrade Progress Update Financial Unit Liaison Meeting May 18, 2011.

OneM2M portal introduction Group Name: Technical Plenary Source: Gerry McAuley, ETSI, Meeting Date: Agenda Item: 1.5.

Proposal for App Id and Service Provider Id registration Group Name: Shelby Kiewel Source: Shelby Kiewel, iconectiv / Ericsson,

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.

App-ID Ad-Hoc Technical Issues TP AppID R01 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,

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

Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless

OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.

Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,

Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Meeting Date:

M2M Abstraction & Semantics Group Name: WG5 Source: France Telecom, NEC Europe Ltd., Meeting Date: xx.

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.

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

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

Setting oneM2M’s Market direction

WG1 status report to TP#17 Group Name: oneM2M TP17 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#17, Item 10.3,

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

Proposal for App Id and Service Provider Id registration Group Name: Shelby Source: Shelby, iconectiv / Ericsson,

WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to

Report of the oneM2M Legal Subcommittee Group Name: oneM2M Steering Committee Source: Thomas Goode, ATIS, Meeting Date:

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

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

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

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

SEC Conference calls following TP#11 Group Name: WG4 (SEC ) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information.

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:

Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: Agenda Item:

3GPP Rel-13 Interworking discussions

LWM2M Interworking Group Name: Architecture

ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.

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

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:

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

1 ERCOT Retail Release Overview. 2 How Are Changes Managed? Retail Testing Business Teams Development Teams Release Management Management of: Migration.

ASUG SAP Adoption Influence Council The focus is on how to increase awareness, adoption and implementation of SAP enhancements that are delivered as part.

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:

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

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:

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016

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

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.

Technical Plenary Terms for the collaboration with P2413 From: oneM2M TP Chair Source: Meeting Date: Agenda Item:

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

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

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

Query Health Operations Workgroup Standards & Interoperability (S&I) Framework October 13, :00am – 12:00pm ET.

Proposed Process for Forming the oneM2M Baseline  Group name: TP#1  Source: Laurent Laporte, Sprint,

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

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

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

Status of Active Work Items Level of Completeness

App-ID Ad-Hoc Technical Issues TP AppID R02

WPM ad-hoc group report TP#24

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

Release Timeline Discussion R2 and beyond

WPM ad-hoc group report TP#25

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

IMT-Advanced Closing Report

Presentation transcript:

Requirements Overview Group Name: Technical Plenary (TP19) Source: Shelby Kiewel, iconectiv, Meeting Date: Agenda Item: Requirements Review – Release 2 Review

Requirements By The Numbers Total Requirements as of 26 August 2015 – 255 Total Requirements in V New Requirements Targeted for Release 2 – Tentative, pending agreement during REQ19 – Based on all new requirements agreed post Release 1 98 Requirements Implemented in Release 1 11 Requirements Partially Met in Release 1 – Review required for inclusion in Release 2 34 Requirements Agreed & Not Met in Release 1 – Review required for inclusion in Release 2 – Review to occur during REQ19 © 2014 oneM2M Partners 2

Requirements By The Numbers Total Requirements as of 26 August 2015 – Requirements by grouping 99 Overall System Requirements – 26 New Requirements targeted for Release 2 – 45 Requirements met in Release 1 – 28 Requirements to be reviewed for inclusion in Release 2 19 Management Requirements – 2 Requirements targeted for Release 2 – 16 Requirements met in Release 1 – 1 Requirements to be reviewed for inclusion in Release 2 61 Security Requirements – 35 Requirements targeted for Release 2 – 18 Requirements met in Release 1 – 8 Requirements to be reviewed for inclusion in Release 2 © 2014 oneM2M Partners 3

Requirements By The Numbers Total Requirements as of 26 August 2015 – Requirements by grouping (cont) 6 Charging Requirements – 0 Requirements targeted for Release 2 – 2 Requirements met in Release 1 – 4 Requirements to be reviewed for inclusion in Release 2 10 Operational Requirements – 4 Requirements targeted for Release 2 – 3 Requirements met in Release 1 – 3 Requirements to be reviewed for inclusion in Release 2 15 Communication Management Requirements – 4 Requirements targeted for Release 2 – 3 Requirements met in Release 1 – 3 Requirements to be reviewed for inclusion in Release 2 © 2014 oneM2M Partners 4

Requirements By The Numbers Total Requirements as of 26 August 2015 – Requirements by grouping (cont) 8 LWM2M Interworking Requirements – 8 Requirements targeted for Release 2 2 Non-Functional Requirements – 2 Requirements met in Release 1 © 2014 oneM2M Partners 5

Requirements By The Numbers Total Requirements as of 26 August 2015 – 36 Semantic Requirements 17 Ontology Requirements – 17 New Requirements targeted for Release 2 7 Semantics Annotation Requirements – 7 New Requirements targeted for Release 2 1 Semantics Query Requirements – 1 New Requirement targeted for Release 2 5 Semantics Mashup Requirements – 5 New Requirements targeted for Release 2 3 Semantics Reasoning Requirements – 3 New Requirements targeted for Release 2 3 Data Analytics Requirements – 3 New Requirements targeted for Release 2 © 2014 oneM2M Partners 6

Next Steps Review and Input on Release 2 Inclusion – Contribution REQ to be worked during REQ19 sessions, noting requirements “Targeted for Release 2” – Requesting review of all requirements not currently considered part of Release 1 Determine inclusion in Release 2 Determine validity of requirements carried over from pre-Release 1 activities Determine clarifications needed Work with MoW on Release 3 REQ timelines © 2014 oneM2M Partners 7