Programming Support Environment Research Articles

Content adaptation neural network method cause-specific the state of users

The aim of the study is to develop recommendations for adapting educational content based on the use of a neural network method for recognizing the human autonomic nervous system degree of activity. The initial data for decision making are the vectors of cardiointervals obtained with the help of the pulse sensor. The state of the autonomic nervous system is monitored by a two-layer artificial neural network of direct propagation. The artificial neural network was trained by combining gradient and stochastic training methods. A trial sample was used as a training set, consisting of 168 records of people’s cardiointervals belonging to different social and age groups. The presented method for recognizing the autonomic nervous system activity degree was tested via the shared programming support environment Lazarus. As a result of network training, a set of weighting coefficient values was found, for which 100% correct recognition is performed over the entire trial sample. A personalized training system that monitors the functional state of the student varies the presentation of educational content. When the functional state changes during the training load, the virtual agent organizes the training process so as to avoid stress load.

Methodology and software for estimating target efficiency of land remote sensing satellites at the stage of design

The paper aims to present the software developed with the purpose of estimating land remote sensing satellites and space monitoring system target efficiency indices. The essence of the approach is step-by-step simulation of the satellite orbital motion with permanent determination of the flight conditions and estimation of the satellite and the space monitoring system target parameters. Main factors affecting target efficiency are taken into consideration; they include orbital elements and the satellite coordinates variation while its orbital movement, the satellite manoeuvres in the process of its target operation, conditions of survey objects taking, characteristics of survey equipment, etc. The algorithm used is based on a number of mathematical models such as models for generating initial data on survey objects, models for choice of survey objects within the satellite swath, models for constructing land remote sensing satellites survey path, models for estimating orientation of solar cell battery panels, etc. The software has been developed in Delphi programming support environment. It enables calculation of satellites target parameters such as ground resolution, operational efficiency, surveillance frequency, productivity.

Fuzzy controller adaptation

During writing this work, the fuzzy controller with a double base of rules was studied, which was applied for the synthesis of the automated control system. A method for fuzzy controller adaptation has been developed. The adaptation allows the fuzzy controller to automatically compensate for parametric interferences that occur at the control object. Specifically, the fuzzy controller controlled the outlet steam temperature in the boiler unit BKZ-75-39 GMA. The software code was written in the programming support environment Unity Pro XL designed for fuzzy controller adaptation.

Calculation of the Kinetic Parameters of the Hydrofining Process of Diesel Fraction Using Mathematical Modeling

Using programming support environment FreePascal and FreeBasic, the program providing to calculate values of efficient rate constants for hydrogenation reactions of benz- and dibenzothiophenes in the process of diesel fuel hydrofining, is developed. The basis of the developed algorithm of solving reverse kinetic problem is the method of optimization by scanning the permissible scan area, which let it possible to make calculations with inaccuracy not exceeding 0.007%. By using the developed program, is conducted the calculation of velocity constants and activation energy of transforming individual sulphur compounds on the basis of laboratory stand experimental data, obtained under different conditions. The program can be implemented in oil and gas industry.

Conflict resolution for readers and writers

For those of us who have been teaching Operating Systems for years, you may remember with nostalgia the days when Operating Systems texts [ex: Deitel 1984] included Ada code to illustrate solutions for concurrency problems. I find concurrency the most difficult topic to teach in Operating Systems, and expressing solutions in Ada is a strong teaching aid. Ada's tasking construct is powerful and readable. In addition, an Ada Programming Support Environment enables hands-on experimentation.The Readers/Writers problem, a classic mutual exclusion synchronization problem, puzzled computer science professionals for years. Explaining these solutions, as presented in current Operating Systems texts, is daunting.We contrast code expressed in C to that proposed by Burns [Burns1985] and Barnes [Barnes1995] for readability. We then suggest a slight modification to obtain what we consider to be a preferred solution, one that illuminates concurrency issues in general.

International high technology cooperation: lessons learned

In February 1986, in response to the Nunn Amendment in the United States, a special Conference of National Armaments Directors (CNAD) examined possible ways to foster cooperative high technology research and development programs within the NATO Alliance. As a result, they established the Special Working Group on Ada Programming Support Environments (SWG APSE) to oversee the development of a multinational software development environment for developing real-time weapon systems in the Ada programming language. The Working Group also developed a requirements specification for a software development environment interface standard. The author describes the benefits and pitfalls of this joint software development. He also describes the lessons learned from such joint multinational development efforts. Further, the author describes the management issues that are unique to such an international collaborative effort and gives a frank assessment of the techniques that had helped and hindered the program's progress.

Development of process-centered IPSEs in the ALF project

In this article we describe the main results of the ESPRIT project ALF (in French: Accueil de Logiciel Futur or Advanced Software Engineering Environments' Logistics Framework). In ALF we have developed a framework for Integrated Programming Support Environments (IPSEs), a software process modeling language (based on the notion of Models of Assisted Software Processes (MASP)), and an environment used to develop software process models. A MASP describes a software development method. This method specifies how an IPSE should behave. It can be plugged into the framework for IPSEs. Moreover, a MASP is used to integrate tools into the IPSE framework. In this article we focus on assistance and guidance facilities for software developers implemented in the framework for IPSEs.

A uniform graphical view of the program construction process: GRIPSE

This paper describes the ideas leading to the development and construction of a Graphical Integrated Programming Support Environment (GRIPSE) for a modified form of the Pascal language. In order to represent all procedural and declarative aspects of a Pascal program, the original Nassi-Shneiderman diagrams forming the graphical basis of GRIPSE have been augmented into a multi-level, three dimensional system capable of supporting all static and most dynamic aspects of a program in a uniform manner. The dynamic view exists by virtue of an interpreter that has been incorporated along with debugging aids. A planned extension to the environment is an interactive form of mutation testing called Firm mutation which exploits the middle-ground between Strong and Weak mutation, both of which have traditionally been applied in a non-conversational, non-interactive mode of use.

Enhancing software productivity through templating

The paper presents Template Reusability in Programs (TRIP), a programming support environment that increases software productivity through the reuse of code fragments, objects, and logic sets encoded in templates. Templates are procedures that preprocess the source code before it is submitted to a compiler. Preprocessing results in the generation of code segments, which are inserted into one or more locations in a given target code, based on logic rules embedded in templates. To provide the templates with information about the source code as it is being scanned, a directive process matches user-defined patterns in the source code. Directives are responsible for the execution of templates according to the appearance of the user-defined patterns in the source code. The templates are customizable. They can be modified to produce target codes that follow the user's programming standards and styles. In addition, sets of templates may be used to generate codes for different operating environments from the same source code. A salient feature of TRIP is that templates support both the development and maintenance phases of the software life-cycle. The paper describes TRIP's concept of templating, its language, and the image specification and pattern-matching directives. TRIP has been used at Software Brewers, Inc., in the implementation of two software projects: CC2 (a compiler-compiler) and XCobol (a commercial package that generates business application programs in Cobol).

A look at multipolicy research today and some proposed directions for tomorrow

Most information systems which we try to model from a security perspective are implicitly governed by multiple security policies, hereafter called multipolicies. This stems from the fact that these systems generally support people-oriented activities which have different security relevant characteristics and are regulated by varying rules depending upon the roles and functions of individuals as well as the contexts of tasks performed by them. Such systems are evident in a variety of commercial and government enterprises. Examples of multipolicy environments include trusted software programming support environments, banking systems, interservice military programs such as SDI, international military organizations such as NATO, medical information systems, and multinational corporations to mention a few.

A generic persistent object store

Persistent programming systems have demonstrated the benefits of abstracting over the implementation details related to the storage and manipulation of long-term data. In particular, programming systems in which persistence is provided as an orthogonal property of all data types have been used to produce cost-effective implementations of applications such as integrated programming support environments. In this paper, we describe a generic architecture that supports persistent programming. In particular, the provision of an object store is highlighted, outlining its design aims and resultant structure. The application of the architecture in a wide variety of programming paradigms is reported.

On the decline of classical programming

Summary form only given. The author puts forward the view that we are in a period of far-reaching and fundamental change in the practice of information technology. This has been a gradual though accelerating process during the 1980s and some of its effects are now becoming apparent in the changes in the structure and activities of industry. A central aspect is the increasing shift to the design of computing systems by non-specialists in IT. He looks at the general features of this new era. Then he turns to an analysis of the specific developments in computer programming and the role of the 'professional programmer'. Finally, he embarks on some speculation as to the future of programming support environments and of research in the field.

VADS APSE

During the 1980's, the United States Department of Defense developed the Ada language to combat the growing "software crisis," while software companies developed Computer-Aided Software Engineering (CASE) tools to enhance software development productivity. Ada and CASE are beginning to merge, but the disjoined solutions offered by individual CASE vendors to this point are lacking in two key areas: (1) exploitation of program information available as a by-product of compiling an Ada program; and (2) integration of individual tools to produce synergistic benefits over a broader range of the software development cycle.To remedy these shortcomings, Verdix Corporation has begun development of an Integrated Ada Programming Support Environment, VADS APSE. VADS APSE represents a significant departure from previous APSE development efforts in that it is built on an environment framework from commercially available software and it exploits the capabilities of powerful, low-cost, networked engineering workstations. While VADS APSE represents an instance of an environment built upon a framework, it also represents, through extensions to the underlying framework, an Ada-specific environment framework that can be tailored to meet the needs of a specific software development activity.

Programming Support Environment for Control Software

Programming Support Environment for Control Software

Past and future trends for portable tools interfaces

The paper reviews the history of computer science theory and practice, to try and identify the important trends that ought to be influencing the evolution of Portable Tools Interfaces (PTIs). PTIs are a relatively recent development, providing a manufacturer-independent interface to operating-system features. This enables portable software to be written that will run on any machine on which the PTI is implemented. The paper concludes with a requirement for what the authors feel is both a powerful and practical PTI that will support the development of a new generation of programming languages, operating systems, programming support environments (PSEs), and integrated project support environments (IPSEs).

Integrated project support environments

The paper presents an overview of integrated project support environments (IPSEs) which are software development environments intended to support large, long-lifetime software projects. The logical structure of an IPSE is discussed from the view that the IPSE is a set of layered facilities. Each layer in the set is described. Standardization is important for future IPSE development and standard public tool interfaces are discussed. Common ada programming support environment interface set (CATS) and portable common tool environment (PCTE) are introduced. Examples of tool and user interface integration in an IPSE are provided using the Eclipse IPSE as an exemplar. Deficiencies in current systems and future developments in this area are addressed.

Segue: support for distributed graphical interfaces

The authors describe their experiences developing Segue, an interface tool for supporting application programs that manipulate tree-like data structures. This semantic domain, although restrictive, includes a number of important application programs, such as structured editors, incremental compilers, and file system managers. The user interface tools described here support the Distributed Ada Programming Support Environment (DAPSE). The authors discuss the structure of Segue, present the R2D unparsing system, and examine tree-to-tree mappings. They then present three Segue user interfaces: an Ada editor, an Ada library manager, and the Gift interface specification tool. >

An overview of DOD-STD-1838A (proposed) the common APSE interface set: revision

A five-year effort under the Ada Joint Program Office has developed a proposed standard for a host system interface as seen by tools running in an Ada Programming Support Environment (APSE). Standardization of this interface as DOD-STD-1838A will have a number of desirable effects for the Department of Defense, including tool portability, tool integration, data transportability, encouragement of a market in portable tools, and better programmer productivity. As the capability of tools to communicate with each other is a central requirement in APSEs, the Common APSE Interface Set (CAIS) has paid particular attention to facilitate such communication in a host-independent fashion. CAIS incorporates a well-integrated set of concepts tuned to the needs of writers and users of integrated tool sets. This paper covers several of these concepts: • the entity management system used in place of a traditional filing system, • object typing with inheritance, • process control including atomic transactions, • access control and security, • input/output methods, • support for distributed resource control, and • facilities for inter-system data transport.

Version management in Gypsy

This paper describes the Version Manager of the Gypsy programming support environment, and its integration with the object-oriented extension of Unix 1 on which it is built.

An overview of DOD-STD-1838A (proposed) the common APSE interface set: revision

A five-year effort under the Ada Joint Program Office has developed a proposed standard for a host system interface as seen by tools running in an Ada Programming Support Environment (APSE). Standardization of this interface as DOD-STD-1838A will have a number of desirable effects for the Department of Defense, including tool portability, tool integration, data transportability, encouragement of a market in portable tools, and better programmer productivity. As the capability of tools to communicate with each other is a central requirement in APSEs, the Common APSE Interface Set (CAIS) has paid particular attention to facilitate such communication in a host-independent fashion. CAIS incorporates a well-integrated set of concepts tuned to the needs of writers and users of integrated tool sets. This paper covers several of these concepts: • the entity management system used in place of a traditional filing system, • object typing with inheritance, • process control including atomic transactions, • access control and security, • input/output methods, • support for distributed resource control, and • facilities for inter-system data transport.