Service Specification and Validation for the Intelligent Network

Jean-Pierre Hubaux
1997
Report or working paper

We propose an object-oriented specification language, FUS++, for expressing the functional behaviors and the desired properties of each telecommunications service at the analysis phase. Our approach is based on Fusion, an object-oriented method that consists of analysis, design, and implementation phases for software development. Accompanying FUS++ is a tool we developed for translating FUS++ specifications to Promela statements; validation of service specifications and detection of feature interactions are thus possible by applying Spin tools to these Promela statements. To ensure a correct implementation of services with respect to their specifications, we exercise a novel concept of adding a service modeler and observer (SMO) to the target system where the execution of these services takes place. Combined with a test scenario generator, SMO is quite effective in identifying implementation errors on the fly. This paper presents the FUS++ language, the specification of telecommunications services based on FUS++, the concept of SMO, and the realization of SMO in a CS-1 (Capability Set No 1) intelligent network. Index terms : telecommunication software engineering, validation, software lifecycle, property verification, intelligent network.

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Related concepts

Related publications

Jean-Pierre Hubaux
1997
Report or working paper

Abstract

Official source

https://infoscience.epfl.ch/record/52252?ln=en

About this result

Related concepts (7)

Related concepts

Related publications (2)

Related publications

Service Specification and Validation for the Intelligent Network

Jean-Pierre Hubaux

We propose an object-oriented specification language, FUS , for expressing the functional behaviors and the desired properties of each telecommunications service at the analysis phase. Our approach is based on Fusion, an object-oriented method that consists of analysis, design, and implementation phases for software development. Accompanying FUS is a tool we developed for translating FUS specifications to Promela statements

1998

The Goals of the Analysis Model

When developing an analysis model, the notation itself does not suffice for determining the content of the analysis model and the end of the analysis process. For this, the goals and intents of the analysis model are used, either implicitly or explicitly. In this report we take a look at various possibilities to define the term analysis and the goals of the analysis model. We start with considering the reference model of the problem solving cycle. We examine the definitions that refer to analysis as the "what" in opposite to the "how", or as the problem definition phase of a problem solving cycle. We then continue with a discussion of various criteria (like technology independence, real word model, unambiguous or essential model) that are often used to specify the goals of an analysis model. Difficulties that arise with these criteria are that they cannot be combined arbitrarily and that some of them are very vague; we propose therefore also some more concrete formulations. In the last part of the report we take a closer look at some misconceptions and intent clashes that are due to a too idealistic model of the software development process. Objective real world models, analysis models that are stable after the analysis phase and analysis models that are equal to the high-level view of the final software system are often attempted, but are normally not realistic. This leads to intent clashes with the desire for a seamless and easy controllable development process. We explain these intent clashes and we also describe the three different approaches taken by software development methods to cope with these intent clashes.

1996

Software development

Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other soft

Electronic engineering

Electronic engineering is a sub-discipline of electrical engineering which emerged in the early 20th century and is distinguished by the additional use of active components such as semiconductor dev

Formal verification

In the context of hardware and software systems, formal verification is the act of proving or disproving the correctness of intended algorithms underlying a system with respect to a certain formal sp