Search NASA⌕ Search

SEARCH · Search NASA

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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

NASA GSFC Opportunities for STEM Professionals Using the Vantage Point of Space

NASA has a variety of learning opportunities for STEM professionals. Three opportunities at GSFC are examined in this chapter: 1) standard summer research and development internship for undergraduates, 2) senior internship for undergraduate and graduate students and 3) a workshop series for informal learning center professionals. We describe these programs, examine their evolution with respect to most effective education practices and their assessment and evaluation, and identify the similarities and differences between them. The internship programs highlight authentic project-based research and development experiences with the senior internship providing a richer, deeper, and more demanding experience that has greater professional value. The workshops for informal learning center professionals on-the-other hand, focus on building knowledge of GSFC s science and engineering strengths among these professionals, and on building enduring partnerships between individuals (participants and GSFC scientist, engineers and educators) and between organizations (GSFC and the informal learning center). Finally, we examine the characteristics of these programs from a design and management perspective. Through this examination we identify a general structure that provides insight into more effective design and management of similar education programs.

Meeson, Blanche W.↗
NASA NTRS1978

Survey of university programs in remote sensing funded under grants from the NASA University-Space Applications program

NASA's Office of Space and Terrestrial Applications (OSTA) is currently assessing approaches to transferring NASA technology to both the public and private sectors. As part of this assessment, NASA is evaluating the effectiveness of an ongoing program in remote sensing technology transfer conducted by 20 university contractors/grantees, each supported totally or partially by NASA funds. The University-Space Applications program has as its objective the demonstration of practical benefits from the use of remote sensing technology to a broad spectrum of new users, principally in state and local governments. To evaluate the University-Space Applications program, NASA has a near-term requirement for data on each university effort including total funding, funding sources, length of program, program description, and effectiveness measures.

Madigan, J. A.↗
NASA NTRS2008

Design Development Test and Evaluation (DDT and E) Considerations for Safe and Reliable Human Rated Spacecraft Systems

A team directed by the NASA Engineering and Safety Center (NESC) collected methodologies for how best to develop safe and reliable human rated systems and how to identify the drivers that provide the basis for assessing safety and reliability. The team also identified techniques, methodologies, and best practices to assure that NASA can develop safe and reliable human rated systems. The results are drawn from a wide variety of resources, from experts involved with the space program since its inception to the best-practices espoused in contemporary engineering doctrine. This report focuses on safety and reliability considerations and does not duplicate or update any existing references. Neither does it intend to replace existing standards and policy.

Miller, James↗
NASA NTRS2008

Design Development Test and Evaluation (DDT and E) Considerations for Safe and Reliable Human Rated Spacecraft Systems

A team directed by the NASA Engineering and Safety Center (NESC) collected methodologies for how best to develop safe and reliable human rated systems and how to identify the drivers that provide the basis for assessing safety and reliability. The team also identified techniques, methodologies, and best practices to assure that NASA can develop safe and reliable human rated systems. The results are drawn from a wide variety of resources, from experts involved with the space program since its inception to the best-practices espoused in contemporary engineering doctrine. This report focuses on safety and reliability considerations and does not duplicate or update any existing references. Neither does it intend to replace existing standards and policy.

Miller, James↗
NASA NTRS1979

Integrated energy management study. Energy efficient transport program

The Integrated Energy Management (IEM) Study investigated the practicality and feasibility of a closed-loop energy management system for transport aircraft. The study involved: (1) instrumentation and collection of in-flight data for a United Airlines 727-200 flying 80 revenue flights throughout the United Airlines network,(2) analysis of the in-flight data to select representative city pairs and establish operational procedures employed in flying a reference flight profile, (3) simulation of the reference profile in a fast-time model to verify the model and establish performance values against which to measure IEM benefits, (4) development of IEM algorithms, and (5) assessment of the IEM concept.

Source record↗
NASA NTRS1986

Interesting viewpoints to those who will put Ada into practice

Ada will most probably be used as the programming language for computers in the NASA Space Station. It is reasonable to suppose that Ada will be used for at least embedded computers, because the high software costs for these embedded computers were the reason why Ada activities were initiated about ten years ago. The on-board computers are designed for use in space applications, where maintenance by man is impossible. All manipulation of such computers has to be performed in an autonomous way or remote with commands from the ground. In a manned Space Station some maintenance work can be performed by service people on board, but there are still a lot of applications, which require autonomous computers, for example, vital Space Station functions and unmanned orbital transfer vehicles. Those aspect which have come out of the analysis of Ada characteristics together with the experience of requirements for embedded on-board computers in space applications are examined.

Carlsson, Arne↗
NASA NTRS2010

NASA Supportability Engineering Implementation Utilizing DoD Practices and Processes

The Ares I design and development program made the determination early in the System Design Review Phase to utilize DoD ILS and LSA approach for supportability engineering as an integral part of the system engineering process. This paper is to provide a review of the overall approach to design Ares-I with an emphasis on a more affordable, supportable, and sustainable launch vehicle. Discussions will include the requirements development, design influence, support concept alternatives, ILS and LSA planning, Logistics support analyses/trades performed, LSA tailoring for NASA Ares Program, support system infrastructure identification, ILS Design Review documentation, Working Group coordination, and overall ILS implementation. At the outset, the Ares I Project initiated the development of the Integrated Logistics Support Plan (ILSP) and a Logistics Support Analysis process to provide a path forward for the management of the Ares-I ILS program and supportability analysis activities. The ILSP provide the initial planning and coordination between the Ares-I Project Elements and Ground Operation Project. The LSA process provided a system engineering approach in the development of the Ares-I supportability requirements; influence the design for supportability and development of alternative support concepts that satisfies the program operability requirements. The LSA planning and analysis results are documented in the Logistics Support Analysis Report. This document was required during the Ares-I System Design Review (SDR) and Preliminary Design Review (PDR) review cycles. To help coordinate the LSA process across the Ares-I project and between programs, the LSA Report is updated and released quarterly. A System Requirement Analysis was performed to determine the supportability requirements and technical performance measurements (TPMs). Two working groups were established to provide support in the management and implement the Ares-I ILS program, the Integrated Logistics Support Working Group (ILSWG) and the Logistics Support Analysis Record Working Group (LSARWG). The Ares I ILSWG is established to assess the requirements and conduct, evaluate analyses and trade studies associated with acquisition logistic and supportability processes and to resolve Ares I integrated logistics and supportability issues. It established a strategic collaborative alliance for coordination of Logistics Support Analysis activates in support of the integrated Ares I vehicle design and development of logistics support infrastructure. A Joint Ares I - Orion LSAR Working Group was established to: 1) Guide the development of Ares-I and Orion LSAR data and serve as a model for future Constellation programs, 2) Develop rules and assumptions that will apply across the Constellation program with regards to the program's LSAR development, and 3) Maintain the Constellation LSAR Style Guide.

Smith, David A.↗
NASA NTRS2011

The Application of Software Safety to the Constellation Program Launch Control System

The application of software safety practices on the LCS project resulted in the successful implementation of the NASA Software Safety Standard NASA-STD-8719.138 and CxP software safety requirements. The GOP-GEN-GSW-011 Hazard Report was the first report developed at KSC to identify software hazard causes and their controls. This approach can be applied to similar large software - intensive systems where loss of control can lead to a hazard.

Kania, James↗
NASA NTRS2002

AutoBayes/CC: Combining Program Synthesis with Automatic Code Certification: System Description

Code certification is a lightweight approach to formally demonstrate software quality. It concentrates on aspects of software quality that can be defined and formalized via properties, e.g., operator safety or memory safety. Its basic idea is to require code producers to provide formal proofs that their code satisfies these quality properties. The proofs serve as certificates which can be checked independently, by the code consumer or by certification authorities, e.g., the FAA. It is the idea underlying such approaches as proof-carrying code [6]. Code certification can be viewed as a more practical version of traditional Hoare-style program verification. The properties to be verified are fairly simple and regular so that it is often possible to use an automated theorem prover to automatically discharge all emerging proof obligations. Usually, however, the programmer must still splice auxiliary annotations (e.g., loop invariants) into the program to facilitate the proofs. For complex properties or larger programs this quickly becomes the limiting factor for the applicability of current certification approaches.

Whalen, Michael↗
NASA NTRS2009

Early Career Hire Rapid Training and Development Program: Status Report

The aging of the industrialized workforce, particularly in the aerospace industry, has resulted in a very large generation gap in the workforce. The disproportionate size of Baby Boomers, increasing longevity and declining birth rates has made this phenomenon a reality that no organization can ignore. It is now critical that aerospace organizations prepare themselves for this watershed transformation in the workforce and take the initiative to prepare the incoming workforce with the skills and knowledge necessary to stay at the forefront. Last year the Jet Propulsion Laboratory launched a pioneering training program, known as Phaeton, to provide the knowledge, practice, experience, mentoring opportunities, and project life cycle exposure to our incoming generation of engineers. After 14 months of operation, now is the time to discuss the preliminary results of this new program.

Riley, Betsy N.↗
NASA NTRS2002

Engine System Loads Analysis Compared to Hot-Fire Data

Early implementation of structural dynamics finite element analyses for calculation of design loads is considered common design practice for high volume manufacturing industries such as automotive and aeronautical industries. However with the rarity of rocket engine development programs starts, these tools are relatively new to the design of rocket engines. In the NASA MC-1 engine program, the focus was to reduce the cost-to-weight ratio. The techniques for structural dynamics analysis practices, were tailored in this program to meet both production and structural design goals. Perturbation of rocket engine design parameters resulted in a number of MC-1 load cycles necessary to characterize the impact due to mass and stiffness changes. Evolution of loads and load extraction methodologies, parametric considerations and a discussion of load path sensitivities are important during the design and integration of a new engine system. During the final stages of development, it is important to verify the results of an engine system model to determine the validity of the results. During the final stages of the MC-1 program, hot-fire test results were obtained and compared to the structural design loads calculated by the engine system model. These comparisons are presented in this paper.

Frady, Gregory P.↗
NASA NTRS1993

Repository-Based Software Engineering Program: Working Program Management Plan

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

Source record↗
NASA NTRS2013

Applications of Automation Methods for Nonlinear Fracture Test Analysis

Using automated and standardized computer tools to calculate the pertinent test result values has several advantages such as: 1. allowing high-fidelity solutions to complex nonlinear phenomena that would be impractical to express in written equation form, 2. eliminating errors associated with the interpretation and programing of analysis procedures from the text of test standards, 3. lessening the need for expertise in the areas of solid mechanics, fracture mechanics, numerical methods, and/or finite element modeling, to achieve sound results, 4. and providing one computer tool and/or one set of solutions for all users for a more "standardized" answer. In summary, this approach allows a non-expert with rudimentary training to get the best practical solution based on the latest understanding with minimum difficulty.Other existing ASTM standards that cover complicated phenomena use standard computer programs: 1. ASTM C1340/C1340M-10- Standard Practice for Estimation of Heat Gain or Loss Through Ceilings Under Attics Containing Radiant Barriers by Use of a Computer Program 2. ASTM F 2815 - Standard Practice for Chemical Permeation through Protective Clothing Materials: Testing Data Analysis by Use of a Computer Program 3. ASTM E2807 - Standard Specification for 3D Imaging Data Exchange, Version 1.0 The verification, validation, and round-robin processes required of a computer tool closely parallel the methods that are used to ensure the solution validity for equations included in test standard. The use of automated analysis tools allows the creation and practical implementation of advanced fracture mechanics test standards that capture the physics of a nonlinear fracture mechanics problem without adding undue burden or expense to the user. The presented approach forms a bridge between the equation-based fracture testing standards of today and the next generation of standards solving complex problems through analysis automation.

Allen, Phillip A.↗
NASA NTRSDate not supplied

Spacecraft Passivation – An Overview of Requirements, Principles, and Practices

Explosions, collisions, and other catastrophic breakups of launch vehicle orbital stages and satellites continue to be major contributors to the generation of orbital debris. Both launch vehicles and payload satellites typically have several types of stored energy sources on board, any of which might result in energetic breakups and the creation of debris after their mission has ended. These energy sources include propulsion systems, pressure vessels, reaction wheels, control moment gyros, heat pipes, and power systems. NASA, ESA, JAXA and other space-faring organizations have requirements in place to limit the growth of the orbital debris population by passivating space vehicles that remain in orbit after their missions have ended. In this paper, we review current spacecraft passivation philosophies and principles, as well as how those principles have been applied in practice. In particular, we focus on how NASA programs have addressed spacecraft passivation. We begin by considering and reviewing general passivation requirements, with specific emphasis on pressure vessel passivation. We discuss passivation approaches used in several recent NASA missions as well as some practical considerations in spacecraft passivation, and conclude by providing some summary guidelines regarding what may be considered acceptable (reduced) pressure level targets (depending on the tank commodity and the type of propulsion system) that could allow the pressure vessel to be considered in a passivated state.

Scott Hull↗
NASA NTRS2022

Spacecraft Passivation - An Overview of Requirements, Principles, and Practices as Applied to Spacecraft Pressure Vessels

Explosions, collisions, and other catastrophic breakups of launch vehicle orbital stages and satellites continue to be major contributors to the generation of orbital debris. Both launch vehicles and payload satellites typically have several types of stored energy sources on board, any of which might result in energetic breakups and the creation of debris after their mission has ended. These energy sources include propulsion systems, pressure vessels, reaction wheels, control moment gyros, heat pipes, and power systems. NASA, ESA, JAXA and other space-faring organizations have requirements in place to limit the growth of the orbital debris population by passivating space vehicles that remain in orbit after their missions have ended. In this paper, we review current spacecraft passivation philosophies and principles, as well as how those principles have been applied in practice. In particular, we focus on how NASA programs have addressed spacecraft passivation. We begin by considering and reviewing general passivation requirements, with specific emphasis on pressure vessel passivation. We then discuss passivation approaches used in several recent NASA missions as well as some practical considerations in spacecraft passivation, and conclude by providing some summary guidelines regarding what may be considered acceptable (reduced) pressure level targets (depending on the tank commodity and the type of propulsion system) that could allow the pressure vessel to be considered in a passivated state.

Scott Hull↗
NASA NTRS2021

NASA High Efficiency, High OPR Capable Small Core Compressor

As future aircraft become lighter and more aerodynamically efficient, thrust requirements will decrease, reducing the core size of the engine. Furthermore, in the pursuit of improved fuel burn, engine overall pressure ratio and bypass ratio will increase, further driving down engine core size (core size being defined as high-pressure compressor [HPC] exit-corrected flow). These drivers together mean that the core size for future single-aisle aircraft applications will shrink below 3.0 lb/s. Traditionally, this small core compressor size is in the domain of axi-centrifugal designs, machines that are typically less efficient and limited to pressure ratios of ~25 due to stress and thermomechanical fatigue in the centrifugal impeller. In this light, NASA and Pratt & Whtiney (P&W) embarked upon a program to develop technologies to enable an all-axial high-pressure compressor with a core size below 3.0 lb/s and an overall pressure ratio greater than 50. The challenge with an all-axial high-pressure compressor at this core size is the small span at the rear of the compressor. As core size is scaled down, the rotor tip clearances, stator hub seal clearances, fillet sizes and leading edge thicknesses do not scale, leading to significant efficiency penalties. The goal of this program is to recover this lapse and realize the cycle benefits of small core size and high overall pressure ratio. The small core challenges described are mitigated through design optimization and technology insertion, enabling an estimated 5 to 10% fuel burn reduction relative to 2020 best-in-class. Three test rigs run at NASA Glenn Research Center evolved the small core design: a low-speed rig to vet technology and validate tools, and two high speeds rigs, the first to demonstrate an optimized meanline design and the second to validate technology to manage large rotor tip gaps. The efficiency improvement validated with these rigs has unlocked the small core design space, demonstrating that small core compressors can maintain a similar efficiency to current best-in-class large core size compressors. In addition to advancing the state-of-the-art of technology, the program has also advanced the modeling standards for multistage compressors with large clearance-to-span ratios. A best practice modeling standard was developed over the course of the program, incorporating learning from all three rig programs.

Axial Compressors↗