Search NASA⌕ Search

SEARCH · Search NASA

Results for “REPORTING REQUIREMENTS”

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 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS1992

Compatibility and consistency in display-control systems - Implications for aircraft decision aid design

In this study we contrast display-control movement relations defined in terms of stimulus-response (physical) compatibility with those defined by stimulus-cognitive compatibility, and we relate these findings to the issue of command versus status levels of decision aid support. A second issue addressed is the cost of inconsistency across multiple display-control mappings. Subjects performed a flight control task while responding to one to four analog indicators, formatted as either command or status displays. The results suggest that there is an advantage for the status format when subjects are required to verbally report the state of the indicator(s), but no advantage was found for either format when subjects were required to manually correct the indicated state. The data point to the importance of display-control consistency and suggest that it may even outweigh that of compatibility.

Andre, Anthony D.↗
NASA NTRS1988

Space-based multifunctional end effector systems functional requirements and proposed designs

The end effector is an essential element of teleoperator and telerobot systems to be employed in space in the next decade. The report defines functional requirements for end effector systems to perform operations that are currently only feasible through Extra-Vehicular Activity (EVA). Specific tasks and functions that the end effectors must be capable of performing are delineated. Required capabilities for forces and torques, clearances, compliance, and sensing are described, using current EVA requirements as guidelines where feasible. The implications of these functional requirements on the elements of potential end effector systems are discussed. The systems issues that must be considered in the design of space-based manipulator systems are identified; including impacts on subsystems tightly coupled to the end effector, i.e., control station, information processing, manipulator arm, tool and equipment stowage. Possible end effector designs are divided into three categories: single degree-of-freedom end effectors, multiple degree of freedom end effectors, and anthropomorphic hands. Specific design alternatives are suggested and analyzed within the individual categories. Two evaluations are performed: the first considers how well the individual end effectors could substitute for EVA; the second compares how manipulator systems composed of the top performers from the first evaluation would improve the space shuttle Remote Manipulator System (RMS) capabilities. The analysis concludes that the anthropomorphic hand is best-suited for EVA tasks. A left- and right-handed anthropomorphic manipulator arm configuration is suggested as appropriate to be affixed to the RMS, but could also be used as part of the Smart Front End for the Orbital Maneuvering Vehicle (OMV). The technical feasibility of the anthropomorphic hand and its control are demonstrated. An evolutionary development approach is proposed and approximate scheduling provided for implementing the suggested manipulator systems in time for space stations operations in the early 1990s.

Mishkin, A. H.↗
NASA NTRS1991

Ground Systems Development Environment (GSDE) interface requirements analysis: Operations scenarios

This report is a preliminary assessment of the functional and data interface requirements to the link between the GSDE GS/SPF (Amdahl) and the Space Station Control Center (SSCC) and Space Station Training Facility (SSTF) Integration, Verification, and Test Environments (IVTE's). These interfaces will be involved in ground software development of both the control center and the simulation and training systems. Our understanding of the configuration management (CM) interface and the expected functional characteristics of the Amdahl-IVTE interface is described. A set of assumptions and questions that need to be considered and resolved in order to complete the interface functional and data requirements definitions are presented. A listing of information items defined to describe software configuration items in the GSDE CM system is included. It also includes listings of standard reports of CM information and of CM-related tools in the GSDE.

Church, Victor E.↗
NASA NTRS2009

NASA Standard for Models and Simulations: Philosophy and Requirements Overview

Following the Columbia Accident Investigation Board report, the NASA Administrator chartered an executive team (known as the Diaz Team) to identify those CAIB report elements with NASA-wide applicability and to develop corrective measures to address each element. One such measure was the development of a standard for the development, documentation, and operation of models and simulations. This report describes the philosophy and requirements overview of the resulting NASA Standard for Models and Simulations.

Blattnig, St3eve R.↗
NASA NTRS2013

NASA Standard for Models and Simulations: Philosophy and Requirements Overview

Following the Columbia Accident Investigation Board report, the NASA Administrator chartered an executive team (known as the Diaz Team) to identify those CAIB report elements with NASA-wide applicability and to develop corrective measures to address each element. One such measure was the development of a standard for the development, documentation, and operation of models and simulations. This report describes the philosophy and requirements overview of the resulting NASA Standard for Models and Simulations.

Blattnig, Steve R.↗
NASA NTRS2009

Generating Code Review Documentation for Auto-Generated Mission-Critical Software

Model-based design and automated code generation are increasingly used at NASA to produce actual flight code, particularly in the Guidance, Navigation, and Control domain. However, since code generators are typically not qualified, there is no guarantee that their output is correct, and consequently auto-generated code still needs to be fully tested and certified. We have thus developed AUTOCERT, a generator-independent plug-in that supports the certification of auto-generated code. AUTOCERT takes a set of mission safety requirements, and formally verifies that the autogenerated code satisfies these requirements. It generates a natural language report that explains why and how the code complies with the specified requirements. The report is hyper-linked to both the program and the verification conditions and thus provides a high-level structured argument containing tracing information for use in code reviews.

Denney, Ewen↗
NASA NTRS1973

Shuttle mission simulator hardware conceptual design report

The detailed shuttle mission simulator hardware requirements are discussed. The conceptual design methods, or existing technology, whereby those requirements will be fulfilled are described. Information of a general nature on the total design problem plus specific details on how these requirements are to be satisfied are reported. The configuration of the simulator is described and the capabilities for various types of training are identified.

Burke, J. F.↗
NASA NTRS1993

Tools reference manual for a Requirements Specification Language (RSL), version 2.0

This report describes a general-purpose Requirements Specification Language, RSL. The purpose of RSL is to specify precisely the external structure of a mechanized system and to define requirements that the system must meet. A system can be comprised of a mixture of hardware, software, and human processing elements. RSL is a hybrid of features found in several popular requirements specification languages, such as SADT (Structured Analysis and Design Technique), PSL (Problem Statement Language), and RMF (Requirements Modeling Framework). While languages such as these have useful features for structuring a specification, they generally lack formality. To overcome the deficiencies of informal requirements languages, RSL has constructs for formal mathematical specification. These constructs are similar to those found in formal specification languages such as EHDM (Enhanced Hierarchical Development Methodology), Larch, and OBJ3.

Fisher, Gene L.↗
NASA NTRS2008

Dimensions of Credibility in Models and Simulations

Based on the National Aeronautics and Space Administration's (NASA's) work in developing a standard for models and simulations (M&S), the subject of credibility in M&S became a distinct focus. This is an indirect result from the Space Shuttle Columbia Accident Investigation Board (CAIB), which eventually resulted in an action, among others, to improve the rigor in NASA's M&S practices. The focus of this action came to mean a standardized method for assessing and reporting results from any type of M&S. As is typical in the standards development process, this necessarily developed into defming a common terminology base, common documentation requirements (especially for M&S used in critical decision making), and a method for assessing the credibility of M&S results. What surfaced in the development of the NASA Standard was the various dimensions credibility to consider when accepting the results from any model or simulation analysis. The eight generally relevant factors of credibility chosen in the NASA Standard proved only one aspect in the dimensionality of M&S credibility. At the next level of detail, the full comprehension of some of the factors requires an understanding along a couple of dimensions as well. Included in this discussion are the prerequisites for the appropriate use of a given M&S, the choice of factors in credibility assessment with their inherent dimensionality, and minimum requirements for fully reporting M&S results.

Steele, Martin J.↗
NASA NTRS1972

A cognitive operating system (COGNOSYS) for JPL's robot, phase 1 report

The most important software requirement for any robot development is the COGNitive Operating SYStem (COGNOSYS). This report describes the Stanford University Artificial Intelligence Laboratory's hand eye software system from the point of view of developing a cognitive operating system for JPL's robot. In this, the Phase 1 of the JPL robot COGNOSYS task the installation of a SAIL compiler and a FAIL assembler on Caltech's PDP-10 have been accomplished and guidelines have been prepared for the implementation of a Stanford University type hand eye software system on JPL-Caltech's computing facility. The alternatives offered by using RAND-USC's PDP-10 Tenex operating sytem are also considered.

Mathur, F. P.↗
NASA NTRS2002

Technology Requirements for Information Management

This report provides the results of a panel study conducted into the technology requirements for information management in support of application domains of particular government interest, including digital libraries, mission operations, and scientific research. The panel concluded that it was desirable to have a coordinated program of R&D that pursues a science of information management focused on an environment typified by applications of government interest - highly distributed with very large amounts of data and a high degree of heterogeneity of sources, data, and users.

Graves, Sara↗
NASA NTRS1992

From Earth to Orbit: An assessment of transportation options

The report assesses the requirements, benefits, technological feasibility, and roles of Earth-to-Orbit transportation systems and options that could be developed in support of future national space programs. Transportation requirements, including those for Mission-to-Planet Earth, Space Station Freedom assembly and operation, human exploration of space, space science missions, and other major civil space missions are examined. These requirements are compared with existing, planned, and potential launch capabilities, including expendable launch vehicles (ELV's), the Space Shuttle, the National Launch System (NLS), and new launch options. In addition, the report examines propulsion systems in the context of various launch vehicles. These include the Advanced Solid Rocket Motor (ASRM), the Redesigned Solid Rocket Motor (RSRM), the Solid Rocket Motor Upgrade (SRMU), the Space Shuttle Main Engine (SSME), the Space Transportation Main Engine (STME), existing expendable launch vehicle engines, and liquid-oxygen/hydrocarbon engines. Consideration is given to systems that have been proposed to accomplish the national interests in relatively cost effective ways, with the recognition that safety and reliability contribute to cost-effectiveness. Related resources, including technology, propulsion test facilities, and manufacturing capabilities are also discussed.

Gavin, Joseph G., Jr.↗
NASA NTRS2001

Evolution of safety-critical requirements post-launch

This paper reports the results of a small study of requirements changes to the onboard software of three spacecraft subsequent to launch. Only those requirement changes that resulted from post-launch anoma-lies (i.e., during operations) were of interest here, since the goal was to better understand the relation-ship between critical anomalies during operations and how safety-critical requirements evolve. The results of the study were surprising in that anomaly-driven, post-launch requirements changes were rarely due to previous requirements having been incorrect. Instead, changes involved new requirements (1) for the software to handle rare events or (2) for the software to compensate for hardware failures or limitations. The prevalence of new requirements as a result of post-launch anomalies suggests a need for increased requirements-engineering support of maintenance activities in these systems. The results also confirm both the difficulty and the benefits of pursuing requirements completeness, especially in terms of fault tolerance, during development of critical systems.

Software requirements↗
NASA NTRS2001

Evolution of safety-critical requirements post-launch

This paper reports the results of a small study of requirements changes to the onboard software of three spacecraft subsequent to launch. Only those requirement changes that resulted from post-launch anomalies (i.e., durring operations) were of interest here, since the goal was to better understand the relationship between critical anomolies during operations and how safety-critical requirements evolve.

requirements↗
NASA NTRS2013

Zelenchukskaya Radio Astronomical Observatory

This report summarizes information about Zelenchukskaya Radio Astronomical Observatory activities in 2012. Last year a number of changes took place in the observatory to improve some technical characteristics and to upgrade some units to the required status. The report provides an overview of current geodetic VLBI activities and gives an outlook for the future.

Smolentsev, Sergey↗
NASA NTRS2013

Svetloe Radio Astronomical Observatory

This report summarizes information about the Svetloe Radio Astronomical Observatory activities in 2012. Last year, a number of changes took place in the observatory to improve some technical characteristics and to upgrade some units to their required status. The report provides an overview of current geodetic VLBI activities and gives an outlook for the future.

Smolentsev, Sergey↗
NASA NTRS2010

NASA Supportability Engineering Implementation Utilizing DoD Practices and Processes

The Ares I design and development program made the determination early in the System Design Review Phase to utilize DoD ILS and LSA approach for supportability engineering as an integral part of the system engineering process. This paper is to provide a review of the overall approach to design Ares-I with an emphasis on a more affordable, supportable, and sustainable launch vehicle. Discussions will include the requirements development, design influence, support concept alternatives, ILS and LSA planning, Logistics support analyses/trades performed, LSA tailoring for NASA Ares Program, support system infrastructure identification, ILS Design Review documentation, Working Group coordination, and overall ILS implementation. At the outset, the Ares I Project initiated the development of the Integrated Logistics Support Plan (ILSP) and a Logistics Support Analysis process to provide a path forward for the management of the Ares-I ILS program and supportability analysis activities. The ILSP provide the initial planning and coordination between the Ares-I Project Elements and Ground Operation Project. The LSA process provided a system engineering approach in the development of the Ares-I supportability requirements; influence the design for supportability and development of alternative support concepts that satisfies the program operability requirements. The LSA planning and analysis results are documented in the Logistics Support Analysis Report. This document was required during the Ares-I System Design Review (SDR) and Preliminary Design Review (PDR) review cycles. To help coordinate the LSA process across the Ares-I project and between programs, the LSA Report is updated and released quarterly. A System Requirement Analysis was performed to determine the supportability requirements and technical performance measurements (TPMs). Two working groups were established to provide support in the management and implement the Ares-I ILS program, the Integrated Logistics Support Working Group (ILSWG) and the Logistics Support Analysis Record Working Group (LSARWG). The Ares I ILSWG is established to assess the requirements and conduct, evaluate analyses and trade studies associated with acquisition logistic and supportability processes and to resolve Ares I integrated logistics and supportability issues. It established a strategic collaborative alliance for coordination of Logistics Support Analysis activates in support of the integrated Ares I vehicle design and development of logistics support infrastructure. A Joint Ares I - Orion LSAR Working Group was established to: 1) Guide the development of Ares-I and Orion LSAR data and serve as a model for future Constellation programs, 2) Develop rules and assumptions that will apply across the Constellation program with regards to the program's LSAR development, and 3) Maintain the Constellation LSAR Style Guide.

Smith, David A.↗