Designing Influence Metric at the Architectural Level for Improving the Reliability of a System
|
10.5120/3600-5001 |
Mitrabinda Ray and Durga Prasad Mohapatra. Article: Designing Influence Metric at the Architectural Level for Improving the Reliability of a System. International Journal of Computer Applications 29(10):16-23, September 2011. Full text available. BibTeX
@article{key:article,
author = {Mitrabinda Ray and Durga Prasad Mohapatra},
title = {Article: Designing Influence Metric at the Architectural Level for Improving the Reliability of a System},
journal = {International Journal of Computer Applications},
year = {2011},
volume = {29},
number = {10},
pages = {16-23},
month = {September},
note = {Full text available}
}
Abstract
Though some components play a major role for enhancing the quality of a system, but exactly identifying those components at the early stage is a big challenge. Metrics that are designed at the early stage guide both the test manager and the system analyst in decision making. In this paper, we propose an Influence Metric at the architectural level to get the influence of a component towards the system failures. First, we generate an intermediate graph called Sequence Diagram Graph (SDG) for a sequence diagram and compute the occurrence probability of each event within the sequence diagram based on operational profile of the system. Then, we propose an algorithm called Influence Computation Algorithm (ICA) to compute the influence of a component within a use case and within the whole system. The influence of a component c is decided by checking how many components are calling directly or indirectly the component c and the probabilities of their call to c. A component with high influence value is more sensitive towards system failures. The influence metric is applied on two well known case studies and the sensitivity analysis is conducted through a set of experiments to validate our approach.
Reference
- Sommerville, I.: Software Engineering. 5th Edn. Pearson (1995).
- Musa, J.D.: Operational profiles in Software-Reliability Engineering. IEEE Softw. 10(2) (1993), pp. 14-32.
- Cobb, R.H., Mills, H.D.: Engineering Software under Statistical Quality Control. IEEE Softw. 7(6) (1990), pp. 44-54.
- Musa, J.D.: Software Reliability Engineering: More Reliable Software Faster and Cheaper. AuthorHouse (2004).
- Ray, M., Kumawat, K., L., and Mohapatra, D., P.: Source code prioritization using forward slicing for exposing critical elements in a program. Journal of Computer Science and Technology 26(2) (2011), pp. 314-327.
- Ray, M., Mohapatra, D.P.: Reliability improvement based on prioritization of source code. In Janowski, T., Mohanty, H., eds.: ICDCIT. Volume 5966 of Lecture Notes in Computer Science. Springer (2010), pp. 212-223.
- Yacoub, S., M., Cukic, B., and Ammar, H., H.. Scenario-based reliability analysis of component-based software. IEEE Transactions on Reliability, 53(04) (2004), pp.465–480.
- Sarma, M. and Mall, R.. Automatic test case generation from UML models. In 10th International Conference on Information Technology (2007), pp. 197–201.
- Srikant, Y.N., Shankar, P., eds.: The Compiler Design Handbook: Optimizations and Machine Code Generation. CRC Press (2002).
- Ray, M. and Mohapatra, D., P.: A scheme to prioritize classes at the early stage for improving observable reliability. In Proceedings of the 3rd India software engineering conference, ACM, New York, NY, USA, ISEC (2010), pp. 69-72.
- ATM case study available: http://www.mathcs.gordon.edu/courses/cs211/ATMExample/.
- Eaddy, M., Zimmermann, T., Sherwood, K.D., Garg, V., Murphy, G.C., Nagappan, N., Aho, A.V.: Do crosscutting concerns cause defects? IEEE Transactions on Software Engineering 34 (2008), pp. 497–515.
- Ostrand, T.J., Weyuker, E.J., Bell, R.M.: Automating algorithms for the identification of fault-prone files. In: proceedings of the 2007 international symposium on Software testing and analysis. (2007), pp-219–227.
- Emam, K., Melo, W., Machado, C., J.: The prediction of faulty classes using object-oriented design metrics. Journal of Systems and Software 56(1) (2001), pp. 63–75.
- Ostrand, T.J., Weyuker, E.J., Bell, R.M.: Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering 31 (2005), pp. 340–355.
- Munson, J.C., Khoshgoftaar, T.M.: The detection of fault-prone programs. IEEE Trans. Softw. Eng. 18(5) (1992), pp. 423–433.
- Subramanyam, R., Krishnan, M.S.: Empirical analysis of ck metrics for object-oriented design complexity: Implications for software defects. IEEE Trans. Softw. Eng. 29(4) (2003), pp-297–310.
- Lyu, M.R.: Software reliability engineering: A roadmap. In: FOSE ’07: 2007 Future of Software Engineering (2007), pp.153–170.
- Briand, L.C., W¨ust, J., Daly, J.W., Porter, D.V.: Exploring the relationship between design measures and software quality in object-oriented systems. J. Syst. Softw. 51(3) (2000), pp. 245–273.
- Subramanyam, R., Krishnan, M.: Empirical analysis of ck metrics for object-oriented design complexity: Implications for software defects. IEEE Transactions on Software Engineering 29 (2003), pp. 297–310.
- Chidamber, S.R., Kemerer, C.F.: A metrics suite for object-oriented design. IEEE Trans. Softw. Eng. 20(6) (1994), pp. 476–493.
- Cortellessa, V., Singh, H., and Cukic, B.. Early reliability assessment of UML based software models. In WOSP’02: Proceedings of the 3rd international workshop on Software and performance (2002), pp. 302–309.
- Garousi, V., Briand, L., C., and Labiche, Y.. Analysis and visualization of behavioral dependencies among distributed objects based on UML models. Technical Report TR SCE-06-03, Carleton University, Ottawa, Canada, (2006).