A study of System Interface Sets (SIS) for the host, target and integration environments of the Space Station Program (SSP)

System interface sets (SIS) for large, complex, non-stop, distributed systems are examined. The SIS of the Space Station Program (SSP) was selected as the focus of this study because an appropriate virtual interface specification of the SIS is believed to have the most potential to free the project from four life cycle tyrannies which are rooted in a dependance on either a proprietary or particular instance of: operating systems, data management systems, communications systems, and instruction set architectures. The static perspective of the common Ada programming support environment interface set (CAIS) and the portable common execution environment (PCEE) activities are discussed. Also, the dynamic perspective of the PCEE is addressed

PROSET — A Language for Prototyping with Sets

We discuss the prototyping language PROSET(Prototyping with Sets) as a language for experimental and evolutionary prototyping, focusing its attention on algorithm design. Some of PROSET’s features include generative communication, flexible exception handling and the integration of persistence. A discussion of some issues pertaining to the compiler and the programming environment conclude the pape

Open environments to support systems engineering tool integration: A study using the Portable Common Tool Environment (PCTE)

A study of computer engineering tool integration using the Portable Common Tool Environment (PCTE) Public Interface Standard is presented. Over a 10-week time frame, three existing software products were encapsulated to work in the Emeraude environment, an implementation of the PCTE version 1.5 standard. The software products used were a computer-aided software engineering (CASE) design tool, a software reuse tool, and a computer architecture design and analysis tool. The tool set was then demonstrated to work in a coordinated design process in the Emeraude environment. The project and the features of PCTE used are described, experience with the use of Emeraude environment over the project time frame is summarized, and several related areas for future research are summarized

Study of Tools Interoperability

Interoperability of tools usually refers to a combination of methods and techniques that address the problem of making a collection of tools to work together. In this study we survey different notions that are used in this context: interoperability, interaction and integration. We point out relation between these notions, and how it maps to the interoperability problem. We narrow the problem area to the tools development in academia. Tools developed in such environment have a small basis for development, documentation and maintenance. We scrutinise some of the problems and potential solutions related with tools interoperability in such environment. Moreover, we look at two tools developed in the Formal Methods and Tools group1, and analyse the use of different integration techniques

Japanese cooperative R&D projects in software technology

Includes bibliographical references (leaves 50-55).Michael A. Cusumano

An approach to impact analysis in software maintenance

Impact analysis is a software maintenance activity, which consists of determining the scope of a requested change, as a basis for planning and implementing it. After a change request has been specified (change understanding) and the initial part of the system to be changed has been identified (change localization), impact analysis helps to understand consequences of the change on other parts of the system. Induced changes, also named ripple effects, among software components are detected. Most existing approaches perform impact analysis for changes occurring at the code level. In this thesis, concepts developed to perform impact analysis at the code level are applied to trace changes occurring at the design level. The method consists of proposing an activity model addressing the different steps of impact analysis and a data model on which propagations of changes can be traced. The method is validated with a case study applied to a system from the aerospace field. The tools we developed on PCTE help for consistency checks in HOOD based designs during editing. Our data-model based on an Entity Relationship notation describes a way to model HOOD diagrams in PCTE and further on to propagate changes on the repository. Examples chosen address the design phase of a simple engine system. We show that addressing modifications at a higher level of abstraction than the code eases understanding and localization of changes. It also limits the propagation of ripple effects (i.e., unexpected behaviour of the system) by detecting secondary changes at an earlier stage

Developing and integrating tools in Eclipse/PCTE

The whole area of software engineering environments is an emerging one. Such environments have become necessary due to the rapid changes which have occurred in the software industry in the last twenty years. The desire is to produce products of high quality and at a reasonable cost. Unfortunately history shows that, in general, software systems rarely met the specific need for which they were developed and were often unreliable, inefficient , poorly documented and required considerable maintenance. One of the main areas of research into increasing both the productivity and the quality of software has been the use of software engineering environments. The area of software engineering environments is a changing one with evolving definitions. What can be stated is that a key objective of software engineering environments is the support of software process from requirements definition through to system maintenance. Such support can only be provided through the development of integrated sets of tools each supporting various aspects of the software development process. In order for tools to be fully integrated and have the same ’look and feel’ it is necessary that they are developed on a common platform, providing all the facilities needed for tool development and integration. Such a platform is the Eclipse tool builder’s kit based on the Portable Common Tool Environment (PCTE). The work in this thesis was based on an evaluation of this development platform for developing and integrating software tools, particularly real-time telecommunications software tools. The work in this thesis was carried out as part of the European Community’s RACE programme. The project was called SPECS 1. The SPECS project is outlined in chapter one of this thesis along with a brief history of the research into software engineering environments to date. The work which I was responsible for involved both the integration of existing toolsets and tools, developed by other partners in the SPECS project, as well as the development of new "native" tools within Eclipse/PCTE. This work was necessary so that the SPECS project could produce an integrated set of tools at the end of its research. It was my job to evaluate the potential of Eclipse/PCTE as a basis for this integration