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.

SourceResearch connectionFrom yearThrough year

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

At least 19 records

All sources NASA NTRS DOE 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↗

DOE OSTI2026

Human-system Interface Style Guide for ACORN Control System

The purpose of this style guide is to provide a clear, consistent framework for the design and development of human system interfaces (HSIs) used throughout the Fermilab accelerator complex. It establishes a shared visual and interaction foundation to ensure that interfaces remain intuitive, effective, and cohesive, regardless of when or by whom they are developed. By adhering to these guidelines, developers can avoid introducing unnecessary deviations that compromise usability or increase system training burden. This consistency is especially critical in long-term, multi-contributor projects where interface continuity and maintainability are paramount. This document serves as a practical reference for all HSI development activities related to the accelerator control environment. While the guidance provided is comprehensive, it is not exhaustive of every potential design scenario. As such, the style guide is intended to function as a living document, subject to regular review and revision. Updates will be made at least annually to incorporate emerging best practices, operational feedback, and evolving system needs. Areas where detailed guidance is still under development are clearly indicated in gray throughout the document and will be addressed in future revisions according to project priorities.

Hill, Rachael [Idaho Natl. Lab.] (ORCID:0000000263↗

DOE OSTI2023

Human-System Interface Style Guide for ACORN Digital Control System

The purpose of this style guide is to assist developers in designing effective and consistent-looking user interfaces for accelerator control rooms. A similar purpose is to help developers avoid the creation of user interfaces that needlessly stray from the accepted standard set forth in this document. This way, all interfaces combined will look congruous. This is especially beneficial for development that spans multiple years by many different contributors. This document is intended as a ready reference source for all user interface design for the Fermilab accelerator complex.

43 PARTICLE ACCELERATORS↗

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.↗

DOE OSTI2020

Human-System Interface Design Review Guidelines

The U.S. Nuclear Regulatory Commission (NRC) staff reviews the human factors engineering (HFE) aspects of nuclear power plants in accordance with the Standard Review Plan (NUREG-0800, Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants: LWR Edition). The Human Factors Engineering Program Review Model (NUREG-0711, Revision 3, issued November 2012) contains detailed design review procedures. As part of the review process, the interfaces between plant personnel and the plant's systems and components are evaluated for conformance with HFE guidelines. This document, Human-System Interface Design Review Guidelines (NUREG-0700, Revision 3), provides the guidelines necessary to perform this evaluation. The review guidelines address the physical and functional characteristics of human-system interfaces (HSIs). Because these guidelines only address the HFE aspects of design and not other related considerations, such as instrumentation and control and structural design, they are referred to as HFE guidelines. In addition to the review of actual HSIs, the NRC staff can use the NUREG-0700 guidelines to evaluate a design-specific HFE guidelines document or style guide. The HFE guidelines are organized into four basic parts, which are divided into sections. Part I contains guidelines for the basic HSI elements: information displays, user-interface interaction and management, and analog displays and controls. These elements are used as building blocks to develop HSI systems to serve specific functions. Part II contains the guidelines for reviewing the following HSI systems: alarm system, safety parameter display system, group-view display system, soft control system, computer-based procedure system, automation system, and communication system. Part III provides guidelines for the review of workstations and workplaces. Part IV provides guidelines for the review of HSI support (i.e., maintainability of digital systems and degraded HSI and instrumentation and control conditions).

42 ENGINEERING↗

DOE OSTI2022

Design Philosophy for Accelerator Control Rooms

43 PARTICLE ACCELERATORS↗

DOE OSTI2022

Design Philosophy for Accelerator Control Rooms

This report describes the foundational human factors principles needed to design user interfaces for accelerator control rooms. These principles are presented as recommendations for accelerator control system interface design and are illustrated with examples drawn from accelerator operations at Fermi National Accelerator Laboratory (Fermilab). These high-level principles are intended to serve as design objectives that apply generally across all control system interfaces developed for the accelerator complex. This design philosophy document is a high-level roadmap to approach the general interface design for the accelerator complex. This philosophy applies state-of-the-art human factors principles and evidence-based design standards to an accelerator environment, which will transform the next era of accelerator interfaces as outlined by the Accelerator Controls Operations Research Network (ACORN) Project. Further work will include mapping the general design principles included in this report to more specific guidance in the form of a user interface style guide.

43 PARTICLE ACCELERATORS↗

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↗

DOE OSTI2021

Design & Brand Guidelines (V.1.03)

The goal is to revitalize the Lab’s identity so that it reflects a focused and forward-looking approach to solving national security challenges. This goal is achieved through design that is dynamic, accessible, and optimized for 21st century communications.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

DOE OSTI2020

Introduction to FLAG

The following guide is a tutorial-style introduction to the free Lagrange (FLAG) hydrocode for anyone who wants to get started with or learn more about FLAG.

97 MATHEMATICS AND COMPUTING↗

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.↗

DOE OSTI2021

Integrating Advanced Modeling and Accelerated Testing for a Modernized Fuel Qualification Paradigm

With the increasing interest in sodium fast reactor technology, as seen by applications to the U.S. Nuclear Regulatory Commission for the OKLO Aurora plant, fuel testing for the TerraPower Traveling Wave Reactor, and the impending construction and startup of the versatile test reactor (VTR), a modernized, accelerated approach to fuel qualification is needed. To guide this effort, a Phenomena Identification Ranking Table–styled analysis was performed for a U-Pu-Zr sodium-free annular fuel system. This analysis evaluated a series of fuel design properties and parameters against their contributions to key fuel performance phenomena. The resulting priority parameters were then reviewed against existing modeling and experimental capabilities to support investigation of the highest-priority parameters. A pathway for qualification was then established using highthroughput, high-volume experiments from MiniFuel and FAST in parallel with advanced physics-based model development. This effort outlines how the first stages of qualification can be reduced from the typical 20+-year development cycle to 5 to 7 years by deploying accelerated irradiation testing platforms. As with any accelerated test, these methods are prototypic in some aspects and less so in others; however, by coupling with advanced fuel performance modeling and simulation capabilities, the larger space of irradiation parameters and material response provided offers advantages for the validation of physics-based models supporting the deployment of novel fuel designs. As a test case, this paper utilizes a proposed Mark II fuel system for the upcoming VTR. Thus, an accelerated qualification method can be tested for the development of MARK II driver fuel so that by the time of VTR startup, lead test assemblies for a Mark II fuel can be initiated.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗