13,037 research outputs found
Recommended from our members
Using formal methods to support testing
Formal methods and testing are two important approaches that assist in the development of high quality software. While traditionally these approaches have been seen as rivals, in recent
years a new consensus has developed in which they are seen as complementary. This article reviews the state of the art regarding ways in which the presence of a formal specification can be used to assist testing
On the engineering of crucial software
The various aspects of the conventional software development cycle are examined. This cycle was the basis of the augmented approach contained in the original grant proposal. This cycle was found inadequate for crucial software development, and the justification for this opinion is presented. Several possible enhancements to the conventional software cycle are discussed. Software fault tolerance, a possible enhancement of major importance, is discussed separately. Formal verification using mathematical proof is considered. Automatic programming is a radical alternative to the conventional cycle and is discussed. Recommendations for a comprehensive approach are presented, and various experiments which could be conducted in AIRLAB are described
FORTEST: Formal methods and testing
Formal methods have traditionally been used for specification and development of software. However there are potential benefits for the testing stage as well. The panel session associated with this paper explores the usefulness
or otherwise of formal methods in various contexts for improving software testing. A number of different possibilities for the use of formal methods are explored and questions raised. The contributors are all members of the UK FORTEST Network on formal methods and testing. Although
the authors generally believe that formal methods
are useful in aiding the testing process, this paper is intended to provoke discussion. Dissenters are encouraged to put their views to the panel or individually to the authors
An Industrial Case Study on Test Cases as Requirements
It is a conundrum that agile projects can succeed 'without requirements' when
weak requirements engineering is a known cause for project failures. While
Agile development projects often manage well without extensive requirements
documentation, test cases are commonly used as requirements. We have
investigated this agile practice at three companies in order to understand how
test cases can fill the role of requirements. We performed a case study based
on twelve interviews performed in a previous study. The findings include a
range of benefits and challenges in using test cases for eliciting, validating,
verifying, tracing and managing requirements. In addition, we identified three
scenarios for applying the practice, namely as a mature practice, as a de facto
practice and as part of an agile transition. The findings provide insights into
how the role of requirements may be met in agile development including
challenges to consider.Comment: Proceedings of XP 2015: 27-3
- ā¦