Mitrabinda Ray and Durga P. Mohapatra


  1. [1] S. Naik and P. Tripathy, Software testing and quality assurance: Theory and practice (India: Wiley India Pvt Ltd, 2008), pages 648.
  2. [2] T.M. Khoshgoftaar, E.B. Allen, R. Halstead, G.P. Trio, and R.M. Flass, Using process history to predict software quality, Computer, 31, (April), 1998, 66–72.
  3. [3] J. Czerwonka, R. Das, N. Nagappan, A. Tarvo, and A. Teterev, Crane: Failure prediction, change analysis and test prioritization in practice – experiences from windows, Proc. Fourth IEEE International Conf. on Software Testing, Verification and Validation, Washington, DC, 2011, 357–366.
  4. [4] S. Elbaum, A. Malishevsky, and G. Rothermel, Incorporating varying test costs and fault severities into test case prioritization, Proc. 23rd International Conf. on Software Engineering, Washington, DC, 2001, 329–338.
  5. [5] M. Ray and D.P. Mohapatra, Reliability improvement based on prioritization of source code, in T. Janowski and H. Mohanty (eds.), ICDCIT. Volume 5966 of lecture notes in computer science (Germany: Springer, 2010), 212–223.
  6. [6] J.J. Li, Prioritize code for testing to improve code coverage of complex software, Proc. 16th IEEE International Symposium on Software Reliability Engineering, Washington, DC, 2005, 75–84.
  7. [7] J. Li, D. Weiss, and H. Yee, Code-coverage guided prioritized test generation, Information and Software Technology, 48 (12), 2006, 1187–1198.
  8. [8] Q. Li, Using additive multiple-objective value functions for value-based software testing prioritization, Technical Report, Computer Science Department, University of Southern California, University Park Campus, Los Angeles, CA, 2009.
  9. [9] T.J. Ostrand, E.J. Weyuker, and R.M. Bell, Automating algorithms for the identification of fault-prone files, Proc. International Symposium on Software Testing and Analysis, New York, NY, 2007, 219–227.
  10. [10] T.J. Ostrand, E.J. Weyuker, and R.M. Bell, Predicting the location and number of faults in large software systems, IEEE Transactions on Software Engineering, 31, 2005, 340–355.
  11. [11] J.D. Musa, Operational profiles in software-reliability engineering, IEEE Software, 10 (2), 1993, 14–32.
  12. [12] D. Jeffrey and N. Gupta, Experiments with test case prioritization using relevant slices, Journal of Systems and Software, 81 (2), 2008, 196–221.
  13. [13] M. Ray, K.L. Kumwat, and D.P. Mohapatra, Source code prioritization using forward slicing for exposing critical elements in a program, Journal of Computer Science and Technology, 26 (2), 2011, 314–327.
  14. [14] L.C. Briand, J.W. Daly, and J.K. Wüst, A unified framework for coupling measurement in object-oriented systems, IEEE Transaction on Software Engineering, 25 (01), 1999, 91–121.
  15. [15] L. Larsen and M.J. Harrold, Slicing object-oriented software, Proc. 18th International Conference on Software Engineering, Washington, DC, 1996, 495–505.
  16. [16] Procedures for Performing Failure Mode Effects and Criticality Analysis, US MIL_STD_1629 November 1974, US MIL_STD_1629A November 1980, US MIL_STD_1629A/Notice 2, November 1984.
  17. [17] K. Goseva-Popstojanova, A. Hassan, A. Guedem, W. Abdelmoez, D.E.M. Nassar, H. Ammar, and A. Mili, Architectural-level risk analysis using UML, IEEE Transaction on Software Engineering, 29 (10), 2003, 946–960.
  18. [18] K.E. Wiegers, First things first: Prioritizing requirements, Software Development (September 1999),
  19. [19] R. Ramler, S. Biffl, and P. Gr¨unbacher, Value-based management of software testing, ISBN:3-540-25993-7 (Berlin Heidelberg: Springer, 2005).
  20. [20] B. Boehm, and L. Huang, Value-based software engineering: A case study, IEEE Computer, 36(3), March 2003, 33–41.
  21. [21] Q. Li, M. Li, Y. Yang, Q. Wang, T. Tan, B. Boehm, and C. Hu, Bridge the gap between software test process and business value: A case study, Proc. International Conf. on Software Process: Trustworthy Software Development Processes, (Canada, LNCS:Springer-Verlag Berlin Heidelberg), 2009, 212–223.
  22. [22] J. Andrews, L. Briand, and Y. Labiche, Is mutation an appropriate tool for testing experiments? IEEE Internal Conf. on Software Engineering, St. Louis, Missouri, USA, May 2005, 402–411.
  23. [23] S.K. John, J.A. Clark, and J.A. Mcdermid, Class mutation: Mutation testing for object-oriented programs, Proc. Net. ObjectDays, (Germany: Erfurt, 2000), 9–12.
  24. [24] R. Binder, Testing object-oriented systems – models, patterns and tools (USA: Addison-Wesley, 2000).
  25. [25] A.M.R. Vincenzi, W.E. Wong, M.E. Delamaro, and J.C. Maldonado, JaBUTi Java bytecode understanding and testing: Users guide (Carlos, S. and SP, Brazil: Universidade de sãopaulo, instituto de ciencias matemáticas e de computação, March 2003).
  26. [26] M.R. Lyu, Software reliability engineering: A roadmap, FOSE ’07: 2007 Future of Software Engineering, Washington, DC, 2007, 153–170.
  27. [27] R.H. Cobb and H.D. Mills, Engineering software under statistical quality control, IEEE Software, 7 (6), 1990, 44–54.
  28. [28] R.C. Cheung, A user-oriented software reliability model, IEEE Transactions on Software Engineering, 6 (2), 1980, 118–125.

Important Links:

Go Back