SEARCH · Engineering Papers

Results for “documentation”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 109 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRS2020

Development of VBA Tool for Document Term Search

Employees throughout different agencies such as NASA, have identified that the search of determined terms/words through documents, consume substantial research time of such. These types of searches are substantially limited towards one word in a one document identification; forward one, these usual types of searches lack efficiency & optimization through research aspects of work. Consequently, this reflects in the decrease productivity during work hours etc. The application of VBA (Visual Basic for Applications) is the programming language of Excel, which was conducted for the development of optimized tool for document term search. The project enables the search of single & multiple word/term search through single format documents for paragraph data extraction.

Ssytems Development↗

NASA NTRS2020

KSC Integration Office Documentation and Support

This report details the process of document management within the KSC Integration Office throughout my internship in the fall term of the year 2020. During this term, I was mentored by Felix A. Soto-Toro and my main objective was to support the Audit Liaison Representatives (ALR) in their documentation processes. I worked alongside the members of the KSC Integration Office to streamline the auditing process in order to facilitate the interchangement of documents and communication between auditors and our agency. My approach to this situation was to document the events of each audit in a report, which would be updated weekly every Monday following a specific format. As support I was required to gather, organize, and release data relevant to current audits in an online server for ALRs to use across the entire NASA Agency.

Ana C Arvelo Serrano↗

NASA NTRS2023

Exploration Systems Development Mission Directorate (ESDMD) Moon-to-Mars Architecture Definition Document

There are many opportunities in executing the ambitious Moon-to-Mars efforts through an integrated architecture. NASA addresses this in its Moon-to-Mars Strategy and Objectives Development2 document (hereafter referred to as the M2M Strategy). Many of these opportunities involve establishing a system engineering framework that can support the breadth of necessary program and system contributions. By applying these needs to nearer-term lunar development, NASA will be instituting the process, procedures, and techniques needed to enable longer-term Mars goals and more. Some of the challenges being addressed in the M2M Strategy are associated with the architecture definition and include broad/changing goals, funding, and external pressures/influences. This document and the methodology outlined for architecture definition have been crafted to contend with these using an iterative and adaptable framework. The primary purpose of the Architecture Definition Document (ADD) is to capture the methodology, organization, and decomposition necessary to translate the broad objectives outlined in the M2M Strategy into functions and use cases that can be allocated to implementable programs and projects. Inherent in this process will be the need to communicate the long-term vision, maintain traceability to responsible parties, and iterate on the architectural implementation as innovations and solutions develop. This document will be updated and improved in conjunction with the Architecture Concept Review (ACR) which will be held annually to help unify the Agency and to get buy-in and input from across the Agency on the human exploration architecture. The annual nature of the process provides the opportunity to continually incorporate new developments in technologies and new partnerships, whether they be with industry, the U.S. Government, international entities, or academia.

Moon-to-Mars Strategy↗

NASA NTRSDate not supplied

Document Classification Techniques for Aviation Letters of Agreement

Often when working with technical documents, it is helpful to classify them into specific categories. In this paper, we conduct a thorough review of natural language processing techniques to perform this classification task on Letters of Agreement (LOAs), technical aviation documents outlining rules for utilizing US airspace. We evaluate multiple techniques, including Transfer Learning, for representing the text in the documents as embeddings: unigram and bigram Term Frequency Inverse Document Frequency (TFIDF), Word2Vec, Doc2Vec, GloVe and RoBERTa. We investigate a wide range of classification models: K-Nearest Neighbors, Random Forest, Support Vector Machines (SVM), Logistic Regression, Naive Bayes, Feed-Forward Neural Network, Convolutional Neural Networks (CNNs) and Long-Short Term Memory (LSTM). By comparing the different methods, we found the best overall approach for our task was to use unigram TFIDF representations with SVM while also gaining insight into how the other methodologies performed on a small technical datasets.

Aayushi Batra↗

NASA NTRSDate not supplied

Document Classification Techniques for Aviation Letters of Agreement

Often when working with historic air traffic management (ATM) documents, it is helpful to classify them into specific categories. In this paper, we conduct a thorough review of natural language processing techniques to perform this classification task on Letters of Agreement (LOAs), technical aviation documents outlining rules for utilizing US airspace. We evaluate multiple techniques for representing the text in the documents as embeddings: unigram and bigram Term Frequency Inverse Document Frequency (TFIDF), Word2Vec, Doc2Vec, GloVe and RoBERTa. We investigate a wide range of classification models: K-Nearest Neighbors, Random Forest, Support Vector Machines (SVM), Logistic Regression, Naive Bayes, Feed-Forward Neural Network, Convolutional Neural Networks (CNNs) and Long-Short Term Memory (LSTM). By comparing the different methods, we found the best overall approach for our task was to use unigram TFIDF representations with SVM while also gaining insight into how the other methodologies performed on a small technical datasets.

ATM↗

NASA NTRSDate not supplied

Document Classification Techniques for Aviation Letters of Agreement

ATM↗

NASA NTRSDate not supplied

Enhancing accessibility and usability of Algorithm Theoretical Basis Documents through the Algorithm Publication Tool

Effective communication of scientific theories is crucial for transforming raw instrument data into valuable Earth observation products. The NASA Earth science data community disseminates this knowledge through Algorithm Theoretical Basis Documents (ATBDs). Historically, these documents lacked a standardized format, were designed for human readability rather than machine interpretation, and were challenging to locate due to the absence of a centralized repository. The Algorithm Publication Tool (APT) transforms how ATBD content is presented, simplifying the processes of creating, updating, and locating these documents. APT offers authors the option to use its user-friendly cloud-based interface or standardized templates for ATBD development. The primary advantage of the interface is its capability to manage the entire ATBD creation process within a single environment, ensuring comprehensive tracking of all activities and facilitating user tasks. Conversely, the use of standardized ATBD templates allows users to create documents using familiar tools like Google Docs, Microsoft Word, or Overleaf for LaTeX. APT also provides a centralized repository, enabling easy search and discovery of published ATBDs. This presentation showcases APT's functionalities, illustrates its contributions to advancing open science, and highlights potential benefits for broader community adoption.

Bradley Baker↗

NASA NTRS2024

Exploration Systems Development Mission Directorate: Moon to Mars Architecture Definition Document

The National Aeronautics and Space Administration (NASA) explores the unknown in air and space, innovates for the benefit of humanity, and inspires the world through discovery. Extending the reach of humanity through the human exploration of the Moon, Mars, and beyond is key to that mission. NASA’s Moon to Mars Strategy and Objectives document establishes long-term goals and objectives for crewed deep space exploration; however, satisfying NASA’s Moon to Mars Objectives requires an innovative approach to the definition, management, and execution of NASA’s Moon to Mars Architecture. An architecture offers a high-level unifying structure and defines a system. It provides rules, guidelines, and constraints that define a cohesive and coherent framework that identifies constituent parts, relationships, and connections and establishes how those parts fit and work together. This Architecture Definition Document (ADD) establishes the process for the decomposition of objectives empowers the agency’s success in achieving human exploration of the cosmos. NASA updates this document annually to reflect the maturation of the architecture and the progress NASA and partners make toward achieving exploration objectives. The ADD is not a manifest or requirements document. Instead, it serves as a tool for the programs, projects, and engineers who will implement and execute NASA’s bold ambitions for crewed exploration of deep space. As established in the Moon to Mars Strategy and Objectives, “Why” we explore encompasses three pillars: Science, Inspiration, and National Posture. Ensuring success in all three areas requires an architectural approach that incorporates innovation, collaboration, and partnerships that can be sustained across a multi-decadal effort. This second revision (Rev-B) of the ADD, developed to support NASA’s 2024 Architecture Concept Review (ACR), incorporates several key updates to support the continued evolution of the architecture. Since the last revision of the ADD, NASA has significantly improved the clarity of the objective decomposition, which distills exploration objectives into the characteristics and needs and use cases and functions needed to achieve them. The updated decomposition incorporates findings from internal studies and diverse stakeholder feedback. A model-based systems engineering approach ensures coherence and consistency, removing inconsistency and repetition. Revision B also incorporates advancements to NASA’s Mars architecture, including insight into initial capabilities, systems, and operations necessary to support the Humans to Mars segment. Updates to objective decomposition for Mars add significant detail to the ADD and hint at areas of forward work and future study. An appendix adds greater depth in the future decisions needed for Mars that will drive lunar needs. They are not the only decisions to be made, but they will have huge effects on subsequent decisions. NASA continues to introduce new exploration systems into the architecture. Two new elements — initial surface habitat and lunar surface cargo lander—successfully passed mission concept review in 2024 as a result of extensive analysis, concept refinement, and studies. These elements and their respective reference missions appear in this revision. NASA also continues to apply architecture processes to cross-agency efforts and coordination with external stakeholders by including definitions of architecture technology gaps — essential areas for engagement across and beyond the agency. The technology gaps appendix identifies areas that need attention and innovation to enable future exploration. In publishing this information, NASA communicates the technologies and capabilities that may benefit from partnership with industry, academia, other U.S. government agencies, and international space agencies. Ultimately, NASA established the Moon to Mars Architecture approach to communicate and facilitate humanity’s journey into the universe according to the principles and recurring tenets of NASA’s Moon to Mars Strategy and Objectives. The NASA architecture team thanks their many stakeholders, participants, and partners for their efforts to review and provide feedback. Their support has been critical to the success of this approach.

Elements↗

NASA NTRS1972

Program documentation standards

A style manual is presented to serve as a reference and guide for system and program documentation. It is intended to set standards for documentation, prescribing the procedures to be followed, format to be used, and information to be produced. The standards for program documentation specify the extent to which the programmer should support his efforts in writing. The first three sections of the manual (system, program, and operation descriptions) contain information of particular interest to management, operators, and program users, respectively. Each section was designed as a self-sufficient description from the management, operator, or user point of view.

Parker, D. A.↗

NASA NTRS1970

Views on computer program documentation and automation

Various aspects of the problem of program documentation and description are discussed. Particular emphasis is placed on the problem of semantics. It is pointed out that the information produced by documentation of a program, if presented to several different groups, may mean entirely different things to these groups. Recognition of the fact that people look at problems differently is proposed as a more practical approach to the problem of documentation rather than extensive use of standards or strict formatting. The difficulties involved in searching for ways to provide a common ground for the transmission and use of information are discussed.

Grosch, H. R.↗

NASA NTRS1970

Making automated computer program documentation a feature of total system design

It is pointed out that in large-scale computer software systems, program documents are too often fraught with errors, out of date, poorly written, and sometimes nonexistent in whole or in part. The means are described by which many of these typical system documentation problems were overcome in a large and dynamic software project. A systems approach was employed which encompassed such items as: (1) configuration management; (2) standards and conventions; (3) collection of program information into central data banks; (4) interaction among executive, compiler, central data banks, and configuration management; and (5) automatic documentation. A complete description of the overall system is given.

Wolf, A. W.↗

NASA NTRS1970

COSMIC program documentation experience

A brief history of COSMIC as it relates to the handling of program documentation is summarized; the items that are essential for computer program documentation are also discussed. COSMIC documentation and program standards handbook is appended.

Kalar, M. C.↗

NASA NTRS1970

Program analysis for documentation

A program analysis for documentation (PAD) written in FORTRAN has three steps: listing the variables, describing the structure and writing the program specifications. Technical notes on editing criteria for reviewing program documentation, technical notes for PAD, and FORTRAN program analyzer for documentation are appended.

Lolmaugh, G. H.↗

NASA NTRS1970

A scan processor as an aid to program documentation

Program documentation was separated into two catagories: documentation for program use and documentation for program analysis, modification, or extension. The symbol scanner, flow chart production subsystem, decision table subsystem, and scan processor are also described.

Oliver, P.↗

NASA NTRS1974

NSSDC and WDC-A-R and S document availability and distribution services

The documents available from the National Space Science Data Center and the World Data Center A for Rockets and Satellites are described. The availability, costs, ordering procedures for documents presently available, and the procedures for obtaining future documents are given.

Source record↗

NASA NTRS1976

Standard classification of software documentation

General conceptual requirements for standard levels of documentation and for application of these requirements to intended usages. These standards encourage the policy to produce only those forms of documentation that are needed and adequate for the purpose. Documentation standards are defined with respect to detail and format quality. Classes A through D range, in order, from the most definitive down to the least definitive, and categories 1 through 4 range, in order, from high-quality typeset down to handwritten material. Criteria for each of the classes and categories, as well as suggested selection guidelines for each are given.

Tausworthe, R. C.↗

NASA NTRS1976

NASA/ESA CV-990 Spacelab simulation. Appendixes: C, data-handling: Planning and implementation; D, communications; E, mission documentation

Data handling, communications, and documentation aspects of the ASSESS mission are described. Most experiments provided their own data handling equipment, although some used the airborne computer for backup, and one experiment required real-time computations. Communications facilities were set up to simulate those to be provided between Spacelab and the ground, including a downlink TV system. Mission documentation was kept to a minimum and proved sufficient. Examples are given of the basic documents of the mission.

Reller, J. O., Jr.↗

NASA NTRS1977

Software design and documentation language

A communications medium to support the design and documentation of complex software applications is studied. The medium also provides the following: (1) a processor which can convert design specifications into an intelligible, informative machine reproducible document; (2) a design and documentation language with forms and syntax that are simple, unrestrictive, and communicative; and (3) methodology for effective use of the language and processor.

Kleine, H.↗