Relevant bibliographies by topics / Software testing, verification and validation

Academic literature on the topic 'Software testing, verification and validation'

Author: Grafiati
Published: 10 December 2022
Last updated: 29 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software testing, verification and validation.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software testing, verification and validation"

1

Karamanlidis, D. "Software validation: inspection - testing - verification - alternatives." Advances in Engineering Software (1978) 7, no. 4 (October 1985): 216. http://dx.doi.org/10.1016/0141-1195(85)90080-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Yamada, Shigeru. "Software validation: Inspection-testing-verification-alternatives." European Journal of Operational Research 27, no. 3 (December 1986): 385. http://dx.doi.org/10.1016/0377-2217(86)90337-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Venugopal, Manokar, Manju Nanda, G. Anand, and Hari Chandana Voora. "An integrated Hardware/Software Verification and Validation methodology for Signal Processing Systems." ITM Web of Conferences 50 (2022): 02001. http://dx.doi.org/10.1051/itmconf/20225002001.

Full text
Abstract:
The testing and validation services team assesses project deliverables at various stages of development using innovative and effective verification and validation, to ensure that the deliverables are compliance with the customer specifications and requirements. Whenever new products and devices are released, completely integrated verification and validation services are delivered to accurate and complete records usability, performance, and quality assurance services. Throughout the product development and testing process, the testing and validation services team employs verification and validation techniques. Code reviews, walk through, inspections, desk-checking, and code execution are all examples of verification and validation techniques. Services for verification and validation are used to assess whether or not the software or application provided complies with the requirements and serves the intended purpose. A procedure used to ensure that the software created is of good quality and consistently operates as expected is independent testing and validation services. Unit testing (also known as “White Box Testing”), hardware-software integration testing (HSIT), and system testing are the three primary independent verification and validation approaches (Black Box Testing). The teams responsible for the verification and validation services actively participate in each stage of the project and design the services according to the project’s needs (e.g., prototype, spiral, iterative, V Model, and Agile). Our expertise in the embedded domain, tried-and-true verification and validation techniques, and a thorough methodology provide a quick turnaround and excellent results for the targeted solution. Independent Verification and validation services covering Source code, design, and requirements White box testing, or unit testing Testing for hardware-software integration Black box testing, or system testing To reduce test cycle-time significantly on test Automation solutions. Verification and validation techniques can be used to effectively and efficiently carry out stress and performance tests, and to detect defects early in the life cycle. Documentation of test process. Liaison and Certification
APA, Harvard, Vancouver, ISO, and other styles
4

Petrenko, A. K. "Verification, Validation, and Testing of Software: Special Issue of theProgrammirovanieJournal." Programming and Computer Software 29, no. 6 (November 2003): 296–97. http://dx.doi.org/10.1023/b:pacs.0000004129.28766.3d.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Li, Bing, Li Hong Li, and Fan Ming Liu. "Verification, Validation and Accreditation of Ship Electric Propulsion Simulation System." Applied Mechanics and Materials 433-435 (October 2013): 1915–20. http://dx.doi.org/10.4028/www.scientific.net/amm.433-435.1915.

Full text
Abstract:
in this paper, the concepts of modelling, simulation, verification and validation are described in order to analyse their necessities in electric ship propulsion system simulation. Traditional verification and validation methods are outlined before a new method based on expert theory and verification and validation methods of software testing is proposed to verify if the simulation program meets customers needs and respective software protocols, according to the characteristics of electric ship propulsion system.
APA, Harvard, Vancouver, ISO, and other styles
6

Zhou, Jiantao, Jing Liu, Jinzhao Wu, and Guodong Zhong. "A Latent Implementation Error Detection Method for Software Validation." Journal of Applied Mathematics 2013 (2013): 1–10. http://dx.doi.org/10.1155/2013/138287.

Full text
Abstract:
Model checking and conformance testing play an important role in software system design and implementation. From the view of integrating model checking and conformance testing into a tightly coupled validation approach, this paper presents a novel approach to detect latent errors in software implementation. The latent errors can be classified into two kinds, one is called as Unnecessary Implementation Trace, and the other is called as Neglected Implementation Trace. The method complements the incompleteness of security properties for software model checking. More accurate models are characterized to leverage the effectiveness of the model-based software verification and testing combined method.
APA, Harvard, Vancouver, ISO, and other styles
7

Sziray, József. "A Test Model for Hardware and Software Systems." Journal of Advanced Computational Intelligence and Intelligent Informatics 8, no. 5 (September 20, 2004): 523–29. http://dx.doi.org/10.20965/jaciii.2004.p0523.

Full text
Abstract:
The paper is concerned with the general aspects of testing complex hardware and software systems. First a mapping scheme as a test model is presented for an arbitrary given system. This scheme serves for describing the one-to-one correspondence between the input and output domains of the system, where the test inputs and fault classes are also involved. The presented test model incorporates both the verification and the validation schemes for hardware and software. The significance of the model is that it alleviates the clear differentiation between verification and validation tests, which is important and useful in the process of test design and evaluation. On the other hand, this model provides a clear overview on the various purpose test sets, which helps in organizing and applying these sets. The second part of the paper examines the case when the hardware and software are designed by using formal specification. Here the consequences and problems of formal methods, and their impacts on verification and validation are discussed.
APA, Harvard, Vancouver, ISO, and other styles
8

Reddy, Jogannagari Malla, and Kothuri Parashu Ramulu. "The Complexity of Verification and Validation Testing in Component Based Software Engineering." International Journal of Computer Sciences and Engineering 5, no. 12 (December 31, 2017): 296–300. http://dx.doi.org/10.26438/ijcse/v5i12.296300.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Voronova, Anna, Elena Zhilenkova, Anton Zhilenkov, and Vladislav Borisenko. "Practical approaches to verification and validation of engineering software when solving problems of nonlinear and chaotic dynamics." E3S Web of Conferences 258 (2021): 01012. http://dx.doi.org/10.1051/e3sconf/202125801012.

Full text
Abstract:
The article discusses the problem of verification and validation of engineering software when solving problems of nonlinear dynamics. The problems of validation and verification are shown on the example of dynamic chaos systems. The results of testing systems are presented. It is shown that in general when solving problems of nonlinear dynamics the characteristics of the developed engineering software are of critical importance. It is also indicated that neglecting this fact leads to irreversible negative consequences, ultimately resulting in the decay of the dynamics of a nonlinear system as well as in the decay of its orbits. The influence of the hardware and a number of aspects of the system and software implementation of the verification and validation systems under study is also shown. The article demonstrates modern approaches to the development of the studied software systems. It is shown that a high-quality software product suggests division into subsystems and stages.
APA, Harvard, Vancouver, ISO, and other styles
10

Murray-Smith, David. "Some Issues in the Testing of Computer Simulation Models." International Journal of Business & Technology 5, no. 1 (November 1, 2016): 1–10. http://dx.doi.org/10.33107/ijbte.2016.5.1.01.

Full text
Abstract:
The testing of simulation models has much in common with testing processes in other types of application involving software development. However, there are also important differences associated with the fact that simulation model testing involves two distinct aspects, which are known as verification and validation. Model validation is concerned with investigation of modelling errors and model limitations while verification involves checking that the simulation program is an accurate representation of the mathematical and logical structure of the underlying model. Success in model validation depends upon the availability of detailed information about all aspects of the system being modelled. It also may depend on the availability of high quality data from the system which can be used to compare its behaviour with that of the corresponding simulation model. Transparency, high standards of documentation and good management of simulation models and data sets are basic requirements in simulation model testing. Unlike most other areas of software testing, model validation often has subjective elements, with potentially important contributions from face- validation procedures in which experts give a subjective assessment of the fidelity of the model. Verification and validation processes are not simply applied once but must be used repeatedly throughout the model development process, with regressive testing principles being applied. Decisions about when a model is acceptable for the intended application inevitably involve some form of risk assessment. A case study concerned with the development and application of a simulation model of a hydro-turbine and electrical generator system is used to illustrate some of the issues arising in a typical control engineering application. Results from the case study suggest that it is important to bring together objective aspects of simulation model testing and the more subjective face- validation aspects in a coherent fashion. Suggestions are also made about the need for changes in approach in the teaching of simulation techniques to engineering students to give more emphasis to issues of model quality, testing and validation.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software testing, verification and validation"

1

Tekin, Yasar. "An Automated Tool For Requirements Verification." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/12605401/index.pdf.

Full text
Abstract:
In today&
#8217
s world, only those software organizations that consistently produce high quality products can succeed. This situation enforces the effective usage of defect prevention and detection techniques. One of the most effective defect detection techniques used in software development life cycle is verification of software requirements applied at the end of the requirements engineering phase. If the existing verification techniques can be automated to meet today&
#8217
s work environment needs, the effectiveness of these techniques can be increased. This study focuses on the development and implementation of an automated tool that automates verification of software requirements modeled in Aris eEPC and Organizational Chart for automatically detectable defects. The application of reading techniques on a project and comparison of results of manual and automated verification techniques applied to a project are also discussed.
APA, Harvard, Vancouver, ISO, and other styles
2

Imanian, James A. "Automated test case generation for reactive software systems based on environment models." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Jun%5FImanian.pdf.

Full text
Abstract:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, June 2005.
Thesis Advisor(s): Mikhail Auguston, James B. Michael. Includes bibliographical references (p. 55-56). Also available online.
APA, Harvard, Vancouver, ISO, and other styles
3

Natraj, Shailendra. "An Empirical Evaluation & Comparison of Effectiveness & Efficiency of Fault Detection Testing Techniques." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4047.

Full text
Abstract:
Context: The thesis is the analysis work of the replication of software experiment conducted by Natalia and Sira at Technical University of Madrid, SPAIN. The empirical study was conducted for the verification and validation of experimental data, and to evaluate the effectiveness and efficiency of the testing techniques. The analysis blocks, considered for the analysis were observable fault, failure visibility and observed faults. The statistical data analysis involved the ANOVA and Classification package of SPSS. Objective: To evaluate and compare the result obtained from the statistical data analysis. To establish the verification and validation of effectiveness and efficiency of testing techniques by using ANOVA and Classification tree analysis for percentage subject, percentage defect-subject and values (Yes / No) for each of the blocks. RQ1: Empirical evaluation of effectiveness of fault detection testing technique, using data analysis (ANOVA and Classification tree package). For the blocks (observable fault, failure visibility and observed faults) using ANOVA and Classification tree. RQ2: Empirical evaluation of efficiency of fault detection technique, based on time and number of test cases using ANOVA. RQ3: Comparison and inference of the obtained results for both effectiveness and efficiency. Method:The research will be focused on the statistical data analysis to empirically evaluate the effectiveness and efficiency of the fault detection technique for the experimental data collected at UPM (Technical university of Madrid, SPAIN). Empirical Strategy Used: Software Experiment. Results: Based on the planned research work. The analysis result obtained for the observable fault types were standardized (Ch5). Within the observable fault block, both the techniques, functional and structural were equally effective. In the failure visibility block, the results were partially standardized. The program types nametbl and ntree were equally effective in fault detection than cmdline. The result for observed fault block was partially standardized and diverse. The list for significant factors in this blocks were program types, fault types and techniques. In the efficiency block, the subject took less time in isolating the fault in the program type cmdline. Also the efficiency in fault detection was seen in cmdline with the help of generated test cases. Conclusion:This research will help the practitioners in the industry and academic in understanding the factors influencing the effectiveness and efficiency of testing techniques.This work also presents a comprehensive analysis and comparison of results of the blocks observable fault, failure visibility and observed faults. We discuss the factors influencing the efficiency of the fault detection techniques.
shailendra.natraj@gmail.com +4917671952062
APA, Harvard, Vancouver, ISO, and other styles
4

Cong, Kai. "Post-silicon Functional Validation with Virtual Prototypes." Thesis, Portland State University, 2015. http://pqdtopen.proquest.com/#viewpdf?dispub=3712209.

Full text
Abstract:

Post-silicon validation has become a critical stage in the system-on-chip (SoC) development cycle, driven by increasing design complexity, higher level of integration and decreasing time-to-market. According to recent reports, post-silicon validation effort comprises more than 50% of the overall development effort of an 65nm SoC. Though post-silicon validation covers many aspects ranging from electronic properties of hardware to performance and power consumption of whole systems, a central task remains validating functional correctness of both hardware and its integration with software. There are several key challenges to achieving accelerated and low-cost post-silicon functional validation. First, there is only limited silicon observability and controllability; second, there is no good test coverage estimation over a silicon device; third, it is difficult to generate good post-silicon tests before a silicon device is available; fourth, there is no effective software robustness testing approaches to ensure the quality of hardware/software integration.

We propose a systematic approach to accelerating post-silicon functional validation with virtual prototypes. Post-silicon test coverage is estimated in the pre-silicon stage by evaluating the test cases on the virtual prototypes. Such analysis is first conducted on the initial test suite assembled by the user and subsequently on the expanded test suite which includes test cases that are automatically generated. Based on the coverage statistics of the initial test suite on the virtual prototypes, test cases are automatically generated to improve the test coverage. In the post-silicon stage, our approach supports coverage evaluation of test cases on silicon devices to ensure fidelity of early coverage evaluation. The generated test cases are issued to silicon devices to detect inconsistencies between virtual prototypes and silicon devices using conformance checking. We further extend the test case generation framework to generate and inject fault scenario with virtual prototypes for driver robustness testing. Besides virtual prototype-based fault injection, an automatic driver fault injection approach is developed to support runtime fault generation and injection for driver robustness testing. Since virtual prototype enables early driver development, our automatic driver fault injection approach can be applied to driver testing in both pre-silicon and post-silicon stages.

For preliminary evaluation, we have applied our coverage evaluation and test generation to several network adapters and their virtual prototypes. We have conducted coverage analysis for a suite of common tests on both the virtual prototypes and silicon devices. The results show that our approach can estimate the test coverage with high fidelity. Based on the coverage estimation, we have employed our automatic test generation approach to generate additional tests. When the generated test cases were issued to both virtual prototypes and silicon devices, we observed significant coverage improvement. And we detected 20 inconsistencies between virtual prototypes and silicon devices, each of which reveals a virtual prototype or silicon device defect. After we applied virtual prototype-based fault injection approach to virtual prototypes for three widely-used network adapters, we generated and injected thousands of fault scenarios and found 2 driver bugs. For automatic driver fault injection, we have applied our approach to 12 widely used drivers with either virtual prototypes or silicon devices. After testing all these drivers, we found 28 distinct bugs.

APA, Harvard, Vancouver, ISO, and other styles
5

De, Sousa Barroca José Duarte. "Verification and validation of knowledge-based clinical decision support systems - a practical approach : A descriptive case study at Cambio CDS." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-104935.

Full text
Abstract:
The use of clinical decision support (CDS) systems has grown progressively during the past decades. CDS systems are associated with improved patient safety and outcomes, better prescription and diagnosing practices by clinicians and lower healthcare costs. Quality assurance of these systems is critical, given the potentially severe consequences of any errors. Yet, after several decades of research, there is still no consensual or standardized approach to their verification and validation (V&V). This project is a descriptive and exploratory case study aiming to provide a practical description of how Cambio CDS, a market-leading developer of CDS services, conducts its V&V process. Qualitative methods including semi-structured interviews and coding-based textual data analysis were used to elicit the description of the V&V approaches used by the company. The results showed that the company’s V&V methodology is strongly influenced by the company’s model-driven development approach, a strong focus and leveraging of domain knowledge and good testing practices with a focus on automation and test-driven development. A few suggestions for future directions were discussed.
APA, Harvard, Vancouver, ISO, and other styles
6

Lacerda, Jésus Thiago Sousa. "Investigação de operadores essenciais de mutação para programas orientados a aspectos." Universidade Federal de São Carlos, 2014. https://repositorio.ufscar.br/handle/ufscar/585.

Full text
Abstract:
Made available in DSpace on 2016-06-02T19:06:18Z (GMT). No. of bitstreams: 1 6398.pdf: 1432485 bytes, checksum: dbb2a36cf46b2e3c828fe5dd53dc5d1a (MD5) Previous issue date: 2014-10-20
Financiadora de Estudos e Projetos
Context: The literature on software testing reports on the application of the Mutation Analysis criterion or mutation testing as a promising approach for revealing faults in aspect-oriented (AO) programs. However, it is widely known that this criterion is highly costly due to the large number of generated mutants and the effort required to identify equivalent mutants. We highlight that little existing research on mutation testing for AO programs focuses on cost reduction strategies. Objective: this work aims at investigating the cost reduction of mutation testing for AO programs. In particular, we intend to reduce the cost of mutation testing by identifying a reduced set of mutation operators that are capable of keeping the effectiveness in guaranteeing the quality of the designed test sets. Method: to achieve the goals, we applied an approach called Sufficient Procedure. Such approach yields sufficient (sets of) mutation operators. Test sets that are adequate with respect to mutants produced by sufficient operators are able to reveal the majority of faults simulated by a whole set of mutants. Results: by applying the Sufficient Procedure, we obtained substantial cost reductions for three groups of AO programs. The cost reduction in the experiments range from 52% to 62%. The final mutation scores yielded by the test sets that are adequate to mutants produced by the sufficient operators range from 92% to 94%. Conclusion: with the achieved results, we conclude that it is possible to reduce the cost of mutation testing applied to AO programs without significant losses with respect to the capacity of revealing prespecified fault types. The Sufficient Procedure has shown to be able to support cost reduction and to maintain the effectiveness of the criterion.
Contexto: A literatura de teste de software relata a aplicação do critério Análise de Mutantes ou teste de mutação em programas orientados a aspectos (OA) como uma forma promissora para revelar defeitos. Entretanto, esse critério é reconhecidamente de alto custo devido ao grande número de mutantes usualmente gerados e ao esforço para detectar os mutantes equivalentes. Ressalta-se que as iniciativas de aplicação de teste de mutação nesse contexto apresentam pouco enfoque em estratégias de redução de custo. Objetivo: este trabalho tem como objetivo investigar a redução de custo de teste de mutação para programas OA. Em específico, este trabalho objetiva reduzir o custo do teste de mutação por meio da identificação de um conjunto reduzido de operadores de mutação que mantenham a efetividade do critério em garantir a qualidade dos conjuntos de teste produzidos. Metodologia: para atingir o objetivo proposto, aplicou-se uma abordagem intitulada Procedimento Essencial, a qual resulta em conjuntos de operadores essenciais de mutação. Os testes adequados para os mutantes produzidos com esses operadores são capazes de revelar a maioria dos defeitos simulados em um conjunto completo de mutantes. Resultados: por meio da aplicação do Procedimento Essencial, foi possível obter reduções de custo substanciais para três conjuntos de programas OA. As reduções obtidas nos experimentos variam de 52% a 62%. Os escores de mutação finais alcançados pelos testes adequados aos mutantes produzidos com os operadores essenciais variam de 92% a 94%. Conclusão: com os resultados alcançados neste trabalho pode-se afirmar que é possível reduzir o custo do teste de mutação em programas OA sem perdas significativas na capacidade de revelar tipos de defeitos pré-definidos. O Procedimento Essencial mostrou-se eficaz na redução de custo e na manutenção da efetividade do critério.
APA, Harvard, Vancouver, ISO, and other styles
7

Addy, Edward A. "Verification and validation in software product line engineering." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1068.

Full text
Abstract:
Thesis (Ph. D.)--West Virginia University, 1999.
Title from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 35-39).
APA, Harvard, Vancouver, ISO, and other styles
8

von, Spakovsky Alexis P., Reffela Davidson, Ashley Mathis, and David Patterson. "Software Independent Verification and Validation (SIVandV) simplified." Monterey, California. Naval Postgraduate School, 2006. http://hdl.handle.net/10945/10063.

Full text
Abstract:
Joint Applied Project
SIVandV has been in existence for some 40 years, and many people still know little about its existence. Software IVandV certifies the quality of the software and independently validates and verifies that it meets or exceeds the customer[alpha]s expectations. Independent VandV for component or element software development activities encompasses the following: 1) review and thorough evaluations of the software development, 2) review and comment on software documentation, 3) participation in all software requirements and design reviews, and 4) participation in software integration and testing for each software build. This thesis will explore and explain the benefits and rationale for Software Independent Verification and Validation. It will identify SIVandV processes that are used to support acquisition weapon systems. [beta]SIVandV Simplified[gamma] will translate, into understandable terms, why SIVandV is considered [beta]Cheap Insurance[gamma] and why it is needed. Additionally, this thesis serves as a tutorial, providing suggested policy and guidance, suggested software Computer-Aided Software Engineering (CASE) tools, criteria, and lessons learned for implementing a successful SIVandV program.
APA, Harvard, Vancouver, ISO, and other styles
9

Arno, Matthew G. (Matthew Gordon). "Verification and validation of safety related software." Thesis, Massachusetts Institute of Technology, 1994. http://hdl.handle.net/1721.1/33517.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Argote, Garcia Gonzalo. "Formal verification and testing of software architectural models." FIU Digital Commons, 2009. http://digitalcommons.fiu.edu/etd/1308.

Full text
Abstract:
Ensuring the correctness of software has been the major motivation in software research, constituting a Grand Challenge. Due to its impact in the final implementation, one critical aspect of software is its architectural design. By guaranteeing a correct architectural design, major and costly flaws can be caught early on in the development cycle. Software architecture design has received a lot of attention in the past years, with several methods, techniques and tools developed. However, there is still more to be done, such as providing adequate formal analysis of software architectures. On these regards, a framework to ensure system dependability from design to implementation has been developed at FIU (Florida International University). This framework is based on SAM (Software Architecture Model), an ADL (Architecture Description Language), that allows hierarchical compositions of components and connectors, defines an architectural modeling language for the behavior of components and connectors, and provides a specification language for the behavioral properties. The behavioral model of a SAM model is expressed in the form of Petri nets and the properties in first order linear temporal logic. This dissertation presents a formal verification and testing approach to guarantee the correctness of Software Architectures. The Software Architectures studied are expressed in SAM. For the formal verification approach, the technique applied was model checking and the model checker of choice was Spin. As part of the approach, a SAM model is formally translated to a model in the input language of Spin and verified for its correctness with respect to temporal properties. In terms of testing, a testing approach for SAM architectures was defined which includes the evaluation of test cases based on Petri net testing theory to be used in the testing process at the design level. Additionally, the information at the design level is used to derive test cases for the implementation level. Finally, a modeling and analysis tool (SAM tool) was implemented to help support the design and analysis of SAM models. The results show the applicability of the approach to testing and verification of SAM models with the aid of the SAM tool.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software testing, verification and validation"

1

Haug, Michael, Eric W. Olsen, and Luisa Consolini, eds. Software Quality Approaches: Testing, Verification, and Validation. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Beautiful testing. Sebastopol, Calif: O'Reilly, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Haug, Michael. Software Quality Approaches: Testing, Verification, and Validation: Software Best Practice 1. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Berglund, Tim. Building and testing with Gradle. Sebastopol, CA: O'Reilly Media, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Specification by example: How successful teams deliver the right software. Shelter Island, N.Y: Manning, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bach, James. Lessons learned in software testing: A context-driven approach. New York: Wiley, 2002.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Workshop on the Assessment of Formal Methods for Trustworthy Computer Systems (1989 Halifax, N.S.). Formal methods for trustworthy computer systems (FM89): Report from FM89--a Workshop on the Assessment of Formal Methods for Trustworthy Computer Systems, 23-27 July 1989, Halifax, Canada. Edited by Craigen Dan 1953- and Summerskill Karen 1958-. London: Springer-Verlag, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

IEEE International High-Level Design Validation and Test Workshop (6th 2001 Monterey, Calif.). Sixth IEEE International High-Level Design Validation and Test Workshop: Proceedings : 7-9 November, 2001. Los Alamitos, Calif: IEEE Computer Society, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

IEEE Computer Society. Technical Council on Test Technology. and IEEE Computer Society. Design Automation Technical Committee., eds. Seventh IEEE International High-Level Design Validation and Test Workshop: Proceedings : 27-29 October, 2002, Cannes, France. Los Alamitos, California: IEEE Computer Society, 2002.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Engel, Avner. Verification, Validation, and Testing of Engineered Systems. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2010. http://dx.doi.org/10.1002/9780470618851.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software testing, verification and validation"

1

Voges, U., and J. R. Taylor. "Systematic Testing." In Verification and Validation of Real-Time Software, 115–46. Berlin, Heidelberg: Springer Berlin Heidelberg, 1985. http://dx.doi.org/10.1007/978-3-642-70224-2_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ehrenberger, W. "Statistical Testing of Real Time Software." In Verification and Validation of Real-Time Software, 147–78. Berlin, Heidelberg: Springer Berlin Heidelberg, 1985. http://dx.doi.org/10.1007/978-3-642-70224-2_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Adir, Allon, Amir Nahir, Avi Ziv, Charles Meissner, and John Schumann. "Reaching Coverage Closure in Post-silicon Validation." In Hardware and Software: Verification and Testing, 60–75. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19583-9_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Haug, Michael, Eric W. Olsen, and Luisa Consolini. "Software Process Improvement A European View." In Software Quality Approaches: Testing, Verification, and Validation, 3–15. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Kadry, Wisam, Anatoly Koyfman, Dmitry Krestyashyn, Shimon Landa, Amir Nahir, and Vitali Sokhin. "Improving Post-silicon Validation Efficiency by Using Pre-generated Data." In Hardware and Software: Verification and Testing, 166–81. Cham: Springer International Publishing, 2013. http://dx.doi.org/10.1007/978-3-319-03077-7_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Haug, Michael, Eric W. Olsen, and Luisa Consolini. "Summaries of PIE Reports." In Software Quality Approaches: Testing, Verification, and Validation, 215–93. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Haug, M., and E. W. Olsen. "The EUREX Project." In Software Quality Approaches: Testing, Verification, and Validation, 17–24. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Haug, M., and E. W. Olsen. "The EUREX Taxonomy." In Software Quality Approaches: Testing, Verification, and Validation, 25–30. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Consolini, L. "Perspectives." In Software Quality Approaches: Testing, Verification, and Validation, 33–81. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Consolini, L. "Resources for Practitioners." In Software Quality Approaches: Testing, Verification, and Validation, 83–86. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56612-7_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software testing, verification and validation"

1

Bianchi, Francesco A. "Testing Concurrent Software Systems." In 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST). IEEE, 2016. http://dx.doi.org/10.1109/icst.2016.45.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Vemuri, Venkata Raghunath. "Testing Predictive Software in Mobile Devices." In 2008 International Conference on Software Testing, Verification, and Validation. IEEE, 2008. http://dx.doi.org/10.1109/icst.2008.61.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Chu, Matt, Christian Murphy, and Gail Kaiser. "Distributed In Vivo Testing of Software Applications." In 2008 International Conference on Software Testing, Verification, and Validation. IEEE, 2008. http://dx.doi.org/10.1109/icst.2008.13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Dantas, Ayla, Francisco Brasileiro, and Walfredo Cirne. "Improving Automated Testing of Multi-threaded Software." In 2008 International Conference on Software Testing, Verification, and Validation. IEEE, 2008. http://dx.doi.org/10.1109/icst.2008.38.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Fraser, Gordon, and Neil Walkinshaw. "Behaviourally Adequate Software Testing." In 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation (ICST). IEEE, 2012. http://dx.doi.org/10.1109/icst.2012.110.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tøndel, Inger Anne, Martin Gilje Jaatun, and Jostein Jensen. "Learning from Software Security Testing." In 2008 IEEE International Conference on Software Testing Verification and Validation Workshop. IEEE, 2008. http://dx.doi.org/10.1109/icstw.2008.25.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Karhu, Katja, Tiina Repo, Ossi Taipale, and Kari Smolander. "Empirical Observations on Software Testing Automation." In 2009 International Conference on Software Testing Verification and Validation (ICST). IEEE, 2009. http://dx.doi.org/10.1109/icst.2009.16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Bardin, Sebastien, and Philippe Herrmann. "Structural Testing of Executables." In 2008 International Conference on Software Testing, Verification, and Validation. IEEE, 2008. http://dx.doi.org/10.1109/icst.2008.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Benton, Bruce. "Designing and Building a Software Test Organization." In 2008 International Conference on Software Testing, Verification, and Validation. IEEE, 2008. http://dx.doi.org/10.1109/icst.2008.49.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Fraser, Gordon. "Gamifying software testing (keynote)." In Gamify '22: 1st International Workshop on Gamification of Software Development, Verification, and Validation. New York, NY, USA: ACM, 2022. http://dx.doi.org/10.1145/3548771.3570193.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software testing, verification and validation"

1

Wallace, Dolores R., and Roger U. Fujii. Software verification and validation. Gaithersburg, MD: National Institute of Standards and Technology, 1989. http://dx.doi.org/10.6028/nist.sp.500-165.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Olund, Thomas S. Software Verification and Validation Procedure. Office of Scientific and Technical Information (OSTI), September 2008. http://dx.doi.org/10.2172/1027706.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Riemenschneider, R. A., Theodore A. Linden, Karen Morgan, and William Vrotney. Verification and Validation of AI Software. Fort Belvoir, VA: Defense Technical Information Center, May 1992. http://dx.doi.org/10.21236/ada254601.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Kalinina, Elena Arkadievna. TSL-CALVIN Software Verification and Validation. Office of Scientific and Technical Information (OSTI), October 2014. http://dx.doi.org/10.2172/1163120.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Collofello, James S. Introduction to Software Verification and Validation. Fort Belvoir, VA: Defense Technical Information Center, December 1988. http://dx.doi.org/10.21236/ada236117.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Narahari, Bhagirath, Rahul Simha, and Alok Choudhary. Evolvable Approaches to Software Verification and Validation. Fort Belvoir, VA: Defense Technical Information Center, February 2009. http://dx.doi.org/10.21236/ada495407.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Smith, Curtis L., Yong-Joon Choi, and Ling Zou. RELAP-7 Software Verification and Validation Plan. Office of Scientific and Technical Information (OSTI), September 2014. http://dx.doi.org/10.2172/1168648.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Morris, Katherine C. Architecture for Validation Testing System Software. Gaithersburg, MD: National Institute of Standards and Technology, 1991. http://dx.doi.org/10.6028/nist.ir.4742.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Rae J. Nims and Kent M. Norris. SAPHIRE 8 Software Independent Verification and Validation Plan. Office of Scientific and Technical Information (OSTI), February 2010. http://dx.doi.org/10.2172/974787.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Rae J. Nims. SAPHIRE 8 Software Independent Verification and Validation Plan. Office of Scientific and Technical Information (OSTI), April 2009. http://dx.doi.org/10.2172/957547.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software testing, verification and validation' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography