a case study in database reliability component types usage profiles and testing n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
A Case Study in Database Reliability: Component Types, Usage Profiles, and Testing PowerPoint Presentation
Download Presentation
A Case Study in Database Reliability: Component Types, Usage Profiles, and Testing

Loading in 2 Seconds...

play fullscreen
1 / 13

A Case Study in Database Reliability: Component Types, Usage Profiles, and Testing - PowerPoint PPT Presentation


  • 113 Views
  • Uploaded on

A Case Study in Database Reliability: Component Types, Usage Profiles, and Testing. Colin Taylor, IBM Toronto Lab, Canada Mechelle Gittens, IBM Toronto Lab, Canada Andriy Miranskyy, University of Western Ontario, Canada. Outline. Motivation Database under test Relevant terms Case study

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'A Case Study in Database Reliability: Component Types, Usage Profiles, and Testing' - hilaire


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
a case study in database reliability component types usage profiles and testing

A Case Study in Database Reliability: Component Types,Usage Profiles, and Testing

Colin Taylor, IBM Toronto Lab, Canada

Mechelle Gittens, IBM Toronto Lab, Canada

Andriy Miranskyy, University of Western Ontario, Canada

outline
Outline
  • Motivation
  • Database under test
  • Relevant terms
  • Case study
  • Conclusion
  • Future work
motivation
Motivation
  • Improved DBMS reliability
  • Efficient assignment of DBMS testing effort
database under test
Database Under Test
  • Distributed enterprise relational DBMS
  • >20 MLOC
  • Has evolved over >20 years and >10 major versions
relevant terms
Relevant Terms
  • LOC
  • LOCC
  • Component call frequency
  • Usage profiles: FT and ST
  • Component types: Development and Architectural
  • Defects
case study
Case Study
  • Case study presented as an analysis of our perceptions
    • Contour plots
    • Tabular summary of contour plots
    • Correlation tables
case study perceptions
Case Study – Perceptions
  • Number of defects ~ LOC
  • Number of defects ~ Component call frequency
  • For the Development component type, FT Profile more strongly correlated to number of defects than ST Profile
conclusion
Conclusion
  • Weak support for Perceptions 1 and 2
  • Analysis of Perception 3 inconclusive
  • Component size, the size of changes, and call frequency are variables that impact DBMS reliability
  • Testing effort should be assigned according to relational DBMS architecture
future work
Future Work
  • Static code complexity variable
  • Component overlap
colin a taylor

Colin A. Taylor

colint@ca.ibm.com

related work
Related Work
  • Majority of studies deal with test tool implementation; only two papers consider the relationships between variables that influence DBMS reliability
    • Chays, D., Dan, S., Frankl, P. G., Vokolos, F. I., and Weber, E. J. 2000. A framework for testing database applications.
    • Deng, Y., Frankl, P., and Wang, J. 2004. Testing web database applications.
    • Suárez-Cabal, M. J. and Tuya, J. 2004. Using an SQL coverage measurement for testing database applications.
    • Wu, X., Wang, Y., and Zheng, Y. 2003. Privacy preserving database application testing.
    • Gittens, M., Lutfiyya, H., Bauer, M., Godwin, D., Kim, Y. W., and Gupta, P. 2002. An empirical evaluation of system and regression testing.
    • Sullivan, M., Chillarege, R. A comparison of software defects in database management systems and operating systems.