Search NASA⌕ Search

SEARCH · Search NASA

Results for “system specification”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1977

Space radar system specifications

System specifications are proposed for an imaging radar whose primary objective is to provide useful information for land applications including hydrology, agriculture and geology.

Ulaby, F. T.↗
NASA NTRS1968

Development of a Space Vehicle Electromagnetic Interference/compatibility Specification. Volume 3 - System Specification

This specification represents a new approach to controlling electromagnetic interference. In this approach the system integration contractor will be responsible for the development of discrete specification limits to be utilized on the program to which this specification is applied. The specification limits imposed upon subsystem contractors will be developed by the use of a computer program, available from the procuring agency, which is designed to consider the total system electromagnetic environment in the computation of these limits. The integration contractor will be required to mathematically model those circuits which represent required emitters and receptors of electromagnetic energy on the space vehicle. There are contained herein, a list of available computer models into which must be inserted particular parameters of the spacecraft subsystems. These functional models, when inserted into the computer program, will develop discrete specification limits based upon the requirements of the particular system modelled.

Cooperstein, B. D.↗
NASA NTRS1989

Outline for reusable reentry satellite system specification, volumes 1 - volume 9

This document describes the outline proposed by the SAIC team for the RRS System Specification document. This document will be updated periodically during the course of the study, providing design insights and information pertinent to the various elements of the RRS design. The RRS System Specification document organization is shown schematically. The RRS Vehicle (RRV), Payload Module (PM), and the Operations Support (OS) are the three main segments of the overall system for which formal interface control will exist. The number and relationship of these interface specifications to the main segments is also shown.

Source record↗
NASA NTRS1976

Mission Control Center (MCC) System Specification for the Shuttle Orbital Flight Test (OFT) Timeframe

System specifications to be used by the mission control center (MCC) for the shuttle orbital flight test (OFT) time frame were described. The three support systems discussed are the communication interface system (CIS), the data computation complex (DCC), and the display and control system (DCS), all of which may interfere with, and share processing facilities with other applications processing supporting current MCC programs. The MCC shall provide centralized control of the space shuttle OFT from launch through orbital flight, entry, and landing until the Orbiter comes to a stop on the runway. This control shall include the functions of vehicle management in the area of hardware configuration (verification), flight planning, communication and instrumentation configuration management, trajectory, software and consumables, payloads management, flight safety, and verification of test conditions/environment.

Source record↗
NASA NTRS1988

MODIS Information, Data, and Control System (MIDACS) system specifications and conceptual design

The MODIS Information, Data, and Control System (MIDACS) Specifications and Conceptual Design Document discusses system level requirements, the overall operating environment in which requirements must be met, and a breakdown of MIDACS into component subsystems, which include the Instrument Support Terminal, the Instrument Control Center, the Team Member Computing Facility, the Central Data Handling Facility, and the Data Archive and Distribution System. The specifications include sizing estimates for the processing and storage capacities of each data system element, as well as traffic analyses of data flows between the elements internally, and also externally across the data system interfaces. The specifications for the data system, as well as for the individual planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, and data archive and distribution components, do not yet fully specify the data system in the complete manner needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams have not yet been formed; however, it was possible to develop the specifications and conceptual design based on the present concept of EosDIS, the Level-1 and Level-2 Functional Requirements Documents, the Operations Concept, and through interviews and meetings with key members of the scientific community.

Han, D.↗
NASA NTRS1976

LUMIS Interactive graphics operating instructions and system specifications

The LUMIS program has designed an integrated geographic information system to assist program managers and planning groups in metropolitan regions. Described is the system designed to interactively interrogate a data base, display graphically a portion of the region enclosed in the data base, and perform cross tabulations of variables within each city block, block group, or census tract. The system is designed to interface with U. S. Census DIME file technology, but can accept alternative districting conventions. The system is described on three levels: (1) introduction to the systems's concept and potential applications; (2) the method of operating the system on an interactive terminal; and (3) a detailed system specification for computer facility personnel.

Bryant, N. A.↗
NASA NTRS1992

Knowledge-based approach for generating target system specifications from a domain model

Several institutions in industry and academia are pursuing research efforts in domain modeling to address unresolved issues in software reuse. To demonstrate the concepts of domain modeling and software reuse, a prototype software engineering environment is being developed at George Mason University to support the creation of domain models and the generation of target system specifications. This prototype environment, which is application domain independent, consists of an integrated set of commercial off-the-shelf software tools and custom-developed software tools. This paper describes the knowledge-based tool that was developed as part of the environment to generate target system specifications from a domain model.

Gomaa, Hassan↗
NASA NTRS1976

HAL/S-FC compiler system specifications

This document specifies the informational interfaces within the HAL/S-FC compiler, and between the compiler and the external environment. This Compiler System Specification is for the HAL/S-FC compiler and its associated run time facilities which implement the full HAL/S language. The HAL/S-FC compiler is designed to operate stand-alone on any compatible IBM 360/370 computer and within the Software Development Laboratory (SDL) at NASA/JSC, Houston, Texas.

Source record↗
NASA NTRS1976

Radar system specifications for hydrology and agriculture

Using truck-mounted radar spectrometers, an experimental program was conducted from 1971 to 1976 to define radar system specifications for hydrological and agricultural applications. Data were acquired over the 1-18 GHz region, 0 deg (nadir) to 70 deg range and for all linear polarization combinations. The discussion here concerns radar parameters for crop classification and for soil moisture determination.

Ulaby, F. T.↗
NASA NTRS1991

Generating target system specifications from a domain model using CLIPS

The quest for reuse in software engineering is still being pursued and researchers are actively investigating the domain modeling approach to software construction. There are several domain modeling efforts reported in the literature and they all agree that the components that are generated from domain modeling are more conducive to reuse. Once a domain model is created, several target systems can be generated by tailoring the domain model or by evolving the domain model and then tailoring it according to the specified requirements. This paper presents the Evolutionary Domain Life Cycle (EDLC) paradigm in which a domain model is created using multiple views, namely, aggregation hierarchy, generalization/specialization hierarchies, object communication diagrams and state transition diagrams. The architecture of the Knowledge Based Requirements Elicitation Tool (KBRET) which is used to generate target system specifications is also presented. The preliminary version of KBRET is implemented in the C Language Integrated Production System (CLIPS).

Sugumaran, Vijayan↗
NASA NTRS1971

Expendable Second Stage Reusable Space Shuttle Booster: Preliminary System Specification - Volume 9

The specification for establishing the requirements for the system performance, design, development, and ground and flight operations of the expendable second stage on a reusable space shuttle booster system is presented. The basic specification is that the system shall be capable of placing payloads in excess of 100,000 pounds into earth orbit. In addition, the expendable second stage provides a multimission, economical, large capability system suitable for a variety of space missions in the 1980 time period.

Source record↗
NASA NTRS2012

Architectural Implementation of NASA Space Telecommunications Radio System Specification

This software demonstrates a working implementation of the NASA STRS (Space Telecommunications Radio System) architecture specification. This is a developing specification of software architecture and required interfaces to provide commonality among future NASA and commercial software-defined radios for space, and allow for easier mixing of software and hardware from different vendors. It provides required functions, and supports interaction with STRS-compliant simple test plug-ins ("waveforms"). All of it is programmed in "plain C," except where necessary to interact with C++ plug-ins. It offers a small footprint, suitable for use in JPL radio hardware. Future NASA work is expected to develop into fully capable software-defined radios for use on the space station, other space vehicles, and interplanetary probes.

Peters, Kenneth J.↗