K. J. Turner. Formalising the CHISEL feature notation. In M. H. Calder and E. H. Magill, editors, Proc. 6th. Feature Interactions in Telecommunications and Software Systems, pages 241--256, Amsterdam, Netherlands, May 2000. IOS Press. 16  Home/Search   Document Details and Download   Summary   Related Articles   Check

....tool. However, the extension relation may also be violated by this approach. Turner presents an approach called CRESS (Chisel Representation Employing Systematic Specification) which defines tightly defined rules for the syntax and static semantics of an enhanced version of Chisel diagrams [76]. This improved notation has formal denotations in both LOTOS and SDL, hence enabling the synthesis of formal models in order to support the rapid creation, specification, analysis and development of features. Although CRESS often represents scenarios as trees (more precisely as directed acyclic ....

Turner, K.J. (2000) "Formalising the Chisel Feature Notation"'. In: Sixth International Workshop on Feature Interactions in Telecommunications and Software Systems (FIW'00), Glasgow, Scotland, UK, May 2000. IOS Press, Amsterdam, 241-256. ftp://ftp.cs.stir.ac.uk/pub/staff/kjt/research/pubs/form-chis.pdf

....view. UCMs can abstract from these events, and UCMs also support advanced concepts such as dynamic stubs, which have no equivalent in the Chisel notation. Note that similar to the UCM Lotos translation mentioned in Section 3. 3, a Chisel Lotos mapping has been defined and automated by Turner [33]. Petri Nets (PNs) these are abstract machines used to describe system behaviour visually with a directed graph containing two types of nodes: places and transitions. Basic PNs su#er from a state explosion problem when complex problems are addressed. Various extensions for data types and ....

Turner, K. J.: "Formalising the Chisel Feature Notation". In: Sixth International Workshop on Feature Interactions in Telecommunications and Software Systems (FIW'00), Glasgow, Scotland, UK, May 2000. IOS Press, Amsterdam, 241--256.

....discusses a development of CRESS (CHISEL Representation Employing Systematic Specification) CRESS is considerably evolved from its basis in CHISEL, which was developed by BellCore [1] for telephony services. CRESS is a notation and set of tools for graphical description and analysis of services [12]. It is graphical in order to improve its attractiveness to an industrial audience. CRESS has previously been used to model and analyse IN (Intelligent Network) services [12] Adaptation of CRESS for SIP has been fairly straightforward, though different service models have been required. Unlike ....

....BellCore [1] for telephony services. CRESS is a notation and set of tools for graphical description and analysis of services [12] It is graphical in order to improve its attractiveness to an industrial audience. CRESS has previously been used to model and analyse IN (Intelligent Network) services [12]. Adaptation of CRESS for SIP has been fairly straightforward, though different service models have been required. Unlike CHISEL, CRESS allows modular service descriptions and permits much more flexible combination of services. CRESS also has plug in application domains, so it can be used ....

K. J. Turner. Formalising the CHISEL feature notation. In M. H. Calder and E. H. Magill, editors, Proc. 6th. Feature Interactions in Telecommunications and Software Systems, pages 241--256, Amsterdam, Netherlands, May 2000. IOS Press. 16

....paper is to demonstrate that CRESS is a flexible notation of value in a number of domains. As background, Section 2 summarises the CRESS diagram format. Of necessity, the description is brief and condensed. Refer back to it when studying the diagrams that appear later. More on CRESS appears in [17, 18]. To complement previous CRESS work on IN services [17] Sections 3 and 4 show how CRESS can be applied to SIP and VoiceXML. It will be seen that SIP has affinities with IN telephony, but that VoiceXML supports very different kind of services. Nonetheless, the same notation can be used in all ....

....of value in a number of domains. As background, Section 2 summarises the CRESS diagram format. Of necessity, the description is brief and condensed. Refer back to it when studying the diagrams that appear later. More on CRESS appears in [17, 18] To complement previous CRESS work on IN services [17], Sections 3 and 4 show how CRESS can be applied to SIP and VoiceXML. It will be seen that SIP has affinities with IN telephony, but that VoiceXML supports very different kind of services. Nonetheless, the same notation can be used in all three domains for various purposes: representing services ....

K. J. Turner. Formalising the CHISEL feature notation. In M. H. Calder and E. H. Magill, editors, Proc. 6th. Feature Interactions in Telecommunications and Software Systems, pages 241--256, Amsterdam, Netherlands, May 2000. IOS Press.

....validated in the field of telephony. The approach is neutral with respect to the target language, and so can be used as a front end for any formally based approach. The toolset is portable and can be used on a range of platforms. 1. 2 Previous Work The initial version of CRESS was described in [14]. The emphasis in that paper was on formalising CHISEL diagrams. The main limitation was that feature descriptions were not very modular. Features could be described and analysed individually, but their automated combination was severely limited. The work reported in the present paper has ....

....interaction since this is handled by other tools that take a specification as the starting point. As an example, the University of Ottawa [4] have developed analysis techniques that can be used with the output of CRESS. In fact the Ottawa team wrote their specifications by hand, but as reported in [14] the LOTOS generated CRESS is more compact and more readable. And of course, automatically generated specifications are much easier to maintain through changes to the feature diagrams. 2 2 CRESS Notation This section provides a brief overview of the CRESS notation. CRESS is illustrated with ....

K. J. Turner. Formalising the CHISEL feature notation. In M. H. Calder and E. H. Magill, editors, Proc. 6th. Feature Interactions in Telecommunications and Software Systems, pages 241--256, Amsterdam, Netherlands, May 2000. IOS Press.

....practice in defining features, and because it requires simple structuring mechanisms. However the rules for Chisel are relatively informal. The author has therefore tightened up and extended the definition of Chisel. The result is Cress (Chisel Representation Employing Structured Specifications [18]) a feature notation backwards compatible with Chisel, but with a formalised interpretation using Lotos and SDL (Specification and Description Language [9] Cress starts with even simpler behaviours than Anise: the isolated events that describe communication between a user and the network. ....

Kenneth J. Turner. Formalising the Chisel feature notation. In Mu#y H. Calder and Evan H. Magill, editors, Proc. 6th. Feature Interactions in Telecommunications and Software Systems, pages 241--256, Amsterdam, Netherlands, May 2000. IOS Press.

....(e.g. BER 97, BLO 97, DSS 97] AMY 99] proposes an approach for the structuring of features based on use case maps. CHISEL [AHO 98] is another example of a graphically based approach to structuring service specifications. The author has also developed translations to LOTOS (and SDL) for CHISEL [TUR 00] Another class of offline techniques is termed architectural by the author. The emphasis here is on proper structuring of features. Indeed the author feels that a good theory for structuring and specifying features is an essential foundation. If features are defined in an ad hoc manner, it is ....

TURNER K. J., "Formalising the CHISEL Feature Notation", in: Proc. 6th. Feature Interactions in Telecommunications and Software Systems (ed. by CALDER M. H., MA- GILL E. H.), pp. 241--256, IOS Press, Amsterdam, Netherlands, May 2000.

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