Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Software Design”

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 505 records · Page 28

Low cost paths to binary optics

Application of binary optics has been limited to a few major laboratories because of the limited availability of fabrication facilities such as e-beam machines and the lack of standardized design software. Foster-Miller has attempted to identify low cost approaches to medium-resolution binary optics using readily available computer and fabrication tools, primarily for the use of students and experimenters in optical computing. An early version of our system, MacBEEP, made use of an optimized laser film recorder from the commercial typesetting industry with 10 micron resolution. This report is an update on our current efforts to design and build a second generation MacBEEP, which aims at 1 micron resolution and multiple phase levels. Trails included a low cost scanning electron microscope in microlithography mode, and alternative laser inscribers or photomask generators. Our current software approach is based on Mathematica and PostScript compatibility.

Nelson, Arthur↗

Real Time Mars Approach Navigation Aided by the Mars Network

A NASA Mars technology project is described that is building a prototype embedded real time Mars approach navigation capability which can be hosted on the Mars Network's Electra transceiver. The paper motivates the reason for doing real time Mars approach navigation via a set of analyses demonstrating its utility for enabling Mars pin-point landing (< 1-km landing error). The development approach, software design, and test results are discussed. Finally, the way forward towards a flight demonstration on the Mars Science Laboratory is presented.

embedded software↗

A proposed research program in information processing

The goal of the Formalized Software Development (FSD) project was to demonstrate improvements productivity of software development and maintenance through the use of a new software lifecycle paradigm. The paradigm calls for the mechanical, but human-guided, derivation of software implementations from formal specifications of the desired software behavior. It relies on altering a system's specification and rederiving its implementation as the standard technology for software maintenance. A system definition for this paradigm is composed of a behavioral specification together with a body of annotations that control the derivation of executable code from the specification. Annotations generally achieve the selection of certain data representations and/or algorithms that are consistent with, but not mandated by, the behavioral specification. In doing this, they may yield systems which exhibit only certain behaviors among multiple alternatives permitted by the behavioral specification. The FSD project proposed to construct a testbed in which to explore the realization of this new paradigm. The testbed was to provide operational support environment for software design, implementation, and maintenance. The testbed was proposed to provide highly automated support for individual programmers ('programming in the small'), but not to address the additional needs of programming teams ('programming in the large'). The testbed proposed to focus on supporting rapid construction and evolution of useful prototypes of software systems, as opposed to focusing on the problems of achieving production quality performance of systems.

Schorr, Herbert↗

International Space Station (ISS) Risk Reduction Activities

As the assembly of the ISS nears completion, it is worthwhile to step back and review some of the actions pursued by the Program in recent years to reduce risk and enhance the safety and health of ISS crewmembers, visitors, and space flight participants. While the ISS requirements and initial design were intended to provide the best practicable levels of safety, it is always possible to reduce risk -- given the determination and commitment to do so. The following is a summary of some of the steps taken by the ISS Program Manager, by our International Partners, by hardware and software designers, by operational specialists, and by safety personnel to continuously enhance the safety of the ISS. While decades of work went into developing the ISS requirements, there are many things in a Program like the ISS that can only be learned through actual operational experience. These risk reduction activities can be divided into roughly three categories: (1) Areas that were initially noncompliant which have subsequently been brought into compliance or near compliance (i.e., Micrometeoroid and Orbital Debris [MMOD] protection, acoustics) (2) Areas where initial design requirements were eventually considered inadequate and were subsequently augmented (i.e., Toxicity Level 4 materials, emergency hardware and procedures) (3) Areas where risks were initially underestimated, and have subsequently been addressed through additional mitigation (i.e., Extravehicular Activity [EVA] sharp edges, plasma shock hazards) Due to the hard work and cooperation of many parties working together across the span of nearly a decade, the ISS is now a safer and healthier environment for our crew, in many cases exceeding the risk reduction targets inherent in the intent of the original design. It will provide a safe and stable platform for utilization and discovery.

Fodroci, Michael↗

User engineering: A new look at system engineering

User Engineering is a new System Engineering perspective responsible for defining and maintaining the user view of the system. Its elements are a process to guide the project and customer, a multidisciplinary team including hard and soft sciences, rapid prototyping tools to build user interfaces quickly and modify them frequently at low cost, and a prototyping center for involving users and designers in an iterative way. The main consideration is reducing the risk that the end user will not or cannot effectively use the system. The process begins with user analysis to produce cognitive and work style models, and task analysis to produce user work functions and scenarios. These become major drivers of the human computer interface design which is presented and reviewed as an interactive prototype by users. Feedback is rapid and productive, and user effectiveness can be measured and observed before the system is built and fielded. Requirements are derived via the prototype and baselined early to serve as an input to the architecture and software design.

Mclaughlin, Larry L.↗

Long-Term International Space Station (ISS) Risk Reduction Activities

As the assembly of the ISS nears completion, it is worthwhile to step back and review some of the actions pursued by the Program in recent years to reduce risk and enhance the safety and health of ISS crewmembers, visitors, and space flight participants. While the initial ISS requirements and design were intended to provide the best practicable levels of safety, it is always possible to further reduce risk given the determination, commitment, and resources to do so. The following is a summary of some of the steps taken by the ISS Program Manager, by our International Partners, by hardware and software designers, by operational specialists, and by safety personnel to continuously enhance the safety of the ISS, and to reduce risk to all crewmembers. While years of work went into the development of ISS requirements, there are many things associated with risk reduction in a Program like the ISS that can only be learned through actual operational experience. These risk reduction activities can be divided into roughly three categories: Areas that were initially noncompliant which have subsequently been brought into compliance or near compliance (i.e., Micrometeoroid and Orbital Debris [MMOD] protection, acoustics) Areas where initial design requirements were eventually considered inadequate and were subsequently augmented (i.e., Toxicity hazard level-4 materials, emergency procedures, emergency equipment, control of drag-throughs) Areas where risks were initially underestimated, and have subsequently been addressed through additional mitigation (i.e., Extravehicular Activity [EVA] sharp edges, plasma shock hazards). Due to the hard work and cooperation of many parties working together across the span of more than a decade, the ISS is now a safer and healthier environment for our crew, in many cases exceeding the risk reduction targets inherent in the intent of the original design. It will provide a safe and stable platform for utilization and discovery for years to come.

Forroci, Michael P.↗

Real Time Mars Approach Navigation Aided by the Mars Network

A NASA Mars technology project is described that is building a prototype embedded real time Mars approach navigation capability which can be hosted on the Mars Network's Electra transceiver. The paper motivates the reason for doing real time Mars approach navigation via a set of analyses demonstrating its utility for enabling Mars pin-point landing (less than 1-km landing error). The development approach, software design, and test results are discussed. Finally, the way forward towards a flight demonstration on the Mars Science Laboratory (MSL) is presented.

Mars Network↗

Improving the Automatic Inversion of Digital Alouette/ISIS Ionogram Reflection Traces into Topside Electron Density Profiles

The topside sounders of the International Satellites for Ionospheric Studies (ISIS) program were designed as analog systems. The resulting ionograms were displayed on 35 mm film for analysis by visual inspection. Each of these satellites, launched between 1962 and 1971, produced data for 10 to 20 years. A number of the original telemetry tapes from this large data set have been converted directly into digital records. Software, known as the Topside Ionogram Scalar With True-Height (TOPIST) algorithm, has been produced and used for the automatic inversion of the ionogram reflection traces on more than 100,000 ISIS-2 digital topside ionograms into topside vertical electron density profiles Ne(h). Here we present some topside ionospheric solar cycle variations deduced from the TOPIST database to illustrate the scientific benefit of improving and expanding the topside ionospheric Ne(h) database. The profile improvements will be based on improvements in the TOPIST software motivated by direct comparisons between TOPIST profiles and profiles produced by manual scaling in the early days of the ISIS program. The database expansion will be based on new software designed to overcome limitations in the original digital topside ionogram database caused by difficulties encountered during the analog-to-digital conversion process in the detection of the ionogram frame sync pulse and/or the frequency markers. This improved and expanded TOPIST topside Ne(h) database will greatly enhance investigations into both short- and long-term ionospheric changes, e.g., the observed topside ionospheric responses to magnetic storms, induced by interplanetary magnetic clouds, and solar cycle variations, respectively.

Benson, Robert F.↗

Considerations regarding the Use of Computer Vision Machine Learning in Safety-Related or Risk-Significant Applications in Nuclear Power Plants

With the advancements made to date in the field of artificial intelligence (AI), significant potential exists to utilize AI capabilities for nuclear power plant (NPP) applications. AI can replicate human decision making and it is usually faster and more accurate than humans. For implementations that impact critical NPP applications (e.g., safety-related or non-safety systems that potentially affect overall plant risk), a deeper safety analysis of the AI methods is necessary. AI applied to NPP operations could resemble the use of digital I&C (DI&C) because such applications involve digital computer hardware and custom-designed software that input plant data, execute complex software algorithms, and output the results to a system or licensed human operator to potentially provoke an action. For AI methods to be compliant with current safety requirements for DI&C, AI compatibility must be evaluated, and AI-related gaps may exist that prevent the prompt deployment of AI in NPPs. This effort aims to evaluate how example AI technologies align with the DI&C safety framework, and discusses how they could be analyzed, modeled, tested, and validated in a manner similar to typical DI&C technologies. Because AI is a broad field that encompasses areas such as machine learning (ML), natural language processing, and computer vision, this research focused on a subset of methods categorized as the computer vision ML (CVML) methods. This report explores two CVML use cases, gauge reading and fire watch, considered relevant to the DI&C standards, as they could play a safety-critical role. For the gauge reading use case, a CVML-enabled technology that can read gauges at oblique angles is utilized. For the fire watch use case, a CVML-enabled technology is utilized that migrates fire watch from a manual (human) approach to automated fire detection. These use cases are mainly intended to give context to the CVML system discussion. This effort assumes the worst-case scenario, with the CVML system being used to replace a safety-related or risk-significant system, thus requiring evaluation. Evaluating CVML against most of the relevant safety requirements for DI&C yielded several CVML-specific considerations due to the uniqueness of its characteristics in comparison with typical DI&C systems. For example, CVML models often employ commonly used (open-source) datasets, and it is not always possible to determine the level of overlap among open-source datasets. Therefore, the independence of the developed CVML models when demonstrating diversity is questionable, therefore creating vulnerability to common cause failure (CCF). The design verification process is also impacted since the data overlap could result in overestimation of the software validation and verification (V&V) performance results. Section 2 of this report evaluates a list of the identified CVML-specific characteristics and discusses the resulting considerations and potential solutions in the context of each referenced requirement. A summation is provided in Section 3. This report is not to be used as a guideline. It was developed to identify and consider issues in the implementation of ML technologies used to augment activities that may have a bearing on plant operation. The report draws parallels to the use of DI&C technologies, for which many standards are available to guide their use in nuclear plant operation. It considers the technologies and some of the potential implications of their use in safety-related applications but is not intended to address regulatory or licensing related issues.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Tools to aid the specification and design of flight software, appendix B

The tasks that are normally performed during the specification and architecture design stages of software development are identified. Ways that tools could perform, or aid the performance, of such tasks are also identified. Much of the verification and analysis that is suggested is currently rarely performed during these early stages, but it is believed that this analysis should be done as early as possible so as to detect errors as early as possible.

Bristow, G.↗

Design of an interactive accounting tutor

A project to design an interactive program to teach accounting techniques is described. The four major goals of the project are discussed and a review of the literature on teaching machines and computer-assisted-instruction is included. The system is implemented on the CTSS time sharing system at M.I.T. and uses an ARDS graphic display. The software design of the system is described in detail. A typical session with the tutor is also described. Appendices include complete system documentation.

Macko, J.↗

Suppression of Transient Events by Levitation (STABLE): Results From the USML-2 Mission

Microgravity science payloads can be extremely sensitive to vibrations from machinery, acoustics, ventilation, and crew activity. Suppression of Transient Acceleration by Levitation (STABLE) is an active vibration isolation system designed to protect payloads from these disturbances. This paper gives an account of results from the flight demonstration of the STABLE microgravity isolation system, which was developed and successfully flight tested in orbit during USML-2, with the participation of Astronaut Fred Leslie. Following a very brief description of the operational principles, the hardware and software design, and performance criteria, results of the analysis of measured flight data are presented to provide an evaluation of system performance parameters, including acceleration attenuation, assessment of sway space, system power consumption, and other factors critical to the performance of an isolation system. Lessons learned and potential design improvements and evolutions are discussed. Data reduction by Robert Boucher of McDonnell Douglas Aerospace (MDA) was substantially assisted by Kenneth Hrovat of Tal-Cut, Inc., under support from National Aeronautics and Space Administration/Lewis Research Center (LeRC), Cleveland, OH.

Nurre, Gerald S.↗

Reliability Assessment Of Conceptual Launch Vehicles

Planning is underway for new NASA missions to the moon and to MARS. These missions carry a great deal of risk, as the Challenger and Columbia accidents demonstrate. In order to minimize the risks to the crew and the mission, risk reduction must be done at every stage, not only in quality manufacturing, but also in design. It is necessary, therefore, to be able to compare the risks posed in different launch vehicle designs. Further, these designs have not yet been implemented, so it is necessary to compare these risks without being able to test the vehicles themselves. This paper will discuss some of the issues involved in this type of comparison. It will start with a general discussion of reliability estimation. It will continue with a short look at some software designed to make this estimation easier and faster. It will conclude with a few recommendations for future tools.

Bloomer, Lisa A.↗

An open, parallel I/O computer as the platform for high-performance, high-capacity mass storage systems

APTEC Computer Systems is a Portland, Oregon based manufacturer of I/O computers. APTEC's work in the context of high density storage media is on programs requiring real-time data capture with low latency processing and storage requirements. An example of APTEC's work in this area is the Loral/Space Telescope-Data Archival and Distribution System. This is an existing Loral AeroSys designed system, which utilizes an APTEC I/O computer. The key attributes of a system architecture that is suitable for this environment are as follows: (1) data acquisition alternatives; (2) a wide range of supported mass storage devices; (3) data processing options; (4) data availability through standard network connections; and (5) an overall system architecture (hardware and software designed for high bandwidth and low latency). APTEC's approach is outlined in this document.

Abineri, Adrian↗

Towards a Theory for Integration of Mathematical Verification and Empirical Testing

From the viewpoint of a project manager responsible for the V&V (verification and validation) of a software system, mathematical verification techniques provide a possibly useful orthogonal dimension to otherwise standard empirical testing. However, the value they add to an empirical testing regime both in terms of coverage and in fault detection has been difficult to quantify. Furthermore, potential cost savings from replacing testing with mathematical verification techniques cannot be realized until the tradeoffs and synergies can be formulated. Integration of formal verification with empirical testing is also difficult because the idealized view of mathematical verification providing a correctness proof with total coverage is unrealistic and does not reflect the limitations imposed by computational complexity of mathematical techniques. This paper first describes a framework based on software reliability and formalized fault models for a theory of software design fault detection - and hence the utility of various tools for debugging. It then describes a utility model for integrating mathematical and empirical techniques with respect to fault detection and coverage analysis. It then considers the optimal combination of black-box testing, white-box (structural) testing, and formal methods in V&V of a software system. Using case studies from NASA software systems, it then demonstrates how this utility model can be used in practice.

Lowry, Michael↗

Spectator Proton Detection and Reconstruction in Deep Inelastic D(E,EPS) Scattering

A Radial Time Projection Chamber (RTPC) was designed and installed in Jefferson Lab's Hall B as part of the BONuS12 (Barely Off-shell Nucleon Structure) experiment. The goal of BONuS12 is to accurately measure the structure function of the neutron by scattering 11 GeV electrons and detecting them with the CLAS12 spectrometer. Deuterium gas was used as an effective neutron target, and the new RTPC was used to detect low momentum spectator protons. Protons follow a curved path in the 5 Tesla solenoid that is part of CLAS12, ionizing the He-CO2 gas in an annular drift region surrounding the target. These ionization electrons are radially drifted outwards, amplified using cylindrical GEM (Gaseous Electron Multiplication) foils and recorded using readout pads located along the entire outer face of the cylindrical detector. The particle track reconstruction software discussed in detail in this thesis uses the signals from these pads to build tracks, which are reconstructed into the drift region using the arrival times of the signals and the positions of the pads. The proton momentum is measured from the track?s curvature and thus used to extract information about the struck neutron. This thesis introduces the theory of spectator tagging as an effective strategy for measuring neutron structure, by minimizing nuclear effects in the absence of a free neutron target. Along with discussing the many detectors that make up the CLAS12 spectrometer, the RTPC will be covered in detail, along with the tracking software designed to interpret the electronic signals to rebuild the low-momentum particle tracks, and fit them to extract the relevant kinematics. The results of the software, and preliminary analysis will be shown in the final chapter, as well as the discussion of possible improvements which could be made to the tracking software.

Payette, David↗

Urban Air Mobility Fleet Manager Gap Analysis and System Design

NASA’s Urban Air Mobility (UAM) Sub-Project is engaged in re-search to facilitate the introduction of air taxis into the US National Airspace System. Given the history of conventional aircraft operations, it is clear that dispatcher support will be required for UAM. This paper presents a gap analysis, system requirements, and a workstation design concept for the UAM dispatcher or Fleet Manager (FM) position. The gap analysis focuses on the differences be-tween the tasks of the airline dispatcher and those projected for the FM. FM system capabilities and data requirements are then presented as foundations for soft-ware development. An initial user interface concept is provided. The FM software uses a single, large display. The system supports prediction, monitoring, and task execution. This paper is intended to support FM software design for future air taxi systems.

Richard Mogford↗

Creating and Testing Simulation Software

The goal of this project is to learn about the software development process, specifically the process to test and fix components of the software. The paper will cover the techniques of testing code, and the benefits of using one style of testing over another. It will also discuss the overall software design and development lifecycle, and how code testing plays an integral role in it. Coding is notorious for always needing to be debugged due to coding errors or faulty program design. Writing tests either before or during program creation that cover all aspects of the code provide a relatively easy way to locate and fix errors, which will in turn decrease the necessity to fix a program after it is released for common use. The backdrop for this paper is the Spaceport Command and Control System (SCCS) Simulation Computer Software Configuration Item (CSCI), a project whose goal is to simulate a launch using simulated models of the ground systems and the connections between them and the control room. The simulations will be used for training and to ensure that all possible outcomes and complications are prepared for before the actual launch day. The code being tested is the Programmable Logic Controller Interface (PLCIF) code, the component responsible for transferring the information from the models to the model Programmable Logic Controllers (PLCs), basic computers that are used for very simple tasks.

Heinich, Christina M.↗