ETSI's Bug Tracker - Part 04: TTCN-3 Operational Semantics
View Issue Details
0000373Part 04: TTCN-3 Operational SemanticsTechnicalpublic22-11-2006 16:0712-12-2008 11:41
Stephan Schulz 
 
highminoralways
closedfixed 
v2.2.1 (published 2003-02) 
v3.1.1 (published 2005-06)v3.1.1 (published 2005-06) 
$9.49, $9.50
dr. György Réthy, Ericsson
0000373: Clarification of stop execute in operational semantics
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.
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.
No tags attached.
Issue History
22-11-2006 16:07Stephan SchulzNew Issue
22-11-2006 16:07Stephan SchulzClause Reference(s) => $9.49, $9.50
22-11-2006 16:07Stephan SchulzSource (company - Author) => dr. György Réthy, Ericsson
22-11-2006 16:08Stephan SchulzStatusnew => closed
22-11-2006 16:08Stephan SchulzResolutionopen => fixed
22-11-2006 16:08Stephan SchulzFixed in Version => Edition 3.1.1
12-12-2008 11:41Ina SchieferdeckerTarget Version => Edition 3.1.1
12-12-2008 11:41Ina SchieferdeckerDescription Updated

There are no notes attached to this issue.