Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “SPECIFICATIONS”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Formal specification and verification of Ada software

The use of formal methods in software development achieves levels of quality assurance unobtainable by other means. The Larch approach to specification is described, and the specification of avionics software designed to implement the logic of a flight control system is given as an example. Penelope is described which is an Ada-verification environment. The Penelope user inputs mathematical definitions, Larch-style specifications and Ada code and performs machine-assisted proofs that the code obeys its specifications. As an example, the verification of a binary search function is considered. Emphasis is given to techniques assisting the reuse of a verification effort on modified code.

Hird, Geoffrey R.↗
NASA NTRS1991

Integrated flight/propulsion control specifications for systems with two-way coupling

A general technique for generating specifications for integrated flight propulsion control is extended to include systems with significant two-way coupling between the flight and propulsion systems. These specification define how the subsystems must perform within an integrated control system in order to assure that performance goals (specifically stability) are met when the subsystems are combined to form a closed-loop integrated system. Such specifications are useful for a large class of integrated control problems that are best approached in a partitioned or decentralized manner. An example demonstrating the application of these techniques to a simple helicopter problem is provided.

Rock, Stephen M.↗
NASA NTRS1991

Experiment module/support module interface specification for the reusable reentry satellite

This Interface Specification (IFS) identifies, defines, and controls the interface between the Reusable Reentry Satellite (RRS) Vehicle (RRV) Experiment Module (EM) and the Support Module (SM) equipment. Contained in this specification are the physical, functional, and environmental interface requirements for the SM and EM. This specification is tailored to the unique requirements of the EM associated with the Rodent Module. The addenda to this specification contain the requirements for alternate EM's.

Source record↗
NASA NTRS1992

On the nature of bias and defects in the software specification process

Implementation bias in a specification is an arbitrary constraint in the solution space. This paper describes the problem of bias. Additionally, this paper presents a model of the specification and design processes describing individual subprocesses in terms of precision/detail diagrams and a model of bias in multi-attribute software specifications. While studying how bias is introduced into a specification we realized that software defects and bias are dual problems of a single phenomenon. This was used to explain the large proportion of faults found during the coding phase at the Software Engineering Laboratory at NASA/GSFC.

Straub, Pablo A.↗
NASA NTRS1992

The KASE approach to domain-specific software systems

Designing software systems, like all design activities, is a knowledge-intensive task. Several studies have found that the predominant cause of failures among system designers is lack of knowledge: knowledge about the application domain, knowledge about design schemes, knowledge about design processes, etc. The goal of domain-specific software design systems is to explicitly represent knowledge relevant to a class of applications and use it to partially or completely automate various aspects of the designing systems within that domain. The hope is that this would reduce the intellectual burden on the human designers and lead to more efficient software development. In this paper, we present a domain-specific system built on top of KASE, a knowledge-assisted software engineering environment being developed at the Stanford Knowledge Systems Laboratory. We introduce the main ideas underlying the construction of domain specific systems within KASE, illustrate the application of the idea in the synthesis of a system for tracking aircraft from radar signals, and discuss some of the issues in constructing domain-specific systems.

Bhansali, Sanjay↗
NASA NTRS1992

Comparison of specificity and information for fuzzy domains

This paper demonstrates how an integrated theory can be built on the foundation of possibility theory. Information and uncertainty were considered in 'fuzzy' literature since 1982. Our departing point is the model proposed by Klir for the discrete case. It was elaborated axiomatically by Ramer, who also introduced the continuous model. Specificity as a numerical function was considered mostly within Dempster-Shafer evidence theory. An explicity definition was given first by Yager, who has also introduced it in the context of possibility theory. Axiomatic approach and the continuous model have been developed very recently by Ramer and Yager. They also establish a close analytical correspondence between specificity and information. In literature to date, specificity and uncertainty are defined only for the discrete finite domains, with a sole exception. Our presentation removes these limitations. We define specificity measures for arbitrary measurable domains.

Ramer, Arthur↗
NASA NTRS1988

NASA specification for manufacturing and performance requirements of NASA standard aerospace nickel-cadmium cells

On November 25, 1985, the NASA Chief Engineer established a NASA-wide policy to maintain and to require the use of the NASA standard for aerospace nickel-cadmium cells and batteries. The Associate Administrator for Safety, Reliability, Maintainability, and Quality Assurance stated on December 29, 1986, the intent to retain the NASA standard cell usage policy established by the Office of the Chief Engineer. The current NASA policy is also to incorporate technological advances as they are tested and proven for spaceflight applications. This policy will be implemented by modifying the existing standard cells or by developing new NASA standards and their specifications in accordance with the NASA's Aerospace Battery Systems Program Plan. This NASA Specification for Manufacturing and Performance Requirements of NASA Standard Aerospace Nickel-Cadmium Cells is prepared to provide requirements for the NASA standard nickel-cadmium cell. It is an interim specification pending resolution of the separator material availability. This specification has evolved from over 15 years of nickel-cadmium cell experience by NASA. Consequently, considerable experience has been collected and cell performance has been well characterized from many years of ground testing and from in-flight operations in both geosynchronous (GEO) and low earth orbit (LEO) applications. NASA has developed and successfully used two standard flight qualified cell designs.

Source record↗
NASA NTRS1993

An elementary tutorial on formal specification and verification using PVS

A tutorial on the development of a formal specification and its verification using the Prototype Verification System (PVS) is presented. The tutorial presents the formal specification and verification techniques by way of specific example - an airline reservation system. The airline reservation system is modeled as a simple state machine with two basic operations. These operations are shown to preserve a state invariant using the theorem proving capabilities of PVS. The technique of validating a specification via 'putative theorem proving' is also discussed and illustrated in detail. This paper is intended for the novice and assumes only some of the basic concepts of logic. A complete description of user inputs and the PVS output is provided and thus it can be effectively used while one is sitting at a computer terminal.

Butler, Ricky W.↗
NASA NTRS1994

NASA geometry data exchange specification for computational fluid dynamics (NASA IGES)

This document specifies a subset of an existing product data exchange specification that is widely used in industry and government. The existing document is called the Initial Graphics Exchange Specification. This document, a subset of IGES, is intended for engineers analyzing product performance using tools such as computational fluid dynamics (CFD) software. This document specifies how to define mathematically and exchange the geometric model of an object. The geometry is represented utilizing nonuniform rational B-splines (NURBS) curves and surfaces. Only surface models are represented; no solid model representation is included. This specification does not include most of the other types of product information available in IGES (e.g., no material properties or surface finish properties) and does not provide all the specific file format details of IGES. The data exchange protocol specified in this document is fully conforming to the American National Standard (ANSI) IGES 5.2.

Blake, Matthew W.↗
NASA NTRS1994

The meteorological parameterization of specific attenuation in rain viewed at Nadir

Polynomial expressions are presented for the parameterization of the specific attenuation in rain from 9 to 38 GHz that are applicable to a wide range of naturally occurring drop size distributions and for viewing angles close to nadir. Because the temperature T affects the specific attenuation at some frequencies, expressions for the polynomial coefficients as functions of T are also provided for -10C less than or equal to T less than or equal to 30C. The advantage of this parameterization is that even without a detailed specification of the drop size distribution, useful estimates of the specific attenuation are often possible given only two out of three parameters, namely, the rainfall rate R, the rainwater content W, or D(sub m) (the mass-weighted mean drop diameter), particularly if the temperature is also specified.

Jameson, A. R.↗
NASA NTRS1992

Domain and Specification Models for Software Engineering

This paper discusses our approach to representing application domain knowledge for specific software engineering tasks. Application domain knowledge is embodied in a domain model. Domain models are used to assist in the creation of specification models. Although many different specification models can be created from any particular domain model, each specification model is consistent and correct with respect to the domain model. One aspect of the system-hierarchical organization is described in detail.

Iscoe, Neil↗
NASA NTRS1995

Formal Methods Specification and Verification Guidebook for Software and Computer Systems: Planning and Technology Insertion - Volume 1

The Formal Methods Specification and Verification Guidebook for Software and Computer Systems describes a set of techniques called Formal Methods (FM), and outlines their use in the specification and verification of computer systems and software. Development of increasingly complex systems has created a need for improved specification and verification techniques. NASA's Safety and Mission Quality Office has supported the investigation of techniques such as FM, which are now an accepted method for enhancing the quality of aerospace applications. The guidebook provides information for managers and practitioners who are interested in integrating FM into an existing systems development process. Information includes technical and administrative considerations that must be addressed when establishing the use of FM on a specific project. The guidebook is intended to aid decision makers in the successful application of FM to the development of high-quality systems at reasonable cost. This is the first volume of a planned two-volume set. The current volume focuses on administrative and planning considerations for the successful application of FM.

Source record↗
NASA NTRS1999

Designing Specification Languages for Process Control Systems: Lessons Learned and Steps to the Future

Previously, we defined a blackbox formal system modeling language called RSML (Requirements State Machine Language). The language was developed over several years while specifying the system requirements for a collision avoidance system for commercial passenger aircraft. During the language development, we received continual feedback and evaluation by FAA employees and industry representatives, which helped us to produce a specification language that is easily learned and used by application experts. Since the completion of the PSML project, we have continued our research on specification languages. This research is part of a larger effort to investigate the more general problem of providing tools to assist in developing embedded systems. Our latest experimental toolset is called SpecTRM (Specification Tools and Requirements Methodology), and the formal specification language is SpecTRM-RL (SpecTRM Requirements Language). This paper describes what we have learned from our use of RSML and how those lessons were applied to the design of SpecTRM-RL. We discuss our goals for SpecTRM-RL and the design features that support each of these goals.

Leveson, Nancy G.↗
NASA NTRS1998

Compositional Specification of Software Architecture

This paper describes our experience using parameterized algebraic specifications to model properties of software architectures. The goal is to model the decomposition of requirements independent of the style used to implement the architecture. We begin by providing an overview of the role of architecture specification in software development. We then describe how architecture specifications are build up from component and connector specifications and give an overview of insights gained from a case study used to validate the method.

Penix, John↗
NASA NTRS2001

Structuring Formal Requirements Specifications for Reuse and Product Families

In this project we have investigated how formal specifications should be structured to allow for requirements reuse, product family engineering, and ease of requirements change, The contributions of this work include (1) a requirements specification methodology specifically targeted for critical avionics applications, (2) guidelines for how to structure state-based specifications to facilitate ease of change and reuse, and (3) examples from the avionics domain demonstrating the proposed approach.

Heimdahl, Mats P. E.↗
NASA NTRS2002

Specification of the ISS Plasma Environment Variability

Quantifying the spacecraft charging risks and corresponding hazards for the International Space Station (ISS) requires a plasma environment specification describing the natural variability of ionospheric temperature (Te) and density (Ne). Empirical ionospheric specification and forecast models such as the International Reference Ionosphere (IRI) model typically only provide estimates of long term (seasonal) mean Te and Ne values for the low Earth orbit environment. Knowledge of the Te and Ne variability as well as the likelihood of extreme deviations from the mean values are required to estimate both the magnitude and frequency of occurrence of potentially hazardous spacecraft charging environments for a given ISS construction stage and flight configuration. This paper describes the statistical analysis of historical ionospheric low Earth orbit plasma measurements used to estimate Ne, Te variability in the ISS flight environment. The statistical variability analysis of Ne and Te enables calculation of the expected frequency of Occurrence of any particular values of Ne and Te, especially those that correspond to possibly hazardous spacecraft charging environments. The database used in the original analysis included measurements from the AE-C, AE-D, and DE-2 satellites. Recent work on the database has added additional satellites to the database and ground based incoherent scatter radar observations as well. Deviations of the data values from the IRI estimated Ne, Te parameters for each data point provide a statistical basis for modeling the deviations of the plasma environment from the IRI model output. This technique, while developed specifically for the Space Station analysis, can also be generalized to provide ionospheric plasma environment risk specification models for low Earth orbit over an altitude range of 200 km through approximately 1000 km.

Minow, Joseph I.↗
NASA NTRS2004

Development and Characterization of High-Efficiency, High-Specific Impulse Xenon Hall Thrusters

This dissertation presents research aimed at extending the efficient operation of 1600 s specific impulse Hall thruster technology to the 2000 to 3000 s range. Motivated by previous industry efforts and mission studies, the aim of this research was to develop and characterize xenon Hall thrusters capable of both high-specific impulse and high-efficiency operation. During the development phase, the laboratory-model NASA 173M Hall thrusters were designed and their performance and plasma characteristics were evaluated. Experiments with the NASA-173M version 1 (v1) validated the plasma lens magnetic field design. Experiments with the NASA 173M version 2 (v2) showed there was a minimum current density and optimum magnetic field topography at which efficiency monotonically increased with voltage. Comparison of the thrusters showed that efficiency can be optimized for specific impulse by varying the plasma lens. During the characterization phase, additional plasma properties of the NASA 173Mv2 were measured and a performance model was derived. Results from the model and experimental data showed how efficient operation at high-specific impulse was enabled through regulation of the electron current with the magnetic field. The electron Hall parameter was approximately constant with voltage, which confirmed efficient operation can be realized only over a limited range of Hall parameters.

Hofer, Richard R.↗
NASA NTRS2002

Sensory, motor, and combined contexts for context-specific adaptation of saccade gain in humans

Saccadic eye movements can be adapted in a context-specific manner such that their gain can be made to depend on the state of a prevailing context cue. We asked whether context cues are more effective if their nature is primarily sensory, motor, or a combination of sensory and motor. Subjects underwent context-specific adaptation using one of three different context cues: a pure sensory context (head roll-tilt right or left); a pure motor context (changes in saccade direction); or a combined sensory-motor context (head roll-tilt and changes in saccade direction). We observed context-specific adaptation in each condition; the greatest degree of context-specificity occurred in paradigms that used the motor cue, alone or in conjunction with the sensory cue. Copyright 2002 Elsevier Science Ireland Ltd.

NASA Discipline Neuroscience↗