SEARCH · Engineering Papers

Results for “Development assurance”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 847 records · Page 47

All sources NASA NTRS DOE OSTI

NASA NTRS2019

Can We Use the QA4ECV Black-sky Fraction of Absorbed Photosynthetically Active Radiation (FAPAR) using AVHRR Surface Reflectance to Assess Terrestrial Global Change?

NOAA platforms provide the longest period of terrestrial observation since the 1980s. The progress in calibration, atmospheric corrections and physically based land retrieval offers the opportunity to reprocess these data for extending terrestrial product time series. Within the Quality Assurance for Essential Climate Variables (QA4ECV) project, the black-sky Joint Research Centre (JRC)-fraction of absorbed photosynthetically active radiation (FAPAR) algorithm was developed for the AVHRR sensors on-board NOAA-07 to -16 using the Land Surface Reflectance Climate Data Record. The retrieval algorithm was based on the radiative transfer theory, and uncertainties were included in the products. We proposed a time and spatial composite for providing both 10-day and monthly products at 0.05º × 0.05º. Quality control and validation were achieved through benchmarking against third-party products, including Sea-Viewing Wide Field-of-View Sensor (SeaWiFS) datasets produced with the same retrieval algorithm. Past ground-based measurements, providing a proxy of FAPAR, showed good agreement of seasonality values over short homogeneous canopies and mixed vegetation. The average difference between SeaWiFS and QA4ECV monthly products over 2002–2005 is about 0.075 with a standard deviation of 0.091. We proposed a monthly linear bias correction that reduced these statistics to 0.02 and 0.001. The complete harmonized long-term time series was then used to address its fitness for the purpose of analysis of global terrestrial change.

AVHRR↗

NASA NTRS2020

The “Gearamid” Model: Transforming NASA Langley’s Role in the Aerospace Technology Ecosystem

NASA’s operating environment is evolving: numerous new emerging technologies are converging to create breakthrough solutions, many nontraditional players are partnering to create those solutions, and a diverse array of new public-private funding models are being employed. A team at NASA’s Langley Research Center (LaRC) developed a model to describe the challenges that must be addressed for an emerging breakthrough technology to penetrate the appropriate market sector, and how all the players in the relevant ecosystem can collaborate to accelerate the market infusion process. This model, which the team dubbed the “Gearamid,” originated from a narrower study to determine what LaRC should do to capitalize on and advance autonomous technology as a “game changer” in the civil aerospace domain. The elements in the original version of the Gearamid depict the various challenges that need to be addressed as an autonomous technology proceeds from initial development to market infusion. In addition, the Gearamid indicates the “actors” best suited to address each challenge element. The study team noted that all challenge elements in the Gearamid must be worked concurrently to assure successful infusion of autonomous solutions. The team also found that NASA expertise naturally positions Agency organizations—including LaRC—to lead contributions that address certain challenge elements and to play a supplemental role in other areas where entities external to NASA are actively working and investing to solve challenges. Furthermore, the team concluded that NASA can play a leadership role in coordinating efforts of the diverse entities across the civil aerospace community. After determining the center’s optimal role in the autonomous technology development ecosystem, the study team then extrapolated the Gearamid model for autonomous technologies into a broader, more general model depicting the challenge elements that must be overcome to develop and infuse any emerging technology. LaRC has embraced the Gearamid model and is using it to drive changes that will transform the center and allow it to function optimally in the evolving landscape. Given LaRC’s successes, the study team suggests that other organizations may also be able to use the Gearamid model to inform future planning/strategy efforts.

Jill M Marlowe↗

NASA NTRS2009

Shuttle Shortfalls and Lessons Learned for the Sustainment of Human Space Exploration

Much debate and national soul searching has taken place over the value of the Space Shuttle which first flew in 1981 and which is currently scheduled to be retired in 2010. Originally developed post-Saturn Apollo to emphasize affordability and safety, the reusable Space Shuttle instead came to be perceived as economically unsustainable and lacking the technology maturity to assure safe, routine access to low earth orbit (LEO). After the loss of two crews, aboard Challenger and Columbia, followed by the decision to retire the system in 2010, it is critical that this three decades worth of human space flight experience be well understood. Understanding of the past is imperative to further those goals for which the Space Shuttle was a stepping-stone in the advancement of knowledge. There was significant reduction in life cycle costs between the Saturn Apollo and the Space Shuttle. However, the advancement in life cycle cost reduction from Saturn Apollo to the Space Shuttle fell far short of its goal. This paper will explore the reasons for this shortfall. Shortfalls and lessons learned can be categorized as related to design factors, at the architecture, element and sub-system levels, as well as to programmatic factors, in terms of goals, requirements, management and organization. Additionally, no review of the Space Shuttle program and attempt to take away key lessons would be complete without a strategic review. That is, how do national space goals drive future space transportation development strategies? The lessons of the Space Shuttle are invaluable in all respects - technical, as in design, program-wise, as in organizational approach and goal setting, and strategically, within the context of the generational march toward an expanded human presence in space. Beyond lessons though (and the innumerable papers, anecdotes and opinions published on this topic) this paper traces tangible, achievable steps, derived from the Space Shuttle program experience, that must be a part of any 2l century initiatives furthering a growing human presence beyond earth.

Zapata, Edgar↗

NASA NTRS2013

Assessment Environment for Complex Systems Software Guide

This Software Guide (SG) describes the software developed to test the Assessment Environment for Complex Systems (AECS) by the West Virginia High Technology Consortium (WVHTC) Foundation's Mission Systems Group (MSG) for the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD). This software is referred to as the AECS Test Project throughout the remainder of this document. AECS provides a framework for developing, simulating, testing, and analyzing modern avionics systems within an Integrated Modular Avionics (IMA) architecture. The purpose of the AECS Test Project is twofold. First, it provides a means to test the AECS hardware and system developed by MSG. Second, it provides an example project upon which future AECS research may be based. This Software Guide fully describes building, installing, and executing the AECS Test Project as well as its architecture and design. The design of the AECS hardware is described in the AECS Hardware Guide. Instructions on how to configure, build and use the AECS are described in the User's Guide. Sample AECS software, developed by the WVHTC Foundation, is presented in the AECS Software Guide. The AECS Hardware Guide, AECS User's Guide, and AECS Software Guide are authored by MSG. The requirements set forth for AECS are presented in the Statement of Work for the Assessment Environment for Complex Systems authored by NASA Dryden Flight Research Center (DFRC). The intended audience for this document includes software engineers, hardware engineers, project managers, and quality assurance personnel from WVHTC Foundation (the suppliers of the software), NASA (the customer), and future researchers (users of the software). Readers are assumed to have general knowledge in the field of real-time, embedded computer software development.

tests↗

NASA NTRS2015

Survey of Verification and Validation Techniques for Small Satellite Software Development

The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation.

Small Satellite Technology↗

NASA NTRS2004

Evaluation of Open-Source Hard Real Time Software Packages

Reliable software is, at times, hard to find. No piece of software can be guaranteed to work in every situation that may arise during its use here at Glenn Research Center or in space. The job of the Software Assurance (SA) group in the Risk Management Office is to rigorously test the software in an effort to ensure it matches the contract specifications. In some cases the SA team also researches new alternatives for selected software packages. This testing and research is an integral part of the department of Safety and Mission Assurance. Real Time operation in reference to a computer system is a particular style of handing the timing and manner with which inputs and outputs are handled. A real time system executes these commands and appropriate processing within a defined timing constraint. Within this definition there are two other classifications of real time systems: hard and soft. A soft real time system is one in which if the particular timing constraints are not rigidly met there will be no critical results. On the other hand, a hard real time system is one in which if the timing constraints are not met the results could be catastrophic. An example of a soft real time system is a DVD decoder. If the particular piece of data from the input is not decoded and displayed to the screen at exactly the correct moment nothing critical will become of it, the user may not even notice it. However, a hard real time system is needed to control the timing of fuel injections or steering on the Space Shuttle; a delay of even a fraction of a second could be catastrophic in such a complex system. The current real time system employed by most NASA projects is Wind River's VxWorks operating system. This is a proprietary operating system that can be configured to work with many of NASA s needs and it provides very accurate and reliable hard real time performance. The down side is that since it is a proprietary operating system it is also costly to implement. The prospect of replacing this somewhat costly implementation is the focus of one of the SA group s current research projects. The explosion of open source software in the last ten years has led to the development of a multitude of software solutions which were once only produced by major corporations. The benefits of these open projects include faster release and bug patching cycles as well as inexpensive if not free software solutions. The main packages for hard real time solutions under Linux are Real Time Application Interface (RTAI) and two varieties of Real Time Linux (RTL), RTLFree and RTLPro. During my time here at NASA I have been testing various hard real time solutions operating as layers on the Linux Operating System. All testing is being run on an Intel SBC 2590 which is a common embedded hardware platform. The test plan was provided to me by the Software Assurance group at the start of my internship and my job has been to test the systems by developing and executing the test cases on the hardware. These tests are constructed so that the Software Assurance group can get hard test data for a comparison between the open source and proprietary implementations of hard real time solutions.

Mattei, Nicholas S.↗

NASA NTRS2015

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision D

This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.

Roberts, Barry C.↗

NASA NTRS2012

Miniature EVA Software Defined Radio

As NASA embarks upon developing the Next-Generation Extra Vehicular Activity (EVA) Radio for deep space exploration, the demands on EVA battery life will substantially increase. The number of modes and frequency bands required will continue to grow in order to enable efficient and complex multi-mode operations including communications, navigation, and tracking applications. Whether conducting astronaut excursions, communicating to soldiers, or first responders responding to emergency hazards, NASA has developed an innovative, affordable, miniaturized, power-efficient software defined radio that offers unprecedented power-efficient flexibility. This lightweight, programmable, S-band, multi-service, frequency- agile EVA software defined radio (SDR) supports data, telemetry, voice, and both standard and high-definition video. Features include a modular design, an easily scalable architecture, and the EVA SDR allows for both stationary and mobile battery powered handheld operations. Currently, the radio is equipped with an S-band RF section. However, its scalable architecture can accommodate multiple RF sections simultaneously to cover multiple frequency bands. The EVA SDR also supports multiple network protocols. It currently implements a Hybrid Mesh Network based on the 802.11s open standard protocol. The radio targets RF channel data rates up to 20 Mbps and can be equipped with a real-time operating system (RTOS) that can be switched off for power-aware applications. The EVA SDR's modular design permits implementation of the same hardware at all Network Nodes concept. This approach assures the portability of the same software into any radio in the system. It also brings several benefits to the entire system including reducing system maintenance, system complexity, and development cost.

Pozhidaev, Aleksey↗

NASA NTRS1974

Membrane water deaerator investigation

The purpose of the membrane water deaerator program was to develop data on a breadboard hollow fiber membrane unit that removes both dissolved and evolved gas from a water transfer system in order to: (1) assure a hard fill of the EVLSS expendable water tank; (2) prevent flow blockage by gas bubbles in circulating systems; and (3) prevent pump cavitation.

Elam, J.↗

NASA NTRS1974

Spacelab program requirements, level 1

The design and development of Spacelab is reported including the ground support equipment, facilities, and operational planning. The shuttle interface, and user requirements are discussed along with product assurance and safety.

Source record↗

NASA NTRS1981

On-board computer progress in development of A 310 flight testing program

Onboard computer progress in development of an Airbus A 310 flight testing program is described. Minicomputers were installed onboard three A 310 airplanes in 1979 in order to: (1) assure the flight safety by exercising a limit check of a given set of parameters; (2) improve the efficiency of flight tests and allow cost reduction; and (3) perform test analysis on an external basis by utilizing onboard flight types. The following program considerations are discussed: (1) conclusions based on simulation of an onboard computer system; (2) brief descriptions of A 310 airborne computer equipment, specifically the onboard universal calculator (CUB) consisting of a ROLM 1666 system and visualization system using an AFIGRAF CRT; (3) the ground system and flight information inputs; and (4) specifications and execution priorities for temporary and permanent programs.

Reau, P.↗

NASA NTRS1985

Life sciences accomplishments

From its inception, the main charter of Life Sciences has been to define biomedical requirements for the design and development of spacecraft systems and to participate in NASA's scientific exploration of the universe. The role of the Life Sciences Division is to: (1) assure the health, well being and productivity of all individuals who fly in space; (2) study the origin, evolution, and distribution of life in the universe; and (3) to utilize the space environment as a tool for research in biology and medicine. The activities, programs, and accomplishments to date in the efforts to achieve these goals are detailed and the future challenges that face the division as it moves forward from the shuttle era to a permanent manned presence in space space station's are examined.

Source record↗

NASA NTRS1989

Aerospace Safety Advisory Panel

This report provides findings, conclusions and recommendations regarding the National Space Transportation System (NSTS), the Space Station Freedom Program (SSFP), aeronautical projects and other areas of NASA activities. The main focus of the Aerospace Safety Advisory Panel (ASAP) during 1988 has been monitoring and advising NASA and its contractors on the Space Transportation System (STS) recovery program. NASA efforts have restored the flight program with a much better management organization, safety and quality assurance organizations, and management communication system. The NASA National Space Transportation System (NSTS) organization in conjunction with its prime contractors should be encouraged to continue development and incorporation of appropriate design and operational improvements which will further reduce risk. The data from each Shuttle flight should be used to determine if affordable design and/or operational improvements could further increase safety. The review of Critical Items (CILs), Failure Mode Effects and Analyses (FMEAs) and Hazard Analyses (HAs) after the Challenger accident has given the program a massive data base with which to establish a formal program with prioritized changes.

Source record↗

NASA NTRS1993

Efficient development and processing of thermal math models of very large space truss structures

As the spacecraft moves along the orbit, the truss members are subjected to direct and reflected solar, albedo and planetary infra-red (IR) heating rates, as well as IR heating and shadowing from other spacecraft components. This is a transient process with continuously changing heating loads and the shadowing effects. The resulting nonuniform temperature distribution may cause nonuniform thermal expansion, deflection and stress in the truss elements, truss warping and thermal distortions. There are three challenges in the thermal-structural analysis of the large truss structures. The first is the development of the thermal and structural math models, the second - model processing, and the third - the data transfer between the models. All three tasks require considerable time and computer resources to be done because of a very large number of components involved. To address these challenges a series of techniques of automated thermal math modeling and efficient processing of very large space truss structures were developed. In the process the finite element and finite difference methods are interfaced. A very substantial reduction of the quantity of computations was achieved while assuring a desired accuracy of the results. The techniques are illustrated on the thermal analysis of a segment of the Space Station main truss.

Warren, Andrew H.↗

NASA NTRS1991

Data systems and computer science: Software Engineering Program

An external review of the Integrated Technology Plan for the Civil Space Program is presented. This review is specifically concerned with the Software Engineering Program. The goals of the Software Engineering Program are as follows: (1) improve NASA's ability to manage development, operation, and maintenance of complex software systems; (2) decrease NASA's cost and risk in engineering complex software systems; and (3) provide technology to assure safety and reliability of software in mission critical applications.

Zygielbaum, Arthur I.↗

NASA NTRS2002

Architecture-Adaptive Computing Environment: A Tool for Teaching Parallel Programming

Recently, networked and cluster computation have become very popular. This paper is an introduction to a new C based parallel language for architecture-adaptive programming, aCe C. The primary purpose of aCe (Architecture-adaptive Computing Environment) is to encourage programmers to implement applications on parallel architectures by providing them the assurance that future architectures will be able to run their applications with a minimum of modification. A secondary purpose is to encourage computer architects to develop new types of architectures by providing an easily implemented software development environment and a library of test applications. This new language should be an ideal tool to teach parallel programming. In this paper, we will focus on some fundamental features of aCe C.

Dorband, John E.↗

NASA NTRS2004

The NASA Micro-Pulse Lidar Network (MPLNET): Co-location of Lidars with AERONET

We present the formation of a global-ground based eye-safe lidar network, the NASA Micro-Pulse Lidar Network (MPLNET). The aim of MPLNET is to acquire long-term observations of aerosol and cloud vertical profiles at unique geographic sites within the NASA Aerosol Robotic Network (AERONET). Network growth follows a federated approach, pioneered by AERONET, wherein independent research groups may join MPLNET with their own instrument and site. MPLNET utilizes standard instrumentation and data processing algorithms for efficient network operations and direct comparison of data between each site. The micro-pulse lidar is eye-safe, compact, and commercially available, and most easily allows growth of the network without sacrificing standardized instrumentation gods. Red-time data products (next-day) are available, and include Level 1 daily lidar signal images from the surface to -2Okm, and Level 1.5 aerosol extinction provides at times co-incident with AERONET observations. Testing of our quality assured aerosol extinction products, Level 2, is near completion and data will soon be available. Level 3 products, continuous daylight aerosol extinction profiles, are under development and testing has begun. An overview of h4PL" will be presented. Successful methods of merging standardized lidar operations with AERONET will also be discussed, with the first 4 years of MPLNET results serving as an example.

Welton, Ellsworth J.↗

NASA NTRS2009

Influence of Combined Whole-Body Vibration Plus G-Loading on Visual Performance

Recent engineering analyses of the integrated Ares-Orion stack show that vibration levels for Orion crews have the potential to be much higher than those experienced in Gemini, Apollo, and Shuttle vehicles. Of particular concern to the Constellation Program (CxP) is the 12 Hz thrust oscillation (TO) that the Ares-I rocket develops during the final ~20 seconds preceding first-stage separation, at maximum G-loading. While the structural-dynamic mitigations being considered can assure that vibration due to TO is reduced to below the CxP crew health limit, it remains to be determined how far below this limit vibration must be reduced to enable effective crew performance during launch. Moreover, this "performance" vibration limit will inform the operations concepts (and crew-system interface designs) for this critical phase of flight. While Gemini and Apollo studies provide preliminary guidance, the data supporting the historical limits were obtained using less advanced interface technologies and very different operations concepts. In this study, supported by the Exploration Systems Mission Directorate (ESMD) Human Research Program, we investigated display readability-a fundamental prerequisite for any interaction with electronic crew-vehicle interfaces-while observers were subjected to 12 Hz vibration superimposed on the 3.8 G loading expected for the TO period of ascent. Two age-matched groups of participants (16 general population and 13 Crew Office) performed a numerical display reading task while undergoing sustained 3.8 G loading and whole-body vibration at 0, 0.15, 0.3, 0.5, and 0.7 g in the eyeballs in/out (x-axis) direction. The time-constrained reading task used an Orion-like display with 10- and 14-pt non-proportional sans-serif fonts, and was designed to emulate the visual acquisition and processing essential for crew system monitoring. Compared to the no-vibration baseline, we found no significant effect of vibration at 0.15 and 0.3 g on task error rates (ER) or response times (RT). Significant degradations in both ER and RT, however, were observed at 0.5 and 0.7 g for 10-pt, and at 0.7 g for 14-pt font displays. These objective performance measures were mirrored by participants' subjective ratings. Interestingly, we found that the impact of vibration on ER increased with distance from the center of the display, but only for vertical displacements. Furthermore, no significant ER or RT aftereffects were detected immediately following vibration, regardless of amplitude. Lastly, given that our reading task required no specialized spaceflight expertise, our finding that effects were not statistically distinct between our two groups is not surprising. The results from this empirical study provide initial guidance for evaluating the display readability trade-space between text-font size and vibration amplitude. However, the outcome of this work should be considered preliminary in nature for a number of reasons: 1. The single 12 Hz x-axis vibration employed was based on earlier load-cycle models of the induced TO environment at the end of Ares-I first stage flight. Recent analyses of TO mitigation designs suggest that significant concurrent off-axis vibration may also occur. 2. The shirtsleeve environment in which we tested fails to capture the full kinematic and dynamic complexity of the physical interface between crewmember and the still-to-bematured helmet-suit-seat designs, and the impact these will have for vibration transmission and consequent performance. 3. By examining performance in this reading and number processing task, we are only assessing readability, a first and necessary step that in itself does not directly address the performance of more sophisticated operational tasks such as vehicle-health monitoring or manual control of the vehicle.

readability↗