| |
ETSI's Bug Tracker |
| Anonymous | Login | Signup for local Mantis account | 02-05-2024 15:04 IST |  |
| Main | My View | View Issues | Change Log | Roadmap | Monitor project |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0007627 | Part-1 Metamodel | [TDL] New Feature | public | 08-03-2017 13:17 | 28-04-2017 16:45 | ||||
| Reporter | Gyorgy Rethy | ||||||||
| Assigned To | Philip Makedonski | ||||||||
| Priority | normal | Severity | major | Reproducibility | have not tried | ||||
| Status | resolved | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | [TDL] Part-1 V1.3.1 | ||||||||
| Target Version | [TDL] Part-1 V1.4.1 | Fixed in Version | [TDL] Part-1 V1.4.1 | ||||||
| Summary | 0007627: Add an attribute to identify that a given system being tested doesn't require global ordering | ||||||||
| Description | In some domains systems may require a global ordering of interactions. In other domains distributed systems are not requiring that events not dependent on each other happen in a strict order, and often this simply cannot be even assured. Telecom systems are typically such. For example, when X number of SIP users, each represented by a component shall register to _different registrars_ (so not to the same one), the order of registration depends on the order of starting the components in a real implementation of the test, the delay between the client and the registrar, etc. Current version of TDL supports only a user friendly description of tests for systems requiring strict ordering. In principle the parallel combined block could be used to specify behavior without the need of global ordering, but it suffers from several problems: - users in these domains are not used to explicitly identify independent ordering of independent events (i.e. when using MSC or UML SD), it may easily be forgotten; - as it should be used in each case of independent orders, it complicates the test descriptions; - when there are more than just a few independent interactions, it makes the description long, inconvenient to create and hard to read; It is proposed to allow test descriptions without global ordering in the language and add a global (i.e. at the level of TD) attribute identifying that a given description doesn't use global ordering. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0014605) Philip Makedonski (manager) 28-04-2017 16:27 |
The realisation of this feature requires the addition of a property to the TestDescription meta class and the extension of its semantics: The 'isLocallyOrdered' property, set to 'false' by default, enables the specification of 'TestDescriptions' that override the assumption of total ordering of all 'Behaviour's. If set to 'true', the default semantics of total ordering of all 'Behaviour's within the 'TestDescription' is changed to local ordering within a 'ComponentInstance' for the 'TestDescription'. Local ordering implies that 'Behaviours' involving different 'ComponentInstance's that do not interact with each other directly or indirectly may occur in any order. The 'Behaviours' for a 'ComponentInstance' shall still occur in the specified order. Under Properties: isLocallyOrdered: Boolean [1] = false If set to 'true', the default semantics of total ordering of all behaviours within the test description is changed to local ordering for the 'TestDescription'. |
|
(0014606) Philip Makedonski (manager) 28-04-2017 16:30 |
Additional consequence is the need for a property indicating the location of combined behaviours in order to enable local ordering of combined behaviours as well. Consequently the semantics of the CominedBehaviour meta class is extended and a corresponding property is added: A 'CombinedBehaviour' may be optionally localised to a 'ComponentInstance' by means of the 'scope' property. In this case the 'CombinedBehaviour' may only contain 'AtomicBehaviours' and other 'CombinedBehaviours' that are specified for the 'ComponentInstance' designated through the 'scope' property. Any 'PeriodicBehaviour's and 'ExceptionalBehaviour's contained in the 'CombinedBehaviour' are by extension also localised to the same 'ComponentInstance'. Under Properties: scope: ComponentInstance [0..1] Reference to a 'ComponentInstance' to which the 'CombinedBehaviour' may be restricted. |
|
(0014607) Philip Makedonski (manager) 28-04-2017 16:32 |
Finally, the semantics of the Assertion meta class and its properties are extended as follows in order to be able to specify locally ordered Assertions: An 'Assertion' may be optionally localised to a 'ComponentInstance' by means of the 'scope' property. This determines where the 'condition' shall be evaluated. Any changes in the test verdict resulting from the evaluation of the 'Assertion' still apply to the whole 'TestDescription'. Under Properties: scope: ComponentInstance [0..1] Reference to a 'ComponentInstance' to which the 'Assertion' may be restricted. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 08-03-2017 13:17 | Gyorgy Rethy | New Issue | |
| 17-04-2017 17:11 | Philip Makedonski | Assigned To | => Philip Makedonski |
| 17-04-2017 17:11 | Philip Makedonski | Status | new => assigned |
| 28-04-2017 16:27 | Philip Makedonski | Note Added: 0014605 | |
| 28-04-2017 16:30 | Philip Makedonski | Note Added: 0014606 | |
| 28-04-2017 16:32 | Philip Makedonski | Note Added: 0014607 | |
| 28-04-2017 16:45 | Philip Makedonski | Status | assigned => resolved |
| 28-04-2017 16:45 | Philip Makedonski | Resolution | open => fixed |
| 28-04-2017 16:45 | Philip Makedonski | Fixed in Version | => [TDL] Part-1 V1.4.1 |
| 28-04-2017 16:45 | Philip Makedonski | Target Version | => [TDL] Part-1 V1.4.1 |
|
Issue History |
| MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |
 |