Feasibility study of an Integrated Program for Aerospace vehicle Design (IPAD). Volume 6: IPAD system development and operation

The strategy of the IPAD implementation plan presented, proposes a three phase development of the IPAD system and technical modules, and the transfer of this capability from the development environment to the aerospace vehicle design environment. The system and technical module capabilities for each phase of development are described. The system and technical module programming languages are recommended as well as the initial host computer system hardware and operating system. The cost of developing the IPAD technology is estimated. A schedule displaying the flowtime required for each development task is given. A PERT chart gives the developmental relationships of each of the tasks and an estimate of the operational cost of the IPAD system is offered

Spacelab software development and integration concepts study report, volume 1

The proposed software guidelines to be followed by the European Space Research Organization in the development of software for the Spacelab being developed for use as a payload for the space shuttle are documented. Concepts, techniques, and tools needed to assure the success of a programming project are defined as they relate to operation of the data management subsystem, support of experiments and space applications, use with ground support equipment, and for integration testing

On the engineering of crucial software

The various aspects of the conventional software development cycle are examined. This cycle was the basis of the augmented approach contained in the original grant proposal. This cycle was found inadequate for crucial software development, and the justification for this opinion is presented. Several possible enhancements to the conventional software cycle are discussed. Software fault tolerance, a possible enhancement of major importance, is discussed separately. Formal verification using mathematical proof is considered. Automatic programming is a radical alternative to the conventional cycle and is discussed. Recommendations for a comprehensive approach are presented, and various experiments which could be conducted in AIRLAB are described

System Programming - The Human and the Machine

The purpose of this paper is to document my experiences in planning, generating, and modifying the IBM VM/SP operating system (systems programming), survey literature on systems programming, and to draw conclusions as to what makes a successful systems programming experience. I will explore the skills necessary for the systems programmer to perform the tasks, as well as discuss aspects of the system itself (hardware, software, and documentation) that affect the success of any systems programming effort. This work is intended to serve as a case study of a VM/SP systems programmer working on WISPcompatible hardware. Judgments as to how these skills and conclusions may apply to other platforms are left to the reader

Rational's experience using Ada for very large systems

The experience using the Rational Environment has confirmed the advantages forseen when the project was started. Interactive syntatic and semantic information makes a tremendous difference in the ease of constructing programs and making changes to them. The ability to follow semantic references makes it easier to understand exisiting programs and the impact of changes. The integrated debugger makes it much easier to find bugs and test fixes quickly. Taken together, these facilites have helped greatly in reducing the impact of ongoing maintenance of the ability to produce a new code. Similar improvements are anticipated as the same level of integration and interactivity are achieved for configuration management and version control. The environment has also proven useful in introducing personnel to the project and existing personnel to new parts of the system. Personnel benefit from the assistance with syntax and semantics; everyone benefits from the ability to traverse and understand the structure of unfamiliar software. It is often possible for someone completely unfamiliar with a body of code to use these facilities, to understand it well enough to successfully with a body of code to use these facilities to understand it well enough to successfully diagnose and fix bugs in a matter of minutes

Industry liaison section implementation plan

The Industry Liaison Section is a new function of the Army/NASA Aircrew-Aircraft Integration (AAAI) Program that is intended to bridge an existing gap between Government developers (including contractors) and outside organizations who are potential users of products and services developed by the AAAI Program. Currently in its sixth year, the Program is experiencing considerable pull from industry and other government organizations to disseminate products. Since the AAAI Program's charter is exploratory and research in nature, and satisfying proper dissemination requirements is in conflict with the rapid prototyping approach utilized by the design team, the AAAI Program has elected to create an Industry Liaison Section (ILS) to serve as the Program's technology transfer focal point. The process by which the ILS may be established, organized and managed is described, including the baseline organizational structure, duties, functions, authority, responsibilities, relations and policies and procedures relevant to the conduct of the ILS

The cleanroom case study in the Software Engineering Laboratory: Project description and early analysis

This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage

Automating hypertext for decision support

A decision support system (DSS) shell is being constructed that can support applications in a variety of fields, e.g., engineering, manufacturing, finance. The shell provides a hypertext-style interface for 'navigating' among DSS application models, data, and reports. The traditional notion of hypertext had to be enhanced. Hypertext normally requires manually, pre-defined links. A DSS shell, however, requires that hypertext connections to be built 'on the fly'. The role of hypertext is discussed in augmenting DSS applications and the decision making process. Also discussed is how hypertext nodes, links, and link markers tailored to an arbitrary DSS application were automatically generated

CASE TECHNOLOGY AS A MEDIATING FACTOR IN ANALYST AND PROGRAMMER JOB OUTCOMES

Information Systems Working Papers Serie