Validation, verification, and testing of computer software

Adrion, W. Richards; Branstad, Martha; Cherniavsky, John C.

doi:10.6028/nbs.sp.500-75

Cited by 37 publications

(56 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Unfortunately, Software testing has been described as difficult, time consuming and inadequate [1], [2]. Several testing techniques are available now but there is no consensus on the absolute or relative applicability or usability of these techniques.…”

Section: A Software Testingmentioning

confidence: 99%

“…Several testing techniques are available now but there is no consensus on the absolute or relative applicability or usability of these techniques. Testing techniques are inherently heuristic as their application does not guarantee the detection of faults [2]. In addition to that, some researchers characterize software testing as tricky; as the evaluation of some testing techniques generated counter-intuitive results [3].…”

Section: A Software Testingmentioning

confidence: 99%

“…One vital question that is still pending an answer from researchers and practitioners is "which testing technique to use and when to use it?" Several researchers pointed out that more research is needed to advance the maturity level of software testing [2], [5], [10]. Integration of the existing techniques and test automation are two areas that need more attention [2].…”

Section: A Software Testingmentioning

confidence: 99%

See 2 more Smart Citations

Open Problems in Software Test Coverage

Alrmuny¹

2014

LNSE

View full text Add to dashboard Cite

Abstract-Software testing is concerned with the production and maintenance of high quality systems. Test coverage is one major component in software testing. It gives a meaningful description of how much testing is required. The level of test coverage is an indicator of testing thoroughness, which in turn helps testers decide when to stop testing. Several studies addressed coverage criteria effectiveness and adequacy. However, there are several interesting open problems. We identify nine open problems in test coverage and discuss what issues need to be addressed. The objective of this paper is to direct the attention of researchers and testers toward the areas that need to be investigated.

show abstract

Section: A Software Testingmentioning

confidence: 99%

Section: A Software Testingmentioning

confidence: 99%

Section: A Software Testingmentioning

confidence: 99%

See 1 more Smart Citation

Open Problems in Software Test Coverage

Alrmuny¹

2014

LNSE

View full text Add to dashboard Cite

show abstract

“…However, as is already known from the domain of software engineering, an early identi®cation of¯aws within algorithmic knowledge is critically important [1]. In the domain of software engineering in general and in the domain of knowledge-based systems (KBS) in particular, a common strategy to examine a system for potential defects consists in its veri®cation.…”

Section: Veri®cation Of Clinical Guidelinesmentioning

confidence: 99%

Knowledge-based verification of clinical guidelines by detection of anomalies

Duftschmid

Miksch

2001

Artificial Intelligence in Medicine

View full text Add to dashboard Cite

As shown in numerous studies, a signi®cant part of published clinical guidelines is tainted with different types of semantical errors that interfere with their practical application. The adaptation of generic guidelines, necessitated by circumstances such as resource limitations within the applying organization or unexpected events arising in the course of patient care, further promotes the introduction of defects. Still, most current approaches for the automation of clinical guidelines are lacking mechanisms, which check the overall correctness of their output. In the domain of software engineering in general and in the domain of knowledge-based systems (KBS) in particular, a common strategy to examine a system for potential defects consists in its veri®cation. The focus of this work is to present an approach, which helps to ensure the semantical correctness of clinical guidelines in a three-step process. We use a particular guideline speci®cation language called Asbru to demonstrate our veri®cation mechanism. A scenario-based evaluation of our method is provided based on a guideline for the arti®cial ventilation of newborn infants. The described approach is kept suf®ciently general in order to allow its application to several other guideline representation formats. #

show abstract

“…As revisões de software do tipo inspeção, por exemplo, realizam uma análise estática do produto (durante uma reunião de inspeção pode-se utilizar um checklist de erros historicamente comuns de programação para descobrir problemas de qualidade no produto). As revisões de software do tipo walkthrough, por exemplo, realizam uma análise dinâmica, pois, simulam a execução de um programa com um conjunto de casos de teste [ADR82]. As revisões de software são uma das técnicas de validação disponíveis nas fases inicias de desenvolvimento.…”

Section: Introductionunclassified

Replicação de estudos empíricos em engenharia de software.

Dória¹

View full text Add to dashboard Cite

Validation, verification, and testing of computer software

Cited by 37 publications

References 3 publications

Open Problems in Software Test Coverage

Open Problems in Software Test Coverage

Knowledge-based verification of clinical guidelines by detection of anomalies

Replicação de estudos empíricos em engenharia de software.

Contact Info

Product

Resources

About