Search NASA⌕ Search

SEARCH · Search NASA

Results for “Lessons”

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 307 records · Page 17

Measuring the software process and product: Lessons learned in the SEL

The software development process and product can and should be measured. The software measurement process at the Software Engineering Laboratory (SEL) has taught a major lesson: develop a goal-driven paradigm (also characterized as a goal/question/metric paradigm) for data collection. Project analysis under this paradigm leads to a design for evaluating and improving the methodology of software development and maintenance.

Basili, V. R.↗

High-angle-of-attack aerodynamics - Lessons learned

Recently, the military and civil technical communities have undertaken numerous studies of the high angle-of-attack aerodynamic characteristics of advanced airplane and missile configurations. The method of approach and the design methodology employed have necessarily been experimental and exploratory in nature, due to the complex nature of separated flows. However, despite the relatively poor definition of many of the key aerodynamic phenomena involved for high-alpha conditions, some generic guidelines for design consideration have been identified. The present paper summarizes some of the more important lessons learned in the area of high angle-of-attack aerodynamics with examples of a number of key concepts and with particular emphasis on high-alpha stability and control characteristics of high performance aircraft. Topics covered in the discussion include the impact of design evolution, forebody flows, control of separated flows, configuration effects, aerodynamic controls, wind-tunnel flight correlation, and recent NASA research activities.

Chambers, J. R.↗

Two gimbal bearing case studies: Some lessons learned

Two troublesome, torque related problems associated with gimbal actuators are discussed. Large, thin section angular contact bearings can have a surprisingly high torque sensitivity to radial thermal gradients. A predictive thermal-mechanical bearing analysis, as described, was helpful in establishing a safe temperature operating envelope. In the second example, end-of-travel torque limits of an oscillatory gimbal bearing appoached motor stall during limit cycling life tests. Bearing modifications required to restore acceptable torque performance are described. The lessons learned from these case studies should benefit designers of precision gimbals where singular bearing torque related problems are not uncommon.

Loewenthal, Stuart H.↗

The Solar Maximum Mission repair - Lessons learned

The on-orbit repair sequence of the Solar Maximum Mission in April 1984 is described, and important lessons learned concerning orbital debris are summarized. Scientific results pertaining to a solar flare which occurred just before the repair are reviewed. The implications of the repair experience for serviceability in the design of future spacecraft and instruments are illustrated by the case of the Hubble Space Telescope and its second generation spectrograph.

Woodgate, Bruce E.↗

ACES program - Lessons learned

The ACES Program involved the experimental evaluation of three LSS (large space structures) control design techniques at the LSS GTF (ground test facility) at NASA/MSFC. The three techniques were developed under the ACOSS (active control of space structures) Program specifically for application to LSS. The techniques included FAMESS (filter accommodated model error sensitivity suppression), HAC/LAC (high authority control/low authority control), and positivity. Some of the lessons that have been learned during the course of the ACES program are examined.

Jones, Victoria L.↗

Lessons learned: Managing the development of a corporate Ada training project

The management lessons learned during the implementation of a corporate mandate to develop and deliver an effective Ada training program to all divisions are discussed. The management process involved in obtaining cooperation from all levels in the development of a corporate-wide project is described. The problem areas are identified along with some possible solutions.

Blackmon, Linda F.↗

Lessons learned in creating spacecraft computer systems: Implications for using Ada (R) for the space station

Twenty-five years of spacecraft onboard computer development have resulted in a better understanding of the requirements for effective, efficient, and fault tolerant flight computer systems. Lessons from eight flight programs (Gemini, Apollo, Skylab, Shuttle, Mariner, Voyager, and Galileo) and three reserach programs (digital fly-by-wire, STAR, and the Unified Data System) are useful in projecting the computer hardware configuration of the Space Station and the ways in which the Ada programming language will enhance the development of the necessary software. The evolution of hardware technology, fault protection methods, and software architectures used in space flight in order to provide insight into the pending development of such items for the Space Station are reviewed.

Tomayko, James E.↗

Tethered system/space platform integration - TSS lessons learned

Tethered spacecraft systems must be integrated with their user platforms in a way that allows both to carry out their design functions efficiently and safely. This paper describes the lessons learned about tethered system integration with a space platform from the NASA/PSN Tethered Satellite System. Items discussed include platform attitude control, induced voltage and current control, satellite tracking and tether length measurement, satellite communications and system operations sensitivities. A number of engineering issues yet to be resolved are noted. Tethered systems are complex and require careful design to ensure successful operation.

Rudolph, L. K.↗

Lessons learned from trend analysis of Shuttle Payload Processing problem reports

In the wake of the Challenger accident, NASA has placed an increasing emphasis on trend analysis techniques. These analyses provide meaningful insights into system and hardware status, and also develop additional lessons learned from historical data to aid in the design and operation of future space systems. This paper presents selected results from such a trend analysis study that was conducted on the problem report data files for the Shuttle Payload Processing activities. Specifically, the results shown are for the payload canister system which interfaces with and transfers payloads from their processing facilities to the orbiter.

Heuser, Robert E.↗

Resource Allocation Planning Helper (RALPH): Lessons learned

The current task of Resource Allocation Process includes the planning and apportionment of JPL's Ground Data System composed of the Deep Space Network and Mission Control and Computing Center facilities. The addition of the data driven, rule based planning system, RALPH, has expanded the planning horizon from 8 weeks to 10 years and has resulted in large labor savings. Use of the system has also resulted in important improvements in science return through enhanced resource utilization. In addition, RALPH has been instrumental in supporting rapid turn around for an increased volume of special what if studies. The status of RALPH is briefly reviewed and important lessons learned from the creation of an highly functional design team are focused on through an evolutionary design and implementation period in which an AI shell was selected, prototyped, and ultimately abandoned, and through the fundamental changes to the very process that spawned the tool kit. Principal topics include proper integration of software tools within the planning environment, transition from prototype to delivered to delivered software, changes in the planning methodology as a result of evolving software capabilities and creation of the ability to develop and process generic requirements to allow planning flexibility.

Durham, Ralph↗

RSRA/X-Wing flight control system development - Lessons learned

The X-Wing, in concept, marries the efficiencies of a helicopter and fixed wing aircraft through the use of a four-bladed wing/rotor that can be rotated or stopped in flight. The RSRA/X-Wing flight test program was a technology demonstration of this concept which, after three successful flights, was discontinued in late 1987. In spite of many technical challenges in this program, such as the use of circulation control, the fabrication of a large all-composite rotor, the development of an advanced, quadruplex digital flight control system, and the need for higher harmonic control, no major technical problems had been encountered at the time of the stop-work order. This paper addresses the issues of flight control system development and focuses on lessons learned. As with other such programs, software development was the most consuming issue. Other subjects of discussion include the problems of balancing program goals with technical goals, software- and hard-ware-related problems, safety issues, and system testing.

Corliss, Lloyd D.↗

Establishing a measurement based maintenance improvement program - Lessons learned in the SEL

The Software Engineering Laboratory (SEL) is a joint venture between NASA's Goddard Space Flight Center, the University of Maryland, and Computer Sciences Corporation. The use of a goal-oriented approach to measurement to establish a maintenance improvement program within the SEL is discussed. Differences are found to exist between the initial phase of the program and its routine application. This approach is demonstrated through concrete examples, and lessons learned in the establishment of a measurement based, maintenance improvement program are summarized.

Rombach, H. Dieter↗

Capturing flight system test engineering expertise: Lessons learned

Within a few years, JPL will be challenged by the most active mission set in history. Concurrently, flight systems are increasingly more complex. Presently, the knowledge to conduct integration and test of spacecraft and large instruments is held by a few key people, each with many years of experience. JPL is in danger of losing a significant amount of this critical expertise, through retirement, during a period when demand for this expertise is rapidly increasing. The most critical issue at hand is to collect and retain this expertise and develop tools that would ensure the ability to successfully perform the integration and test of future spacecraft and large instruments. The proposed solution was to capture and codity a subset of existing knowledge, and to utilize this captured expertise in knowledge-based systems. First year results and activities planned for the second year of this on-going effort are described. Topics discussed include lessons learned in knowledge acquisition and elicitation techniques, life-cycle paradigms, and rapid prototyping of a knowledge-based advisor (Spacecraft Test Assistant) and a hypermedia browser (Test Engineering Browser). The prototype Spacecraft Test Assistant supports a subset of integration and test activities for flight systems. Browser is a hypermedia tool that allows users easy perusal of spacecraft test topics. A knowledge acquisition tool called ConceptFinder which was developed to search through large volumes of data for related concepts is also described and is modified to semi-automate the process of creating hypertext links.

Woerner, Irene Wong↗

LDEF electronic systems: Successes, failures, and lessons

Following the Long Duration Exposure Facility (LDEF) retrieval, the Systems Special Investigation Group (SIG) participated in an extensive series of tests of various electronic systems, including the NASA provided data and initiate systems, and some experiment systems. Overall, these were found to have performed remarkably well, even though most were designed and tested under limited budgets and used at least some nonspace qualified components. However, several anomalies were observed, including a few which resulted in some loss of data. The postflight test program objectives, observations, and lessons learned from these examinations are discussed. All analyses are not yet complete, but observations to date will be summarized, including the Boeing experiment component studies and failure analysis results related to the Interstellar Gas Experiment. Based upon these observations, suggestions for avoiding similar problems on future programs are presented.

Miller, Emmett↗

Lessons learned and their application to program development and cultural issues

The knowledge used today is contained in an untold number of technical and managerial handbooks. This knowledge is derived from the known strengths and weaknesses experienced during the execution of programs and projects that are being used today. The purpose is to stir up thought, not on specific experiences, but on implementation of lessons learned from these experiences.

Roth, Gilbert L.↗

Unstructured-grid methods development: Lessons le arned

The development is summarized of unstructured grid methods for the solution of the equations of fluid flow and some of the lessons learned are shared. The 3-D Euler equations are solved, including spatial discretizations, temporal discretizations, and boundary conditions. An example calculation with an upwind implicit method using a CFL (Courant Friedricks Lewy) number of infinity is presented for the Boeing 747 aircraft. The results obtained in less than one hour of CPU time on a Cray-2 computer, thus demonstrating the speed and robustness of the present capability.

Batina, John T.↗

Lessons learned from the Hubble Space Telescope planning and scheduling system implementation and operation

The major challenge of the NASA Hubble Space Telescope (HST) Ground System has been the implementation of the planning and scheduling system. This paper describes the operational flow of HST from science proposals to the actual execution of science observations on board the HST. The paper provides a collection of lessons learned over the 10 years that have covered the definition, development, test, and initial operation of HST's planning and scheduling system.

Ruitberg, Edward O.↗

Sounding rocket lessons learned

Programmatic, applicatory, developmental, and operational aspects of sounding rocket utilization for materials processing studies are discussed. Lessons learned through the experience of 10 sounding rocket missions are described. Particular attention is given to missions from the SPAR, Consort, and Joust programs. Successful experiments on Consort include the study of polymer membranes and resins, biological processes, demixing of immiscible liquids, and electrodeposition.

Wessling, Francis C.↗