| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000373 | Part 04: TTCN-3 Operational Semantics | Technical | public | 22-11-2006 16:07 | 12-12-2008 11:41 |
|
| Reporter | Stephan Schulz | |
| Assigned To | | |
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | v2.2.1 (published 2003-02) | |
| Target Version | v3.1.1 (published 2005-06) | Fixed in Version | v3.1.1 (published 2005-06) | |
|
| Summary | 0000373: Clarification of stop execute in operational semantics |
| Description | Terms �stop component� and �stop execution� are not clarified (neither in the core nor in the OS). They are implicitly distinguished by the existence of a component reference in the statement. However, this is a pure syntactical matter and should not have any effect on the semantics (in the accompanying CR357 �Problems in the stop component operation in the operational semantics� a simple replacement stop -> self.stop is proposed for test cases, functions and altsteps).
As the result currently stopping a test component is handled both by $9.49 and by $9.50 that is an unnecessary and disturbing duplication.
|
| Additional Information | Use the following concept:
- stop component means to stop the MTC (and as the consequence finishing the test case), a PTC or all PTCs (including both stopping itself and stopping by an another component)
- stop execution means stopping the control part (namely execution of the test session).
Once the above is accepted, subclause $9.50 can be considerably simplified as below.
|
| Tags | No tags attached. |
|
| Clause Reference(s) | $9.49, $9.50 |
| Source (company - Author) | dr. György Réthy, Ericsson |
|
| Attached Files | |
|
Relationships 
Relationships 