Search NASA⌕ Search

SEARCH · Search NASA

Results for “Program”

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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS1984

A new implementation of the programming system for structural synthesis (PROSSS-2)

This new implementation of the PROgramming System for Structural Synthesis (PROSSS-2) combines a general-purpose finite element computer program for structural analysis, a state-of-the-art optimization program, and several user-supplied, problem-dependent computer programs. The results are flexibility of the optimization procedure, organization, and versatility of the formulation of constraints and design variables. The analysis-optimization process results in a minimized objective function, typically the mass. The analysis and optimization programs are executed repeatedly by looping through the system until the process is stopped by a user-defined termination criterion. However, some of the analysis, such as model definition, need only be one time and the results are saved for future use. The user must write some small, simple FORTRAN programs to interface between the analysis and optimization programs. One of these programs, the front processor, converts the design variables output from the optimizer into the suitable format for input into the analyzer. Another, the end processor, retrieves the behavior variables and, optionally, their gradients from the analysis program and evaluates the objective function and constraints and optionally their gradients. These quantities are output in a format suitable for input into the optimizer. These user-supplied programs are problem-dependent because they depend primarily upon which finite elements are being used in the model. PROSSS-2 differs from the original PROSSS in that the optimizer and front and end processors have been integrated into the finite element computer program. This was done to reduce the complexity and increase portability of the system, and to take advantage of the data handling features found in the finite element program.

Rogers, James L., Jr.↗
NASA NTRS1988

Automatic programming for critical applications

The important phases of a software life cycle include verification and maintenance. Usually, the execution performance is an expected requirement in a software development process. Unfortunately, the verification and the maintenance of programs are the time consuming and the frustrating aspects of software engineering. The verification cannot be waived for the programs used for critical applications such as, military, space, and nuclear plants. As a consequence, synthesis of programs from specifications, an alternative way of developing correct programs, is becoming popular. The definition, or what is understood by automatic programming, has been changed with our expectations. At present, the goal of automatic programming is the automation of programming process. Specifically, it means the application of artificial intelligence to software engineering in order to define techniques and create environments that help in the creation of high level programs. The automatic programming process may be divided into two phases: the problem acquisition phase and the program synthesis phase. In the problem acquisition phase, an informal specification of the problem is transformed into an unambiguous specification while in the program synthesis phase such a specification is further transformed into a concrete, executable program.

Loganantharaj, Raj L.↗
NASA NTRS1993

Minimum Hamiltonian Ascent Trajectory Evaluation (MASTRE) program (update to automatic flight trajectory design, performance prediction, and vehicle sizing for support of Shuttle and Shuttle derived vehicles) engineering manual

The Minimum Hamiltonian Ascent Trajectory Evaluation (MASTRE) program and its predecessors, the ROBOT and the RAGMOP programs, have had a long history of supporting MSFC in the simulation of space boosters for the purpose of performance evaluation. The ROBOT program was used in the simulation of the Saturn 1B and Saturn 5 vehicles in the 1960's and provided the first utilization of the minimum Hamiltonian (or min-H) methodology and the steepest ascent technique to solve the optimum trajectory problem. The advent of the Space Shuttle in the 1970's and its complex airplane design required a redesign of the trajectory simulation code since aerodynamic flight and controllability were required for proper simulation. The RAGMOP program was the first attempt to incorporate the complex equations of the Space Shuttle into an optimization tool by using an optimization method based on steepest ascent techniques (but without the min-H methodology). Development of the complex partial derivatives associated with the Space Shuttle configuration and using techniques from the RAGMOP program, the ROBOT program was redesigned to incorporate these additional complexities. This redesign created the MASTRE program, which was referred to as the Minimum Hamiltonian Ascent Shuttle TRajectory Evaluation program at that time. Unique to this program were first-stage (or booster) nonlinear aerodynamics, upper-stage linear aerodynamics, engine control via moment balance, liquid and solid thrust forces, variable liquid throttling to maintain constant acceleration limits, and a total upgrade of the equations used in the forward and backward integration segments of the program. This modification of the MASTRE code has been used to simulate the new space vehicles associated with the National Launch Systems (NLS). Although not as complicated as the Space Shuttle, the simulation and analysis of the NLS vehicles required additional modifications to the MASTRE program in the areas of providing additional flexibility in the use of the program, allowing additional optimization options, and providing special options for the NLS configuration.

Lyons, J. T.↗
NASA NTRS1998

NASA Ambassadors: A Speaker Outreach Program

The work done on this project this summer has been geared toward setting up the necessary infrastructure and planning to support the operation of an effective speaker outreach program. The program has been given the name, NASA AMBASSADORS. Also, individuals who become participants in the program will be known as "NASA AMBASSADORS". This summer project has been conducted by the joint efforts of this author and those of Professor George Lebo who will be issuing a separate report. The description in this report will indicate that the NASA AMBASSADOR program operates largely on the contributions of volunteers, with the assistance of persons at the Marshall Space Flight Center (MSFC). The volunteers include participants in the various summer programs hosted by MSFC as well as members of the NASA Alumni League. The MSFC summer participation programs include: the Summer Faculty Fellowship Program for college and university professors, the Science Teacher Enrichment Program for middle- and high-school teachers, and the NASA ACADEMY program for college and university students. The NASA Alumni League members are retired NASA employees, scientists, and engineers. The MSFC offices which will have roles in the operation of the NASA AMBASSADORS include the Educational Programs Office and the Public Affairs Office. It is possible that still other MSFC offices may become integrated into the operation of the program. The remainder of this report will establish the operational procedures which will be necessary to sustain the NASA AMBASSADOR speaker outreach program.

McDonald, Malcolm W.↗
NASA NTRS2002

Processes and Procedures of the Higher Education Programs at Marshall Space Flight Center

The purpose of my research was to investigate the policies, processes, procedures and timelines for the higher education programs at Marshall Space Flight Center. The three higher education programs that comprised this research included: the Graduate Student Researchers Program (GSRP), the National Research Council/Resident Research Associateships Program (NRC/RRA) and the Summer Faculty Fellowship Program (SFFP). The GSRP award fellowships each year to promising U.S. graduate students whose research interest coincides with NASA's mission. Fellowships are awarded for one year and are renewable for up to three years to competitively selected students. Each year, the award provides students the opportunity to spend a period in residence at a NASA center using that installation's unique facilities. This program is renewable for three years, students must reapply. The National Research Council conducts the Resident Research Associateships Program (NRC/RRA), a national competition to identify outstanding recent postdoctoral scientists and engineers and experience senior scientists and engineers, for tenure as guest researchers at NASA centers. The Resident Research Associateship Program provides an opportunity for recipients of doctoral degrees to concentrate their research in association with NASA personnel, often as a culmination to formal career preparation. The program also affords established scientists and engineers an opportunity for research without any interruptions and distracting assignments generated from permanent career positions. All opportunities for research at NASA Centers are open to citizens of the U.S. and to legal permanent residents. The Summer Faculty Fellowship Program (SFFP) is conducted each summer. NASA awards research fellowships to university faculty through the NASA/American Society for Engineering Education. The program is designed to promote an exchange of ideas between university faculties, NASA scientists and engineers. Selected participants in fields of science, engineering, math, and other disciplines spend approximately 10 weeks working with their professional peers on research projects at NASA facilities. Workshops and seminars further enrich the experience. This program is only for U.S. citizens.

Pamala D. Heard↗
NASA NTRS2002

Program Instrumentation and Trace Analysis

Several attempts have been made recently to apply techniques such as model checking and theorem proving to the analysis of programs. This shall be seen as a current trend to analyze real software systems instead of just their designs. This includes our own effort to develop a model checker for Java, the Java PathFinder 1, one of the very first of its kind in 1998. However, model checking cannot handle very large programs without some kind of abstraction of the program. This paper describes a complementary scalable technique to handle such large programs. Our interest is turned on the observation part of the equation: How much information can be extracted about a program from observing a single execution trace? It is our intention to develop a technology that can be applied automatically and to large full-size applications, with minimal modification to the code. We present a tool, Java PathExplorer (JPaX), for exploring execution traces of Java programs. The tool prioritizes scalability for completeness, and is directed towards detecting errors in programs, not to prove correctness. One core element in JPaX is an instrumentation package that allows to instrument Java byte code files to log various events when executed. The instrumentation is driven by a user provided script that specifies what information to log. Examples of instructions that such a script can contain are: 'report name and arguments of all called methods defined in class C, together with a timestamp'; 'report all updates to all variables'; and 'report all acquisitions and releases of locks'. In more complex instructions one can specify that certain expressions should be evaluated and even that certain code should be executed under various conditions. The instrumentation package can hence be seen as implementing Aspect Oriented Programming for Java in the sense that one can add functionality to a Java program without explicitly changing the code of the original program, but one rather writes an aspect and compiles it into the original program using the instrumentation. Another core element of JPaX is an observation package that supports the analysis of the generated event stream. Two kinds of analysis are currently supported. In temporal analysis the execution trace is evaluated against formulae written in temporal logic. We have implemented a temporal logic evaluator on finite traces using the Maude rewriting system from SRI International, USA. Temporal logic is defined in Maude by giving its syntax as a signature and its semantics as rewrite equations. The resulting semantics is extremely efficient and can handle event streams of hundreds of millions events in few minutes. Furthermore, the implementation is very succinct. The second form of even stream analysis supported is error pattern analysis where an execution trace is analyzed using various error detection algorithms that can identify error-prone programming practices that may potentially lead to errors in some different executions. Two such algorithms focusing on concurrency errors have been implemented in JPaX, one for deadlocks and the other for data races. It is important to note, that a deadlock or data race potential does not need to occur in order for its potential to be detected with these algorithms. This is what makes them very scalable in practice. The data race algorithm implemented is the Eraser algorithm from Compaq, however adopted to Java. The tool is currently being applied to a code base for controlling a spacecraft by the developers of that software in order to evaluate its applicability.

Havelund, Klaus↗
NASA NTRS2003

Accomplishments of the Abrupt Wing Stall (AWS) Program and Future Research Requirements

The Abrupt Wing Stall (AWS) Program has addressed the problem of uncommanded lateral motions, such as wing drop and wing rock, at transonic speeds. The genesis of this Program was the experience of the F/A-18E/F Program in the late 199O's, when wing drop was discovered in the heart of the maneuver envelope for the pre-production aircraft. While the F/A-18E/F problem was subsequently corrected by a leading-edge flap scheduling change and the addition of a porous door to the wing fold fairing, the AWS Program was initiated as a national response to the lack of technology readiness available at the time of the F/A-18E/F Development Program. The AWS Program objectives were to define causal factors for the F/A-18E/F experience, to gain insights into the flow physics associated with wing drop, and to develop methods and analytical tools so that future programs could identify this type of problem before going to flight test. The paper reviews, for the major goals of the AWS Program, the status of the technology before the program began, the program objectives, accomplishments, and impacts. Lessons learned are presented for the benefit of future programs that must assess whether a vehicle will have uncommanded lateral motions before going to flight test. Finally, recommended future research needs are presented in light of the AWS Program experience.

Hall, Robert M.↗
NASA NTRS2004

College Bound with the Office of Educational Programs

The Educational Programs Office at NASA Glenn Research Center hosts a variety of programs that takes on the hard task of getting students of all ages interested in pursuing careers in science, mathematics, and engineering. To help assist students along the way there are many programs to participate in such as: the explorers, shadowing opportunities, and paid internships. The Educational Programs Office not only creates learning opportunities for students, they also host workshops to help educators enhance their knowledge these fields. This summer I assisted Marie Borowski in the Educational Programs Office with the Tennessee State University College Bound Program. The Tennessee state University College Bound Program is an intensive two-week summer academic workshop designed to introduce minority students to the profession of engineering. NASA Glenn Research Center sent forty dedicated students on a bus to Nashville, Tennessee to experience college life as a whole. At the college the students day consisted of a math class, aeronautics, ACT/SAT preparation, writing and research, African American Culture, computer science, and study sessions. The students also went on educational field trips to the Fisk Museum, the Space and Rocket Center, and the Parthenon Museum. On the last day of the program the students competed in an oratorical contest where the students made a Powerpoint presentation on the class that they enjoyed the most. There were many processes that had to be put into action for the college bound program to run smoothly. The process started in early January with the preparation of applications. Once prepared, the applications were then sent to schools and past participants in hopes of receiving a well-qualified pool of applicants. Once the applications were received, a prescreening is done which ensures all of the information is complete. Then, they are reviewed by a panel, using a rubric to evaluate them, and the semifinalists are then selected. Interviews are held with the students and their parents had to be interviewed by a panel of judges and graded on a rubric. The scores were added up and the forty students were selected. My job this summer was getting the students ready to leave for Tennessee. My job consisted of working very closely with my mentor, Marie Borowski, compile the student data to provide it to the chaperones, TSU records, and NASA records. I learned about the vital communication between the NASA and the TSU program managers. After all the planning was done and the program had begun I had a chance to fly to Tennessee for six days to observe the students daily activities. The students had adjusted very well to the intense schedule, and seemed very enthusiastic about the activities to follow. The whole group was very attentive and enthusiastic program be longer. My goals for the summer were all met. I wanted to learn and retain all the information I possibly could on the job I was given. I was very happy with the end result.

Neal, Brittany D.↗
NASA NTRS2008

NASA's In Space Propulsion Technology Program Accomplishments and Lessons Learned

NASA's In-Space Propulsion Technology (ISPT) Program was managed for 5 years at the NASA MSFC and significant strides were made in the advancement of key transportation technologies that will enable or enhance future robotic science and deep space exploration missions. At the program's inception, a set of technology investment priorities were established using an NASA-wide, mission-driven prioritization process and, for the most part, these priorities changed little - thus allowing a consistent framework in which to fund and manage technology development. Technologies in the portfolio included aerocapture, advanced chemical propulsion, solar electric propulsion, solar sail propulsion, electrodynamic and momentum transfer tethers, and various very advanced propulsion technologies with significantly lower technology readiness. The program invested in technologies that have the potential to revolutionize the robotic exploration of deep space. For robotic exploration and science missions, increased efficiencies of future propulsion systems are critical to reduce overall life-cycle costs and, in some cases, enable missions previously considered impossible. Continued reliance on conventional chemical propulsion alone will not enable the robust exploration of deep space - the maximum theoretical efficiencies have almost been reached and they are insufficient to meet needs for many ambitious science missions currently being considered. By developing the capability to support mid-term robotic mission needs, the program was to lay the technological foundation for travel to nearby interstellar space. The ambitious goals of the program at its inception included supporting the development of technologies that could support all of NASA's missions, both human and robotic. As time went on and budgets were never as high as planned, the scope of the program was reduced almost every year, forcing the elimination of not only the broader goals of the initial program, but also of funding for over half of the technologies in the original portfolio. In addition, the frequency at which the application requirements for the program changed exceeded the development time required to mature technologies: forcing sometimes radical rescoping of research efforts already halfway (or more) to completion. At the end of its fifth year, both the scope and funding of the program were at a minimum despite the program successfully meeting all of it's initial high priority objectives. This paper will describe the program, its requirements, technology portfolio, and technology maturation processes. Also discussed will be the major technology milestones achieved and the lessons learned from managing a $100M+ technology program.

Johnson, Les C.↗
NASA NTRS2007

Application-Program-Installer Builder

A computer program builds application programming interfaces (APIs) and related software components for installing and uninstalling application programs in any of a variety of computers and operating systems that support the Java programming language in its binary form. This program is partly similar in function to commercial (e.g., Install-Shield) software. This program is intended to enable satisfaction of a quasi-industry-standard set of requirements for a set of APIs that would enable such installation and uninstallation and that would avoid the pitfalls that are commonly encountered during installation of software. The requirements include the following: 1) Properly detecting prerequisites to an application program before performing the installation; 2) Properly registering component requirements; 3) Correctly measuring the required hard-disk space, including accounting for prerequisite components that have already been installed; and 4) Correctly uninstalling an application program. Correct uninstallation includes (1) detecting whether any component of the program to be removed is required by another program, (2) not removing that component, and (3) deleting references to requirements of the to-be-removed program for components of other programs so that those components can be properly removed at a later time.

Wolgast, Paul↗
NASA NTRS1991

ALPS: A Linear Program Solver

ALPS is a computer program which can be used to solve general linear program (optimization) problems. ALPS was designed for those who have minimal linear programming (LP) knowledge and features a menu-driven scheme to guide the user through the process of creating and solving LP formulations. Once created, the problems can be edited and stored in standard DOS ASCII files to provide portability to various word processors or even other linear programming packages. Unlike many math-oriented LP solvers, ALPS contains an LP parser that reads through the LP formulation and reports several types of errors to the user. ALPS provides a large amount of solution data which is often useful in problem solving. In addition to pure linear programs, ALPS can solve for integer, mixed integer, and binary type problems. Pure linear programs are solved with the revised simplex method. Integer or mixed integer programs are solved initially with the revised simplex, and the completed using the branch-and-bound technique. Binary programs are solved with the method of implicit enumeration. This manual describes how to use ALPS to create, edit, and solve linear programming problems. Instructions for installing ALPS on a PC compatible computer are included in the appendices along with a general introduction to linear programming. A programmers guide is also included for assistance in modifying and maintaining the program.

Ferencz, Donald C.↗
NASA NTRS1997

Summer High School Apprenticeship Research Program (SHARP)

The summer of 1997 will not only be noted by NASA for the mission to Mars by the Pathfinder but also for the 179 brilliant apprentices that participated in the SHARP Program. Apprentice participation increased 17% over last year's total of 153 participants. As indicated by the End-of-the-Program Evaluations, 96% of the programs' participants rated the summer experience from very good to excellent. The SHARP Management Team began the year by meeting in Cocoa Beach, Florida for the annual SHARP Planning Conference. Participants strengthened their Education Division Computer Aided Tracking System (EDCATS) skills, toured the world-renowned Kennedy Space Center, and took a journey into space during the Alien Encounter Exercise. The participants returned to their Centers with the same goals and objectives in mind. The 1997 SHARP Program goals were: (1) Utilize NASA's mission, unique facilities and specialized workforce to provide exposure, education, and enrichment experiences to expand participants' career horizons and inspire excellence in formal education and lifelong learning. (2) Develop and implement innovative education reform initiatives which support NASA's Education Strategic Plan and national education goals. (3) Utilize established statistical indicators to measure the effectiveness of SHARP's program goals. (4) Explore new recruiting methods which target the student population for which SHARP was specifically designed. (5) Increase the number of participants in the program. All of the SHARP Coordinators reported that the goals and objectives for the overall program as well as their individual program goals were achieved. Some of the goals and objectives for the Centers were: (1) To increase the students' awareness of science, mathematics, engineering, and computer technology; (2) To provide students with the opportunity to broaden their career objectives; and (3) To expose students to a variety of enrichment activities. Most of the Center goals and objectives were consistent with the overall program goals. Modem Technology Systems, Inc., was able to meet the SHARP Apprentices, Coordinators and Mentors during their site visits to Stennis Space Center, Ames Research Center and Dryden Flight Research Center. All three Centers had very efficient programs and adhered to SHARP's general guidelines and procedures. MTSI was able to meet the apprentices from the other Centers via satellite in July during the SHARP Video-Teleconference(ViTS). The ViTS offered the apprentices and the NASA and SHARP Coordinators the opportunity to introduce themselves. The apprentices from each Center presented topical "Cutting Edge Projects". Some of the accomplishments for the 1997 SHARP Program year included: MTSI hiring apprentices from four of the nine NASA Centers, the full utilization of the EDCATS by apprentices and NASA/SHARP Coordinators, the distribution of the SHARP Apprentice College and Scholarship Directory, a reunion with former apprentices from Langley Research Center and the development of a SHARP Recruitment Poster. MTSI developed another exciting newsletter containing graphics and articles submitted by the apprentices and the SHARP Management Team.

Source record↗
NASA NTRS2002

Evaluating the Effectiveness of NASA's Destination Tomorrow(Trademark) 2000-2001 Program

NASA's Destination Tomorrow(trademark) series consists of 30-minute educational television programs that focus on NASA research, past, present, and future and are designed for educators, parents, and adult (lifelong) learners. Programs in this award-winning series follow a magazine style format with segments ranging from 3-5 minutes to 6-8 minutes. An associated web site provides summaries of stories and links to related program material. The development of the programs is based on educational theory, principles, and research as they pertain to how adults learn and apply knowledge. The five programs in the 2000-2001 season were produced in English and dubbed in Spanish. Telephone interviews with managers of cable access television stations were conducted in January 2002. NASA's Destination Tomorrow(trademark) interviewees reported that (1) from a programming standpoint, the most appealing aspects of the series are its production quality and educational value, (2) programs in the series are 'better than average' when compared to other education programming, (3) the programs are very credible, (4) the programs are successful in educating people about what NASA does, and (5) the programs have been 'very well received' by their audiences.

Pinelli, Thomas E.↗
NASA NTRS2004

Lapin Data Interchange Among Database, Analysis and Display Programs Using XML-Based Text Files

The purpose was to investigate and evaluate the interchange of application- specific data among multiple programs each carrying out part of the analysis and design task. This has been carried out previously by creating a custom program to read data produced by one application and then write that data to a file whose format is specific to the second application that needs all or part of that data. In this investigation, data of interest is described using the XML markup language that allows the data to be stored in a text-string. Software to transform output data of a task into an XML-string and software to read an XML string and extract all or a portion of the data needed for another application is used to link two independent applications together as part of an overall design effort. This approach was initially used with a standard analysis program, Lapin, along with standard applications a standard spreadsheet program, a relational database program, and a conventional dialog and display program to demonstrate the successful sharing of data among independent programs. See Engineering Analysis Using a Web-Based Protocol by J.D. Schoeffler and R.W. Claus, NASA TM-2002-211981, October 2002. Most of the effort beyond that demonstration has been concentrated on the inclusion of more complex display programs. Specifically, a custom-written windowing program organized around dialogs to control the interactions have been combined with an independent CAD program (Open Cascade) that supports sophisticated display of CAD elements such as lines, spline curves, and surfaces and turbine-blade data produced by an independent blade design program (UD0300).

Source record↗
NASA NTRS2005

Lapin Data Interchange Among Database, Analysis and Display Programs Using XML-Based Text Files

The purpose of grant NCC3-966 was to investigate and evaluate the interchange of application-specific data among multiple programs each carrying out part of the analysis and design task. This has been carried out previously by creating a custom program to read data produced by one application and then write that data to a file whose format is specific to the second application that needs all or part of that data. In this investigation, data of interest is described using the XML markup language that allows the data to be stored in a text-string. Software to transform output data of a task into an XML-string and software to read an XML string and extract all or a portion of the data needed for another application is used to link two independent applications together as part of an overall design effort. This approach was initially used with a standard analysis program, Lapin, along with standard applications a standard spreadsheet program, a relational database program, and a conventional dialog and display program to demonstrate the successful sharing of data among independent programs. Most of the effort beyond that demonstration has been concentrated on the inclusion of more complex display programs. Specifically, a custom-written windowing program organized around dialogs to control the interactions have been combined with an independent CAD program (Open Cascade) that supports sophisticated display of CAD elements such as lines, spline curves, and surfaces and turbine-blade data produced by an independent blade design program (UD0300).

Source record↗
NASA NTRS2004

Collaborative Aerospace Research and Fellowship Program at NASA Glenn Research Center

During the summer of 2004, a 10-week activity for university faculty entitled the NASA-OAI Collaborative Aerospace Research and Fellowship Program (CFP) was conducted at the NASA Glenn Research Center in collaboration with the Ohio Aerospace Institute (OAI). This is a companion program to the highly successful NASA Faculty Fellowship Program and its predecessor, the NASA-ASEE Summer Faculty Fellowship Program that operated for 38 years at Glenn. The objectives of CFP parallel those of its companion, viz., (1) to further the professional knowledge of qualified engineering and science faculty,(2) to stimulate an exchange of ideas between teaching participants and employees of NASA, (3) to enrich and refresh the research and teaching activities of participants institutions, and (4) to contribute to the research objectives of Glenn. However, CFP, unlike the NASA program, permits faculty to be in residence for more than two summers and does not limit participation to United States citizens. Selected fellows spend 10 weeks at Glenn working on research problems in collaboration with NASA colleagues and participating in related activities of the NASA-ASEE program. This year's program began officially on June 1, 2004 and continued through August 7, 2004. Several fellows had program dates that differed from the official dates because university schedules vary and because some of the summer research projects warranted a time extension beyond the 10 weeks for satisfactory completion of the work. The stipend paid to the fellows was $1200 per week and a relocation allowance of $1000 was paid to those living outside a 50-mile radius of the Center. In post-program surveys from this and previous years, the faculty cited numerous instances where participation in the program has led to new courses, new research projects, new laboratory experiments, and grants from NASA to continue the work initiated during the summer. Many of the fellows mentioned amplifying material, both in undergraduate and graduate courses, on the basis of the summer s experience at Glenn. A number of 2004 fellows indicated that proposals to NASA will grow out of their summer research projects. In addition, some journal articles and NASA publications will result from this past summer s activities. Fellows from past summers continue to send reprints of articles that resulted from work initiated at Glenn. This report is intended primarily to summarize the research activities comprising the 2004 CFP Program at Glenn. Particular research studies include: 1) Development of an Imaging-Based, Computational Fluid Dynamics Tool to Assess Fluid Mechanics in Experimental Models that Simulate Blood Vessels; 2) Analysis of Nanomaterials Produced from Precursors; and 3) LEO Propagation Analysis Tool.

Heyward, Ann O.↗
NASA NTRS2008

Seven Key Principles of Program and Project Success: A Best Practices Survey

The National Aeronautics and Space Administration (NASA) Organization Design Team (ODT), consisting of 20 seasoned program and project managers and systems engineers from a broad spectrum of the aerospace industry, academia, and government, was formed to support the Next Generation Launch Technology (NGLT) Program and the Constellation Systems Program. The purpose of the ODT was to investigate organizational factors that can lead to success or failure of complex government programs, and to identify tools and methods for the design, modeling, and analysis of new and more-efficient program and project organizations. The ODT conducted a series of workshops featuring invited lectures from seasoned program and project managers representing 25 significant technical programs spanning 50 years of experience. The result was the identification of seven key principles of program success that can be used to help design and operate future program organizations. This paper presents the success principles and examples of best practices that can significantly improve the design of program, project, and performing technical line organizations, the assessment of workforce needs and organization performance, and the execution of programs and projects.

Bilardo, Vincent J.↗
NASA NTRS2006

A Silent Safety Program

NASA's Columbia Accident Investigation Board (CAIB) referred 8 times to the NASA "Silent Safety Program." This term, "Silent Safety Program" was not an original observation but first appeared in the Rogers Commission's Investigation of the Challenger Mishap. The CAIB on page 183 of its report in the paragraph titled 'Encouraging Minority Opinion,' stated "The Naval Reactor Program encourages minority opinions and "bad news." Leaders continually emphasize that when no minority opinions are present, the responsibility for a thorough and critical examination falls to management. . . Board interviews revealed that it is difficult for minority and dissenting opinions to percolate up through the agency's hierarchy. . ." The first question and perhaps the only question is - what is a silent safety program? Well, a silent safety program may be the same as the dog that didn't bark in Sherlock Holmes' "Adventure of the Silver Blaze" because system safety should behave as a devil's advocate for the program barking on every occasion to insure a critical review inclusion. This paper evaluates the NASA safety program and provides suggestions to prevent the recurrence of the silent safety program alluded to in the Challenger Mishap Investigation. Specifically targeted in the CAM report, "The checks and balances the safety system was meant to provide were not working." A silent system safety program is not unique to NASA but could emerge in any and every organization. Principles developed by Irving Janis in his book, Groupthink, listed criteria used to evaluate an organization's cultural attributes that allows a silent safety program to evolve. If evidence validates Jams's criteria, then Jams's recommendations for preventing groupthink can also be used to improve a critical evaluation and thus prevent the development of a silent safety program.

Goodin, James Ronald↗