Downloads & Free Reading Options - Results

This report surveys the field of software testing, and suggests applications to the testing practices of the United States Army Computer Systems Command. Its emphasis is on the practical aspects of testing, as they are seen by working programmers. Other studies which have addressed management issues are briefly examined. The study is addressed to the actual Computer Systems Command environment. Therefore, a good deal of the research literature on testing is irrelevant. A few comments that characterize impractical research are included to give direction to those examining the literature. Recommendations whose implementation would require substantial changes in resources have been avoided. It is assumed that the Computer Systems Command can move gradually to a better employment of its testing effort, but that no substantial increase in the resources devoted to testing can occur. (Author)

This thesis outlines the development, programming, and testing a logical interface between a radar system, the AN/SPS-65(V)1, and a general-purpose reconfigurable computing platform, the SRC Computer, Inc. model, the SRC-6E. To confirm the proper operation of the interface and associated subcomponents, software was developed to perform basic radar signal processing. The interface, as proven by the signal processing results, accurately reflects radar imagery generated by the radar system when compared to maps of the surrounding area. The research accomplished here will allow follow on research to evaluate the potential benefits reconfigurable computing platforms offer for radar signal processing.

Testing is an expensive but essential part of any software project. Having the right methods to detect faults is a primary factor for success in the software industry. Component based systems are problematic because they are prone to unexpected interaction faults, yet these may be left undetected by traditional testing techniques. In all but the smallest of systems, it is not possible to test every component interaction. One can use a reduced test suite that guarantees to include a defined subset of interactions instead. A well studied combinatorial object, the covering array, can be used to achieve this goal. Constructing covering arrays for a specific software system is not always simple and the resulting object may not closely mirror the real test environment. Not only are new methods for building covering arrays needed, but new tools to support these are required as well. Our aim is to develop methods for building smaller test suites that provide stronger interaction coverage, while retaining the flexibility required in a practical test suite. We combine ideas from combinatorial design theory, computational search, statistical design of experiments and software engineering. We begin with a description of a framework for greedy algorithms that has formed the basis for several published methods and a widely used commercial tool. We compare this with a meta-heuristic search algorithm, simulated annealing. The results suggest that simulated annealing is more effective at finding smaller test suites, and in some cases improves on combinatorial methods as well. We then develop a mathematical model for variable strength interaction testing. This allows us to balance the cost and the time of testing by targeting individual subsets of components. We present construction techniques using meta-heuristic search and provide the first known bounds for objects of this type. We end by presenting some new cut-and-paste techniques that merge recursive combinatorial constructions

http://www.infuse.it - Infuse Consulting Group (Infuse) is a pioneering provider of Quality Assurance and Software Testing.

http://www.infuse.it - Infuse Consulting Group (Infuse) is a pioneering provider of Quality Assurance and Software Testing.

The Light Attack and Strike Fighter communities employ manual information management systems for administrative duties. This antiquated method of handling information results in degraded combat readiness as flightcrews expend inordinate amounts of time away from aviation or tactical concerns. The communities must alter their methods of information management to re-align pilot priorities, permitting flightcrews to become more proficient aviators. The complexity of modern Naval aircraft and the proliferation of modern air defenses demand this shift in priorities. This thesis is an attempt to automate the Operations department of an A-7 or F/A-18 squadron. Subsequent additions may extend to other departments. The Squadron Information Management System (SIMS) is flexible, supportable, and transportable. The SIMS will help slay the paper dragon in the TACAIR community, letting the pilots concentrate on their most demanding responsibility . . . becoming a professional warrior. Keywords: relational data bases; expert systems; Navy TACAIR Combat readiness. (Author)

Software reliability is one of the important factors of software quality. Before software delivered in to market it is thoroughly checked and errors are removed. Every software industry wants to develop software that should be error free. Software reliability growth models are helping the software industries to develop software which is error free and reliable. In this paper an analysis is done based on incorporating the logistic-exponential testing-effort in to NHPP Software reliability growth model and also observed its release policy. Experiments are performed on the real datasets. Parameters are calculated and observed that our model is best fitted for the datasets.

This report addresses the actual development of the Dynamic Help module and the testing of the module as installed in the Consolidated Issue Facility (CIF) Installation Support Module (ISM) developed and maintained by Software Development Center-Atlanta (SDC-A). The test procedures, dynamic help development, test tasks, and results of actual tasks are shown in appendixes. Dynamic Help is an on-line user-invoked help message capability developed for supporting ISM modules identified by the PM-ISM. Messages are assembled from stored phrases and the available state variables. This information is of significant importance to the PM-ISM and the ISM Project Support Staff (Software Integration Group-SIG). Additionally, this information could prove to be of value to all software development activities throughout the Army and DOD.... Dynamic Help, ISM, CIF, On-line user interface, Horizontal DBMS integration, Vertical DBMS integration, Windows management

Dev Labs Alliance Top 10 Software Testing Interview Questions For SDET Converted

Dev Labs Alliance Top 10 Software Testing Interview Questions For SDET Converted

Performance Testing of Software Defined Radios. Included in DLARC with permission of the author.

Performance Testing of Software Defined Radios. Included in DLARC with permission of the author.

Performance Testing of Software Defined Radios. Included in DLARC with permission of the author.

Human limb segment angle tracking requires a system which can track through all orientations. The major problem addressed by this research was to develop a real time inertial motion tracking system based on quaternions to overcome the singularities of Euler angle filters. This work involves clarification of the theory behind quaternion attitude estimation and development of a system capable of determining the orientation of an object in world coordinates. System sensors were built using miniature accelerometers, rate sensors, and magnetometers. The software system was designed by using Unified Modeling Language (UML) with object oriented design techniques. The actual implementation created a real time orientation tracking system. The system was tested with dynamic tilt table experiments. Test results showed that the quaternion attitude estimation filter system can track human limb segments in real time within 1 degree of accuracy in an orientation and with a 55 Hz update rate.

A suitably organized and executed test process can contribute to the success of a product line organization. Testing is used to identify defects during construction and to assure that completed products possess the qualities specified for the products. Test-related activities are organized into a test process that is designed to take advantage of the economies of scope and scale that are present in a product line organization. These activities are sequenced and scheduled so that a test activity occurs immediately following the construction activity whose output the test is intended to validate. This report expands on the testing practice area described by Clements and Northrop Clements 02b. Test-related activities that can be used to form the test process for a product line organization are described. Product line organizations face unique challenges in testing. This report describes techniques and activities for meeting those challenges.

The only constant is change. Nowhere is this more evident than in the world of software. The addition of field changes, patches, updates and upgrades at regular, short-term intervals makes the acquisition of software intensive systems complex at best. Is the system configuration as stable today in test as it was six months ago at the last software review? Is today's test item representative of the item that will be delivered to the servicemember in the field a year from now? Traditional software metrics fall shot of providing useful answers to these questions. SLOC, version numbers, and release dates describe the physical characteristics of an application. The questions that most often arise in the management of a software program, however, need information on the operational performance of the application.

When it comes to industrial organizations, current collaboration efforts in software engineering research are very often kept in-house, depriving these organizations off the skills necessary to build independent collaborative research. The current trend, towards empirical software engineering research, requires certain standards to be established which would guide these collaborative efforts in creating a strong partnership that promotes independent, evidence-based, software engineering research. This paper examines key enabling factors for an efficient and effective industry-academia collaboration in the software testing domain. A major finding of the research was that while technology is a strong enabler to better collaboration, it must be complemented with industrial openness to disclose research results and the use of a dedicated tooling platform. We use as an example an automated test generation approach that has been developed in the last two years collaboratively with Bombardier Transportation AB in Sweden.

When it comes to industrial organizations, current collaboration efforts in software engineering research are very often kept in-house, depriving these organizations off the skills necessary to build independent collaborative research. The current trend, towards empirical software engineering research, requires certain standards to be established which would guide these collaborative efforts in creating a strong partnership that promotes independent, evidence-based, software engineering research. This paper examines key enabling factors for an efficient and effective industry-academia collaboration in the software testing domain. A major finding of the research was that while technology is a strong enabler to better collaboration, it must be complemented with industrial openness to disclose research results and the use of a dedicated tooling platform. We use as an example an automated test generation approach that has been developed in the last two years collaboratively with Bombardier Transportation AB in Sweden.

When it comes to industrial organizations, current collaboration efforts in software engineering research are very often kept in-house, depriving these organizations off the skills necessary to build independent collaborative research. The current trend, towards empirical software engineering research, requires certain standards to be established which would guide these collaborative efforts in creating a strong partnership that promotes independent, evidence-based, software engineering research. This paper examines key enabling factors for an efficient and effective industry-academia collaboration in the software testing domain. A major finding of the research was that while technology is a strong enabler to better collaboration, it must be complemented with industrial openness to disclose research results and the use of a dedicated tooling platform. We use as an example an automated test generation approach that has been developed in the last two years collaboratively with Bombardier Transportation AB in Sweden.

When it comes to industrial organizations, current collaboration efforts in software engineering research are very often kept in-house, depriving these organizations off the skills necessary to build independent collaborative research. The current trend, towards empirical software engineering research, requires certain standards to be established which would guide these collaborative efforts in creating a strong partnership that promotes independent, evidence-based, software engineering research. This paper examines key enabling factors for an efficient and effective industry-academia collaboration in the software testing domain. A major finding of the research was that while technology is a strong enabler to better collaboration, it must be complemented with industrial openness to disclose research results and the use of a dedicated tooling platform. We use as an example an automated test generation approach that has been developed in the last two years collaboratively with Bombardier Transportation AB in Sweden.

This article is from PeerJ , volume 2 . Abstract Purpose. To design and validate a prenatal chromosomal microarray testing strategy that moves away from size-based detection thresholds, towards a more clinically relevant analysis, providing higher resolution than G-banded chromosomes but avoiding the detection of copy number variants (CNVs) of unclear prognosis that cause parental anxiety.Methods. All prenatal samples fulfilling our criteria for karyotype analysis (n = 342) were tested by chromosomal microarray and only CNVs of established deletion/duplication syndrome regions and any other CNV >3 Mb were detected and reported. A retrospective full-resolution analysis of 249 of these samples was carried out to ascertain the performance of this testing strategy.Results. Using our prenatal analysis, 23/342 (6.7%) samples were found to be abnormal. Of the remaining samples, 249 were anonymized and reanalyzed at full-resolution; a further 46 CNVs were detected in 44 of these cases (17.7%). None of these additional CNVs were of clear clinical significance.Conclusion. This prenatal chromosomal microarray strategy detected all CNVs of clear prognostic value and did not miss any CNVs of clear clinical significance. This strategy avoided both the problems associated with interpreting CNVs of uncertain prognosis and the parental anxiety that are a result of such findings.

In the simulation world, software upgrade is more common than new development. Thus it is extremely important to ensure proper operation of the simulation model as it is enhanced. The big question is how does one keep the current model operating correctly while adding new capabilities? The Model Development Team at the Air Combat Environment Test and Evaluation Facility, Patuxent River Naval Air Station, Maryland, has developed an approach that is useful in making sure that the current simulation model keeps its current capabilities operating correctly as well as testing any new capability that is added. The purpose of this paper is to present the approach used by the Model Development Team to answer the question put forth. This paper discusses the software development and maintenance criteria used as the overarching guide for testing. The testing process used and how this process ensures that the model meets the criteria is then given. Specific test examples and expected output are provided as a model testing approach. Finally, the future of development testing for the Model Development Team is presented.

This report presents Space and Naval Warfare Systems Center Pacific's (SSC Pacific) preliminary efforts to implement and test the JANUS acoustic communication protocol onto a software-defined acoustic modem previously developed by engineers working at the Center. The SSC Pacific developed acoustic modem serves as an ideal open platform suitable for testing and evaluating physical layer protocols such as JANUS, which has recently become a North Atlantic Treaty Organization (NATO) adopted standard. The system configuration, implementation approach, laboratory, tank, and field tests at SSC Pacific's Transducer Evaluation Center (TRANSDEC) facility are discussed. The outcome of the preliminary testing and several lessons learned have paved the path for a promising future effort to create an integrated software-defined interoperable solution for the U.S. Navy's underwater acoustic communication operations with NATO and non-NATO military and civilian maritime assets.

This report presents Space and Naval Warfare Systems Center Pacific's (SSC Pacific) preliminary efforts to implement and test the JANUS acoustic communication protocol onto a software-defined acoustic modem previously developed by engineers working at the Center. The SSC Pacific developed acoustic modem serves as an ideal open platform suitable for testing and evaluating physical layer protocols such as JANUS, which has recently become a North Atlantic Treaty Organization (NATO) adopted standard. The system configuration, implementation approach, laboratory, tank, and field tests at SSC Pacific's Transducer Evaluation Center (TRANSDEC) facility are discussed. The outcome of the preliminary testing and several lessons learned have paved the path for a promising future effort to create an integrated software-defined interoperable solution for the U.S. Navy's underwater acoustic communication operations with NATO and non-NATO military and civilian maritime assets.

We present qHiPSTER, the Quantum High Performance Software Testing Environment. qHiPSTER is a distributed high-performance implementation of a quantum simulator on a classical computer, that can simulate general single-qubit gates and two-qubit controlled gates. We perform a number of single- and multi-node optimizations, including vectorization, multi-threading, cache blocking, as well as overlapping computation with communication. Using the TACC Stampede supercomputer, we simulate quantum circuits ("quantum software") of up to 40 qubits. We carry out a detailed performance analysis to show that our simulator achieves both high performance and high hardware efficiency, limited only by the sustainable memory and network bandwidth of the machine.

The procedure of carrying out a program or else scheme by means of the target of ruling bugs called “Software s w Testing”. It is whichever action intended by estimating a characteristic or else ability of a program system plus shaping that it congregates its requisite consequences. Testing is an essential piece in s w growth. It is generally arranged in each stage in the s w progress sequence. Classically, in excess of fifty two perecent of the progress period is used up in testing. Metrics are attainmenting significance plus receiving in commercial segments as associations raise, grown up and endeavour to get better venture values. This study talks about s w testing methods as well as measurements. Indu Maurya "Software Testing Outline: Performances and Measurements" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-5 | Issue-2 , February 2021, URL: https://www.ijtsrd.com/papers/ijtsrd38550.pdf Paper Url: https://www.ijtsrd.com/computer-science/other/38550/software-testing-outline-performances-and-measurements/indu-maurya

A 7-step approach for quantitatively evaluating software technologies couples software methodology evaluation with software measurement. The approach is applied in-depth in (1) Software Testing Strategies: A 74-subject study, including 32 professional programmers and 42 advanced university students, compared code reading, functional testing, and structural testing in a fractional factorial design. (2) Cleanroom Software Development: Fifteen three-person teams separately built a 1200-line message system to compare Cleanroom software development (in which software is developed completely off-line) with a more traditional approach. (3) Characteristic Software Metric Sets: In the NASA S.E.L. production environment, a study of 65 candidate product and process measures of 652 modules from six (51,000 -112,000 line) projects yielded a characteristic set of software cst/quality metrics. The approach described for quantitatively evaluating software technologies was effective in a variety of problem domains. With the professionals, code reading detected more software faults and had a higher fault detection rate than did functional or structural testing. With the students, the 3 techniques were not noticeably different in the number of faults detected or in the fault detection rate. Code reading detected more interface faults and functional testing detected more control faults than did the other methods. Most developers using the Cleanroom software development approach were able to build systems completely off-line. The Cleanroom teams' products met system requirements more completely and succeeded on more operational test cases than did those developed with traditional approach.

Program testing is studied for maximizing the reliability of computer programs. Several formulas are derived to estimate the number of tests required to say that a program being tested is correct with a given probability. Strategies to select those test cases which minimize the probability of program error while keeping the number of tests fixed, are investigated. (author)

The large adoption of wireless devices goes further than WiFi (smartmeters, wearable devices, Internet of Things, etc.). The developers of these new types of devices may not have a deep security background and it can lead to security and privacy issues when the solution is stressed. However, to assess those types of devices, the only solution would be a dedicated hardware component with an appropriate radio interface for each one of them. That is why we developed an easy-to-use wireless monitor/injector tool based on Software Defined Radio using GNU Radio and the well-known scapy framework. In this talk, we will introduce this tool we developed for a wide range of wireless security assessments: the main goal of our tool is to provide effective penetration testing capabilities for security auditors with little to no knowledge of radio communications. Source: https://www.youtube.com/watch?v=hZJDdz6kVJ4 Uploader: Black Hat

The large adoption of wireless devices goes further than WiFi (smartmeters, wearable devices, Internet of Things, etc.). The developers of these new types of devices may not have a deep security background and it can lead to security and privacy issues when the solution is stressed. However, to assess those types of devices, the only solution would be a dedicated hardware component with an appropriate radio interface for each one of them. That is why we developed an easy-to-use wireless monitor/injector tool based on Software Defined Radio using GNU Radio and the well-known scapy framework. In this talk, we will introduce this tool we developed for a wide range of wireless security assessments: the main goal of our tool is to provide effective penetration testing capabilities for security auditors with little to no knowledge of radio communications. Source: https://www.youtube.com/watch?v=hZJDdz6kVJ4 Uploader: Black Hat

Our briefing will cover the: (1) F/A-18 Aircraft; (2) An overview of the Hornet's Flight Control System; (3) A brief synopsis of selected flight controls system related mishaps; (4) Our testing of the software, or 'Operational Flight Program' which in a highly augmented, fly-by-wire aircraft constitutes a new flight control system; and (5) Results and Conclusions. And a brief overview of lessons learned.

Our briefing will cover the: (1) F/A-18 Aircraft; (2) An overview of the Hornet's Flight Control System; (3) A brief synopsis of selected flight controls system related mishaps; (4) Our testing of the software, or 'Operational Flight Program' which in a highly augmented, fly-by-wire aircraft constitutes a new flight control system; and (5) Results and Conclusions. And a brief overview of lessons learned.

Our briefing will cover the: (1) F/A-18 Aircraft; (2) An overview of the Hornet's Flight Control System; (3) A brief synopsis of selected flight controls system related mishaps; (4) Our testing of the software, or 'Operational Flight Program' which in a highly augmented, fly-by-wire aircraft constitutes a new flight control system; and (5) Results and Conclusions. And a brief overview of lessons learned.

A validation procedure for the Ada binding of the Graphical Kernel System (GKS) is being developed. PRIOR Data Sciences is also producing a version of the GKS written in Ada. These major software engineering projects will provide an opportunity to demonstrate a sound approach for software testing in an Ada environment. The GKS/Ada validation capability will be a collection of test programs and data, and test management guidelines. These products will be used to assess the correctness, completeness, and efficiency of any GKS/Ada implementation. The GKS/Ada developers will be able to obtain the validation software for their own use. It is anticipated that this validation software will eventually be taken over by an independent standards body to provide objective assessments of GKS/Ada implementations, using an approach similar to the validation testing currently applied to Ada compilers. In the meantime, if requested, this validation software will be used to assess GKS/Ada products. The second project, implementation of GKS using the Ada language, is a conventional software engineering tasks. It represents a large body of Ada code and has some interesting testing problems associated with automatic testing of graphics routines. Here the normal test practices which include automated regression testing, independent quality assistance, test configuration management, and the application of software quality metrics will be employed. The software testing methods emphasize quality enhancement and automated procedures. Ada makes some aspects of testing easier, and introduces some concerns. These issues are addressed.

This report surveys the field of software testing, and suggests applications to the testing practices of the United States Army Computer Systems Command. Its emphasis is on the practical aspects of testing, as they are seen by working programmers. Other studies which have addressed management issues are briefly examined. The study is addressed to the actual Computer Systems Command environment. Therefore, a good deal of the research literature on testing is irrelevant. A few comments that characterize impractical research are included to give direction to those examining the literature. Recommendations whose implementation would require substantial changes in resources have been avoided. It is assumed that the Computer Systems Command can move gradually to a better employment of its testing effort, but that no substantial increase in the resources devoted to testing can occur. (Author)

This report identifies hardware and software issues associated with the transition of computerized tests from old hardware and software configurations to currently available hardware and software. Hardware issues addressed include real-time clock performance, storage devices, video adapter, central processing unit (CPU), and CPU processing speed. Software issues addressed include conversion from PASCAL to C code and hardware-dependent routines.

This report surveys the field of software testing, and suggests applications to the testing practices of the United States Army Computer Systems Command. Its emphasis is on the practical aspects of testing, as they are seen by working programmers. Other studies which have addressed management issues are briefly examined. The study is addressed to the actual Computer Systems Command environment. Therefore, a good deal of the research literature on testing is irrelevant. A few comments that characterize impractical research are included to give direction to those examining the literature. Recommendations whose implementation would require substantial changes in resources have been avoided. It is assumed that the Computer Systems Command can move gradually to a better employment of its testing effort, but that no substantial increase in the resources devoted to testing can occur. (Author)

Program testing is studied for maximizing the reliability of computer programs. Several formulas are derived to estimate the number of tests required to say that a program being tested is correct with a given probability. Strategies to select those test cases which minimize the probability of program error while keeping the number of tests fixed, are investigated. (author)

A crucial step for either initial issue development or post deployment support updates of military software products is integrated systems testing. After the development team has conducted progressive coding/module level tests and appropriate systems integration tests (using a systems integration laboratory), a proposed new version for the software product emerges. The critical issue becomes 'Is this version ready for final operational testing and for release for use by our military users?'. During Developmental Test and Evaluation (DT&E), each proposed new version is subjected to integrated systems testing. The configuration item is installed into representatively configured military hardware system (aircraft, ships, etc.). During testing, it is operated in the near-operational environment (at sea or in flight, using highly skilled military operators performing a carefully planned representative task). The authors are team members of Naval Helicopter software development Integrated Program Teams (IPTs). Their pragmatic experiences in performing this value added testing in the near-operational environment is useful for consideration by all software developers and testers.

In this talk, I will share our experiences with creating tools and a methodology for testing concurrent software during the last nine years. I will start by explaining why the problem is troublesome. Then, I will cover these topics: Using tools that increase the likelihood of test failure Unit and system test methodology Evaluating concurrent coverage Finding potential deadlocks Debugging aids for concurrent software Discovering bug location in code automatically Healing concurrent programs ©2008 Microsoft Corporation. All rights reserved.

In this talk, I will share our experiences with creating tools and a methodology for testing concurrent software during the last nine years. I will start by explaining why the problem is troublesome. Then, I will cover these topics: Using tools that increase the likelihood of test failure Unit and system test methodology Evaluating concurrent coverage Finding potential deadlocks Debugging aids for concurrent software Discovering bug location in code automatically Healing concurrent programs ©2008 Microsoft Corporation. All rights reserved.

In this talk, I will share our experiences with creating tools and a methodology for testing concurrent software during the last nine years. I will start by explaining why the problem is troublesome. Then, I will cover these topics: Using tools that increase the likelihood of test failure Unit and system test methodology Evaluating concurrent coverage Finding potential deadlocks Debugging aids for concurrent software Discovering bug location in code automatically Healing concurrent programs ©2008 Microsoft Corporation. All rights reserved.

This project involved the modification, implementation and evaluation of a remote terminal emulator (RTE) as a software validation and stress testing tool. Considerable background information is provided about the sponsor's release environment to show the sponsor's need for a reliable testing tool. Information is also presented about acceptance and validation testing. The emphasis of this research centered on a RTE made available by the Joint Data System Support Center. The modified package was found to be a very good tool for software validation. Comparisons are made between the RTE and the sponsor's internal test driver in the areas of scenario collection and management. The two tools are also compared during the emulation phase of software validation. The RTE package was also examined as a stress testing tool. Several problems in the RTE application software which inhibit its use as a stress testing tool are discussed.

Available from National Technical Information Service, Springfield, Va

unsophisticated imrpvosied shit http://www.myspace.com/vikistufx

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

Tri 2 2016/2017

Tri 2 2016/2017

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies--for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results.