Indian Journal of Science and Technology
DOI: 10.17485/ijst/2019/v12i12/143201
Year: 2019, Volume: 12, Issue: 12, Pages: 1-6
Original Article
Varun K. L. Srivastava1*, N. Chandra Sekhar Reddy2 and Anubha Shrivastava3
1Association of Education Training and Research Institute (ASSOED), Noida – 201301, Uttar Pradesh, India; [email protected]
2Department of Computer Science and Engineering, MLR Institute of Technology, Dundigal – 500043, Hyderabad, Telangana, India; [email protected]
3G. L. Bajaj Institute of Technology and Management, Noida - 201301, Uttar Pradesh, India;
[email protected]
*Author for correspondence
Varun K. L. Srivastava
Association of Education Training and Research Institute (ASSOED), Noida – 201301, Uttar Pradesh, India.
Email: [email protected]
Background/Objectives: The OSS is generally unique in relation to the proprietary programming. In the OSS improvement situation an absolute designer alternately aggregation for developers composes that source book to the primary rendition of the product and makes it uninhibitedly accessible over those webs. At that point other developers would welcome to help the existing code to its next arrival. Settling on the source book of the programming accessible on the web permits developers around the universe to help code, include new functionality, change of the existing source book and submitting bug fixes of the current arrival. Previously, such a programming improvement situation the upkeep of the open hotspot product is a culprit assignment. Creating an OSS framework infers an arrangement from claiming incessant upkeep deliberations to debugging existing purpose what’s more including new purpose of the programming framework. The procedure for making those adjustments to product frameworks then afterward their initially arrival may be known as upkeep procedure. The expression maintainability may be nearly identified with that product support. Portability, adaptability and issue tolerance are the opposite essential part that ensures that seamlessness of the programming item. Those generally utilized programming metric to quantify the maintainability is known as Maintainability list (MI). Methods: In this investigation the MI from claiming four A large portion mainstream OSS to be specific Apache, Mozilla Firefox, MySql and FileZilla for fifty progressive discharges might have been observationally investigated. The MI as far as programming measurements in particular Lines about code (LOC), Cyclomatic unpredictability (CC), and Halstead Volume (V) might have been registered for every last one of fifty progressive variants about four OSS. Findings: Proposed agent based approach are cost effective, efficient and accurate solutions to evaluate the software (web application) RMA metrics including the monitoring in cloud computing services that means “Testing/Debugging as a Service Evaluation”. Proposed system has performs faster and produce more accurate results to assure the quality of the software related to the non-functional.
Keywords: Agent, Availability, Cloud Computing, Cyclomatic intricacy, Lines Code, Maintenance, Maintainability, Maintainability Index, Reliability, RMA, Software of Open Source, T/DaaS, Volume of Halstead
Subscribe now for latest articles and news.