Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “IV&V”

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 73 records · Page 4

New insights into nonradiative heating in late A star chromospheres

Using new and archival spectra from the Goddard High Resolution Spectrograph, we have searched for evidence of chromospheric and transition region emission in six stars of mid to late A spectral type. Two of the stars, alpha Aq1 (A7 IV-V) and alpha Cep (A7 IV-V), show emission in the C II 1335 A doublet, confirming the presence of hot plasma with temperatures comparable to that of the solar transition region. Using radiative equilibrium photospheric models, we estimate the net surface fluxes in the CII emission line to be 9.4 x 10(exp 4) ergs/sq cm/s for alpha Aq1 and 6.5 x 10(exp 4)ergs/sq cm/s for alpha Cep. These are comparable to fluxes observed in stars as hot as approximately 8000 K (B-V = 0.22). We find no evidence for the blueshifted emission reported by Simon et al. (1994). We estimate the basal flux level to be about 30% of that seen in early F stars, and that the bulk of the emission is not basal in origin. We conclude that the basal flux level drops rapidly for B-V approximately less than 0.3, but that magnetic activity may persist to B-v as small as 0.22.

Walter, Frederick M.↗

A Predictive Approach to Eliminating Errors in Software Code

NASA s Metrics Data Program Data Repository is a database that stores problem, product, and metrics data. The primary goal of this data repository is to provide project data to the software community. In doing so, the Metrics Data Program collects artifacts from a large NASA dataset, generates metrics on the artifacts, and then generates reports that are made available to the public at no cost. The data that are made available to general users have been sanitized and authorized for publication through the Metrics Data Program Web site by officials representing the projects from which the data originated. The data repository is operated by NASA s Independent Verification and Validation (IV&V) Facility, which is located in Fairmont, West Virginia, a high-tech hub for emerging innovation in the Mountain State. The IV&V Facility was founded in 1993, under the NASA Office of Safety and Mission Assurance, as a direct result of recommendations made by the National Research Council and the Report of the Presidential Commission on the Space Shuttle Challenger Accident. Today, under the direction of Goddard Space Flight Center, the IV&V Facility continues its mission to provide the highest achievable levels of safety and cost-effectiveness for mission-critical software. By extending its data to public users, the facility has helped improve the safety, reliability, and quality of complex software systems throughout private industry and other government agencies. Integrated Software Metrics, Inc., is one of the organizations that has benefited from studying the metrics data. As a result, the company has evolved into a leading developer of innovative software-error prediction tools that help organizations deliver better software, on time and on budget.

Source record↗

Alternate Methods of Model Reduction to Avoid Dynamic Modal Truncation Error

Loads analysis is traditionally performed using dynamically reduced models, which provides the benefit to reduce run time. If the reduced model frequency cutoff is not chosen appropriately, the model will lack the dynamic content required to fully represent the response of the non-reduced model. Standard guidance for reduced model frequency content, provided in NASA-STD-5002, is to solve fixed base modes up to a minimum of 1.5x the model frequency content of interest and to employ static modal truncation methods such as residual vectors, the mode acceleration method, and the residual flexibility method to account for the truncated flexibility of the missing modes. Fixed base modes require the selection of a set of degrees of freedom to be constrained which, if not properly selected, may affect the accuracy of the reduced model by excluding some of the dynamic characteristic of the full model. In this case, the standard NASA guidance would be insufficient, but it may not be readily apparent that a portion of the reduced model response is missing. This error was encountered during an independent verification and validation (IV&V) effort, where it was observed that the resulting dynamic response was lower than the inline analysis. In this specific case, despite following the standard NASA model reduction guidelines in the selection of the frequency cutoff, the inline model still did not fully capture the necessary dynamic content. As part of the IV&V, an alternate reduction methodology was employed using an unconstrained mode acceleration method. The original model initially performed a constrained reduction to twice the frequency content of interest before doing a free-free run, employing the mode acceleration method to account for the truncated modes. In contrast in the IV&V, the unconstrained model reduced directly to the needed frequency content of the free-free run, avoiding any interactions between constraints and dynamic content. To verify the model, the original reduction methodology was used to generate a series of Hurty-Craig-Bampton reductions, each with a higher frequency cutoff than the previous. The results were shown to converge once the frequency cutoff increased past eight times the frequency content of interest. At the same frequency cutoff, the results of the Hurty-Craig-Bampton model converged with the results of the unconstrained mode acceleration model. This comparative study provided confidence that the results of the unconstrained modal acceleration reduced model were correct and that the Hurty-Craig-Bampton needed to increase its frequency cutoff to fully capture the dynamic response.

Erin Simmons↗

Alternate Methods of Model Reduction to Avoid Dynamic Modal Truncation Error

Loads analysis is traditionally performed using dynamically reduced models, which provides the benefit to reduce run time. If the reduced model frequency cutoff is not chosen appropriately, the model will lack the dynamic content required to fully represent the response of the non-reduced model. Standard guidance for reduced model frequency content, provided in NASA-STD-5002, is to solve fixed base modes up to a minimum of 1.5x the model frequency content of interest and to employ static modal truncation methods such as residual vectors, the mode acceleration method, and the residual flexibility method to account for the truncated flexibility of the missing modes. Fixed base modes require the selection of a set of degrees of freedom to be constrained which, if not properly selected, may affect the accuracy of the reduced model by excluding some of the dynamic characteristic of the full model. In this case, the standard NASA guidance would be insufficient, but it may not be readily apparent that a portion of the reduced model response is missing. This error was encountered during an independent verification and validation (IV&V) effort, where it was observed that the resulting dynamic response was lower than the inline analysis. In this specific case, despite following the standard NASA model reduction guidelines in the selection of the frequency cutoff, the inline model still did not fully capture the necessary dynamic content. As part of the IV&V, an alternate reduction methodology was employed using an unconstrained mode acceleration method. The original model initially performed a constrained reduction to twice the frequency content of interest before doing a free-free run, employing the mode acceleration method to account for the truncated modes. In contrast in the IV&V, the unconstrained model reduced directly to the needed frequency content of the free-free run, avoiding any interactions between constraints and dynamic content. To verify the model, the original reduction methodology was used to generate a series of Hurty-Craig-Bampton reductions, each with a higher frequency cutoff than the previous. The results were shown to converge once the frequency cutoff increased past eight times the frequency content of interest. At the same frequency cutoff, the results of the Hurty-Craig-Bampton model converged with the results of the unconstrained mode acceleration model. This comparative study provided confidence that the results of the unconstrained modal acceleration reduced model were correct and that the Hurty-Craig-Bampton needed to increase its frequency cutoff to fully capture the dynamic response.

Erin Simmons↗

Formal Methods for Verification and Validation of Partial Specifications: A Case Study

This paper describes our work exploring the suitability of formal specification methods for independent verification and validation (IV&V) of software specifications for large, safety critical systems. An IV&V contractor often has to perform rapid analysis on incomplete specifications, with no control over how those specifications are represented. Lightweight formal methods show significant promise in this context, as they offer a way of uncovering major errors, without the burden of full proofs of correctness. We describe a case study of the use of partial formal models for V&V of the requirements for Fault Detection Isolation and Recovery on the space station. We conclude that the insights gained from formalizing a specification are valuable, and it is the process of formalization, rather than the end product that is important. It was only necessary to build enough of the formal model to test the properties in which we were interested. Maintenance of fidelity between multiple representations of the same requirements (as they evolve) is still a problem, and deserves further study.

Easterbrook, Steve↗

Formal Methods of V&V of Partial Specifications: An Experience Report

This paper describes our work exploring the suitability of formal specification methods for independent verification and validation (IV&V) of software specifications for large, safety critical systems. An IV&V contractor often has to perform rapid analysis on incomplete specifications, with no control over how those specifications are represented. Lightweight formal methods show significant promise in this context, as they offer a way of uncovering major errors, without the burden of full proofs of correctness. We describe an experiment in the application of the method SCR. to testing for consistency properties of a partial model of requirements for Fault Detection Isolation and Recovery on the space station. We conclude that the insights gained from formalizing a specification is valuable, and it is the process of formalization, rather than the end product that is important. It was only necessary to build enough of the formal model to test the properties in which we were interested. Maintenance of fidelity between multiple representations of the same requirements (as they evolve) is still a problem, and deserves further study.

Easterbrook, Steve↗

Radial Velocity Detection of Extra-Solar Planetary Systems

The McDonald Observatory Planetary Search (MOPS) was designed to search for Jovian-mass planets in orbit around solar-type stars by making high-precision measurements of the Radial Velocity (RV) of a star, to attempt to detect the reflex orbital motion of the star around the star-planet barycenter. In our solar system, the velocity of the Sun around the Sun-Jupiter barycenter averages 12.3 m/ s. The MOPS survey started operation in September 1987, and searches 36 bright, nearby, solar-type dwarfs to 10 m/s precision. The survey was started using telluric O2 absorption lines as the velocity reference metric. Observations use the McDonald Observatory 2.7-m Harlan Smith Telescope coude spectrograph with the six-foot camera. This spectrograph configuration isolates a single order of the echelle grating on a Texas Instruments 800 x 800 CCD. The telluric line method gave us a routine radial velocity precision of about 15 m/s for stars down to about 5-th magnitude. However, the data obtained with this technique suffered from some source of long-term systematic errors, which was probably the intrinsic velocity variability of the terrestrial atmosphere, i.e. winds. In order to eliminate this systematic error and to improve our overall measurement precision, we installed a stabilized I2 gas absorption cell as the velocity metric for the MOPS in October 1990. In use at the telescope, the cell is placed directly in front of the spectrograph entrance slit, with starlight passing through the cell. The use of this sealed stabilized I2 cell removes potential problems with possible long-term drifts in the velocity metric. The survey now includes a sample of 36 nearby F, G, and K type stars of luminosity class V or IV-V.

Cochran, William D.↗

Ares I-X Range Safety Trajectory Analyses Overview and Independent Validation and Verification

All Flight Analysis data products were successfully generated and delivered to the 45SW in time to support the launch. The IV&V effort allowed data generators to work through issues early. Data consistency proved through the IV&V process provided confidence that the delivered data was of high quality. Flight plan approval was granted for the launch. The test flight was successful and had no safety related issues. The flight occurred within the predicted flight envelopes. Post flight reconstruction results verified the simulations accurately predicted the FTV trajectory.

Tarpley, Ashley F.↗

Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification & Validation (IV&V) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASAs Office of Safety and Mission Assurance (OSMA) defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domain/component, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IV&V enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing this database for adaptive, risk-informed FM assurance that critical software systems will safely and securely protect against faults and respond to ACs in order to achieve successful missions.

IV&V↗

A process improvement model for software verification and validation

We describe ongoing work at the NASA Independent Verification and Validation (IV&V) Facility to establish a process improvement model for software verification and validation (V&V) organizations. This model, similar to those used by some software development organizations, uses measurement-based techniques to identify problem areas and introduce incremental improvements. We seek to replicate this model for organizations involved in V&V on large-scale software development projects such as EOS and Space Station. At the IV&V Facility, a university research group and V&V contractors are working together to collect metrics across projects in order to determine the effectiveness of V&V and improve its application. Since V&V processes are intimately tied to development processes, this paper also examines the repercussions for development organizations in large-scale efforts.

Callahan, John↗

A process improvement model for software verification and validation

We describe ongoing work at the NASA Independent Verification and Validation (IV&V) Facility to establish a process improvement model for software verification and validation (V&V) organizations. This model, similar to those used by some software development organizations, uses measurement-based techniques to identify problem areas and introduce incremental improvements. We seek to replicate this model for organizations involved in V&V on large-scale software development projects such as EOS and space station. At the IV&V Facility, a university research group and V&V contractors are working together to collect metrics across projects in order to determine the effectiveness of V&V and improve its application. Since V&V processes are intimately tied to development processes, this paper also examines the repercussions for development organizations in large-scale efforts.

Callahan, John↗

Completing the Loop: Linking Software Features to Failures

The PITS Modification Script has been under development. Testing, debugging, and optimization of the script are in progress. MSIS has begun population of ODC values from historic issue data. Design of the Linker Tool is also continuing. The quarterly review meeting held on December 17,2003, allowed for a venue to discuss installing the PITS Modification Script to the production version of PITS upon completion and incorporation of ODC into an IV&V project s issue tracking process. Feedback from NASA was positive although any global implementation will likely be timed to coordinate with other activities such as establishment of an IV&V Work Breakdown Structure.

Source record↗

CST: A Tool for Optimizing the Efficiency and Effectiveness of Static-Code Analysis Tools

Static Code Analysis (SCA) is a vital component of NASA IV&V’s mission assurance for safety-critical software as it reduces the likelihood of software-induced hazards impacting mission success. Static Code Analysis achieves this by identifying hazards that may not have been otherwise detectable by typical code reviews or other testing. Using SCA tools, however, can be intimidating due to steep learning curves, especially considering tool performance and defect coverage varies greatly. Because of this variation amongst SCA tools, understanding which tools support certain defects and which do not, as well as understanding how to run an analysis based on steps that are unique to each tool, can be difficult to both new and experienced analysts alike. To mitigate this, the SCAWG or the IV&V Static Code Analysis Working Group, created the SCA Checker Taxonomy and Starting Point Profiles. The Checker Selection Tool (CST) incorporates these two SCAWG products into an interactive tool which allows the user to: select organized categories of defects they would like the SCA tools to discover, select default checkers depending on their mission type (e.g. flight), and configure multiple SCA tools at once. C/C++, Java, and Python defect checkers from four common SCA tools were utilized in this iteration of the CST. This iteration also includes the addition of training, SCA tool specific help, and taxonomy guide links, into its design to help users new to Static Code Analysis learn how to perform SCA more efficiently. The CST has been subject to beta testing by experienced static code analysts from the SCAWG to ensure a usable and accurate final product. The implications of the CST in the mission assurance of NASA safety-critical software are profound, as the CST can help identify and reduce false positives and false negatives, fundamentally improving overall SCA efficiency and accuracy.

static code analysis↗

IUE spectra of F and late A stars

The International Ultraviolet Explorer (IUE) spectra of alpha CMi (F5 IV-V), beta Cas (F2 IV), alpha Car (F0 Ib), and gamma Boo (A7 III) in the context of the question as to whether chromospheres disappear in the early F late A portions of the Hertzsprung-Russell diagram. Both alpha CMi (Procyon) and beta Cas show bright emission line spectra indicative of chromospheres and transition regions, but neither alpha Car (Canopus) nor gamma Boo show any evidence of emission in their SWP spectra or at the Mg II lines, despite very deep exposures. Alpha CMi has emission line fluxes roughly 6 times those of the quiet Sun, but the rapidly rotating delta Scuti type variable beta Cas has surface fluxes 10 to 50 times those of the quiet Sun. Upper limits on emission line fluxes for alpha Car are 4 to 20 and for gamma Boo 15 to 80 times the quiet Sun. It is concluded that the apparent absence of emission lines in the spectra of alpha Car and gamma Boo should not be interpreted as due to the absence of nonradiatively heated outer atmospheres in stars hotter than spectral type F0, but rather to the inability to see emission lines with IUE against a background of scattered light and a bright photospheric absorption line spectrum either in low or high dispersion.

Linsky, J. L.↗

Model Checking Verification and Validation at JPL and the NASA Fairmont IV and V Facility

We show how a technology transfer effort was carried out. The successful use of model checking on a pilot JPL flight project demonstrates the usefulness and the efficacy of the approach. The pilot project was used to model a complex spacecraft controller. Software design and implementation validation were carried out successfully. To suggest future applications we also show how the implementation validation step can be automated. The effort was followed by the formal introduction of the modeling technique as a part of the JPL Quality Assurance process.

Schneider, Frank↗

Software IV and V Research Priorities and Applied Program Accomplishments Within NASA

The mission of this research is to be world-class creators and facilitators of innovative, intelligent, high performance, reliable information technologies that enable NASA missions to (1) increase software safety and quality through error avoidance, early detection and resolution of errors, by utilizing and applying empirically based software engineering best practices; (2) ensure customer software risks are identified and/or that requirements are met and/or exceeded; (3) research, develop, apply, verify, and publish software technologies for competitive advantage and the advancement of science; and (4) facilitate the transfer of science and engineering data, methods, and practices to NASA, educational institutions, state agencies, and commercial organizations. The goals are to become a national Center Of Excellence (COE) in software and system independent verification and validation, and to become an international leading force in the field of software engineering for improving the safety, quality, reliability, and cost performance of software systems. This project addresses the following problems: Ensure safety of NASA missions, ensure requirements are met, minimize programmatic and technological risks of software development and operations, improve software quality, reduce costs and time to delivery, and improve the science of software engineering

Blazy, Louis J.↗