SEARCH · Search NASA

Results for “System Level Verification”

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 235 records · Page 13

All sources NASA NTRS DOE OSTI

NASA NTRS2008

System Engineering on the Use for Ares I,V - the Simpler, the Better

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt & Whitney Rocketdyne Company. The J-2X is an improved higher power version of the original J-2 engine used during the Apollo program. With higher power and updated requirements for safety and performance, the J-2X becomes a new engine using state-of-the-art design methodology, materials and manufacturing processes. The implementation of Systems Engineering (SE) principles enables the rapid J-2X development program to remain aligned with the ARES I and V vehicle programs, Meeting the aggressive development schedule is a challenge. Coordinating the best expertise thai NASA and PWR have to offer requires effectively utilizing resources at multiple sites. This presents formidable communication challenges. SE allows honest and open discussions of issues and problems. This simple idea is often overlooked in large and complex SE programs. Regular and effective meetings linking SE objectives to component designs are used to voice differences of opinions with customer and contractor in attendance so that the best mutual decisions can be made on the shortest possible schedule. Regular technical interchange meetings on secure program wide computer networks and CM processes are effective,in the "Controlled Change" process that exemplifies good SE. Good communication is a key effective SE implementation. The System of Systems approach is the vision of the Orion program which facilitates the establishment of dynamic SE processes at all levels including the engine. SE enables requirements evolution by facilitating organizational and process agility. Flow down and distribution of requirements is controlled by Allocation Reports which breakdown numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements helps eliminate redundancy and potential mistakes inherent m separated systems. Another tool, the Architecture Design Description, is being used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof is in successful program accomplishment. The SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. The Ares I SE system of systems has delivered according to expectations thus far. All major design reviews (SRR. PDR, CDR) have been successfully conducted to satisfy overall program objectives using SE as the basis for accomplishment. The paper describes SE tools and techniques utilized to achieve this success.

Kelly, William↗

NASA NTRS2018

Design Limit Loads and Verification Approach for the TESS Observatory

The Transiting Exoplanet Survey Satellite (TESS) is a NASA Explorer mission. The TESS Observatory is scheduled to launch on Falcon 9 in April 2018. This presentation covers the process used to define and update design limit loads for the observatory, instrument, and components throughout the life of the program. The limit loads that drove the need for a SoftRide isolation system are highlighted. The testing performed to qualify the observatory for launch loads at the instrument and observatory level is also detailed. In addition, exchanges with the launch vehicle provider in terms of loads predictions and hardware for test are discussed along with the associated issues encountered and lessons learned. The loads development and verification success on TESS was a team effort. Orbital ATK is the spacecraft provider, NASA GSFC provides project management and technical oversight, the instrument is managed by MIT Kavli Institute and the instrument cameras are built and tested by MIT Lincoln Laboratory. Since the instrument was designed in parallel with the spacecraft, the instrument design limit loads were developed in partnership with NASA and the instrument team. The three teams collaborated on a regular basis starting in the early design phase and continuing through observatory level testing.

Limit Loads↗

NASA NTRS1977

Wind estimates from cloud motions - Results from Phases I, II and III of an in situ aircraft verification experiment

An experiment is in progress to verify geostationary-satellite-derived cloud-motion wind estimates by in-situ aircraft wind-velocity measurements. One or more low-level aircraft equipped with Inertial Navigation Systems (INS) were used to define the vertical extent and horizontal motion of a cloud and to measure the ambient wind field. A high-level aircraft, also equipped with an INS, took photographs to describe the horizontal extent of the cloud field and to measure cloud motion. To date the experiment has been conducted over tropical oceans and in the western Gulf of Mexico. A total of 60 h have been spent tracking some 40 tropical cumulus and five cirrus clouds. Results for tropical cumulus clouds indicate excellent agreement between the cloud motion and the wind at cloud base. The magnitude of the vector difference between the cloud motion and the cloud-base wind is less than 1.3 m/s for 67% of the cases with track lengths of 1 h or longer. Similarly, the vector differences between the cloud motion and the wind at sub-cloud (150 m), mid-cloud, and cloud-top levels are 1.5, 3.6 and 7.0 m/s, respectively. The cirrus cloud motions agreed best with the mean wind in the cloud layer with a vector difference of about 1.6 m/s.

Hasler, A. F.↗

NASA NTRS1977

Space power system design and development from an economic point of view

The concept of a satellite solar power system offers a feasible, but unproven, long-range energy alternative. While the basic physics of these systems is understood, many developments are necessary in order to reduce the system cost to the point of being cost-competitive with alternative energy sources. Thus, a substantial technology advancement and verification program, plus test and demonstration satellite programs are necessary before a full-scale satellite can be designed and built. It is important to properly identify those elements of the technology that should be subject to development efforts, the goals of the corresponding development programs and the appropriate funding levels and schedules. Systems studies and designs play a major role in rationally formulating a development program. This paper uses an economic approach to place these studies into a framework for formulating a viable satellite solar power system development plan.

Hazelrigg, G. A., Jr.↗

NASA NTRS2006

Inspection and Verification of Domain Models with PlanWorks and Aver

When developing a domain model, it seems natural to bring the traditional informal tools of inspection and verification, debuggers and automated test suites, to bear upon the problems that will inevitably arise. Debuggers that allow inspection of registers and memory and stepwise execution have been a staple of software development of all sorts from the very beginning. Automated testing has repeatedly proven its considerable worth, to the extent that an entire design philosophy (Test Driven Development) has been developed around the writing of tests. Unfortunately, while not entirely without their uses, the limitations of these tools and the nature of the complexity of models and the underlying planning systems make the diagnosis of certain classes of problems and the verification of their solutions difficult or impossible. Debuggers provide a good local view of executing code, allowing a fine-grained look at algorithms and data. This view is, however, usually only at the level of the current scope in the implementation language, and the data-inspection capabilities of most debuggers usually consist of on-line print statements. More modem graphical debuggers offer a sort of tree view of data structures, but even this is too low-level and is often inappropriate for the kinds of structures created by planning systems. For instance, god or constraint networks are at best awkward when visualized as trees. Any any non-structural link between data structures, as through a lookup table, isn't captured at all. Further, while debuggers have powerful breakpointing facilities that are suitable for finding specific algorithmic errors, they have little use in the diagnosis of modeling errors.

Bedrax-Weiss, Tania↗

NASA NTRS1996

V&V Within Reuse-Based Software Engineering

Verification and Validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission-critical software. V&V is a systems engineering discipline that evaluates the software in a systems context, and is currently applied during the development of a specific application system. In order to bring the effectiveness of V&V to bear within reuse-based software engineering, V&V must be incorporated within the domain engineering process.

Addy, Edward A.↗

NASA NTRS2018

Space System Verification Approach Based on MEAL and Mission Risk Posture

There is no "one size fits all" solution for verifying space avionics systems to ensure safety and mission success. This paper presents a verification approach based on MEAL and risk posture for space systems. MEAL refers to Mission, mission Environment, Application, and Lifetime of the application. In addition to the description of the verification approach, the paper also provides the awareness of the different levels of risks associated with verification tests and inspections when performed at part-, board- and box-level, and discusses the applications of the approach for flight heritage verification, commercial off the shelf (COTS) verification and radiation-effects verification.

Mission Environment Application and Lifetime (MEAL↗

NASA NTRS2018

Space System Verification Approach Based on MEAL and Mission Risk Posture

Mission Environment Application and Lifetime (MEAL↗

NASA NTRS1982

Development of a static feed water electrolysis system

A one person level oxygen generation subsystem was developed and production of the one person oxygen metabolic requirements, 0.82 kg, per day was demonstrated without the need for condenser/separators or electrolyte pumps. During 650 hours of shakedown, design verification, and endurance testing, cell voltages averaged 1.62 V at 206 mA/sq cm and at average operating temperature as low as 326 K, virtually corresponding to the state of the art performance previously established for single cells. This high efficiency and low waste heat generation prevented maintenance of the 339 K design temperature without supplemental heating. Improved water electrolysis cell frames were designed, new injection molds were fabricated, and a series of frames was molded. A modified three fluid pressure controller was developed and a static feed water electrolysis that requires no electrolyte in the static feed compartment was developed and successfully evaluated.

Schubert, F. H.↗

NASA NTRS2012

Model-Based Verification and Validation of Spacecraft Avionics

Our simulation was able to mimic the results of 30 tests on the actual hardware. This shows that simulations have the potential to enable early design validation - well before actual hardware exists. Although simulations focused around data processing procedures at subsystem and device level, they can also be applied to system level analysis to simulate mission scenarios and consumable tracking (e.g. power, propellant, etc.). Simulation engine plug-in developments are continually improving the product, but handling time for time-sensitive operations (like those of the remote engineering unit and bus controller) can be cumbersome.

Systems Modeling Language (SysML↗

NASA NTRS2020

Environmental Verification of NASA’s Europa Clipper Mission

NASA’s Jet Propulsion Laboratory (JPL) and its partner are planning a mission to explore an icy moon of Jupiter, Europa. The objective of the planned Europa Clipper mission is to gain insight into the key ingredients for this potentially habitable world. This mission will conduct investigations using a suite of remote sensing and in-situ fields and particles instruments, and a two-channel ice-penetrating radar. Among its science objectives are to produce high-resolution images of Europa's surface, determine its composition, look for signs of recent or ongoing activity, measure the thickness of the ice shell, search for subsurface lakes, and determine the depth and salinity of Europa's ocean. Europa Clipper is expected to encounter very challenging environments. These environments include radiation, dynamics, thermal, and electromagnetics, which have been translated into a set of environmental requirements that are levied onto the Europa Clipper flight system design. This paper describes how the environmental requirements are specified and verified for each flight component and at which level of integration. A couple of examples will be provided to illustrate the process by which a comprehensive set of verification activities is specified and performed for individual subsystems and instruments to ensure mission success.

Man, Kin Fung↗

DOE OSTI2025

PROACTIVE FA4: Progress Update 2024

The Priority Research Objectives for Arms Control Technology Innovation, Verification, and Evaluation (PROACTIVE) venture’s overall goal is to address the technical challenges that will “enable the negotiation and implementation of future nuclear arms limitation/reduction treaties with verification at the level of individual warheads by advancing the state of the art in verification and monitoring capabilities.” One of the four focus areas of the venture, Focus Area 4 (FA4), is a system-of-systems effort to establish methodologies for the integration of monitoring and verification (M&V) technologies into verification systems that support treaty objectives.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗

NASA NTRS2014

Spot: A Programming Language for Verified Flight Software

The C programming language is widely used for programming space flight software and other safety-critical real time systems. C, however, is far from ideal for this purpose: as is well known, it is both low-level and unsafe. This paper describes Spot, a language derived from C for programming space flight systems. Spot aims to maintain compatibility with existing C code while improving the language and supporting verification with the SPIN model checker. The major features of Spot include actor-based concurrency, distributed state with message passing and transactional updates, and annotations for testing and verification. Spot also supports domain-specific annotations for managing spacecraft state, e.g., communicating telemetry information to the ground. We describe the motivation and design rationale for Spot, give an overview of the design, provide examples of Spot's capabilities, and discuss the current status of the implementation.

validation↗

NASA NTRS2019

SAFE50 Reference Design Study for Large-Scale High-Density Low-Altitude UAS Operations in Urban Areas

Enabling safe, routine, and high-density flight operations of small UAS at low-altitude over heavily populated urban centers presents a difficult challenge for emerging UAS Traffic Management (UTM) system concepts. Urban operations by definition involve flight over people, property, and infrastructure. Low-altitude urban environments - such as urban canyons â€“ are one of the most difficult areas for UTM to consider. Mission concepts require routine operations in a cluttered radio-frequency (RF) environment with degraded or denied Global Positioning System (GPS) reception. Flights with any appreciable distance will be beyond visual and communications line-of-sight from ground operators. Timely detection and response to emergencies and onboard failures, which is critical for safe aircraft operation, will be difficult. This work seeks to establish a feasible reference autonomy architecture for autonomous vehicles in an urban UTM system, then verifying and validating this architecture within a complete UTM concept point-design and systems analysis study. In this paper, we present the results from the NASA SAFE50 conceptual design and systems study that investigates the trade-space of urban UTM operations. This advanced conceptual design study develops a feasible, verified, validated point-design solution. The SAFE50 point-design concept places emphasis on advanced, highly-autonomous, and highly-capable vehicles that favors intelligent onboard autonomy over direct human control with today's technologies and operating in today's urban environments. This paper focuses on an general overview of the design study, highlighting decisions made in the architectural solution. This paper will presents a summary of the study, architectures, and requirements. We present an overview of the architecture designs as derived from the top-level UTM system. The point-design has been implemented in both simulation and through flight testing of hardware design prototypes. The results from simulation and flight testing as part of the verification and validation process of the reference design study.

Ippolito, Corey A.↗

NASA NTRS2019

Psyche Early Project Verification & Validation Planning Development

The Psyche mission to the asteroid (16) Psyche was selected as the fourteenth mission in the Discovery program in January 2017. The Psyche mission will determine if (16) Psyche is the core of a larger differentiated body. As part of the development of this mission a Verification and Validation (V&V) engineer was assigned early in the project’s design Phase B. This paper will discuss some of the strategies that the Psyche team is using to take full advantage of the early planning for V&V on flight projects and specifically how the Psyche mission is approaching these tasks. This paper will discuss the effects of having a V&V mindset on: 1) The Psyche requirements development process, and how focusing not only on how the team will verify these requirements but also on developing the tools necessary to track and monitor that verification feeds back into the requirement development process. 2) The Psyche testbed development, and how using a verification mindset is useful for identifying holes in the testbed development process, including the required testbed speed and how to think about testbed certification early in the process while encouraging trades and developing relationships with the testbed team. 3) Developing new V&V Tools for Psyche, and how developing tools early in the project development process means that they can influence the development of other requirement and scheduling tools. 4) Verification Activity Planning, which is typically done to a preliminary level during Phase B of the project, and is important for understanding the major testing that is needed to ensure that the system as built represents the design. On Psyche we are not only focused on bringing this planning to a preliminary level, we are also developing a V&V focused schedule to help us de-conflict V&V activities that may require similar resources early on in the program’s development. 5) Validation Planning, for which we are working with the testbed and model development teams to ensure that their models can be effectively validated and that the plans to do so are in place. In this paper we will describe how the Psyche mission is approaching each of these V&V areas and identify lessons that can be taken by other space missions trying to decide how much effort should be put into V&V early in the project lifecycle.

Solish, Benjamin↗

NASA NTRS2016

James Webb Space Telescope (JWST) Integrated Science Instruments Module (ISIM) Cryo-Vacuum (CV) Test Campaign Summary

JWST Integrated Science Instruments Module (ISIM) completed its system-level space simulation testing program at the NASA Goddard Space Flight Center (GSFC). In March 2016, ISIM was successfully delivered to the next level of integration with the Optical Telescope Element (OTE), to form OTIS (OTE + ISIM), after concluding a series of three cryo-vacuum (CV) tests. During these tests, the complexity of the mission has generated challenging requirements that demand highly reliable system performance and capabilities from the Space Environment Simulator (SES) vacuum chamber. The first test served as a risk reduction test; the second test provided the initial verification of the fully-integrated flight instruments; and the third test verified the system in its final flight configuration following mechanical environmental tests (vibration and acoustics). From one test to the next, shortcomings of the facility were uncovered and associated improvements in operational capabilities and reliability of the facility were required to enable the project to verify system-level requirements. This paper: (1) provides an overview of the integrated mechanical and thermal facility systems required to achieve the objectives of JWST ISIM testing, (2) compares the overall facility performance and instrumentation results from the three ISIM CV tests, and (3) summarizes lessons learned from the ISIM testing campaign.

Yew, Calinda↗

NASA NTRS2011

Achieving Maximum Integration Utilizing Requirements Flow Down

A robust and experienced systems engineering team is essential for a successful program. It is often a challenge to build a core systems engineering team early enough in a program to maximize integration and assure a common path for all supporting teams in a project. Ares I was no exception. During the planning of IVGVT, the team had many challenges including lack of: early identification of stakeholders, team training in NASA s system engineering practices, solid requirements flow down and a top down documentation strategy. The IVGVT team started test planning early in the program before the systems engineering framework had been matured due to an aggressive schedule. Therefore the IVGVT team increased their involvement in the Constellation systems engineering effort. Program level requirements were established that flowed down to IVGVT aligning all stakeholders to a common set of goals. The IVGVT team utilized the APPEL REQ Development Management course providing the team a NASA focused model to follow. The IVGVT team engaged directly with the model verification and validation process to assure that a solid set of requirements drove the need for the test event. The IVGVT team looked at the initial planning state, analyzed the current state and then produced recommendations for the ideal future state of a wide range of systems engineering functions and processes. Based on this analysis, the IVGVT team was able to produce a set of lessons learned and to provide suggestions for future programs or tests to use in their initial planning phase.

Archiable, Wes↗

NASA NTRS1991

Experimental verification of nanometer level optical pathlength control on a flexible structure

This paper describes an experimental facility being developed for demonstration and validation of control concepts arising out of NASA's Control Structure Interaction program. The facility is meant to be a ground testbed with relevance to a broad class of precision optical space systems. The objective of the experimental program is to investigate a multilayer control approach to the maintenance of nanometer-level optical pathlength stability in the presence of external disturbances and multiple structural resonances. The facility is designed to explore the effect of applying, separately and in combinations, structural vibration suppression, vibration isolation, and active optical articulation. This paper describes the testbed facility, the structure, optics, sensors, actuators, and real-time computer and program development environment. Initial optical articulation experimental results are presented.

O'Neal, Michael↗