SEARCH · Engineering Papers
Results for “Software Process”
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.
AFRC Core Simulation Overview
Overview of the AFRC Core Simulation Framework and Software Engineering processes. This is a common technology used for advance programming of multi-threaded applications such as the core simulation.
Model-Based Prognostics of Hybrid Systems
Model-based prognostics has become a popular approach to solving the prognostics problem. However, almost all work has focused on prognostics of systems with continuous dynamics. In this paper, we extend the model-based prognostics framework to hybrid systems models that combine both continuous and discrete dynamics. In general, most systems are hybrid in nature, including those that combine physical processes with software. We generalize the model-based prognostics formulation to hybrid systems, and describe the challenges involved. We present a general approach for modeling hybrid systems, and overview methods for solving estimation and prediction in hybrid systems. As a case study, we consider the problem of conflict (i.e., loss of separation) prediction in the National Airspace System, in which the aircraft models are hybrid dynamical systems.
6DOF Testing of the SLS Inertial Navigation Unit
The Navigation System on the NASA Space Launch System (SLS) Block 1 vehicle performs initial alignment of the Inertial Navigation System (INS) navigation frame through gyrocompass alignment (GCA). Because the navigation architecture for the SLS Block 1 vehicle is a purely inertial system, the accuracy of the achieved orbit relative to mission requirements is very sensitive to initial alignment accuracy. The assessment of this sensitivity and many others via simulation is a part of the SLS Model-Based Design and Model-Based Requirements approach. As a part of the aforementioned, 6DOF Monte Carlo simulation is used in large part to develop and demonstrate verification of program requirements. To facilitate this and the GN&C flight software design process, an SLS-Program-controlled Design Math Model (DMM) of the SLS INS was developed by the SLS Navigation Team. The SLS INS model implements all of the key functions of the hardware-namely, GCA, inertial navigation, and FDIR (Fault Detection, Isolation, and Recovery)-in support of SLS GN&C design requirements verification. Despite the strong sensitivity to initial alignment, GCA accuracy requirements were not verified by test due to program cost and schedule constraints. Instead, the system relies upon assessments performed using the SLS INS model. In order to verify SLS program requirements by analysis, the SLS INS model is verified and validated against flight hardware. In lieu of direct testing of GCA accuracy in support of requirement verification, the SLS Navigation Team proposed and conducted an engineering test to, among other things, validate the GCA performance and overall behavior of the SLS INS model through comparison with test data. This paper will detail dynamic hardware testing of the SLS INS, conducted by the SLS Navigation Team at Marshall Space Flight Center's 6DOF Table Facility, in support of GCA performance characterization and INS model validation. A 6-DOF motion platform was used to produce 6DOF pad twist and sway dynamics while a simulated SLS flight computer communicated with the INS. Tests conducted include an evaluation of GCA algorithm robustness to increasingly dynamic pad environments, an examination of GCA algorithm stability and accuracy over long durations, and a long-duration static test to gather enough data for Allan Variance analysis. Test setup, execution, and data analysis will be discussed, including analysis performed in support of SLS INS model validation.
Technologies and Methods Used at the Laboratory for Atmospheric and Space Physics (LASP) to Serve Solar Irradiance Data
The Laboratory for Atmospheric and Space Physics (LASP) at the University of Colorado in Boulder, USA operates the Solar Radiation and Climate Experiment (SORCE) NASA mission, as well as several other NASA spacecraft and instruments. Dozens of Solar Irradiance data sets are produced, managed, and disseminated to the science community. Data are made freely available to the scientific immediately after they are produced using a variety of data access interfaces, including the LASP Interactive Solar Irradiance Datacenter (LISIRD), which provides centralized access to a variety of solar irradiance data sets using both interactive and scriptable/programmatic methods. This poster highlights the key technological elements used for the NASA SORCE mission ground system to produce, manage, and disseminate data to the scientific community and facilitate long-term data stewardship. The poster presentation will convey designs, technological elements, practices and procedures, and software management processes used for SORCE and their relationship to data quality and data management standards, interoperability, NASA data policy, and community expectations.
New Results from Galileo's First Flyby of Ganymede: Reconnection-Driven Flows at the Low-Latitude Magnetopause Boundary, Crossing the Cusp, and Icy Ionospheric Escape
On 27 June 1996, the NASA Galileo spacecraft made humanity’s first flyby of Jupiter’s largest moon, Ganymede, discovering that it is the only moon known to possess an internally generated magnetic field. Resurrecting the original Galileo Plasma Subsystem (PLS) data analysis software, we processed the raw PLS data from G01 and for the first time present the properties of plasmas encountered. Entry into the magnetosphere of Ganymede occurred near the confluence of the magnetopause and plasma sheet. Reconnection-driven plasma flows were observed (consistent with an Earth-like Dungey cycle), which may be a result of reconnection in the plasma sheet, magnetopause, or might be Ganymede’s equivalent of a Low-Latitude Boundary Layer. Dropouts in plasma density combined with velocity perturbations afterward suggest that Galileo briefly crossed the cusps into closed magnetic field lines. Galileo then crossed the cusps, where field-aligned precipitating ions were observed flowing down into the surface, at a location consistent with observations by the Hubble Space Telescope. The density of plasma outflowing from Ganymede jumped an order of magnitude around closest approach over the north polar cap. The abrupt increase may be a result of crossing the cusp or may represent an altitude-dependent boundary such as an ionopause. More diffuse, warmer field-aligned outflows were observed in the lobes. Fluxes of particles near the moon on the nightside were significantly lower than on the dayside, possibly resulting from a diurnal cycle of the ionosphere and/or neutral atmosphere.
Simulation and Flight Test Environments for the TASAR Traffic Aware Planner
The Traffic Aware Planner (TAP) software is a flight deck decision support tool that enhances the flight crew’s ability to make flight-optimizing route change requests while airborne. The software provides conflict-free, optimized trajectory suggestions during en route flight to produce time- and fuel-savings compared to the current trajectory. The TAP software requires evaluation in an operational environment with real pilot users to validate projected benefits. To this end, a set of developmental test environments have been developed to mature the software and mitigate technical risk prior to entering operational evaluation. The unique attributes of each test environment were leveraged to provide a range of purpose- and case-dependent TAP software tests. This paper describes the elements of a testing environment, discusses several environments of varying fidelity used to test the TAP software, and provides a review of two case studies highlighting the vital role testing played in the TAP software development process.
Integrated System for Autonomous and Adaptive Caretaking (ISAAC): Phase 1 Low-Fidelity Demo
This presentation describes the ISAAC phase 1 low-fidelity demonstration results. The demonstration satisfied the milestone from the Gateway-ISAAC Memorandum of Understanding to "Demonstrate spatial and logical data registration between robotics and spacecraft". It integrated many new ISAAC components, including a spatially linked model, Astrobee multi-sensor mapping, and an integrated data interface. It advanced ISAAC key performance parameters related to mapping, in a lab setting. Areas for phase 1 forward work include: improve maturity toward the high-fidelity demo on the ISS; demonstrate mapping with more sensor modalities; expand initial anomaly detection implementation into a flexible framework with multiple detection algorithms for different tasks; begin open source software release process for releasable ISAAC components.
Causal Modeling and Event-driven Simulation for Monitoring of Continous Systems
Monitoring of complex continous physical systems has been traditionally accomplished in computer-based process control software by one or both of the following methods: 1) establishing limit checks for sensors and raising an alarm whenever a sensor's value crosses one of these thresholds, and 2) comparing predicted values from a simulation to actual sensor values and flagging discrepancies.
Integrated Handling Qualities Safety Analysis For Conceptual Design of Urban Air Mobility Vehicles
The recent emergence of distributed electric propulsion Vertical Takeoff and Landing (VTOL) aircraft has created a rapid introduction of new design concepts with unique stability and control characteristics. A challenge to realizing the full potential of these vehicles for urban transportation is to gain public acceptance which is largely driven by flight safety. This paper describes ongoing research to address the feasibility of integrating flying qualities safety metrics into conceptual design of VTOL Urban Air Mobility (UAM) vehicles. The discussion is composed of the approach and progress toward a toolbox that integrates with existing NASA rotorcraft design software and processes. Several key challenges are highlighted including modeling requirements for failures, identification of critical failures, and capturing critical failures, with robustness to model uncertainty. A discussion of requirements for safety metrics, specific to UAM vehicles, as well as the effects of the control system design is also included. Results to date have demonstrated the degradation in flying qualities metrics due to propulsion failures.
The Core Flight System (cFS): NASA Quality Flight Software to Power Science and Exploration Available to the World
The presentation is planned to be a continuation of two previous discussions completed at the FSW Workshop regarding the cFS Test Framework (CTF) and Engineering Data Sheets (EDS). The presentation will also cover the latest advancements in cFS, including: 1. Quick into to cFS 2. An overview of our software release process + Git repo 3. Release of EDS files for the cFE + open-source apps 4. Overview of how to independently verify EDS files using CTF + what they can be used for. 5. Future plans for cFS. This presentation complements the talk on configuration management of distributed cFS repos, to be presented by Tam Ngo from Johnson Space Center.
Plant Habitat Telemetry / Command Interface and E-MIST
Plant Habitat (PH) is an experiment to be taken to the International Space Station (ISS) in 2016. It is critical that ground support computers have the ability to uplink commands to control PH, and that ISS computers have the ability to downlink PH telemetry data to ground support. This necessitates communication software that can send, receive, and process, PH specific commands and telemetry. The objective of the Plant Habitat Telemetry/ Command Interface is to provide this communication software, and to couple it with an intuitive Graphical User Interface (GUI). Initial investigation of the project objective led to the decision that code be written in C++ because of its compatibility with existing source code infrastructures and robustness. Further investigation led to a determination that multiple Ethernet packet structures would need to be created to effectively transmit data. Setting a standard for packet structures would allow us to distinguish these packets that would range from command type packets to sub categories of telemetry packets. In order to handle this range of packet types, the conclusion was made to take an object-oriented programming approach which complemented our decision to use the C++ programming language. In addition, extensive utilization of port programming concepts was required to implement the core functionality of the communication software. Also, a concrete understanding of a packet processing software was required in order to put aU the components of ISS-to-Ground Support Equipment (GSE) communication together and complete the objective. A second project discussed in this paper is Exposing Microbes to the Stratosphere (EMIST). This project exposes microbes into the stratosphere to observe how they are impacted by atmospheric effects. This paper focuses on the electrical and software expectations of the project, specifically drafting the printed circuit board, and programming the on-board sensors. The Eagle Computer-Aided Drafting (CAD) software was used to draft the E-MIST circuit. This required several component libraries to be created. Coding the sensors and obtaining sensor data involved using the Arduino Uno developmental board and coding language, and properly wiring peripheral sensors to the microcontroller (the central control unit of the experiment).
Streamlining Software Aspects of Certification: Report on the SSAC Survey
The aviation system now depends on information technology more than ever before to ensure safety and efficiency. To address concerns about the efficacy of software aspects of the certification process, the Federal Aviation Administration (FAA) began the Streamlining Software Aspects of Certification (SSAC) program. The SSAC technical team was commissioned to gather data, analyze results, and propose recommendations to maximize efficiency and minimize cost and delay, without compromising safety. The technical team conducted two public workshops to identify and prioritize software approval issues, and conducted a survey to validate the most urgent of those issues. The SSAC survey, containing over two hundred questions about the FAA's software approval process, reached over four hundred industry software developers, aircraft manufacturers, and FAA designated engineering representatives. Three hundred people responded. This report presents the SSAC program rationale, survey process, preliminary findings, and recommendations.
WISE: Automated support for software project management and measurement
One important aspect of software development and IV&V is measurement. Unless a software development effort is measured in some way, it is difficult to judge the effectiveness of current efforts and predict future performances. Collection of metrics and adherence to a process are difficult tasks in a software project. Change activity is a powerful indicator of project status. Automated systems that can handle change requests, issues, and other process documents provide an excellent platform for tracking the status of the project. A World Wide Web based architecture is developed for (a) making metrics collection an implicit part of the software process, (b) providing metric analysis dynamically, (c) supporting automated tools that can complement current practices of in-process improvement, and (d) overcoming geographical barrier. An operational system (WISE) instantiates this architecture allowing for the improvement of software process in a realistic environment. The tool tracks issues in software development process, provides informal communication between the users with different roles, supports to-do lists (TDL), and helps in software process improvement. WISE minimizes the time devoted to metrics collection, analysis, and captures software change data. Automated tools like WISE focus on understanding and managing the software process. The goal is improvement through measurement.
Expert system verification and validation study. Delivery 3A and 3B: Trip summaries
Key results are documented from attending the 4th workshop on verification, validation, and testing. The most interesting part of the workshop was when representatives from the U.S., Japan, and Europe presented surveys of VV&T within their respective regions. Another interesting part focused on current efforts to define industry standards for artificial intelligence and how that might affect approaches to VV&T of expert systems. The next part of the workshop focused on VV&T methods of applying mathematical techniques to verification of rule bases and techniques for capturing information relating to the process of developing software. The final part focused on software tools. A summary is also presented of the EPRI conference on 'Methodologies, Tools, and Standards for Cost Effective Reliable Software Verification and Validation. The conference was divided into discussion sessions on the following issues: development process, automated tools, software reliability, methods, standards, and cost/benefit considerations.
Modular digital holographic fringe data processing system
A software architecture suitable for reducing holographic fringe data into useful engineering data is developed and tested. The results, along with a detailed description of the proposed architecture for a Modular Digital Fringe Analysis System, are presented.
Application of industry-standard guidelines for the validation of avionics software
The application of industry standards to the development of avionics software is discussed, focusing on verification and validation activities. It is pointed out that the procedures that guide the avionics software development and testing process are under increased scrutiny. The DO-178A guidelines, Software Considerations in Airborne Systems and Equipment Certification, are used by the FAA for certifying avionics software. To investigate the effectiveness of the DO-178A guidelines for improving the quality of avionics software, guidance and control software (GCS) is being developed according to the DO-178A development method. It is noted that, due to the extent of the data collection and configuration management procedures, any phase in the life cycle of a GCS implementation can be reconstructed. Hence, a fundamental development and testing platform has been established that is suitable for investigating the adequacy of various software development processes. In particular, the overall effectiveness and efficiency of the development method recommended by the DO-178A guidelines are being closely examined.
Software Design Improvements: Software Quality and the Design and Inspection Process - Part 2
The application of assurance engineering techniques improves the duration of failure-free performance of software. The totality of features and characteristics of a software product are what determine its ability to satisfy customer needs. Software in safety-critical systems is very important to NASA. We follow the System Safety Working Groups definition for system safety software as: 'The optimization of system safety in the design, development, use and maintenance of software and its integration with safety-critical systems in an operational environment. 'If it is not safe, say so' has become our motto. This paper goes over methods that have been used by NASA to make software design improvements by focusing on software quality and the design and inspection process.