Скачать презентацию Discussion on Certification Group Name TST WG Source Скачать презентацию Discussion on Certification Group Name TST WG Source

f7c069449a75386690e7ccd8d35eea38.ppt

  • Количество слайдов: 6

Discussion on Certification Group Name: TST WG Source: Jae. Seung Song, WG 6 Chair, Discussion on Certification Group Name: TST WG Source: Jae. Seung Song, WG 6 Chair, jssong@sejong. ac. kr Meeting Date: TST #21

Action point 1 • Test environment. The certification for the various entities may include 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 one. M 2 M Partners 2

Action point 2 • Testing language. Given the various test environments, the test cases 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 one. M 2 M test cases? • Can TST have consensus on TTCN-3 as the testing description language? • Who could be the source for this? © 2014 one. M 2 M Partners 3

Action point 3 • The TP TST will need to define a unique way 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-20160022 -product classification’. • Volunteers to proceed this? © 2014 one. M 2 M Partners 4

Action point 4 • Release strategy. It is very likely that updates and bug 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 one. M 2 M 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 one. M 2 M Partners 5

Information • Note that the SC Certification and Test Strategy ad hoc group will 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 one. M 2 M Partners 6