SEARCH · Engineering Papers
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.
NASA's organization and policy for metrification, history from 1964, NASA participation in Federal agency activities, interaction with nongovernmental metrication organizations, and the proposed metrication assessment study are reviewed.
The use of K sub A-band to alleviate the radio metric degradation caused by charged particles is discussed. Those aspects of radio metrics which are relevant to the possible future use of K sub A-band deep space to Earth and Earth to deep space links are reviewed. In particular the effects of the Earth ionosphere, troposphere, and solar plasma are examined. It is concluded that, from the standpoint of reducing the harmful effects of charged particles, the use of K sub A-band appears highly desirable. While stability will be a more serious design constraint at K sub A-band than it is at X-band (for example in the ground power amplifier and the spacecraft multiplier stages) this problem is amenable to a state of the art engineering solution.
The frequencies of two atomic hydrogen masers and of three superconducting cavity stabilized oscillators were compared as the ensemble of oscillators was moved in the Sun's gravitational field by the rotation and orbital motion of the Earth. Metric gravitation theories predict that the gravitational redshifts of the two types of oscillators are identical, and that there should be no relative frequency shift between the oscillators; nonmetric theories, in contrast, predict a frequency shift between masers and SCSOs that is proportional to the change in solar gravitational potential experienced by the oscillators. The results are consistent with metric theories of gravitation at a level of 2%.
For a stochastic stress-energy tensor associated with cosmic turbulence, it is observed that Einstein's equations imply fluctuations in the space-time metric tensor. Such metrical fluctuations are shown to engender modified values for the average effective proper density and total pressure and thus to alter the solutions to the Friedman equations.
A model support system used to support a model in a wind tunnel test section is described. The model comprises a metric, or measured, half-span supported by a nonmetric, or nonmeasured half-span which is connected to a sting support. Moments and forces acting on the metric half-span are measured without interference from the support system during a wind tunnel test.
Functionally generated acceptance tests are examined using structural coverage metrics. A method of comparing acceptance tests and operational usage was generated. Acceptance tests are prepresentative of operational usage except for the mix of statement types. Structural coverage metrics may provide insight into software faults.
An algorithm was designed for a wire list net sort problem. A branch and bound algorithm for the metric traveling salesman problem is presented for this. The algorithm is a best bound first recursive descent where the bound is based on the triangle inequality. The bounded subsets are defined by the relative order of the first K of the N cities (i.e., a K city subtour). When K equals N, the bound is the length of the tour. The algorithm is implemented as a one page subroutine written in the C programming language for the VAX 11/750. Average execution times for randomly selected planar points using the Euclidean metric are 0.01, 0.05, 0.42, and 3.13 seconds for ten, fifteen, twenty, and twenty-five cities, respectively. Maximum execution times for a hundred cases are less than eleven times the averages. The speed of the algorithms is due to an initial ordering algorithm that is a N squared operation. The algorithm also solves the related problem where the tour does not return to the starting city and the starting and/or ending cities may be specified. It is possible to extend the algorithm to solve a nonsymmetric problem satisfying the triangle inequality.
Two topics in topology, the comparison of plane curves and faces on geometric models, are discussed. With regard to the first problem, a curve is defined to be a locus of points without any underlying parameterization. A metric on a class of plane curves is defined, a finite computation of this metric is given for the case of piecewise linear curves, and it is shown how to approximate curves that have bounded curvature by piecewise linear curves. In this way a bound on the distance between two curves can be computed. With regard to the second problem, the questions to be discussed are under what circumstances do geometrical faces make sense; how can they be explicity defined; and when are these geometrical faces homeomorphic to the realization of the abstract (topological) face.
An attempt is made to study the origin of coronal shocks by comparing several flare characteristics for two groups of flares: those with associated metric type II bursts and coronal mass ejections (CMEs) and those with associated metric type II bursts but no CMEs. CMEs accompany about 60 percent of all flares with type II bursts for solar longitudes greater than 30 deg, where CMEs are well observed with the NRL Solwind coronagraph. H-alpha flare areas, 1-8 A X-ray fluxes, and impulsive 3-cm fluxes are all statistically smaller for events with no CMEs than for events with CMEs. It appears that both compact and large mass ejection flares are associated with type II bursts. The events with no CMEs imply that at least many type II shocks are not piston-driven, but the large number of events of both groups with small 3 cm bursts does not support the usual assumption that type II shocks are produced by large energy releases in flare impulsive phases. The poor correlation between 3 cm burst fluxes and the occurrence of type II bursts may be due to large variations in the coronal Alfven velocity.
Fast velocities of 500 km/s or greater coronal mass ejections (CME's) are compared with reported metric type II bursts to study the properties of CME's associated with coronal shocks. An earlier report of fast frontside CME's with no associated metric type II bursts is confirmed, and it is calculated that 33 + or - 15 percent of all fast frontside CME's are not associated with such bursts. Faster CME's are more likely to be associated with type II bursts, as expected from the hypothesis of piston-driven shocks. However, CME brightness and associated peak 3-cm burst intensity are also important factors, as might be inferred from the Wagner and MacQueen (1983) view of type II shocks decoupled from associated CME's. The equal visibility of solar frontside and backside CME's is used to deduce the observability of backside type II bursts. It is calculated that 23 + or - 7 percent of all backside type II bursts associated with fast CME's can be observed at the earth and that 13 + or - 4 percent of all type II bursts originate in backside flares. CME speed again is the most important factor in the obervability of backside type II bursts.
This paper attempts to characterize and present a state of the art view of several quantitative models and metrics of the software life cycle. These models and metrics can be used to aid in managing and engineering software projects. They deal with various aspects of the software process and product, including resources allocation and estimation, changes and errors, size, complexity and reliability. Some indication is given of the extent to which the various models have been used and the success they have achieved.
The findings are reported of the Jet Propulsion Laboratory (JPL)/Software Product Assurance (SPA) Metrics Study, conducted as part of a larger JPL effort to improve software quality and productivity. Until recently, no comprehensive data had been assembled on how JPL manages and develops software-intensive systems. The first objective was to collect data on software development from as many projects and for as many years as possible. Results from five projects are discussed. These results reflect 15 years of JPL software development, representing over 100 data points (systems and subsystems), over a third of a billion dollars, over four million lines of code and 28,000 person months. Analysis of this data provides a benchmark for gauging the effectiveness of past, present and future software development work. In addition, the study is meant to encourage projects to record existing metrics data and to gather future data. The SPA long term goal is to integrate the collection of historical data and ongoing project data with future project estimations.
A parametric study of loudness levels with respect to weight, altitude, and Mach number for sonic boom signatures generated by two Mach 2.0 conceptual configurations is presented and compared with a similar study for nose shock overpressure. This paper discusses the relative importance of the two sonic boom metrics and the implications of the trends shown. Of the two configurations considered in this study, one was designed for optimum aerodynamic performance and the second was designed to produce a constrained overpressure sonic boom signature at cruise flight conditions. Results indicate that reductions in both loudness and overpressure level are possible when the configuration is shaped to produce a low boom signature. Results also prove that the loudness metric is a more reliable measure of the disturbance due to sonic booms than nose shock overpressure, because the overpressure does not include the sometimes significant effects of embedded shocks which are often present in mid-field low boom signatures.
Due to the large number of product, project, and people parameters which impact large custom software development efforts, measurement of software product quality is a complex undertaking. Furthermore, the absolute perspective from which quality is measured (customer satisfaction) is intangible. While we probably can't say what the absolute quality of a software product is, we can determine the relative quality, the adequacy of this quality with respect to pragmatic considerations, and identify good and bad trends during development. While no two software engineers will ever agree on an optimum definition of software quality, they will agree that the most important perspective of software quality is its ease of change. We can call this flexibility, adaptability, or some other vague term, but the critical characteristic of software is that it is soft. The easier the product is to modify, the easier it is to achieve any other software quality perspective. This paper presents objective quality metrics derived from consistent lifecycle perspectives of rework which, when used in concert with an evolutionary development approach, can provide useful insight to produce better quality per unit cost/schedule or to achieve adequate quality more efficiently. The usefulness of these metrics is evaluated by applying them to a large, real world, Ada project.
As an integral part of the overall upgraded National Airspace System (NAS), the objective of the Real-Time Weather Processor (RWP) project is to improve the quality of weather information and the timeliness of its dissemination to system users. To accomplish this, an RWP will be installed in each of the Center Weather Service Units (CWSUs), located in 21 of the 23 Air Route Traffic Control Centers (ARTCCs). The RWP System is a prototype system. It is planned that the software will be GFE and that production hardware will be acquired via industry competitive procurement. The ARTCC is a facility established to provide air traffic control service to aircraft operating on Instrument Flight Rules (IFR) flight plans within controlled airspace, principally during the en route phase of the flight. Covered here are requirement metrics, Software Problem Failure Reports (SPFRs), and Ada portability metrics and observations.
In recent years there has been a proliferation of proposals in the artificial intelligence (AI) literature for integrated agent architectures. Each architecture offers an approach to the general problem of constructing an integrated agent. Unfortunately, the ways in which one architecture might be considered better than another are not always clear. There has been a growing realization that many of the positive and negative aspects of an architecture become apparent only when experimental evaluation is performed and that to progress as a discipline, we must develop rigorous experimental methods. In addition to the intrinsic intellectual interest of experimentation, rigorous performance evaluation of systems is also a crucial practical concern to our research sponsors. DARPA, NASA, and AFOSR (among others) are actively searching for better ways of experimentally evaluating alternative approaches to building intelligent agents. One tool for experimental evaluation involves testing systems on benchmark tasks in order to assess their relative performance. As part of a joint DARPA and NASA funded project, NASA-Ames and Teleos Research are carrying out a research effort to establish a set of benchmark tasks and evaluation metrics by which the performance of agent architectures may be determined. As part of this project, we held a workshop on Benchmarks and Metrics at the NASA Ames Research Center on June 25, 1990. The objective of the workshop was to foster early discussion on this important topic. We did not achieve a consensus, nor did we expect to. Collected here is some of the information that was exchanged at the workshop. Given here is an outline of the workshop, a list of the participants, notes taken on the white-board during open discussions, position papers/notes from some participants, and copies of slides used in the presentations.
Software productivity metrics are useful for sizing and costing proposed software and for measuring development productivity. Estimating and measuring source lines of code (SLOC) has proven to be a bad idea because it encourages writing more lines of code and using lower level languages. Function Point Analysis is an improved software metric system, but it is not compatible with newer rapid prototyping and object-oriented approaches to software development. A process is presented here for counting object-oriented effort points, based on a preliminary object-oriented analysis. It is proposed that this approach is compatible with object-oriented analysis, design, programming, and rapid prototyping. Statistics gathered on actual projects are presented to validate the approach.
A great deal of effort is now being devoted to the study, analysis, prediction, and minimization of software maintenance expected cost, long before software is delivered to users or customers. It has been estimated that, on the average, the effort spent on software maintenance is as costly as the effort spent on all other software costs. Software design methods should be the starting point to aid in alleviating the problems of software maintenance complexity and high costs. Two aspects of maintenance deserve attention: (1) protocols for locating and rectifying defects, and for ensuring that noe new defects are introduced in the development phase of the software process; and (2) protocols for modification, enhancement, and upgrading. This article focuses primarily on the second aspect, the development of protocols to help increase the quality and reduce the costs associated with modifications, enhancements, and upgrades of existing software. This study developed parsimonious models and a relative complexity metric for complexity measurement of software that were used to rank the modules in the system relative to one another. Some success was achieved in using the models and the relative metric to identify maintenance-prone modules.