Proceedings of the Seventh Annual Software Engineering Workshop
The Software Engineering Laboratory, software tools, software errors and cost estimation are addressed.
Source record↗
SEARCH · Search NASA
Results for “Software errors”
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.
Evaluation of airborne lidar wind measurements
The verification of the Doppler lidar wind measurement is continued. The in situ measurements on a 500 meter tall tower are used to check the lidar determined winds (flight 4), followed by other tests applied to the extensive data sets of flights 19 and 21. After checking for possible software errors in the processing programs, the inconsistency was not solved. The source of the errors appears to be the uncertainty in the calculation of the contribution of the aircraft motion to the lidar measured line of sight speed. Possible techniques for estimating the aircraft motion errors from the aircraft data are investigated.
Carroll, J. J.↗
SSME digital control design characteristics
To protect against a latent programming error (software fault) existing in an untried branch combination that would render the space shuttle out of control in a critical flight phase, the Backup Flight System (BFS) was chartered to provide a safety alternative. The BFS is designed to operate in critical flight phases (ascent and descent) by monitoring the activities of the space shuttle flight subsystems that are under control of the primary flight software (PFS) (e.g., navigation, crew interface, propulsion), then, upon manual command by the flightcrew, to assume control of the space shuttle and deliver it to a noncritical flight condition (safe orbit or touchdown). The problems associated with the selection of the PFS/BFS system architecture, the internal BFS architecture, the fault tolerant software mechanisms, and the long term BFS utility are discussed.
Mitchell, W. T.↗
Four applications of a software data collection and analysis methodology
The evaluation of software technologies suffers because of the lack of quantitative assessment of their effect on software development and modification. A seven-step data collection and analysis methodology couples software technology evaluation with software measurement. Four in-depth applications of the methodology are presented. The four studies represent each of the general categories of analyses on the software product and development process: blocked subject-project studies, replicated project studies, multi-project variation studies, and single project strategies. The four applications are in the areas of, respectively, software testing, cleanroom software development, characteristic software metric sets, and software error analysis.
Basili, Victor R.↗
A specification-based approach to concurrent structure verification in multiprocessor systems
A recently initiated research project concerned with the concurrent detection of software errors and errors due to physical failures in the hardware of multiprocessor systems is described in this paper. An approach to error detection is described, which is specification based and relies on the structural verification of program control flow and data structure integrity. The techniques discussed utilize the hardware redundancy inherent in parallel processing systems to provide verification of both program structure and data concurrently with program execution.
Fuchs, W. Kent↗
Software quality assurance plan for GCS
The software quality assurance (SQA) function for the Guidance and Control Software (GCS) project which is part of a software error studies research program is described. The SQA plan outlines all of the procedures, controls, and audits to be carried out by the SQA organization to ensure adherence to the policies, procedures, and standards for the GCS project.
Duncan, Stephen E.↗
Software requirements: Guidance and control software development specification
The software requirements for an implementation of Guidance and Control Software (GCS) are specified. The purpose of the GCS is to provide guidance and engine control to a planetary landing vehicle during its terminal descent onto a planetary surface and to communicate sensory information about that vehicle and its descent to some receiving device. The specification was developed using the structured analysis for real time system specification methodology by Hatley and Pirbhai and was based on a simulation program used to study the probability of success of the 1976 Viking Lander missions to Mars. Three versions of GCS are being generated for use in software error studies.
Withers, B. Edward↗
An expert system for diagnosing anomalies of spacecraft
Although the analysis of anomalous behavior of satellites is difficult because it is a very complex process, it is important to be able to make an accurate assessment in a timely manner when the anomaly is observed. Spacecraft operators may have to take corrective action or to 'safe' the spacecraft; space-environment forecasters may have to assess the environmental situation and issue warnings and alerts regarding hazardous conditions, and scientists and engineers may want to gain knowledge for future designs to mitigate the problems. Anomalies can be hardware problems, software errors, environmentally induced, or even the cause of workmanship. Spacecraft anomalies attributable to electrostatic discharges have been known to cause command errors. A goal is to develop an automated system based on this concept to reduce the number of personnel required to operate large programs or missions such as Hubble Space Telescope (HST) and Mission to Planet Earth (MTPE). Although expert systems to detect anomalous behavior of satellites during operations are established, diagnosis of the anomaly is a complex procedure and is a new development.
Lauriente, Michael↗
Getting it right, making it better
The research into the advancement of software error compensation techniques is discussed in this video. Although these techniques were originally designed for coordinate measuring machines, they are now used for machine tools as well.
Source record↗
A statistical analysis of the broadband 0.1 to 3.5 keV spectral properties of X-ray-selected active galactic nuclei
We survey the broadband spectral properties of approximately 500 X-ray-selected active galactic nuclei (AGNs) observed with the Einstein Observatory. Included in this survey are the approximately 450 AGNs in the Extended Medium Sensitivity Survey (EMSS) of Gioia et al. (1990) and the approximately 50 AGNs in the Ultrasoft Survey of Cordova et al. (1992). We present a revised version of the latter sample, based on the post publication discovery of a software error in the Einstein Rev-1b processing. We find that the mean spectral index of the AGNs between 0.1 and 0.6 keV is softer, and the distribution of indices wider, than previous estimates based on analyses of the X-ray spectra of optically selected AGNs. A subset of these AGNs exhibit flux variabiulity, some on timescales as short as 0.05 days. A correlation between radio and hard X-ray luminosity is confirmed, but the data do not support a correlation between the radio and soft X-ray luminosities, or between radio loudness and soft X-ray spectral slope. Evidence for physically distinct soft and hard X-ray components is found, along with the possibility of a bias in previous optically selected samples toward selection of AGNs with flatter X-ray spectra.
Thompson, R. J.↗
Integration of the Shuttle RMS/CBM Positioning Virtual Environment Simulation
Constructing the International Space Station, or other structures, in space presents a number of problems. In particular, payload restrictions for the Space Shuttle and other launch mechanisms prohibit assembly of large space-based structures on Earth. Instead, a number of smaller modules must be boosted into orbit separately and then assembled to form the final structure. The assembly process is difficult, as docking interfaces such as Common Berthing Mechanisms (CBMS) must be precisely positioned relative to each other to be within the "capture envelope" (approximately +/- 1 inch and +/- 0.3 degrees from the nominal position) and attach properly. In the case of the Space Station, the docking mechanisms are to be positioned robotically by an astronaut using the 55-foot-long Remote Manipulator System (RMS) robot arm. Unfortunately, direct visual or video observation of the placement process is difficult or impossible in many scenarios. One method that has been tested for aligning the CBMs uses a boresighted camera mounted on one CBM to view a standard target on the opposing CBM. While this method might be sufficient to achieve proper positioning with considerable effort, it does not provide a high level of confidence that the mechanisms have been placed within capture range of each other. It also does nothing to address the risk of inadvertent contact between the CBMS, which could result in RMS control software errors. In general, constraining the operator to a single viewpoint with few, if any, depth cues makes the task much more difficult than it would be if the target could be viewed in three-dimensional space from various viewpoints. The actual work area could be viewed by an astronaut during EVA; however, it would be extremely impractical to have an astronaut control the RMS while spacewalking. On the other hand, a view of the RMS and CBMs to be positioned in a virtual environment aboard the Space Shuttle orbiter or Space Station could provide similar benefits more safely and conveniently with little additional cost. In order to render and view the RMS and CBMs in a virtual world, the position and orientation of the end effector in three-dimensional space must be known with a high degree of accuracy. A precision video alignment sensor has been developed which can determine the position and orientation of the controlled element relative to the target CBM within approximately one-sixteenth inch and 0.07 angular degrees. Such a sensor could replace or augment the boresighted camera mentioned above. The computer system used to render the virtual world and the position tracking systems which might be used to monitor the user's movements (in order to adjust the viewpoint in virtual space) are small enough to carry to orbit. Thus, such a system would be feasible for use in constructing structures in space.
Dumas, Joseph D.↗
Joint NASA Ames/Langley Experimental Evaluation of Integrated Air/Ground Operations for En Route Free Maneuvering
In order to meet the anticipated future demand for air travel, the National Aeronautics and Space Administration (NASA) is investigating a new concept of operations known as Distributed Air-Ground Traffic Management (DAG-TM). Under the En Route Free Maneuvering component of DAG-TM, appropriately equipped autonomous aircraft self separate from other autonomous aircraft and from managed aircraft that continue to fly under today s Instrument Flight Rules (IFR). Controllers provide separation services between IFR aircraft and assign traffic flow management constraints to all aircraft. To address concept feasibility issues pertaining to integrated air/ground operations at various traffic levels, NASA Ames and Langley Research Centers conducted a joint human-in-the-loop experiment. Professional airline pilots and air traffic controllers flew a total of 16 scenarios under four conditions: mixed autonomous/managed operations at three traffic levels and a baseline all-managed condition at the lowest traffic level. These scenarios included en route flights and descents to a terminal area meter fix in airspace modeled after the Dallas Ft. Worth area. Pilots of autonomous aircraft met controller assigned meter fix constraints with high success. Separation violations by subject pilots did not appear to vary with traffic level and were mainly attributable to software errors and procedural lapses. Controller workload was lower for mixed flight conditions, even at higher traffic levels. Pilot workload was deemed acceptable under all conditions. Controllers raised several safety concerns, most of which pertained to the occurrence of near-term conflicts between autonomous and managed aircraft. These issues are being addressed through better compatibility between air and ground systems and refinements to air and ground procedures.
Barhydt, Richard↗
Backup control system (BUCS)
A backup software program is installed in an isolated portion in the memory of at least one of redundant computers. The backup program performs basically the same functions as the prime program but is dissimilarly programmed to prevent a common software error. Switchover to the backup program occurs either automatically in response to monitors, or manually by the operator (i.e. pilot) when he detects an anomaly.
Murphy, Richard D.↗
Erratum to "Solar Sources and Geospace Consequences of Interplanetary Magnetic Clouds Observed During Solar Cycle 23-Paper 1" [J. Atmos. Sol.-Terr. Phys. 70(2-4) (2008) 245-253]
One of the figures (Fig. 4) in "Solar sources and geospace consequences of interplanetary magnetic Clouds observed during solar cycle 23 -- Paper 1" by Gopalswamy et al. (2008, JASTP, Vol. 70, Issues 2-4, February 2008, pp. 245-253) is incorrect because of a software error in t he routine that was used to make the plot. The source positions of various magnetic cloud (MC) types are therefore not plotted correctly.
Gopalswamy, N.↗
XML-Based Generator of C++ Code for Integration With GUIs
An open source computer program has been developed to satisfy a need for simplified organization of structured input data for scientific simulation programs. Typically, such input data are parsed in from a flat American Standard Code for Information Interchange (ASCII) text file into computational data structures. Also typically, when a graphical user interface (GUI) is used, there is a need to completely duplicate the input information while providing it to a user in a more structured form. Heretofore, the duplication of the input information has entailed duplication of software efforts and increases in susceptibility to software errors because of the concomitant need to maintain two independent input-handling mechanisms. The present program implements a method in which the input data for a simulation program are completely specified in an Extensible Markup Language (XML)-based text file. The key benefit for XML is storing input data in a structured manner. More importantly, XML allows not just storing of data but also describing what each of the data items are. That XML file contains information useful for rendering the data by other applications. It also then generates data structures in the C++ language that are to be used in the simulation program. In this method, all input data are specified in one place only, and it is easy to integrate the data structures into both the simulation program and the GUI. XML-to-C is useful in two ways: 1. As an executable, it generates the corresponding C++ classes and 2. As a library, it automatically fills the objects with the input data values.
Hua, Hook↗
Survey of Verification and Validation Techniques for Small Satellite Software Development
The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation.
Small Satellite Technology↗
TechEdSat-13: The First Flight of an AI/ML Neuromorphic Processor
Neuromorphic processors, inspired by the wiring of the brain, permit certain classes of Artificial Intelligence/Machine Learning (AI/ML) algorithms to run far more efficiently. Ultimately, such systems will make the small- and nano-satellite platforms even more useful in terms of greatly improved power, communication and internal data management. In addition, on-board processing of images and data will help to not only rapidly interpret the information, but also reduce the amount of data that needs to be transmitted to ground stations. This initial flight experiment uses the Intel/ Loihi processor combined with a custom interface board and three communication channels to run the AI/ML scripts. These will vary with increasing length and complexity during the course of the mission. The algorithms will use the (at first) limited sensor data to ‘learn’ - with comparisons to similar architecture in comparable ground experiments. Some of the applications for successor flights in the TES-n flight series include Cognitive Communications, whereby the overall communication system is optimized per overflight – by optimizing timing and data transmission functions. Lastly, the performance of the Loihi 14nm process technology will be monitored for performance in the LEO radiation environment, thus looking for induced hardware and software errors. This information will help guide future radiation protection techniques to extend the lifetime and overall utility. The TES-13 is a 3U nanosat successfully launched by the Virgin Orbit Launcher-1 on January 13, 2022, and will presage more flights and AI/ML applications to come.
TechEdSat↗
Trajectory Specification Applied to Terminal Airspace
Despite major efforts to automate air traffic control (ATC), it is still performed by humans today. The complexity and safety-criticality of ATC makes it very difficult to safely automate, but it must be automated to increase airspace capacity (the density of traffic that can be safely managed) and airport throughput (the number of arrivals and departures that an airport can safely handle in a given period of time) beyond what is possible with human controllers. This paper presents the Trajectory Specification (TS) concept, which can help to safely automate ATC. TS is a method of specifying aircraft trajectories such that the position at any given time in flight is restricted to a precisely defined bounding space, removing all ambiguity as to where the flight is allowed to be. The bounding space or volume is determined by tolerances relative to a reference trajectory (position as a function of time). The tolerances are dynamic and are based on the aircraft navigation capabilities and the traffic situation. The tolerances can be a piecewise linear function of time or distance along the route, allowing the tolerances to vary as needed, typically increasing with time for departures and decreasing for arrivals. A Trajectory Specification Language (TSL) is proposed for communicating trajectories from aircraft to ATC as requests and from ATC to aircraft as assignments. The TS concept requires a new generation of airborne Flight Management Systems (FMS) that understand the TSL and can fly the assigned trajectories, but this paper focuses on the ATC functions and the prototype ATC algorithms and software that were developed to test the TS concept. Assuming conformance, TS can guarantee safe separation for an arbitrary length of time even in the event of an ATC system or communication outage. It can help to achieve the high level of safety and reliability needed for ATC automation, and it can also reduce the reliance on ATC backup systems for tactical conflict detection and resolution during normal operation. TS can be applied to any controlled airspace, including enroute, terminal, and urban airspace, but this paper presents algorithms and software for arrival spacing and conflict detection and resolution in the terminal airspace serving a major airport. In a fast-time simulation of a full day of traffic in a major terminal airspace, all conflicts were resolved in near real time, demonstrating the computational feasibility and the preliminary operational feasibility of the TS concept. This paper is a compilation of previous papers, and it adds significant information that was omitted from those papers due to length limitations. It also updates some of the results of those earlier papers due to algorithm refinements and corrections of minor software errors.
air traffic control, trajectory↗