Engineering Papers⌕ Search

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.

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

At least 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

NASA Mission Operations Directorate Preparations for the COTS Visiting Vehicles

With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better understanding of the mission assurance that MOD brings to commercial ventures to the ISS

Shull, Sarah A.↗
NASA NTRS2018

Assurance of Autonomy for Robotic Space Missions

While there have been meetings on assurance of autonomy in other application areas, this meeting seeks to develop a roadmap for assurance of autonomy specifically for robotic space missions. Key characteristics that distinguish this application area include: the lack of detailed prior knowledge of the environments in which those missions are to operate; the challenges of mimicking deep space operating conditions for purposes of testing; the need to be highly assured of failsafe operation; limited and delayed (due to speed of light over solar system distances) communication; and the one/few-of-a-kind, must-work-the-first-time nature of most space missions.

Feather, Martin↗
NASA NTRS2004

Software for Analyzing Laminar-to-Turbulent Flow Transitions

Software assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures. Examples of such activities are the following: code inspections, unit tests, design reviews, performance analyses, construction of traceability matrices, etc. In practice, software development projects have only limited resources (e.g., schedule, budget, and availability of personnel) to cover the entire development effort, of which assurance is but a part. Projects must therefore select judiciously from among the possible assurance activities. At its heart, this can be viewed as an optimization problem; namely, to determine the allocation of limited resources (time, money, and personnel) to minimize risk or, alternatively, to minimize the resources needed to reduce risk to an acceptable level. The end result of the work reported here is a means to optimize quality-assurance processes used in developing software. This is achieved by combining two prior programs in an innovative manner

Chang, Chau-Lyan↗
NASA NTRS2004

Software for Optimizing Quality Assurance of Other Software

Software assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures. Examples of such activities are the following: code inspections, unit tests, design reviews, performance analyses, construction of traceability matrices, etc. In practice, software development projects have only limited resources (e.g., schedule, budget, and availability of personnel) to cover the entire development effort, of which assurance is but a part. Projects must therefore select judiciously from among the possible assurance activities. At its heart, this can be viewed as an optimization problem; namely, to determine the allocation of limited resources (time, money, and personnel) to minimize risk or, alternatively, to minimize the resources needed to reduce risk to an acceptable level. The end result of the work reported here is a means to optimize quality-assurance processes used in developing software.

Feather, Martin↗
NASA NTRS1977

Recollections from an earlier period in American aeronautics

The situation of American aeronautics in the year 1929 is examined. In that year manufacturers all over the U.S. were bringing out new aircraft models to capture an assured market. Earlier developments in aviation in the U.S. after World War I are also considered along with the conditions of American aeronautics in the 1930s. Attention is given to the introduction of the Barling NB-3 with its all-metal construction, efforts of NACA to collect and disseminate in a uniform notation aerodynamic characteristics of airfoils from laboratories around the world, and the invention of the variable-density wind tunnel.

Jones, R. T.↗
NASA NTRS1990

A cost-effective strategy for nonoscillatory convection without clipping

Clipping of narrow extrema and distortion of smooth profiles is a well known problem associated with so-called high resolution nonoscillatory convection schemes. A strategy is presented for accurately simulating highly convective flows containing discontinuities such as density fronts or shock waves, without distorting smooth profiles or clipping narrow local extrema. The convection algorithm is based on non-artificially diffusive third-order upwinding in smooth regions, with automatic adaptive stencil expansion to (in principle, arbitrarily) higher order upwinding locally, in regions of rapidly changing gradients. This is highly cost effective because the wider stencil is used only where needed-in isolated narrow regions. A recently developed universal limiter assures sharp monotonic resolution of discontinuities without introducing artificial diffusion or numerical compression. An adaptive discriminator is constructed to distinguish between spurious overshoots and physical peaks; this automatically relaxes the limiter near local turning points, thereby avoiding loss of resolution in narrow extrema. Examples are given for one-dimensional pure convection of scalar profiles at constant velocity.

Leonard, B. P.↗
NASA NTRS1991

Sharp monotonic resolution of discontinuities without clipping of narrow extrema

A strategy is presented for accurately simulating highly convective flows containing discontinuities such as density fronts or shock waves, without distorting smooth profiles or clipping narrow local extrema. The convection algorithm is based on non-artificially-diffusive third-order upwinding in smooth regions, with automatic adaptive stencil expansion to (in principle, arbitrarily) higher order upwinding locally, in regions of rapidly changing gradients. This is highly cost-effective because the wider stencil is used only where needed - in isolated narrow regions. A recently developed universal limiter assures sharp monotonic resolution of discontinuities without introducing artificial diffusion or numerical compression. An adaptive discriminator is constructed to distinguish between spurious overshoots and physical peaks; this automatically relaxes the limiter near local turning points, thereby avoiding loss of resolution in narrow extrema. Examples are given for one-dimensional pure convection of scalar profiles at constant velocity.

Leonard, B. P.↗
NASA NTRS1995

Helpful hints to painless payload processing

The helpful hints herein describe, from a system perspective, the functional flow of hardware and software. The flow will begin at the experiment development stage and continue through build-up, test, verification, delivery, launch and deintegration of the experiment. An effort will be made to identify those interfaces and transfer functions of processing that can be improved upon in the new world of 'Faster, Better, and Cheaper.' The documentation necessary to ensure configuration and processing requirements satisfaction will also be discussed. Hints and suggestions for improvements to enhance each phase of the flow will be derived from extensive experience and documented lessons learned. Charts will be utilized to define the functional flow and a list of 'lessons learned' will be addressed to show applicability. In conclusion, specific improvements for several areas of hardware processing, procedure development and quality assurance, that are generic to all Small Payloads, will be identified.

Terhune, Terry↗
NASA NTRS2009

IT Project Success w\7120 and 7123 NPRs to Achieve Project Success

This slide presentation reviews management techniques to assure information technology development project success. Details include the work products, the work breakdown structure (WBS), system integration, verification and validation (IV&V), and deployment and operations. An example, the NASA Consolidated Active Directory (NCAD), is reviewed.

Walley, Tina L.↗
NASA NTRS2016

Retrieving the Height of Smoke and Dust Aerosols by Synergistic Use of Multiple Satellite Sensors

The Aerosol Single scattering albedo and Height Estimation (ASHE) algorithm was first introduced in Jeong and Hsu (2008) to provide aerosol layer height and single scattering albedo (SSA) for biomass burning smoke aerosols. By using multiple satellite sensors synergistically, ASHE can provide the height information over much broader areas than lidar observations alone. The complete ASHE algorithm uses aerosol data from MODIS or VIIRS, OMI or OMPS, and CALIOP. A simplified algorithm also exists that does not require CALIOP data as long as the SSA of the aerosol layer is provided by another source. Several updates have recently been made: inclusion of dust layers in the retrieval process, better determination of the input aerosol layer height from CALIOP, improvement in aerosol optical depth (AOD) for nonspherical dust, development of quality assurance (QA) procedure, etc.

satellite remote sensing↗
NASA NTRS1996

Defect Detection and Prevention

As NASA continues to impement its Faster, Better, Cheaper philosophy, new approaches for implementing Mission Assurance activities are being developed.

faster↗
NASA NTRSDate not supplied

The NASA JSC Hypervelocity Impact Technology (HVIT) Office

The Hypervelocity Impact Technology (HVIT) office at the National Aeronautical and Space Administration (NASA) Johnson Space Center (JSC) is dedicated to support NASA flight programs in meeting their meteoroid and orbital debris (MMOD) protection requirements both efficiently and effectively, with a minimum of shielding mass, volume, and cost. This paper provides an overview of HVIT capabilities in providing hypervelocity tests, analyses, MMOD risk assessments and shielding expertise. HVIT personnel work closely with NASA program and safety/mission assurance personnel to develop program-specific MMOD protection requirements which are both achievable based on initial risk assessments and will meet overall safety and mission success requirements. HVIT then proceeds with hypervelocity impact testing and hydrocode assessments to update and verify ballistic limit equations used in the MMOD risk assessment. Hypervelocity impact tests are primarily performed at the NASA WSTF Remote Hypervelocity Test Laboratory (RHTL). Other hypervelocity facilities that provide complementary test capabilities are called on when necessary to fill data gaps. The goal of the final pre-flight MMOD risk assessment is to show compliance with MMOD requirements prior to flight. This final assessment will also incorporate changes in the MMOD environment from meteoroid showers and orbital debris breakups. After the mission is flown, post-flight inspections are performed by HVIT to document and trend MMOD damage to returned spacecraft surfaces and hardware. HVIT accomplishments in NASA mission support are described. In addition, current HVIT activities to aid on-going NASA crewed missions and science missions are presented.

Meteoroid↗
NASA NTRS1981

Development and demonstration of manufacturing processes for fabricating graphite/LARC 160 polyimide structural elements

The development and demonstration of manufacturing technologies for the structural application of Celion graphite/LARC-160 polyimide composite material is discussed. Process development and fabrication of demonstration components are discussed. Process development included establishing quality assurance of the basic composite material and processing, nondestructive inspection of fabricated components, developing processes for specific structural forms, and qualification of processes through mechanical testing. Demonstration components were fabricated. The demonstration components consisted of flat laminates, skin/stringer panels, honeycomb panels, chopped fiber compression moldings, and a technology demonstrator segment (TDS) representative of the space shuttle aft body flap.

Frost, R. K.↗
NASA NTRS2008

Using Space Weather Variability in Evaluation the Radiation Environment Specifications for NASA's Constellation Program

Hardware design environments for NASA's Constellation Program-the Vision for Space Exploration program to design and build new vehicles for servicing low Earth orbit and the Moon and beyond-have been developed that are necessarily conservative in nature to assure robust hardware design and development required to build space systems which will meet operational goals in a wide range of space environments, This presentation will describe the rationale used to establish the space radiation and plasma design environments specified for a variety of applications including total ionizing radiation dose, dose rate effects, and spacecraft charging and will compare the design environments with "space weather" variability to evaluate the applicability of the design environments and potential vulnerabilities of the system to extreme space weather events.

Coffey, Victoria N.↗
NASA NTRS1975

A study of low cost approaches to scientific experiment implementation for shuttle launched and serviced automated spacecraft

Cost reductions that can be obtained in experiment instrumentation by the use of standardized electronics and by the relaxation of instrument reliability requirements are studied. The feasibility of using standardized equipment for experiment instrumentation is assessed and a system design approach that most effectively incorporates standardized equipment is developed. The level and form of modularization that is appropriate for the standardized equipment is determined. Mission assurance aspects of instrument development are examined to determine the cost reductions that might be derived from the relaxation of reliability requirements and to formulate a systematic approach to the optimization of mission assurance cost reductions. The results of the analyses are applied to a representative model HEAO payload in order to provide a concrete example of the cost reductions that can be achieved by a standardized approach to the instrument electronics.

Source record↗
NASA NTRS1977

Breadboard Facility

In the sixties, Chrysler was NASA's prime contractor for the Saturn I and IB test launch vehicles. The company installed and operated at Huntsville what was known as the Saturn I/IB Development Breadboard Facility. "Breadboard," means an array of electrical and electronic equipment for performing a variety of development and test functions. This work gave Chrysler a broad capability in computerized testing to assure quality control in development of solid-state electronic systems. Today that division is manufacturing many products not destined for NASA, most of them being associated with the company's automotive line. A major project is production and quality-control testing of the "lean-burn" engine, one that has a built-in Computer to control emission timing, and allow the engine to run on a leaner mixture of fuel and air. Other environment-related products include vehicle emission analyzers. The newest of the line is an accurate, portable solid state instrument for testing auto exhaust gases. The exhaust analyzers, now being produced for company dealers and for service

Source record↗
NASA NTRS2009

A Reference Model for Software and System Inspections. White Paper

Software Quality Assurance (SQA) is an important component of the software development process. SQA processes provide assurance that the software products and processes in the project life cycle conform to their specified requirements by planning, enacting, and performing a set of activities to provide adequate confidence that quality is being built into the software. Typical techniques include: (1) Testing (2) Simulation (3) Model checking (4) Symbolic execution (5) Management reviews (6) Technical reviews (7) Inspections (8) Walk-throughs (9) Audits (10) Analysis (complexity analysis, control flow analysis, algorithmic analysis) (11) Formal method Our work over the last few years has resulted in substantial knowledge about SQA techniques, especially the areas of technical reviews and inspections. But can we apply the same QA techniques to the system development process? If yes, what kind of tailoring do we need before applying them in the system engineering context? If not, what types of QA techniques are actually used at system level? And, is there any room for improvement.) After a brief examination of the system engineering literature (especially focused on NASA and DoD guidance) we found that: (1) System and software development process interact with each other at different phases through development life cycle (2) Reviews are emphasized in both system and software development. (Figl.3). For some reviews (e.g. SRR, PDR, CDR), there are both system versions and software versions. (3) Analysis techniques are emphasized (e.g. Fault Tree Analysis, Preliminary Hazard Analysis) and some details are given about how to apply them. (4) Reviews are expected to use the outputs of the analysis techniques. In other words, these particular analyses are usually conducted in preparation for (before) reviews. The goal of our work is to explore the interaction between the Quality Assurance (QA) techniques at the system level and the software level.

He, Lulu↗