Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software quality”

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

WTEC monograph on instrumentation, control and safety systems of Canadian nuclear facilities

This report updates a 1989-90 survey of advanced instrumentation and controls (I&C) technologies and associated human factors issues in the U.S. and Canadian nuclear industries carried out by a team from Oak Ridge National Laboratory (Carter and Uhrig 1990). The authors found that the most advanced I&C systems are in the Canadian CANDU plants, where the newest plant (Darlington) has digital systems in almost 100 percent of its control systems and in over 70 percent of its plant protection system. Increased emphasis on human factors and cognitive science in modern control rooms has resulted in a reduced workload for the operators and the elimination of many human errors. Automation implemented through digital instrumentation and control is effectively changing the role of the operator to that of a systems manager. The hypothesis that properly introducing digital systems increases safety is supported by the Canadian experience. The performance of these digital systems has been achieved using appropriate quality assurance programs for both hardware and software development. Recent regulatory authority review of the development of safety-critical software has resulted in the creation of isolated software modules with well defined interfaces and more formal structure in the software generation. The ability of digital systems to detect impending failures and initiate a fail-safe action is a significant safety issue that should be of special interest to nuclear utilities and regulatory authorities around the world.

Uhrig, Robert E.↗
NASA NTRS1994

Test/score/report: Simulation techniques for automating the test process

A Test/Score/Report capability is currently being developed for the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) system which will automate testing of the Goddard Space Flight Center (GSFC) Payload Operations Control Center (POCC) and Mission Operations Center (MOC) software in three areas: telemetry decommutation, spacecraft command processing, and spacecraft memory load and dump processing. Automated computer control of the acceptance test process is one of the primary goals of a test team. With the proper simulation tools and user interface, the task of acceptance testing, regression testing, and repeatability of specific test procedures of a ground data system can be a simpler task. Ideally, the goal for complete automation would be to plug the operational deliverable into the simulator, press the start button, execute the test procedure, accumulate and analyze the data, score the results, and report the results to the test team along with a go/no recommendation to the test team. In practice, this may not be possible because of inadequate test tools, pressures of schedules, limited resources, etc. Most tests are accomplished using a certain degree of automation and test procedures that are labor intensive. This paper discusses some simulation techniques that can improve the automation of the test process. The TASS system tests the POCC/MOC software and provides a score based on the test results. The TASS system displays statistics on the success of the POCC/MOC system processing in each of the three areas as well as event messages pertaining to the Test/Score/Report processing. The TASS system also provides formatted reports documenting each step performed during the tests and the results of each step. A prototype of the Test/Score/Report capability is available and currently being used to test some POCC/MOC software deliveries. When this capability is fully operational it should greatly reduce the time necessary to test a POCC/MOC software delivery, as well as improve the quality of the test process.

Hageman, Barbara H.↗
NASA NTRS1993

Upgrades to the NOAA/NESDIS automated Cloud-Motion Vector system

The latest version of the automated cloud motion vector software has yielded significant improvements in the quality of the GOES cloud-drift winds produced operationally by NESDIS. Cloud motion vectors resulting from the automated system are now equal or superior in quality to those which had the benefit of manual quality control a few years ago. The single most important factor in this improvement has been the upgraded auto-editor. Improved tracer selection procedures eliminate targets in difficult regions and allow a higher target density and therefore enhanced coverage in areas of interest. The incorporation of the H2O-intercept height assignment method allows an adequate representation of the heights of semi-transparent clouds in the absence of a CO2-absorption channel. Finally, GOES-8 water-vapor motion winds resulting from the automated system are superior to any done previously by NESDIS and should now be considered as an operational product.

Nieman, Steve↗
NASA NTRS1995

TOPEX/Poseidon Precision Orbit Determination Using Combined GPS, SLR, and DORIS

TOPEX/Poseidon (T/P) is a joint spaceborne oceanographic mission of U.W. NASA and France CNES design launched August 10, 1992. The satellite has a variety tracking systems for both operational and precision orbit determination. Three precise tracking systems: Satellite Laser Ranging (SLR), Doppler Orbitography and Radiopositioning Integrated by Satellite (DORIS), and Global Positioning System (GPS) provide high quality measurements essential for reconstructing the T/P orbital height with centimeter precision. This paper presents results of simultaneously processing all three data types to exploit the inherent strength of each in a combined solution. SLR and DORIS are routinely combined to provide orbit solutions for the T/P science team. GPS orbit solutions are produced as part of the first demonstration flight of a high quality spaceborne GPS receiver. Coordinate frame and software system differences between the combined SLR/DORIS orbits and the GPS orbits induce orbital height differences of 2 to 3 centimeters. Combining the three data types within a single software system permits removal of software system differences while obtaining coordinate frame calibration information. These calibrations will aid future spaceborne GPS missions that are not complemented with SLR and/or DORIS.

TOPEX/Poseidon↗
NASA NTRS2013

Surface Inspection Tool for Optical Detection of Surface Defects

The Space Shuttle Orbiter windows were damaged both by micrometeor impacts and by handling, and required careful inspection before they could be reused. The launch commit criteria required that no defect be deeper than a critical depth. The shuttle program used a refocus microscope to perform a quick pass/fail determination, and then followed up with mold impressions to better quantify any defect. However, the refocus microscope is slow and tedious to use due to its limited field of view, only focusing on one small area of glass at a time. Additionally, the unit is bulky and unable to be used in areas with tight access, such as defects near the window frame or on the glass inside the Orbiter due to interference with the dashboard. The surface inspection tool is a low-profile handheld instrument that provides two digital video images on a computer for monitoring surface defects. The first image is a wide-angle view to assist the user in locating defects. The second provides an enlarged view of a defect centered in the window of the first image. The focus is adjustable for each of the images. However, the enlarged view was designed to have a focal plane with a short depth. This allows the user to get a feel for the depth of different parts of the defect under inspection as the focus control is varied. A light source is also provided to illuminate the defect, precluding the need for separate lighting tools. The software provides many controls to adjust image quality, along with the ability to zoom digitally the images and to capture and store them for later processing.

Nurge, Mark↗
NASA NTRS2017

Lessons from Astrobiological Planetary Analogue Exploration in Iceland: Biomarker Assay Performance and Downselection

Understanding the sensitivity of biomarker assays to the local physicochemical environment, and the underlying spatial distribution of the target biomarkers in 'homogeneous' environments, can increase mission science return. We have conducted four expeditions to Icelandic Mars analogue sites in which an increasingly refined battery of physicochemical measurements and biomarker assays were performed, staggered with scouting of further sites. Completed expeditions took place in 2012 (location scouting and field assay use testing), 2013 (sampling of two major sites with three assays and observational physicochemical measurements), 2015 (repeat sampling of prior sites and one new site, scouting of new sites, three assays and three instruments), and 2016 (preliminary sampling of new sites with analysis of returned samples). Target sites were geologically recent basaltic lava flows, and sample loci were arranged in hierarchically nested grids at 10 cm, 1 m, 10 m, 100 m, and >1 km order scales, subject to field constraints. Assays were intended to represent a diversity of potential biomarker types (cell counting via nucleic acid staining and fluorescence microscopy, ATP quantification via luciferase luminescence, and relative DNA quantification with simple domain-level primers) rather a specific mission science target, and were selected to reduce laboratory overhead, require limited consumables, and allow rapid turnaround. All analytical work was performed in situ or in a field laboratory within a day's travel of the field sites unless otherwise noted. We have demonstrated the feasibility of performing ATP quantification and qPCR analysis in a field-based laboratory with single-day turnaround. The ATP assay was generally robust and reliable and required minimal field equipment and training to produce a large amount of useful data. DNA was successfully extracted from all samples, but the serial-batch nature of qPCR significantly limited the number of primers (hence classifications) and replicates that could be run in a single day. Fluorescence microscopy did not prove feasible under the same constraints, primarily due to the large number of person-hours required to view, analyze, and record results from the images; however, this could be mitigated with higher-quality imaging instruments and appropriate image analysis software.

Planetary↗
NASA NTRS2018

Computer Programming Resources 2018

The document is a compilation of Computer Programming resources. It is geared toward front-end and back-end web development. It specializes on an ongoing project to create a website for the Safety and Mission Assurance Directorate. The Quality Assurance System (QAS) is intended to improve the overall quality and efficiency of communication among NASA Quality Assurance Engineers and Contractors. The use of QAS software will be limited to NASA Kennedy Space Center and Contractors. It is accessible through the KSC network.

Confluence↗
NASA NTRSDate not supplied

Simulated Ice Shapes on the High Lift Common Research Model Using LEWICE3D

Computational icing tools consist of predicting two distinct problems, the dry air aerodynamics around the iced or uniced vehicle and the accretion of ice due to inclement weather. A desire exists to advance these tools such that they can be reliably used earlier in the design process to limit the need for more costly flight and wind tunnel testing. To achieve these goals the computational tools need to be benchmarked and validated against high quality experimental data sets to raise the software’s Technology Readiness Level. An ongoing collaborative effort between NASA and Boeing Commercial Airplanes is focused on obtaining this required experimental data and subsequently benchmarking and/or validating the tools that predict the aerodynamics around the iced and uniced vehicle. Currently the scope of this effort is focused on the usage of simulated ice shapes to be representative of the iced vehicle. This presentation discusses the generation of those simulated ice shapes.

Icing↗
NASA NTRS1986

The March 1985 demonstration of the fiducial network concept for GPS geodesy: A preliminary report

The first field tests in preparation for the NASA Global Positioning System (GPS) Caribbean Initiative were conducted in late March and Early April of 1985. The GPS receivers were located at the POLARIS Very Long Base Interferometry (VLBI) stations at Westford, Massachusetts; Richmond, Florida; and Ft. Davis, Texas; and at the Mojave, Owens Valley, and Hat Creek VLBI stations in California. Other mobile receivers were placed near Mammoth Lakes, California; Pt. Mugu, California; Austin, Texas; and Dahlgren, Virginia. These sites were equipped with a combination of GPS receiver types, including SERIES-X, TI-4100 and AFGL dual frequency receivers. The principal objectives of these tests were the demonstration of the fiducial network concept for precise GPS geodesy, the performance assessment of the participating GPS receiver types, and to conduct the first in a series of experiments to monitor ground deformation in the Mammoth Lakes-Long Valley caldera region in California. Other objectives included the testing of the water vapor radiometers for the calibration of GPS data, the development of efficient procedures for planning and coordinating GPS field exercise, the establishment of institutional interfaces for future cooperating ventures, the testing of the GPS Data Analysis Software (GIPSY, for GPS Inferred Positioning SYstem), and the establishment of a set of calibration baselines in California. Preliminary reports of the success of the field tests, including receiver performance and data quality, and on the status of the data analysis software are given.

Davidson, J. M.↗
NASA NTRS1992

Independent verification and validation for Space Shuttle flight software

The Committee for Review of Oversight Mechanisms for Space Shuttle Software was asked by the National Aeronautics and Space Administration's (NASA) Office of Space Flight to determine the need to continue independent verification and validation (IV&V) for Space Shuttle flight software. The Committee found that the current IV&V process is necessary to maintain NASA's stringent safety and quality requirements for man-rated vehicles. Therefore, the Committee does not support NASA's plan to eliminate funding for the IV&V effort in fiscal year 1993. The Committee believes that the Space Shuttle software development process is not adequate without IV&V and that elimination of IV&V as currently practiced will adversely affect the overall quality and safety of the software, both now and in the future. Furthermore, the Committee was told that no organization within NASA has the expertise or the manpower to replace the current IV&V function in a timely fashion, nor will building this expertise elsewhere necessarily reduce cost. Thus, the Committee does not recommend moving IV&V functions to other organizations within NASA unless the current IV&V is maintained for as long as it takes to build comparable expertise in the replacing organization.

Source record↗
NASA NTRS2014

Verification and Validation of the General Mission Analysis Tool (GMAT)

This paper describes the processes and results of Verification and Validation (V&V) efforts for the General Mission Analysis Tool (GMAT). We describe the test program and environments, the tools used for independent test data, and comparison results. The V&V effort produced approximately 13,000 test scripts that are run as part of the nightly buildtest process. In addition, we created approximately 3000 automated GUI tests that are run every two weeks. Presenting all test results are beyond the scope of a single paper. Here we present high-level test results in most areas, and detailed test results for key areas. The final product of the V&V effort presented in this paper was GMAT version R2013a, the first Gold release of the software with completely updated documentation and greatly improved quality. Release R2013a was the staging release for flight qualification performed at Goddard Space Flight Center (GSFC) ultimately resulting in GMAT version R2013b.

GMAT↗
NASA NTRS1988

Towards a comprehensive framework for reuse: A reuse-enabling software evolution environment

Reuse of products, processes and knowledge will be the key to enable the software industry to achieve the dramatic improvement in productivity and quality required to satisfy the anticipated growing demand. Although experience shows that certain kinds of reuse can be successful, general success has been elusive. A software life-cycle technology which allows broad and extensive reuse could provide the means to achieving the desired order-of-magnitude improvements. The scope of a comprehensive framework for understanding, planning, evaluating and motivating reuse practices and the necessary research activities is outlined. As a first step towards such a framework, a reuse-enabling software evolution environment model is introduced which provides a basis for the effective recording of experience, the generalization and tailoring of experience, the formalization of experience, and the (re-)use of experience.

Basili, V. R.↗
NASA NTRS1991

Support for comprehensive reuse

Reuse of products, processes, and other knowledge will be the key to enable the software industry to achieve the dramatic improvement in productivity and quality required to satisfy the anticipated growing demands. Although experience shows that certain kinds of reuse can be successful, general success has been elusive. A software life-cycle technology which allows comprehensive reuse of all kinds of software-related experience could provide the means to achieving the desired order-of-magnitude improvements. A comprehensive framework of models, model-based characterization schemes, and support mechanisms for better understanding, evaluating, planning, and supporting all aspects of reuse are introduced.

Basili, V. R.↗
NASA NTRS2012

Test Driven Development of Scientific Models

Test-Driven Development (TDD) is a software development process that promises many advantages for developer productivity and has become widely accepted among professional software engineers. As the name suggests, TDD practitioners alternate between writing short automated tests and producing code that passes those tests. Although this overly simplified description will undoubtedly sound prohibitively burdensome to many uninitiated developers, the advent of powerful unit-testing frameworks greatly reduces the effort required to produce and routinely execute suites of tests. By testimony, many developers find TDD to be addicting after only a few days of exposure, and find it unthinkable to return to previous practices. Of course, scientific/technical software differs from other software categories in a number of important respects, but I nonetheless believe that TDD is quite applicable to the development of such software and has the potential to significantly improve programmer productivity and code quality within the scientific community. After a detailed introduction to TDD, I will present the experience within the Software Systems Support Office (SSSO) in applying the technique to various scientific applications. This discussion will emphasize the various direct and indirect benefits as well as some of the difficulties and limitations of the methodology. I will conclude with a brief description of pFUnit, a unit testing framework I co-developed to support test-driven development of parallel Fortran applications.

Clune, Thomas L.↗
NASA NTRS2017

Wearable Biosensor Monitor to Support Autonomous Crew Health and Readiness to Perform

For future human exploration missions, NASA needs a health monitoring system composed of hardware that is compact, fully interoperable with an integrated data management system, and requires minimal consumables. Such a system will be achieved through the integration of small, easy to use biomedical sensors that will have the ability to measure, store and transmit physiological parameters during operational and ambulatory activity. Since 2012, the Canadian Space Agency (CSA) has been active in funding the development of wearable biomonitoring sensors. The Astroskin is the first prototype and consists of a shirt-based garment and headband with embedded sensors, and associated software and technology that measure vital signs, sleep quality and activity level of the wearer. NASA and CSA have been collaborating since 2014 to test and validate this system in a lab environment at Ames Research Center and more recently in the Human Exploration Research Analog (HERA) located at Johnson Spaceflight Center. Specific objectives of the HERA study were: 1) to assess the performance of the Astroskin biosensor system for long-term health monitoring (24-hours) capabilities and during exercise as a measure of crew fitness; 2) to obtain crew feedback on comfort and usability of the Astroskin system; 3) to demonstrate performance of Bluetooth communication during real-time transmission and for verification of data in this environment; and 4) to obtain baseline data for further development of algorithms and tools that facilitate decision support for diagnosing and monitoring of a sick or injured crewmember. HERA Campaign 3 included four missions (each 30-days in duration) with four crewmembers assigned to each mission. A total of 9 men and 7 women participated in the Astroskin evaluation that included continuous physiological monitoring (24-hours) on mission days MD-11, MD1 (high workload), MD15 (low workload), MD19, MD29, and MD+7. Mission days 19 and 29 also included 30 minutes of sub-maximal exercise on a cycle ergometer. Following each 24-hour monitoring session crew physiological data were downloaded to laptops and each crewmember completed a 28 question survey on their experiences with the Astroskin hardware and software. This presentation will focus on lessons learned from the HERA missions. Specifically it will address Astroskin system performance in terms of data loss and data quality (no comparison to lab standard devices), wireless communication with the onboard mobile device, crew usability and comfort, and future development of a next generation biomonitoring system.

crew fitness↗
NASA NTRS2003

Patterns of software defect data on spacecraft

The identification of patterns of software defect data yields insights into improving the quality of both operational and future spacecraft. This paper describes the results of applying this technique to both post-launch and pre-launch spacecraft. It then describes four key challenges that remain to achieving fuller utilization of defect analysis in future systems.

software defect defect analysis defect data↗
NASA NTRS1991

Ada and the rapid development lifecycle

JPL is under contract, through NASA, with the US Army to develop a state-of-the-art Command Center System for the US European Command (USEUCOM). The Command Center System will receive, process, and integrate force status information from various sources and provide this integrated information to staff officers and decision makers in a format designed to enhance user comprehension and utility. The system is based on distributed workstation class microcomputers, VAX- and SUN-based data servers, and interfaces to existing military mainframe systems and communication networks. JPL is developing the Command Center System utilizing an incremental delivery methodology called the Rapid Development Methodology with adherence to government and industry standards including the UNIX operating system, X Windows, OSF/Motif, and the Ada programming language. Through a combination of software engineering techniques specific to the Ada programming language and the Rapid Development Approach, JPL was able to deliver capability to the military user incrementally, with comparable quality and improved economies of projects developed under more traditional software intensive system implementation methodologies.

Deforrest, Lloyd↗
NASA NTRS1992

Software assurance standard

This standard specifies the software assurance program for the provider of software. It also delineates the assurance activities for the provider and the assurance data that are to be furnished by the provider to the acquirer. In any software development effort, the provider is the entity or individual that actually designs, develops, and implements the software product, while the acquirer is the entity or individual who specifies the requirements and accepts the resulting products. This standard specifies at a high level an overall software assurance program for software developed for and by NASA. Assurance includes the disciplines of quality assurance, quality engineering, verification and validation, nonconformance reporting and corrective action, safety assurance, and security assurance. The application of these disciplines during a software development life cycle is called software assurance. Subsequent lower-level standards will specify the specific processes within these disciplines.

Source record↗