Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0007380

Part-1 Metamodel

[TDL] Clarification

public

04-02-2016 14:02

13-03-2016 19:54

Reporter

Philip Makedonski

Assigned To

Philip Makedonski

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

[TDL] Part-1 V1.2.1

Target Version

[TDL] Part-1 V1.3.1

Fixed in Version

Summary

0007380: Variable use in TimeConstraints

Description

Currently one of the constraints under TimeConstraints states

Use of local variables only
The expression given in the 'DataUse' specification shall contain only 'Variable's that are local to the 'AtomicBehaviour' that contains this time constraint. That is, all 'Variable's shall be referenced in the 'ComponentInstance' that executes the 'AtomicBehaviour'.

What is the correct interpretation of this statement?

There are AtomicBehaviours that are global (VerdictAssignment, Assertion, ActionReference, InlineAction, to name a few). Which Variables can be used in time constraints on such AtomitcBehaviours?

Tags

No tags attached.

Attached Files

Relationships

Notes
(0013834) Philip Makedonski (manager) 15-02-2016 12:58	It concerns Interactions and ActionBehaviours only, where the relevant component instances can be identified via the source and target gates of the Interaction, and the component instance of the ActionBehaviour respectively.

(0013888) Andreas Ulrich (manager) 13-03-2016 19:54	Just to let you know: The reason for this constraint is that the time constraint shall be evaluated using local information of a component instance only. That is, variables inside this time constraint shall be local to one component instance. Without this constraint, a coordination mechanism between involved component instances would be needed to exchange information about local variable values.

Issue History
Date Modified	Username	Field	Change
04-02-2016 14:02	Philip Makedonski	New Issue
04-02-2016 14:02	Philip Makedonski	Status	new => assigned
04-02-2016 14:02	Philip Makedonski	Assigned To	=> Andreas Ulrich
15-02-2016 12:57	Philip Makedonski	Assigned To	Andreas Ulrich => Philip Makedonski
15-02-2016 12:58	Philip Makedonski	Note Added: 0013834
15-02-2016 12:58	Philip Makedonski	Status	assigned => resolved
15-02-2016 12:58	Philip Makedonski	Resolution	open => fixed
13-03-2016 19:54	Andreas Ulrich	Note Added: 0013888

MantisBT 1.2.14 [^]