Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “verification and validation”

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 505 records · Page 28

Adaptation of a software development methodology to the implementation of a large-scale data acquisition and control system

A progress report is presented on a program to upgrade the existing NASA Deep Space Network in terms of a redesigned computer-controlled data acquisition system for channelling tracking, telemetry, and command data between a California-based control center and three signal processing centers in Australia, California, and Spain. The methodology for the improvements is oriented towards single subsystem development with consideration for a multi-system and multi-subsystem network of operational software. Details of the existing hardware configurations and data transmission links are provided. The program methodology includes data flow design, interface design and coordination, incremental capability availability, increased inter-subsystem developmental synthesis and testing, system and network level synthesis and testing, and system verification and validation. The software has been implemented thus far to a 65 percent completion level, and the methodology being used to effect the changes, which will permit enhanced tracking and communication with spacecraft, has been concluded to feature effective techniques.

Madrid, G. A.↗

Software control and system configuration management - A process that works

A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

Petersen, K. L.↗

Flight test experience and controlled impact of a large, four-engine, remotely piloted airplane

A controlled impact demonstration (CID) program using a large, four engine, remotely piloted transport airplane was conducted. Closed loop primary flight control was performed from a ground based cockpit and digital computer in conjunction with an up/down telemetry link. Uplink commands were received aboard the airplane and transferred through uplink interface systems to a highly modified Bendix PB-20D autopilot. Both proportional and discrete commands were generated by the ground pilot. Prior to flight tests, extensive simulation was conducted during the development of ground based digital control laws. The control laws included primary control, secondary control, and racetrack and final approach guidance. Extensive ground checks were performed on all remotely piloted systems. However, manned flight tests were the primary method of verification and validation of control law concepts developed from simulation. The design, development, and flight testing of control laws and the systems required to accomplish the remotely piloted mission are discussed.

Kempel, R. W.↗

Some key considerations in evolving a computer system and software engineering support environment for the space station program

The space station data management system involves networks of computing resources that must work cooperatively and reliably over an indefinite life span. This program requires a long schedule of modular growth and an even longer period of maintenance and operation. The development and operation of space station computing resources will involve a spectrum of systems and software life cycle activities distributed across a variety of hosts, an integration, verification, and validation host with test bed, and distributed targets. The requirement for the early establishment and use of an apporopriate Computer Systems and Software Engineering Support Environment is identified. This environment will support the Research and Development Productivity challenges presented by the space station computing system.

Mckay, C. W.↗

X-29A technology demonstrator flight test program overview

An overview of the X-29A functional flight program and concept evaluation program is presented, including some of the unique and different preparations for the first flight. Included are a discussion of the many organizational responsibilities and a description of the program management structure for the test team. Also discussed are preflight ground, flight functional envelope expansion, and flight research test objectives and qualitive results to date for both a limited-envelope flight control system and an expanded-envelope system. The aircraft, including the instrumentation system and measurements, is described. In addition, a discussion is included regarding the use of major support facilities, such as ground and flight simulators, the NASA Western Aeronautical Test Range and mission control center, and the Grumman automated telemetry station. An overview of the associated real-time and postflight batch data processing software approaches is presented. The use of hardware-in-the-loop simulation for independent verification and validation and mission planning and practice is discussed. Also included is a description of the flight-readiness review, the airworthiness and flight safety review, work scheduling, technical briefings, and preflight and postflight crew briefings. The configuration control process used on the X-29A program is described, and its relationship to both simulation and aircraft operations is discussed. An X-29A schedule overview is presented with an outline of a proposed follow-on program.

Sefic, W. J.↗

Near field to far field transformations and multiple beam forming and steering

The feasibility of acoustic verification of microwave near field to far field transformation algorithms using the Phased Array Sonic Simulation System was studied. Existing electromagnetic near field measurement techniques and transformation algorithms (equations) were investigated. It was analytically determined that acoustic verification is valid. Acoustic simulation of electromagnetic near field to far field transformations is emphasized. The acoustic simulation of electromagnetic near field to far field transformation is verified for the modal expansion method. In the modal expansion method, data from antenna near field measurements are converted to a summation or spectrum of modes corresponding to wave numbers in the measurement coordinate system. Fourier transformation of those measurements preserves the far field information in a spectral form that is then readily extractable.

Source record↗

Investigation of an advanced fault tolerant integrated avionics system

Presented is an advanced, fault-tolerant multiprocessor avionics architecture as could be employed in an advanced rotorcraft such as LHX. The processor structure is designed to interface with existing digital avionics systems and concepts including the Army Digital Avionics System (ADAS) cockpit/display system, navaid and communications suites, integrated sensing suite, and the Advanced Digital Optical Control System (ADOCS). The report defines mission, maintenance and safety-of-flight reliability goals as might be expected for an operational LHX aircraft. Based on use of a modular, compact (16-bit) microprocessor card family, results of a preliminary study examining simplex, dual and standby-sparing architectures is presented. Given the stated constraints, it is shown that the dual architecture is best suited to meet reliability goals with minimum hardware and software overhead. The report presents hardware and software design considerations for realizing the architecture including redundancy management requirements and techniques as well as verification and validation needs and methods.

Dunn, W. R.↗

Flight test experience and controlled impact of a large, four-engine remotely piloted airplane

A controlled impact demonstration (CID) program using a large, four engine, remotely piloted transport airplane was conducted. Closed loop primary flight control was performed from a ground based cockpit and digital computer in conjunction with an up/down telemetry link. Uplink commands were received aboard the airplane and transferred through uplink interface systems to a highly modified Bendix PB-20D autopilot. Both proportional and discrete commands were generated by the ground pilot. Prior to flight tests, extensive simulation was conducted during the development of ground based digital control laws. The control laws included primary control, secondary control, and racetrack and final approach guidance. Extensive ground checks were performed on all remotely piloted systems. However, manned flight tests were the primary method of verification and validation of control law concepts developed from simulation. The design development, and flight testing of control laws and the systems required to accomplish the remotely piloted mission are discussed.

Kempel, R. W.↗

Identification of large space structures: A state-of-practice report

An outline of this work is presented. It begins with a schematic flow diagram and a logical flow diagram of the identification process for large space structures (LSS). Next, the task is defined by a structure model definition. A matrix polynomial formulation with a node displacement equation and a state variable formulation with node displacement and velocities are outlined. Further outlined is the identification of LSS on orbit; modeling errors and uncertainties; verification and validation of model; and noise, computations, and data collection.

Source record↗

The fault-tolerant multiprocessor computer

The development and evaluation of fault-tolerant computer architectures and software-implemented fault tolerance (SIFT) for use in advanced NASA vehicles and potentially in flight-control systems are described in a collection of previously published reports prepared for NASA. Topics addressed include the principles of fault-tolerant multiprocessor (FTMP) operation; processor and slave regional designs; FTMP executive, facilities, acceptance-test/diagnostic, applications, and support software; FTM reliability and availability models; SIFT hardware design; and SIFT validation and verification.

Smith, T. B., III↗

Practical aspects of achieving accurate radiometric field measurements

This paper provides practical advice for investigators new to the field of high accuracy radiometric experiments. Sources typically used for calibrating land reflectance measurement instruments are identified, and some special considerations for their use are highlighted. The physical nature of the processes determining the output of these sources is emphasized, and an estimate of the typical calibration accuracies achieved with these sources is described. Several techniques for the validation and verification of instrument characterization are reviewed. Experiment design of the Backscattered Ultraviolet Spectrometer (BUV) and the Earth Radiation Budget Experiment (ERBE) are introduced as successful mission designs for accomplishing high accuracy radiation measurements from space. The goal of this paper is to introduce reasoning developed in other missions to experiments devoted to sensing the earth's surface and near surface.

Guenther, B.↗

KBS V and V as related to automation of space station subsystems: Rationale for a KBS lifecycle

The role of verification and validation (V and V) in software has been to support and strengthen the software lifecycle and to ensure that the resultant code meets the standards of the requirements document. Knowledge based systems (KBS) V and V should serve the same role, but the KBS lifecycle is ill-defined. Here, the rationale of the simple form of the KBS lifecycle is explained. Special KBS development requirements are accommodated where possible by modifications to the traditional software lifecycle. Research areas are suggested for those aspects which present new or unusual difficulties for V and V.

Richardson, K.↗

Methodology requirements for intelligent systems architecture

The methodology required for the development of the 'intelligent system architecture' of distributed computer systems which integrate standard data processing capabilities with symbolic processing to provide powerful and highly autonomous adaptive processing capabilities must encompass three elements: (1) a design knowledge capture system, (2) computer-aided engineering, and (3) verification and validation metrics and tests. Emphasis must be put on the earliest possible definition of system requirements and the realistic definition of allowable system uncertainties. Methodologies must also address human factor issues.

Grant, Terry↗

Software engineering environment tool set integration

Space Transportation System Division (STSD) Engineering has a program to promote excellence within the engineering function. This program resulted in a capital funded facility based on a VAX cluster called the Rockwell Operational Engineering System (ROSES). The second phase of a three phase plan to establish an integrated software engineering environment for ROSES is examined. It discusses briefly phase one which establishes the basic capability for a modern software development environment to include a tool set, training and standards. Phase two is a tool set integration. The tool set is primarily off-the-shelf tools acquired through vendors or government agencies (public domain). These tools were placed into categories of software development. These categories are: requirements, design, and construction support; verification and validation support; and software management support. The integration of the tool set is being performed through concept prototyping and development of tools specifically designed to support the life cycle and provide transition from one phase to the next.

Selfridge, William P.↗

Extending the granularity of representation and control for the MIL-STD CAIS 1.0 node model

The Common APSE (Ada 1 Program Support Environment) Interface Set (CAIS) (DoD85) node model provides an excellent baseline for interfaces in a single-host development environment. To encompass the entire spectrum of computing, however, the CAIS model should be extended in four areas. It should provide the interface between the engineering workstation and the host system throughout the entire lifecycle of the system. It should provide a basis for communication and integration functions needed by distributed host environments. It should provide common interfaces for communications mechanisms to and among target processors. It should provide facilities for integration, validation, and verification of test beds extending to distributed systems on geographically separate processors with heterogeneous instruction set architectures (ISAS). Additions to the PROCESS NODE model to extend the CAIS into these four areas are proposed.

Rogers, Kathy L.↗

Real-time application of knowledge-based systems

The Rapid Prototyping Facility (RPF) was developed to meet a need for a facility which allows flight systems concepts to be prototyped in a manner which allows for real-time flight test experience with a prototype system. This need was focused during the development and demonstration of the expert system flight status monitor (ESFSM). The ESFSM was a prototype system developed on a LISP machine, but lack of a method for progressive testing and problem identification led to an impractical system. The RPF concept was developed, and the ATMS designed to exercise its capabilities. The ATMS Phase 1 demonstration provided a practical vehicle for testing the RPF, as well as a useful tool. ATMS Phase 2 development continues. A dedicated F-18 is expected to be assigned for facility use in late 1988, with RAV modifications. A knowledge-based autopilot is being developed using the RPF. This is a system which provides elementary autopilot functions and is intended as a vehicle for testing expert system verification and validation methods. An expert system propulsion monitor is being prototyped. This system provides real-time assistance to an engineer monitoring a propulsion system during a flight.

Brumbaugh, Randal W.↗

Fly-by-light flight control system technology development plan

The results of a four-month, phased effort to develop a Fly-by-Light Technology Development Plan are documented. The technical shortfalls for each phase were identified and a development plan to bridge the technical gap was developed. The production configuration was defined for a 757-type airplane, but it is suggested that the demonstration flight be conducted on the NASA Transport Systems Research Vehicle. The modifications required and verification and validation issues are delineated in this report. A detailed schedule for the phased introduction of fly-by-light system components has been generated. It is concluded that a fiber-optics program would contribute significantly toward developing the required state of readiness that will make a fly-by-light control system not only cost effective but reliable without mitigating the weight and high-energy radio frequency related benefits.

Chakravarty, A.↗

Development of an Automated Requirements Management System for the Space Station Freedom Program

The Automated Requirements Management System, which is being developed to support traceability and documentation of Space Station Freedom requirements, is described. The objectives of requirements management are validation and verification. Other benefits include comprehensive analytical capabilities, commonality and timeliness of requirements information availability across the program, and the reduction of information duplication and overlap.

Giffin, Geoff↗