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

Slides:

Advertisements

Similar presentations

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

Advertisements

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

Analysis of oneM2M Certification Model TST 15 Source: Sookhyun Jeon, TTA, Meeting Date:

Test WG (WG6) 2015 Planning TST 15 Source: JaeSeung Song, TST WG Convenor (TTA), Meeting Date: TST WG6_2015_planning.

Testing Framework TST 15 Source: Laurent Velez, ETSI, Meeting Date: TST Testing_framework.PPT.

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

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

Analysis of Available oneM2M Certification Models TST 15.3 Source: JaeSeung Song (WG6 Chair, Sookhyun Jeon (TTA,

ISO 9001:2015 Revision overview - General users

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

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.

CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.

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

Larry Wolf, chair Marc Probst, co-chair Certification / Adoption Workgroup March 19, 2014.

Part II: Planning Your Research Project Module Six: Proposal Development RESEARCH PROJECT MANAGEMENT 1.

SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed draft.

SCFAH r1 Title: Working Draft “Ad-Hoc Recommendation to SC on 3GPP2 Future” Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.

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

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

An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T;

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

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

Summary Report Project Name: IHTSDO Workbench Brief Project Description: Development of a collaborative tool to allow maintenance of terminology, mapping.

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

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

DevelopersCommitters Users I’m getting the following exception…. Anybody have any clue why??? +1, I like that idea… Source & Binary Code Repository Bug.

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

Issues in Evaluation Criteria Document November 15, 2006.

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.

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

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 Preliminary Statewide Full Service Partnership Classification System BASED ON STAKEHOLDER FEEDBACK THIS REPORT IS THE MENTAL HEALTH SERVICES OVERSIGHT.

SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future ver2 Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed.

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:

Copyright © 2007, Oracle. All rights reserved. Using Document Management and Collaboration Appendix B.

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

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

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.

Privacy & Proxy Services Accreditation Issues PDP WG Graeme Bunton, Vice Chair | ICANN-52 | February 2015.

Test environments serving device certification Group Name: WG6 (TST) Source: Denis Chabot, Sierra Wireless,

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

SCFAH r2 Title: “Ad-Hoc Recommendation to SC on 3GPP2 Future” – Working Draft Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.

Status summary of the ad-hoc discussions 29th of June 2012 oneM2M call.

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

Feedbacks on oneM2M certification Group Name: TP Source: JaeSeung Song KETI, TST WG Chair Meeting Date: Agenda Item:

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

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

TST WG Status Report to TP #21 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP21, Item.

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

Discussion points for 2 nd Interop Event Group Name: TST WG Source: Keebum Kim, TTA, Meeting Date: TP#22.

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:

2 nd oneM2M Interoperability Event Prof. Song JaeSeung (KETI, TST WG Chair) TST Introduction-to-2 nd -interop-event.

Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, Meeting Date: Agenda.

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

TST TTCN-3_development_plan TTCN-3 development plan Group Name: TST WG Source: Easy Global Market (EGM) Meeting Date:

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.

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

App-ID Ad-Hoc Technical Issues TP AppID R02

Issues on TST #28 (Overview)

Process for SW Development

WPM ad-hoc group report TP#25

MINISTRY OF ECONOMY AND FINANCE

ETSI MTS#76 Meeting 23-Jan-2019

Presentation transcript:

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

Action point 1 Test environment. The certification for the various entities may include both testing at a test house / using 3 rd party test equipment, some sort of ‘online test-it-your-self’ and test fest/Field trials, etc. The TST group is requested to describe the current thinking and input proposals to the SC CT strategy ad hoc group. Volunteers? © 2014 oneM2M Partners 2

Action point 2 Testing language. Given the various test environments, the test cases should be divided into the categories. The format should be set up accordingly to category. E.g. the test cases for simulation equipment should be implemented in TTCN. Can we identify sources for TTCN? In another word, who will develop TTCN-3 code for oneM2M test cases? Can TST have consensus on TTCN-3 as the testing description language? Who could be the source for this? © 2014 oneM2M Partners 3

Action point 3 The TP TST will need to define a unique way to identify mandatory test cases for a certain device / SW module based on implemented functionality. TP (or SC?) will need to discuss ‘mandatory features’ based on a classified product. This is related to a contribution, ‘TST product classification’. Volunteers to proceed this? © 2014 oneM2M Partners 4

Action point 4 Release strategy. It is very likely that updates and bug fixes will be occur frequently (at least in the beginning). TST should discuss if e.g. a quarterly release of test cases and TTCN is appropriate. During implementation of oneM2M devices/modules, the vendors will not be able to update their SW after a certain stage of the development. One default proposal is for vendors during certification, to references a version no older than 3 months (110 days from the final day of certification). © 2014 oneM2M Partners 5

Information Note that the SC Certification and Test Strategy ad hoc group will meet on Jan 28 th and discuss strategies further. Solid input from the TP TST group would be vital for progress. © 2014 oneM2M Partners 6