ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0003039 | Part 01: TTCN-3 Core Language | Clarification | public | 17-03-2008 09:35 | 09-05-2008 11:53

Reporter | Thomas DeiÃŸ |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | major | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v3.4.1 (published 2008-09) | Fixed in Version | v3.4.1 (published 2008-09) |
Clause Reference(s) | part 1, part4
Source (company - Author) | Nokia Siemens Networks - Thomas DeiÃŸ

Summary | 0003039: Unclear semantics of any/all port

Description

In case that the actual test component is an extension of the runs on clause of the behaviour statement containing an any/all port operation, it is not clear whether the ports in the runs on clause or those of the actual test component shall be considered.
The operational semantics refers in this case to a part of the state that is defined on the module level, i.e. global for the whole test case.
The semantics needs to be checked and defined clearly.

Steps To Reproduce |

Additional Information

In part 1) this question is not touched. In clause 22.2.2 it is simply
stated:
Receive on any port
To receive a message on any port, use the any port keywords.
The operational semantics (part 4) explains the use of 'any port.receive' by refering to ALL-PORT-STATES, which is a global list of ports. In this case this is actually global per test case, not per module! At least this is my understanding. I assume that the intention is that this should be global per test component, but this is an assumption.

Tags | No tags attached.
Relationships |
Attached Files | CR-3039-Clearification-Any-All-Port.doc (131,584) 23-04-2008 15:19 http://oldforge.etsi.org/mantis/file_download.php?file_id=1440&type=bug CR-3039-Corrections-to-part-4-related-to-the-use-of-any-and-all-port.doc (700,416) 27-04-2008 14:33 http://oldforge.etsi.org/mantis/file_download.php?file_id=1467&type=bug

Issue History
Date Modified | Username | Field | Change
17-03-2008 09:35 | Thomas DeiÃŸ | New Issue |
17-03-2008 09:35 | Thomas DeiÃŸ | Status | new => assigned
17-03-2008 09:35 | Thomas DeiÃŸ | Assigned To | => Jens Grabowski
17-03-2008 09:35 | Thomas DeiÃŸ | Clause Reference(s) | => part 1, part4
17-03-2008 09:35 | Thomas DeiÃŸ | Source (company - Author) | => Nokia Siemens Networks - Thomas DeiÃŸ
22-04-2008 18:10 | Jens Grabowski | Note Added: 0005506 |
23-04-2008 11:02 | Jens Grabowski | Note Added: 0005512 |
23-04-2008 15:19 | Jens Grabowski | Note Added: 0005520 |
23-04-2008 15:19 | Jens Grabowski | File Added: CR-3039-Clearification-Any-All-Port.doc |
23-04-2008 15:21 | Jens Grabowski | Assigned To | Jens Grabowski => Gyorgy Rethy
23-04-2008 18:49 | Gyorgy Rethy | Note Added: 0005539 |
23-04-2008 18:49 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Jens Grabowski
24-04-2008 09:23 | Jens Grabowski | Note Added: 0005547 |
27-04-2008 14:32 | Jens Grabowski | Note Deleted: 0005547 |
27-04-2008 14:33 | Jens Grabowski | File Added: CR-3039-Corrections-to-part-4-related-to-the-use-of-any-and-all-port.doc |
27-04-2008 14:35 | Jens Grabowski | Note Added: 0005584 |
27-04-2008 14:37 | Jens Grabowski | Assigned To | Jens Grabowski => Ina Schieferdecker
27-04-2008 14:37 | Jens Grabowski | Status | assigned => resolved
27-04-2008 14:37 | Jens Grabowski | Resolution | open => fixed
09-05-2008 11:50 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
09-05-2008 11:53 | Ina Schieferdecker | Status | resolved => closed
09-05-2008 11:53 | Ina Schieferdecker | Fixed in Version | => Edition 3.4.1 (not yet published)
09-05-2008 11:53 | Ina Schieferdecker | Target Version | Edition 4.1.1 (not yet published) => Edition 3.4.1 (not yet published)

Notes

(0005506)
Jens Grabowski
22-04-2008 18:10

In the operational semantics ports are owned by a component. Each time when a new component is created, all ports specified by the component type are instantiated.
Afterwards, the operational semantics does not care about the runs-on type, because the consistency of runs-on type and type of the created component can be checked by other means than the operational semantics.
The operational semantics assumes that any port and all port are related to all ports of a component independent of whether they are known via a runs-on clause of a test case, function or altstep or not.
This is in line with the latest changes to timers and the handling of defaults.
This meaning has to be clearified in part 1 of the standard.

(0005512)
Jens Grabowski
23-04-2008 11:02

Disconnect and unmap operations have to be added in Table 21.

(0005520)
Jens Grabowski
23-04-2008 15:19

Find proposal enclosed. Instead of adding a note everywhere, I propose to add only one note to clause 22.6.

(0005539)
Gyorgy Rethy
23-04-2008 18:49

OK with me.

(0005584)
Jens Grabowski
27-04-2008 14:35

This CR has also been used for corrections in Part 4 related to the use of any and all for port and communication operations. The halt operation is not covered, because there is another CR on introducing the halt operation into the operational semantics.