Showing papers on "Acceptance testing published in 1997"

Computerized adaptive testing: From inquiry to operation.

Abstract: Introduction to ASVAB and CAT Policy and Programme Management Perspective, R&D Laboratory Management Perspective Technical Perspective Research Antecedents of Applied Adaptive Testing The Marine Corps Exploratory Development Project - 1977-1982 The Computerized Adaptive Screening Test Preliminary Psychometric Research for CAT-ASVAB - Selecting an Adaptive Testing Strategy Development of the Experimental CAT-ASVAB System Validation of the experimental CAT-ASVAB System Item Pool Development and Evaluation Psychometric Procedures for Administering CAT-ASVAB Item Exposure Control in CAT-ASVAB ACAP Hardware Selection, Software Development and Acceptance Testing Human Factors in the CAT System - A Pilot Study Evaluating Item Calibration Medium in Computerized Adaptive Testing Reliability and Construct Validity of CAT-ASVAB Evaluating the Predictive Validity of CAT-ASVAB Equating the CAT-ASVAB CAT-ASVAB Operational Test and Evaluation Development of a System for Nationwide Implementation The Psychometric Comparability of Computer Hardware CAT-ASVAB Cost and Benefit Analyses Expanding the Content of CAT-ASVAB - New Tests and Their Validity Dissemination of CAT-ASVAB Technology Current and Future Challenges.

Adequate Testing of Component-Based Software

Abstract: People have long advocated a component-based approach to software construction as a way of simplifying the design and maintenance of large software systems, increasing the opportunities for reuse, and increasing software development productivity. Although the technology for constructing component-based software is relatively advanced, we lack a sufficient theoretical basis for testing component-based software. This paper initiates the development of such a theory. The main result is a formal definition of the concept C-adequate-forfor adequate unit testing of a component and the concept C-adequateon-M for adequate integration testing of a component-based system. The paper uses these concepts to discuss practical considerations in adequate testing of component-based software.

Computer system and computer implemented process for performing user-defined tests of a client-server system with run time compilation of test results

Abstract: The present invention provides a client application to measure the performance, reliability or security of a system under test, based on user-defined loads to be applied to the system under test. In the present invention, a test may be performed simultaneously on several servers and applications. As the test progresses, results are compiled during run time and visual feedback is provided. By allowing a user to define the test, and by providing run time compilation of results, the present invention can be used for capacity planning. Stopped or truncated tests still provide relevant results. The application also may allow acceptance criteria to be analyzed during the run time of test. Finally, the number of users simulated may be regulated by the application.

Software requirements and acceptance testing

Abstract: In this paper we 1) review industry acceptance testing practices and 2) present a systematic approach to scenario analysis and its application to acceptance testing with the aim to improve the current practice. It summarizes the existing practice into categories and identifies the serious weakness. Then, a new approach based on the formal scenario analysis is presented. It is systematic, and easily applicable to any software or system. A simple, yet realistic example is used to illustrate its effectiveness. Finally, its benefits and its applicability are summarized.

How assertions can increase test effectiveness

Abstract: Novel views of mature ideas on software and quality productivity are presented. The author investigates the nature of object oriented development and what it says about the nature of testing techniques. Specifically, he explores an approach to assertion placement based on error masking. As expected, he found that information hiding and encapsulation can be detrimental to system level and integration testing, but not always.

A study of user acceptance tests

Abstract: The user acceptance test (UAT) is the final stage of testing in application software development. When testing results meet the acceptance criteria, the software system can be released for operational use.This paper first compares the different testing phases of software development (i.e. unit test, integration test, system test and UAT) in terms of important testing elements so as to highlight the uniqueness of UAT relative to the other test phases. Then, we describe several approaches for acceptance test, including the behaviour-based approach, the black-box strategy and a new UAT strategy called operation-based testing. The new strategy uses the operational profile for testing purposes, includes a well-defined acceptance criteria, and satisfies the test requirements of ISO9001 standards.

Current signatures for IDDQ testing

Abstract: A method of using static power supply current in response to test vectors for acceptance testing and defect diagnosis of CMOS integrated circuit die. Testing is based on comparison of two or more power supply current measurements from the die under test. Defect diagnosis is based on characterizing a defect by one or more current levels produced by the circuit in the presence of the defect.

Acceptance Criteria for Critical Software Based on Testability Estimates and Test Results

Abstract: Testability is defined as the probability that a program will fail a test, conditional on the program containing some fault. In this paper, we show that statements about the testability of a program can be more simply described in terms of assumptions on the probability distribution of the failure intensity of the program. We can thus state general acceptance conditions in clear mathematical terms using Bayesian inference. We develop two scenarios, one for software for which the reliability requirements are that the software must be completely fault-free, and another for requirements stated as an upper bound on the acceptable failure probability.

Introduction to software reliability engineering and testing

Abstract: Software testing often results in delays to market and high cost without assuring product reliability. Software reliability engineering can be applied to carefully engineer testing to overcome these weaknesses. This application is often referred to as software-reliability-engineered testing. We present several case studies illustrating the application of software reliability engineering to testing. We take a quick overview of the field, to better understand the terms used and procedures discussed in the case studies.

The economics of system-level testing

Abstract: Competitive pressure to streamline system-level test without affecting product quality is mounting. Identifying the features unique to system-level testing, the authors present key results of production testing based on a new test cost model.

Software reliability in weapon systems

Abstract: Summary form only given, as follows. The Air Force Operational Test and Evaluation Center (AFOTEC) is responsible for the operational testing of application software used in weapon systems. In order to determine if a system is ready for operational testing, raw data from unit and integration testing is analyzed to determine if the software is exhibiting maturity and reliability growth. A graphical tool containing a library of widely accepted software reliability growth models then selects the optimum model by first subjecting the data to goodness of fit criterion and then prequential likelihood as a measure of predictive strength. The intent is to use this data with operational profiles to determine the expected software reliability for a given system operational mission.

Construction of the FORS Focal Reducer/Spectrographs: status report and first test results

Abstract: The hardware construction of FORS1, the first of the two focal reducer/low dispersion spectrographs of the ESO very large telescope (VLT), is now finished. An extensive testing program is under way which will guarantee that the instrument is fully understood and well calibrated when it will be installed at the Cassegrain focus of the first unit telescope of the VLT in 1998. This program includes a full characterization of the optical system and the evaluation of the setting accuracies and reproducibility of the numerous electromechanical functions as well as testing the flexure compensation which will minimize image shift during telescope motions. Telescope and star simulators were specially built for this purpose in order to test the optical and mechanical behavior of the instrument on the 8 m-telescope. Acceptance tests of the optical performance and the subsystem tests of all electromechanical functions indicate an excellent quality, especially for the complex multi object spectroscopy unit, while the overall system tests are just starting.

Object-Oriented Testing

Abstract: In contrast to the explosion of activity in object-oriented design and programming, relatively little attention has been given to object testing. The proposed tutorial discusses problems and potential solutions with the testing of object-oriented software. After a brief introduction in which the testing of 00 software is compared with the testing of more traditional software, an in-depth look is taken at two approaches to the testing of 00 software. The first is a method for the testing of 00 systems that is used by MPR Teltech, a Canadian telecommunications company. In this method, the ACE tool is used to automatically test individual classes. The second is the ClassBench methodology and framework for the testing of collection classes, which has been used to test several classes from commercial class libraries.

One strategy of accelerated testing technique

Abstract: Strategic, theoretical and experimental bases are developed for accelerated testing technique using physical modeling in the laboratory to demonstrate the influence of mechanical and environmental factors under operating conditions. This combination permits the acceleration testing and evaluation of the dynamics of reliability and other aspects of quality.

Selecting Parameters and Limits for Equipment Operational Qualification

Abstract: While operational qualification (OQ) is a well-established term within equipment qualification, users of equipment often become unsure when it comes to implementation. The biggest problem is how to select procedures and acceptance criteria. Should these be the vendor's specifications or should the users define their own limits, and, if so, how? Should all instruments of the same type have the same values or should these be optimized for each individual instrument? This article will provide an overall strategy and specific examples for HPLC on how to select procedures and acceptance limits that are based on efficient use of resources, on practicality and on the intended use of the equipment.

Measuring requirements testing: experience report

Abstract: Requirements are written to completed software system. Linda Rosenberg, Ph.D. Unisys Federal Systems Code 300.1 Greenbelt, h4D 207712 spec@ the functionality of a Software systems are often released in segments called builds, each one adding new functionality and satisfying an additional set of requirements. New software requirements tools are allowing quality assurance engineers to develop and use new metrics to assist them in evaluating the relationships of requirements to tests, thus ensuring the required functionality in the new system. NASA‘s Goddard Space Flight Center is applying new tools and technology to measure the effectiveness of requirements testing. This paper discusses an effort that uses project data to demonstrate metrics effectiveness.

Aspects of performance assessment of whole body imaging systems.

Abstract: Regular quality control is one of the cornerstones of nuclear medicine and a prerequisite for adequate diagnostic imaging. Many papers have been published on quality control of planar and tomographic imaging systems. Up to now, however, only minor attention has been given to the assessment of the performance of whole body imaging systems. In this paper we present a comprehensive set of test procedures including acceptance testing and regular quality control. It is not our purpose to present a thorough analysis of the methods and results. The selection of the tests is discussed and the tests are described; some results are presented. In addition action thresholds are proposed. The quality control tests can be applied to systems with either a moving detector or a moving imaging table, and to both detectors with a large field of view and detectors with a small field of view. The tests presented in this paper do not require special phantoms or sources other than those used for quality control of stationary gamma cameras. They can be applied for acceptance testing and for performance testing in a regular quality assurance programme.

Lessons Learned from Fifteen Years of Cleanroom Testing

Abstract: This paper describes lessons learned through fifteen years of applying the Cleanroom software engineering approach. It focuses on the real-life practice of Cleanroom testing, rather than on a rigid ideal or orthodoxy. Although Cleanroom still recommends that development teams devote most of their testing effort to statistical testing (in concert with verification-based inspections and other development techniques), we also recognize the value of other formal testing techniques. This paper will look at practical techniques for defining the expected usage of the software under development, modeling that usage with software tools, generating test scenarios, and interpreting outcomes. Then, we will describe how statistical testing can work together with other testing strategies to cover the quality assurance spectrum.

International Space Station nickel-hydrogen battery cell testing at NAVSURFWARCENDIV Crane

Abstract: Testing for the International Space Station nickel-hydrogen battery cell test program began in 1990 at Crane Division, Naval Surface Warfare Center (NAVSURFWARCENDIV Crane). The purpose of the testing is to develop a statistically significant nickel-hydrogen database. The program has included acceptance testing, characterization testing, random vibration, life cycle testing and failure analysis of nickel-hydrogen battery cells. The program is directed by the Electrochemistry Branch at NASA Lewis Research Center. Over 400 nickel-hydrogen individual pressure vessel cells and one 22 cell single pressure vessel battery have been received for testing representing varying designs from four separate manufacturers; Yardney Technical Products (Yardney), Eagle-Picher Industries (EPI), Gates Energy Produces (Gates) and SAFT. This report is meant to provide an update of the results of the testing and the current status since the beginning of the program.

PACS component testing: beta and acceptance testing

Abstract: The functionality and performance expectations of all PACS components must be specified at the time of purchase and tested completely upon delivery to assure customer satisfaction and successful adoption of the new technology. This process may be more elaborate if the customer agrees to serve as a Beta test site for a new component or a new revision of an existing component.A carefully designed test plan will save time at installation, will allow the customer and vendor to agree on expectations, and will assure that the installation will proceed as planned. This paper describes the test procedure used at the University of Florida to accept each PACS component, either a commercial product, or one developed in house. A set of documents contain descriptions of the pre-installation environment, sets of studies to be used in the test, installation checklist, functional usage reports, subjective evaluations, and problem reporting forms. Training and user documentation is also reviewed and 'help lists' are created to help users perform the most common functions. Although details in the documents are changed to match the type of component being tested, the general form of the test remains the same. A formal procedure for testing the functionality and performance of new equipment can save time for both the vendor and the customer and, if specified at the time of purchase, can serve to document the expectations of the customer. Following these procedures will assure a successful installation and improve customer satisfaction.

Specification-Based Testing of Interactive Systems

Abstract: Achieving correct user interface software is difficult because such software is complex, highly interactive, modeless, concurrent, graphical, and has user-based real-time requirements. In this paper I propose developing a framework for applying formal methods to testing of user interface software. I survey relevant work in the areas of formal development of user interface software and specification-based testing. I then outline a case study based research plan to extend an existing specification-based testing framework to incorporate multiparadigm user interface specifications.

Statistical Quality Control and Reliability Tests

Abstract: Statistical quality control and reliability tests are performed to estimate or demonstrate quality and reliability characteristics on the basis of data collected from sampling tests. Estimation leads to a point or interval estimate of an unknown characteristic. Demonstration is a test of a given hypothesis on the unknown characteristic, often at an acceptance test. Estimation and demonstration of an unknown probability is investigated in Section 7.1 for the case of a defective probability p (fraction of defective items) and applied in Section 7.2.1 to reliability, maintainability, and availability figures. Estimation and demonstration of a constant failure rate λ (or MTBF=1/λ) and of an MTTR are discussed in depth in Sections 7.2.2 and 7.3. Basic models for accelerated tests and for goodness-of-fit tests are considered in Sections 7.4 and 7.5, respectively. Empirical & graphical methods are given in Section 7.5. Some refinement on reliability data analysis are discussed in Section 7.6. To simplify the notation, sample will be used instead of random sample. Theoretical foundations for this chapter are in Appendix A8. A large number of examples illustrate practical aspects.

Automated testing system for switching systems with multiple modules

Abstract: Efficient testing of switching systems is essential to provide new services quickly and to reduce development costs. This paper presents an automated testing system for switching systems with multiple modules. This system allocates hardware resources, which include test equipment and inter-module connector ports, automatically constructs a test environment for each test item, and executes test scripts. It can reduce the complexity of scheduling hardware and setting up the test environment, reduce the testing cycle time, and improve hardware resource utilization. We also show the effects of this system through our experiences developing the NTT's NS8000 Series switching systems.

Acceptance testing, commissioning and quality assurance for a 370 GBq 192Ir HDR brachytherapy afterloader.

Abstract: Proposed methods for the initial source installation tests, acceptance testing and a continuing quality assurance program are presented for a Nucletron-Odelft High Dose-Rate Brachytherapy Afterloader system.

Cassini RTG acceptance test results and RTG performance on Galileo and Ulysses

Abstract: Flight acceptance testing has been completed for the radioisotope thermoelectric generators (RTGs) to be used on the Cassini spacecraft which is scheduled for an October 6, 1997 launch to Saturn. The acceptance test program includes vibration tests, magnetic field measurements, mass properties (weight and c.g.) and a thermal vacuum test. This paper presents the thermal vacuum test results.