Risk-Based Testing
Michael Felderer, Marc-Florian Wendland, Ina Schieferdecker · Lecture notes in computer science · 2014
Cited by 9
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “Risk-based testing”
Michael Felderer, Marc-Florian Wendland, Ina Schieferdecker · Lecture notes in computer science · 2014
Cited by 9
Erkki Pöyhönen · 2001
Cited by 1
David Stokes · 2003
Cited by 0
Faber, M. H., Sørensen, John Dalsgaard, Kroon, I. B. · VBN Forskningsportal (Aalborg Universitet) · 1992
Cited by 0
Abdulhadi Kırkıcı · 2018
Thesis (M.A.)--Özyeğin University, Graduate School of Sciences and Engineering, Department of Computer Science, May 2018.
Cited by 0
Iris Pinkster, Bob van de Burgt, Dennis Janssen et al. · 2004
Cited by 0
Hrayer Aprahamian, Douglas R. Bish, Ebru K. Bish · Management Science · 2019
Group testing (i.e., testing multiple subjects simultaneously with a single test) is essential for classifying a large population of subjects as positive or negative for a binary characteristic (e.g., presence of a disease). We study optimal group testing designs under subject-specific risk characteristics and imperfect tests, considering classification accuracy-, efficiency- and equity-based objectives, and characterize important structural properties of optimal testing designs. These properties allow us to model the testing design problems as partitioning problems, develop efficient algorithms, and derive insights on equity versus accuracy trade-off. One of our models reduces to a constrained shortest path problem, for a special case of which we develop a polynomial-time algorithm. We also show that determining an optimal risk-based Dorfman testing scheme that minimizes the expected number of tests is tractable, resolving an open conjecture. We demonstrate the value of optimal risk-based testing schemes with a case study of public health screening. This paper was accepted by Yinyu Ye, optimization.
Cited by 66
Engblom, Pontus · Dalarna University College Electronic Archive · 2020
A risk is something that can happen and a problem is something that we know will happen or that has already happened. Security testing is used to evaluate a programs security using various methods and risk-based security testing is used to analyze, calculate and correct potential defects or problems in a system.Testing can be very costly and it is the most primary way of removing software defects. Many people focus their testing looking for correct behavior and not deviant behaviors in software, therefore security testing has not been as relevant in traditional testing. It is usually not possible to perform exhaustive testing on a system, instead you must selectively choose tests to conduct. How should the selection of tests be conducted? The study therefore intends to investigate how one can start working with risk-based security testing in development projects in order to prioritize and choose test cases and test methods. The study also aims to answer whether you can get any financial or practical benefits from working with risk-based security testing. To conduct the study a case study was used and to collect data, a document study was used to provide the opportunity to answer the questions. In order to analyze the collected data, a qualitative data analysis method has been used to explain and describe the content with a descriptive research approach. The results of the study provided an example of risk management with different steps one can take to start working on risk-based security testing in existing or new development projects. The study’s conclusion also shows that if you work with risk-based security testing there are practical benefits. For instance, higher quality of the system and economic benefits by finding defects or implementing countermeasures for possible risks at an early stage during the systems development.
Cited by 0Open access
Ellen Souza, Cristine Martins Gomes de Gusmão, Júlio Venâncio · 2010
This paper describes the application of risk-based testing for a software product evaluation in a real case study. Risk-based testing consists of a set of activities regarding risk factors identification related to software requirements. Once identified, the risks are prioritized according to their likelihood and impact and test cases are designed based on the strategies for treatment of the identified risk factors. Thus, test efforts are continuously adjusted according to risk monitoring. The paper also briefly reviews available risk-based approaches, describes the benefits that are likely to accrue from the growing body of work in this area and provides a set of problems, challenges and future work.
Cited by 19
Michael Felderer, Ina Schieferdecker · International Journal on Software Tools for Technology Transfer · 2014
Cited by 94
Siu-kay Wong · Accreditation and Quality Assurance · 2017
Cited by 17
Seehusen, F., Menz, N., Viehmann, J. et al. · Fraunhofer-Publica (Fraunhofer-Gesellschaft) · 2012
This document constitutes the second deliverable for task 4.2 and task 4.3 of work package 4 on risk- and model-based security testing methodologies. While the other work packages of the DIAMONDS project describe techniques/methods and tools, work package 4 describes processes/guidelines for applying these tool and techniques in practice. This deliverable has four sections. First, in Section 1, we describe a conceptual framework defining the main concepts related to model-based security testing risk-based testing and their relationships. The conceptual framework serves a basis for defining methodologies for risk- and model-based security testing. In Section 2, we present an initial process for test-driven security risk assessment which was used in a DIAMONDS case study. This process has b een evaluated, and the results of the evaluation are presented in Section 3. Finally, Section 4 presents a method to increase the efficiency of the risk analysis process in the setting of model-based risk assessment.
Cited by 0Open access
Felix Redmill · Software Testing Verification and Reliability · 2004
Abstract If software cannot be tested exhaustively, it must be tested selectively. But, on what should selection be based in order to maximize test effectiveness? It seems sensible to concentrate on the parts of the software where the risks are greatest, but what risks should be sought and how can they be identified and analysed? ‘Risk‐based testing’ is a term in current use, for example in an accredited test‐practitioner's course syllabus, but there is no broadly accepted definition of the phrase and no literature or body of knowledge to underpin the subject implied by it. Moreover, there has so far been no suggestion that it requires an understanding of the subject of risk. This paper examines what is implied by risk‐based testing, shows that its practice requires an understanding of risk, and points to the need for research into the topic and the development of a body of knowledge to underpin it. Copyright © 2004 John Wiley & Sons, Ltd.
Cited by 33
Karl D. Pfeiffer, Valery Kanevsky, Thomas J. Housel · Calhoun: The Naval Postgraduate School Institutional Archive (Naval Postgraduate School) · 2009
Approved for public release; distribution is unlimited.
Cited by 0Open access
Felix Redmill · Software Testing Verification and Reliability · 2004
This paper extends a theory of risk-based test planning that was outlined in a previous paper, introduces techniques to facilitate it, explains their practical application, and highlights opportunities for research to enquire into their feasibility and efficacy. Copyright © 2004 John Wiley & Sons, Ltd.
Cited by 45
T. K. Bragina, Galyna Tabunshchyk · ELECTRICAL AND COMPUTER SYSTEMS · 2014
Cited by 0Open access
Hrayer Aprahamian, Ebru K. Bish, Douglas R. Bish · Stochastic Systems · 2020
Testing multiple subjects within a group, with a single test applied to the group (i.e., group testing), is an important tool for classifying populations as positive or negative for a specific binary characteristic in an efficient manner. We study the design of easily implementable, static group testing schemes that take into account operational constraints, heterogeneous populations, and uncertainty in subject risk, while considering classification accuracy- and robustness-based objectives. We derive key structural properties of optimal risk-based designs and show that the problem can be formulated as network flow problems. Our reformulation involves computationally expensive high-dimensional integrals. We develop an analytical expression that eliminates the need to compute high-dimensional integrals, drastically improving the tractability of constructing the underlying network. We demonstrate the impact through a case study on chlamydia screening, which leads to the following insights: (1) Risk-based designs are shown to be less expensive, more accurate, and more robust than current practices. (2) The performance of static risk-based schemes comprised of only two group sizes is comparable to those comprised of many group sizes. (3) Static risk-based schemes are an effective alternative to more complicated dynamic schemes. (4) An expectation-based formulation captures almost all benefits of a static risk-based scheme.
Cited by 10Open access
Etsi Guide · 2015
Cited by 7
P Zech · 2011
Assuring the security of a software system in terms of testing nowadays still is a quite tricky task to conduct. Security requirements are taken as a foundation to derive tests to be executed against a system under test. Yet, these positive requirements by far do not cover all the relevant security aspects to be considered. Hence, especially in the event of security testing, negative requirements, derived from risk analysis, are vital to be incorporated. If considering today's emerging trend in the adoption of cloud computing, security testing even has a more important significance. Due to a cloud's openness, in theory there exists an infinite number of tests. Hence, a concise technique to incorporate the results of risk analysis in security testing is inevitable. We therefore propose a new model-driven methodology for the security testing of cloud environments, ingesting misuse cases, defined by negative requirements derived from risk analysis.
Cited by 50
Valdis Bērziņš · Calhoun: The Naval Postgraduate School Institutional Archive (Naval Postgraduate School) · 2013
Naval Postgraduate School Acquisition Research Program
Cited by 0Open access