1 / 9

TC MTS#41 Sophia Antipolis, Oct 11-13 2005 STF276 Status

TC MTS#41 Sophia Antipolis, Oct 11-13 2005 STF276 Status. Anthony Wiles, STF Leader. Resources Used up to 30 th September. Paid effort: 386 days 18 days remaining (total 386+18=404) Which leaves 432-404=28 days not assigned

dahlia-rice
Download Presentation

TC MTS#41 Sophia Antipolis, Oct 11-13 2005 STF276 Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TC MTS#41Sophia Antipolis, Oct 11-13 2005 STF276 Status Anthony Wiles, STF Leader

  2. Resources Used up to 30th September • Paid effort: 386 days • 18 days remaining (total 386+18=404) • Which leaves 432-404=28 days not assigned • 20 days will be allocated to Alexandre Berge (+ equal amount as voluntary effort) • 8 days will be assigned to final ‘maintenance’ • Suggest that maximum amount of travel budget is converted to time (= 3 days) • Total unnassigned time = 11 days • Voluntary expert effort: 124 days • 21 days remaining • Total voluntary effort: 145 days which is 145-110=34 days more than originally promised to the EC

  3. Dissemination • Scott Moseley attended IPv6 Ready Technical meeting at UNH in US (draft travel report is on the server). • Planning/preparation of MTS/3GPP workshop to be held 11th October • Planning/preparation of STF276 participation in IPv6 Plugtest is well advanced (17-21 October)

  4. Conformance Tests • Final draft TSS&TP ready for approval (version 1) according to EC schedule (14.10.2005) • Final total is 404 TPs • Interim draft ATS available for review according to EC schedule • 273 TPs identified as being testable. This final total is lower than the figure anticipated last month. • 273 Test Cases written (i.e., all TCs are now written) • Number of fully validated TCs: 88 • Number of partially validated TCs: 106 (i.e., executed but TTCN-3 corrections yet to be done) • Number of TCs yet to be validated: 79

  5. Conformance Tests: To do • Only the validation will remain after end of October • Probably 79 test cases in total • This will be completed by Alexandre Berge, hopefully by the end of December • Final output of the STF: • 404 TPs • 273 fully validated conformance test cases • Core TTCN-3 Library • Quality issues for the Steering group • TPs are not syntax checked • Why is TP summary field empty? • Have naming and documentation conventions been followed?

  6. Interop Tests • All IOP TPs are written (approx 130) • Interim draft IOP TPs available for review according to EC schedule (actually this is the final draft of the TPs but no explicit TP deliverable required by the EC. The deliverable in February is combined TPs+TDs) • So far 43 TDs have been written. • 17 TDs have been identified as untestable. • (Total left to write 130-43-17=70) • Final figure will depend on whether there are more untestable TPs (likely) • Remaining TDs in progress • No IOP TDs validated (except those done in prototyping phase).

  7. Interop Tests: To do • XF will complete approx 35 of the remaining 70 IOP TDs with his outstanding resource (5 paid + 10 days voluntary) • LV will complete the final 35 TDs before end of project • AB will do some IOP validation (depends on what time he has left after conformance validation) • Final Output of the STF • 130 IOP TPs • Approx 100 TDs • Quality issues for the Steering Group • Not much validation

  8. Other Work • SCOP and Upper Tester complete • but not tested as we are still waiting on implementation of SCOP encoder in test tool • dependant on Testing Tech for that • Not critical but cannot validate all conformance tests without it • Only small number use the UT configuration

  9. Open Issues • No technical issues • But we need assistance with dissemination • quotes from stakeholders • press releases • other possibilities?

More Related