Search NASA⌕ Search

SEARCH · Search NASA

Results for “software testing”

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 487 records · Page 27
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Developing interpretable models with optimized set reduction for identifying high risk software components

Applying equal testing and verification effort to all parts of a software system is not very efficient, especially when resources are limited and scheduling is tight. Therefore, one needs to be able to differentiate low/high fault frequency components so that testing/verification effort can be concentrated where needed. Such a strategy is expected to detect more faults and thus improve the resulting reliability of the overall system. This paper presents the Optimized Set Reduction approach for constructing such models, intended to fulfill specific software engineering needs. Our approach to classification is to measure the software system and build multivariate stochastic models for predicting high risk system components. We present experimental results obtained by classifying Ada components into two classes: is or is not likely to generate faults during system and acceptance test. Also, we evaluate the accuracy of the model and the insights it provides into the error making process.

Briand, Lionel C.↗
NASA NTRS1994

Model-based software process improvement

The activities of a field test site for the Software Engineering Institute's software process definition project are discussed. Products tested included the improvement model itself, descriptive modeling techniques, the CMM level 2 framework document, and the use of process definition guidelines and templates. The software process improvement model represents a five stage cyclic approach for organizational process improvement. The cycles consist of the initiating, diagnosing, establishing, acting, and leveraging phases.

Zettervall, Brenda T.↗
NASA NTRS1976

Application of LANDSAT system for improving methodology for inventory and classification of wetlands

The author has identified the following significant results. A newly developed software system for generating statistics on surface water features was tested using LANDSAT data acquired previous to 1975. This software test provided a satisfactory evaluation of the system and also allowed expansion of data base on prairie water features. The software system recognizes water on the basis of a classification algorithm. This classification is accomplished by level thresholding a single near infrared data channel. After each pixel is classified as water or nonwater, the software system then recognizes ponds or lakes as sets of contiguous pixels or as single isolated pixels in the case of very small ponds. Pixels are considered to be contiguous if they are adjacent between successive scan lines. After delineating each water feature, the software system then assigns the feature a position based upon a geographic grid system and calculates the feature's planimetric area, its perimeter, and a parameter known as the shape factor.

Gilmer, D. S.↗
NASA NTRS2013

Assessment Environment for Complex Systems Software Guide

This Software Guide (SG) describes the software developed to test the Assessment Environment for Complex Systems (AECS) by the West Virginia High Technology Consortium (WVHTC) Foundation's Mission Systems Group (MSG) for the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD). This software is referred to as the AECS Test Project throughout the remainder of this document. AECS provides a framework for developing, simulating, testing, and analyzing modern avionics systems within an Integrated Modular Avionics (IMA) architecture. The purpose of the AECS Test Project is twofold. First, it provides a means to test the AECS hardware and system developed by MSG. Second, it provides an example project upon which future AECS research may be based. This Software Guide fully describes building, installing, and executing the AECS Test Project as well as its architecture and design. The design of the AECS hardware is described in the AECS Hardware Guide. Instructions on how to configure, build and use the AECS are described in the User's Guide. Sample AECS software, developed by the WVHTC Foundation, is presented in the AECS Software Guide. The AECS Hardware Guide, AECS User's Guide, and AECS Software Guide are authored by MSG. The requirements set forth for AECS are presented in the Statement of Work for the Assessment Environment for Complex Systems authored by NASA Dryden Flight Research Center (DFRC). The intended audience for this document includes software engineers, hardware engineers, project managers, and quality assurance personnel from WVHTC Foundation (the suppliers of the software), NASA (the customer), and future researchers (users of the software). Readers are assumed to have general knowledge in the field of real-time, embedded computer software development.

tests↗
NASA NTRS2024

X-57 Cruise Motor GVT Using Fixed-Base Correction Technique

The National Aeronautics and Space Administration (NASA) Armstrong Flight Research Center (AFRC) completed a modal survey of the X-57 Maxwell aircraft cruise motor system to help inform cruise motor redesign efforts. X-57 Maxwell was an electric propulsion demonstrator aircraft developed by NASA to inform airworthiness standards for electrified-aircraft. The cruise motor system modal survey was completed in spring of 2023 utilizing the fixed-base correction (FBC) ground vibration test (GVT) technique developed by ATA Engineering, to decouple the motor modes from the aircraft modes. Previously during the full aircraft GVT, a detailed modal assessment of the cruise motors was not performed. Owing to the X-57 project’s phase in the aircraft development cycle when the motor redesign effort occurred, the cruise motor GVT could only be performed with the cruise motor system installed on the aircraft, with most of its installation hardware (wiring, baffling, sensors, etc.) attached. An impact hammer was used to provide excitation input at various locations within the tight confines of the cruise motor installation. To better support motor redesign efforts, the FBC methodology was utilized to fix, separate and de-couple the cruise motor modes from aircraft modal response. During the GVT, this required additional impact tap tests on candidate fixed-boundary points for each degree of freedom (DOF) to be fixed. Additional triaxial accelerometers installed at the candidate points were used to compute frequency response functions (FRFs) in X, Y, and Z directions to enable those DOFs to be numerically fixed. Test data was acquired using Hottinger Brüel & Kjær’s LAN-XI data acquisition hardware and BK Connect software. FBC post-test processing was performed using the Structural Modification Using Frequency Response Functions (SMURF) technique with ATA Engineering’s Interface between MATLAB, Analysis, Test (IMAT) software. Utilizing the FBC technique relieved test engineers from having to instrument the entire aircraft to identify and separate aircraft response from cruise motor modes of interest. The FBC technique also permitted structural analysis engineers to omit secondary components from their finite element model (FEM) of the cruise motor system. This FBC modal survey was successful, and the first time NASA AFRC utilized the FBC method on an aircraft rather than a test fixture, and also using an impact hammer rather than multiple shakers allowing significant project schedule and cost savings

Modal Survey↗
NASA NTRS1989

Experiments in fault tolerant software reliability

Twenty functionally equivalent programs were built and tested in a multiversion software experiment. Following unit testing, all programs were subjected to an extensive system test. In the process sixty-one distinct faults were identified among the versions. Less than 12 percent of the faults exhibited varying degrees of positive correlation. The common-cause (or similar) faults spanned as many as 14 components. However, a majority of these faults were trivial, and easily detected by proper unit and/or system testing. Only two of the seven similar faults were difficult faults, and both were caused by specification ambiguities. One of these faults exhibited variable identical-and-wrong response span, i.e. response span which varied with the testing conditions and input data. Techniques that could have been used to avoid the faults are discussed. For example, it was determined that back-to-back testing of 2-tuples could have been used to eliminate about 90 percent of the faults. In addition, four of the seven similar faults could have been detected by using back-to-back testing of 5-tuples. It is believed that most, if not all, similar faults could have been avoided had the specifications been written using more formal notation, the unit testing phase was subject to more stringent standards and controls, and better tools for measuring the quality and adequacy of the test data (e.g. coverage) were used.

Mcallister, David F.↗
NASA NTRS2012

Improving Flight Software Module Validation Efforts : a Modular, Extendable Testbed Software Framework

Ever since Explorer-1, the United States' first Earth satellite, was developed and launched in 1958, JPL has developed many more spacecraft, including landers and orbiters. While these spacecraft vary greatly in their missions, capabilities,and destination, they all have something in common. All of the components of these spacecraft had to be comprehensively tested. While thorough testing is important to mitigate risk, it is also a very expensive and time consuming process. Thankfully,since virtually all of the software testing procedures for SMAP are computer controlled, these procedures can be automated. Most people testing SMAP flight software (FSW) would only need to write tests that exercise specific requirements and then check the filtered results to verify everything occurred as planned. This gives developers the ability to automatically launch tests on the testbed, distill the resulting logs into only the important information, generate validation documentation, and then deliver the documentation to management. With many of the steps in FSW testing automated, developers can use their limited time more effectively and can validate SMAP FSW modules quicker and test them more rigorously. As a result of the various benefits of automating much of the testing process, management is considering this automated tools use in future FSW validation efforts.

flight software testing↗
NASA NTRS1988

Wall adjustment strategy software for use with the NASA Langley 0.3-meter transonic cryogenic tunnel adaptive wall test section

The Wall Adjustment Strategy (WAS) software provides successful on-line control of the 2-D flexible walled test section of the Langley 0.3-m Transonic Cryogenic Tunnel. This software package allows the level of operator intervention to be regulated as necessary for research and production type 2-D testing using and Adaptive Wall Test Section (AWTS). The software is designed to accept modification for future requirements, such as 3-D testing, with a minimum of complexity. The WAS software described is an attempt to provide a user friendly package which could be used to control any flexible walled AWTS. Control system constraints influence the details of data transfer, not the data type. Then this entire software package could be used in different control systems, if suitable interface software is available. A complete overview of the software highlights the data flow paths, the modular architecture of the software and the various operating and analysis modes available. A detailed description of the software modules includes listings of the code. A user's manual is provided to explain task generation, operating environment, user options and what to expect at execution.

Wolf, Stephen W. D.↗
NASA NTRS1996

A Description of the Software Element of the NASA EME Flight Tests

In support of NASA's Fly-By-Light/Power-By-Wire (FBL/PBW) program, a series of flight tests were conducted by NASA Langley Research Center in February, 1995. The NASA Boeing 757 was flown past known RF transmitters to measure both external and internal radiated fields. The aircraft was instrumented with strategically located sensors for acquiring data on shielding effectiveness and internal coupling. The data are intended to support computational and statistical modeling codes used to predict internal field levels of an electromagnetic environment (EME) on aircraft. The software was an integral part of the flight tests, as well as the data reduction process. The software, which provided flight test instrument control, data acquisition, and a user interface, executes on a Hewlett Packard (HP) 300 series workstation and uses BP VEEtest development software and the C programming language. Software tools were developed for data processing and analysis, and to provide a database organized by frequency bands, test runs, and sensors. This paper describes the data acquisition system on board the aircraft and concentrates on the software portion. Hardware and software interfaces are illustrated and discussed. Particular attention is given to data acquisition and data format. The data reduction process is discussed in detail to provide insight into the characteristics, quality, and limitations of the data. An analysis of obstacles encountered during the data reduction process is presented.

Koppen, Sandra V.↗
NASA NTRS2018

NOS3: NASA Operational Simulator for Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of open-source software tools to aid in areas such as software development, integration & test (I&T), mission operations/training, verification and validation (V&V), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, operational interface/ground software, dynamics and environment simulations, and software-based hardware models. NOS3 has just recently been open-sourced by NASA and is available for immediate use. It enables the development of flight software (FSW) early in the project life cycle when hardware availability is limited. Small satellite development suffers from extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETUs). To alleviate the need to provide a hardware test-bed for each developer/tester, NOS3 hardware models are based upon characteristic data or manufacturer's data sheets for each individual component. The NOS3 hardware models' fidelity is such that FSW executes unaware that physical hardware is not present. This allows FSW binaries to be compiled for both the simulation environment and the flight computer without changing the FSW source code. For hardware models that provide data which is dependent upon the environment and spacecraft dynamics, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulator) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for V&V of larger missions such as James Webb Space Telescope (JWST). As hardware is selected and becomes available, drivers can be added to the NOS3 environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. NOS3 was actively used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat and the Lunar IceCube CubeSat. As NOS3 matures, hardware models have been added for common small satellite components such as GPS receivers, electrical power systems and batteries, and antenna systems.

Suder, Mark↗
NASA NTRS1989

The use of real-time, hardware-in-the-loop simulation in the design and development of the new Hughes HS601 spacecraft attitude control system

Realtime simulation and hardware-in-the-loop testing is being used extensively in all phases of the design, development, and testing of the attitude control system (ACS) for the new Hughes HS601 satellite bus. Realtime, hardware-in-the-loop simulation, integrated with traditional analysis and pure simulation activities is shown to provide a highly efficient and productive overall development program. Implementation of high fidelity simulations of the satellite dynamics and control system algorithms, capable of real-time execution (using applied Dynamics International's System 100), provides a tool which is capable of being integrated with the critical flight microprocessor to create a mixed simulation test (MST). The MST creates a highly accurate, detailed simulated on-orbit test environment, capable of open and closed loop ACS testing, in which the ACS design can be validated. The MST is shown to provide a valuable extension of traditional test methods. A description of the MST configuration is presented, including the spacecraft dynamics simulation model, sensor and actuator emulators, and the test support system. Overall system performance parameters are presented. MST applications are discussed; supporting ACS design, developing on-orbit system performance predictions, flight software development and qualification testing (augmenting the traditional software-based testing), mission planning, and a cost-effective subsystem-level acceptance test. The MST is shown to provide an ideal tool in which the ACS designer can fly the spacecraft on the ground.

Slafer, Loren I.↗
NASA NTRS2018

Leveraging Commercial Software Defined Radio for Low Cost Deep Space Testing

In a typical space mission development life cycle, there is a stage where the spacecraft needs to test against the ground station for interface compatibility to ensure that the spacecraft will be properly tracked after launch. This testing normally requires the spacecraft team to bring their flight equipment to the ground station facility. While recognizing that testing with actual flight or engineering module is the most preferred option because of maximum fidelity, there are occasion when the use of actual flight hardware is a logistically challenge because of spacecraft development. Having another test tool that can emulate the spacecraft signal – by recording the signal transmitted by the spacecraft and regenerate an RF signal for ground system testing - would be very useful. It is even more an attractive option if such spacecraft emulator is inexpensive and highly portable. In this paper, we describe a low-cost, light-weight recorder/playback assembly (RPA) that supports deep space missions testing. The equipment leverages on commercially available software defined radios (SDR) and public-domain software. The RPA has been used to support two missions. One effort is to validate that the Uchinoura 34-m tracking station of the Japanese Aerospace Exploration Agency (JAXA) would be able to track the upcoming NASA Exploration Mission 1 (EM-1) spacecraft, scheduled for launch in 2019. The second effort is to help with the testing and certification of the 21-m antenna ground station at the Morehead State University (MSU) in Kentucky, United States, prior to the time when the Lunar IceCube spacecraft is ready for actual compatibility testing. The RPA also enables students/staff training of the new ground station, using the RPA signal as test input into the system. This low-cost test signal allows the MSU team to save money on not having to develop a full-scale self-generated telemetry test signal source.

White, Leslie↗
NASA NTRS1987

Biaxial thermo-mechanical fatigue

Stress-strain and durability information is often desirable for situations in which strain and temperature are changing simultaneously. To obtain such information, strain controlled uniaxial push-pull tests have typically been done. In order to control the mechanical strain, it is necessary in such tests to compute the mechanical strain from the total measured strain using measured temperature and the thermal expansion properties of the specimen. A system for conducting torsional thermomechanical tests is described which has the great advantage that the torsional strain is unaffected by the changing temperature and thus real time computations of quantities is not required for control of the test and the mechanical strain need not be determined from the subtraction of two measured qnantities as is the case in the uniaxial test. In addition to describing torsional thermomechanical tests, guidelines for software to be used in running biaxial thermomechanical tests will also be presented.

Jordan, Eric H.↗
NASA NTRS2001

Life Testing of the Hollow Cathode Plasma Contactor for the ProSEDS Mission

The Propulsive Small Expendable Deployer System (ProSEDS) mission is designed to provide an on-orbit demonstration of the electrodynamic propulsion capabilities of tethers in space. The ProSEDS experiment will be a secondary payload on a Delta 11 unmanned expendable booster. A 5-km conductive tether is attached to the Delta 11 second stage and collects current from the low Earth orbit (LEO) plasma. A hollow cathode plasma contactor emits the collected electrons from the Delta II, completing the electrical circuit with the ambient plasma. The current flowing through the tether generates thrust based on the Lorentz Force Law. The thrust will be generated opposite to the velocity vector, slowing down the spacecraft and causing it to de-orbit in approximately 14 days compared to the normal 6 months. A 10-km non-conductive tether is between the conductive tether and an endmass containing several scientific instruments. The ProSEDS mission lifetime was set at I day because most of the primary objectives can be met in that time. The extended ProSEDS mission will be for as many days as possible, until the Delta 11 second stage burns up or the tether is severed by a micrometeoroid or space debris particle. The Hollow Cathode Plasma Contactor (HCPC) unit has been designed for a 12-day mission. Because of the science requirements to measure the background ambient plasma, the HCPC must operate on a duty cycle. Later in the ProSEDS mission, the HCPC is operated in a manner to allow charging of the secondary battery. Due to the unusual operating requirements by the ProSEDS mission, a development unit of the HCPC was built for thorough testing. This developmental unit was tested for a simulated ProSEDS mission, with measurements of the ability to start and stop during the duty cycle. These tests also provided valuable data for the ProSEDS software requirements. Qualification tests of the HCPC flight hardware are also discussed.

Vaughn, Jason A.↗
NASA NTRS1991

Development of a calibrated software reliability model for flight and supporting ground software for avionic systems

The object of this project was to develop and calibrate quantitative models for predicting the quality of software. Reliable flight and supporting ground software is a highly important factor in the successful operation of the space shuttle program. The models used in the present study consisted of SMERFS (Statistical Modeling and Estimation of Reliability Functions for Software). There are ten models in SMERFS. For a first run, the results obtained in modeling the cumulative number of failures versus execution time showed fairly good results for our data. Plots of cumulative software failures versus calendar weeks were made and the model results were compared with the historical data on the same graph. If the model agrees with actual historical behavior for a set of data then there is confidence in future predictions for this data. Considering the quality of the data, the models have given some significant results, even at this early stage. With better care in data collection, data analysis, recording of the fixing of failures and CPU execution times, the models should prove extremely helpful in making predictions regarding the future pattern of failures, including an estimate of the number of errors remaining in the software and the additional testing time required for the software quality to reach acceptable levels. It appears that there is no one 'best' model for all cases. It is for this reason that the aim of this project was to test several models. One of the recommendations resulting from this study is that great care must be taken in the collection of data. When using a model, the data should satisfy the model assumptions.

Lawrence, Stella↗
NASA NTRS1976

IPCS implications for future supersonic transport aircraft

The Integrated Propulsion Control System (IPCS) demonstrates control of an entire supersonic propulsion module - inlet, engine afterburner, and nozzle - with an HDC 601 digital computer. The program encompasses the design, build, qualification, and flight testing of control modes, software, and hardware. The flight test vehicle is an F-111E airplane. The L.H. inlet and engine will be operated under control of a digital computer mounted in the weapons bay. A general description and the current status of the IPCS program are given.

Billig, L. O.↗
NASA NTRS1978

Digital Fly-By-Wire Flight Control Validation Experience

The experience gained in digital fly-by-wire technology through a flight test program being conducted by the NASA Dryden Flight Research Center in an F-8C aircraft is described. The system requirements are outlined, along with the requirements for flight qualification. The system is described, including the hardware components, the aircraft installation, and the system operation. The flight qualification experience is emphasized. The qualification process included the theoretical validation of the basic design, laboratory testing of the hardware and software elements, systems level testing, and flight testing. The most productive testing was performed on an iron bird aircraft, which used the actual electronic and hydraulic hardware and a simulation of the F-8 characteristics to provide the flight environment. The iron bird was used for sensor and system redundancy management testing, failure modes and effects testing, and stress testing in many cases with the pilot in the loop. The flight test program confirmed the quality of the validation process by achieving 50 flights without a known undetected failure and with no false alarms.

Szalai, K. J.↗
NASA NTRS1984

Investigation of a nozzle instability on an F100 engine equipped with a digital electronic engine control

An instability in the nozzle of the F100 engine, equipped with a digital electronic engine control (DEEC), was observed during a flight evaluation on an F-15 aircraft. The instability occurred in the upper left hand corner (ULMC) of the flight envelope during augmentation. The instability was not predicted by stability analysis, closed-loop simulations of the the engine, or altitude testing of the engine. The instability caused stalls and augmentor blowouts. The nozzle instability and the altitude testing are described. Linear analysis and nonlinear digital simulation test results are presented. Software modifications on further flight test are discussed.

Burcham, F. W., Jr.↗