Risk Reduction Activities Identification in Software Component Integration for Component Based Software Development (CBSD)

Full Text (PDF, 1280KB), PP.19-31

Views: 0 Downloads: 0


Fariha Fatima 1,* Saqib Ali 1 Muhammad Usman Ashraf 2

1. Department of Computer Science, University of Agriculture, Faisalabad, Pakistan

2. Department of Computer Science, King Abdulaziz University, Jeddah, Saudi Arabia

* Corresponding author.

DOI: https://doi.org/10.5815/ijmecs.2017.04.03

Received: 12 Jan. 2017 / Revised: 8 Feb. 2017 / Accepted: 16 Mar. 2017 / Published: 8 Apr. 2017

Index Terms

Integration, CBSD, Risk Reduction Activities, Risk Mitigation


In the modern era, the ideas related to software developments are totally replaced the old traditional software development to CBSD. CBSD is the approach that can provide reusability of components to develop new software under minimum chances of risks. Beyond the CBSD features, there are still some significant risks overall the development phase. Generally, the quality of a developed software is depending upon the component integration phase. Nevertheless, component integration phase plays a tremendous role in the success of CBSD that leads to develop new risk free software. The objective of this research was to identify all the risks in CBSD and applied risk reduction activities to mitigate these risks. On the basis of the literature survey, categorized the risks into different categories. For this, an online questionnaire was performed to identify the risks and the risk reduction activities. 85% results point out that CBSD approach is the best approach as compared to the traditional approach. 80% results show that it performs the risk reduction activities, then the quality of the product improves. However, it is a step towards the mitigation of the vulnerabilities and reducing the cost of maintenance.

Cite This Paper

Fariha Fatima, Saqib Ali, Muhammad Usman Ashraf,"Risk Reduction Activities Identification in Software Component Integration for Component Based Software Development (CBSD)", International Journal of Modern Education and Computer Science(IJMECS), Vol.9, No.4, pp.19-31, 2017. DOI:10.5815/ijmecs.2017.04.03


[1]Basha, N. M. J. and Dr. S. A. Moiz. 2012. Component Based Software Development: A State of Art. ICAESM., pp. 599-604.
[2]Qureshi, M. R. J. and E. Sandhu. 2009. A validation of proposed Component Based Devlopment process. Sci. Int., 21(2): 131-135.
[3]Kaur, A. and S. Goel. 2011. Designing RIMCOTS Model for Risk Identification and Mitigation for COTS –based Software Development. pp. 24- 26.
[4]Shashank, P. S., P. Chakka and D. V. Kumar. 2010. A Systematic Literature Survey of Integration Testing in Component Based Software Engineering. ICCCT., pp. 562-568.
[5]Johar, K. A. and S. Goel. 2011. COTS Components usage Risks in Component Based Software Development. International Journal of Information Technology and Knowledge Management, 4(2): 573-575.
[6]Mahmood, S. 2011. Towards Component Based System Integration Testing Framework. Engineering, pp. 4-8.
[7]Gupta, R. and S. Raghav. 2012. Risk Assessment Techniques and Survey Method for COTS Components. IJJSEA., 3(1): 181-195.
[8]Khan, A., N. Qayyum and U. A. Khan. 2012. An Improved Model for Component Based Software Development. Software Engineering, 2(4): 138-146.
[9]Mandal, A. and S. C. Pal. 2012. Emergence of Component Based Software Engineering. IARCSSE., 2(3): 311-315.
[10]Khan, U. A., I. A. Al-Bidewi and K. Gupta. 2011. Challenges in Component Based Software Engineering as the Technology of Modern Era. IJIC., 1(2): 67-72.
[11]Kusumo, D. S., M. Staples, L. Zhu, H. Zhang and R. Jeffery. 2012. Risks of Off the Shelf Based Software Acquisition and Development: A Systematic Mapping Study and Survey. IET., pp. 233-242.
[12]Kaur, M. 2014. Analysis of Component Integration on Component Based Development Paradigm. IJESRT., 3(8): 143-146.
[13]Bannerman, P. L. 2015. A Reassessmet of Risk Management in Software Projects. Springer, pp. 1119-1134.
[14]Ray, M. and D. P. Mohaptra. 2013. Risk analysis, a guiding force in the improving of Testing. IET Softw., pp. 29-46.
[15]Mahmood, S. 2013. Empirical Study of Software Component Integration Process Activities. IET Softw., 7(2): 65-75.
[16]Pande, J. 2012. On Some Critical Issues in Component Selection in Component based Software Development. International Journal of Computer Application., 46(4): 44-50.
[17]Vale, T., I. Crnkovic, E. S. D. Almeida, P. A. D. M. S. Neto, Y. C. Cavalcanti and S. R. D. L. Meira. 2016. Twenty Eight years of Component Based Software Engineering. Sci. Dir., 111:128-148.
[18]Kathan, H., N. A. Bakar and R. Nordin. 2014. Reviewing the Challenges of Security Features in Component Based Software Development Models. IEEE., pp. 230-235.
[19]Hijazi, H., S. Alqrainy, H. Muaidi and T. Khdour. 2014. Identifying Casualty Relation between Software Projects Risk Factors. IJSEIA., 8(2): 51-58.