Skip to main content

A Framework to Assure the Quality of Sanity Check Process

  • Conference paper
Software Engineering and Computer Systems (ICSECS 2011)

Part of the book series: Communications in Computer and Information Science ((CCIS,volume 181))

Included in the following conference series:

Abstract

Sanity check is a process which verifies that the software under development meets its basic functional requirements. In quality audits sanity check is consider as a major activity. It performs a quick test to check the main functionality of the software. Sanity check decides the completion of development phase and makes a go/no go decision to forward the software to testing phase. The depth of sanity check process varies in different scenarios and sometimes it is considered as a full quality audit. A proper and well prepared sanity check significantly reduce the time and cost of overall project. In this paper we proposed a new framework to assure the quality of sanity check process with prioritize set of activities.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 129.00
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Lahouar, S., Rahoman, S.: Design and implementation of an expert system for data sanity checking. In: Proceedings of Southeastcon 1989, Energy and Information Technologies in the Southeast, vol, April 9-12, 1989, IEEE, Los Alamitos (1989), doi:10.1109/SECON.1989.132347

    Google Scholar 

  2. Lev-Yehudi, Y., Perry, A.: Implementing Automatic testing is not so automatic: Lessons learned from an implementation experiment in Magic Software Enterprises (1997)

    Google Scholar 

  3. Filho, W.P.P.: Quality Gates in Use-Case Driven Development. In: Proceedings of the 2006 international workshop on Software quality, WoSQ 2006 (2006), ISBN:1-59593-399-9

    Google Scholar 

  4. Lassenius, K.R.C.: Pacing Software Product Development: A Framework and Practical Implementation Guidelines (2006), ISBN 951-22-8382-4

    Google Scholar 

  5. Jones, C.: By popular demand: Software estimating rules of thumb. Computer 29(3), 116 (1996), doi:10.1109/MC.1996.4859

    Article  Google Scholar 

  6. Sundmark, D., Möller, A., Nolin, M.: Monitoring Software Components- A Novel Software Engineering Approach. In: Proceedings of the 11th Asia-Pacific Software Engineering Conference (APSEC 2004). IEEE Computer Society, Los Alamitos (2004)

    Google Scholar 

  7. Mead, N., Stehney, T.: Security Quality Requirements Engineering (SQUARE) Methodology (2005)

    Google Scholar 

  8. Li, S., Xu, J., Deng, L.: Periodic Partial Validation: Cost-effective Source Code Validation Process in Cross-platform Software Development Environment. In: Proceedings of the 10th IEEE Pacific Rim International Symposium on Dependable Computing, PRDC 2004 (2004)

    Google Scholar 

  9. Weller, E.F.: Lessons from three years of inspection data. Journal of IEEE software 10(5) (1993)

    Google Scholar 

  10. Trappe, W., Zhang, Y., Nath, B.: MIAMI: Methods and Infrastructure for the Assurance of Measurement Information. In: Proceedings of the 2nd International VLDB Workshop on Data Management for Sensor Networks (2005)

    Google Scholar 

  11. Piprani, B.: Using ORM-Based Models as a Foundation for a Data Quality Firewall in an Advanced Generation Data Warehouse. Springer, Heidelberg (2006)

    Book  Google Scholar 

  12. Mellado, D., Fernández-Medina, E., Piattini, M.: A common criteria based security requirements engineering process for the development of secure information systems. Elsevier, Amsterdam (2006)

    Google Scholar 

  13. Coulter, R.E.: Ice Edge Detection and Icewater Classification Utilizing the ERS-1 and TOPEX Altimeters. IEEE, Los Alamitos (1994)

    Google Scholar 

  14. Onoma, A.K., Tsai, W.K., Poonawala, M.H., Suganuma, H.: Regression Testing in an Industrial Environment. ACM Press, New York (1998)

    Google Scholar 

  15. IEEE standards, (IEEE Std 610.12-1990)

    Google Scholar 

  16. Fecko, M.A., Lott, C.M.: Lessons learned from automating tests for an operations support system, Pract. Exper. 00, 1–23 (2002)

    MATH  Google Scholar 

  17. Zhao, N.Y., Shum, M.W.: Technical Solution to Automate Smoke Test Using Rational Functional Tester and Virtualization Technology. 30th Annual International Conference on Computer Software and Applications Conference (COMPSAC 2006) 2, 367 (2006), doi:10.1109/COMPSAC.2006.166

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Sammi, R., Masood, I., Jabeen, S. (2011). A Framework to Assure the Quality of Sanity Check Process. In: Zain, J.M., Wan Mohd, W.M.b., El-Qawasmeh, E. (eds) Software Engineering and Computer Systems. ICSECS 2011. Communications in Computer and Information Science, vol 181. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-22203-0_13

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-22203-0_13

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-22202-3

  • Online ISBN: 978-3-642-22203-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics