K.J.Turner. Validating Architectural Feature Descriptions Using LOTOS. In: K. Kimbler and L.G. Bouma (eds.) Feature Interactions in Telecommunications and Software Systems V, IOS Press (1998) 247-261.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... Feature integration [28] uses model checking for validation of features properties; incremental integration validation [15] uses the synchronous model Lustre and a testing tool for validation of feature properties; modular description of features and static detection of feature interaction [31]are mainly based on an architectural approach founded on LOTOS; the state based approach for defining and detecting feature interactions [25,33,17] the relational approach for defining and detecting feature interactions [16] and the logical approach for defining and detecting feature interactions ....

K. Turner. Validating Architectural Feature Descriptions using LOTOS. In K. Kimbler and W. Bouma, editors, Feature Interaction Workshop. IOS Press, 1998. In [22].

....Language Of Temporal Ordering Specification (LOTOS) 26] in our case, and formal V V techniques. LOTOS has been used for years for the specification and validation of telephony systems ( 7] 19] 20] 23] and for the detection of interactions between telephony features ( 21] 22] 31] 32] 38] 39] 40][41]) Research is still ongoing as to its application to real size problems. Use cases were utilized for the analysis of interactions in [33] More recently, UCMs have also been used to tackle the problems of feature interactions and resolution of conflicts in multi agent systems ....

Turner, K.J. (1998) "Validating Architectural Feature Descriptions using LOTOS". In: K. Kimbler and W. Bouma (eds.), Fifth International Workshop on Feature Interactions in Telecommunications Software Systems,

....paths is just manageable. Conference Calling, for example, has 23 significant paths. Validation scenarios are generated to characterise the expected behaviour of services in isolation. The scenarios can then be encoded using the ANTEST (ANISE Test) language developed by the author for ANISE [11]. Briefly, ANTEST is a flexible validation language that expresses tests in terms of user visible behaviour. Acceptance tests (behaviour must happen) and rejection tests (behaviour must not happen) can be written. Tests may have sequential or concurrent behaviour. Alternatives are permitted, and ....

K. J. Turner. Validating architectural feature descriptions using LOTOS. In K. Kimbler and W. Bouma, editors, Proc. 5th. Feature Interactions in Telecommunications and Software Systems, pages 247--261, Amsterdam, Netherlands, Sept. 1998. IOS Press.

....analysing and implementing services. It is not in itself an approach for detecting feature interactions. Rather it supports other detection techniques. LOTOS and SDL, for example, have been used in several approaches to detecting interactions. Among these the author s own approach is applicable [16], but so are a number of others like [4, 6] CRESS is also a front end for implementing features. It is possible to translate LOTOS and SDL to implementation languages such as C, thus realising features. However the CRESS tools also support more direct implementation through SIP CPL, SIP CGI and ....

....Call Back, Call Forwarding (several varieties) Call Screening (several varieties) Camp On Busy and Return Call. As noted earlier, CRESS is a front end for analysing and implementing features. Feature interactions are detected using separate techniques. For example, the author s approach in [16] is applicable to SIP. This considers an interaction to have occurred if a feature s behaviour changes in the presence of other features. Each feature is characterised by use case scenarios derived from automatic simulation of the feature description in CRESS. The scenarios are represented as ....

K. J. Turner. Validating architectural feature descriptions using LOTOS. In K. Kimbler and W. Bouma, editors, Proc. 5th. Feature Interactions in Telecommunications and Software Systems, pages 247--261, Amsterdam, Netherlands, Sept. 1998. IOS Press.

....15] have been devised to allow features to be treated as building blocks. In some approaches, the architectural descriptions are translated to formal specifications that permit further analysis. For example, 2] describes use case maps for telephony features that are hand translated into LOTOS. [12, 13] and other papers illustrate the author s work on ANISE (Architectural Notions in Service Engineering) ANISE builds features and services in a hierarchical fashion, and then translates them to LOTOS for simulation and interaction analysis. CRESS intentionally separates the representation of ....

....2 stops ringing for 3 ) User Disconnect 1 2 ( 1 is told 2 has hung up ) User OnHook 1 ( 1 hangs up ) Validation scenarios like these characterise the expected behaviour of features of isolation. The scenarios can then be encoded using the ANTEST (ANISE Test) language developed for ANISE [13]. Briefly, ANTEST is a flexible validation language that expresses tests in terms 14 of user visible behaviour. Acceptance tests (behaviour must happen) and rejection tests (behaviour must not happen) can be written. Tests may have sequential or concurrent behaviour. Alternatives are permitted, ....

K. J. Turner. Validating architectural feature descriptions using LOTOS. In K. Kimbler and W. Bouma, editors, Proc. 5th. Feature Interactions in Telecommunications and Software Systems, pages 247--261, Amsterdam, Netherlands, Sept. 1998. IOS Press.

....deal with other kinds of services, and not just those in telecommunications. There is insu#cient space here to describe Anise and Cress in detail; see the referenced papers for more information. Structuring Telecommunications Features 3 2 ANISE Anise (Architectural Notions In Service Engineering [14 17,19]) constructs services through progressive combination of simpler behaviours. In the Anise approach, there is no distinction between the simplest behaviours and the most complex services. All are termed features , though this does not match the normal usage of the word so well. However the ....

Kenneth J. Turner. Validating architectural feature descriptions using Lotos. In Kristofer Kimbler and Wiet Bouma, editors, Proc. 5th. Feature Interactions in Telecommunications and Software Systems, pages 247--261, Amsterdam, Netherlands, September 1998. IOS Press.

....Basic Call are potential suspects for interaction. This does not definitely indicate interaction, but experience of using ANISE [TUR 98a] suggests that such overlaps are very often true interaction problems. To discover feature interaction requires rigorous evaluation of features in combination. TUR 98b] reports the next stage in developing ANISE: the rigorous analysis (simulation) of features. In isolation, the desired characteristics of a feature can be confirmed. When features are combined, their joint behaviour can be checked for deviations (interactions) from their individual behaviours. ....

....The idea of use cases [JAC 92] inspired the language ANTEST (ANISE Test) that allows features to be validated individually or together. Although ANTEST supports feature validation rather than verification, this was a pragmatic choice that reflects current industrial practice. TUR 97a, TUR 98a, TUR 98b] focus on architectural and telecommunications oriented aspects of ANISE. The present paper looks at the detailed mechanisms that 5 support ANISE, and consolidates the results of these papers. The overall approach is illustrated in section 2, that shows typical feature descriptions and how they ....

[Article contains additional citation context not shown here]

TURNER K. J., "Validating Architectural Feature Descriptions using LOTOS", in: Proc. 5th. Feature Interactions in Telecommunications and Software Systems (ed. by KIM- BLER K., BOUMA W.), pp. 247--261, IOS Press, Amsterdam, Netherlands, September 1998.

No context found.

K.J.Turner. Validating Architectural Feature Descriptions Using LOTOS. In: K. Kimbler and L.G. Bouma (eds.) Feature Interactions in Telecommunications and Software Systems V, IOS Press (1998) 247-261.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC