Search NASA⌕ Search

SEARCH · Search NASA

Results for “agile,”

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 433 records · Page 24

Understanding and Evaluating Assurance Cases

Assurance cases are a method for providing assurance for a system by giving an argument to justify a claim about the system, based on evidence about its design, development, and tested behavior. In comparison with assurance based on guidelines or standards (which essentially specify only the evidence to be produced), the chief novelty in assurance cases is provision of an explicit argument. In principle, this can allow assurance cases to be more finely tuned to the specific circumstances of the system, and more agile than guidelines in adapting to new techniques and applications. The first part of this report (Sections 1-4) provides an introduction to assurance cases. Although this material should be accessible to all those with an interest in these topics, the examples focus on software for airborne systems, traditionally assured using the DO-178C guidelines and its predecessors. A brief survey of some existing assurance cases is provided in Section 5. The second part (Section 6) considers the criteria, methods, and tools that may be used to evaluate whether an assurance case provides sufficient confidence that a particular system or service is fit for its intended use. An assurance case cannot provide unequivocal "proof" for its claim, so much of the discussion focuses on the interpretation of such less-than-definitive arguments, and on methods to counteract confirmation bias and other fallibilities in human reasoning.

Rushby, John↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the software community. This paper discusses the findings and TR suite informing the FM domain in best practices for FM architectural design, visibility observations, and methods employed for IV&V and mission assurance.

Fitz, Rhonda↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IVV) Program, with Software Assurance Research Program support, extracted FM architectures across the IVV portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IVV projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management.

Fitz, Rhonda↗

Armstrong Flight Research Center Research Technology and Engineering Report 2015

I am honored to endorse the 2015 Neil A. Armstrong Flight Research Center’s Research, Technology, and Engineering Report. The talented researchers, engineers, and scientists at Armstrong are continuing a long, rich legacy of creating innovative approaches to solving some of the difficult problems and challenges facing NASA and the aerospace community.Projects at NASA Armstrong advance technologies that will improve aerodynamic efficiency, increase fuel economy, reduce emissions and aircraft noise, and enable the integration of unmanned aircraft into the national airspace. The work represented in this report highlights the Center’s agility to develop technologies supporting each of NASA’s core missions and, more importantly, technologies that are preparing us for the future of aviation and space exploration.We are excited about our role in NASA’s mission to develop transformative aviation capabilities and open new markets for industry. One of our key strengths is the ability to rapidly move emerging techniques and technologies into flight evaluation so that we can quickly identify their strengths, shortcomings, and potential applications.This report presents a brief summary of the technology work of the Center. It also contains contact information for the associated technologists responsible for the work. Don’t hesitate to contact them for more information or for collaboration ideas.

flight research↗

Using Modern Methodologies with Maintenance Software

Jet Propulsion Laboratory uses multi-mission software produced by the Mission Planning and Sequencing (MPS) team to process, simulate, translate, and package the commands that are sent to a spacecraft. MPS works under the auspices of the Multi-Mission Ground Systems and Services (MGSS). This software consists of nineteen applications that are in maintenance. The MPS software is classified as either class B (mission critical) or class C (mission important). The scheduling of tasks is difficult because mission needs must be addressed prior to performing any other tasks and those needs often spring up unexpectedly. Keeping track of the tasks that everyone is working on is also difficult because each person is working on a different software component. Recently the group adopted the Scrum methodology for planning and scheduling tasks. Scrum is one of the newer methodologies typically used in agile development. In the Scrum development environment, teams pick their tasks that are to be completed within a sprint based on priority. The team specifies the sprint length usually a month or less. Scrum is typically used for new development of one application. In the Scrum methodology there is a scrum master who is a facilitator who tries to make sure that everything moves smoothly, a product owner who represents the user(s) of the software and the team. MPS is not the traditional environment for the Scrum methodology. MPS has many software applications in maintenance, team members who are working on disparate applications, many users, and is interruptible based on mission needs, issues and requirements. In order to use scrum, the methodology needed adaptation to MPS. Scrum was chosen because it is adaptable. This paper is about the development of the process for using scrum, a new development methodology, with a team that works on disparate interruptible tasks on multiple software applications.

Scrum↗

Evolution of the Scope and Capabilities of Uplink Support Software for Mars Surface Operations

In January of 2004 both of the Mars Exploration Rover spacecraft landed safely, initiating daily surface operations at the Jet Propulsion Laboratory for what was anticipated to be approximately three months of mobile exploration. The longevity of this mission, still ongoing after ten years, has provided not only a tremendous return of scientific data but also the opportunity to refine and improve the methodology by which robotic Mars surface missions are commanded. Since the landing of the Mars Science Laboratory spacecraft in August of 2012, this methodology has been successfully applied to operate a Martian rover which is both similar to, and quite different from, its predecessors. For MER and MSL, daily uplink operations can be most broadly viewed as converting the combined interests of both the science and engineering teams into a spacecraft-safe set of transmittable command files. In order to accomplish these ends a discrete set of mission-critical software tools were developed which not only allowed for conformation to established JPL standards and practices but also enabled innovative technologies specific to each mission. Although these primary programs provided the requisite capabilities for meeting the high-level goals of each distinct phase of the uplink process, there was little in the way of secondary software to support the smooth flow of data from one phase to the next. In order to address this shortcoming a suite of small software tools was developed to aid in phase transitions, as well as to automate some of the more laborious and error-prone aspects of uplink operations. This paper describes the evolution of this software suite, from its initial attempts to merely shorten the duration of the operator's shift, to its current role as an indispensable tool enforcing workflow of the uplink operations process and agilely responding to the new and unexpected challenges of missions which can, and have, lasted many years longer than originally anticipated.

CoUGAR↗

NextGen Far-Term Concept Exploration for Integrated Gate-to-Gate Trajectory-Based Operations

NASA is currently conducting concept exploration studies toward the definition of a far-term, gate-to-gate concept for Trajectory-Based Operations. This paper presents a basic architectural framework for the far-term concept and discusses some observations about implementation of trajectory-based operations in the National Airspace System. Within the concept, operators and service providers collaboratively negotiate aircraft trajectories, providing agile, optimized, aircraft-specific routing to meet service provider gate-to-gate flow-management constraints and increasing capacity by smoothly and effectively combining flight-deck-based and ground-based metering, merging, and spacing in a mixed-equipage environment. The far-term TBO concept is intended to influence the direction of mid-term TBO research and to inform the definition of stable requirements and standards for TBO communications infrastructure and user equipage.

Johnson, Sally C.↗

AFSPC Innovation and Science and Technology Outreach to Industry and Academia

The U.S. Air Force is taking a strategic approach to ensuring that we are at the cutting edge of science and technology. This includes fostering game-changing approaches and technologies that are balanced with operational needs. The security of the Nation requires a constant pursuit of science, technical agility, and a rapid adoption of innovation. This includes pursuits of game-changing technologies and domains that perhaps we cannot even imagine today. This paper highlights the Air Force Space Command (AFSPC) collaboration and outreach to other government agencies, military and national laboratories, industry, and academia on long term science and technology challenges. In particular we discuss the development of the AFSPC Long Term Science and Technology Challenges that include both space and cyberspace operations within a multi-domain environment and the subsequent Innovation Summits.

Science Technology S&T Forum↗

Non-Maximally Decimated Filter Banks Enable Adaptive Frequency Hopping for Unmanned Aircraft Vehicles

In the last few years, radio technologies for unmanned aircraft vehicle (UAV) have advanced very rapidly. The increasing need to fly unmanned aircraft systems (UAS) in the national airspace system (NAS) to perform missions of vital importance to national security, defense, and science has pushed ahead the design and implementation of new radio platforms. However, a lot still has to be done to improve those radios in terms of performance and capabilities. In addition, an important aspect to account for is hardware cost and the feasibility to implement these radios using commercial off-the-shelf (COTS) components. UAV radios come with numerous technical challenges and their development involves contributions at different levels of the design. Cognitive algorithms need to be developed in order to perform agile communications using appropriate frequency allocation while maintaining safe and efficient operations in the NAS and, digital reconfigurable architectures have to be designed in order to ensure a prompt response to environmental changes. Command and control (C2) communications have to be preserved during "standard" operations while crew operations have to be minimized. It is clear that UAV radios have to be software-defined systems, where size, weight and power consumption (SWaP) are critical parameters. This paper provides preliminary results of the efforts performed to design a fully digital radio architecture as part of a NASA Phase I STTR. In this paper, we will explain the basic idea and technical principles behind our dynamic/adaptive frequency hopping radio for UAVs. We will present our Simulink model of the dynamic FH radio transmitter design for UAV communications and show simulation results and FPGA system analysis.

UAV↗

Automation of Flight Software Regression Testing

NASA is developing the Space Launch System (SLS) to be a heavy lift launch vehicle supporting human and scientific exploration beyond earth orbit. SLS will have a common core stage, an upper stage, and different permutations of boosters and fairings to perform various crewed or cargo missions. Marshall Space Flight Center (MSFC) is writing the Flight Software (FSW) that will operate the SLS launch vehicle. The FSW is developed in an incremental manner based on "Agile" software techniques. As the FSW is incrementally developed, testing the functionality of the code needs to be performed continually to ensure that the integrity of the software is maintained. Manually testing the functionality on an ever-growing set of requirements and features is not an efficient solution and therefore needs to be done automatically to ensure testing is comprehensive. To support test automation, a framework for a regression test harness has been developed and used on SLS FSW. The test harness provides a modular design approach that can compile or read in the required information specified by the developer of the test. The modularity provides independence between groups of tests and the ability to add and remove tests without disturbing others. This provides the SLS FSW team a time saving feature that is essential to meeting SLS Program technical and programmatic requirements. During development of SLS FSW, this technique has proved to be a useful tool to ensure all requirements have been tested, and that desired functionality is maintained, as changes occur. It also provides a mechanism for developers to check functionality of the code that they have developed. With this system, automation of regression testing is accomplished through a scheduling tool and/or commit hooks. Key advantages of this test harness capability includes execution support for multiple independent test cases, the ability for developers to specify precisely what they are testing and how, the ability to add automation, and the ability of the harness and cases to be executed continually. This test concept is an approach that can be adapted to support other projects.

Tashakkor, Scott B.↗

Precision Pointing for the Wide-Field Infrared Survey Telescope (WFIRST)

The Wide-Field Infrared Survey Telescope (WFIRST) mission, scheduled for a mid-2020's launch, is currently in its definition phase. The mission is designed to investigate essential questions in the areas of dark energy, exoplanets, and infrared astrophysics. WFIRST will use a 2.4-meter primary telescope (same size as the Hubble Space Telescope's primary mirror) and two instruments: the Wide Field Instrument (WFI) and the Coronagraph Instrument (CGI). In order to ad-dress the critical science requirements, the WFIRST mission will conduct large-scale surveys of the infrared sky, requiring both agility and precision pointing (11.6 milli-arcsec stability, 14 milli-arcsec jitter). This paper describes some of the challenges this mission profile presents to the GNC subsystem, and some of the design elements chosen to accommodate those challenges. The high-galactic-latitude survey is characterized by 3-minute observations separated by slews ranging from 0.025 deg to 0.8 deg. The need for observation efficiency drives the slew and settle process to be as rapid as possible. A description of the shaped slew profile chosen to minimize excitation of structural oscillation, and the handoff from star tracker-gyro control to fine guidance sensor control is detailed. Also presented is the fine guidance sensor (FGS), which is integral with the primary instrument (WFI). The FGS is capable of tracking up to 18 guide stars, enabling robust FGS acquisition and precision pointing. To avoid excitation of observatory structural jitter, reaction wheel speeds are operationally maintained within set limits. In addition, the wheel balance law is designed to maintain 1-Hz separation between the wheel speeds to avoid reinforcing jitter excitation at any particular frequency. The wheel balance law and operational implications are described. Finally, the candidate GNC hardware suite needed to meet the requirements of the mission is presented.

Stoneking, Eric↗

Precision Pointing for the Wide-Field Infrared Survey Telescope(WFIRST)

The Wide-Field Infrared Survey Telescope (WFIRST) mission, scheduled for a mid-2020's launch, is currently in its definition phase. The mission is designed to investigate essential questions in the areas of dark energy, exoplanets, and infrared astrophysics. WFIRST will use a 2.4-meter primary telescope (same size as the Hubble Space Telescope's primary mirror) and two instruments: the Wide Field Instrument (WFI) and the Coronagraph Instrument (CGI). In order to address the critical science requirements, the WFIRST mission will conduct large-scale surveys of the infrared sky, requiring both agility and precision pointing (11.6 milli-arcsec stability, 14 milli-arcsec jitter). This paper describes some of the challenges this mission profile presents to the Guidance, Navigation, and Control (GNC) subsystem, and some of the design elements chosen to accommodate those challenges. The high-galactic-latitude survey is characterized by 3-minute observations separated by slews ranging from 0.025 deg to 0.8 deg. The need for observation efficiency drives the slew and settle process to be as rapid as possible. A description of the shaped slew profile chosen to minimize excitation of structural oscillation, and the handoff from star tracker-gyro control to fine guidance sensor control is detailed. Also presented is the fine guidance sensor (FGS), which is integral with the primary instrument (WFI). The FGS is capable of tracking up to 18 guide stars, enabling robust FGS acquisition and precision pointing. To avoid excitation of observatory structural jitter, reaction wheel speeds are operationally maintained within set limits. In addition, the wheel balance law is designed to maintain 1-Hz separation between the wheel speeds to avoid reinforcing jitter excitation at any particular frequency. The wheel balance law and operational implications are described. Finally, the candidate GNC hardware suite needed to meet the requirements of the mission is presented.

Stoneking, Eric T.↗

Next Generation P-Band Planetary Synthetic Aperture Radar

The Space Exploration Synthetic Aperture Radar (SESAR) is an advanced P-band beamforming radar instrument concept to enable a new class of observations suitable to meet Decadal Survey science goals for planetary exploration. The radar operates at full polarimetry and fine (meter scale) resolution, and achieves beam agility through programmable waveform generation and digital beamforming. The radar architecture employs a novel low power, lightweight design approach to meet stringent planetary instrument requirements. This instrument concept has the potential to provide unprecedented surface and near- subsurface measurements applicable to multiple DecadalSurvey Science Goals.

Wide band↗

Diffusivities of Redox-Sensitive Elements in Basalt vs. Oxygen Fugacity Determined by LA-ICP-MS

Several diffusion experiments were conducted in a piston cylinder device across a range of oxygen fugacities (FMQ-3 FMQ-1.2, FMQ+6) at 1 GPa and 1300 C. This was done to explore the effects of oxygen fugacity (fO2) on diffusivity of redox sensitive trace elements. This allows investigation of how these elements diffuse across the fO2 range encountered in different reservoirs on planets and moons in our solar system. The University of Rochester LA-ICP-MS system was used for analysis of samples. Analyses were conducted using an Agilent 7900 quadrupole mass spectrometer connected to a Photon Machines 193 nm G2 laser ablation (LA) system equipped with a HelEx 2-volume sample chamber. Spots used were 35 micrometers circles spaced at 65 micrometers intervals. Laser fluence was 7.81 J/cm^2 with a rep rate of 10 Hz. The iolite software package was used to reduce data collected from laser ablation analysis of experiments with Si-29 used as the internal standard isotope. Iolite's global fit module was used to simultaneously fit elements' diffusivities in each experiment while keeping the Matano interface constant. Elements analysed include V, Nb, W, Mo, La, Ce, Pr, Sm, Eu, Gd, Ta, and W. Figures

Szumila, Ian↗

Get the Power You Need, When and Where You Need It Aboard the International Space Station (ISS) Using the ISS Plug-In Plan (IPiP) Requirement Request Process

Trying to get your experiment aboard ISS? You likely will need power. Many enditem providers do. ISS Plug-In Plan (IPiP) supports power and data for science, Payloads (or Utilization), vehicle systems, and daily operations through the Electrical Power System (EPS) Secondary Power/Data Subsystem. Yet limited resources and increasing requirements continue to influence decisions on deployment of ISS end items. Given the fluid launch schedule and the rapidly- increasing number of end item providers requiring power support, the focus of the Plug-In Plan has evolved from a simple FIFO recommendation to provide power to end item users, to anticipating future requirements by judicious development and delivery of support equipment (cables, power supplies, power strips, and alternating current (AC) power inverters), employing innovative deployment strategies, and collaborating on end item development. This paper describes the evolution of the ISS Program Office, Engineering Directorate, Flight Operations Directorate (FOD), International Partners and the end item provider relationship and how collaboration successfully leverages unique requirements with limited on- board equipment and resources, tools and processes which result in more agile integration, and describes the process designed for the new ISS end item provider to assure that their power requirements will be met.

Moore, Kevin D.↗

Digital Model-Based Engineering: Expectations, Prerequisites, and Challenges of Infusion

Digital model-based engineering (DMbE) is the use of digital artifacts, digital environments, and digital tools in the performance of engineering functions. DMbE is intended to allow an organization to progress from documentation-based engineering methods to digital methods that may provide greater flexibility, agility, and efficiency. The term 'DMbE' was developed as part of an effort by the Model-Based Systems Engineering (MBSE) Infusion Task team to identify what government organizations might expect in the course of moving to or infusing MBSE into their organizations. The Task team was established by the Interagency Working Group on Engineering Complex Systems, an informal collaboration among government systems engineering organizations. This Technical Memorandum (TM) discusses the work of the MBSE Infusion Task team to date. The Task team identified prerequisites, expectations, initial challenges, and recommendations for areas of study to pursue, as well as examples of efforts already in progress. The team identified the following five expectations associated with DMbE infusion, discussed further in this TM: (1) Informed decision making through increased transparency, and greater insight. (2) Enhanced communication. (3) Increased understanding for greater flexibility/adaptability in design. (4) Increased confidence that the capability will perform as expected. (5) Increased efficiency. The team identified the following seven challenges an organization might encounter when looking to infuse DMbE: (1) Assessing value added to the organization. Not all DMbE practices will be applicable to every situation in every organization, and not all implementations will have positive results. (2) Overcoming organizational and cultural hurdles. (3) Adopting contractual practices and technical data management. (4) Redefining configuration management. The DMbE environment changes the range of configuration information to be managed to include performance and design models, database objects, as well as more traditional book-form objects and formats. (5) Developing information technology (IT) infrastructure. Approaches to implementing critical, enabling IT infrastructure capabilities must be flexible, reconfigurable, and updatable. (6) Ensuring security of the single source of truth (7) Potential overreliance on quantitative data over qualitative data. Executable/ computational models and simulations generally incorporate and generate quantitative vice qualitative data. The Task team also developed several recommendations for government, academia, and industry, as discussed in this TM. The Task team recommends continuing beyond this initial work to further develop the means of implementing DMbE and to look for opportunities to collaborate and share best practices.

Hale, J. P.↗

Next Generation P-Band Planetary Synthetic Aperture Radar

The Space Exploration Synthetic Aperture Radar (SESAR) is an advanced P-band beamforming radar instrument concept to enable a new class of observations suitable to meet Decadal Survey science goals for planetary exploration. The radar operates at full polarimetry and fine (meter scale) resolution, and achieves beam agility through programmable waveform generation and digital beamforming. The radar architecture employs a novel low power, lightweight design approach to meet stringent planetary instrument requirements. This instrument concept has the potential to provide unprecedented surface and near- subsurface measurements applicable to multiple Decadal Survey Science Goals.

P-band↗

NASA Centers and Universities Collaborate Through Smallsat Technology Partnerships

The Small Spacecraft Technology (SST) Program within the NASA Space Technology Mission Directorate is chartered develop and demonstrate the capabilities that enable small spacecraft to achieve science and exploration missions in "unique" and "more affordable" ways. Specifically, the SST program seeks to enable new mission architectures through the use of small spacecraft, to expand the reach of small spacecraft to new destinations, and to make possible the augmentation existing assets and future missions with supporting small spacecraft. The SST program sponsors smallsat technology development partnerships between universities and NASA Centers in order to engage the unique talents and fresh perspectives of the university community and to share NASA experience and expertise in relevant university projects to develop new technologies and capabilities for small spacecraft. These partnerships also engage NASA personnel in the rapid, agile and cost-conscious small spacecraft approaches that have evolved in the university community, as well as increase support to university efforts and foster a new generation of innovators for NASA and the nation.

Partnerships↗