Search NASA⌕ Search

SEARCH · Search NASA

Results for “dictionary”

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 91 records · Page 5

Field-testing the new DECtalk PC system for medical applications

Synthesized human speech has now reached a new level of performance. With the introduction of DEC's new DECtalk PC, the small system developer will have a very powerful tool for creative design. It has been our privilege to be involved in the beta-testing of this new device and to add a medical dictionary which covers a wide range of medical terminology. With the inherent board level understanding of speech synthesis and the medical dictionary, it is now possible to provide full digital speech output for all medical files and terms. The application of these tools will cover a wide range of options for the future and allow a new dimension in dealing with the complex user interface experienced in medical practice.

NASA Discipline Data Analysis↗

XML technology planning database : lessons learned

A hierarchical Extensible Markup Language(XML) database called XCALIBR (XML Analysis LIBRary) has been developed by Millennium Program to assist in technology investment (ROI) analysis and technology Language Capability the New return on portfolio optimization. The database contains mission requirements and technology capabilities, which are related by use of an XML dictionary. The XML dictionary codifies a standardized taxonomy for space missions, systems, subsystems and technologies. In addition to being used for ROI analysis, the database is being examined for use in project planning, tracking and documentation. During the past year, the database has moved from development into alpha testing. This paper describes the lessons learned during construction and testing of the prototype database and the motivation for moving from an XML taxonomy to a standard XML-based ontology.

prototype databases↗

Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Source record↗

Mobilization Protocols for Hybrid Sensors for Environmental AOP Sampling (HySEAS) Observations

The protocols presented here enable the proper mobilization of the latest-generation instruments for measuring the apparent optical properties (AOPs) of aquatic ecosystems. The protocols are designed for the Hybrid Sensors for Environmental AOP Sampling (HySEAS) class of instruments, but are applicable to the community of practice for AOP measurements. The protocols are organized into eleven sections beyond an introductory overview: a) cables and connectors, b) HySEAS instruments, c) platform preparation, d) instrument installation, e) cable installation, f) test deployment, g) test recovery, h) maintenance, i) shipping, j) storage, and k) smallboat operations. Each section concentrates on documenting how to prevent the most likely faults, remedy them should they occur, and accomplishing both with the proper application of a modest set of useful tools. Within the twelve sections, there are Socratic exercises to stimulate thought, and the answers to these exercises appear in Appendix A. Frequently asked questions (FAQs) are summarized in a separate section after the answers to the exercises in Appendix B. For practitioners unfamiliar with the nautical terms used throughout this document plus others likely encountered at sea, an abbreviated dictionary of nautical terms appears in Appendix C. An abbreviated dictionary of radiotelephone terms is presented in Appendix D. To ensure familiarity with many of the tools that are presented, Appendix E provides a description of the tools alongside a thumbnail picture. Abbreviated deployment checklists and cable diagrams are provided in Appendix F. The document concludes with an acknowledgments section, a glossary of acronyms, a definition of symbols, and a list of references.

Mobilizarion↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Planning↗

Benefits and Challenges of Model-based Software Engineering: Lessons Learned based on Qualitative and Quantitative Findings

Even though Model-based Software Engineering (MBSwE) techniques and Autogenerated Code (AGC) have been increasingly used to produce complex software systems, there is only anecdotal knowledge about the state-of-thepractice. Furthermore, there is a lack of empirical studies that explore the potential quality improvements due to the use of these techniques. This paper presents in-depth qualitative findings about development and Software Assurance (SWA) practices and detailed quantitative analysis of software bug reports of a NASA mission that used MBSwE and AGC. The mission’s flight software is a combination of handwritten code and AGC developed by two different approaches: one based on state chart models (AGC-M) and another on specification dictionaries (AGC-D). The empirical analysis of fault proneness is based on 380 closed bug reports created by software developers. Our main findings include: (1) MBSwE and AGC provide some benefits, but also impose challenges. (2) SWA done only at a model level is not sufficient. AGC code should also be tested and the models and AGC should always be kept in-sync. AGC must not be changed manually. (3) Fixes made to address an individual bug report were spread both across multiple modules and across multiple files. On average, for each bug report 1.4 modules, that is, 3.4 files were fixed. (4) Most bug reports led to changes in more than one type of file. The majority of changes to auto-generated source code files were made in conjunction to changes in either file with state chart models or XML files derived from dictionaries. (5) For newly developed files, AGC-M and handwritten code were of similar quality, while AGC-D files were the least fault prone.

Goseva-Popstojanova, Katerina↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for WBS and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Christopher Lewis Sadler↗

Defining the Core Archive Data Standards of the International Planetary Data Alliance (IPDA)

A goal of the International Planetary Data Alliance (lPDA) is to develop a set of archive data standards that enable the sharing of scientific data across international agencies and missions. To help achieve this goal, the IPDA steering committee initiated a six month proj ect to write requirements for and draft an information model based on the Planetary Data System (PDS) archive data standards. The project had a special emphasis on data formats. A set of use case scenarios were first developed from which a set of requirements were derived for the IPDA archive data standards. The special emphasis on data formats was addressed by identifying data formats that have been used by PDS nodes and other agencies in the creation of successful data sets for the Planetary Data System (PDS). The dependency of the IPDA information model on the PDS archive standards required the compilation of a formal specification of the archive standards currently in use by the PDS. An ontology modelling tool was chosen to capture the information model from various sources including the Planetary Science Data Dictionary [I] and the PDS Standards Reference [2]. Exports of the modelling information from the tool database were used to produce the information model document using an object-oriented notation for presenting the model. The tool exports can also be used for software development and are directly accessible by semantic web applications.

ontology↗

Air Traffic Management TestBed Data Exchange Model

The Air Traffic Management (ATM) TestBed is a Platform as a Service that is being developed by the National Aeronautics and Space Administration (NASA) to help design, configure, integrate, run, and monitor air traffic simulations. The platform is designed to provide cloud services including back-end, big-data analytics tools, on-demand computing resource management, data storage, and communication middleware. The ATM TestBed reduces the time to test concepts and technologies, supports interactions among various methods such as human-in-the-loop and automation-in-the-loop simulations, and enables collaborative simulations by sharing technologies and tools in the ATM community. In order to allow easier access to simulation components, TestBed provides a messaging support layer for connectivity using a consistent set of input/output interfaces. In addition, a standard data format is introduced to facilitate communication between the components. The data exchange model, supported in the messaging support layer, standardizes the format of the information to be exchanged among the components. This document describes the messaging data model currently developed in TestBed and provides data dictionaries for references to component developers as well as simulation engineers.

air traffic simulation↗

Synchronization techniques.

Word synchronization techniques, random source and delay methods applied to orthogonal group code dictionaries

ORTHOGONAL FUNCTION↗

An on-line system for hand-printed input

The capability of graphic input/output systems is described. Topics considered are a character recognizer and dictionary building program, an initial flow chart element input program, and a system entitled The Assistant Mathematician, which uses ordinary mathematics to specify numeric computation. All three parts are necessary to allow a user to carry on a mathematical dialogue with the computer in the language and notation of his discipline or problem domain.

Williams, T. G.↗

Computer program for thermodynamic analysis of open cycle multishaft power system with multiple reheat and intercool

A computer program to analyze power systems having any number of shafts up to a maximum of five is presented. On each shaft there can be as many as five compressors and five turbines, along with any specified number of intervening intercoolers and reheaters. A recuperator can be included. Turbine coolant flow can be accounted for. Any fuel consisting entirely of hydrogen and/or carbon can be used. The program is valid for maximum temperatures up to about 2000 K (3600 R). The system description, the analysis method, a detailed explanation of program input and output including an illustrative example, a dictionary of program variables, and the program listing are explained.

Glassman, A. J.↗

Tug fleet and ground operations schedules and controls. Volume 3: Program cost estimates

Cost data for the tug DDT&E and operations phases are presented. Option 6 is the recommended option selected from seven options considered and was used as the basis for ground processing estimates. Option 6 provides for processing the tug in a factory clean environment in the low bay area of VAB with subsequent cleaning to visibly clean. The basis and results of the trade study to select Option 6 processing plan is included. Cost estimating methodology, a work breakdown structure, and a dictionary of WBS definitions is also provided.

Source record↗

Automated storage and retrieval of data obtained in the Interkosmos project

The formation of a data bank and information retrieval system for scientific data is described. The stored data can be digital or documentation data. Data classification methods are discussed along with definition and compilation of the dictionary utilized, definition of the indexing scheme, and definition of the principles used in constructing a file for documents, data blocks, and tapes. Operating principles are also presented.

Ziolkovski, K.↗