Objectif
ARISE will act as a catalyst in the forming of consensus in the European telecommunications industry on the IBC software development process.
A key part of any software development is the environment: ARISE is preparing statements on development environment architectures that support novel development techniques and permit their integration with existing development methodologies, tools and environments.
The project has the goal of developing and populating a prototype environment that validates ideas submitted for standards consideration. These prototypes will reflect architecture and integration principles and demonstrate their practicality.
The ARISE project has studied the programming infrastructure that will allow the production of high volumes of reliable, complex, real-time software. Tools have been prototyped which will assist in the support of the documentation produced during the software development process.
The project has the goal of developing and populatinga prototype environment that validates ideas submitted for standards consideration. These prototypes will reflect architecture and integration principles and demonstrate their practicality.
The project follows 2 main approaches, in seeking to improve the productivity of software development and management for integrated broadband communications (IBC). A reusability infrastructure for software engineerng (ARISE) is putting significant effort into experimenting with reuse of software, and developing tools to support reuse. The project intends to confirm the potential of reuse and to further develop support for reuse based development methodologies.
The second approach develops the support environment for IBC software engineering. This encompasses the project's architecture and integration studies as well as the prototyping and customization of tools and the environment itself.
The ARISE architecture has been specified, taking into account related proposals from standards bodies and other initiatives. A study on the different integration methods that can be applied to ARISE has been completed. Extensive investigation of integration by event mechanisms and their suitability for tool integration within ARISE have been made.
The process support provided by the environment has been developed and refined in the key areas of quality management, process modelling, configuration management and documentation. The specification of the environment has also been enriched. The configuration management model and the change management prototype have also been developed further, and are being applied, within the project, to much of the production of ARISE software.
The second release of the integrated ARISE prototype environment was demonstrated in October 1991. The core of the environment is a set of generic tools supporting management processes. This is populated with other tools to support the complete software life cy cle.
A new design method, ZOOD, combining the Z specification language and hierarchical object oriented design method (HOOD) has been defined and applied to a few case studies. A component model which includes the documentation of all software life cycle phases has been defined assuming HOOD as the design method.
Technical Approach
The project follows two main approaches, in seeking to improve the productivity of software development and management for IBC. ARISE is putting significant effort into experimenting with reuse of software, and developing tools to support reuse. The project intends to confirm the potential of reuse and to further develop support for reuse-based development methodologies.
The second approach develops the support environment for IBC software engineering. This encompasses the project's architecture and integration studies as well as the prototyping and customisation of tools and the environment itself.
In 1992 two major case studies will be used to validate the ARISE environment:
- an in-house experiment in CET will be performed, to compare the use of the environment populated with a set of tools against existing approaches
- the ARISE environment will be tailored to match requirements from CAP SESA Telecom who will use it in a 'real' multimedia project.
Key Issues
- Software reuse.
- Process support, quality improvements.
- Configuration and change management support.
- Tools and methods for IBC software engineering.
Achievements
The ARISE architecture has been specified, taking into account related proposals from standards bodies and other initiatives. A study on the different integration methods that can be applied to ARISE has been completed. Extensive investigation of 'integration by event' mechanisms and their suitability for tool integration within ARISE have been made.
The process support provided by the environment has been developed and refined in the key areas of quality management, process modelling, configuration management and documentation. The specification of the environment has also been enriched. The configuration management model and the change management prototype have also been developed further, and are being applied, within the project, to much of the production of ARISE software.
The second release of the integrated ARISE prototype environment was demonstrated in October 1991, at the ICB Symposium. The core of the environment is a set of generic tools supporting management processes. This is populated with other tools to support the complete software life cycle. A working prototype of Museion (the Reuse repository) is integrated into the ARISE environment. Museion contains a number of functionalities for classifying, storing, retrieving and analysing reusable information.
A new design method, ZOOD, combining the Z specification language and hierarchical object oriented design method (HOOD) has been defined and applied to a few case studies. A component model which includes the documentation of all software life-cycle phases has been defined assuming HOOD as the design method.
To date the ARISE project has produced 28 major deliverables and more than 30 conference papers. 13 final reports are due in 1992.
Expected Impact
Some results from the ARISE project are suitable for contribution to standardisation organisations. Others will be influencing the de facto industry standards used in the CASE area. A secondary impact may arise in the choice and application of new technology in this field, by European telecommunications industry.
Champ scientifique (EuroSciVoc)
CORDIS classe les projets avec EuroSciVoc, une taxonomie multilingue des domaines scientifiques, grâce à un processus semi-automatique basé sur des techniques TLN. Voir: Le vocabulaire scientifique européen.
CORDIS classe les projets avec EuroSciVoc, une taxonomie multilingue des domaines scientifiques, grâce à un processus semi-automatique basé sur des techniques TLN. Voir: Le vocabulaire scientifique européen.
- sciences naturelles informatique et science de l'information logiciel développement logiciel
- sciences sociales économie et affaires économie économie de la production productivité
- sciences naturelles sciences chimiques catalyse
- ingénierie et technologie génie électrique, génie électronique, génie de l’information ingénierie de l’information télécommunication
Vous devez vous identifier ou vous inscrire pour utiliser cette fonction
Programme(s)
Programmes de financement pluriannuels qui définissent les priorités de l’UE en matière de recherche et d’innovation.
Programmes de financement pluriannuels qui définissent les priorités de l’UE en matière de recherche et d’innovation.
Thème(s)
Les appels à propositions sont divisés en thèmes. Un thème définit un sujet ou un domaine spécifique dans le cadre duquel les candidats peuvent soumettre des propositions. La description d’un thème comprend sa portée spécifique et l’impact attendu du projet financé.
Données non disponibles
Les appels à propositions sont divisés en thèmes. Un thème définit un sujet ou un domaine spécifique dans le cadre duquel les candidats peuvent soumettre des propositions. La description d’un thème comprend sa portée spécifique et l’impact attendu du projet financé.
Appel à propositions
Procédure par laquelle les candidats sont invités à soumettre des propositions de projet en vue de bénéficier d’un financement de l’UE.
Données non disponibles
Procédure par laquelle les candidats sont invités à soumettre des propositions de projet en vue de bénéficier d’un financement de l’UE.
Régime de financement
Régime de financement (ou «type d’action») à l’intérieur d’un programme présentant des caractéristiques communes. Le régime de financement précise le champ d’application de ce qui est financé, le taux de remboursement, les critères d’évaluation spécifiques pour bénéficier du financement et les formes simplifiées de couverture des coûts, telles que les montants forfaitaires.
Régime de financement (ou «type d’action») à l’intérieur d’un programme présentant des caractéristiques communes. Le régime de financement précise le champ d’application de ce qui est financé, le taux de remboursement, les critères d’évaluation spécifiques pour bénéficier du financement et les formes simplifiées de couverture des coûts, telles que les montants forfaitaires.
Données non disponibles
Coordinateur
2 DUBLIN
Irlande
Les coûts totaux encourus par l’organisation concernée pour participer au projet, y compris les coûts directs et indirects. Ce montant est un sous-ensemble du budget global du projet.