1. 40TD11 STF276 – Status (including TPLan and T3Doc)
MTS#40
Berlin
15-17 March

2. STF276 Status (1) Started work 3 January
Project website:
Two SG meetings (reports on STF276 Docbox)
January
February
1st Progress Report input to this meeting (40TD09)
Endorsement by SG
Approval by TC MTS

3. STF276 Status (2) Experts/ContractsV S 1 AF
Annie Floch 20 8 28 2 BG
Basavanna Gowda 15 5 3 CO
César Olvera 10 30 4 DT
Dirk Tepelmann FR
Frédéric Roudaut 6 PK
Péter Krémer 40 12 52 7 PS
Peter Schmitting 35 RC
Ranganai Chaparadza 9
SAM
Scott Moseley 50 SM
Sebastian Mueller 11 SR
Steve Randall SS
Stephan Schulz 13 XF
Xiaoming Fu 60
Total (Experts)
335
143
478
Approx. 25% of resources used to date

4. STF276 Status (3) Main Project Phases
Project divided in 3 phases
1. Prototype
Draft Framework - available
Process validation (including implementation/execution)
IOP validation - completed
Conformance validation – ongoing ties week
2. Main phase
Final Framework - on target for submission to MTS 15. April
Full Requirements Catalogue – on target
IOP TPs/TDs - started
Conformance TPs/ATS
will start (low key) this week
main effort from week 22
Final IPv6 TTCN-3 Library
Interim report (EC)
3. Close down
Dissemination
Final report (EC)
Overview

5. STF276 Status (4) Deliverable Status
Deliverable
Due date
% Done
Status
Task 1
Admin/consultancy
continuous
On target
WP1
Task 2 D1
Framework v2
15/04/2005
85% D2
Baseline library
70%
WP2
Task 3 D3
Requirement catalogue
15/04/ /07/ /10/2005
10%
Task 4 D4
Core library
15/07/ /10/ /02/2006 0%
Not started
Conf. TSS&TP
15/07/ /10/2005 D5
Conf. ATS (TTCN-3)
14/10/ /02/2005
Task 5 D7
Interop. ATS (TD)
15/04/ /09/ /10/ /02/2006
Started
Task 6
Testbed
01/03/ /05/2005
50%

6. TP Lan Decision on to use or not to use Divided opinions
For: precise, checkable, tool processable
Against: tabular format concise enough, not so readable, why bother
Workaround: transformations
Will be used for interop TPs
Decision on conformance still open (PS )

7. TP Lan Keywords
Keywords
Main constructs
Grammar

8. TP Lan Examples
IOP
Conformance
Alternative conformance

9. TTCN-3 Comment Documentation Rationale
Documentation tags embedded in TTCN-3 comments
Like Java Doc
Enables automatic generation of, for example, HTML-based test suite documentation
For example /*
@author John Smith */
Need standardised tags
Part of TTCN-3 standard rather than IPv6 Framework?
And guidelines on use
Part of IPv6 Framework

10. TTCN-3 Comment Documentation Standard Tags
Description
@author
Name of the individual author or authoring organisation.
@desc
This is probably the most import of all the tags. It should be used to describe the purpose of individual TTCN-3 constructions. The description should be concise yet informative and describe the function and use of the construct.
@remark
This tag may be used to add additional information, such as highlighting a particular feature or aspect not covered in the description. Should be used sparingly.
@img
This tag may be used to add images to an element description.
@see
This tag may be used to add references to other constructions in the same TTCN-3 module or in other TTCN-3 modules.
@url
This tag should be used to make (possibly multiple) references to external files or web pages.
@return
This tag should only be used with functions. It is used to provide additional information on the value returned by the given function
@param
This tag is used to document the parameters of parameterized module elements.
@version
This tag is used to state the version of a particular piece of TTCN-3 code.

11. TTCN-3 Comment Documentation Where to use
Comment tags may be used in any TTCN-3 language construct, however, it is recommended that at a minimum the following constructs should be tagged:
Module parameter;
Import statement;
Constant declaration;
Type definition;
Signature definition;
Function definition;
Testcase definition;
Altstep definition;
Group definition;
Control part.

12. TTCN-3 Comment Documentation When to use
Recommended that documentation tags are used as follows:
each TTCN-3 module should tags;
all other language elements should use tag
should not be taken to the extreme (e.g., not every constant);
major constructs such as test cases, functions, templates etc. should have a comprehensive description
where relevant tag may also be used;
Parameterised constructions such as functions and templates should use tags.;
when used in an integrated framework (such as STF276) tag may be used to link to relevant documentation such as Test Purposes or original requirements;
use of tags are at the discretion of the user.