Skip to main content
SpringerLink
Log in

Using test case patterns to estimate software development and quality management cost

  • Published:
Software Quality Journal Aims and scope Submit manuscript

Abstract

A novel process to discover test case patterns is proposed. This has led to the construction of a test case patterns catalogue. The catalogue has been analysed to estimate the potential reusability in different software applications. This has shown that 43% of system functions are generally application domain independent, whereas 57% are application domain dependent. Statistical tests showed that the level of specialisation in software systems could be as low as 20%, which supports the direction taken in this research to reuse test case patterns in software engineering activities, in particular, software cost estimation at the early sages of software development.

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

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7

Similar content being viewed by others

References

  • Acosta, A., & Zambrano, N. (2004). Patterns and objects for user interface construction. Journal of Object Technology, 3(3), 75–90.

    Google Scholar 

  • Alexander, C., Ishikawa, S., Silverstein, M., Jacobson, M., Fiksdahl-King, I., & Angel, S. (1977). A pattern language: Towns, buildings, construction. NY: Oxford University Press.

    Google Scholar 

  • American Productivity and Quality Center. (2004). Process classification framework. Houston: APQC.

    Google Scholar 

  • Anda, B., Angelvik, E., & Ribu, K. (2002). Improving estimation practices by applying use case models. In: Proceedings of 4th international conference on product focused software process improvement PROFES 2002 (pp. 383–397). Rovaniemi, Finland: Springer-Verlag.

  • Biddle, R., Nobel, J., & Tempero, E. (2001). Patterns for essential use cases. In: Proceedings of KoalaPLoP (pp. 1–15) Newzeland Victoria University.

  • Binder, R. (1999). Testing object-oriented systems: Models, patterns, and tools. Reading, MA: Addison-Wesley.

    Google Scholar 

  • Boehm, B., Abts, C., & Chulani, S. (2000a). Software development cost estimation approaches—a survey. Annals of Software Engineering, 10(1–4), 177–205. doi:10.1023/A:1018991717352.

    Article  MATH  Google Scholar 

  • Boehm, B., Horowitz, E., Madachy, R., Reifer, D., Clark, B., Steece, B., et al. (2000b). Software cost estimation with Cocomo II. Upper Saddle River, NJ: Prentice Hall.

    Google Scholar 

  • Booch, G., Rumbaugh, J., & Jacobson, I. (1999). The unified modeling language user guide. Reading, MA: Addison-Wesley.

    Google Scholar 

  • Coad, P. (1992). Object-oriented patterns. Communications of the ACM, 35(9), 152–159. doi:10.1145/130994.131006.

    Article  Google Scholar 

  • Coad, P. (1997). Object models: Strategies, patterns, and applications. Englewood Cliffs, NJ: Yourdon.

    Google Scholar 

  • CRM and Content Center. (2003). CRM glossary. Resource document. http://www.crmandcontactcentre-247.com/Default.aspx. Accessed 16 Sep 2004.

  • Diaz, I., Losavio, F., Matteo, A., & Pastor, O. (2004). A specification pattern for use cases. Information & Management, 41(8), 961–975.

    Article  Google Scholar 

  • Fowler, M. (1997). Analysis patterns: Reusable object models. Menlo Park, CA: Addison-Wesley Longman.

    Google Scholar 

  • Fowler, M. (2003). Patterns of enterprise application architecture. London: Addison-Wesley.

    Google Scholar 

  • Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1995). Design patterns: Elements of reusable object-oriented software. Reading, MA: Addison-Wesley.

    Google Scholar 

  • Gerber, S. B., Voelkl, K. E., & Anderson, T. W. (1997). The SPSS guide to the new statistical analysis of data by T. W. Anderson and Jeremy D. Finn. New York: Springer.

    MATH  Google Scholar 

  • Hohmann, L. (1998). Getting started with patterns. Document source. Software development magazine. http://www.lukehohmann.com/papers/gettingstartedwithpatterns.htm. Accessed 12 Dec 2003.

  • Integrant Inc. (2003). Integrant business solutions products. Document source. http://www.integrantinc.com/products.aspx. Accessed 4 Nov 2004.

  • Integrate Software. (2004). SalesBase CRM and business information software. Document source http://www.integrate-software.com/index.htm. Accessed 16 Sep 2004.

  • ISBSG. (2003). Projects data repository (Release 8). Document source. International Software Benchmarking Standards Group. http://www.isbsg.org.au/html/index2.html. Accessed 15 Jan 2004.

  • Issa, A., Abu Rub, F., & Thabata, F. (2007). Test case patterns catalogue. Technical Report of Software Engineering Research Group in Philadelphia University. PhILA-SERG-0004.

  • Kaner, C., Bach, J., & Pettichord, B. (2001). Lessons learned in software testing (1st ed.). NY: Wiley.

    Google Scholar 

  • Kruchten, P. (2002). The rational unified process: an introduction. Boston, MA: Addison-Wesley. Swedish edition.

    Google Scholar 

  • Lam, W., McDermid, J. A., & Vickers, A. J. (1997). Ten steps towards systematic requirements reuse. In: Proceedings of the 1997 3rd international symposium on requirements engineering, Annapolis, MD (pp. 6–15), Jan 6–10 1997. Los Alamitos, CA: IEEE.

  • Lange, M. (2001). Patterns for software testing. In: Proceedings of EuroPLoP (pp. 1–10). Germany.

  • Larman, C. (2002). Applying UML and patterns: An introduction to object-oriented analysis and design and the unified process (2nd ed.). Upper Saddle River, NJ: Prentice Hall PTR. c2002.

    Google Scholar 

  • Larsen, G. (1999). Designing component-based frameworks—using patterns in the UML. Communications of the ACM, 42(10), 38–45.

    Article  Google Scholar 

  • Liwu, L. (2002). Use case patterns. International Journal of Software Engineering and Knowledge Engineering, 12(1), 19–40.

    Article  Google Scholar 

  • Malone, T., Crowston, K., & Herman, G. (2003). Organizing business knowledge: The MIT process handbook. Cambridge, MA: MIT Press.

    Google Scholar 

  • NetSuite Inc. (2004). NETCRM. Source document. http://www.netsuite.com/portal/home.shtml. Accessed 16/9/2004.

  • ORACLE. (2004). ORACLE services. Source document. http://www.oracle.com/services/index.html. Accessed 16 Sep 2004.

  • Patton, R. (2005). Software testing (2nd ed.). Indianapolis, IN: Sams Publishing.

    Google Scholar 

  • Reifer, D. (2004). Industry software cost quality and productivity benchmarks. The DoD SoftwareTech News, 7(2), 3–19.

    Google Scholar 

  • Roberts, S. (1999). Requirements patterns via events/use cases. Source document. The Atlantic Systems Guild Inc. http://www.systemsguild.com/GuildSite/SQR/Requirements_Patterns.html. Accessed 12 Dec 2003.

  • Schmidt, D. (1995). Using design patterns to develop reusable object-oriented communication software. Communications of the ACM, 38(10), 65–74.

    Article  Google Scholar 

  • Schmidt, D., Fayad, M., & Johnson, R. (1996). Software patterns. Communications of the ACM, 39(10), 37–39.

    Article  Google Scholar 

  • Seruca, I., & Loucopoulos, P. (2003). Towards a systematic approach to the capture of patterns within a business domain. Journal of Systems and Software, 67(1), 1–18.

    Article  Google Scholar 

  • Sferyx Internet Based Systems. (2001). Source document. Sferyx Tools Library. http://www.sferyx.com/english/b2bcomponents/index.htm. Accessed 9 Sep 2004.

  • Sommerville, I., & Kotonya, G. (1998). Requirements engineering: processes and techniques. Chichester: Wiley.

    Google Scholar 

  • Soundarajan, N., Hallstrom, J., Shu, G., & Delibas, A. (2008). Patterns: From system design to software testing. Innovations in Systems and Software Engineering, 4(1), 71–85.

    Article  Google Scholar 

  • Tome, A. (2006). Test case design using patterns. Source document. Microsoft. http://blogs.msdn.com/alanpa/default.aspx. Accessed 1 Apr 2007.

Download references

Author information

Authors and Affiliations

  1. Software Engineering Department, Faculty of Information Technology, Philadelphia University, P.O. Box 1, Amman, 19392, Jordan

    Ayman A. Issa

  2. Management Information Systems Department, Faculty of Business and Financial Sciences, University of Petra, Amman, Jordan

    Faisal A. Abu Rub

  3. Management Information Systems Department, Faculty of Information Technology, Philadelphia University, P.O. Box 1, Amman, 19392, Jordan

    Fadi F. Thabata

Authors
  1. Ayman A. Issa
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Faisal A. Abu Rub
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Fadi F. Thabata
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Ayman A. Issa.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Issa, A.A., Abu Rub, F.A. & Thabata, F.F. Using test case patterns to estimate software development and quality management cost. Software Qual J 17, 263–281 (2009). https://doi.org/10.1007/s11219-009-9076-9

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11219-009-9076-9

Keywords

Search

Navigation