Skip to main content
European Commission logo print header
Inhalt archiviert am 2024-04-16

Specification and Programming Environment for Communications Software

Ziel

The aim of the project is to define a methodology to provide maximum automation and optimisation through the design, implementation, test, execution, maintenance and adaptation of software. The project has a firm basis from which this aim can be realised: the use of formal methods. The handling and integration of informal methods is included as an important objective. Formal methods make automation possible, and automation makes formal methods amenable to human use. This twin emphasis on formal methods and maximum automation is applied throughout the project. The centre of the project is a common mathematical model. This allows the elimination of some manual language transformations during the software life-cycle and supports design transformations. Finally, it is an objective that adoption of the methodology can take place in an evolutionary way from existing approaches.
The aim of the research was to define a methodology to provide maximum automation and optimization of the programming environment for communications software through the design, implementation, test, execution, maintenance and adaption of software. The project was based on the use of formal methods which make automation possible, and automation makes formal methods amenable to human use. This twin emphasis on formal methods and maximum automation was applied throughout the research which was centred on a common mathematical model. This allows the elimination of some manual language transformations during the software life cycle and supports design transformations.

The main achievements of the research are:

The development of a methodology and architecture for handling specifications to reduce as much as possible the discountinuities within the software transformation process;
the realization of convergence within a programming infrastructure;
methods and methodology covering the following topics:
understanding of informal requirements or specifications;
generation of formal specifications;
refinement and analysis of formal specifications;
design and generation of code;
components for reuse;
and test and certification of software components and systems;

methods and tools for the following areas:
informal specification handling and formal specification generation;
formal specification handling with emphasis on specifications in SDL and LOTOS;
common semantics analysis;
simulation and execution of specifications;
online interface;

an integrated prototype to support the pilot use study.
Technical Approach

Methodology interfaces and functions are demonstrated through prototype implementations applied to real examples derived from other RACE tasks. Demonstration of results (methods, interfaces, functions and techniques demonstrated in the project) is being carried out in collaboration with other projects involved in programming infrastructure (PI) integration. It is envisaged that these can also be used as the basis of commercially- supported environments, and applied to IBC systems by the mid 1990s.

All of the specified functions of SPECS are grouped into a single, unifying architecture, based on existing standard specification languages (SDL, LOTOS). This is the enabling idea for automating to the maximum degree, the creation and handling of product quality code. SPECS allows maximum use of verification functions to improve greatly the quality of the software. The SPECS methodology and techniques support the object oriented design of software. The formal basis of the software can also be used for subsequent software reuse and modification, even of an installed software base.

Key Issues

- Wide ranging expertise within the project
- Co-ordination of activities across all projects
- Common semantic model

Achievements

The main achievements of the work done up to December 1991 are:

- Development of a methodology and architecture for handling specifications to reduce as much as possible the discontinuities within the software transformation process. Both goals have been reached through the delivery of SPECS Methodology and Architecture, the initial version of which has been demonstrated and further validated / enhanced by several model examples.
- Realisation of convergence within the programming infrastructure activity of RACE. The internal work done by each PI project and synthesised during common meetings is producing consensus on the recommended class of infrastructures and common practice recommendations (CPRs) for programming.
- Methods and methodology covering the following topics: understanding of informal requirements or specifications, generation of formal specifications, refinement and analysis of formal specifications, design and generation of code, components for reuse, and test and certification of software components and systems.
- Methods and tools have been implemented in the following areas: informal specification handling and formal specification generation, formal specification handling with emphasis on specifications in SDL and LOTOS, common semantics analysis, simulation and execution of specifications, on-line interface.
- The integrated prototype supports the pilot use study in 1992 and therefore allows evaluation of the SPECS approach. The prototype will be enhanced before the end of the project.

The results of the work have a clear focus on the needs of IBC designers, who may be working at different levels of abstraction. The range of prospective users of the SPECS results are quite well represented by the partners within the SPECS project. Thus the project team has been able to develop a clearer appreciation of the effectiveness of formal methods.

Expected Impact

The set of methods developed by SPECS has been moulded specifically to the needs of IBC software development and support. They are available within the Community as a basis for adaptation to specific industrial environments. Feedback to standards bodies such as CCITT and ISO has already taken place especially in the area of methodology and object orientation of SDL and LOTOS.

To support a full technology transfer to Europe's software industry, a briefing and a book summarising the SPECS approach are planned for the end of 1992. Detailed project results are available as reports from the prime contractor: GSI-TECSI.

SPECS methods are expected to reduce development and support costs, and yield a faster throughput of software development with, in particular, early simulation, validation and analysis.

Thema/Themen

Data not available

Aufforderung zur Vorschlagseinreichung

Data not available

Finanzierungsplan

Data not available

Koordinator

GSI TECSI
EU-Beitrag
Keine Daten
Adresse
6 Cours Michelet
92064 Paris la Défense
Frankreich

Auf der Karte ansehen

Gesamtkosten
Keine Daten

Beteiligte (11)