scispace - formally typeset
Search or ask a question

Showing papers on "Acceptance testing published in 1985"


Journal ArticleDOI
TL;DR: Why it is necessary to test specifications early in the software life cycle to guarantee a system that meets its critical requirements and that also provides the desired functionality is demonstrated.
Abstract: Formal specification and verification techniques are now apused to increase the reliability of software systems. However, these proaches sometimes result in specifying systems that cannot be realized or that are not usable. This paper demonstrates why it is necessary to test specifications early in the software life cycle to guarantee a system that meets its critical requirements and that also provides the desired functionality. Definitions to provide the framework for classifying the validity of a functional requirement with respect to a formal specification tion are also introduced. Finally, the design of two tools for testing formal specifications is discussed.

193 citations



Journal ArticleDOI
TL;DR: Members of a Subcommittee of the Society of Motion Picture and Television Engineers have developed specifications for an operational test pattern for evaluation of television monitors and film recording cameras used in medical diagnostic imaging.
Abstract: Members of a Subcommittee of the Society of Motion Picture and Television Engineers, with the cooperation of other professional societies, have developed specifications for an operational test pattern for evaluation of television monitors and film recording cameras used in medical diagnostic imaging. The purpose of this test pattern and the associated recommended practice is to provide the users of the medical diagnostic display systems with a comprehensive test for set-up, acceptance testing, and day-to-day operational checks. Details of the test pattern, examples of the system problems diagnosed by use of the pattern, and methods for optimizing display devices with the pattern are presented.

75 citations


Proceedings ArticleDOI
01 Aug 1985
TL;DR: Evidence suggests that it may be possible to use structural coverage to aid in the management of the acceptance test process and evidence that implies that in this environment, faults revealed in a procedure are independent of the number of times the procedure is executed is provided.
Abstract: A large, commercially developed FORTRAN program was modified to produce structural coverage metrics. The modified program was executed on a set of functionally generated acceptance tests and a large sample of operational usage cases. The resulting structural coverage metrics are combined with fault and error data to evaluate structural coverage in the SEL environment.We can show that in this environment the functionally generated tests seem to be a good approximation of operational use. The relative proportions of the exercised statement sub-classes (executable, assignment, CALL, DO, IF, READ, WRITE) changes as the structural coverage of the program increases. We also propose a method for evaluating if two sets of input data exercise a program in a similar manner.We also provide evidence that implies that in this environment, faults revealed in a procedure are independent of the number of times the procedure is executed and that it may be reasonable to use procedure coverage in software models that use statement coverage. Finally, the evidence suggests that it may be possible to use structural coverage to aid in the management of the acceptance test process.

33 citations


Journal ArticleDOI
TL;DR: It is shown how the techniques developed can be used to estimate, prior to the commencement of testing, the optimum allocation of test effort for software which is to be nonuniformly executed in its operational phase.
Abstract: In this paper, an approach to the modeling of software testing is described. A major aim of this approach is to allow the assessment of the effects of different testing (and debugging) strategies in different situations. It is shown how the techniques developed can be used to estimate, prior to the commencement of testing, the optimum allocation of test effort for software which is to be nonuniformly executed in its operational phase. In addition, the question of application of statistical models in cases where the data environment undergoes changes is discussed. Finally, two models are presented for the assessment of the effects of imperfections in the debugging process.

31 citations


ReportDOI
01 Jan 1985
TL;DR: All rights reserved.
Abstract: All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise) without the prior written permission of the publisher. INTRODUCTION 1 PART 1: Principles and characteristics of diagnostic x-3 ray generators and automatic exposure control devices PART 2: Characteristics and performance specifications for x-ray generators and automatic exposure control devices 68 PART 3: Test methods and performance levels for x-ray generators and automatic exposure control devices 75

25 citations


Journal Article

25 citations


Journal ArticleDOI
TL;DR: The DFD's provided a picture of the logical flow through the integrated system for thorough system acceptance testing, and system test repeatability was enhanced by the matrix which flowed from the test sets.
Abstract: This paper deals with the use of Structured Analysis just prior to system acceptance testing. Specifically, the drawing of data flow diagrams (DFD) was done after integration testing. The DFD's provided a picture of the logical flow through the integrated system for thorough system acceptance testing. System test sets, were derived from the flows in the DFD's. System test repeatability was enhanced by the matrix which flowed from the test sets.

22 citations


Journal ArticleDOI
TL;DR: The assumption underlying MIL-STD-781 is a constant mean time between failures (MTBF) and typical practice applies MIL- STD-781 to electrical, electronic, and mechanical equipment as discussed by the authors.
Abstract: MIL-STD-781 specifies reliability acceptance test procedures based on both fixed-length tests and probability ratio sequential tests. The assumption underlying MIL-STD-781 is a constant mean time between failures (MTBF) and typical practice applies MIL-STD-781 to electrical, electronic, and mechanical equipment. This article discusses some of the difficulties that have prompted the C and D revisions of MIL-STD-781. In addition, it discusses the relationship of MIL-STD-781 with MIL-STD-1635(EC) which deals with reliability growth testing. The article concludes with a discussion of needed research in reliability growth testing, in support of MIL-STD-781, and in the area of stress and its impact of MTBF.

10 citations



Journal ArticleDOI
TL;DR: Acceptance testing is the legal tool used to define satisfactory performance and both legal and technical concepts must be substantially improved to allow the contracting process to carry out the intentions of the parties.
Abstract: Contracting for computer software is a novel problem, with complex technical and legal issues. Acceptance testing is. the legal tool used to define satisfactory performance. However, both legal and technical concepts must be substantially improved to allow the contracting process to carry out the intentions of the parties.

Journal ArticleDOI
TL;DR: In this paper, the European Commission's second 4-year program of solar energy R&D has concluded that all the photovoltaic installations were aesthetically pleasing, in accordance with CEC guidelines, but there is scope for reducing the costs of site preparation, support structures and array installation.
Abstract: Official acceptance tests, involving performance measurement, visual inspection and functioning checks, have been carried out on all fifteen of the photovoltaic pilot plants in the European Commission' second 4-year programme of solar energy R&D. Equipment and procedures developed for on-site performance measurement have been successfully applied throughout the year - even in an English November. All installations were found to be aesthetically pleasing, in accordance with CEC guidelines, but there is scope for reducing the costs of site preparation, support structures and array installation. Some of the modules were of high quality but others had low efficiency, poor process control and unsatisfactory arrangements for mounting and interconnection -faults which should be remedied in today's highly competitive market. Measurement discrepancies could be reduced if all manufacturers adhered strictly to the current European standard, CEC Specification 101, Issue 2. A single international standard for...

01 Sep 1985
TL;DR: It is demonstrated that systems-based FDIC techniques can yield consistency checks that are easier to implement than acceptance tests based on software specifications and can be generalized to the domain of software fault tolerance in developing software error recovery procedures.
Abstract: The major aim of this study is to investigate the feasibility of using systems-based failure detection isolation and compensation (FDIC) techniques in building fault-tolerant software and extending them, whenever possible, to the domain of software fault tolerance. First, it is shown that systems-based FDIC methods can be extended to develop software error detection techniques by using system models for software modules. In particular, it is demonstrated that systems-based FDIC techniques can yield consistency checks that are easier to implement than acceptance tests based on software specifications. Next, it is shown that systems-based failure compensation techniques can be generalized to the domain of software fault tolerance in developing software error recovery procedures. Finally, the feasibility of using fault-tolerant software in flight software is investigated. In particular, possible system and version instabilities, and functional performance degradation that may occur in N-Version programming applications to flight software are illustrated. Finally, a comparative analysis of N-Version and recovery block techniques in the context of generic blocks in flight software is presented.

28 Jun 1985
TL;DR: In this article, the authors describe the special tests and procedures that will be performed on the broadband microwave amplifier panel and the various essential elements that comprise the panel for reliability purposes and are used to burn-in components, screen out weak parts and deficiencies, determine design deficiencies, and accumulate data to verify and/or improve the reliability analyses performed beforehand.
Abstract: : This report describes the special tests and procedures that will be performed on the broadband microwave amplifier panel and the various essential elements that comprise the panel. These tests and procedures outlined are those items that are essential for reliability purposes and are used to burn-in components, screen out weak parts and deficiencies, determine design deficiencies, and accumulate data to verify and/or improve the reliability analyses performed beforehand. Keywords include: CDRL A004 and Contract N00014-84-C-2232.

Journal ArticleDOI
TL;DR: Computerised radiotherapy treatment planning systems are in common use and offer advantages of speed and accuracy, however, they are complex systems which involve large application programs, several computer peripherals and the computer system itself.
Abstract: Computerised radiotherapy treatment planning systems are in common use and offer advantages of speed and accuracy However, they are complex systems which involve large application programs, several computer peripherals and the computer system itself Experience and common sense suggest that their results should be checked carefully because of this complexity Wilkinson and Redmond (1975), and McCullough and Krueger (1980) showed the need for acceptance tests for new treatment planning systems to ensure correct function and accuracy These should always be supplemented by checking the computed result before each plan leaves the planning section (ICRU, 1976) for two important reasons Firstly, acceptance tests cannot cover all combinations of hardware and software parameters, and secondly, transient artefacts should be guarded against Although most faults may be obvious, not all are (Conere, 1980) In our department we have always checked our computer plans manually (Armstrong & Smith, 1980), but because


Proceedings ArticleDOI
01 Jan 1985
TL;DR: The rationale used to develop the design criteria for both the hardware and software required for automated systems designed for long-term, unattended use in remote marine locations is explored.
Abstract: With the advent of satellite communications and microprocessor technology, the National Data Buoy Center (NDBC) has successfully developed and deployed several different evolutionary classes of data acquisition systems for buoy and coastal applications. Emphasis has always been placed on reliability, maintainability, and low cost. This paper will explore the rationale used to develop the design criteria for both the hardware and software required for automated systems designed for long-term, unattended use in remote marine locations. Four basic areas will be addressed: (1) sensor systems, (2) data acquisition and control, (3) data communications, and (4) power systems. This paper will discuss the overall design criteria for these areas, the end-to-end system acceptance testing requirements, and the reliability and maintenance philosophy used to achieve NDBC's goal of providing continuous, reliable, user data from the marine environment.




01 Jul 1985
TL;DR: A literature survey and limited study of laboratory concretes were conducted to evaluate varius methods for predicting concrete strengths at 28 days based on procedures for accelerated strength development or measurement of strength to normally cured specimens at early ages.
Abstract: A literature survey and limited study of laboratory concretes were conducted to evaluate varius methods for predicting concrete strengths at 28 days based on procedures for accelerated strength development or measurement of strength to normally cured specimens at early ages. A review of the literature was also made to assess the usefulness of procedures for the direct determinations of water and cement contents in quality control of hydraulic cement concrete. It is concluded that although general relationships exist as reported in the literature, none of the procedures are sufficiently precise for use in quality control or acceptance testing by the Virginia Department of Highways & Transportation. The amount of calibration testing for projects normally built by the Department would be prohibitive. Any application of reduced pay factors for strength in a statistical specification must be based on tests made at the age designated in thee specification. The literature survey shows that in their present state of development existing procedures foo the direct determination of water and cement in plastic concrete are not sufficiently fast or precise to be useful for quality control of hydraulic cement concrete. It recommended that further evaluation of such procedures by the Virginia Department of Highways and Transportation be deferred until results of studies now being made for the FHWA are available. The results of 14-day and 28-day tests on the same field concretes reveal that the ratio of strengths at these two ages often varies significantly from the assumed value of 0.85. Thus, it is recommended that the practice of accepting concrete on the basis of 14-day strengths be discontinued unless the value at 14 days is equal to the required value at 28 days.

Book ChapterDOI
01 Jan 1985
TL;DR: The users' perspective of the benefits and limitations of a North American organization established to provide standardized protocols and testing of instrumentation used in automated control of water and wastewater treatment plants is presented.
Abstract: This paper presents the users' perspective of the benefits and limitations of a North American organization established to provide standardized protocols and testing of instrumentation used in automated control of water and wastewater treatment plants. The paper also identifies the need for testing, the objectives of the testing organization, testing procedures and recommendations for improving the testing program.

01 Nov 1985
TL;DR: In this article, a large commercially developed FORTRAN program was modified to produce structural coverage metrics, which were combined with fault and error data to evaluate structural coverage, and the results indicated that the functionally generated tests seem to be a good approximation of operational use.
Abstract: A large, commercially developed FORTRAN program was modified to produce structural coverage metrics. The modified program was executed on a set of functionally generated acceptance tests and a large sample of operational usage cases. The resulting structural coverage metrics are combined with fault and error data to evaluate structural coverage. It was shown that in the software environment the functionally generated tests seem to be a good approximation of operational use. The relative proportions of the exercised statement subclasses change as the structural coverage of the program increases. A method was also proposed for evaluating if two sets of input data exercise a program in a similar manner. Evidence was provided that implies that in this environment, faults revealed in a procedure are independent of the number of times the procedure is executed and that it may be reasonable to use procedure coverage in software models that use statement coverage. Finally, the evidence suggests that it may be possible to use structural coverage to aid in the management of the acceptance test processed.

Journal ArticleDOI
V. Castagnoli1, U. Bazzi1, M. Mocenigo1, P. Ricci1
TL;DR: The new Power Generation and Transmission Control project of ENEL meets both the above requirements: the authors describe their two-years activity in preparing, securing and maintaining static data for the on-line Data Base and in carrying out acceptance tests vis-a-vis of the manufacturer.

Journal ArticleDOI
J. M. Keelty1
TL;DR: In this article, the related matters of testing and maintenance of TDMA traffic terminals are discussed, and it is shown that the best maintenance philosophy is to adopt a circuit card replacement strategy.
Abstract: In this paper the related matters of testing and maintenance of TDMA traffic terminals are discussed. Generally three types of testing are required: first of all testing to ensure that the equipment complies with the stipulations of INTELSAT (called application tests herein), secondly tests to ensure that a product has been manufactured in accordance with the design (manufacturing tests) and finally maintenance tests for the purpose of resolving equipment malfunctions. It is shown that application testing can be split between tests performed on an entire terminal and tests performed on individual subsystems, and that manufacturing testing best employs automatic software-driven facilities. Finally it is shown that the best maintenance philosophy is to adopt a circuit card replacement strategy.