Search NASA⌕ Search

SEARCH · Search NASA

Results for “legacy documents”

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 19 records

Software Safety Risk in Legacy Safety-Critical Computer Systems

Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.

Hill, Janice↗

Analysis of Space Shuttle Ground Support System Fault Detection, Isolation, and Recovery Processes and Resources

As part of the FDIR (Fault Detection, Isolation, and Recovery) Project for the Constellation Program, a task was designed within the context of the Constellation Program FDIR project called the Legacy Benchmarking Task to document as accurately as possible the FDIR processes and resources that were used by the Space Shuttle ground support equipment (GSE) during the Shuttle flight program. These results served as a comparison with results obtained from the new FDIR capability. The task team assessed Shuttle and EELV (Evolved Expendable Launch Vehicle) historical data for GSE-related launch delays to identify expected benefits and impact. This analysis included a study of complex fault isolation situations that required a lengthy troubleshooting process. Specifically, four elements of that system were considered: LH2 (liquid hydrogen), LO2 (liquid oxygen), hydraulic test, and ground special power.

Gross, Anthony R.↗

Constellation Program Lessons Learned: Detailed Lessons Learned - Volume 2

These lessons learned are part of a suite of hardware, software, test results, designs, knowledge base, and documentation that comprises the legacy of the Constellation Program. The context, summary information, and lessons learned are presented in a factual format, as known and described at the time. While our opinions might be discernable in the context, we have avoided all but factually sustainable statements. Statements should not be viewed as being either positive or negative; their value lies in what we did and what we learned that is worthy of passing on. The lessons include both "dos" and "don ts." In many cases, one person s "do" can be viewed as another person s "don t"; therefore, we have attempted to capture both perspectives when applicable and useful. While Volume I summarizes the views of those who managed the program, this Volume II encompasses the views at the working level, describing how the program challenges manifested in day-to-day activities. Here we see themes that were perhaps hinted at, but not completely addressed, in Volume I: unintended consequences of policies that worked well at higher levels but lacked proper implementation at the working level; long-term effects of the "generation gap" in human space flight development, the need to demonstrate early successes at the expense of thorough planning, and the consequences of problems and challenges not yet addressed because other problems and challenges were more immediate or manifest. Not all lessons learned have the benefit of being operationally vetted, since the program was cancelled shortly after Preliminary Design Review. We avoid making statements about operational consequences (with the exception of testing and test flights that did occur), but we do attempt to provide insight into how operational thinking influenced design and testing. The lessons have been formatted with a description, along with supporting information, a succinct statement of the lesson learned, and recommendations for future programs and projects that may be placed in similar circumstances.

Jennifer Rhatigan↗

CANDELS: The Cosmic Assembly Near-Infrared Deep Extragalactic Legacy Survey

The Cosmic Assembly Near-IR Deep Extragalactic Legacy Survey (CANDELS) is designed to document the first third of galactic evolution, from z approx. 8 - 1.5. It will image > 250,000 distant galaxies using three separate cameras on the Hubble Space Tele8cope, from the mid-UV to near-IR, and will find and measure Type Ia supernovae beyond z > 1.5 to test their accuracy as standard candles for cosmology. Five premier multi-wavelength sky regions are selected, each with extensive ancillary data. The use of five widely separated fields mitigates cosmic variance and yields statistically robust and complete samples of galaxies down to a stellar mass of 10(exp 9) solar mass to z approx. 2, reaching the knee of the UV luminosity function of galaxies to z approx. 8. The survey covers approximately 800 square arc minutes and is divided into two parts. The CANDELS/Deep survey (5(sigma) point-source limit H =27.7mag) covers approx. 125 square arcminutes within GOODS-N and GOODS-S. The CANDELS/Wide survey includes GOODS and three additional fields (EGS, COSMOS, and UDS) and covers the full area to a 50(sigma) point-source limit of H ? or approx. = 27.0 mag. Together with the Hubble Ultradeep Fields, the strategy creates a three-tiered "wedding cake" approach that has proven efficient for extragalactic surveys. Data from the survey are non-proprietary and are useful for a wide variety of science investigations. In this paper, we describe the basic motivations for the survey, the CANDELS team science goals and the resulting observational requirements, the field selection and geometry, and the observing design.

Grogin, Norman A.↗

Advances in Above- and In-Water Radiometry, Volume 1: Enhanced Legacy and State-of-the-Art Instrument Suites

This publication documents the scientific advances associated with new instrument systems and accessories built to improve above- and in-water observations of the apparent optical properties (AOPs) of aquatic ecosystems. The perspective is to obtain high quality data in offshore, nearshore, and inland waters with equal efficacy. The principal objective is to be prepared for the launch of the next-generation ocean color satellites with the most capable commercial off-the-shelf (COTS) instrumentation in the shortest time possible. The technologies described herein are designed to either improve legacy radiometric systems or to provide entirely new hybrid sampling capabilities, so as to satisfy the requirements established for diverse remote sensing requirements. Both above- and in-water instrument suites are documented with software options for autonomous control of data collection activities. The latter includes an airborne instrument system plus unmanned surface vessel (USV) and buoy concepts.

Hooker, Stanford B.↗

An Overview of Space Exploration Simulation (Basis of Confidence) Documentation

Models and simulations (M&S) are critical resources in the exploration of space. They support program management, systems engineering, integration, analysis, test, and operations by providing critical information that supports key analyses and decisions (technical, cost and schedule). Consequently, there is a clear need to establish a solid understanding of M&S strengths and weaknesses, and the bounds within which they can credibly support decision making. In this presentation we will describe how development of simulation capability documentation will be used to form a Basis of Confidence (Basis of Confidence) for National Aeronautics and Space Administration (NASA) M&S. The process by which BOC documentation is developed will be addressed, as well as the structure and critical concepts that are essential for establishing credibility of NASA's Exploration Systems Mission Directorate (ESMD) legacy M&S. We will illustrate the significance of BOC documentation in supporting decision makers and Accreditation Authorities in M&S risk management.

Bray, Alleen↗

Documenting the NASA Armstrong Flight Research Center Oblate Earth Simulation Equations of Motion and Integration Algorithm

A desire for more complete documentation of the National Aeronautics and Space Administration (NASA) Armstrong Flight Research Center (AFRC), Edwards, California legacy code used in the core simulation has led to this e ort to fully document the oblate Earth six-degree-of-freedom equations of motion and integration algorithm. The authors of this report have taken much of the earlier work of the simulation engineering group and used it as a jumping-o point for this report. The largest addition this report makes is that each element of the equations of motion is traced back to first principles and at no point is the reader forced to take an equation on faith alone. There are no discoveries of previously unknown principles contained in this report; this report is a collection and presentation of textbook principles. The value of this report is that those textbook principles are herein documented in standard nomenclature that matches the form of the computer code DERIVC. Previous handwritten notes are much of the backbone of this work, however, in almost every area, derivations are explicitly shown to assure the reader that the equations which make up the oblate Earth version of the computer routine, DERIVC, are correct.

integrators↗

Exploring Airfoil Table Generation using XFOIL and OVERFLOW

The rotorcraft design process is a continuously evolving field of research that incorporates a number of software programs. An accurate airfoil table is critical in the design and testing process for rotorcraft. With multiple flow solvers available and flow conditions of multirotor UAM vehicles potentially covering a wide range of Reynolds and Mach numbers, a documented approach for developing airfoil tables is needed. Using benchmark data from legacy airfoil tables and wind tunnel tests for comparison, simulations for a comprehensive test matrix could guide rotorcraft design engineers in generating their own airfoil tables using the XFOIL and OVERFLOW solvers. The motivation for this study is to investigate flow solver features to develop a best practices document for airfoil table generation. The study uses the OVERFLOW and XFOIL flow solvers, coupled with the airfoil table generator AFTGen, to analyze three airfoils for a specific Reynolds numbers flow regime and provide details on how well each flow solver performs within a specific angle of attack range, Mach number range, Reynolds number range, and in different flow conditions, such as turbulent and transitional flow. OVERFLOW analyses in AFTGen for fully turbulent and transition flow are compared with XFOIL results and experimental test data for the section lift, section drag, and pressure coefficients. XFOIL ultimately yields results that are accurate within the linear angle of attack range and below a Mach number of 0.4 but tends to overpredict lift and underpredict drag unless the flow is in the compressible regime. XFOIL cannot accurately model stall and post-stall conditions due to the nature of the solver. This is evident in nearly every case run with XFOIL, where the linear range is usually predicted acceptably and the lift coefficient is overpredicted as the stall angle of attack is approached (with the exception being the generally poor correlation with most of the SSC-A09 cases). OVERFLOW is limited at low Mach numbers, and appears to perform best at Mach numbers of 0.4 and above. The exploration of airfoil table generation using XFOIL and OVERFLOW yielded moderately successful results for the NACA 0012 airfoil, reasonably good results for the RC(4)-10 airfoil, and less accurate results for the SSC-A09 airfoil.

Airfoil Table Generation↗

Wilbur and Orville Wright: A Reissue of a Chronology Commemorating the Hundredth Anniversary of the Birth of Orville Wright, August 19, 1871

During the year 2003, hundreds of events will mark the one-hundredth anniversary of the Wright brothers historic first flights at Kitty Hawk, North Carolina. The centennial year will witness exhibitions, lectures, television documentaries, films, air shows, flight recreations of Wright aircraft, the issuing of postage stamps and medals, the publication of dozens of new books and articles, and numerous other commemorative activities. One of these events, although not likely to make the evening news, is among the most important of all in terms of a lasting contribution to the observance of this ultimate aviation milestone: the reprinting of Arthur G. Renstrom WIlbur & Orville Wrght: A Chronology Commemorating the Hundredth Anniversary of the Birth of Orville Wright, August 19, 1871. Since its appearance in 1975, Wilbur end Orville Wright: A Chronology has become indispensable to students and authors concerned with the life and work of the famous brothers. No doubt every book on the subject published in the last quarter century, including three of my own, was written with this treasure close at hand. This volume is far more than a simple compilation of dates and facts. Renstrom was a master reference librarian and bibliographer with a passion for aviation and the Wright brothers. He brought his considerable research skills to bear on the topic, and the result is a richly detailed, ever-informative, often entertaining walk through the lives and achievements of these two extraordinary individuals. Renstrom was not content to offer a date with a one-line tidbit. His entries are brimming with information. This is a highly readable reference work that, believe it or not, can be enjoyably read from cover to cover. The project was clearly a labor of love by a talented professional. During most of the last twenty years, I have been privileged to be the curator of the 1903 Wright Flyer at the Smithsonian Institution s National Air and Space Museum. The position brings a steady stream of inquiries about the Wright airplane and the endlessly fascinating brothers who created it. I do not know how I would have done this job without Renstrom s superb volume on my bookshelf. It is the first place I go to check anything on the Wright brothers, and I typically find what I am looking for in its pages. Arthur Renstrom also published two other classic reference works on the Wright brothers: Wilbur & Orville Wright: A Bibliography Commemorating the Hundredth Anniversary of the Birth of Wilbur Wright, April 16, 1867, in 1968 (an updated revision was published by the National Aeronautics and Space Administration in 2002) and Wilbur & Orville Wright, Pictorial Materials: A Documentary Guide in 1982, completing a series of research tools for which there are few peers on any subject. He was also part of the team that produced the landmark two-volume compilation of the Wrights letters, notebooks, and diaries in 1953, The Papers of Wilbur and Orville Wright, edited by Marvin W. McFarland. Renstrom s contribution to the documentation and preservation of the Wright story is a lasting legacy that will serve researchers, students, and general enthusiasts for generations to come. In this busy, high-profile anniversary year, the reprinting of a nearly thirty-year-old reference book may seem a mundane and quiet contribution to the celebration surrounding the Wright brothers world-changing achievement, but it is perhaps one of the most important. The U.S. Centennial of Flight Commission and NASA are to be commended for their foresight.

Renstrom, Arthur George↗

SQL-RAMS

SQL-RAMS (where "SQL" signifies Structured Query Language and "RAMS" signifies Rocketdyne Automated Management System) is a successor to the legacy version of RAMS -- a computer program used to manage all work, nonconformance, corrective action, and configuration management on rocket engines and ground support equipment at Stennis Space Center. The legacy version resided in the File-Maker Pro software system and was constructed in modules that could act as standalone programs. There was little or no integration among modules. Because of limitations on file-management capabilities in FileMaker Pro, and because of difficulty of integration of FileMaker Pro with other software systems for exchange of data using such industry standards as SQL, the legacy version of RAMS proved to be limited, and working to circumvent its limitations too time-consuming. In contrast, SQL-RAMS is an integrated SQL-server-based program that supports all data-exchange software industry standards. Whereas in the legacy version, it was necessary to access individual modules to gain insight into a particular workstatus document, SQL-RAMS provides access through a single-screen presentation of core modules. In addition, SQL-RAMS enables rapid and efficient filtering of displayed statuses by predefined categories and test numbers. SQL-RAMS is rich in functionality and encompasses significant improvements over the legacy system. It provides users the ability to perform many tasks, which in the past required administrator intervention. Additionally, many of the design limitations have been corrected, allowing for a robust application that is user centric.

Alfaro, Victor O.↗

Using Reliability to Meet Z540.3's 2 percent Rule

NASA's Kennedy Space Center (KSC) undertook implementation of ANSI/NCSL Z540.3-2006 in October 2008. Early in the implementation, KSC identified that the largest cost driver of Z540.3 implementation is measurement uncertainty analyses for legacy calibration processes. NASA, like other organizations, has a significant inventory of measuring and test equipment (MTE) that have documented calibration procedures without documented measurement uncertainties. This paper provides background information to support the rationale for using high in-tolerance reliability as evidence of compliance to the 2% probability of false acceptance (PFA) quality metric of ANSI/NCSL Z540.3-2006 allowing use of qualifying legacy processes. NASA is adopting this as policy and is recommending NCSL International consider this as a method of compliance to Z540.3. Topics covered include compliance issues, using end-of-period reliability (EOPR) to estimate test point uncertainty, reliability data influences within the PFA model, the validity of EOPR data, and an appendix covering "observed" versus "true" EOPR.

Mimbs, Scott M.↗

SQL-RAMS

SQL-RAMS (where "SQL" signifies Structured Query Language and "RAMS" signifies Rocketdyne Automated Management System) is a successor to the legacy version of RAMS a computer program used to manage all work, nonconformance, corrective action, and configuration management on rocket engines and ground support equipment at Stennis Space Center. The legacy version resided in the FileMaker Pro software system and was constructed in modules that could act as stand-alone programs. There was little or no integration among modules. Because of limitations on file-management capabilities in FileMaker Pro, and because of difficulty of integration of FileMaker Pro with other software systems for exchange of data using such industry standards as SQL, the legacy version of RAMS proved to be limited, and working to circumvent its limitations too time-consuming. In contrast, SQL-RAMS is an integrated SQL-server-based program that supports all data-exchange software industry standards. Whereas in the legacy version, it was necessary to access individual modules to gain insight to a particular work-status documents, SQL-RAMS provides access through a single-screen presentation of core modules. In addition, SQL-RAMS enable rapid and efficient filtering of displayed statuses by predefined categories and test numbers. SQL-RAMS is rich in functionality and encompasses significant improvements over the legacy system. It provides users the ability to perform many tasks which in the past required administrator intervention. Additionally many of the design limitations have been corrected allowing for a robust application that is user centric.

Alfaro, Victor O.↗

Interfacing with Legacy using Remote Method Invocation

The assignment described was enough to make a neophyte Java developer bolt for the door: provide a remote method for use by an applet which invokes a native method that wraps a function in an existing legacy library. The purpose of the remote method is to return an instance of a class object whose contents reflect the data structure returned by the legacy function. While embroiled in implementation, I would have spent the time wading through their JNI use group archive as well, but I couldn't seem to locate one. Subsequently, I made the decision to try to document my findings in order to assist others. Before we start on the class design, let's look at what the existing legacy code does. The C function to be called, Get-Legacy-Data, consists of two steps: an ASII file is read from the local disk and its contents are parsed into a Legacy_Type structure whose address is passed as an argument by the caller. The legacy code was compiled into a shared object library, legacy. so, using the IRIX 6.2 compiler and then loaded onto the Web server, a Silicon Graphics Indy station loaded with the IRIX 6.4 operating system. As far as the class design is concerned, the first thing required is a class to act as a template for the data structure returned by the legacy function. This class, JLegacy, declares a series of public instance variables which correspond to the members of Legacy_Type and provides a parameterless constructor. This constructor is never called, not even by the native method which allocates the object for return to the remote method. Next, the remote interface declaration for the remote object must be defined. In order for JLegacyRO to implement getJLegacy, JLegacyRO must interface with the existing legacy code through a native method, getn. getn is declared in the JLegacyRO class but implemented in C, just like the legacy code. getn returns a JLegacy instance and is declared static since its implementation is the same for all instances of the JLegacyRO class.

Howard, Scott M.↗

Airspace Technology Demonstration 3 (ATD-3): Dynamic Weather Routes (DWR) Technology Transfer Document Summary Version 2.0

This summary document and accompanying technology artifacts satisfy the first of three Research Transition Products (RTPs) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan. The original transfer, completed in September 2016, consisted of NASA's legacy Dynamic Weather Routes (DWR) work for efficient routing for en-route weather avoidance. This transfer updates the Concept of Operations document to a publicly-available NASA Technical Memorandum. Dynamic Weather Routes (DWR) is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to identify opportunities for simple corrections to flight plan routes that can save significant flying time, at least five minutes wind-corrected, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions.

DWR↗

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, in a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation; testing results, and other information. Where appropriate, actual performance history was used for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to verify compliance with requirements and to highlight design or performance shortcomings for further decision-making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability and maintainability analysis, and present findings and observation based on analysis leading to the Ground Systems Preliminary Design Review milestone.

Gernand, Jeffrey L.↗

U.S. Spacesuit Legacy: Maintaining it for the Future

The history of U.S. spacesuit development and its use are rich with information on lessons learned, and constitutes a valuable legacy to those designing spacesuits for the future, as well as to educators, students, and the general public. The genesis of lessons learned is best understood by studying the evolution of past spacesuit programs - how the challenges and pressures of the times influenced the direction of the various spacesuit programs. This paper shows how the legacy of various spacesuit-related programs evolved in response to these forces. Important aspects of how this U.S. spacesuit legacy is being preserved today is described, including the archiving of spacesuit hardware, important documents, videos, oral history, and the rapidly expanding U.S. Spacesuit Knowledge Capture program.

Chullen, Cinda↗

Web-Based Environment for Maintaining Legacy Software

Advanced Tool Integration Environment (ATIE) is the name of both a software system and a Web-based environment created by the system for maintaining an archive of legacy software and expertise involved in developing the legacy software. ATIE can also be used in modifying legacy software and developing new software. The information that can be encapsulated in ATIE includes experts documentation, input and output data of tests cases, source code, and compilation scripts. All of this information is available within a common environment and retained in a database for ease of access and recovery by use of powerful search engines. ATIE also accommodates the embedment of supporting software that users require for their work, and even enables access to supporting commercial-off-the-shelf (COTS) software within the flow of the experts work. The flow of work can be captured by saving the sequence of computer programs that the expert uses. A user gains access to ATIE via a Web browser. A modern Web-based graphical user interface promotes efficiency in the retrieval, execution, and modification of legacy code. Thus, ATIE saves time and money in the support of new and pre-existing programs.

Tigges, Michael↗

U.S. Spacesuit Legacy: Maintaining it for the Future

The history of US Spacesuit development and use is rich with information on lessons learned, and constitutes a valuable legacy to those designing spacesuits for the future, as well as educators, students and the general public. The genesis of lessons learned is best understood by studying the evolution of past spacesuit programs how the challenges and pressures of the times influenced the direction of the various spacesuit programs. This paper will show how the legacy of various programs evolved in response to these forces. Important aspects of how this rich U.S. spacesuit legacy is being preserved today will be described, including the archiving of spacesuit hardware, important documents, videos, oral history, and the rapidly expanding US Spacesuit Knowledge Capture program.

Chullen, Cinda↗