Search NASA⌕ Search

SEARCH · Search NASA

Results for “Reusable”

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 739 records · Page 41
All sourcesNASA NTRSDOE OSTI
NASA NTRS1987

A controlled experiment on the impact of software structure on maintainability

The impact of software structure on maintainability aspects including comprehensibility, locality, modifiability, and reusability in a distributed system environment is studied in a controlled maintenance experiment involving six medium-size distributed software systems implemented in LADY (language for distributed systems) and six in an extended version of sequential PASCAL. For all maintenance aspects except reusability, the results were quantitatively given in terms of complexity metrics which could be automated. The results showed LADY to be better suited to the development of maintainable software than the extension of sequential PASCAL. The strong typing combined with high parametrization of units is suggested to improve the reusability of units in LADY.

Rombach, Dieter H.↗
NASA NTRS1986

Programming support environment issues in the Byron programming environment

Issues are discussed which programming support environments need to address in order to successfully support software engineering. These concerns are divided into two categories. The first category, issues of how software development is supported by an environment, includes support of the full life cycle, methodology flexibility, and support of software reusability. The second category contains issues of how environments should operate, such as tool reusability and integration, user friendliness, networking, and use of a central data base. This discussion is followed by an examination of Byron, an Ada based programming support environment developed at Intermetrics, focusing on the solutions Byron offers to these problems, including the support provided for software reusability and the test and maintenance phases of the life cycle. The use of Byron in project development is described briefly, and some suggestions for future Byron tools and user written tools are presented.

Larsen, Matthew J.↗
NASA NTRS1986

Certification of Ada parts for reuse

One of the claims made by proponents of Ada is that Ada software is highly reusable. The fact that specifications are compiled and accessible would make reusability seem easily achievable. However, specifications give only a limited amount of information about a package; moreover, a specification cannot help determine whether a package worked, or how well it worked. This problem has led to the concept of certifying Ada parts for reuse; that is, determining the worthiness of a part as a reusable component. Issues that are critical to reuse are addressed: the characterization of part performance, design for reuse, and correct utilization of parts. Current areas of study beneficial in the development of a certification process are then addressed.

Hansen, Gregory A.↗
NASA NTRS1990

A preliminary TPS design for MRSR - Aerobraking at Mars and at earth

An investigation was made to determine the feasibility of using an aerobrake system for an unmanned mission to Mars and for a return vehicle to earth. A preliminary thermal protection system (TPS) is examined for two small nose radius, straight biconic vehicles aerocapturing at Mars. The TPS for these vehicles, entering at 6 km/s and 8 km/s, are shown to have an advantage over a propulsive burn velocity reduction for orbit insertion. The TPS for each vehicle consisted of an ablator in the region of high heating, and reusable insulation over the rest of the structure. It was determined that a reusable TPS could be used over 98 percent of the aeroshell structure. Also presented is the preliminary TPS design for an Apollo-shaped vehicle aerocapturing at earth. As with the biconics, this vehicle had an ablator in the region of high heating, and reusable insulation on the aft conic section. In contrast to the vehicles aerocapturing at Mars, the ablator is used on 63 percent of the vehicle's aeroshell structure.

Williams, S. D.↗
NASA NTRS1990

Cyclic hot firing results of tungsten-wire-reinforced, copper-lined thrust chambers

An advanced thrust liner material for potential long life reusable rocket engines is described. This liner material was produced with the intent of improving the reusable life of high pressure thrust chambers by strengthening the chamber in the hoop direction, thus avoiding the longitudinal cracking due to low cycle fatigue that is observed in conventional homogeneous copper chambers, but yet not reducing the high thermal conductivity that is essential when operating with high heat fluxes. The liner material produced was a tungsten wire reinforced copper composite. Incorporating this composite into two hydrogen-oxygen test rocket chambers was done so that its performance as a reusable liner material could be evaluated. Testing results showed that both chambers failed prematurely, but the crack sites were perpendicular to the normal direction of cracking indicating a degree of success in containing the tremendous thermal strain associated with high temperature rocket engines. The failures, in all cases, were associated with drilled instrumentation ports and no other damages or deformations were found elsewhere in the composite liners.

Kazaroff, John M.↗
NASA NTRS1993

A packet-based concept for spacecraft command planning

The current generation of spacecraft being developed and operated by the Applied Physics Laboratory provides users with access to a broad spectrum of scientific instruments on maneuverable platforms that can be oriented for observation of both moving and stationary targets of interest. The capability of these increasingly complex spacecraft to perform data collection operations is approaching one observation per orbit. To enable both rapid configuration and generation of complex spacecraft command sequences, as well as reusability of command sequences among data collection operations, a packet-based concept for spacecraft command planning has been developed. The configuration of the spacecraft for any operation is designed using 'packets' where a packet represents a set of commands that is reusable. The packets can be combined in varying levels of functionality, and in varying time relationships, to create an observation timeline. At the lowest packet level are primitives. Primitives relate the details of command generation for a particular spacecraft to a 'message template.' Thus the packet concept itself is reusable from one spacecraft to the next.

Barnes, Valerie B.↗
NASA NTRS1994

The Rationale/Benefits of Nuclear Thermal Rocket Propulsion for NASA's Lunar Space Transportation System

The solid core nuclear thermal rocket (NTR) represents the next major evolutionary step in propulsion technology. With its attractive operating characteristics, which include high specific impulse (approximately 850-1000 s) and engine thrust-to-weight (approximately 4-20), the NTR can form the basis for an efficient lunar space transportation system (LTS) capable of supporting both piloted and cargo missions. Studies conducted at the NASA Lewis Research Center indicate that an NTR-based LTS could transport a fully-fueled, cargo-laden, lunar excursion vehicle to the Moon, and return it to low Earth orbit (LEO) after mission completion, for less initial mass in LEO than an aerobraked chemical system of the type studied by NASA during its '90-Day Study.' The all-propulsive NTR-powered LTS would also be 'fully reusable' and would have a 'return payload' mass fraction of approximately 23 percent--twice that of the 'partially reusable' aerobraked chemical system. Two NTR technology options are examined--one derived from the graphite-moderated reactor concept developed by NASA and the AEC under the Rover/NERVA (Nuclear Engine for Rocket Vehicle Application) programs, and a second concept, the Particle Bed Reactor (PBR). The paper also summarizes NASA's lunar outpost scenario, compares relative performance provided by different LTS concepts, and discusses important operational issues (e.g., reusability, engine 'end-of life' disposal, etc.) associated with using this important propulsion technology.

Borowski, Stanley K.↗
NASA NTRS1994

Taking advantage of ground data systems attributes to achieve quality results in testing software

During the software development life cycle process, basic testing starts with the development team. At the end of the development process, an acceptance test is performed for the user to ensure that the deliverable is acceptable. Ideally, the delivery is an operational product with zero defects. However, the goal of zero defects is normally not achieved but is successful to various degrees. With the emphasis on building low cost ground support systems while maintaining a quality product, a key element in the test process is simulator capability. This paper reviews the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) test tool that is used in the acceptance test process for unmanned satellite operations control centers. The TASS is designed to support the development, test and operational environments of the Goddard Space Flight Center (GSFC) operations control centers. The TASS uses the same basic architecture as the operations control center. This architecture is characterized by its use of distributed processing, industry standards, commercial off-the-shelf (COTS) hardware and software components, and reusable software. The TASS uses much of the same TPOCC architecture and reusable software that the operations control center developer uses. The TASS also makes use of reusable simulator software in the mission specific versions of the TASS. Very little new software needs to be developed, mainly mission specific telemetry communication and command processing software. By taking advantage of the ground data system attributes, successful software reuse for operational systems provides the opportunity to extend the reuse concept into the test area. Consistency in test approach is a major step in achieving quality results.

Sigman, Clayton B.↗
NASA NTRS1997

Methyl Chloroform Elimination from the Production of Space Shuttle Sold Rocket Motors

Thiokol Space Operations manufactures the Reusable Solid Rocket Motors used to launch America's fleet of Space Shuttles. In 1989, Thiokol used more than 1.4 Mlb of methyl chloroform to produce rocket motors. The ban placed by the Environmental Protection Agency on the sale of methyl chloroform had a significant effect on future Reusable Solid Rocket Motor production. As a result, changes in the materials and processes became necessary. A multiphased plan was established by Thiokol in partnership with NASA's Marshall Space Flight Center to eliminate the use of methyl chloroform in the Reusable Solid Rocket Motor production process. Because of the extensive scope of this effort, the plan was phased to target the elimination of the majority of methyl chloroform use (90 percent) by January 1, 1996, the 3 Environmental Protection Agency deadline. Referred to as Phase I, this effort includes the elimination of two large vapor degreasers, grease diluent processes, and propellant tooling handcleaning using methyl chloroform. Meanwhile, a request was made for an essential use exemption to allow the continued use of the remaining 10 percent of methyl chloroform after the 1996 deadline, while total elimination was pursued for this final, critical phase (Phase II). This paper provides an update to three previous presentations prepared for the 1993, 1994, and 1995 CFC/Halon Alternative Conferences, and will outline the overall Ozone Depleting Compounds Elimination Program from the initial phases through the final testing and implementation phases, including facility and equipment development. Processes and materials to be discussed include low-pressure aqueous wash systems, high-pressure water blast systems- environmental shipping containers, aqueous and semi-aqueous cleaning solutions, and bond integrity and inspection criteria. Progress toward completion of facility implementation and lessons learned during the scope of the program, as well as the current development efforts and basic requirements of future methyl chloroform handcleaning elimination, will also be outlined.

Golde, Rick P.↗
NASA NTRS1998

X-34 Experimental Aeroheating at Mach 6 and 10

Critical technologies are being developed to support the goals of the NASA Office of Aeronautics and Space Transportation Technology Access to Space initiative for next-generation reusable space transportation systems. From the perspective of aerothermodynamic performance throughout the flight trajectory, the Reusable Launch Vehicle program incorporates conceptual analysis, ground-based testing, and computational fluid dynamics to provide flyable suborbital flight demonstrator vehicles. This report provides an overview of the hypersonic aeroheating wind tunnel test program conducted at the NASA Langley Research Center in support of one of these vehicles, the X-34 small reusable technology demonstrator program. Global surface heat transfer images, surface streamline patterns, and shock shapes were measured on 0.0153- and 0.0183-scale models of proposed X-34 flight vehicles at Mach 6 and 10 in air. The primary parametrics that were investigated include angles-of-attack from 0 to 35 deg. and freestream unit Reynolds numbers from 0.5 to 8 million per foot (which was sufficient to produce laminar, transitional, and turbulent heating data), both with and without control surface deflections. Comparisons of the experimental data to computational predictions are included, along with a discussion of the implications of some of the experimental flow features for the flight vehicle.

Berry, Scott A.↗
NASA NTRS1999

Rocket-Based Combined Cycle Activities in the Advanced Space Transportation Program Office

NASA's Office of Aero-Space Technology (OAST) has established three major goals, referred to as, "The Three Pillars for Success". The Advanced Space Transportation Program Office (ASTP) at the NASA's Marshall Space Flight Center (MSFC) in Huntsville, Ala. focuses on future space transportation technologies Under the "Access to Space" pillar. The Core Technologies Project, part of ASTP, focuses on the reusable technologies beyond those being pursued by X-33. One of the main activities over the past two and a half years has been on advancing the rocket-based combined cycle (RBCC) technologies. In June of last year, activities for reusable launch vehicle (RLV) airframe and propulsion technologies were initiated. These activities focus primarily on those technologies that support the decision to determine the path this country will take for Space Shuttle and RLV. This year, additional technology efforts in the reusable technologies will be awarded. The RBCC effort that was completed early this year was the initial step leading to flight demonstrations of the technology for space launch vehicle propulsion.

Hueter, Uwe↗
NASA NTRS1997

Rocketdyne RBCC Concept Development

Rocketdyne is pursuing the conceptual design and development of a Rocket Based Combined Cycle (BBCC) engine for booster and SSTO, advanced reusable space transportation systems under the Advanced Reusable Transportation Technologies contract with NASA Marshall Space Flight Center. The Rocketdyne concept is a fixed geometry integrated rocket, ramjet, scramjet which is hydrogen fueled and uses hydrogen regenerative cooling. Vision vehicle integration studies have determined that scramjet operation to the range of Mach 10 to 12 has high payoff for low cost reusable space transportation. Rocketdyne is internally developing versions of the concept for other applications in high speed aircraft and missiles with hydrocarbon fuel systems. A subscale engine ground test program is underway for all modes of operation from takeoff to Mach 8. High altitude rocket tests will only be completed as part of the ground test program to validate high expansion ratio performance. A unique feature of the ground test series is the inclusion of dynamic trajectory simulation with real time Mach number, altitude, engine throttling, and RBCC mode changes in a specially modified freejet test facility at GASL. Preliminary cold flow air augmented rocket and all rocket test results have met program goals and have been used to integrate all modes of operation in a single combustor design with a fixed geometry inlet for design confirmation tests. A water cooled subscale engine is currently being fabricated for test during the early part of 1998.

Ortwerth, P.↗
NASA NTRS1998

Lifting Body Flight Vehicles

NASA has a technology program in place to build the X-33 test vehicle and then the full sized Reusable Launch Vehicle, VentureStar. VentureStar is a Lifting Body (LB) flight vehicle which will carry our future payloads into orbit, and will do so at a much reduced cost. There were three design contenders for the new Reusable Launch Vehicle: a Winged Vehicle, a Vertical Lander, and the Lifting Body(LB). The LB design won the competition. A LB vehicle has no wings and derives its lift solely from the shape of its body, and has the unique advantages of superior volumetric efficiency, better aerodynamic efficiency at high angles-of-attack and hypersonic speeds, and reduced thermal protection system weight. Classically, in a ballistic vehicle, drag has been employed to control the level of deceleration in reentry. In the LB, lift enables the vehicle to decelerate at higher altitudes for the same velocity and defines the reentry corridor which includes a greater cross range. This paper outlines our LB heritage which was utilized in the design of the new Reusable Launch Vehicle, VentureStar. NASA and the U.S. Air Force have a rich heritage of LB vehicle design and flight experience. Eight LB's were built and over 225 LB test flights were conducted through 1975 in the initial LB Program. Three LB series were most significant in the advancement of today's LB technology: the M2-F; HL-1O; and X-24 series. The M2-F series was designed by NASA Ames Research Center, the HL-10 series by NASA Langley Research Center, and the X-24 series by the Air Force. LB vehicles are alive again today.

Barret, Chris↗
NASA NTRS1997

NASA X-34 Technology in Motion

The X-34 technology development program is a joint industry/government project to develop, test, and operate a small, fully-reusable hypersonic flight vehicle. The objective is to demonstrate key technologies and operating concepts applicable to future reusable launch vehicles. Integrated in the vehicle are various systems to assure successful completion of mission objectives, including the Main Propulsion System (MPS). NASA-Marshall Space Flight Center (MSFC) is responsible for developing the X-34's MPS including the design and complete build package for the propulsion system components. The X-34 will be powered by the Fastrac Engine, which is currently in design and development at NASA-MSFC. Fastrac is a single-stage main engine, which burns a mixture of liquid oxygen (LOX) and kerosene(RP-1). The interface between the MPS and Fastrac engine are critical for proper system operation and technologies applicable to future reusable launch vehicles. Deneb's IGRIP software package with the Dynamic analysis option provided a key tool for conducting studies critical to this interface as well as a mechanism to drive the design of the LOX and RP-1 feedlines. Kinematic models were created for the Fastrac Engine and the feedlines for various design concepts. Based on the kinematic simulation within Envision, design and joint limits were verified and system interference controlled. It was also critical to the program to evaluate the effect of dynamic loads visually, providing a verification tool for dynamic analysis and in some cases uncovering areas that had not been considered. Deneb's software put the X-34 technology in motion and has been a key factor in facilitating the strenuous design schedule.

Beech, Geoffrey↗
NASA NTRS2000

Developing CORBA-Based Distributed Scientific Applications from Legacy Fortran Programs

Recent progress in distributed object technology has enabled software applications to be developed and deployed easily such that objects or components can work together across the boundaries of the network, different operating systems, and different languages. A distributed object is not necessarily a complete application but rather a reusable, self-contained piece of software that co-operates with other objects in a plug-and-play fashion via a well-defined interface. The Common Object Request Broker Architecture (CORBA), a middleware standard defined by the Object Management Group (OMG), uses the Interface Definition Language (IDL) to specify such an interface for transparent communication between distributed objects. Since IDL can be mapped to any programming language, such as C++, Java, Smalltalk, etc., existing applications can be integrated into a new application and hence the tasks of code re-writing and software maintenance can be reduced. Many scientific applications in aerodynamics and solid mechanics are written in Fortran. Refitting these legacy Fortran codes with CORBA objects can increase the codes reusability. For example, scientists could link their scientific applications to vintage Fortran programs such as Partial Differential Equation(PDE) solvers in a plug-and-play fashion. Unfortunately, CORBA IDL to Fortran mapping has not been proposed and there seems to be no direct method of generating CORBA objects from Fortran without having to resort to manually writing C/C++ wrappers. In this paper, we present an efficient methodology to integrate Fortran legacy programs into a distributed object framework. Issues and strategies regarding the conversion and decomposition of Fortran codes into CORBA objects are discussed. The following diagram shows the conversion and decomposition mechanism we proposed. Our goal is to keep the Fortran codes unmodified. The conversion- aided tool takes the Fortran application program as input and helps programmers generate C/C++ header file and IDL file for wrapping the Fortran code. Programmers need to determine by themselves how to decompose the legacy application into several reusable components based on the cohesion and coupling factors among the functions and subroutines. However, programming effort still can be greatly reduced because function headings and types have been converted to C++ and IDL styles. Most Fortran applications use the COMMON block to facilitate the transfer of large amount of variables among several functions. The COMMON block plays the similar role of global variables used in C. In the CORBA-compliant programming environment, global variables can not be used to pass values between objects. One approach to dealing with this problem is to put the COMMON variables into the parameter list. We do not adopt this approach because it requires modification of the Fortran source code which violates our design consideration. Our approach is to extract the COMMON blocks and convert them into a structure-typed attribute in C++. Through attributes, each component can initialize the variables and return the computation result back to the client. We have tested successfully the proposed conversion methodology based on the f2c converter. Since f2c only translates Fortran to C, we still needed to edit the converted code to meet the C++ and IDL syntax. For example, C++/IDL requires a tag in the structure type, while C does not. In this paper, we identify the necessary changes to the f2c converter in order to directly generate the C++ header and the IDL file. Our future work is to add GUI interface to ease the decomposition task by simply dragging and dropping icons.

Sang, Janche↗
NASA NTRS2001

The Launch Systems Operations Cost Model

One of NASA's primary missions is to reduce the cost of access to space while simultaneously increasing safety. A key component, and one of the least understood, is the recurring operations and support cost for reusable launch systems. In order to predict these costs, NASA, under the leadership of the Independent Program Assessment Office (IPAO), has commissioned the development of a Launch Systems Operations Cost Model (LSOCM). LSOCM is a tool to predict the operations & support (O&S) cost of new and modified reusable (and partially reusable) launch systems. The requirements are to predict the non-recurring cost for the ground infrastructure and the recurring cost of maintaining that infrastructure, performing vehicle logistics, and performing the O&S actions to return the vehicle to flight. In addition, the model must estimate the time required to cycle the vehicle through all of the ground processing activities. The current version of LSOCM is an amalgamation of existing tools, leveraging our understanding of shuttle operations cost with a means of predicting how the maintenance burden will change as the vehicle becomes more aircraft like. The use of the Conceptual Operations Manpower Estimating Tool/Operations Cost Model (COMET/OCM) provides a solid point of departure based on shuttle and expendable launch vehicle (ELV) experience. The incorporation of the Reliability and Maintainability Analysis Tool (RMAT) as expressed by a set of response surface model equations gives a method for estimating how changing launch system characteristics affects cost and cycle time as compared to today's shuttle system. Plans are being made to improve the model. The development team will be spending the next few months devising a structured methodology that will enable verified and validated algorithms to give accurate cost estimates. To assist in this endeavor the LSOCM team is part of an Agency wide effort to combine resources with other cost and operations professionals to support models, databases, and operations assessments.

Prince, Frank A.↗
NASA NTRS2001

Survey of Advanced Booster Options for Potential Shuttle Derivative Vehicles

A never-ending major goal for the Space Shuttle program is to continually improve flight safety, as long as this launch system remains in operational service. One of the options to improve system safety and to enhance vehicle performance as well, that has been seriously studied over the past several decades, is to replace the existing strap-on four segment solid rocket boosters (SRB's) with more capable units. A number of booster upgrade options have been studied in some detail, ranging from five segment solids through hybrids and a wide variety of liquid strap-ons (both pressure and pump fed with various propellants); all the way to a completely reusable liquid fly back booster (complete with air breathing engines for controlled landing and return). All of these possibilities appear to offer improvements in varying degrees; and each has their strengths and weaknesses from both programmatic and technical points of view. The most beneficial booster upgrade/design, if the shuttle program were to continue long enough to justify the required investment, would be an approach that greatly increased both vehicle and crew safety. This would be accomplished by increasing the minimum range/minimum altitude envelope that would readily allow abort to orbit (ATO), possibly even to zero/zero, and possibly reduce or eliminate the Return to Launch Site (RTLS) and even the Trans Atlantic Landing (TAL) abort mode requirements. This paper will briefly survey and discuss all of the various booster'upgrade options studied previously, and compare their relative attributes. The survey will explicitly discuss, in summary comparative form, options that include: five segment solids; several hybrid possibilities; pressure and/or pump-fed liquids using either LO2/kerosene, H2O/kerosene and LO2/J2, any of which could be either fully expendable, partly or fully reusable; and finally a fully reusable liquid fly back booster system, with a number of propellant and propulsion system options. Performance and configuration comparison illustrations and tables will be included to provide a comprehensive survey for the paper.

Sackheim, Robert L.↗
NASA NTRS2001

I(sup STAR), NASA's Next Step in Air-Breathing Propulsion for Space Access

The United States' National Aeronautics and Space Administration (NASA) has established a strategic plan for future activities in space. A primary goal of this plan is to make drastic improvements in the cost and safety of earth to low-earth-orbit transportation. One approach to achieving this goal is through the development of highly reusable, highly reliable space transportation systems analogous to the commercial airline system. In the year 2000, NASA selected the Rocket Based Combined Cycle (RBCC) engine as the next logical step towards this goal. NASA will develop a complete flight-weight, pump-fed engine system under the Integrated System Test of an Airbreathing Rocket (I(sup STAR)) Project. The objective of this project is develop a reusable engine capable of self-powering a vehicle through the air-augmented rocket, ramjet and scramjet modes required in all RBCC based operational vehicle concepts. The project is currently approved and funded to develop the engine through ground test demonstration. Plans are in place to proceed with flight demonstration pending funding approval. The project is in formulation phase and the Preliminary Requirements Review has been completed. The engine system and vehicle have been selected at the conceptual level. The I(sup STAR) engine concept is based on an air-breathing flowpath downselected from three configurations evaluated in NASA's Advanced Reusable Technology contract. The selected flowpath features rocket thrust chambers integrated into struts separating modular flowpath ducts, a variable geometry inlet, and a thermally choked throat. The engine will be approximately 220 inches long and 79 inches wide and fueled with a hydrocarbon fuel using liquid oxygen as the primary oxidizer candidate. The primary concept for the pump turbine drive is pressure-fed catalyzed hydrogen peroxide. In order to control costs, the flight demonstration vehicle will be launched from a B-52 aircraft. The vehicle concept is based on the Air Breathing Launch Vehicle 4 (ABLV4) lifting body configuration which has design heritage from NASA's NASP Program. The vehicle will be designed to accelerate from Mach 0.8 to Mach 7 and will be equipped with landing gear for horizontal landing. The complete vehicle, including the engine, will be designed for 25 flights and will be approximately 33 feet long with a total vehicle weight of approximately 25000 lbs.

Hutt, John J.↗