SEARCH · Search NASA
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.
This paper discusses how the CCSDS flight dynamics standards have been implemented in the AMMOS/MDN software, and how they facilitate the provision of a multimission, multiagency operations environment.
This document summarizes the change reports for the ATD-2 V3.1.x series of software releases to Charlotte-Douglas International Airport (CLT). These list all the changes since the previous release. The Release Notes for Distribution are meant to be more readable by stakeholders. [Includes updates to changes for RTC (Ramp Traffic Console), Scheduler, STBO (Surface Trajectory-Based Operations), and Surface Metering Display (graphical-user interface, GUI) clients.]
This document summarizes the software releases and capabilities delivered to CLT and/or DFW during the ATD-2 Phase 2 field evaluation.
Presentation is an update to the Core Flight Software (CFS) Change Control Board (CCB) and other interested parties on the state of the Software Bus Networking (SBN) application.
No abstract available
This document summarizes the 5.x series of ATD-2 software releases to Charlotte-Douglas International Airport (CLT) and/or Dallas-Fort Worth International Airport (DFW) during ATD-2 Phase 3.
Explore the source record for details and available documents.
This document summarizes the 5.x series of ATD-2 software releases to Charlotte-Douglas International Airport (CLT) and/or Dallas-Fort Worth International Airport (DFW) during ATD-2 Phase 3. This is Version 2 of the document that provides updates since the original document was released in August 2020.
This document summarizes the 6.x series of ATD-2 software releases to Dallas-Fort Worth International Airport (DFW) during ATD-2 Phase 3.
No abstract provided
Explore the source record for details and available documents.
Software system for on-line analyses of linear network circuits
Software system permits onsite direct control of logistics operations, which include spare parts, initial installation, tool control, and repairable parts status and control, through all facets of operations. System integrates logistics actions and controls receipts, issues, loans, repairs, fabrications, and modifications and assets in predicting and allocating logistics parts and services effectively.
The Interactive Software Invocation System (ISIS), which allows a user to build, modify, control, and process a total flight software system without direct communications with the host computer, is described. This interactive data management system provides the user with a file manager, text editor, a tool invoker, and an Interactive Programming Language (IPL). The basic file design of ISIS is a five level hierarchical structure. The file manager controls this hierarchical file structure and permits the user to create, to save, to access, and to purge pages of information. The text editor is used to manipulate pages of text to be modified and the tool invoker allows the user to communicate with the host computer through a RUN file created by the user. The IPL is based on PASCAL and contains most of the statements found in a high-level programming language. In order to evaluate the effectiveness of the system as applied to a flight project, the collection of software components required to support the Annular Suspension and Pointing System (ASPS) flight project were integrated using ISIS. The ASPS software system and its integration into ISIS is described.
Within the last decade better reliability models (hardware. software, system) than those currently used have been theorized and developed but not implemented in practice. Previous research on software reliability has shown that while some existing software reliability models are practical, they are no accurate enough. New paradigms of development (e.g. OO) have appeared and associated reliability models have been proposed posed but not investigated. Hardware models have been extensively investigated but not integrated into a system framework. System reliability modeling is the weakest of the three. NASA engineers need better methods and tools to demonstrate that the products meet NASA requirements for reliability measurement. For the new models for the software component of the last decade, there is a great need to bring them into a form that they can be used on software intensive systems. The Statistical Modeling and Estimation of Reliability Functions for Systems (SMERFS'3) tool is an existing vehicle that may be used to incorporate these new modeling advances. Adapting some existing software reliability modeling changes to accommodate major changes in software development technology may also show substantial improvement in prediction accuracy. With some additional research, the next step is to identify and investigate system reliability. System reliability models could then be incorporated in a tool such as SMERFS'3. This tool with better models would greatly add value in assess in GSFC projects.