Search NASA⌕ Search

SEARCH · Search NASA

Results for “requirements 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 127 records · Page 7

The Origin and Early Evolution of Membrane Proteins

The origin and early evolution of membrane proteins, and in particular ion channels, are considered from the point of view that the transmembrane segments of membrane proteins are structurally quite simple and do not require specific sequences to fold. We argue that the transport of solute species, especially ions, required an early evolution of efficient transport mechanisms, and that the emergence of simple ion channels was protobiologically plausible. We also argue that, despite their simple structure, such channels could possess properties that, at the first sight, appear to require markedly larger complexity. These properties can be subtly modulated by local modifications to the sequence rather than global changes in molecular architecture. In order to address the evolution and development of ion channels, we focus on identifying those protein domains that are commonly associated with ion channel proteins and are conserved throughout the three main domains of life (Eukarya, Prokarya, and Archaea). We discuss the potassium-sodium-calcium superfamily of voltage-gated ion channels, mechanosensitive channels, porins, and ABC-transporters and argue that these families of membrane channels have sufficiently universal architectures that they can readily adapt to the diverse functional demands arising during evolution.

Pohorille, Andrew↗

Combinatorial Generation of Test Suites

Testgen is a computer program that generates suites of input and configuration vectors for testing other software or software/hardware systems. As systems become ever more complex, often, there is not enough time to test systems against all possible combinations of inputs and configurations, so test engineers need to be selective in formulating test plans. Testgen helps to satisfy this need: In response to a test-suite-requirement-specification model, it generates a minimal set of test vectors that satisfies all the requirements.

Dvorak, Daniel L.↗

Integrated Lunar Information Architecture for Decision Support Version 3.0 (ILIADS 3.0)

ILIADS 3.0 provides the data management capabilities to access CxP-vetted lunar data sets from the LMMP-provided Data Portal and the LMMP-provided On-Moon lunar data product server. (LMMP stands for Lunar Mapping and Modeling Project.) It also provides specific quantitative analysis functions to meet the stated LMMP Level 3 functional and performance requirements specifications that were approved by the CxP. The purpose of ILIADS 3.0 is to provide an integrated, rich client lunar GIS software application

Talabac, Stephen↗

USDA registration and rectification requirements

Some of the requirements of the United States Department of Agriculture for accuracy of aerospace acquired data, and specifically, requirements for registration and rectification of remotely sensed data are discussed. Particular attention is given to foreign and domestic crop estimation and forecasting, forestry information applications, and rangeland condition evaluations.

Allen, R.↗

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗

Field Guide for Designing Human Interaction with Intelligent Systems

The characteristics of this Field Guide approach address the problems of designing innovative software to support user tasks. The requirements for novel software are difficult to specify a priori, because there is not sufficient understanding of how the users' tasks should be supported, and there are not obvious pre-existing design solutions. When the design team is in unfamiliar territory, care must be taken to avoid rushing into detailed design, requirements specification, or implementation of the wrong product. The challenge is to get the right design and requirements in an efficient, cost-effective manner. This document's purpose is to describe the methods we are using to design human interactions with intelligent systems which support Space Shuttle flight controllers in the Mission Control Center at NASA/Johnson Space Center. Although these software systems usually have some intelligent features, the design challenges arise primarily from the innovation needed in the software design. While these methods are tailored to our specific context, they should be extensible, and helpful to designers of human interaction with other types of automated systems. We review the unique features of this context so that you can determine how to apply these methods to your project Throughout this Field Guide, goals of the design methods are discussed. This should help designers understand how a specific method might need to be adapted to the project at hand.

Malin, Jane T.↗

Towards the formal specification of the requirements and design of a processor interface unit: HOL listings

This technical report contains the HOL listings of the specification of the design and major portions of the requirements for a commercially developed processor interface unit (or PIU). The PIU is an interface chip performing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance-free operation, or both. This report contains the actual HOL listings of the PIU specification as it currently exists. Section two of this report contains general-purpose HOL theories that support the PIU specification. These theories include definitions for the hardware components used in the PIU, our implementation of bit words, and our implementation of temporal logic. Section three contains the HOL listings for the PIU design specification. Aside from the PIU internal bus (I-Bus), this specification is complete. Section four contains the HOL listings for a major portion of the PIU requirements specification. Specifically, it contains most of the definition for the PIU behavior associated with memory accesses initiated by the local processor.

Fura, David A.↗

Calibration-interval adjustment indicator - A concept

Circuit, when used with decision table, permits relatively unskilled personnel to maintain effective quality control. Design determines required changes in calibration intervals. Interval readings are recorded to nearest integer, making high precision unnecessary. Specific required performance-history information is discussed.

Hedene, P. S.↗

Utilizing inheritance in requirements engineering

The scope of this paper is the utilization of inheritance for requirements specification, i.e., the tasks of analyzing and modeling the domain, as well as forming and defining requirements. Our approach and the tool supporting it are named RETH (Requirements Engineering Through Hypertext). Actually, RETH uses a combination of various technologies, including object-oriented approaches and artificial intelligence (in particular frames). We do not attempt to exclude or replace formal representations, but try to complement and provide means for gradually developing them. Among others, RETH has been applied in the CERN (Conseil Europeen pour la Rechereche Nucleaire) Cortex project. While it would be impossible to explain this project in detail here, it should be sufficient to know that it deals with a generic distributed control system. Since this project is not finished yet, it is difficult to state its size precisely. In order to give an idea, its final goal is to substitute the many existing similar control systems at CERN by this generic approach. Currently, RETH is also tested using real-world requirements for the Pastel Mission Planning System at ESOC in Darmstadt. First, we outline how hypertext is integrated into a frame system in our approach. Moreover, the usefulness of inheritance is demonstrated as performed by the tool RETH. We then summarize our experiences of utilizing inheritance in the Cortex project. Lastly, RETH will be related to existing work.

Kaindl, Hermann↗

Thermal Storage Applications Workshop. Volume 2: Contributed Papers

The solar thermal and the thermal and thermochemical energy storage programs are described as well as the technology requirements for both external (electrical) and internal (thermal, chemical) modes for energy storage in solar power plants. Specific technical issues addressed include thermal storage criteria for solar power plants interfacing with utility systems; optimal dispatch of storage for solar plants in a conventional electric grid; thermal storage/temperature tradeoffs for solar total energy systems; the value of energy storage for direct-replacement solar thermal power plants; systems analysis of storage in specific solar thermal power applications; the value of seasonal storage of solar energy; criteria for selection of the thermal storage system for a 10 MW(2) solar power plant; and the need for specific requirements by storage system development teams.

Source record↗

Development of the ISS NORS

This paper will discuss the design and development of the Nitrogen Oxygen Recharge System (NORS) for the International Space Station (ISS). The emphasis of the paper is the collaborative effort between The Boeing Company and Cobham in the crafting of the architecture of the system to meet NASA's requirements. Specific examples to be discussed include the inclusion of the pneumatic isolation valve for compliance with safety requirement, the inclusion of a single stage regulator with flow limiter versus a two-stage regulator, and the use of integrated assemblies as opposed to separate valves/regulators. The paper will also discuss NORS experience with integrated assemblies (common body) verses prior ISS hardware and Cobham trade study efforts, to include lessons learned and potential applications to future programs.

Brandon, Richard↗

A CCIR aeronautical mobile satellite report

Propagation effects in the aeronautical mobile-satellite service differ from those in the fixed-satellite service and other mobile-satellite services because: small antennas are used on aircraft, and the aircraft body may affect the performance of the antenna; high aircraft speeds cause large Doppler spreads; aircraft terminals must accommodate a large dynamic range in transmission and reception; and due to their high speeds, banking maneuvers, and three-dimensional operation, aircraft routinely require exceptionally high integrity of communications, making even short-term propagation effects very important. Data and models specifically required to characterize the path impairments are discussed, which include: tropospheric effects, including gaseous attenuation, cloud and rain attenuation, fog attenuation, refraction and scintillation; surface reflection (multipath) effects; ionospheric effects such as scintillation; and environmental effects (aircraft motion, sea state, land surface type). Aeronautical mobile-satellite systems may operate on a worldwide basis, including propagation paths at low elevation angles. Several measurements of multipath parameters over land and sea were conducted. In some cases, laboratory simulations are used to compare measured data and verify model parameters. The received signals is considered in terms of its possible components: a direct wave subject to atmospheric effects, and a reflected wave, which generally contains mostly a diffuse component.

Davarian, Faramaz↗

SpaceWire Protocol ID: What Does It Mean To You?

Spacewire is becoming a popular solution for satellite high-speed data buses because it is a simple standard that provides great flexibility for a wide range of system requirements. It is simple in packet format and protocol, allowing users to easily tailor their implementation for their specific application. Some of the attractive aspects of Spacewire that make it easy to implement also make it hard for future reuse. Protocol reuse is difficult because Spacewire does not have a defined mechanism to communicate with the higher layers of the protocol stack. This has forced users of Spacewire to define unique packet formats and define how these packets are to be processed. Each mission writes their own Interface Control Document (ICD) and tailors Spacewire for their specific requirements making reuse difficult. Part of the reason for this habit may be because engineers typically optimize designs for their own requirements in the absence of a standard. This is an inefficient use of project resources and costs more to develop missions. A new packet format for Spacewire has been defined as a solution for this problem. This new packet format is a compliment to the Spacewire standard that will support protocol development upon Spacewire. The new packet definition does not replace the current packet structure, i.e., does not make the standard obsolete, but merely extends the standard for those who want to develop protocols over Spacewire. The Spacewire packet is defined with the first part being the Destination Address, which may be one or more bytes. This is followed by the packet cargo, which is user defined. The cargo is truncated with an End-Of-Packet (EOP) marker. This packet structure offers low packet overhead and allows the user to define how the contents are to be formatted. It also provides for many different addressing schemes, which provide flexibility in the system. This packet flexibility is typically an attractive part of the Spacewire. The new extended packet format adds one new field to the packet that greatly enhances the capability of Spacewire. This new field called the Protocol Identifier (ID) is used to identify the packet contents and the associated processing for the packet. This feature along with the restriction in the packet format that uses the Protocol ID, allows a deterministic method of decoding packets that was not before possible. The first part of the packet is still the Destination Address, which still conforms to the original standard but with one restriction. The restriction is that the first byte seen at the destination by the user needs to be a logical address, independent of the addressing scheme used. The second field is defined as the Protocol ID, which is usually one byte in length. The packet cargo (user defined) follows the Protocol ID. After the packet cargo is the EOP, which defines the end of packet. The value of the Protocol ID is assigned by the Spacewire working group and the protocol description published for others to use. The development of Protocols for Spacewire is currently the area of greatest activity by the Spacewire working group. The first protocol definition by the working group has been completed and is now in the process of formal standardization. There are many other protocols in development for missions that have not yet received formal Protocol ID assignment, but even if the protocols are not formally assigned a value, this effort will provide synergism for future developments.

Rakow, Glenn↗

The block program approach to photovoltaic module development

A series of photovoltaic module development activities, designated Blocks I through V, used increasingly refined requirements together with extensive testing and failure analysis to assist industry in developing the most advanced modules possible. The block program approach is described and the design details are given for all modules developed, highlighting the blockwise improvements. The success of this approach is demonstrated by the fact that most design details of the Block V modules have been adopted internationally. Instrumental to this success have been the steady improvements in design and test specifications that have guided module development. The experience gained since development of the Block-V specification is being incorporated into a Block VI Design and Test Specification, which includes upgraded and revised application-specific requirements. Highlights of this Block VI specification are also described.

Smokler, M. I.↗

Spacecraft guidance, navigation, and control requirements for an intelligent plug-n-play avionics (PAPA) architecture

The objective of this research is to design an intelligent plug-n-play avionics system that provides a reconfigurable platform for supporting the guidance, navigation and control (GN&C) requirements for different elements of the space exploration mission. The focus of this study is to look at the specific requirements for a spacecraft that needs to go from earth to moon and back. In this regard we will identify the different GN&C problems in various phases of flight that need to be addressed for designing such a plug-n-play avionics system. The Apollo and the Space Shuttle programs provide rich literature in terms of understanding some of the general GN&C requirements for a space vehicle. The relevant literature is reviewed which helps in narrowing down the different GN&C algorithms that need to be supported along with their individual requirements.

Kulkarni, Nilesh↗

VHF Wide-Band, Dual-Polarization Microstrip-Patch Antenna

The figure depicts selected aspects of a very-high-frequency (VHF) microstrip patch antenna designed and built to satisfy requirements specific to an airborne synthetic-aperture radar system for measuring the thickness of sea ice. One of the requirements is that the antenna be capable of functioning over the relatively wide frequency band of 127 to 172 MHz corresponding to a fractional bandwidth of about 30 percent relative to a nominal mid-band frequency of 149.5 MHz. Another requirement is that the antenna be capable of functioning in either or both of two orthogonal linear polarizations. In addition, the antenna is required to be as compact and lightweight as possible. In a basic design according to generally accepted microstrip-patch-antenna engineering practice, one would ordinarily use a relatively thick dielectric substrate and multiple feed probes to obtain the desired combination of wide-band and dual-polarization capabilities. However, the combination of a thick substrate and multiple feeds would give rise to higher-order electromagnetic nodes, thereby undesirably contributing to cross polarization and to reduction of the isolation between feed probes. To counter these adverse effects while satisfying the requirements stated above, the design of this antenna incorporates several improvements over the basic design.

Huang, John↗

Rapid Prediction of Installed Jet Noise from RANS

A new method of computing jet noise, called mSrc, was developed on the general principles of acoustic analogies. In the method, the problem of translating turbulent flow energy into acoustic energy at a far-field observer is broken into two parts, a calculation of acoustic source strengths and then their propagation. The acoustic sources are related to turbulent quantities in the jet plume in a robust manner. The propagation, which is more properly computed using a Green's function accounting for nonuniform speed of sound and solid surfaces, is instead modeled using commonly observed features of jet acoustic far field directivity, and by diffraction barrier theory for surfaces. The mSrc method does not require gradients of the predicted flow field, allowing it to make use of robust unstructured RANS CFD methods, including embedded boundary codes. Such codes do not require specification of surface meshes, and auto-refine their grid to resolve flow gradients, putting resolution where it is required without a priori user input. The ability of mSrc to use such radically unstructured flow input results in an efficient method of estimating noise from jet flows from complex nozzles installed on aircraft. Many validation cases are presented to demonstrate the accuracy and range of applicability of the mSrc method for representative jet noise applications.

Bridges, James↗