Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Agile Development”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

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↗
NASA NTRS2018

Marrying Social Media Approaches and Space Flight Control: Eight Years at SpaceOps

Three previous SpaceOps papers [1-3] - published in 2010, 2012 (honored by the Conference as a "Best Paper"), and 2014 - have discussed paths to using social media concepts and techniques to enhance space flight controller effectiveness by a) reducing clutter of nonverbal communications (e.g., visual flow with minimal headers and shared content instead of multiple copies), b) moving some voice communication to non-verbal transmission (virtually eliminating "say again" requests because non-verbal comm can be re-read), thus making remaining voice comm easier to focus on, and c) reducing short-term and long-term flight stress on flight control personnel. This paper shows how Marshall Space Flight Center's (MSFC) ISS Payload Operations Integration Center (POIC) is realizing the above goals via the Communications Dashboard (CommDash) software suite deployed in 2017 (including enhancements to the Console Log Tool (CoLT) discussed in earlier papers). Two larger-scope benefits spawned by CommDash evolution are also chronicled: a) emergence of an Agile Software Development (ASD) process adapted to the not-always-nimble environment of government projects, and b) the sprouting of a Human Factors Engineering (HF or HFE) community of practice within MSFC's Payload and Mission Operations Division (PMOD).

Scott, David W.↗
NASA NTRSDate not supplied

Using Coordinated, Multi-Agent Platforms for Dynamic Ocean Worlds Science

Planetary science missions have the opportunity to enhance science return through deployment of autonomous capabilities designed to dynamically respond to new information. Future outer solar system missions to ocean worlds in particular would benefit from this technology - intelligent science payloads (ISP) - because it would allow for a coordinated, near real-time response to ephemeral ‘events’ such as plumes, tectonism, surface implantation, volatile releases, thermal and magnetic anomalies, or radiation, as well as increasing the cadence and coverage of data collection. Prioritization and decision-making frameworks from ISP could be deployed at various scales - from analysis onboard a spacecraft with multiple instruments – to coordinated analyses among separate spacecraft in an e.g., distributed systems mission (DSM) composed of multiple SmallSats. Goddard’s Intelligent Science Payload team is developing an agile autonomous architecture for an icy ocean worlds DSM concept. Our goals are to coordinate data collection and onboard data analysis, and to make autonomous decisions for new data collection and analysis based on science priorities between multiple spacecraft with variable instrumentation and orbits. We use a range of data analysis tools to coordinate the DSM response, spanning from observations of data over a specified threshold to more computationally intensive machine learning algorithms (ML). ML algorithms here currently focus on determining the composition of an ocean world using mass spectrometry, and specifically methods for understanding ‘novelties’ and potential biosignatures. These algorithms could be used to quickly process and analyze onboard data that would be significantly delayed in downlink due to long communication delays for outer solar system missions in order to make dynamic science observations. Our ocean worlds case study ISP architecture is intended as an ‘agile’ and modular framework that could be used as a whole or as particular modules based on mission needs.

Distributed Systems↗
NASA NTRS2023

Adaptive Mission Assurance (AMA) – A Conceptual Guide for NASA Missions

NASA is well acquainted with and skilled in conducting Risk Class A Safety and Mission Assurance (SMA). Class A missions are characterized as having highly specific performance with an ultra-low risk tolerance for risk and mission failure. But space is rapidly changing, and the space enterprise is challenged to pursue faster more agile mission developments with fewer resources and directed schedules. To meet this demand mission development teams face accepting more risk and trading performance within strict cost and schedule constraints. In responding to this challenge, The Aerospace Corporation has evolved the Adaptive Mission Assurance (AMA) approach. The benefit of an “adaptive” approach is most realized for smaller Research and Development (R&D), or Science and Technology (S&T) demonstration missions constrained by significantly smaller budgets and directed schedules. The challenge for these “risk tolerant, constraints-driven” missions is how to identify the most valuable mission assurance tasks that will fit within strict budgetary and schedule constraints for “gracefully” accepting risk that still achieves an agreeable expectation of mission success. AMA can respond to this challenge with little to no impact to team staffing or existing workload. This conceptual guide introduces AMA as a potential implementation for NASA Risk Class D and Sub-Class D missions.

Douglas A. Harris↗
NASA NTRSDate not supplied

Linear Parameter-Varying Control Compatible with Excitation for Real-Time Modeling

The Modeling and Control for Agile Aircraft Development project (MCAAD) seeks to reduce the time spent on wind tunnel testing and computational fluid dynamic modeling when developing control laws for new commercial and military aircraft. MCAAD uses advanced dynamic modeling procedures coupled with real-time control design which can reduce the time and cost spent on traditional aircraft development methods. This is done in-flight by using a real-time modeling procedure where programmed test inputs (PTI) deflect the aircraft control surfaces, and the responses are measured in order to create a dynamic model. This paper presents an 𝐻∞-based linear parameter-varying (LPV) control law designed on a nonlinear rigid-body dynamic model which commands control surface deflections at frequencies above the PTI frequency band. Thus the controller will not suppress the response due to the PTI. The LPV controller is compared with a previously designed Nonlinear Dynamic Inversion (NDI) controller and the coherence between the commanded control surface deflections and the PTI is plotted for both controllers. The LPV controller is shown to distort the PTI less than the NDI controller.

Luke J. Miller↗
NASA NTRS1993

Development of a Computer Program for Analyzing Preliminary Aircraft Configurations in Relationship to Emerging Agility Metrics

This paper discusses the development of a FORTRAN computer code to perform agility analysis on aircraft configurations. This code is to be part of the NASA-Ames ACSYNT (AirCraft SYNThesis) design code. This paper begins with a discussion of contemporary agility research in the aircraft industry and a survey of a few agility metrics. The methodology, techniques and models developed for the code are then presented. Finally, example trade studies using the agility module along with ACSYNT are illustrated. These trade studies were conducted using a Northrop F-20 Tigershark aircraft model. The studies show that the agility module is effective in analyzing the influence of common parameters such as thrust-to-weight ratio and wing loading on agility criteria. The module can compare the agility potential between different configurations. In addition, one study illustrates the module's ability to optimize a configuration's agility performance.

Bauer, Brent↗
NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗
NASA NTRS2017

Applying Standard Independent Verification and Validation (IVV) Techniques Within an Agile Framework: Is There a Compatibility Issue?

Agile methods have gained wide acceptance over the past several years, to the point that they are now a standard management and execution approach for small-scale software development projects. While conventional Agile methods are not generally applicable to large multi-year and mission-critical systems, Agile hybrids are now being developed (such as SAFe) to exploit the productivity improvements of Agile while retaining the necessary process rigor and coordination needs of these projects. From the perspective of Independent Verification and Validation (IVV), however, the adoption of these hybrid Agile frameworks is becoming somewhat problematic. Hence, we find it prudent to question the compatibility of conventional IVV techniques with (hybrid) Agile practices.This paper documents our investigation of (a) relevant literature, (b) the modification and adoption of Agile frameworks to accommodate the development of large scale, mission critical systems, and (c) the compatibility of standard IVV techniques within hybrid Agile development frameworks. Specific to the latter, we found that the IVV methods employed within a hybrid Agile process can be divided into three groups: (1) early lifecycle IVV techniques that are fully compatible with the hybrid lifecycles, (2) IVV techniques that focus on tracing requirements, test objectives, etc. are somewhat incompatible, but can be tailored with a modest effort, and (3) IVV techniques involving an assessment requiring artifact completeness that are simply not compatible with hybrid Agile processes, e.g., those that assume complete requirement specification early in the development lifecycle.

Agile↗
NASA NTRS1990

Fighter agility metrics, research, and test

Proposed new metrics to assess fighter aircraft agility are collected and analyzed. A framework for classification of these new agility metrics is developed and applied. A completed set of transient agility metrics is evaluated with a high fidelity, nonlinear F-18 simulation provided by the NASA Dryden Flight Research Center. Test techniques and data reduction methods are proposed. A method of providing cuing information to the pilot during flight test is discussed. The sensitivity of longitudinal and lateral agility metrics to deviations from the pilot cues is studied in detail. The metrics are shown to be largely insensitive to reasonable deviations from the nominal test pilot commands. Instrumentation required to quantify agility via flight test is also considered. With one exception, each of the proposed new metrics may be measured with instrumentation currently available. Simulation documentation and user instructions are provided in an appendix.

Liefer, Randall K.↗
NASA NTRS1990

Fighter agility metrics

Fighter flying qualities and combat capabilities are currently measured and compared in terms relating to vehicle energy, angular rates and sustained acceleration. Criteria based on these measurable quantities have evolved over the past several decades and are routinely used to design aircraft structures, aerodynamics, propulsion and control systems. While these criteria, or metrics, have the advantage of being well understood, easily verified and repeatable during test, they tend to measure the steady state capability of the aircraft and not its ability to transition quickly from one state to another. Proposed new metrics to assess fighter aircraft agility are collected and analyzed. A framework for classification of these new agility metrics is developed and applied. A complete set of transient agility metrics is evaluated with a high fidelity, nonlinear F-18 simulation. Test techniques and data reduction methods are proposed. A method of providing cuing information to the pilot during flight test is discussed. The sensitivity of longitudinal and lateral agility metrics to deviations from the pilot cues is studied in detail. The metrics are shown to be largely insensitive to reasonable deviations from the nominal test pilot commands. Instrumentation required to quantify agility via flight test is also considered. With one exception, each of the proposed new metrics may be measured with instrumentation currently available.

Liefer, Randall K.↗
NASA NTRS1993

Analysis and optimization of preliminary aircraft configurations in relationship to emerging agility metrics

This paper discusses the development of a FORTRAN computer code to perform agility analysis on aircraft configurations. This code is to be part of the NASA-Ames ACSYNT (AirCraft SYNThesis) design code. This paper begins with a discussion of contemporary agility research in the aircraft industry and a survey of a few agility metrics. The methodology, techniques and models developed for the code are then presented. Finally, example trade studies using the agility module along with ACSYNT are illustrated. These trade studies were conducted using a Northrop F-20 Tigershark aircraft model. The studies show that the agility module is effective in analyzing the influence of common parameters such as thrust-to-weight ratio and wing loading on agility criteria. The module can compare the agility potential between different configurations. In addition one study illustrates the module's ability to optimize a configuration's agility performance.

Sandlin, Doral R.↗
NASA NTRSDate not supplied

Unveiling NASA’s Agile Projects, Successes, Challenges, and Transformative Insight

The NASA Agile Community of Practice recently hosted the first NASA Agile Technical Interchange Meeting (TIM). The TIM provided an opportunity for Agile practitioners across the Agency to share their successes, challenges, and recommendations from Agile transformations. NASA has increasingly turned to private industry for collaborative efforts in space exploration, satellite deployment, and other missions. Embracing Agile principles, NASA is adapting its project management strategies to foster more flexible, efficient, and collaborative relationships with commercial partners. This paper provides highlights from the projects presented at the Agile TIM on how those teams have been able to iterate rapidly, respond to changing requirements, and deliver value more effectively.

agile↗
NASA NTRS2016

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Bolton, Albanie T.↗
NASA NTRS1995

Compact, Automated, Frequency-Agile Microspectrofluorimeter

Compact, reliable, rugged, automated cell-culture and frequency-agile microspectrofluorimetric apparatus developed to perform experiments involving photometric imaging observations of single live cells. In original application, apparatus operates mostly unattended aboard spacecraft; potential terrestrial applications include automated or semiautomated diagnosis of pathological tissues in clinical laboratories, biomedical instrumentation, monitoring of biological process streams, and portable instrumentation for testing biological conditions in various environments. Offers obvious advantages over present laboratory instrumentation.

Fernandez, Salvador M.↗
NASA NTRS2004

Discrete Wavelength-Locked External Cavity Laser

A prototype improved external cavity laser (ECL) was demonstrated in the second phase of a continuing effort to develop wavelength-agile lasers for fiber-optic communications and trace-gas-sensing applications. This laser is designed to offer next-generation performance for incorporation into fiber-optic networks. By eliminating several optical components and simplifying others used in prior designs, the design of this laser reduces costs, making lasers of this type very competitive in a price-sensitive market. Diode lasers have become enabling devices for fiber optic networks because of their cost, compactness, and spectral properties. ECLs built around diode laser gain elements further enhance capabilities by virtue of their excellent spectral properties with significantly increased (relative to prior lasers) wavelength tuning ranges. It is essential to exploit the increased spectral coverage of ECLs while simultaneously insuring that they operate only at precisely defined communication channels (wavelengths). Heretofore, this requirement has typically been satisfied through incorporation of add-in optical components that lock the ECL output wavelengths to these specific channels. Such add-in components contribute substantially to the costs of ECL lasers to be used as sources for optical communication networks. Furthermore, the optical alignment of these components, needed to attain the required wavelength precision, is a non-trivial task and can contribute substantially to production costs. The design of the present improved ECL differs significantly from the designs of prior ECLs. The present design relies on inherent features of components already included within an ECL, with slight modifications so that these components perform their normal functions while simultaneously effecting locking to the required discrete wavelengths. Hence, add-in optical components and the associated cost of alignment can be eliminated. The figure shows the locking feedback signal, and the frequency locking achieved by use of this signal, as a mirror is tilted through a range of angles to tune the ECL through 48 channels. The data for the frequency plot were obtained, simultaneously with the data for the locking-signal plot, by using a scanning Michelson interferometer to precisely determine the ECL wavelength (and, hence, frequency). Given the ability of the Michelson interferometer to obtain highly precise readings, the frequency plot can be taken to be a reliable indication of single-mode operation. The discontinuities in the frequency plot signify the switching of the ECL between channels; in other words, they indicate tuning with locking to discrete frequencies. The peaks of the feedbacklocking signal correspond to the centers, or near centers, of the mirror angle scan through the corresponding channels. Thus, it is clear that when the feedback-locking signal is at a local maximum, the ECL is operating at single frequency at or near the middle frequency of the selected channel. This is all that is required for precisely locking the ECL output wavelength. The locking is achieved without additional external optical components.

Pilgrim, Jeffrey S.↗
NASA NTRSDate not supplied

PAX Mobility

Pax Mobility is a Wicked Wild Discovery activity under the Convergent Aeronautics Solutions (CAS) project. It is intended to cut down the end-to-end travel time and friction for people and goods (referred to as passengers) through: (1) A passenger-oriented paradigm to enable faster mobility that is accessible by all people, end to end (rather than port to port), and that is also safer, more efficient, and sustainable. (2) A total mobility paradigm that integrates modes of mobility to achieve end-to-end passenger objectives. (3) Digital transformation that establishes an agile research and development process to reduce the time to reach end-to-end mobility solutions.

Passenger-oriented total mobility↗
NASA NTRS2014

Mission Control Technologies: Empowering Users

Traditional software is developed as monolithic applications that are typed and create boundaries around their domains. ARC, working with JSC, developed an object oriented user interface that reduced domain boundaries in software. We used agile participatory design to develop a solution with our customer in mission control.

Software engineering↗
NASA NTRS1991

The measurement and improvement of the lateral agility of the F-18

The effect of vehicle configuration and flight control system performance on the roll agility of a modern fighter aircraft has been investigated. A batch simulation of a generic F-18 Hornet was used to study the roll agility as measured by the time to roll through 90 deg metric. Problems discussed include definition of agility, factors affecting the agility of a vehicle, the development of the time to roll through 90 deg agility metric, and a simulation experiment. It is concluded that the integral of stability or wind axis roll rate should be used as a measure of the roll measure traversed. The time through roll angle 90 deg metric is considered to be a good metric for measuring the transient performance aspect of agility. Roll agility of the F-18, as measured by 90 deg metric, can be improved by 10 to 30 percent. Compatible roll and rudder actuator rates can significantly affect 90 deg agility metric.

Eggold, David P.↗