Search NASA⌕ Search

SEARCH · Search NASA

Results for “software concepts”

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 235 records · Page 13

Flight Dynamics Mission Support and Quality Assurance Process

This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

Oh, InHwan↗

The Console in A Briefcase: An Approach to Remote Space Operations

The CIAB (Console in a Briefcase) is conceived as an ISS (International Space Station) Payload Operations remote console that would run via an Internet connection, consisting of components (primarily a laptop PC) that fit into a briefcase, and intended for use from home in an 'on call' scenario. The primary purpose of the CIAB project is to verify that the technology and tools exist to support remote-access payload operations for the International Space Station (ISS) and to build, test, and demonstrate a prototype system. The project can potentially provide cost savings and increased morale to the space operations community by reducing demands on staff. Also, the CIAB project provides a vehicle for examining innovative concepts pertaining to Mission Planning software tools that have potential benefits beyond just the immediate needs of remote access. To date we have implemented and tested the basic capability. Current research is focused on reducing bandwidth demands via the adoption of innovative software solutions. Research into current Internet connectivity and bandwidth is also being pursued.

Heaton, Andy F.↗

FAILSAFE Health Management for Embedded Systems

The FAILSAFE project is developing concepts and prototype implementations for software health management in mission- critical, real-time embedded systems. The project unites features of the industry-standard ARINC 653 Avionics Application Software Standard Interface and JPL s Mission Data System (MDS) technology (see figure). The ARINC 653 standard establishes requirements for the services provided by partitioned, real-time operating systems. The MDS technology provides a state analysis method, canonical architecture, and software framework that facilitates the design and implementation of software-intensive complex systems. The MDS technology has been used to provide the health management function for an ARINC 653 application implementation. In particular, the focus is on showing how this combination enables reasoning about, and recovering from, application software problems.

Horvath, Gregory A.↗

Lander Technologies

Since 2006 NASA has been formulating robotic missions to the lunar surface through programs and projects like the Robotic Lunar Exploration Program, Lunar Precursor Robotic Program, and International Lunar Network. All of these were led by NASA Marshall Space Flight Center (MSFC). Due to funding shortfalls, the lunar missions associated with these efforts, the designs, were not completed. From 2010 to 2013, the Robotic Lunar Lander Development Activity was funded by the Science Mission Directorate (SMD) to develop technologies that would enable and enhance robotic lunar surface missions at lower costs. In 2013, a requirements-driven, low-cost robotic lunar lander concept was developed for the Resource Prospector Mission. Beginning in 2014, The Advanced Exploration Systems funded the lander team and established the MSFC, Johnson Space Center, Applied Physics Laboratory, and the Jet Propulsion Laboratory team with MSFC leading the project. The lander concept to place a 300-kg rover on the lunar surface has been described in the New Technology Report Case Number MFS-33238-1. A low-cost lander concept for placing a robotic payload on the lunar surface is shown in figures 1 and 2. The NASA lander team has developed several lander concepts using common hardware and software to allow the lander to be configured for a specific mission need. In addition, the team began to transition lander expertise to United States (U.S.) industry to encourage the commercialization of space, specifically the lunar surface. The Lunar Cargo Transportation and Landing by Soft Touchdown (CATALYST) initiative was started and the NASA lander team listed above is partnering with three competitively selected U.S. companies (Astrobotic, Masten Space Systems, and Moon Express) to develop, test, and operate their lunar landers.

Chavers, Greg↗

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↗

Reuse at the Software Productivity Consortium

The Software Productivity Consortium is sponsored by 14 aerospace companies as a developer of software engineering methods and tools. Software reuse and prototyping are currently the major emphasis areas. The Methodology and Measurement Project in the Software Technology Exploration Division has developed some concepts for reuse which they intend to develop into a synthesis process. They have identified two approaches to software reuse: opportunistic and systematic. The assumptions underlying the systematic approach, phrased as hypotheses, are the following: the redevelopment hypothesis, i.e., software developers solve the same problems repeatedly; the oracle hypothesis, i.e., developers are able to predict variations from one redevelopment to others; and the organizational hypothesis, i.e., software must be organized according to behavior and structure to take advantage of the predictions that the developers make. The conceptual basis for reuse includes: program families, information hiding, abstract interfaces, uses and information hiding hierarchies, and process structure. The primary reusable software characteristics are black-box descriptions, structural descriptions, and composition and decomposition based on program families. Automated support can be provided for systematic reuse, and the Consortium is developing a prototype reuse library and guidebook. The software synthesis process that the Consortium is aiming toward includes modeling, refinement, prototyping, reuse, assessment, and new construction.

Weiss, David M.↗

The TAVERNS emulator: An Ada simulation of the space station data communications network and software development environment

The Space Station DMS (Data Management System) is the onboard component of the Space Station Information System (SSIS) that includes the computers, networks and software that support the various core and payload subsystems of the Space Station. TAVERNS (Test And Validation Environment for Remote Networked Systems) is a distributed approach for development and validation of application software for Space Station. The TAVERNS concept assumes that the different subsystems will be developed by different contractors who may be geographically separated. The TAVERNS Emulator is an Ada simulation of a TAVERNS on the ASD VAX. The software services described in the DMS Test Bed User's Manual are being emulated on the VAX together with simulations of some of the core subsystems and a simulation of the DCN. The TAVERNS Emulator will be accessible remotely from any VAX that can communicate with the ASD VAX.

Howes, Norman R.↗

Integrated design optimization research and development in an industrial environment

An overview is given of a design optimization project that is in progress at the GE Research and Development Center for the past few years. The objective of this project is to develop a methodology and a software system for design automation and optimization of structural/mechanical components and systems. The effort focuses on research and development issues and also on optimization applications that can be related to real-life industrial design problems. The overall technical approach is based on integration of numerical optimization techniques, finite element methods, CAE and software engineering, and artificial intelligence/expert systems (AI/ES) concepts. The role of each of these engineering technologies in the development of a unified design methodology is illustrated. A software system DESIGN-OPT has been developed for both size and shape optimization of structural components subjected to static as well as dynamic loadings. By integrating this software with an automatic mesh generator, a geometric modeler and an attribute specification computer code, a software module SHAPE-OPT has been developed for shape optimization. Details of these software packages together with their applications to some 2- and 3-dimensional design problems are described.

Kumar, V.↗

First Results from the Mojave Volatiles Prospector (MVP) Field Campaign, a Lunar Polar Rover Mission Analog

The Mojave Volatiles Prospector (MVP) project is a science-driven field program with the goal to produce critical knowledge for conducting robotic exploration of the Moon. MVP will feed science, payload, and operational lessons learned to the development of a real-time, short-duration lunar polar volatiles prospecting mission. MVP achieves these goals through a simulated lunar rover mission to investigate the composition and distribution of surface and subsurface volatiles in a natural and a priori unknown environment within the Mojave Desert, improving our understanding of how to find, characterize, and access volatiles on the Moon. The MVP field site is the Mojave Desert, selected for its low, naturally occurring water abundance. The Mojave typically has on the order of 2-6% water, making it a suitable lunar analog for this field test. MVP uses the Near Infrared and Visible Spectrometer Subsystem (NIRVSS), Neutron Spectrometer Subsystem (NSS), and a downward facing GroundCam camera on the KREX-2 rover to investigate the relationship between the distribution of volatiles and soil crust variation. Through this investigation, we mature robotic in situ instruments and concepts of instrument operations, improve ground software tools for real time science, and carry out publishable research on the water cycle and its connection to geomorphology and mineralogy in desert environments. A lunar polar rover mission is unlike prior space missions and requires a new concept of operations. The rover must navigate 3-5 km of terrain and examine multiple sites in in just ~6 days. Operational decisions must be made in real time, requiring constant situational awareness, data analysis and rapid turnaround decision support tools. This presentation will focus on the first science results and operational architecture findings from the MVP field deployment relevant to a lunar polar rover mission.

Heldmann, Jennifer L.↗

Reconfigurable Software for Mission Operations

We developed software that provides flexibility to mission organizations through modularity and composability. Modularity enables removal and addition of functionality through the installation of plug-ins. Composability enables users to assemble software from pre-built reusable objects, thus reducing or eliminating the walls associated with traditional application architectures and enabling unique combinations of functionality. We have used composable objects to reduce display build time, create workflows, and build scenarios to test concepts for lunar roving operations. The software is open source, and may be downloaded from https:github.comnasamct.

Software engineering↗

Space tug economic analysis study. Volume 2: Tug concepts analysis. Part 1: Overall approach and data generation

An economic analysis of space tug operations is presented. The subjects discussed are: (1) data base for orbit injection stages, (2) data base for reusable space tug, (3) performance equations, (4) data integration and interpretation, (5) tug performance and mission model accomodation, (6) total program cost, (7) payload analysis, (8) computer software, and (9) comparison of tug concepts.

Source record↗

Predicting Numbers of Problems in Development of Software

A method has been formulated to enable prediction of the amount of work that remains to be performed in developing flight software for a spacecraft. The basic concept embodied in the method is that of using an idealized curve (specifically, the Weibull function) to interpolate from (1) the numbers of problems discovered thus far to (2) a goal of discovering no new problems after launch (or six months into the future for software already in use in orbit). The steps of the method can be summarized as follows: 1. Take raw data in the form of problem reports (PRs), including the dates on which they are generated. 2. Remove, from the data collection, PRs that are subsequently withdrawn or to which no response is required. 3. Count the numbers of PRs created in 1-week periods and the running total number of PRs each week. 4. Perform the interpolation by making a least-squares fit of the Weibull function to (a) the cumulative distribution of PRs gathered thus far and (b) the goal of no more PRs after the currently anticipated launch date. The interpolation and the anticipated launch date are subject to iterative re-estimation.

Simonds, Charles H.↗

Systems design and comparative analysis of large antenna concepts

Conceptual designs are evaluated and comparative analyses conducted for several large antenna spacecraft for Land Mobile Satellite System (LMSS) communications missions. Structural configurations include trusses, hoop and column and radial rib. The study was conducted using the Interactive Design and Evaluation of Advanced Spacecraft (IDEAS) system. The current capabilities, development status, and near-term plans for the IDEAS system are reviewed. Overall capabilities are highlighted. IDEAS is an integrated system of computer-aided design and analysis software used to rapidly evaluate system concepts and technology needs for future advanced spacecraft such as large antennas, platforms, and space stations. The system was developed at Langley to meet a need for rapid, cost-effective, labor-saving approaches to the design and analysis of numerous missions and total spacecraft system options under consideration. IDEAS consists of about 40 technical modules efficient executive, data-base and file management software, and interactive graphics display capabilities.

Garrett, L. B.↗

Do Research Software Engineers and Software Engineering Researchers Speak the Same Language?

Anecdotal evidence suggests that research software engineers (RSEs) and software engineering researchers (SERs) often use different terminologies for similar concepts, creating communication challenges. To better understand these divergences, we have started investigating how software engineering fundamentals from the SER community are interpreted within the RSE community, identifying aligned concepts, knowledge gaps, and areas for potential adaptation. In conclusion, our preliminary findings reveal opportunities for mutual learning and collaboration, and our systematic methodology for terminology mapping provides a foundation for a crowdsourced extension and validation in the future.

Kehrer, Timo [Univ. of Bern (Switzerland)] (ORCID:↗

Computers in Aerospace Conference, Los Angeles, Calif., October 31-November 2, 1977, Collection of Technical Papers and Addendum

Papers are presented on such topics as nuclear survivability concepts for airborne computers, military aerospace computer trends, a management approach to acquiring computer systems, software acquisition and verification, and future aerospace digital signal processing concepts. Also considered are CCD architecture for spacecraft SAR image processing, avionics software development for the B-1 aircraft, and software sneak analysis.

Source record↗

Conceptual Design of a 150-Passenger Civil Tiltrotor

The conceptual design of a short-haul civil tiltrotor aircraft is presented. The concept vehicle is designed for runway-independent operations to increase the capacity of the National Airspace System without the need for increased infrastructure. This necessitates a vehicle that is capable of integrating with conventional air traffic without interfering with established flightpaths. The NASA Design and Analysis of Rotorcraft software was used to size the concept vehicle based on the mission requirements of this market. The final configuration was selected based upon performance metrics such as acquisition and maintenance costs, fuel fraction, empty weight, and required engine power. The concept presented herein has a proposed initial operating capability date of 2035, and is intended to integrate with conventional air traffic as well as proposed future air transportation concepts.

150-Passenger↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗

Space Station ground data management system

KSC is planning a Space Station Ground Data Management System (GDMS) for support of functional interface verification, integration and test of Space Station modules and elements. This computer system, planned for initial operational support in 1992, currently is entering a definition and prototyping stage. This paper provides an overview of the GDMS system concept. It synopsizes system functional capabilities, and discusses software and hardware architectural approaches currently under evaluation. It identifies programmatic constraints and their influence upon the concept, as well as specific technical issues planned for study or evaluation via prototyping.

Heuser, Jan↗