Search NASA⌕ Search

SEARCH · Search NASA

Results for “Practice Guidelines”

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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Closing the loop on improvement: Packaging experience in the Software Engineering Laboratory

As part of its award-winning software process improvement program, the Software Engineering Laboratory (SEL) has developed an effective method for packaging organizational best practices based on real project experience into useful handbooks and training courses. This paper shares the SEL's experience over the past 12 years creating and updating software process handbooks and training courses. It provides cost models and guidelines for successful experience packaging derived from SEL experience.

Waligora, Sharon R.↗
NASA NTRS1990

Seven ways to make a hypertext project fail

Hypertext is an exciting concept, but designing and developing hypertext applications of practical scale is hard. To make a project feasible and successful 'hypertext engineers' must overcome the following problems: (1) developing realistic expectations in the face of hypertext hype; (2) assembling a multidisciplinary project team; (3) establishing and following design guidelines; (4) dealing with installed base constraints; (5) obtaining usable source files; (6) finding appropriate software technology and methods; and (7) overcoming legal uncertainties about intellectual property concerns.

Glushko, Robert J.↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
NASA NTRS2007

CanSat Competition: Contributing to the Development of NASA's Vision for Robotic Space Exploration

CanSat is an international student design-build-launch competition organized by the American Astronautical Society (AAS) and American Institute of Aeronautics and Astronautics (AIAA). The competition is also sponsored by the Naval Research Laboratory (NRL) and the National Aeronautics and Space Administration (NASA). The CanSat competition is designed for college, university and high school students wanting to participate in an applicable space-related competition. The objective of the CanSat competition is to complete space exploration missions by designing a specific system for a small sounding rocket payload which will follow and perform to a specific set of rules and guidelines for each year's competition. The competition encompasses a complete life-cycle of one year which includes all phases of design, integration, testing, judging and competition. The mission guidelines are based from space exploration missions and include bonus requirement options which teams may choose to participate in. The fundamental goal of the competition is to educate future engineers and scientists. This is accomplished by students applying systems engineering practices to a development project that incorporates an end-to-end life cycle, from requirements analysis, through preliminary design, integration and testing, an actual flight of the CanSat, and concluding with a post-mission debrief. This is done specifically with space related missions to bring a unique aspect of engineering and design to the competition. The competition has been progressing since its creation in 2005. The competition was originally meant to purely convey the engineering and design process to its participants, but through many experiences the competition has also undergone a learning experience with respect to systems engineering process and design. According

Berman, Joshua↗
NASA NTRS1996

System Guidelines for EMC Safety-Critical Circuits: Design, Selection, and Margin Demonstration

Demonstration of safety margins for critical points (circuits) has traditionally been required since it first became a part of systems-level Electromagnetic Compatibility (EMC) requirements of MIL-E-6051C. The goal of this document is to present cost-effective guidelines for ensuring adequate Electromagnetic Effects (EME) safety margins on spacecraft critical circuits. It is for the use of NASA and other government agencies and their contractors to prevent loss of life, loss of spacecraft, or unacceptable degradation. This document provides practical definition and treatment guidance to contain costs within affordable limits.

Lawton, R. M.↗
NASA NTRS2001

National Environmental Change Information System Case Study

The Global Hydrology and Climate Center and NASA's Marshall Space Flight Center conducted a fact-finding case study for the Data Management Working Group (DMWG), now referred to as the Data and Information Working Group (DIWG), of the U.S. Global Change Research Program (USGCRP) to determine the feasibility of an interagency National Environmental Change Information System (NECIS). In order to better understand the data and information needs of policy and decision makers at the national, state, and local level, the DIWG asked the case study team to choose a regional water resources issue in the southeastern United States that had an impact on a diverse group of stakeholders. The southeastern United States was also of interest because the region experiences interannual climatic variations and impacts due to El Nino and La Nina. Jointly, with input from the DIWG, a focus on future water resources planning in the Apalachicola-Chattahoochee-Flint (ACF) River basins of Alabama, Georgia, and Florida was selected. A tristate compact and water allocation formula is currently being negotiated between the states and U.S. Army Corps of Engineers (COE) that will affect the availability of water among competing uses within the ACF River basin. All major reservoirs on the ACF are federally owned and operated by the U.S. Army COE. A similar two-state negotiation is ongoing that addresses the water allocations in the adjacent Alabama-Coosa-Tallapoosa (ACT) River basin, which extends from northwest Georgia to Mobile Bay. The ACF and ACT basins are the subject of a comprehensive river basin study involving many stakeholders. The key objectives of this case study were to identify specific data and information needs of key stakeholders in the ACF region, determine what capabilities are needed to provide the most practical response to these user requests, and to identify any limitations in the use of federal data and information. The NECIS case study followed the terms of reference developed by the interagency DIWG. The case study "lessons learned" and "key findings" offer guidelines and considerations to the DMWG for the development and implementation of a NECIS that would support the data and information needs of policy and decision makers at the national, state, and local level.

Goodman, S. J.↗
NASA NTRS2008

Misalignment in Gas Foil Journal Bearings: An Experimental Study

As gas foil journal bearings become more prevalent in production machines, such as small gas turbine propulsion systems and microturbines, system-level performance issues must be identified and quantified in order to provide for successful design practices. Several examples of system-level design parameters that are not fully understood in foil bearing systems are thermal management schemes, alignment requirements, balance requirements, thrust load balancing, and others. In order to address some of these deficiencies and begin to develop guidelines, this paper presents a preliminary experimental investigation of the misalignment tolerance of gas foil journal bearing systems. Using a notional gas foil bearing supported rotor and a laser-based shaft alignment system, increasing levels of misalignment are imparted to the bearing supports while monitoring temperature at the bearing edges. The amount of misalignment that induces bearing failure is identified and compared to other conventional bearing types such as cylindrical roller bearings and angular contact ball bearings. Additionally, the dynamic response of the rotor indicates that the gas foil bearing force coefficients may be affected by misalignment.

Howard, Samuel A.↗
NASA NTRS2009

Modeling Guidelines for Code Generation in the Railway Signaling Context

Modeling guidelines constitute one of the fundamental cornerstones for Model Based Development. Their relevance is essential when dealing with code generation in the safety-critical domain. This article presents the experience of a railway signaling systems manufacturer on this issue. Introduction of Model-Based Development (MBD) and code generation in the industrial safety-critical sector created a crucial paradigm shift in the development process of dependable systems. While traditional software development focuses on the code, with MBD practices the focus shifts to model abstractions. The change has fundamental implications for safety-critical systems, which still need to guarantee a high degree of confidence also at code level. Usage of the Simulink/Stateflow platform for modeling, which is a de facto standard in control software development, does not ensure by itself production of high-quality dependable code. This issue has been addressed by companies through the definition of modeling rules imposing restrictions on the usage of design tools components, in order to enable production of qualified code. The MAAB Control Algorithm Modeling Guidelines (MathWorks Automotive Advisory Board)[3] is a well established set of publicly available rules for modeling with Simulink/Stateflow. This set of recommendations has been developed by a group of OEMs and suppliers of the automotive sector with the objective of enforcing and easing the usage of the MathWorks tools within the automotive industry. The guidelines have been published in 2001 and afterwords revisited in 2007 in order to integrate some additional rules developed by the Japanese division of MAAB [5]. The scope of the current edition of the guidelines ranges from model maintainability and readability to code generation issues. The rules are conceived as a reference baseline and therefore they need to be tailored to comply with the characteristics of each industrial context. Customization of these recommendations has been performed for the automotive control systems domain in order to enforce code generation [7]. The MAAB guidelines have been found profitable also in the aerospace/avionics sector [1] and they have been adopted by the MathWorks Aerospace Leadership Council (MALC). General Electric Transportation Systems (GETS) is a well known railway signaling systems manufacturer leading in Automatic Train Protection (ATP) systems technology. Inside an effort of adopting formal methods within its own development process, GETS decided to introduce system modeling by means of the MathWorks tools [2], and in 2008 chose to move to code generation. This article reports the experience performed by GETS in developing its own modeling standard through customizing the MAAB rules for the railway signaling domain and shows the result of this experience with a successful product development story.

Ferrari, Alessio↗
NASA NTRS1978

NASTRAN implementation of an isoparametric doubly-curved quadrilateral shell element

A quadrilateral shell element, CQUAD4, was added to level 15.5 and subsequently to level 16.0 of NASTRAN. The element exhibited doubly curved surfaces and used biquadratic interpolation functions. Reduced integration techniques were used to improve the performance of the element in thin shell problems. The creation of several new bulk data items is discussed, along with a special module, GPNORM, to process SHLNORM bulk data cards. In addition to the theoretical basis for the element stiffness matrix, consistent mass and load matrices are presented. Several potential sources of degenerate behavior of the element were investigated. Guidelines for proper use of the element were suggested. Performance of the element on several widely published classical examples was demonstrated. The results showed a significant improvement over presently available NASTRAN shell elements for even the coarsest meshes. Potential applications to two classes of practical problems are discussed.

Potvin, A. B.↗
NASA NTRS2017

Helicopter Flight Procedures for Community Noise Reduction

A computationally efficient, semiempirical noise model suitable for maneuvering flight noise prediction is used to evaluate the community noise impact of practical variations on several helicopter flight procedures typical of normal operations. Turns, "quick-stops," approaches, climbs, and combinations of these maneuvers are assessed. Relatively small variations in flight procedures are shown to cause significant changes to Sound Exposure Levels over a wide area. Guidelines are developed for helicopter pilots intended to provide effective strategies for reducing the negative effects of helicopter noise on the community. Finally, direct optimization of flight trajectories is conducted to identify low noise optimal flight procedures and quantify the magnitude of community noise reductions that can be obtained through tailored helicopter flight procedures. Physically realizable optimal turns and approaches are identified that achieve global noise reductions of as much as 10 dBA Sound Exposure Level.

Greenwood, Eric↗
NASA NTRS1994

On the design of flight-deck procedures

In complex human-machine systems, operations, training, and standardization depend on a elaborate set of procedures which are specified and mandated by the operational management of the organization. The intent is to provide guidance to the pilots, to ensure a logical, efficient, safe, and predictable means of carrying out the mission objectives. In this report the authors examine the issue of procedure use and design from a broad viewpoint. The authors recommend a process which we call 'The Four P's:' philosophy, policies, procedures, and practices. We believe that if an organization commits to this process, it can create a set of procedures that are more internally consistent, less confusing, better respected by the flight crews, and that will lead to greater conformity. The 'Four-P' model, and the guidelines for procedural development in appendix 1, resulted from cockpit observations, extensive interviews with airline management and pilots, interviews and discussion at one major airframe manufacturer, and an examination of accident and incident reports. Although this report is based on airline operations, we believe that the principles may be applicable to other complex, high-risk systems, such as nuclear power production, manufacturing process control, space flight, and military operations.

Degani, Asaf↗
NASA NTRS2024

Ejecta Management in a Safe Lithium Ion Battery Design

As lithium-ion battery energy densities continue to rise, managing the heat and pressure generated during failure events has become increasingly critical. Safety systems must effectively relieve pressure without releasing sparks, flames, or particulate matter, requiring robust filtration solutions. The challenge is compounded by the reduced free volume available for gas expansion in high-density designs, which increases the demands on these filters. While significant progress has been made through experimental studies and modeling efforts to understand the behavior of ejecta during battery failures, there remains a pressing need for practical, rule-of-thumb sizing parameters. These parameters would help correlate high-energy waste streams with appropriate filter design, ensuring reliable containment and safety. This talk will explore recent experimental findings in this area and discuss the potential pathways for developing these essential sizing guidelines.

Ejecta Management↗
NASA NTRS1999

Protecting the GEO Environment: Policies and Practices

The geosynchronous orbital regime has long been recognized as a unique space resource, dictating special measures to ensure its continuing use for future generations. During the past 20 years a variety of national and international policies have been developed to preserve this environment. A review of current practices involving the deployment and disposal of geosynchronous spacecraft, associated upper stages and apogee kick motors, and geosynchronous orbit transfer objects indicates both positive and negative trends. Most spacecraft operators are indeed performing end-of-mission maneuvers, but the boost altitudes normally fall short of policy guidelines. Russia, a major operator in geosynchronous orbit, maneuvers only 1 in 3 spacecraft out of the region, while China has never refired a spacecraft above GEO. The viability of voluntary protection measures for this regime depends upon the responsible actions of the aerospace community as a whole.

Johnson, Nicholas L.↗
NASA NTRS2001

Goals, History and Current Programs of Workshop

Mr. Robert Fusaro, coordinator for the Glenn Research Center Space Mechanisms program, presented the goals of the workshop, history of previous workshops and gave an overview of current space mechanisms work performed by Glenn Research Center. Highlights of his presentation are shown. Following the presentation, Mr. Fusaro demonstrated the new NASA Space Mechanisms Handbook and Reference Guide CD ROM, which was featured as a highlight of the workshop. The handbook is an authoritative guide for design and testing of space mechanisms and related components. Over 600 pages of guidelines written by 25 experts in the field provide in-depth information on how to design space mechanisms and components, including: deployables, release devices, latches, rotating and pointing mechanisms, dampers, motors, gears, fasteners, valves, etc. The handbook provides details on appropriate environmental and tribological testing methods and practices required to evaluate new mechanisms and components. Distribution of the Handbook and Reference Guide is limited by ITAR (International Traffic in Arms Regulations). It is available only to US companies and citizens. A request form for the CD ROM can be found on the Space Mechanisms Project website at http://www.grc.nasa.gov/WWW/spacemech/.

Source record↗
NASA NTRS2010

Medium Earth Orbits: Is There a Need for a Third Protected Region?

The Inter-Agency Space Debris Coordination Committee (IADC) and the United Nations have adopted the concept of near-Earth regions which should be afforded protection from the accumulation of orbital debris. These regions are low Earth orbit (LEO), which extends up to 2000 km altitude, and geosynchronous orbit (GEO), which includes the volume of space encompassed by 35,786 km +/- 200 km in altitude and +/- 15 degrees in inclination. The region between LEO and GEO is commonly referred to as Medium Earth Orbit (MEO). Although historically a small minority of spacecraft have operated in MEO, the number of such satellites residing in or routinely transiting the zone is increasing. The question thus arises: should MEO be considered an orbital debris protected region? This paper first reviews the characteristics of space systems now utilizing MEO, as well as those anticipated to join them in the near future. MEO is then contrasted with LEO and GEO, both physically and pragmatically. Recommended orbital debris mitigation guidelines for MEO space vehicles are highlighted, and the challenges of spacecraft and launch vehicle stage disposal are recognized. Note is also made of the principal tenets of the United Nations Outer Space Treaty and of recent trends toward de facto partitioning of MEO. Finally, the efficacy and practicality of establishing MEO as a new protected region with regard to orbital debris is addressed.

Johnson, Nicholas L.↗
NASA NTRSDate not supplied

Credible Practice of Models and Simulations for Healthcare

As computational models penetrate clinical care and drive healthcare policy decisions, there is increasing need to communicate that model creation and testing follows reasonable credible practice. Although verification and validation have been generally accepted as significant components of a model’s credibility, they cannot be assumed to equate to a holistic credible practice, which includes activities that can impact comprehension and in-depth examination inherent in the development and reuse of the models. This presentation introduces the Ten Rules for credible practice of modeling and simulation in healthcare developed from a comparative multidisciplinary analysis and practitioner survey. These rules establish a unified conceptual framework for modeling and simulation design, implementation, evaluation, dissemination and usage across the modeling and simulation life-cycle. Although some of these are common sense guidelines, many are often missed or misconstrued, even by seasoned practitioners.

credibility↗
NASA NTRS1978

Space Shuttle SRM metal case component fabrication

The 146 in. diam metal case components of the Space Shuttle Solid Rocket Motor (SRM) being developed have been successfully static-tested. The limitations placed on the program included current practice and facilities at the steel mills, forging suppliers, heat treaters, and machining operations. In addition, Thiokol had not previously fabricated metal components of this size with a minimum fracture toughness of 90 ksi-in. to 1/2 power. To insure that the SRM was producible within the established guidelines, it was necessary to coordinate all data heat by heat, forging by forging, and heat treat run by heat treat run. The basic fabrication sequences are outlined, and the data from the heat treat programs are presented.

Krummel, C. H.↗
NASA NTRS2004

Harnessing: Technologies for Sustainable Reindeer Husbandry in the Arctic

To accelerate the development of sustainable reindeer husbandry under the lead of indigenous reindeer herders, it is critical to empower reindeer herders with the best available technologies and to promote a new kind of science where traditional knowledge is fully integrated into the scientific management of the natural environment in the Arctic. This is particularly true given the dramatic environmental, climatic, economic, social and industrial changes, which have taken place across the Arctic in recent years, all of which have had serious impacts on the reindeer herding communities of the North. The Anar Declaration, adopted by the 2d World Reindeer Herders Congress (WRHC), in Inari, Finland, June 2001drew guidelines for the development of a sustainable reindeer husbandry based on reindeer peoples values and goals. The declaration calls for the reindeer herding peoples to be given the possibilities to develop and influence the management of the reindeer industry and its natural environment because of their knowledge and traditional practices. At the same time, Arctic scientists from many institutions and governments are carrying out increasingly highly technical reindeer related research activities. It is important that the technologies and results of these activities be more commonly co-produced with the reindeer herder community and/or made more readily available to the reindeer peoples for comparison with traditional knowledge for improved herd management. This paper describes a project in which reindeer herders and scientists are utilizing technologies to create a system for collecting and sharing knowledge. The project, Reindeer Mapper, is creating an information management and knowledge sharing system, which will help make technologies more readily available to the herder community for observing, data collection and analysis, monitoring, sharing, communications, and dissemination of information - to be integrated with traditional, local knowledge. The paper describes some of the technologies which comprise the system including an intranet system to enable the team members to work together and share information electronically, remote sensing data for monitoring environmental parameters important to reindeer husbandry (e.g. SAR, Landsat), acquisition of ground-based measurements, and the GIS-based information management and knowledge sharing system.

Maynard, Nancy G.↗