ACM Home Page
Please provide us with feedback. Feedback
Random testing of formal software models and induced coverage
Full text PdfPdf (324 KB)
Source International Symposium on Software Testing and Analysis archive
Proceedings of the 1st international workshop on Random testing table of contents
Portland, Maine
SESSION: Session 1 table of contents
Pages: 20 - 27  
Year of Publication: 2006
ISBN:1-59593-457-X
Authors
David Owen  West Virginia University, Morgantown, WV
Dejan Desovski  West Virginia University, Morgantown, WV
Bojan Cukic  West Virginia University, Morgantown, WV
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 46,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1145735.1145739
What is a DOI?

ABSTRACT

This paper presents a methodology for random testing of software models. Random testing tools can be used very effectively early in the modeling process, e.g., while writing formal requirements specification for a given system. In this phase users cannot know whether a correct operational model is being built or whether the properties that the model must satisfy are correctly identified and stated. So it is very useful to have tools to quickly identify errors in the operational model or in the properties, and make appropriate corrections. Using Lurch, our random testing tool for finite-state models, we evaluated the effectiveness of random model testing by detecting manually seeded errors in an SCR specification of a real-world personnel access control system. Having detected over 80% of seeded errors quickly, our results appear to be very encouraging. We further defined and measured test coverage metrics with the goal of understanding why some of the mutants were not detected. Coverage measures allowed us to understand the pitfalls of random testing of formal models, thus providing opportunities for future improvement.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Requirements Specification for Personnel Access Control System. National Security Agency, 2003.
 
2
3
 
4
 
5
 
6
 
7
 
8
 
9
J. Cobleigh, L. Clarke, and L. Osterweil. FLAVERS: a Finite-State Verification Technique for Software Systems. IBM Systems Journal, 41(1), 2002.
10
 
11
12
 
13
 
14
R. Hamlet. Random Testing. In J. Maciniak, editor, Encyclopedia of Software Engineering. Wiley, 1994.
 
15
C. Heitmeyer, M. Archer, R. Bharadwaj, and R. Jeffords. Tools for Constructing Requirements Specifications: The SCR Toolset at the Age of Ten. International Journal of Computer Systems Science and Engineering, 20(1), 2005.
16
 
17
G. Holzmann. On-the-Fly, LTL Model Checking with SPIN. spinroot. com/spin/whatispin.html.
 
18
G. Holzmann. The SPIN Model Checker. Addison-Wesley, 2003.
 
19
 
20
K. McMillan. The SMV Model Checker. www-cad.eecs.berkeley.edu/~kenmcmil.
 
21
 
22
D. Owen and T. Menzies. Lurch: A Lightweight Alternative to Model Checking. In Proc. 15th International Conference on Software Engineering and Knowledge Engineering, 2003.
23
 
24
 
25
26

Collaborative Colleagues:
David Owen: colleagues
Dejan Desovski: colleagues
Bojan Cukic: colleagues