Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software studies”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 253 records · Page 14

Long-Range Fit: A Software Package for the Representation and Study of Long-Range Molecular Interactions

Describing intermolecular forces is fundamental to modeling and predicting the behavior of molecular systems. In particular, long-range molecular interactions─with electrostatic, induction, and dispersion as the main components─play a critical role, especially for low-temperature and low-density regimes. Long-range interactions are often described through perturbation theory, representing the electronic charge distribution via a multipolar series of the moments and polarizability tensors corresponding to each molecule. However, while the theory is well established, obtaining the resulting analytical expressions (and their practical implementation) constitutes a highly complex and system-dependent task. To address this challenge, we developed long-range-fit (LRF), an interactive and user-friendly software package designed to automate the generation and fitting of long-range interaction terms for arbitrary molecules in nondegenerate (ground or excited) electronic states. We have derived and implemented all terms up to 15th order, without approximations, via a spherical tensor representation, with symmetry adaptation to all molecular point-group symmetries. The resulting potential energy surface is compatible with most representations of the close interaction region.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Software development for avionics SSME control and diagnostics

A study was made of software to integrate data from about 500 sensors that monitor the Space Shuttle Main Engine (SSME) and to make decisions for real-time control. Such software is expected to be applicable to other distributed systems as well. This study investigated the use of pattern recognition and other techniques to detect trends that could lead to major damage to the SSME and which would allow an orderly shutdown of the SSME before such damage could occur.

Choudry, A.↗

Software interface verifier

A Telos study of 40 recent subsystem deliveries into the DSN at JPL found software interface testing to be the single most expensive and error-prone activity, and the study team suggested creating an automated software interface test tool. The resulting Software Interface Verifier (SIV), which was funded by NASA/JPL and created by Telos, employed 92 percent software reuse to quickly create an initial version which incorporated early user feedback. SIV is now successfully used by developers for interface prototyping and unit testing, by test engineers for formal testing, and by end users for non-intrusive data flow tests in the operational environment. Metrics, including cost, are included. Lessons learned include the need for early user training. SIV is ported to many platforms and can be successfully used or tailored by other NASA groups.

Soderstrom, Tomas J.↗

SU-E-T-212: Influence of the Modulation Index On Daily Quality Assurance in Rapid Arc Treatments

Purpose: At our Institute some measured parameters for daily quality assurance (DQA) of dynamic arc therapy plans showed an unexpected behavior, therefore an investigation of the influence of the magnitude of modulation was conducted. Methods: In our clinical practice all DQAs of dynamic arc therapy plans are measured and analyzed prior to treatments using commercial software. For this study these plans were additionally exported to our in-house software written in MATLAB.The developed software extracted the leaf position, gantry angle, cumulative meterset weight of each control point (CP) and the total number of Monitor Units (MU) of each arc. Based on this information we calculated the leaf travel distance, irradiated segment area, number of MUs and dose rate for each CP. These data allowed us to calculate the modulation indexes (MI) of the plans, applying five different definitions of MI. The results were then correlated to the results of our DQA measurements.To validate the software, additional plans of known MIs were created and analyzed. For confirmation, the calculated parameters were compared to the segmented treatment table (STT) coming from the treatment planning system. Results: All calculated CP-parameters matched the STT by 99% or better. For linac 1, the comparison of the MI evaluation and the DQA results showed a slight tendency: 91.3% failed DQA plans had a MI lower than the average value. For this definition we consider that the lower the MI the higher the modulation. The results of the linac 2 present no significant relevance due to the low sample sizes for each DQA software. Conclusion: Available data and given definitions of the modulation index do not bring conclusive results; one cannot find a clear and distinct correlation with the failure of the DQA. The ongoing analysis with an increased sample size might lead to another conclusion.

07 ISOTOPE AND RADIATION SOURCES↗

On the nature of bias and defects in the software specification process

Implementation bias in a specification is an arbitrary constraint in the solution space. This paper describes the problem of bias. Additionally, this paper presents a model of the specification and design processes describing individual subprocesses in terms of precision/detail diagrams and a model of bias in multi-attribute software specifications. While studying how bias is introduced into a specification we realized that software defects and bias are dual problems of a single phenomenon. This was used to explain the large proportion of faults found during the coding phase at the Software Engineering Laboratory at NASA/GSFC.

Straub, Pablo A.↗

Evolving the Reuse Process at the Flight Dynamics Division (FDD) Goddard Space Flight Center

This paper presents the interim results from the Software Engineering Laboratory's (SEL) Reuse Study. The team conducting this study has, over the past few months, been studying the Generalized Support Software (GSS) domain asset library and architecture, and the various processes associated with it. In particular, we have characterized the process used to configure GSS-based attitude ground support systems (AGSS) to support satellite missions at NASA's Goddard Space Flight Center. To do this, we built detailed models of the tasks involved, the people who perform these tasks, and the interdependencies and information flows among these people. These models were based on information gleaned from numerous interviews with people involved in this process at various levels. We also analyzed effort data in order to determine the cost savings in moving from actual development of AGSSs to support each mission (which was necessary before GSS was available) to configuring AGSS software from the domain asset library. While characterizing the GSS process, we became aware of several interesting factors which affect the successful continued use of GSS. Many of these issues fall under the subject of evolving technologies, which were not available at the inception of GSS, but are now. Some of these technologies could be incorporated into the GSS process, thus making the whole asset library more usable. Other technologies are being considered as an alternative to the GSS process altogether. In this paper, we outline some of issues we will be considering in our continued study of GSS and the impact of evolving technologies.

Condon, S.↗

Feasibility study for a generalized gate logic software simulator

Unit-delay simulation, event driven simulation, zero-delay simulation, simulation techniques, 2-valued versus multivalued logic, network initialization, gate operations and alternate network representations, parallel versus serial mode simulation fault modelling, extension of multiprocessor systems, and simulation timing are discussed. Functional level networks, gate equivalent circuits, the prototype BDX-930 network model, fault models, identifying detected faults for BGLOSS are discussed. Preprocessor tasks, postprocessor tasks, executive tasks, and a library of bliss coded macros for GGLOSS are also discussed.

Mcgough, J. G.↗

Criteria for software modularization

A central issue in programming practice involves determining the appropriate size and information content of a software module. This study attempted to determine the effectiveness of two widely used criteria for software modularization, strength and size, in reducing fault rate and development cost. Data from 453 FORTRAN modules developed by professional programmers were analyzed. The results indicated that module strength is a good criterion with respect to fault rate, whereas arbitrary module size limitations inhibit programmer productivity. This analysis is a first step toward defining empirically based standards for software modularization.

Card, David N.↗

Study of a unified hardware and software fault-tolerant architecture

A unified architectural concept, called the Fault Tolerant Processor Attached Processor (FTP-AP), that can tolerate hardware as well as software faults is proposed for applications requiring ultrareliable computation capability. An emulation of the FTP-AP architecture, consisting of a breadboard Motorola 68010-based quadruply redundant Fault Tolerant Processor, four VAX 750s as attached processors, and four versions of a transport aircraft yaw damper control law, is used as a testbed in the AIRLAB to examine a number of critical issues. Solutions of several basic problems associated with N-Version software are proposed and implemented on the testbed. This includes a confidence voter to resolve coincident errors in N-Version software. A reliability model of N-Version software that is based upon the recent understanding of software failure mechanisms is also developed. The basic FTP-AP architectural concept appears suitable for hosting N-Version application software while at the same time tolerating hardware failures. Architectural enhancements for greater efficiency, software reliability modeling, and N-Version issues that merit further research are identified.

Lala, Jaynarayan↗

Study of the available finite element software packages at KSC

The interaction among the three finite element software packages, SDRCI/I-DEAS, MSC/NASTRAN, and I/FEM, used at NASA, Kennedy Space Center is addressed. The procedures for using more than one of these application software packages to model and analyze a structure design are discussed. Design and stress analysis of a solid rocket booster fixture is illustrated by using four different combinations of the three software packages. Their results are compared and show small yet acceptable differences.

Lu, Chu-Ho↗

Getting started on metrics - Jet Propulsion Laboratory productivity and quality

A review is presented to describe the effort and difficulties of reconstructing fifteen years of JPL software history. In 1987 the collection and analysis of project data were started with the objective of creating laboratory-wide measures of quality and productivity for software development. As a result of this two-year Software Product Assurance metrics study, a rough measurement foundation for software productivity and software quality, and an order-of-magnitude quantitative baseline for software systems and subsystems are now available.

Bush, M. W.↗

Software Engineering Laboratory (SEL) Ada performance study report

The goals of the Ada Performance Study are described. The methods used are explained. Guidelines for future Ada development efforts are given. The goals and scope of the study are detailed, and the background of Ada development in the Flight Dynamics Division (FDD) is presented. The organization and overall purpose of each test are discussed. The purpose, methods, and results of each test and analyses of these results are given. Guidelines for future development efforts based on the analysis of results from this study are provided. The approach used on the performance tests is discussed.

Booth, Eric W.↗

Recommended approach to software development, revision 3

Guidelines for an organized, disciplined approach to software development that is based on studies conducted by the Software Engineering Laboratory (SEL) since 1976 are presented. It describes methods and practices for each phase of a software development life cycle that starts with requirements definition and ends with acceptance testing. For each defined life cycle phase, guidelines for the development process and its management, and for the products produced and their reviews are presented.

Landis, Linda↗

Software process improvement in the NASA software engineering laboratory

The Software Engineering Laboratory (SEL) was established in 1976 for the purpose of studying and measuring software processes with the intent of identifying improvements that could be applied to the production of ground support software within the Flight Dynamics Division (FDD) at the National Aeronautics and Space Administration (NASA)/Goddard Space Flight Center (GSFC). The SEL has three member organizations: NASA/GSFC, the University of Maryland, and Computer Sciences Corporation (CSC). The concept of process improvement within the SEL focuses on the continual understanding of both process and product as well as goal-driven experimentation and analysis of process change within a production environment.

Mcgarry, Frank↗