Search NASA⌕ Search

SEARCH · Search NASA

Results for “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 217 records · Page 12

Electron/proton spectrometer certification documentation analyses

A compilation of analyses generated during the development of the electron-proton spectrometer for the Skylab program is presented. The data documents the analyses required by the electron-proton spectrometer verification plan. The verification plan was generated to satisfy the ancillary hardware requirements of the Apollo Applications program. The certification of the spectrometer requires that various tests, inspections, and analyses be documented, approved, and accepted by reliability and quality control personnel of the spectrometer development program.

Gleeson, P.↗

Program documentation with advanced data management systems

The problems of program documentation are considered for those cases in which the programmer is using a computer along with an advanced DMS. Three problem areas discussed include: data description, process description, and execution-time documentation.

Swift, W. B.↗

Automated documentation of an assembly program

A program is discussed that can be used as input to another program which will automatically document it. This program was implemented using assembly language program, META-SYMBOL, on XDS 930 computer. The characteristics and identification of the documentation program, DOCMNT, are described.

Thomas, V. L.↗

Cost advantages of an integrated documentation approach

Interactive use of on-line computing terminals for updating programs is discussed. An integrated documentation approach using predocumented subroutines and metaprogram techniques is found to be an efficient means of generating the relevant documentation and of reducing program development costs.

Felsman, W. O.↗

Program automated documentation methods

The mission analysis and trajectory simulation program is summarized; it provides an understanding of the size and complexity of one simulation for which documentation is mandatory. Programs for automating documentation of subroutines, flow charts, and internal cross reference information are also included.

Lanzano, B. C.↗

Space shuttle GN and C equation document no. 21: Shuttle unified navigation filter

The space shuttle navigation equations are presented in a form for a single unified navigation filter used in each mission phase. The document serves as a single reference for the navigation equations replacing each of the individual mission phase navigation documents previously published. The fundamental characteristics of the navigation filter are described. The features of the unified formulation of the filter are analyzed.

Muller, E. S., Jr.↗

Design study of RL10 derivatives. Volume 3, part 1: Preliminary interface control document

The Interface Control Document contains engine information necessary for installation of the baseline RL10 Derivative engines in the Space Tug vehicle. The ICD presents a description of the baseline engines and their operating characteristics, mass and load characteristics, and environmental criteria. The document defines the engine/vehicle mechanical, electrical, fluid and pneumatic interface requirements.

Adams, A.↗

Apollo experience report: Mission evaluation team postflight documentation

The various postflight reports prepared by the mission evaluation team, including the final mission evaluation report, report supplements, anomaly reports, and the 5-day mission report, are described. The procedures for preparing each report from the inputs of the various disciplines are explained, and the general method of reporting postflight results is discussed. Recommendations for postflight documentation in future space programs are included. The official requirements for postflight documentation and a typical example of an anomaly report are provided as appendixes.

Dodson, J. W.↗

Computer output microfilm (FR80) systems software documentation, volume 2

The system consists of a series of programs which convert digital data from magnetic tapes into alpha-numeric characters, graphic plots, and imagery that is recorded on the face of a cathode ray tube. A special camera photographs the face of the tube on microfilm for subsequent display on a film reader. The applicable documents which apply to this system are delineated. The functional relationship between the system software, the standard insert routines, and the applications programs is described; all the applications programs are described in detail. Instructions for locating those documents are presented along with test preparations sheets for all baseline and/or program modification acceptance tests.

Source record↗

Automatic documentation system extension to multi-manufacturers' computers and to measure, improve, and predict software reliability. Appendix A and B

A manual which explains how to use the DOMONIC command language is presented. The manual consists of the following sections: 1. Introduction 2. What You Must Know to Use DOMONIC 3. Functions of DOMONIC 4. Entering and Manipulating Data 5. Templates and Data Definitions 6. Recipes and Document Generation 7. Initiating A Project and 8. Entering and Changing Security Controls. The first four sections must be known by all DOMONIC users. Sections five, seven and eight describe functions normally used only by project management. Section six tells how to generate documents. The manual specifies what commands to use in performing each of the functions mentioned above.

Simmons, D. B.↗

Orbiter description document for Jupiter Orbiter Probe 1981/1982 Mission

The Jupiter Orbiter as it is presently understood is documented. Because the Jupiter Orbiter Probe 1981/1982 (JOP 81/82) Project will be severely cost constrained, the Orbiter design and capabilities described herein are not subject to major change or modification as a result of instrument selection. The JOP science payload should conform to this defined capability and the specified interfaces. A description and discussion of any science instrument complement is excluded, except the imaging science subsystem and the radio science capability which are provided by the project as Orbiter facilities. The environmental design requirements and the mission operations description are studied. This document has been prepared specifically for the JOP Announcement of Opportunity proposal preparation package and describes the Jupiter Orbiter in sufficient detail to allow the science community to propose scientific instrumentation consistent with its capabilities and limitations.

Source record↗

An experimental documentation of pressure gradient and Reynolds number effects on compressible turbulent boundary layers

Attached supersonic turbulent boundary layers, with a wide range of adverse pressure gradient strengths, are investigated for Reynolds numbers from 11.7 x 1 million to 314 x 1 million. Surface pressure and surface shear measurements were obtained for six flow fields over the entire Reynolds number range. In addition, two flow fields - one with a moderate pressure gradient and the other with a severe pressure gradient - are thoroughly documented at a single Reynolds number. This experimental documentation includes both mean and fluctuating profiles throughout the flow field, and is sufficient to define the complete flow field, including the upstream undisturbed flow region.

Kussoy, M. I.↗

Flight design system-1 system design. Volume 5: Data management and data base documentation support system

Application software intended to reduce the man-hours required per flight design cycle by producing major flight design documents with little or no manual typing is described. The documentation support software is divided into two separately executable processors. However, since both processors support the same overall functions, and most of the software contained in one is also contained in the other, both are collectively presented.

Source record↗

User Documentation for Multiple Software Releases

In proposed solution to problems of frequent software releases and updates, documentation would be divided into smaller packages, each of which contains data relating to only one of several software components. Changes would not affect entire document. Concept would improve dissemination of information regarding changes and would improve quality of data supporting packages. Would help to insure both timeliness and more thorough scrutiny of changes.

Humphrey, R.↗

MPS Solidification Model. Volume 2: Operating guide and software documentation for the unsteady model

The operation of solidification Model 2 is described and documentation of the software associated with the model is provided. Model 2 calculates the macrosegregation in a rectangular ingot of a binary alloy as a result of unsteady horizontal axisymmetric bidirectional solidification. The solidification program allows interactive modification of calculation parameters as well as selection of graphical and tabular output. In batch mode, parameter values are input in card image form and output consists of printed tables of solidification functions. The operational aspects of Model 2 that differ substantially from Model 1 are described. The global flow diagrams and data structures of Model 2 are included. The primary program documentation is the code itself.

Maples, A. L.↗

Documentation for the machine-readable version of OAO 2 filter photometry of 531 stars of diverse types

A magnetic tape version of the ultraviolet photometry of 531 stars observed with the Wisconsin Experiment Package aboard the Orbiting Astronomical Observatory (OAO 2) is described. The data were obtained with medium band interference filters and were reduced to a uniform magnitude system. They represent a subset of partially reduced data currently on file at the National Space Science Data Center. The document is intended to enable users of the tape file to read and process data without problems or guesswork. For technical details concerning the observations, instrumentation limitations, and interpretation of the data the reference publication should be consulted. This document was designed for distribution with any machine-readable version of the OAO 2 photometric data.

Warren, W. H., Jr.↗

An Automated FORTRAN documenter

A set of programs designed to help R&D programmers document their FORTRAN programs more effectively were written. The central program reads FORTRAN source code and asks the programmer questions about things it has not heard of before. It inserts the answers to these questions as comments into the FORTRAN code. The comments, as well as extensive cross-reference information, are also written to an unformatted file. Other programs read this file to produce printed information or to act as an interactive document.

Erickson, T.↗