Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “quality guideline”

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 91 records · Page 5

Object-Oriented Software Metrics for Predicting Reusability and Estimating Size

As object-oriented software development methods come into more widespread use, basic questions of software quality assurance must be reconsidered. We will highlight efforts now underway at NASA's Jet Propulsion Laboratory to both assess the quality of software systems developed using object oriented technology and develop guidelines for future development of such systems. The current focus is on design and code reusability., and system size estimation. A number of metrics are proposed and two software systems measured and analyzed. The preliminary results reported here should be useful to software development and quality assurance personnel working in C++ implementation environment.

Sanderson, D. Peter↗

Systems Maintenance Automated Repair Tasks (SMART)

SMART is an interactive decision analysis and refinement software system that uses evaluation criteria for discrepant conditions to automatically provide and populate a document/procedure with predefined steps necessary to repair a discrepancy safely, effectively, and efficiently. SMART can store the tacit (corporate) knowledge merging the hardware specification requirements with the actual "how to" repair methods, sequences, and required equipment, all within a user-friendly interface. Besides helping organizations retain repair knowledge in streamlined procedures and sequences, SMART can also help them in saving processing time and expense, increasing productivity, improving quality, and adhering more closely to safety and other guidelines. Though SMART was developed for Space Shuttle applications, its interface is easily adaptable to any hardware that can be broken down by component, subcomponent, discrepancy, and repair.

Source record↗

Guidelines in preparing computer-generated plots for NASA technical reports with the LaRC graphics output system

To response to a need for improved computer-generated plots that are acceptable to the Langley publication process, the LaRC Graphics Output System has been modified to encompass the publication requirements, and a guideline has been established. This guideline deals only with the publication requirements of computer-generated plots. This report explains the capability that authors of NASA technical reports can use to obtain publication--quality computer-generated plots or the Langley publication process. The rules applied in developing this guideline and examples illustrating the rules are included.

Taylor, N. L.↗

Design and evaluation of a Stochastic Optimal Feed-forward and Feedback Technology (SOFFT) flight control architecture

This paper describes the design and evaluation of a stochastic optimal feed-forward and feedback technology (SOFFT) control architecture with emphasis on the feed-forward controller design. The SOFFT approach allows the designer to independently design the feed-forward and feedback controllers to meet separate objectives and then integrate the two controllers. The feed-forward controller has been integrated with an existing high-angle-of-attack (high-alpha) feedback controller. The feed-forward controller includes a variable command model with parameters selected to satisfy level 1 flying qualities with a high-alpha adjustment to achieve desired agility guidelines, a nonlinear interpolation approach that scales entire matrices for approximation of the plant model, and equations for calculating feed-forward gains developed for perfect plant-model tracking. The SOFFT design was applied to a nonlinear batch simulation model of an F/A-18 aircraft modified for thrust vectoring. Simulation results show that agility guidelines are met and that the SOFFT controller filters undesired pilot-induced frequencies more effectively during a tracking task than a flight controller that has the same feedback control law but does not have the SOFFT feed-forward control.

Ostroff, Aaron J.↗

Guidelines for improving illustrated technical talks

The steps in planning, preparing, and presenting a high-quality illustrated technical talk are presented. Related factors such as audience consideration, defining objectives, storyboarding, developing a written text, rehearsal, final editing, and delivery are covered. Suggestions are made for improving clarity, for achieving proper emphasis, and for easily assimilating information. Detailed considerations for reducing the complexity of visual aids are provided.

Pinelli, T. E.↗

Reliability and quality assurance on the MOD 2 wind system

The Safety, Reliability, and Quality Assurance (R&QA) approach developed for the largest wind turbine generator, the Mod 2, is described. The R&QA approach assures that the machine is not hazardous to the public or to the operating personnel, is operated unattended on a utility grid, demonstrates reliable operation, and helps establish the quality assurance and maintainability requirements for future wind turbine projects. The significant guideline consisted of a failure modes and effects analysis (FMEA) during the design phase, hardware inspections during parts fabrication, and three simple documents to control activities during machine construction and operation.

Mason, W. E. B.↗

Backplane Design Considerations for High Speed SpaceWire Networks

SpaceWire is becoming a preferred protocol for board to board communication over a backplane in addition to its existing use over cabled interfaces, replacing other protocols due to its simplicity and readily available flight quality physical layer devices, IP cores and test equipment. However, without specific guidelines for implementing SpaceWire over a backplane, designers are left to make trade decisions regarding connector selection, layout design rules and test accessibility issues. This paper will discuss NASA's Goddard Space Flight Center s implementation of high speed SpaceWire over backplane on James Webb Space Telescope and other missions.

Pagen, Shahana Aziz↗

Guideline 36 Conformance Test v2.0

ASHRAE Guideline 36 provides guidance for how typical commercial building HVAC systems should be controlled to reduce energy costs and improve the indoor environmental quality for occupants. An industry-led effort is developing test scripts for how control manufacturers can test that the control logic in their control products follows Guideline 36. This software intends to support that effort in two ways. First, by providing a testbed for control manufacturers to run the test scripts against their own control products and compare their generated results to the expected results provided by the test scripts. Second, by providing a testbed that can be used during the development of test scripts to rapidly and repeatably verify they exercise Guideline 36 logic as desired and generate accurate expected results that control products can be compared to. An initial version of the software has already been developed and released open-source by a previous CEC-funded project that implemented the first use case (https://github.com/LBNL-ETA/guideline36_conformance_test/blob/master/LICENSE.txt), while this software disclosure will add the functionality of the second use case, as well as update the software where needed, all open-source. We intend to extend and contribute to the existing open-source software repository.

Blum, David [Lawrence Berkeley National Laboratory↗

Framework for Small-Scale Experiments in Software Engineering: Guidance and Control Software Project: Software Engineering Case Study

Software is becoming increasingly significant in today's critical avionics systems. To achieve safe, reliable software, government regulatory agencies such as the Federal Aviation Administration (FAA) and the Department of Defense mandate the use of certain software development methods. However, little scientific evidence exists to show a correlation between software development methods and product quality. Given this lack of evidence, a series of experiments has been conducted to understand why and how software fails. The Guidance and Control Software (GCS) project is the latest in this series. The GCS project is a case study of the Requirements and Technical Concepts for Aviation RTCA/DO-178B guidelines, Software Considerations in Airborne Systems and Equipment Certification. All civil transport airframe and equipment vendors are expected to comply with these guidelines in building systems to be certified by the FAA for use in commercial aircraft. For the case study, two implementations of a guidance and control application were developed to comply with the DO-178B guidelines for Level A (critical) software. The development included the requirements, design, coding, verification, configuration management, and quality assurance processes. This paper discusses the details of the GCS project and presents the results of the case study.

Hayhurst, Kelly J.↗

Unified results of several analytical and experimental studies of helicopter handling qualities in visual terrain flight

The studies were undertaken to investigate the effects of rotor design parameters, interaxis coupling, and various levels of stability and control augmentation on the flying qualities of helicopters performing low-level, terrain-flying tasks in visual meteorological conditions. Some unified results are presented, and the validity and limitations of the flying-qualities data obtained are interpreted. Selected results, related to various design parameters, provide guidelines for the preliminary design of rotor systems and aircraft augmentation systems.

Chen, R. T. N.↗

Effects of control saturation on the command response of statically unstable aircraft

Hanson and Stengel (1981) have described the effects of saturating controls on the initial-condition response of statically unstable aircraft. In an analysis of the stability augmentation system, consideration was given to maximizing the region of stable response. The present investigation is concerned with an extension of the control saturation analysis to the problem of command response, taking into account the main problem of control design for satisfactory flying qualities (as perceived by the pilot). A model for examining the effects of control saturation on longitudinal stability and command response is developed and applied to an aircraft with a static instability. Three parameters prescribing longitudinal flying qualities are examined with respect to their ability to identify proper flying qualities in the presence of control saturation. The presented analysis provides also satisfactory guidelines for establishing command saturation/stability boundaries.

Hanson, G. D.↗

A rigorous approach to self-checking programming

Self-checking programming is shown to be an effective concurrent error detection technique. The reliability of a self-checking program however relies on the quality of its assertion statements. A self-checking program written without formal guidelines could provide a poor coverage of the errors. A constructive technique for self-checking programming is presented. A Structured Program Design Language (SPDL) suitable for self-checking software development is defined. A set of formal rules, was also developed, that allows the transfromation of SPDL designs into self-checking designs to be done in a systematic manner.

Hua, Kien A.↗

Spiral model pilot project information model

The objective was an evaluation of the Spiral Model (SM) development approach to allow NASA Marshall to develop an experience base of that software management methodology. A discussion is presented of the Information Model (IM) that was used as part of the SM methodology. A key concept of the SM is the establishment of an IM to be used by management to track the progress of a project. The IM is the set of metrics that is to be measured and reported throughout the life of the project. These metrics measure both the product and the process to ensure the quality of the final delivery item and to ensure the project met programmatic guidelines. The beauty of the SM, along with the IM, is the ability to measure not only the correctness of the specification and implementation of the requirements but to also obtain a measure of customer satisfaction.

Source record↗

Requirements for Portable Instrument Suites during Human Scientific Exploration of Mars

Human explorers on the surface of Mars will have access to a far wider array of scientific tools than previous crewed planetary exploration missions, but not every tool will be compatible with the restrictions of this exploration. Spectrometers on flyby, orbital, and landed missions are currently used to determine the composition and mineralogy of geological materials of various types and sizes, from small fragments to celestial bodies in the solar system. Handheld spectrometers that are capable of in situ analyses are already used for geological exploration on Earth; however, their usefulness for human exploration missions and how data from multiple handheld instruments could be combined to enhance scientific return must be further evaluated. As part of the Biologic Analog Science Associated with Lava Terrains (BASALT) research project, we incorporated two handheld instruments, a visible-near infrared spectrometer and an X-Ray Fluorescence spectrometer, into simulated Mars exploration missions conducted on basaltic terrains in Idaho and Hawai'i. To understand the data quality provided by these handheld spectrometers, we evaluated their performance under varying conditions of measurement time, distance, angle, atmosphere, and sample matrix, and we compared data quality between handheld instruments and laboratory techniques. Here, we summarize these findings, provide guidelines and requirements on how to effectively incorporate these instruments into human exploration missions to Mars, and posit that future iterations of these instruments will be beneficial for enhancing science returned from human exploration missions.

Alexander Sehlke↗

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

Acquisition of and Access to Research Omics Data

Omics data are essential for understanding the myriad and complex effects of space environments on humans. To assure maximum benefit from these kinds of data, the NASA Human Research Program Data Management Plan stipulates that human omics data should be archived within and accessed through the NASA Life Sciences Portal (NLSP). The NLSP has the capability to acquire and provision access to omics (and other kinds of) research results for individual and ad-hoc groups of subjects at the direction of institutional review boards, or other authorizing bodies or individuals, per institutional, program and investigation-specific policies and procedures. However, because some single-subject omics data, like CT scans and other kinds of large, complex biomedical data, could be used to identify heretofore unknown risks to the subject’s health, or, in certain cases, be used to identify a subject, NASA Policy Directive 7170.1 describes various policies regarding the management of and access to “research genetic testing” data, which includes many kinds of omics data. For example, NPD 7170.1 prohibits access to human research genetic data by NASA personnel who make employment decisions for the subjects from whom the data were obtained. To meet the objective of acquiring research omics data for NLSP in compliance with the policies in NPD 7170.1 and other applicable NASA policies, we designed NOMADS (the NLSP Omics Multimodal Acquisition of Data System), a new component that supports the transfer of large research data files, including research genetic testing data, using one of several different transfer mechanisms. The choice of mechanism is made by the submitter of the data, with guiding information from the system, and is likely to often be determined in large part by the nature and source location of the data. For example, for small files where the source data files are not already stored in a cloud storage system, users are likely to prefer to transfer their data to the NLSP via a web browser. Conversely, for large sets of files already organized and stored in a cloud storage system, users may opt for NOMAD’s cloud-to-cloud transfer method. All omics datasets targeted for the NASA Life Sciences Data Archive must pass a variety of quality checks to ensure data integrity and adherence to the standards defined by the LSDA Data Submission Guidelines (DSG) (see https://nlsp.nasa.gov/explore/lsdahome/datasubmit). These include requirements that data are consistent with open standards established by the omics community. Non-compliant data will not be accepted however archivists are available to advise submitters on how to revise data submissions and re-submit until compliance is achieved. Following compliance with the LSDA DSG, omics data next undergo a variety of additional quality checks to ensure the data meet omics community standards. Domain specific Omics data quality control tools and techniques are continually evolving and linked to the advancements in omics assays utilized and thus, the tools and techniques utilized by the LSDA for data quality control and validation will need to be sustained accordingly. All human omics data will be access controlled according to the policies described above, and requiring IRB approval for any additional access grants once the data are acquired (including access for analysis using the NLSP workspace tools).

Omics↗

The GuideView System for Interactive, Structured, Multi-modal Delivery of Clinical Guidelines

GuideView is a computerized clinical guideline system which delivers clinical guidelines in an easy-to-understand and easy-to-use package. It may potentially enhance the quality of medical care or allow non-medical personnel to provide acceptable levels of care in situations where physicians or nurses may not be available. Such a system can be very valuable during space flight missions when a physician is not readily available, or perhaps the designated medical personnel is unable to provide care. Complex clinical guidelines are broken into simple steps. At each step clinical information is presented in multiple modes, including voice,audio, text, pictures, and video. Users can respond via mouse clicks or via voice navigation. GuideView can also interact with medical sensors using wireless or wired connections. The system's interface is illustrated and the results of a usability study are presented.

Iyengar, Sriram↗