Search NASA⌕ Search

SEARCH · Search NASA

Results for “project documentation”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS1978

The Partnership: a History of the Apollo-Soyuz Test Project

Correspondance, interviews, official documents, and other published materials were used to trace the evolution of the Apollo Soyuz Test Project from the initial proposal for international cooperation in space use and exploration until the successful completion of the joint Soviet-American mission. Conceptual drawings of proposed docking modules and mechanisms are presented and dicussed. Black and white photographs taken during mission planning and in-flight activities are included with color photographs of the earth taken during the mission. Joint meetings are summarized and the scientific experiments and launch vehicles are discussed in the appendices.

Ezell, E. C.↗
NASA NTRS2024

Applying Generative-AI to NASA Documentation and Processes

This research and development project leverages generative-AI to assist in the generation of software process documentation based on NASA standards. By utilizing fine-tuned AI models, the proposed system will analyze NASA's software guidelines, helping to translate them into well-structured, compliant process documents. This assistance can reduce the manual effort required to produce such documentation, enhance consistency, and assure alignment with NASA's stringent software development and operational requirements. In addition to assisting in the generation of software process documentation, the project explores how generative-AI can help create audit checklists as well as assess the compliance of NASA provider documentation against applicable NASA standards. This approach would support the compliance auditing process, providing real-time insights and assessments. The intended result will be a streamlined process, potentially including a Python-based tool and database, that improves audit efficiency, reduces human error, lowers manpower costs and required manhours, and assures continuous compliance with NASA and industry evolving standards for safety-critical software development. Future task might be to investigate the software industry approach and standards for potential collaboration.

NASA Standards↗
NASA NTRS2010

Implementation and Qualifications Lessons Learned for Space Flight Photonic Components

This slide presentation reviews the process for implementation and qualification of space flight photonic components. It discusses the causes for most common anomalies for the space flight components, design compatibility, a specific failure analysis of optical fiber that occurred in a cable in 1999-2000, and another ExPCA connector anomaly involving pins that broke off. It reviews issues around material selection, quality processes and documentation, and current projects that the Photonics group is involved in. The importance of good documentation is stressed.

Ott, Melanie N.↗
NASA NTRS1993

Data management for support of the Oregon Transect Ecosystem Research (OTTER) project

Management of data collected during projects that involve large numbers of scientists is an often overlooked aspect of the experimental plan. Ecosystem science projects like the Oregon Transect Ecosystem Research (OTTER) Project that involve many investigators from many institutions and that run for multiple years, collect and archive large amounts of data. These data range in size from a few kilobytes of information for such measurements as canopy chemistry and meteorological variables, to hundreds of megabytes of information for such items as views from multi-band spectrometers flown on aircraft and scenes from imaging radiometers aboard satellites. Organizing and storing data from the OTTER Project, certifying those data, correcting errors in data sets, validating the data, and distributing those data to other OTTER investigators is a major undertaking. Using the National Aeronautics and Space Administration's (NASA) Pilot Land Data System (PLDS), a Support mechanism was established for the OTTER Project which accomplished all of the above. At the onset of the interaction between PLDS and OTTER, it was not certain that PLDS could accomplish these tasks in a manner that would aid researchers in the OTTER Project. This paper documents the data types that were collected under the auspices of the OTTER Project and the procedures implemented to store, catalog, validate, and certify those data. The issues of the compliance of investigators with data-management requirements, data use and certification, and the ease of retrieving data are discussed. We advance the hypothesis that formal data management is necessary in ecological investigations involving multiple investigators using many data gathering instruments and experimental procedures. The issues and experience gained in this exercise give an indication of the needs for data management systems that must be addressed in the coming decades when other large data-gathering endeavors are undertaken by the ecological science community.

Skiles, J. W.↗
NASA NTRS1977

Documentation requirements for Applications Systems Verification and Transfer projects (ASVTs)

NASA's Application Systems Verification and Transfer Projects (ASVTs) are deliberate efforts to facilitate the transfer of applications of NASA-developed space technology to users such as federal agencies, state and local governments, regional planning groups, public service institutions, and private industry. This study focused on the role of documentation in facilitating technology transfer both to primary users identified during project planning and to others with similar information needs. It was understood that documentation can be used effectively when it is combined with informal (primarily verbal) communication within each user community and with other formal techniques such as organized demonstrations and training programs. Documentation examples from eight ASVT projects and one potential project were examined to give scope to the investigation.

Suchy, J. T.↗
NASA NTRS1972

Automatic system for computer program documentation

Work done on a project to design an automatic system for computer program documentation aids was made to determine what existing programs could be used effectively to document computer programs. Results of the study are included in the form of an extensive bibliography and working papers on appropriate operating systems, text editors, program editors, data structures, standards, decision tables, flowchart systems, and proprietary documentation aids. The preliminary design for an automated documentation system is also included. An actual program has been documented in detail to demonstrate the types of output that can be produced by the proposed system.

Simmons, D. B.↗
NASA NTRS1972

The interplanetary pioneers. Volume 1: Summary

The Pioneer Space Probe Project is explained to document the events which occurred during the project. The subjects discussed are: (1) origin and history of interplanetary Pioneer program, (2) Pioneer system development and design, (3) Pioneer flight operations, and (4) Pioneer scientific results. Line drawings, circuit diagrams, illustrations, and photographs are included to augment the written material.

Corliss, W. R.↗
NASA NTRS1990

Information System Life-Cycle And Documentation Standards (SMAP DIDS)

Although not computer program, SMAP DIDS written to provide systematic, NASA-wide structure for documenting information system development projects. Each DID (data item description) outlines document required for top-quality software development. When combined with management, assurance, and life cycle standards, Standards protect all parties who participate in design and operation of new information system.

Source record↗
NASA NTRS1993

Software to model AXAF image quality

This draft final report describes the work performed under this delivery order from May 1992 through June 1993. The purpose of this contract was to enhance and develop an integrated optical performance modeling software for complex x-ray optical systems such as AXAF. The GRAZTRACE program developed by the MSFC Optical Systems Branch for modeling VETA-I was used as the starting baseline program. The original program was a large single file program and, therefore, could not be modified very efficiently. The original source code has been reorganized, and a 'Make Utility' has been written to update the original program. The new version of the source code consists of 36 small source files to make it easier for the code developer to manage and modify the program. A user library has also been built and a 'Makelib' utility has been furnished to update the library. With the user library, the users can easily access the GRAZTRACE source files and build a custom library. A user manual for the new version of GRAZTRACE has been compiled. The plotting capability for the 3-D point spread functions and contour plots has been provided in the GRAZTRACE using the graphics package DISPLAY. The Graphics emulator over the network has been set up for programming the graphics routine. The point spread function and the contour plot routines have also been modified to display the plot centroid, and to allow the user to specify the plot range, and the viewing angle options. A Command Mode version of GRAZTRACE has also been developed. More than 60 commands have been implemented in a Code-V like format. The functions covered in this version include data manipulation, performance evaluation, and inquiry and setting of internal parameters. The user manual for these commands has been formatted as in Code-V, showing the command syntax, synopsis, and options. An interactive on-line help system for the command mode has also been accomplished to allow the user to find valid commands, command syntax, and command function. A translation program has been written to convert FEA output from structural analysis to GRAZTRACE surface deformation file (.dfm file). The program can accept standard output files and list files from COSMOS/M and NASTRAN finite analysis programs. Some interactive options are also provided, such as Cartesian or cylindrical coordinate transformation, coordinate shift and scale, and axial length change. A computerized database for technical documents relating to the AXAF project has been established. Over 5000 technical documents have been entered into the master database. A user can now rapidly retrieve the desired documents relating to the AXAF project. The summary of the work performed under this contract is shown.

Ahmad, Anees↗
NASA NTRS2010

A Collaborative Web-Based Approach to Planning Research, Integration, and Testing Using a Wiki

The National Aeronautics and Space Administration Integrated Vehicle Health Management program touches on many different research areas while striving to enable the automated detection, diagnosis, prognosis, and mitigation of adverse events at the aircraft and system level. At the system level, the research focus is on the evaluation of multidisciplinary integrated methods, tools, and technologies for achieving the program goal. The participating program members form a diverse group of government, industry, and academic researchers. The program team developed the Research and Test Integration Plan in order to track significant test and evaluation activities, which are important for understanding, demonstrating, and communicating the overall project state and project direction. The Plan is a living document, which allows the project team the flexibility to construct conceptual test scenarios and to track project resources. The Plan also incorporates several desirable feature requirements for Plan users and maintainers. A wiki has proven to be the most efficient and effective means of implementing the feature requirements for the Plan. The wiki has proven very valuable as a research project management tool, and there are plans to expand its scope.

Delaney, Michael M.↗
NASA NTRS1973

Preliminary flight trajectories for the Apollo Soyuz test project

Preliminary data are documented for a typical launch window opening, a typical in-plane case, and a typical launch window closing trajectory, not necessarily in the same daily launch window, for the Apollo Soyuz test project mission. The Soyuz will be launched first and the Apollo will be launched on the first opportunity, 7 hours 21 minutes later. If the Apollo is unable to be launched on the first opportunity, four additional opportunities are available at 30 hours 56 minutes, 54 hours 31 minutes, 78 hours 05 minutes, and 101 hours 40 minutes. If the Apollo cannot be launched in this time frame, no further attempt will be made to launch and rendezvous with the first Soyuz. Soyuz will then be deorbited; however, a second Soyuz was made available for the same purposes.

Brooks, J. D.↗
NASA NTRS1994

Regular Topologies for Gigabit Wide-Area Networks: Congestion Avoidance Testbed Experiments

This document is Volume 3 of the final technical report on the work performed by SRI International (SRI) on SRI Project 8600. The document includes source listings for all software developed by SRI under this effort. Since some of our work involved the use of ST-II and the Sun Microsystems, Inc. (Sun) High-Speed Serial Interface (HSI/S) driver, we have included some of the source developed by LBL and BBN as well. In most cases, our decision to include source developed by other contractors depended on whether it was necessary to modify the original code. If we have modified the software in any way, it is included in this document. In the case of the Traffic Generator (TG), however, we have included all the ST-II software, even though BBN performed the integration, because the ST-II software is part of the standard TG release. It is important to note that all the code developed by other contractors is in the public domain, so that all software developed under this effort can be re-created from the source included here.

Denny, Barbara A.↗
NASA NTRS1992

View generated database

This document represents the final report for the View Generated Database (VGD) project, NAS7-1066. It documents the work done on the project up to the point at which all project work was terminated due to lack of project funds. The VGD was to provide the capability to accurately represent any real-world object or scene as a computer model. Such models include both an accurate spatial/geometric representation of surfaces of the object or scene, as well as any surface detail present on the object. Applications of such models are numerous, including acquisition and maintenance of work models for tele-autonomous systems, generation of accurate 3-D geometric/photometric models for various 3-D vision systems, and graphical models for realistic rendering of 3-D scenes via computer graphics.

Downward, James G.↗
NASA NTRS1997

Risk Management of NASA Projects

Various NASA Langley Research Center and other center projects were attempted for analysis to obtain historical data comparing pre-phase A study and the final outcome for each project. This attempt, however, was abandoned once it became clear that very little documentation was available. Next, extensive literature search was conducted on the role of risk and reliability concepts in project management. Probabilistic risk assessment (PRA) techniques are being used with increasing regularity both in and outside of NASA. The value and the usage of PRA techniques were reviewed for large projects. It was found that both civilian and military branches of the space industry have traditionally refrained from using PRA, which was developed and expanded by nuclear industry. Although much has changed with the end of the cold war and the Challenger disaster, it was found that ingrained anti-PRA culture is hard to stop. Examples of skepticism against the use of risk management and assessment techniques were found both in the literature and in conversations with some technical staff. Program and project managers need to be convinced that the applicability and use of risk management and risk assessment techniques is much broader than just in the traditional safety-related areas of application. The time has come to begin to uniformly apply these techniques. The whole idea of risk-based system can maximize the 'return on investment' that the public demands. Also, it would be very useful if all project documents of NASA Langley Research Center, pre-phase A through final report, are carefully stored in a central repository preferably in electronic format.

Sarper, Hueseyin↗
NASA NTRS2005

Risk Management for Human Support Technology Development

NASA requires continuous risk management for all programs and projects. The risk management process identifies risks, analyzes their impact, prioritizes them, develops and carries out plans to mitigate or accept them, tracks risks and mitigation plans, and communicates and documents risk information. Project risk management is driven by the project goal and is performed by the entire team. Risk management begins early in the formulation phase with initial risk identification and development of a risk management plan and continues throughout the project life cycle. This paper describes the risk management approach that is suggested for use in NASA's Human Support Technology Development. The first step in risk management is to identify the detailed technical and programmatic risks specific to a project. Each individual risk should be described in detail. The identified risks are summarized in a complete risk list. Risk analysis provides estimates of the likelihood and the qualitative impact of a risk. The likelihood and impact of the risk are used to define its priority location in the risk matrix. The approaches for responding to risk are either to mitigate it by eliminating or reducing the effect or likelihood of a risk, to accept it with a documented rationale and contingency plan, or to research or monitor the risk, The Human Support Technology Development program includes many projects with independently achievable goals. Each project must do independent risk management, considering all its risks together and trading them against performance, budget, and schedule. Since the program can succeed even if some projects fail, the program risk has a complex dependence on the individual project risks.

jones, Harry↗
NASA NTRS2008

Web Based Tool for Mission Operations Scenarios

A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher- and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum visibility across the project. One key aspect is that the tool was built for a scenario process that accounts for stakeholder input, review, comment, and concurrence. By creating well-designed opportunities for stakeholder input and concurrence and by making the scenario content easily accessible to all project personnel, we maximize the opportunities for stakeholders to both understand and agree on the concepts for how their mission is to be carried out.

Boyles, Carole A.↗
NASA NTRS1976

Ballistic Signature Identification System Study

The first phase of a research project directed toward development of a high speed automatic process to be used to match gun barrel signatures imparted to fired bullets was documented. An optical projection technique has been devised to produce and photograph a planar image of the entire signature, and the phototransparency produced is subjected to analysis using digital Fourier transform techniques. The success of this approach appears to be limited primarily by the accuracy of the photographic step since no significant processing limitations have been encountered.

Source record↗
NASA NTRS2013

SBKF Modeling and Analysis Plan: Buckling Analysis of Compression-Loaded Orthogrid and Isogrid Cylinders

This document outlines a Modeling and Analysis Plan (MAP) to be followed by the SBKF analysts. It includes instructions on modeling and analysis formulation and execution, model verification and validation, identifying sources of error and uncertainty, and documentation. The goal of this MAP is to provide a standardized procedure that ensures uniformity and quality of the results produced by the project and corresponding documentation.

Lovejoy, Andrew E.↗