Recommendation Z. 100 - Specification and Description Language (SDL), 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....for describing channels, including mechanisms for specifying buffering capacity, and discusses the implications for formal proof of model properties. Section 4 presents revised communication statements, including a mechanism for specifying timeouts, and compares the mechanism with features of SDL [13]. We summarize and draw conclusions in Section 5. 2. SUAVE s Existing Features for Abstract Communication In a previous paper [3] we identified a number of issues influencing our design of communication mechanisms in SUAVE. Basedona consideration of these issues, we chose asynchronous message ....

ITU, Specification and Description Language (SDL). Revised Recommendation Z.100, 1992.

....the switching of the signaling and the data connections (if any) whenever a MT crosses the boundaries of a cell, and the updating of the location of a MT in the CSU hosted DB. 11 CS MMC has been formally specified and simulated using the Specification and Description Lan guage (SDL [19], 20] The corresponding SDL block consists of four processes (Figure 7) From those processes, only the ROUTER process has one instance. The other three processes, namely, Loca tion Update Handler (LUH) Registration Handler (RHC) and Mobility Control Function (MCF) may have N instances, ....

ITU-T Recommendation Z.100, Specification and Description Language (SDL), 1996.

....handle probabilism, concurrency and time. In POOSL, these aspects are inherent to a model and the formal semantics defines how the SHESim and Rotalumis tools manage them [1] Tools of other UML based methods often do not separate simulated or model time from run time. For example, deriving SDL [22] specifications from UML diagrams or approaches based on ROOM [17] relying on tools like ObjectTime or RoseRT suffer from the problem that hard real time behavior cannot be modeled adequately [7] This is because time is not an inherent aspect of SDL and ROOM models. As a consequence, these ....

ITU-T Recommendation Z.100. Specification and Description Language (SDL), November 1999.

....handle probabilism, concurrency and time. In POOSL, these aspects are inherent to a model and the formal semantics defines how the SHESim and Rotalumis tools manage them [1] Tools of other UML based methods often do not separate simulated or model time from run time. For example, deriving SDL [22] specifications from UML diagrams or approaches based on ROOM [17] relying on tools like ObjectTime or RoseRT suffer from the problem that hard real time behaviour can not be modelled adequately [7] This is because time is not an inherent aspect of SDL and ROOM models. As a consequence, these ....

ITU-T Recommendation Z.100. Specification and Description Language (SDL), November 1999. 12

....is an active area of investigation [18] Many other approaches are based on adding performance attributes to behaviour models, with scenario based and state based languages. For instance, Message Sequence Charts (MSCs) 7] can be supplemented with performance information to generate SDL [6] specifications, as suggested by Dulz et al. 5] and by Kerber [11] UML behaviour models [14] can also have such annotations. Khkipuro uses performance oriented UML models (in addition to the design model) to generate performance models [10] whereas Woodside et al. extract performance models ....

ITU-T (2000) Recommendation Z.100, Specification and Description Language (SDL). Geneva.

....by multi process high level synthesis. Using this approach it is possible to perform a fine grain hardware software partitioning where the control flow is performed by software and high performance data operations are performed by hardware. 2 Related Work Translating designs described in SDL [10] to implementation languages was first made for software. The commercially available case tool TAU [16] allows the generation of C and Chill code. The main application area for TAU is the emulation of the SDL system on a host computer. New code generators of the TAU framework also allow the ....

ITU-T. Recommendation Z.100. Specification and Description Language. ITU, 1993.

....protocol as an illustrating example. In the final section, an example is presented that shows how our approach bridges the gap between SDL specifications and the application of different timing analysis techniques. 2. RELATED WORK Several specification languages for reactive systems, e.g. SDL [9] or StateCharts [7] and specification languages for transformative systems, e.g. synchronous data flow [15] or Matlab Simulink [17] exist. Each of these languages is best suited for and thus established in certain application domains, and supported by domainspecific tools. Specialized languages ....

....model distinct process behaviors; mode tags to model process mode correlations; virtual processes and channels to model the system environment, timing constraints and otherwise hidden scheduling dependencies. We will explain these concepts in more detail in Sec. 3.4. 3. 3 Introduction to SDL SDL [9] was originally designed for the specification of protocol automata in communication systems and is now the standard language for this purpose. SDL automata can perform data operations which leads to the extended finite state machine (EFSM) model of computation. An SDL system is structured into ....

ITU. ITU-T. Recommendation Z.100. Specification and Description Language, 1993.

....the complexity inherent in the design and development of real time software. They allow developers to view the system at various levels of abstraction, and simulate running the software on a variety of target hardware RTOS configurations. 3.4. 1 SDL SDL (Specification and Description Language) [ITU93] is a formal and standardized graphical language intended for the description of complex, event driven, real time systems. System structure is captured as hierarchical partitions (called blocks ) behaviour is captured as processes (described 20 using extended finite state machines) running ....

....signals and synchronous remote procedure calls; communications channels (e.g. C1, C2, C3) and signal routes (e.g. R1, R2, R3, R4) must be explicitly documented. 3.4.1. 1 TeleLogic Tau SDL Suite The Telelogic Tau SDL suite [Tel00] supports the specification and design of systems using SDL [ITU93] notation. It consists of a graphical editor and syntax analyzer, a simulator and validator and several optimized code generators (for C C or CHILL [CHI00] on a variety of targets) It also integrates with the Telelogic Tau UML Suite [Tel00] for requirements capture and use case description) ....

ITU-T. Recommendation Z.100: Specification and Description Language (SDL), 3/93.

....be achieved by its components. This difficult engineering problem has been studied by many researchers in the last few decades. Those research efforts have led to the definition of different techniques and methods in the area of modeling and design ( 10] 11] 13] 17] 18] 36] 40] 44] [46], 47] 51] 74] 83] 87] 93] simulation ( 10] 23] 68] verification ( 10] 40] 41] and testing ( 10] 14] 77] In the last decade, the object oriented paradigm has emerged as a leading development technology in the real time system industry. This paradigm allows modeling ....

....definition of traceability relations between the models of RT TROOP, and 5 development of case studies. These contributions are described in the five next sections (section 1.4.1 to section 1.4. 5) Most of the design methodologies used in the real time system industry today, e.g. ROOM [93] SDL [46], StateChart [36] UML [12] aims at producing communicating state machine models from requirements. One of the difficulties faced by designers when using such methodologies lies in the large gap that exists between requirements and communicating state machines. For this reason, scenario based ....

[Article contains additional citation context not shown here]

ITU (1992). Specification and Description Language (SDL'92). Recommendation Z.100. Geneva.

....types of interaction diagrams and state machines. The work of Haugen [39] and Koskimies et al. 51] focuses on the definition of a transition between interaction diagrams and flat state machines. 39] defines a general approach for making the transition between an MSC model [43] and an SDL model [45]. 51] defines a synthesis algorithm that allows for the automatic generation of state machines from a set of scenario diagrams. Leue et al. 58] defines a similar approach for MSC 96 and ROOM hierarchical state machines. Synthesis algorithm can be useful for the generation of test components ....

ITU (1988). Specification and Description Language (SDL). Recommendation Z.100. Geneva.

....of the user before she is permitted to use any of the facilities. This requires the CORBA Security Service. Figure 4 shows the collaboration of agents related to user mobility. 14 5. DESIGN OF UPC 5. 1 SDL Model of UPC We designed UPC in SDL (Specification and Description Language) [12]. SDL is an extended finitestate machine based language developed by ITU T (former CCITT) to specify communication systems. It is well suited to describe process interactions of distributed systems and therefore satisfies our needs in the design of UPC. We used ObjectGEODE, a commercial SDL ....

....number of protocols that are used between objects to provide UPC services, such as the registration protocol used by the user agent to register in a foreign network and to inform the home network of its current location. All these protocols were specified in 23 the formal description language SDL [12] and verified using SDL tools (e.g. ObjectGEODE) We also defined detailed IDL interfaces for all objects in our system and built the objects in our testbed. In addition to implementation, further architectural considerations include: 1) Security the higher degree of openness of this system ....

ITU Z.100 Specification and Description Language (SDL), 1992.

....requirements and between requirements and (parts of) the service model. 2.2 The SOMT method In this section we give a very brief overview of the SOMT method. For details the reader is referred to [3] Basically SOMT combines object oriented analysis (using OMT [7] notation) with SDL based [8] design. The development process according to SOMT is divided into five major activities the results of which are documented in different models. The following activities are distinguished: Requirements Analysis The purpose of this first activity is to get an understanding of the problem domain. ....

ITU-T. Recommendation Z. 100. Specification and Description Language (SDL). 1994.

....based upon a multimedia binding object used to support a configuration of time dependent information producers and consumers realising the so called lip synchronisation algorithm. Index Terms SDL, Validation, Real Time Systems. 1 INTRODUCTION he Specification and Description Language (SDL) [1] is arguably the most successful formal technique used today with widespread usage throughout the software, telecommunications and automotive industries. Part of the reasons for its general adoption are its intuitive graphical notation and excellent tool support. The tool support typically offers ....

....Specifically, the specifier is able to describe temporally dependent behaviour through using: timers, enabling conditions and continuous signals, where the latter two features can be used for timing purposes through referencing the time variable now. With regard to timers, the SDL 2000 standard [1] states that: a timer is an object owned by an agent that causes a timer signal stimulus to occur at a specified time. When an inactive timer is set, a time value is associated with the timer. Provided there is no reset or other setting of this timer before the system time (now) reaches this time ....

ITU-T, Rec. Z.100, Specification and Description Language (SDL), SDL 2000, Geneva Switzerland.

.... Language (SDL 92) and test purpose descriptions with the 1996 version of Message Sequence Charts (MSC 96) as input and produce test suites based on the second edition of the Tree and Tabular Combined Notation (TTCN 2) 14] Meanwhile, the standards of both SDL and MSC have been updated (SDL2000 [16], MSC 2000 [15] and a thoroughly new version of TTCN has been standardized (TTCN 3 [7] In addition, the European Commission has set up the Interval project [21] to prototype an SDL, MSC and TTCN based tool chain for the development and testing of systems with real time constraints. During the ....

....time of occurrence can be constrained, too. An extension to the MSC 2000 standard has been proposed by the Interval consortium to ITU T Study Group 10 in [20] A new symbol is proposed to express periodic occurrence of repetitive events which are folded into a loop. 3. 3 SDL 2000 In SDL 2000 [16], timer declarations are mandatory. As part of the declaration, a constant default duration may be defined. With the set statement, a timer is activated. With the reset statement, a timer is put back to the inactive state. If an active timer expires, a signal with the same name as the timer is put ....

ITU-T, Geneva, Switzerland. Specification and Description Language (SDL), 1999. ITU-T Recommendation Z.100.

....of the activity thread approach, we present a new technique called transition reordering for mapping formal descriptions on activity threads during compilation. Beforehand, we begin with a short overview on the basic features of SDL. 5.1. SDL SDL (Specification and Description Language) [22] is the specification language of the ITU T. It is a widely accepted specification technique for the software design of telecommunication systems. SDL has also successfully been applied for the specification of communication protocols. The development of SDL started in the seventies. The language ....

ITU-T. Z.100: Specification and Description Language (SDL), ITU, 1993.

....dialect of the Specification and Description Language (SDL) a language for the specification of the behavior of telecommunication systems. Lucent based its dialect on an early draft of the international standard, which only slightly differed from the final standard which appeared in 1988 [12]. To limit maintenance and development costs, Lucent Technologies decided long ago to freeze their proprietary SDL dialect. Since adaptations to their SDL tool set were no longer required, knowledge of these tools disappeared gradually. This eventually led to increased development cost of new ....

....perform largely depends on personal taste. An operator suite designed for expressing this kind of grammar transformations and applying them automatically is described in [17] 3.2. SDL grammar re engineering Lucent s proprietary SDL dialect is closely related to the SDL standard known as SDL 88 [12]. It was derived from an early (yet incomplete) draft of this standard. The absence of block constructs in the SDL dialect was the major difference with SDL 88. After SDL 88 many new language constructs have been defined in additional SDL standards of which SDL 2000 is the most recent one. ....

ITU-T recommendation Z.100, specification and description language (SDL), 1988.

....a formal syntax and formal semantics. In most cases, this language is mathematical, but also graphical and tabular languages have been proposed. A formal method allows describing requirements rigorously and allows analyzing them extensively. Examples of formal methods include 2 SCR [HJL96] SDL [ITU93], VDM [Jon90] and Z [Spi92] A requirements model is a set of requirements that is represented using a RSL. It is a formalized statement of requirements. This paper reports on an empirical study aimed at answering two research questions about the defects spotted in informal requirements during ....

....a formal semantics of SCR [HJL96] and developed a CASE tool called SCR [HBGL95] SDL (Specification and Description Language) is standardized by the International Telecommunication Union. It was developed in the late 1960s. Object oriented concepts have been introduced into the version SDL 92 [ITU93]. SDL is considered today a formal description technique. We used the CASE tool ObjectGEODE from Verilog. OCTOPUS [AKZ96] was developed in 1996 by Nokia. It is an object oriented method based on OMT [RBP 91] and Fusion [Col94] for all phases of the development of embedded systems. There is no ....

Recommendation Z.100, Specification and Description Language (SDL). ITU, 1993.

....presents various construction approaches that target the construction of detailed behavior models from some of these scenario notations. These models are usually in the form of automata, UML) statecharts, or formal specification languages such as ITU T s SDL (Specification and Design Language) [43] and ISO s LOTOS (Language Of Temporal Ordering Specification) 39] Such models are usually executable and suitable for validation, verification, and sometimes code generation. Amyot and Eberlein p. 8 3 Construction Approaches 3.1 Why Construction Approaches In the scenario driven ....

ITU-T (2000) Recommendation Z.100, Specification and Description Language (SDL). Geneva.

....between the different entities involved, represented using Message Sequence Charts (MSCs) 19] 2 To appear in SDL 01, c # Springer Verlag, 2001 Finally, Stage 3 aims to provide (informal) specifications of protocols and procedures. Formal specifications are sometimes provided (e.g. in SDL [18]) but overall they still su#er from a low penetration, especially in North America. In such methodologies, scenarios are often used as a means to model system functionality and interactions between the entities such that di#erent stakeholders may understand their general intent as well as ....

ITU-T: Recommendation Z.100, Specification and Description Language (SDL). Geneva (1999)

....a number of protocols that are used between objects to provide UPC services, such as the registration protocol used by the user agent to register in a foreign network and to inform the home network of its current location. All these protocols are specified in the formal description language SDL [13] and verified using SDL tools (e.g. ObjectGEODE) We are also in the process of defining detailed IDL interfaces for all objects in our system and building the objects in our testbed. In addition to implementation, further architectural considerations include: 1) Security the higher degree of ....

ITU Z.100 Specification and Description Language (SDL), 1992.

.... by the VIRES project (Verifying Industrial REactive Systems, Esprit Long Term Research Project No.23498) VERIMAG is a joint laboratory of CNRS, Universit e Joseph Fourier and Institut Nationale Polytechnique de Grenoble the wand (Wireless ATM Network Demonstrator) consortium [WAN96] sdl [IT94] has been chosen as the specification language by the designers and we have used the commercial tool Objectgeode for maintaining the sdl description of the protocol. The if tool set [BFG 99b,BFG 99a] has been used for analysis of the protocol. All specification and verification tools ....

ITU-T. Recommendation Z.100. Specification and Description Language (SDL). 1994.

....phase and later. see Fig. 3 (source: And99] Due to the quite similar concept of the two formal description techniques, the automated generation from UML to SDL and also the possibility of reverse engineering is becoming more and more attractive. The standardization e#orts of the ITU (Z. 100 [Z.199a] and Z.109 [Z.199b] show that this is a point of general interest. In a diploma thesis at the LKN ( Sch00] we have designed a software engineering process that shows the integration of UML and SDL with focus on design and implementation phases. 4.1 The Tool Telelogic Tau 4.0 In our project we ....

ITU-T Recommendation Z.100. Specification and Description Language (SDL). ITU, 1999.

.... was supported by the VIRES project (Verifying Industrial REactive Systems, Esprit Long Term Research Project No.23498) VERIMAG is a research laboratory associated with CNRS, Universit e Joseph Fourier and Institut Nationale Polytechnique de Grenoble Demonstrator) consortium [WAN96] sdl [IT94] has been chosen as the specification language by the designers and we have used the commercial tool Objectgeode for maintaining the sdl description of the protocol. The if tool set [BFG 99b,BFG 99a] has been used for analysis of the protocol. All specification and verification tools of ....

ITU-T. Recommendation Z.100. Specification and Description Language (SDL). 1994.

....the intra process as well as inter process control and data dependencies in a specification of a distributed system given in SDL. The model facilitates the generation of tests through the application of controlflow as well as data flow oriented test selection criteria. 1 INTRODUCTION In SDL [ITU92, Ell97], a distributed system is viewed as a collection of blocks and processes communicating with each other by exchanging signals through channels and signal routes. The externally observable behavior of a process is defined by an Extended Finite State Machine (EFSM) A specification in SDL expresses ....

Specification and Description Language (SDL), ITU-T Recommendation Z.100, 1992.

No context found.

Recommendation Z. 100 - Specification and Description Language (SDL), 1993.

First 50 documents  Next 50

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