Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Programming Practices”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1979

Atmospheric turbulence effects on aircraft noise propagation

The Brown and Clifford model for the apparent sound attenuation cuased by atmospheric turbulence was reviewed and extended. Calculations, based on the model, were made for the predicted sound attenuation for a tower-mounted loudspeaker-type sound source and for an airplane sound source. The important parameters in the model are identified and discussed. A model for sound fluctuations is also presented and a practical experimental program to validate the models described.

Chapkis, R. L.↗
NASA NTRS1983

Implementation of R & QA practices in Research and Development programs

DOE has established a number of broad programs aimed at reducing fuel consumption. Several programs address the R&D of ground transportation propulsion alternatives to the conventional spark-ignition engine. NASA Lewis is responsible for managing the effort between the Government and industry teams involving American and foreign companies. Thus, existing NASA SR&QA procedure were modified/adapted to these R&D programs and implemented to assure that the test hardware design intent was met, the hardware was not hazardous to personnel, it would demonstrate reliable operation, and it would help establish the future R&D quality assurance and maintainability requirements. This successful low-cost approach might be applicable to other similar projects.

Bankaitis, H.↗
NASA NTRS1982

Land remote sensing in the 1980's

A discussion is presented concerning U.S. governmental funding policy for the Land Remote Sensing programs, in which the Landsat spacecraft and the research and development activities associated with them are essential elements. Even if present program management practices were to be changed in the next 1-2 years, the investment of significant amounts of private capital in land remote sensing may be 3-5 years away, due to the immaturity of the prospective markets for the services rendered and the present state of technological development. It is judged that even if NASA is successful in bringing significant private investment into remote sensing activities by the mid-1980s, government must continue to support basic research and expensive technology development in long term and high risk, but potentially high payoff, areas which the still-developing remote sensing industry cannot afford.

Thome, P. G.↗
NASA NTRS1988

Commercial objectives, technology transfer, and systems analysis for fusion power development

Fusion is an inexhaustible source of energy that has the potential for economic commercial applications with excellent safety and environmental characteristics. The primary focus for the fusion energy development program is the generation of central station electricity. Fusion has the potential, however, for many other applications. The fact that a large fraction of the energy released in a DT fusion reaction is carried by high energy neutrons suggests potentially unique applications. In addition, fusion R and D will lead to new products and new markets. Each fusion application must meet certain standards of economic and safety and environmental attractiveness. For this reason, economics on the one hand, and safety and environment and licensing on the other, are the two primary criteria for setting long range commercial fusion objectives. A major function of systems analysis is to evaluate the potential of fusion against these objectives and to help guide the fusion R and D program toward practical applications. The transfer of fusion technology and skills from the national labs and universities to industry is the key to achieving the long range objective of commercial fusion applications.

Dean, Stephen O.↗
NASA NTRS1990

Predicting Noise From Wind Turbines

Computer program WINDY predicts broadband noise spectra of horizontal-axis wind-turbine generators. Enables adequate assessment of impact of broadband wind-turbine noise. Effects of turbulence, trailing-edge wakes, and bluntness taken into account. Program has practical application in design and siting of wind-turbine machines acceptable to community. Written in GW-Basic.

Grosveld, Ferdinand W.↗
NASA NTRS1993

OSHA Bloodborne Pathogens Standards Exposure Control Plan

The Hummer Associates Exposure Control Plan is designed to reduce significant occupational exposure to bloodborne pathogens and infectious materials for Hummer Associates health care personnel. Under universal precautions, all patients and all body fluids are considered potentially infectious for bloodborne pathogens. Medical personnel need not be at increased risk if universal precautions are correctly understood and followed. This program covers all employees who could reasonably anticipate contact with blood or other potentially infectious materials during the performance of their job responsibilities. Although HIV and hepatitis B are mentioned most often, this program applies to all bloodborne diseases. The two main components needed to implement this program are universal precautions and engineering/work practice controls. This program covers all employees who may have occupational exposure to blood or other potentially infectious materials. Other aspects of this program are discussed.

Luhrs, Caro Elise↗
NASA NTRS2002

Cost Estimation and Control for Flight Systems

Good program management practices, cost analysis, cost estimation, and cost control for aerospace flight systems are interrelated and depend upon each other. The best cost control process cannot overcome poor design or poor systems trades that lead to the wrong approach. The project needs robust Technical, Schedule, Cost, Risk, and Cost Risk practices before it can incorporate adequate Cost Control. Cost analysis both precedes and follows cost estimation -- the two are closely coupled with each other and with Risk analysis. Parametric cost estimating relationships and computerized models are most often used. NASA has learned some valuable lessons in controlling cost problems, and recommends use of a summary Project Manager's checklist as shown here.

Hammond, Walter E.↗
NASA NTRS1980

Space Transportation Systems, Aeronautics and Space Technology, Space and Terrestrial Applications, and Space Sciences

This report is prepared on an annual basis for the purposes of highlighting the fiscal year research and technology (R&T) activities. Its intent is to better inform the R&T Program Managers of significant accomplishments that promise practical and beneficial program application. The report is not inclusive of all R&T activities. The document is organized into two distinct sections: (1) a general summary of the major R&T activities in each program area, and (2) a description of significant individual completed activities and their results. This document will be updated November 1 of each year.

Source record↗
NASA NTRS1982

Research and Technology

This report is prepared on an annual basis for the purposes of highlighting the fiscal year research and technology (R&T) activities. Its intent !s to better inform the R&T Program Managers of significant accomplishments that promise practical and beneficial program application. The report is not inclusive of all R&T activities. This document will be updated in November of each year.

Source record↗
NASA NTRS2009

Proceedings of the Third International Workshop on Proof-Carrying Code and Software Certification

This NASA conference publication contains the proceedings of the Third International Workshop on Proof-Carrying Code and Software Certification, held as part of LICS in Los Angeles, CA, USA, on August 15, 2009. Software certification demonstrates the reliability, safety, or security of software systems in such a way that it can be checked by an independent authority with minimal trust in the techniques and tools used in the certification process itself. It can build on existing validation and verification (V&V) techniques but introduces the notion of explicit software certificates, Vvilich contain all the information necessary for an independent assessment of the demonstrated properties. One such example is proof-carrying code (PCC) which is an important and distinctive approach to enhancing trust in programs. It provides a practical framework for independent assurance of program behavior; especially where source code is not available, or the code author and user are unknown to each other. The workshop wiII address theoretical foundations of logic-based software certification as well as practical examples and work on alternative application domains. Here "certificate" is construed broadly, to include not just mathematical derivations and proofs but also safety and assurance cases, or any fonnal evidence that supports the semantic analysis of programs: that is, evidence about an intrinsic property of code and its behaviour that can be independently checked by any user, intermediary, or third party. These guarantees mean that software certificates raise trust in the code itself, distinct from and complementary to any existing trust in the creator of the code, the process used to produce it, or its distributor. In addition to the contributed talks, the workshop featured two invited talks, by Kelly Hayhurst and Andrew Appel. The PCC 2009 website can be found at http://ti.arc.nasa.gov /event/pcc 091.

Ewen, Denney, W.↗
NASA NTRS2006

QUEST: Qualifying Environmentally Sustainable Technologies

Over the years, pollution prevention has proven to be a means to comply with environmental regulations, improve product performance and reduce costs. The NASA Acquisition Pollution Prevention (AP2) Program was created to help individual NASA Centers and programs work together to evaluate and adopt environmentally preferable technologies and practices. The AP2 Program accomplishes its mission using a variety of tools such as networking, information/technology exchange and partnering. Due to its extensive network of contacts, the AP2 Program is an excellent resource for finding existing solutions to problems. If no solution is readily known, the AP2 Program works to identify potential solutions and partners for demonstration/ validation projects. Partnering to prevent pollution is a cornerstone of NASA's prime mission and the One NASA Initiative. This annual newsletter highlights some of our program's collaborative efforts. I believe you will discover how the AP2 Program is responsive in meeting the Agency's environmental management strategic plans.

Source record↗
NASA NTRS2006

Practical Application of Model-based Programming and State-based Architecture to Space Missions

A viewgraph presentation to develop models from systems engineers that accomplish mission objectives and manage the health of the system is shown. The topics include: 1) Overview; 2) Motivation; 3) Objective/Vision; 4) Approach; 5) Background: The Mission Data System; 6) Background: State-based Control Architecture System; 7) Background: State Analysis; 8) Overview of State Analysis; 9) Background: MDS Software Frameworks; 10) Background: Model-based Programming; 10) Background: Titan Model-based Executive; 11) Model-based Execution Architecture; 12) Compatibility Analysis of MDS and Titan Architectures; 13) Integrating Model-based Programming and Execution into the Architecture; 14) State Analysis and Modeling; 15) IMU Subsystem State Effects Diagram; 16) Titan Subsystem Model: IMU Health; 17) Integrating Model-based Programming and Execution into the Software IMU; 18) Testing Program; 19) Computationally Tractable State Estimation & Fault Diagnosis; 20) Diagnostic Algorithm Performance; 21) Integration and Test Issues; 22) Demonstrated Benefits; and 23) Next Steps

Mission Data System (MDS)↗
NASA NTRS2006

Practical Application of Model-based Programming and State-based Architecture to Space Missions

Innovative systems and software engineering solutions are required to meet the increasingly challenging demands of deep-space robotic missions. While recent advances in the development of an integrated systems and software engineering approach have begun to address some of these issues, they are still at the core highly manual and, therefore, error-prone. This paper describes a task aimed at infusing MIT's model-based executive, Titan, into JPL's Mission Data System (MDS), a unified state-based architecture, systems engineering process, and supporting software framework. Results of the task are presented, including a discussion of the benefits and challenges associated with integrating mature model-based programming techniques and technologies into a rigorously-defined domain specific architecture.

state analysis↗
NASA NTRS2007

MatLab Programming for Engineers Having No Formal Programming Knowledge

MatLab is one of the most widely used very high level programming languages for Scientific and engineering computations. It is very user-friendly and needs practically no formal programming knowledge. Presented here are MatLab programming aspects and not just the MatLab commands for scientists and engineers who do not have formal programming training and also have no significant time to spare for learning programming to solve their real world problems. Specifically provided are programs for visualization. Also, stated are the current limitations of the MatLab, which possibly can be taken care of by Mathworks Inc. in a future version to make MatLab more versatile.

Shaykhian, Linda H.↗
NASA NTRS2007

MatLab Script and Functional Programming

MatLab Script and Functional Programming: MatLab is one of the most widely used very high level programming languages for scientific and engineering computations. It is very user-friendly and needs practically no formal programming knowledge. Presented here are MatLab programming aspects and not just the MatLab commands for scientists and engineers who do not have formal programming training and also have no significant time to spare for learning programming to solve their real world problems. Specifically provided are programs for visualization. The MatLab seminar covers the functional and script programming aspect of MatLab language. Specific expectations are: a) Recognize MatLab commands, script and function. b) Create, and run a MatLab function. c) Read, recognize, and describe MatLab syntax. d) Recognize decisions, loops and matrix operators. e) Evaluate scope among multiple files, and multiple functions within a file. f) Declare, define and use scalar variables, vectors and matrices.

Shaykhian, Gholam Ali↗
NASA NTRS2015

Human Systems Integration (HSI) Practitioner's Guide

The NASA/SP-2015-3709, Human Systems Integration (HSI) Practitioner's Guide, also known as the "HSIPG," provides a tool for implementing HSI activities within the NASA systems engineering framework. The HSIPG is written to aid the HSI practitioner engaged in a program or project (P/P), and serves as a knowledge base to allow the practitioner to step into an HSI lead or team member role for NASA missions. Additionally, this HSIPG is written to address the role of HSI in the P/P management and systems engineering communities and aid their understanding of the value added by incorporating good HSI practices into their programs and projects. Through helping to build a community of knowledgeable HSI practitioners, this document also hopes to build advocacy across the Agency for establishing strong, consistent HSI policies and practices. Human Systems Integration (HSI) has been successfully adopted (and adapted) by several federal agencies-most notably the U.S. Department of Defense (DoD) and the Nuclear Regulatory Commission (NRC)-as a methodology for reducing system life cycle costs (LCCs). These cost savings manifest themselves due to reductions in required numbers of personnel, the practice of human-centered design, decreased reliance on specialized skills for operations, shortened training time, efficient logistics and maintenance, and fewer safety-related risks and mishaps due to unintended human/system interactions. The HSI process for NASA establishes how cost savings and mission success can be realized through systems engineering. Every program or project has unique attributes. This HSIPG is not intended to provide one-size-fits-all recommendations for HSI implementation. Rather, HSI processes should be tailored to the size, scope, and goals of individual situations. The instructions and processes identified here are best used as a starting point for implementing human-centered system concepts and designs across programs and projects of varying types, including manned and unmanned, human spaceflight, aviation, robotics, and environmental science missions. The practitioner using this guide should have expertise in Systems Engineering or other disciplines involved in producing systems with anticipated human interactions. (See section 1.6 of this guide for further discussion on HSI discipline domains.) The HSIPG provides an "HSI layer" to the NASA Systems Engineering Engine (SEE), detailed in NASA Procedural Requirement (NPR) 7123.1B, NASA Systems Engineering Processes and Requirements, and further explained in NASA/SP-2007-6105, Systems Engineering Handbook (see HSIPG Table 2.2-1, NASA Documents with HSI Content, for specific references and document versions).

Zumbado, Jennifer Rochlis↗
NASA NTRS2002

Extreme Programming in a Research Environment

This article explores the applicability of Extreme Programming in a scientific research context. The cultural environment at a government research center differs from the customer-centric business view. The chief theoretical difficulty lies in defining the customer to developer relationship. Specifically, can Extreme Programming be utilized when the developer and customer are the same person? Eight of Extreme Programming's 12 practices are perceived to be incompatible with the existing research culture. Further, six of the nine 'environments that I know don't do well with XP' apply. A pilot project explores the use of Extreme Programming in scientific research. The applicability issues are addressed and it is concluded that Extreme Programming can function successfully in situations for which it appears to be ill-suited. A strong discipline for mentally separating the customer and developer roles is found to be key for applying Extreme Programming in a field that lacks a clear distinction between the customer and the developer.

Wood, William A.↗