Intelligent Risk Analysis Model for Mining Adaptable Reusable Component
Iyapparaja Meenakshisundaram1 and Sureshkumar Sreedharan2
1School of Information Technology and Engineering, Anna University, India
2Vivekanandha College of Technology for Women, India
Abstract: Every elucidation for today’s quandary has been achieved in an easier prospect, with due respect to the experience gained by a normal man. The engineers too look out for the better way in the development cycle of software apart from its traditional approach. Software, being implemented in almost every machine, is in the urge of being developed with many improvisation techniques but obeying the time and cost constrains. Adding to the available simplifications methodologies in the development phases, the proposed Intelligent Risk Analysis Model (IRAM) would abridge the limitations of an object oriented program developed for a new software product showing betterments in time and budget needed. An object oriented program would comprise of individual and exclusive objects with indicated functionalities. Recognizing the usage of the objects in the existing programs would eliminate the necessity of a new coding, thus the component could be reused if it cannot be designated any better. This methodology does a primary verification whether there are any components which match with the stated requirements in the database of programs (e.g., C++, Java, Perl and Python). Based on the analysis of the matched component, it is categorized into Exact Match (EM), Partial Match (PM) or the Rejected Match (RM) which denotes its chances of applicability into the new product. This analysis of the correspondence in the reused object depends on the defined four parameters tuple namely Expected Language (EL), Module Description (MD), Argument Description (AD) and the Usage Threshold (UT). The component that matches exactly EM can be directly incorporated into the new software product whereas if the component falls into the other category PM then it is subjected to additional tests, Rank (R) is allotted, Intelligent Report (IR) is prepared and measures for its updating as an EM are taken. The RM component is eliminated from the list of possible outcomes at once.
Keywords: Software engineering, software reusability, object oriented programming, IR, cohesion and coupling, regression test.
Received February 3, 2013; accepted September 9, 2014