The development and technology transfer of software engineering technology at NASA. Johnson Space Center

The United State's big space projects of the next decades, such as Space Station and the Human Exploration Initiative, will need the development of many millions of lines of mission critical software. NASA-Johnson (JSC) is identifying and developing some of the Computer Aided Software Engineering (CASE) technology that NASA will need to build these future software systems. The goal is to improve the quality and the productivity of large software development projects. New trends are outlined in CASE technology and how the Software Technology Branch (STB) at JSC is endeavoring to provide some of these CASE solutions for NASA is described. Key software technology components include knowledge-based systems, software reusability, user interface technology, reengineering environments, management systems for the software development process, software cost models, repository technology, and open, integrated CASE environment frameworks. The paper presents the status and long-term expectations for CASE products. The STB's Reengineering Application Project (REAP), Advanced Software Development Workstation (ASDW) project, and software development cost model (COSTMODL) project are then discussed. Some of the general difficulties of technology transfer are introduced, and a process developed by STB for CASE technology insertion is described

Space Logistics Modeling and Simulation Analysis using SpaceNet: Four Application Cases

The future of space exploration will not be limited to sortie-style missions to single destinations. Even in present exploration taking place at the International Space Station in low-Earth orbit, logistics is complicated by flights arriving from five launch sites on Earth. The future challenges of space logistics given complex campaigns of interconnected missions in deep space will require innovative tools to aid planning and conceptual design. This paper presents a modeling framework to evaluate the propulsive and logistics feasibility of space exploration from the macro-logistics perspective, which covers the delivery of elements and resources to support demands generated during exploration. The modeling framework is implemented in a versatile and unifying software tool, SpaceNet, for general space exploration scenario analysis. Four space exploration scenarios are presented as application cases to highlight the applicability of the framework across vastly different scenarios. The first case investigates the resupply of the International Space Station between 2010 and 2015 using 77 missions combining NASA, European Space Agency, Japanese Space Agency, Russian Space Agency, and commercial space transportation. The second case models a lunar outpost build-up consisting of 17 flights to achieve continuous human presence over eight years. The third case models and evaluates a conceptual sortie-style mission to a near-Earth object, 1999 AO10. Finally, the fourth case models a flexible path type human exploration in the vicinity of Mars using a combination of human and tele-operated exploration. Taken together these cases demonstrate the challenges and logistical requirements of future human space exploration campaigns during the period from 2010-2050 and illustrate the ability of SpaceNet to model and simulate the feasibility of meeting these requirements.United States. Dept. of DefenseUnited States. Air Force Office of Scientific ResearchAmerican Society for Engineering Education. National Defense Science and Engineering Graduate Fellowship32 CFR 168

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V

SET, A SCENARIO EVALUATOR TOOL FOR SUPPORTING SPACE-EXPLORATION MISSION-ARCHITECTURE DESIGN

The design of space-exploration missions begins with a mission statement that defines the ultimate goals of the mission itself. The mission-architecture defines, instead, how the mission will work in practice, and encompasses all the elements that will take part in it. It includes such issues as the synergies of manned and robotic resources, mission control, and the mission timeline. The mission-architecture design activity is an iterative process in general aimed at the maximization of the cost effectiveness (or value) of the mission and minimization of costs. This is performed by successive comparisons and evaluation of the alternative generated mission architectures. The Scenario Evaluator Tool (SET) is conceived to support the engineering team in the framework of the space mission design process. In particular, SET is a simulation software tool that allows building mission architectures with a significant reduction of development time and computational effort. The software allows the characterization, the comparison, and optimization of exploration scenarios and building blocks through a user friendly graphical interface. Each mission-architecture is characterized and evaluated on the basis of the mass budget of the building blocks, cost index and exploration capabilities. SET is general enough to allow the design of several space exploration scenarios for Gap-analysis studies (flexibility). Further, it allows the users to introduce new model libraries (expandability). This paper describes the main features and the potentialities of the simulation software. To show the working principle of SET, a hypothetical human space-exploration mission scenario has been developed and implemented. The results has been accomplished in the framework of STEPS (Systems and Technologies for the ExPloration of Space), which is a research project co-financed by Piedmont Region (Italy), firms and universities of the Piedmont Aerospace District

Integration and validation of embedded flight software on space-qualified multicore architectures

In the recent decades, the importance of software on space missions has notably increased, reflecting the need to integrate advanced on-board functionalities. With multicore processors being lately introduced to host critical high-performance applications, the complexity to validate software has significantly raised with respect to single core architectures. While there has been a big step forward in avionics after the publication of the CAST-32A paper, the ECSS-E-ST-40C software engineering standard used by the European Space Agency (ESA) is still not providing validation support for multicore processors. Hence, it is expected that standardising guidelines to develop software on such platforms will become a recurring topic in the industry to match the demands of future space exploration missions

Simulator of Space Communication Networks

Multimission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) is a suite of software tools that simulates the behaviors of communication networks to be used in space exploration, and predict the performance of established and emerging space communication protocols and services. MACHETE consists of four general software systems: (1) a system for kinematic modeling of planetary and spacecraft motions; (2) a system for characterizing the engineering impact on the bandwidth and reliability of deep-space and in-situ communication links; (3) a system for generating traffic loads and modeling of protocol behaviors and state machines; and (4) a system of user-interface for performance metric visualizations. The kinematic-modeling system makes it possible to characterize space link connectivity effects, including occultations and signal losses arising from dynamic slant-range changes and antenna radiation patterns. The link-engineering system also accounts for antenna radiation patterns and other phenomena, including modulations, data rates, coding, noise, and multipath fading. The protocol system utilizes information from the kinematic-modeling and link-engineering systems to simulate operational scenarios of space missions and evaluate overall network performance. In addition, a Communications Effect Server (CES) interface for MACHETE has been developed to facilitate hybrid simulation of space communication networks with actual flight/ground software/hardware embedded in the overall system

Whitespace Exploration

As engineering systems grow in complexity so too must the design tools that we use evolve and allow for decision makers to efficiently ask questions of their model and obtain meaningful answers. The process of whitespace exploration has recently been developed to aid in engineering design and provide insight into a design space where traditional design exploration methods may fail. In an effort to further the research and development of whitespace exploration algorithms, a software package called Thalia has been created to allow for automated data collection and experimentation with the whitespace exploration methodology. In this work, whitespace exploration is defined and the current state of the art of whitespace exploration algorithms is reviewed. The whitespace exploration library Thalia along with a collection of benchmarking cases are described in detail. A set of experiments on the benchmark cases are run and analyzed to further understand the behavior of the algorithm and outline initial performance results which can later be used for comparison to aid in improving the methodology

Service Oriented Robotic Architecture for Space Robotics: Design, Testing, and Lessons Learned

This paper presents the lessons learned from six years of experiments with planetary rover prototypes running the Service Oriented Robotic Architecture (SORA) developed by the Intelligent Robotics Group (IRG) at the NASA Ames Research Center. SORA relies on proven software engineering methods and technologies applied to space robotics. Based on a Service Oriented Architecture and robust middleware, SORA encompasses on-board robot control and a full suite of software tools necessary for remotely operated exploration missions. SORA has been eld tested in numerous scenarios of robotic lunar and planetary exploration. The experiments conducted by IRG with SORA exercise a large set of the constraints encountered in space applications: remote robotic assets, ight relevant science instruments, distributed operations, high network latencies and unreliable or intermittent communication links. In this paper, we present the results of these eld tests in regard to the developed architecture, and discuss its bene ts and limitations

Ares I-X Flight Test Philosophy

In response to the Vision for Space Exploration, the National Aeronautics and Space Administration (NASA) has defined a new space exploration architecture to return humans to the Moon and prepare for human exploration of Mars. One of the first new developments will be the Ares I Crew Launch Vehicle (CLV), which will carry the Orion Crew Exploration Vehicle (CEV), into Low Earth Orbit (LEO) to support International Space Station (ISS) missions and, later, support lunar missions. As part of Ares I development, NASA will perform a series of Ares I flight tests. The tests will provide data that will inform the engineering and design process and verify the flight hardware and software. The data gained from the flight tests will be used to certify the new Ares/Orion vehicle for human space flight. The primary objectives of this first flight test (Ares I-X) are the following: Demonstrate control of a dynamically similar integrated Ares CLV/Orion CEV using Ares CLV ascent control algorithms; Perform an in-flight separation/staging event between an Ares I-similar First Stage and a representative Upper Stage; Demonstrate assembly and recovery of a new Ares CLV-like First Stage element at Kennedy Space Center (KSC); Demonstrate First Stage separation sequencing, and quantify First Stage atmospheric entry dynamics and parachute performance; and Characterize the magnitude of the integrated vehicle roll torque throughout the First Stage (powered) flight. This paper will provide an overview of the Ares I-X flight test process and details of the individual flight tests

Model Driven Mutation Applied to Adaptative Systems Testing

Dynamically Adaptive Systems modify their behav- ior and structure in response to changes in their surrounding environment and according to an adaptation logic. Critical sys- tems increasingly incorporate dynamic adaptation capabilities; examples include disaster relief and space exploration systems. In this paper, we focus on mutation testing of the adaptation logic. We propose a fault model for adaptation logics that classifies faults into environmental completeness and adaptation correct- ness. Since there are several adaptation logic languages relying on the same underlying concepts, the fault model is expressed independently from specific adaptation languages. Taking benefit from model-driven engineering technology, we express these common concepts in a metamodel and define the operational semantics of mutation operators at this level. Mutation is applied on model elements and model transformations are used to propagate these changes to a given adaptation policy in the chosen formalism. Preliminary results on an adaptive web server highlight the difficulty of killing mutants for adaptive systems, and thus the difficulty of generating efficient tests.Comment: IEEE International Conference on Software Testing, Verification and Validation, Mutation Analysis Workshop (Mutation 2011), Berlin : Allemagne (2011