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

ID | Project | Category | View Status | Date Submitted | Last Update
0000385 | Part 01: TTCN-3 Core Language | Technical | public | 23-11-2006 14:22 | 12-03-2008 10:24

Reporter | Stephan Schulz |
Assigned To | Ina Schieferdecker |
Priority | high | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v3.3.2 (published 2008-04) | Fixed in Version | v3.3.2 (published 2008-04) |
Clause Reference(s) | $6, $9, $21
Source (company - Author) | dr. György Réthy, Ericsson

Summary | 0000385: Special types not defined

Description

Special configuration types and the default are just mentioned but not specified in $6. While the nature of port, component and default types can be made out from other parts of the standard, there are several ambiguities regarding the address type.
Is it a user-defined type with a pre-determined name or a built-in type with user-defined value structure? The only clause describing address ($8.6) is contradictory in theis respect: ?address is resolved either by an explicit type definition within the test suite? - so it is importable; ?Explicit SUT addresses shall only be generated inside a TTCN-3 module if the type is defined inside the module.? ? a built-in-like behaviour, though the bnf allows aliasing and hence importing. ?If the type is not defined inside the module, explicit SUT addresses shall only be passed in as parameters or be received in message fields or as parameters of remote procedure calls.).? ? as parameters to templates?
In the former case the address type is importable (directly with the name ?address? and any name alias) while in the second case only name aliases are importable but not the address type definition itself. In both cases several address types may exist in a test suite (in some cases shall exist to be able to address different entities).
In a port type definition all message types and procedure signatures shall be listed but the allowed address types are not mentioned.

Steps To Reproduce |

Additional Information

Add the new clause below:
?6.8 Special configuration types and the default type
6.8.1 The address type
The address type is a special user defined type for use with port operations to address SUT entities. The actual data representation of address is resolved either by an explicit type definition within the test suite or externally by the test system (i.e. the address type is left as an open type within the TTCN-3 specification). This allows abstract test cases to be specified independently of any real address mechanism specific to the SUT. In addition, the special value null is available to indicate an undefined address, e.g. for the initialization of variables of the address type.
EXAMPLE:
// Associates the type integer to the open type address
type integer address;
:
// new address variable initialized with null
var address MySUTentity := null;
:
6.8.2 Port type
<to be completed>
6.8.3 Component type
<to be completed>
6.8.4 The default type
<to be completed>
8.6 Addressing entities inside the SUT
An SUT may consist of several entities which have to be addressed individually. When used with to, from and sender the address data type shall only be used in receive and send operations of ports mapped to test system interface.
Explicit SUT addresses shall only be generated inside a TTCN-3 module if the type is defined inside the module. If the type is not defined inside the module, explicit SUT addresses shall only be passed in as parameters or be received in message fields or as parameters of remote procedure calls.
EXAMPLE:
// receiving an address value and assigning it to variable MySUTentity
PCO.receive(address:*) -> value MySUTentity;
:
// usage of the received address for sending template MyResult
PCO.send(MyResult) to MySUTentity;
:
// usage of the received address for receiving a confirmation template
PCO.receive(MyConfirmation) from MySUTentity;

Tags | No tags attached.
Relationships |
Attached Files | CR_385.doc (1,916,416) 25-10-2007 09:50 http://oldforge.etsi.org/mantis/file_download.php?file_id=1072&type=bug

Issue History
Date Modified | Username | Field | Change
23-11-2006 14:22 | Stephan Schulz | New Issue |
23-11-2006 14:22 | Stephan Schulz | Clause Reference(s) | => $6
23-11-2006 14:22 | Stephan Schulz | Source (company - Author) | => dr. György Réthy, Ericsson
23-11-2006 14:23 | Stephan Schulz | Status | new => assigned
23-11-2006 14:23 | Stephan Schulz | Assigned To | => Jens Grabowski
15-10-2007 16:49 | Ina Schieferdecker | Assigned To | Jens Grabowski => developer_u
17-10-2007 12:41 | user10 | Assigned To | developer_u => Thomas DeiÃŸ
18-10-2007 12:15 | Ina Schieferdecker | Target Version | => Edition 3.3.1 (not yet published)
18-10-2007 12:15 | Ina Schieferdecker | Description Updated |
18-10-2007 12:15 | Ina Schieferdecker | Additional Information Updated |
25-10-2007 09:50 | Thomas DeiÃŸ | File Added: CR_385.doc |
25-10-2007 09:53 | Thomas DeiÃŸ | Clause Reference(s) | $6 => $6, $9, $21
25-10-2007 09:53 | Thomas DeiÃŸ | Note Added: 0003792 |
25-10-2007 09:53 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Gyorgy Rethy
25-10-2007 09:53 | Thomas DeiÃŸ | Resolution | open => fixed
05-12-2007 15:37 | Ina Schieferdecker | Assigned To | Gyorgy Rethy => Ina Schieferdecker
05-12-2007 15:37 | Ina Schieferdecker | Status | assigned => resolved
05-12-2007 18:15 | Ina Schieferdecker | Status | resolved => closed
05-12-2007 18:15 | Ina Schieferdecker | Fixed in Version | => Edition 3.3.1 (not yet published)
12-03-2008 10:22 | user10 | Fixed in Version | Edition 3.3.1 --will not be published, see 3.3.2 => Edition 3.3.2 (not yet published)
12-03-2008 10:24 | user10 | Target Version | Edition 3.3.1 --will not be published, see 3.3.2 => Edition 3.3.2 (not yet published)

Notes

(0003792)
Thomas DeiÃŸ
25-10-2007 09:53

Text on type definition moved to clause 6 (from clauses 9 and 21). Remaining text in clause 9 polished a little bit. No further changes made. Especially, the restrictions on connections (clause 9: structural restrictions, clause 21: compatibility of port types) have not been merged.