Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “style guide”

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 NTRS2005

C++ Coding Standards and Style Guide

This document is based on the "C Style Guide" (SEL-94-003). It contains recommendations for C++ implementations that build on, or in some cases replace, the style described in the C style guide. Style guidelines on any topics that are not covered in this document can be found in the "C Style Guide." An attempt has been made to indicate when these recommendations are just guidelines or suggestions versus when they are more strongly encouraged. Using coding standards makes code easier to read and maintain. General principles that maximize the readability and maintainability of C++ are: (1) Organize classes using encapsulation and information hiding techniques. (2) Enhance readability through the use of indentation and blank lines. (3) Add comments to header files to help users of classes. (4) Add comments to implementation files to help maintainers of classes. (5) Create names that are meaningful and readable.

Hughes, Steven↗
NASA NTRS1987

Ada style guide (version 1.1)

Ada is a programming language of considerable expressive power. The Ada Language Reference Manual provides a thorough definition of the language. However, it does not offer sufficient guidance on the appropriate use of Ada's powerful features. For this reason, the Goddard Space Flight Center Ada User's Group has produced this style guide which addresses such program style issues. The guide covers three areas of Ada program style: the structural decomposition of a program; the coding and the use of specific Ada features; and the textural formatting of a program.

Seidewitz, Edwin V.↗
NASA NTRS1994

C style guide

This document discusses recommended practices and style for programmers using the C language in the Flight Dynamics Division environment. Guidelines are based on generally recommended software engineering techniques, industry resources, and local convention. The Guide offers preferred solutions to common C programming issues and illustrates through examples of C Code.

Doland, Jerry↗
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.↗
NASA NTRS1994

Knowledge-based critiquing of graphical user interfaces with CHIMES

CHIMES is a critiquing tool that automates the process of checking graphical user interface (GUI) designs for compliance with human factors design guidelines and toolkit style guides. The current prototype identifies instances of non-compliance and presents problem statements, advice, and tips to the GUI designer. Changes requested by the designer are made automatically, and the revised GUI is re-evaluated. A case study conducted at NASA-Goddard showed that CHIMES has the potential for dramatically reducing the time formerly spent in hands-on consistency checking. Capabilities recently added to CHIMES include exception handling and rule building. CHIMES is intended for use prior to usability testing as a means, for example, of catching and correcting syntactic inconsistencies in a larger user interface.

Jiang, Jianping↗
NASA NTRS1994

Graphical timeline editing

NASA's Experiment Scheduling Program (ESP), which has been used for approximately 12 Spacelab missions, is being enhanced with the addition of a Graphical Timeline Editor. The GTE Clipboard, as it is called, was developed to demonstrate new technology which will lead the development of International Space Station Alpha's Payload Planning System and support the remaining Spacelab missions. ESP's GTE Clipboard is developed in C using MIT's X Windows System X11R5 and follows OSF/Motif Style Guide Revision 1.2.

Meyer, Patrick E.↗
NASA NTRS2023

Human Factors Support for On-Orbit Servicing, Assembly and Manufacturing Mission 1 (OSAM-1)

The NASA Engineering and Safety Center (NESC) Human Factors Technical Discipline Team was requested by the Satellite Servicing Projects Division at Goddard Space Flight Center to provide support in assessing the design of the On-Orbit Servicing, Assembly and Manufacturing Mission 1 (OSAM-1) Mission Operations Center in light of concerns about overcrowding and potential for distractions, as well as assistance in creating a Human-Machine Interface style guide for OSAM-1 user interface design. This report contains the outcome of the NESC assessment.

On-Orbit Servicing, Assembly and Manufacturing Mis↗
NASA NTRS2021

Going Beyond Hooked Participants: The Nibble- and-Drop Framework for Classifying Citizen Science Participation

Many citizen science (CS) programs aim to grow and sustain a pool of enthusiastic participants who consistently contribute their efforts to a specific scientific endeavor. Consequently, much research has explored CS participants’ motivations and their relationship to participant recruitment and retention. However, much of this research has focused on actively participating citizen scientists. If researchers want to elucidate the relationship between participant factors (such as demographics and motivations) and participant retention, it is necessary to develop a more comprehensive picture of the different degrees of participation in CS. This paper presents a framework for classifying participation throughout the participant’s engagement in a CS project/program. We suggest a CS participation model that captures the dynamic nature of participation across an arc of volunteering. Called the Nibble-and-Drop Framework, the model describes multiple exit points and stages of contribution typical of participation in a CS program. Applying the framework to the NASA GLOBE Observer (GO) CS program, we found that it captured the dynamics of participation in a global-scale, mobile, app-based, contributory style CS project. The framework guided our analysis of how different participant factors correlate with degrees of participation. We found that participants were motivated to initially participate because they wanted to contribute to NASA research and science. Participants who dropped out of the program at various points often initially engaged through specific collection events and did not feel the need to continue contributing beyond the event; other drop-outs doubted whether their contributions were meaningful, showing again the need to ensure that participants understand the value of their engagement in a CS project.

Heather Fischer↗
NASA NTRS2009

A Game-Theoretic Approach to Branching Time Abstract-Check-Refine Process

Since the complexity of software systems continues to grow, most engineers face two serious problems: the state space explosion problem and the problem of how to debug systems. In this paper, we propose a game-theoretic approach to full branching time model checking on three-valued semantics. The three-valued models and logics provide successful abstraction that overcomes the state space explosion problem. The game style model checking that generates counter-examples can guide refinement or identify validated formulas, which solves the system debugging problem. Furthermore, output of our game style method will give significant information to engineers in detecting where errors have occurred and what the causes of the errors are.

Wang, Yi↗
NASA NTRS1987

Mobile remote manipulator vehicle system

A mobile remote manipulator system is disclosed for assembly, repair and logistics transport on, around and about a space station square bay truss structure. The vehicle is supported by a square track arrangement supported by guide pins integral with the space station truss structure and located at each truss node. Propulsion is provided by a central push-pull drive mechanism that extends out from the vehicle one full structural bay over the truss and locks drive rods into the guide pins. The draw bar is now retracted and the mobile remote manipulator system is pulled onto the next adjacent structural bay. Thus, translation of the vehicle is inchworm style. The drive bar can be locked onto two guide pins while the extendable draw bar is within the vehicle and then push the vehicle away one bay providing bidirectional push-pull drive. The track switches allow the vehicle to travel in two orthogonal directions over the truss structure which coupled with the bidirectional drive, allow movement in four directions on one plane. The top layer of this trilayered vehicle is a logistics platform. This platform is capable of 369 degees of rotation and will have two astronaut foot restraint platforms and a space crane integral.

Bush, Harold G.↗
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 NTRS1973

Hierarchical hybrid control of manipulators - Artificial intelligence in LSI.

The need for remotely controlled manipulators and explorers, coupled with emerging large-scale integrated (LSI) circuit technology, foreshadow the dominant role of a style of hybrid control. Systems having many degrees of freedom should be guided and regulated by controllers to which commands are given in purpose-oriented form, to be converted into appropriate machine-oriented signals to effectors for achieving the purpose. In particular, numerical tabulations of functions should be replaced by low-level analog microcircuit realizations of the functions, particularly when feedback can keep errors from piling up. The study is concerned with new problems and organizations that arise in attempting to exploit obvious principles to the fullest degree.

Greene, P. H.↗
NASA NTRS1994

SI (Metric) handbook

This guide provides information for an understanding of SI units, symbols, and prefixes; style and usage in documentation in both the US and in the international business community; conversion techniques; limits, fits, and tolerance data; and drawing and technical writing guidelines. Also provided is information of SI usage for specialized applications like data processing and computer programming, science, engineering, and construction. Related information in the appendixes include legislative documents, historical and biographical data, a list of metric documentation, rules for determining significant digits and rounding, conversion factors, shorthand notation, and a unit index.

Artusa, Elisa A.↗
NASA NTRS1973

Programmer's manual for the Mission Analysis Evaluation and Space Trajectory Operations program (MAESTRO)

The Mission Analysis Evaluation and Space Trajectory Operations program known as MAESTRO is described. MAESTRO is an all FORTRAN, block style, computer program designed to perform various mission control tasks. This manual is a guide to MAESTRO, providing individuals the capability of modifying the program to suit their needs. Descriptions are presented of each of the subroutines descriptions consist of input/output description, theory, subroutine description, and a flow chart where applicable. The programmer's manual also contains a detailed description of the common blocks, a subroutine cross reference map, and a general description of the program structure.

Lutzky, D.↗
NASA NTRS1982

A remote computer graphics user at General Motors

The successful use of automotive body surface design data is described. This data has been originally created elsewhere in GM's two large computer graphics systems of CADANCE and Fisher Graphics. As a supplier exterior lighting components, radiator grilles, energy absorbing soft faced bumper systems, and other associated items, Guide has become most dependent on the corporate computer graphics systems to supply accurate car body styling and sheet metal surfacing information for the design of their products. The presentation includes the origin and transfer of design data to a remote user site; its use in the design of their products; and the ultimate production of detailed drawings, N/C punched tapes, and subsequent downstream transfers of detailed part data to a turnkey system for tool design purposes.

Murphy, H. S.↗
NASA NTRS2018

Three Proposed Compendia for Genesis Solar Wind Samples: Science Results, Collector Materials Characterization and Cleaning Techniques

Final Paper and not the abstract is attached. Introduction: Planetary material and cosmochemistry research using Genesis solar wind samples (including the development and implementation of cleaning and analytical techniques) has matured sufficiently that compilations on several topics, if made publically accessible, would be beneficial for researchers and reviewers. We propose here three compendia based on content, organization and source of documents (e.g. published peer-reviewed, published, internal memos, archives). For planning purposes, suggestions are solicited from potential users of Genesis solar wind samples for the type of science content and/or organizational style that would be most useful to them. These compendia are proposed as living documents, periodically updated. Similar to the existing compendia described below, the curation compendia are like library or archival finding aids, they are guides to published or archival documents and should not be cited as primary sources.

Allton, J. H.↗
NASA NTRS2020

Automating Test Consistency

Creating and controlling incredibly complex vehicles such as a rocket requires an unfathomable number of tests. Such tests are necessary to ensure a successful mission and that any issues are caught immediately. Once human lives become involved, the importance of such tests cannot be understated. Often times, however, tests may not be written in a consistent manner and such inconsistencies can lead to slowing down the test-writing process and may even create concerns with the test itself. Because of this, NASA has standards that should be followed by all test writers, but the list of standards is quite long and ensuring that tests follow this perfectly can be challenging. Older tests or tests written by individuals who are unfamiliar with this guide may not be following it which can lead to inconsistencies. To fix this issue, I have taken these human-readable rules and implemented them into an open-source linting program. Linting software is used to automatically check the style of code, and in this case, the tests. In doing so, any rules that the test developer may not have followed will be flagged upon running the software and they can quickly and accurately keep their test consistent with the rules that they are expected to follow.

Software↗
NASA NTRS1982

NASA Publications Guide

The publication programs and management policies of NASA are described and the details that authors and publication specialists need to know to carry out the agency's mission of disseminating the scientific and technical information derived from its activities are highlighted. Topics covered include the various kinds of NASA formal publications; selection of publication medium; printing and distribution; and requirements concerning style and format standards, copyright transfers, the cover, color, and foldouts. The sections of a report are delineated and editorial and page make-up responsibilities are also discussed.

Source record↗