Partition Analysis: A Method Combining Testing and Verification

Richardson, Debra J.; Clarke, Lori A.

doi:10.1109/tse.1985.231892

Cited by 97 publications

(42 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Lowry et al [36] proposed integrating testing and proving, but focused on a cost-benefit trade-off evaluation method, rather than on proposing a specific mechanism for combining testing and proving (other than doing them separately). Richardson & Clarke [50] use a formal specification to help partition the space into equivalence classes that are used in generating tests cases, they claim that "Although this does not give total assurance in program reliability, we believe, and our evaluation supports this, that it provides strong evidence about the reliability of a program". Dill [20] proposed a one-dimensional taxonomy which is similar in some ways to the one we use.…”

Section: Discussionmentioning

confidence: 69%

Assurance of Agent Systems: What Role Should Formal Verification Play?

Winikoff

2010

Specification and Verification of Multi-Agent Systems

View full text Add to dashboard Cite

The Department of Information Science is one of seven departments that make up the School of Business at the University of Otago. The department offers courses of study leading to a major in Information Science within the BCom, BA and BSc degrees. In addition to undergraduate teaching, the department is also strongly involved in postgraduate research programmes leading to MCom, MA, MSc and PhD degrees. Research projects in spatial information processing, connectionist-based information systems, software engineering and software development, information engineering and database, software metrics, distributed information systems, multimedia information systems and information systems security are particularly well supported.The views expressed in this paper are not necessarily those of the department as a whole. The accuracy of the information presented in this paper is the sole responsibility of the authors. CopyrightCopyright remains with the authors. Permission to copy for research or teaching purposes is granted on the condition that the authors and the Series are given due acknowledgment. Reproduction in any form for purposes other than research or teaching is forbidden unless prior written permission has been obtained from the authors. CorrespondenceThis paper represents work to date and may not necessarily form the basis for the authors' final conclusions relating to this topic. It is likely, however, that the paper will appear in some form in a journal or in conference proceedings in the near future. The authors would be pleased to receive correspondence in connection with any of the issues raised in this paper, or for subsequent publication details. Please write directly to the authors at the address provided below. (Details of final journal/conference publication venues for these papers are also provided on the Department's publications web pages: http://www.otago.ac.nz/informationscience/pubs/). Any other correspondence concerning the Series should be sent to the DPS Coordinator. AbstractIn this paper we consider the broader issue of gaining assurance that an agent system will behave appropriately when it is deployed. We ask to what extent this problem is addressed by existing research into formal verification. We identify a range of issues with existing work which leads us to conclude that, broadly speaking, verification approaches on their own are too narrowly focussed. We argue that a shift in direction is needed, and outline some possibilities for such a shift in direction.

show abstract

Section: Discussionmentioning

confidence: 69%

Assurance of Agent Systems: What Role Should Formal Verification Play?

Winikoff

2010

Specification and Verification of Multi-Agent Systems

View full text Add to dashboard Cite

show abstract

“…The research discussed here is confined to the relatively sparse literature on integration of multiple methods of V&V. There are numerous papers that address some degree of integration but literally none that we have been able to find that propose a unification and integration across all of static analysis, testing, model checking and runtime monitoring. For example, Richardson and Clarke addressed integration of testing and verification in 1985 [11]. There have been some research integrating various methods in pairs, for example Kuncak, et.al [9] discuss combining theorem proving with static analysis.…”

Section: Related Researchmentioning

confidence: 99%

Unification of verification and validation methods for software systems: progress report and initial case study formulation

Browne¹,

Lin²,

Kane³

et al. 2006

Proceedings 20th IEEE International Parallel &Amp; Distributed Processing Symposium

View full text Add to dashboard Cite

show abstract

“…For a system specified in Z and im- Axiomatic specifications SST/ADLscope Revealing subdomains [32], Partition analysis [24], TTF [27] plemented in Ada, for example, the relationships between the Z and Ada entities are needed. ADLscope takes advantage of the fact that ADL uses mappable data representation and control structure with respect to C. In terms of data representation, ADL includes all the data types in the C language and adds a few new types that can be mapped easily to equivalent C types.…”

Section: Related Workmentioning

confidence: 99%

Structural Specification-Based Testing: Automated Support and Experimental Evaluation

Chang

Richardson

1999

Software Engineering — ESEC/FSE ’99

View full text Add to dashboard Cite

Abstract. In this paper, we describe a testing technique, called structural specification-based testing (SST), which utilizes the formal specification of a program unit as the basis for test selection and test coverage measurement. We also describe an automated testing tool, called ADLscope, which supports SST for program units specified in Sun Microsystems' Assertion Definition Language (ADL). ADLscope automatically generates coverage conditions from a program's ADL specification. While the program is tested, ADLscope determines which of these conditions are covered by the tests. An uncovered condition exhibits aspects of the specification inadequately exercised during testing. The tester uses this information to develop new test data to exercise the uncovered conditions.We provide an overview of SST's specification-based test criteria and describe the design and implementation of ADLscope. Specification-based testing is guided by a specification, whereby the testing activity is directly related to what a component under test is supposed to do, rather than what it actually does. Specification-based testing is a significant advance in testing, because it is often more straightforward to accomplish and it can reveal failures that are often missed by traditional code-based testing techniques. As an initial evaluation of the capabilities of specification-based testing, we conducted an experiment to measure defect detection capabilities, code coverage and usability of SST/ADLscope; we report here on the results.1.

show abstract

Partition Analysis: A Method Combining Testing and Verification

Cited by 97 publications

References 27 publications

Assurance of Agent Systems: What Role Should Formal Verification Play?

Assurance of Agent Systems: What Role Should Formal Verification Play?

Unification of verification and validation methods for software systems: progress report and initial case study formulation

Structural Specification-Based Testing: Automated Support and Experimental Evaluation

Contact Info

Product

Resources

About