Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “problem reporting”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1990

Information and problem report usage in system saftey engineering division

Five basic problems or question areas are examined. They are as follows: (1) Evaluate adequacy of current problem/performance data base; (2) Evaluate methods of performing trend analysis; (3) Methods and sources of data for probabilistic risk assessment; and (4) How is risk assessment documentation upgraded and/or updated. The fifth problem was to provide recommendations for each of the above four areas.

Morrissey, Stephen J.↗
NASA NTRS1975

Detailed requirements document for the problem reporting data system (PDS)

The system is described as a computer-based system designed to track the status of problems and corrective actions pertinent to space shuttle hardware. The input, processing, output, and performance requirements of the system are presented along with standard display formats and examples. Operational requirements, hardware, requirements, and test requirements are also included.

West, R. S.↗
NASA NTRS1995

The specification-based validation of reliable multicast protocol: Problem Report

Reliable Multicast Protocol (RMP) is a communication protocol that provides an atomic, totally ordered, reliable multicast service on top of unreliable IP multicasting. In this report, we develop formal models for RMP using existing automated verification systems, and perform validation on the formal RMP specifications. The validation analysis help identifies some minor specification and design problems. We also use the formal models of RMP to generate a test suite for conformance testing of the implementation. Throughout the process of RMP development, we follow an iterative, interactive approach that emphasizes concurrent and parallel progress of implementation and verification processes. Through this approach, we incorporate formal techniques into our development process, promote a common understanding for the protocol, increase the reliability of our software, and maintain high fidelity between the specifications of RMP and its implementation.

Wu, Yunqing↗
NASA NTRS1971

Systems management techniques and problems

Report is reviewed which discusses history and trends of systems management, its basic principles, and nature of problems that lend themselves to systems approach. Report discusses systems engineering as applied to weapons acquisition, ecology, patient monitoring, and retail merchandise operations.

Source record↗
NASA NTRS1991

QR Factorization In The Partial-Realization Problem

Report discusses use of QR factorization in solving partial-realization problem. Subject matter relevant to characterization of system, details of which hidden (a "blackbox"), on basis of relationship between its inputs and outputs. When realization process successful, system shown linear with known number of degrees of freedom and representable by mathematical model providing basis for prediction of outputs and design of controllers.

Verhaegen, M. H.↗
NASA NTRS1919

General Analysis of Airplane Radiator Problems

Report embodies the results of a very extensive research, both theoretical and experimental, into the problems involved in the dissipation of heat by means of the airplane radiator.

Dickinson, H C↗
NASA NTRS1991

Analysis of launch site processing effectiveness for the Space Shuttle 26R payload

A trend analysis study has been performed on problem reports recorded during the Space Shuttle 26R payload's processing cycle at NASA-Kennedy, using the defect-flow analysis (DFA) methodology; DFA gives attention to the characteristics of the problem-report 'population' as a whole. It is established that the problem reports contain data which distract from pressing problems, and that fully 60 percent of such reports were caused during processing at NASA-Kennedy. The second major cause of problem reports was design defects.

Flores, Carlos A.↗
NASA NTRS1980

The Crimean Solar Maximum Year Workshop, selected reports

Problems associated with the transport of energy and acceleration of charged particles in solar flares are considered. Existing theories are compared with observation with a view to either discriminating between rival theories (such as whether hard X-rays are emitted by thermal or nonthermal bremsstrahlung), constraining existing theories (such as deduction of the number of nonthermal electrons present from spectroscopic diagnostics in the soft X-ray part of the spectrum), or suggesting theories (such as attempting to explain the observed spatial structure of microwave emission relative to alpha).

Emslie, A. G.↗
NASA NTRS2001

Intelligent Text Retrieval and Knowledge Acquisition from Texts for NASA Applications: Preprocessing Issues

In this contract, which is a component of a larger contract that we plan to submit in the coming months, we plan to study the preprocessing issues which arise in applying natural language processing techniques to NASA-KSC problem reports. The goals of this work will be to deal with the issues of: a) automatically obtaining the problem reports from NASA-KSC data bases, b) the format of these reports and c) the conversion of these reports to a format that will be adequate for our natural language software. At the end of this contract, we expect that these problems will be solved and that we will be ready to apply our natural language software to a text database of over 1000 KSC problem reports.

Source record↗
NASA NTRS2008

JPL Test Effectiveness Analysis

1) The pilot study provided meaningful conclusions that are generally consistent with the earlier Test Effectiveness work done between 1992 and 1994: a) Analysis of pre-launch problem/failure reports is consistent with earlier work. b) Analysis of post-launch early mission anomaly reports indicates that there are more software issues in newer missions, and the no-test category for identification of post-launch failures is more significant than in the earlier analysis. 2) Future work includes understanding how differences in Missions effect these analyses: a) There are large variations in the number of problem reports and issues that are documented by the different Projects/Missions. b) Some missions do not have any reported environmental test anomalies, even though environmental tests were performed. 3) Each project/mission has different standards and conventions for filling out the PFR forms, the industry may wish to address this issue: a) Existing problem reporting forms are to document and track problems, failures, and issues (etc.) for the projects, to ensure high quality. b) Existing problem reporting forms are not intended for data mining.

failure cause↗