CINXE.COM

<!DOCTYPE html> <html lang="en" dir="ltr"> <head>  <script async src="https://www.googletagmanager.com/gtag/js?id=G-P63WKM1TM1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-P63WKM1TM1'); </script>  <script type="text/javascript" > (function(m,e,t,r,i,k,a){m[i]=m[i]||function(){(m[i].a=m[i].a||[]).push(arguments)}; m[i].l=1*new Date(); for (var j = 0; j < document.scripts.length; j++) {if (document.scripts[j].src === r) { return; }} k=e.createElement(t),a=e.getElementsByTagName(t)[0],k.async=1,k.src=r,a.parentNode.insertBefore(k,a)}) (window, document, "script", "https://mc.yandex.ru/metrika/tag.js", "ym"); ym(55165297, "init", { clickmap:false, trackLinks:true, accurateTrackBounce:true, webvisor:false }); </script> <noscript><div><img src="https://mc.yandex.ru/watch/55165297" style="position:absolute; left:-9999px;" alt="" /></div></noscript>    <title>Search results for: software refactoring</title> <meta name="description" content="Search results for: software refactoring"> <meta name="keywords" content="software refactoring"> <meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=1, user-scalable=no"> <meta charset="utf-8"> <link href="https://cdn.waset.org/favicon.ico" type="image/x-icon" rel="shortcut icon"> <link href="https://cdn.waset.org/static/plugins/bootstrap-4.2.1/css/bootstrap.min.css" rel="stylesheet"> <link href="https://cdn.waset.org/static/plugins/fontawesome/css/all.min.css" rel="stylesheet"> <link href="https://cdn.waset.org/static/css/site.css?v=150220211555" rel="stylesheet"> </head> <body> <header> <div class="container"> <nav class="navbar navbar-expand-lg navbar-light"> <a class="navbar-brand" href="https://waset.org"> <img src="https://cdn.waset.org/static/images/wasetc.png" alt="Open Science Research Excellence" title="Open Science Research Excellence" /> </a> <button class="d-block d-lg-none navbar-toggler ml-auto" type="button" data-toggle="collapse" data-target="#navbarMenu" aria-controls="navbarMenu" aria-expanded="false" aria-label="Toggle navigation"> <span class="navbar-toggler-icon"></span> </button> <div class="w-100"> <div class="d-none d-lg-flex flex-row-reverse"> <form method="get" action="https://waset.org/search" class="form-inline my-2 my-lg-0"> <input class="form-control mr-sm-2" type="search" placeholder="Search Conferences" value="software refactoring" name="q" aria-label="Search"> <button class="btn btn-light my-2 my-sm-0" type="submit"><i class="fas fa-search"></i></button> </form> </div> <div class="collapse navbar-collapse mt-1" id="navbarMenu"> <ul class="navbar-nav ml-auto align-items-center" id="mainNavMenu"> <li class="nav-item"> <a class="nav-link" href="https://waset.org/conferences" title="Conferences in 2024/2025/2026">Conferences</a> </li> <li class="nav-item"> <a class="nav-link" href="https://waset.org/disciplines" title="Disciplines">Disciplines</a> </li> <li class="nav-item"> <a class="nav-link" href="https://waset.org/committees" rel="nofollow">Committees</a> </li> <li class="nav-item dropdown"> <a class="nav-link dropdown-toggle" href="#" id="navbarDropdownPublications" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"> Publications </a> <div class="dropdown-menu" aria-labelledby="navbarDropdownPublications"> <a class="dropdown-item" href="https://publications.waset.org/abstracts">Abstracts</a> <a class="dropdown-item" href="https://publications.waset.org">Periodicals</a> <a class="dropdown-item" href="https://publications.waset.org/archive">Archive</a> </div> </li> <li class="nav-item"> <a class="nav-link" href="https://waset.org/page/support" title="Support">Support</a> </li> </ul> </div> </div> </nav> </div> </header> <main> <div class="container mt-4"> <div class="row"> <div class="col-md-9 mx-auto"> <form method="get" action="https://publications.waset.org/abstracts/search"> <div id="custom-search-input"> <div class="input-group"> <i class="fas fa-search"></i> <input type="text" class="search-query" name="q" placeholder="Author, Title, Abstract, Keywords" value="software refactoring"> <input type="submit" class="btn_search" value="Search"> </div> </div> </form> </div> </div> <div class="row mt-3"> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Commenced</strong> in January 2007</div> </div> </div> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Frequency:</strong> Monthly</div> </div> </div> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Edition:</strong> International</div> </div> </div> <div class="col-sm-3"> <div class="card"> <div class="card-body"><strong>Paper Count:</strong> 4798</div> </div> </div> </div> <h1 class="mt-3 mb-3 text-center" style="font-size:1.6rem;">Search results for: software refactoring</h1> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4798</span> Refactoring Object Oriented Software through Community Detection Using Evolutionary Computation</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=R.%20Nagarani">R. Nagarani</a> </p> <p class="card-text"><strong>Abstract:</strong></p> An intrinsic property of software in a real-world environment is its need to evolve, which is usually accompanied by the increase of software complexity and deterioration of software quality, making software maintenance a tough problem. Refactoring is regarded as an effective way to address this problem. Many refactoring approaches at the method and class level have been proposed. But the extent of research on software refactoring at the package level is less. This work presents a novel approach to refactor the package structures of object oriented software using genetic algorithm based community detection. It uses software networks to represent classes and their dependencies. It uses a constrained community detection algorithm to obtain the optimized community structures in software networks, which also correspond to the optimized package structures. It finally provides a list of classes as refactoring candidates by comparing the optimized package structures with the real package structures. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=community%20detection" title="community detection">community detection</a>, <a href="https://publications.waset.org/abstracts/search?q=complex%20network" title=" complex network"> complex network</a>, <a href="https://publications.waset.org/abstracts/search?q=genetic%20algorithm" title=" genetic algorithm"> genetic algorithm</a>, <a href="https://publications.waset.org/abstracts/search?q=package" title=" package"> package</a>, <a href="https://publications.waset.org/abstracts/search?q=refactoring" title=" refactoring"> refactoring</a> </p> <a href="https://publications.waset.org/abstracts/31191/refactoring-object-oriented-software-through-community-detection-using-evolutionary-computation" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/31191.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">418</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4797</span> Code Refactoring Using Slice-Based Cohesion Metrics and AOP</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Jagannath%20Singh">Jagannath Singh</a>, <a href="https://publications.waset.org/abstracts/search?q=Durga%20Prasad%20Mohapatra"> Durga Prasad Mohapatra</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software refactoring is very essential for maintaining the software quality. It is an usual practice that we first design the software and then go for coding. But after coding is completed, if the requirement changes slightly or our expected output is not achieved, then we change the codes. For each small code change, we cannot change the design. In course of time, due to these small changes made to the code, the software design decays. Software refactoring is used to restructure the code in order to improve the design and quality of the software. In this paper, we propose an approach for performing code refactoring. We use slice-based cohesion metrics to identify the target methods which requires refactoring. After identifying the target methods, we use program slicing to divide the target method into two parts. Finally, we have used the concepts of Aspects to adjust the code structure so that the external behaviour of the original module does not change. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20refactoring" title="software refactoring">software refactoring</a>, <a href="https://publications.waset.org/abstracts/search?q=program%20slicing" title=" program slicing"> program slicing</a>, <a href="https://publications.waset.org/abstracts/search?q=AOP" title=" AOP"> AOP</a>, <a href="https://publications.waset.org/abstracts/search?q=cohesion%20metrics" title=" cohesion metrics"> cohesion metrics</a>, <a href="https://publications.waset.org/abstracts/search?q=code%20restructure" title=" code restructure"> code restructure</a>, <a href="https://publications.waset.org/abstracts/search?q=AspectJ" title=" AspectJ"> AspectJ</a> </p> <a href="https://publications.waset.org/abstracts/10366/code-refactoring-using-slice-based-cohesion-metrics-and-aop" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/10366.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">513</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4796</span> Software Cloning and Agile Environment</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ravi%20Kumar">Ravi Kumar</a>, <a href="https://publications.waset.org/abstracts/search?q=Dhrubajit%20Barman"> Dhrubajit Barman</a>, <a href="https://publications.waset.org/abstracts/search?q=Nomi%20Baruah"> Nomi Baruah</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Cloning has grown an active area in software engineering research community yielding numerous techniques, various tools and other methods for clone detection and removal. The copying, modifying a block of code is identified as cloning as it is the most basic means of software reuse. Agile Software Development is an approach which is currently being used in various software projects, so that it helps to respond the unpredictability of building software through incremental, iterative, work cadences. Software Cloning has been introduced to Agile Environment and many Agile Software Development approaches are using the concept of Software Cloning. This paper discusses the various Agile Software Development approaches. It also discusses the degree to which the Software Cloning concept is being introduced in the Agile Software Development approaches. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=agile%20environment" title="agile environment">agile environment</a>, <a href="https://publications.waset.org/abstracts/search?q=refactoring" title=" refactoring"> refactoring</a>, <a href="https://publications.waset.org/abstracts/search?q=reuse" title=" reuse"> reuse</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20cloning" title=" software cloning"> software cloning</a> </p> <a href="https://publications.waset.org/abstracts/16005/software-cloning-and-agile-environment" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/16005.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">530</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4795</span> A Study of Agile Based Approaches to Improve Software Quality</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Gurmeet%20Kaur">Gurmeet Kaur</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Agile software development methods are being recognized as popular, and efficient approach to the development of software system that has a short delivery period with high quality also that meets customer requirements with zero defect. In agile software development, quality means quality of code where in the quality is maintained through the use of methods or approaches like refactoring, test driven development, behavior driven development, acceptance test driven development, and demand driven development. Software quality is measured in term of metrics such as the number of defects during development of software. Usage of above mentioned methods or approaches, reduces the possibilities of defects in developed software, and hence improve quality. This paper focuses on study of agile based quality methods or approaches for software development that ensures improved quality of software as well as reduced cost, and customer satisfaction. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=ATDD" title="ATDD">ATDD</a>, <a href="https://publications.waset.org/abstracts/search?q=BDD" title=" BDD"> BDD</a>, <a href="https://publications.waset.org/abstracts/search?q=DDD" title=" DDD"> DDD</a>, <a href="https://publications.waset.org/abstracts/search?q=TDD" title=" TDD"> TDD</a> </p> <a href="https://publications.waset.org/abstracts/118869/a-study-of-agile-based-approaches-to-improve-software-quality" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/118869.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">172</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4794</span> User-Driven Product Line Engineering for Assembling Large Families of Software</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Zhaopeng%20Xuan">Zhaopeng Xuan</a>, <a href="https://publications.waset.org/abstracts/search?q=Yuan%20Bian"> Yuan Bian</a>, <a href="https://publications.waset.org/abstracts/search?q=C.%20Cailleaux"> C. Cailleaux</a>, <a href="https://publications.waset.org/abstracts/search?q=Jing%20Qin"> Jing Qin</a>, <a href="https://publications.waset.org/abstracts/search?q=S.%20Traore"> S. Traore</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Traditional software engineering allows engineers to propose to their clients multiple specialized software distributions assembled from a shared set of software assets. The management of these assets however requires a trade-off between client satisfaction and software engineering process. Clients have more and more difficult to find a distribution or components based on their needs from all of distributed repositories. This paper proposes a software engineering for a user-driven software product line in which engineers define a feature model but users drive the actual software distribution on demand. This approach makes the user become final actor as a release manager in software engineering process, increasing user product satisfaction and simplifying user operations to find required components. In addition, it provides a way for engineers to manage and assembly large software families. As a proof of concept, a user-driven software product line is implemented for eclipse, an integrated development environment. An eclipse feature model is defined, which is exposed to users on a cloud-based built platform from which clients can download individualized Eclipse distributions. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20product%20line" title="software product line">software product line</a>, <a href="https://publications.waset.org/abstracts/search?q=model-driven%20development" title=" model-driven development"> model-driven development</a>, <a href="https://publications.waset.org/abstracts/search?q=reverse%20engineering%20and%20refactoring" title=" reverse engineering and refactoring"> reverse engineering and refactoring</a>, <a href="https://publications.waset.org/abstracts/search?q=agile%20method" title=" agile method"> agile method</a> </p> <a href="https://publications.waset.org/abstracts/9008/user-driven-product-line-engineering-for-assembling-large-families-of-software" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/9008.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">433</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4793</span> Applying Serious Game Design Frameworks to Existing Games for Integration of Custom Learning Objectives</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Jonathan%20D.%20Moore">Jonathan D. Moore</a>, <a href="https://publications.waset.org/abstracts/search?q=Mark%20G.%20Reith"> Mark G. Reith</a>, <a href="https://publications.waset.org/abstracts/search?q=David%20S.%20Long"> David S. Long</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Serious games (SGs) have been shown to be an effective teaching tool in many contexts. Because of the success of SGs, several design frameworks have been created to expedite the process of making original serious games to teach specific learning objectives (LOs). Even with these frameworks, the time required to create a custom SG from conception to implementation can range from months to years. Furthermore, it is even more difficult to design a game framework that allows an instructor to create customized game variants supporting multiple LOs within the same field. This paper proposes a refactoring methodology to apply the theoretical principles from well-established design frameworks to a pre-existing serious game. The expected result is a generalized game that can be quickly customized to teach LOs not originally targeted by the game. This methodology begins by describing the general components in a game, then uses a combination of two SG design frameworks to extract the teaching elements present in the game. The identified teaching elements are then used as the theoretical basis to determine the range of LOs that can be taught by the game. This paper evaluates the proposed methodology by presenting a case study of refactoring the serious game Battlespace Next (BSN) to teach joint military capabilities. The range of LOs that can be taught by the generalized BSN are identified, and examples of creating custom LOs are given. Survey results from users of the generalized game are also provided. Lastly, the expected impact of this work is discussed and a road map for future work and evaluation is presented. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=serious%20games" title="serious games">serious games</a>, <a href="https://publications.waset.org/abstracts/search?q=learning%20objectives" title=" learning objectives"> learning objectives</a>, <a href="https://publications.waset.org/abstracts/search?q=game%20design" title=" game design"> game design</a>, <a href="https://publications.waset.org/abstracts/search?q=learning%20theory" title=" learning theory"> learning theory</a>, <a href="https://publications.waset.org/abstracts/search?q=game%20framework" title=" game framework"> game framework</a> </p> <a href="https://publications.waset.org/abstracts/156029/applying-serious-game-design-frameworks-to-existing-games-for-integration-of-custom-learning-objectives" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/156029.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">115</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4792</span> Software Engineering Revolution Driven by Complexity Science</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Jay%20Xiong">Jay Xiong</a>, <a href="https://publications.waset.org/abstracts/search?q=Li%20Lin"> Li Lin</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper introduces a new software engineering paradigm based on complexity science, called NSE (Nonlinear Software Engineering paradigm). The purpose of establishing NSE is to help software development organizations double their productivity, half their cost, and increase the quality of their products in several orders of magnitude simultaneously. NSE complies with the essential principles of complexity science. NSE brings revolutionary changes to almost all aspects in software engineering. NSE has been fully implemented with its support platform Panorama++. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=complexity%20science" title="complexity science">complexity science</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20development" title=" software development"> software development</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20maintenance" title=" software maintenance"> software maintenance</a> </p> <a href="https://publications.waset.org/abstracts/41084/software-engineering-revolution-driven-by-complexity-science" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/41084.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">265</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4791</span> Software Architectural Design Ontology</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Muhammad%20Irfan%20Marwat">Muhammad Irfan Marwat</a>, <a href="https://publications.waset.org/abstracts/search?q=Sadaqat%20Jan"> Sadaqat Jan</a>, <a href="https://publications.waset.org/abstracts/search?q=Syed%20Zafar%20Ali%20Shah"> Syed Zafar Ali Shah</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software architecture plays a key role in software development but absence of formal description of software architecture causes different impede in software development. To cope with these difficulties, ontology has been used as artifact. This paper proposes ontology for software architectural design based on IEEE model for architecture description and Kruchten 4+1 model for viewpoints classification. For categorization of style and views, ISO/IEC 42010 has been used. Corpus method has been used to evaluate ontology. The main aim of the proposed ontology is to classify and locate software architectural design information. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=semantic-based%20software%20architecture" title="semantic-based software architecture">semantic-based software architecture</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20architecture" title=" software architecture"> software architecture</a>, <a href="https://publications.waset.org/abstracts/search?q=ontology" title=" ontology"> ontology</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a> </p> <a href="https://publications.waset.org/abstracts/2056/software-architectural-design-ontology" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/2056.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">549</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4790</span> Influence of Security Attributes in Component-Based Software Development</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Somayeh%20Zeinali">Somayeh Zeinali</a> </p> <p class="card-text"><strong>Abstract:</strong></p> A component is generally defined as a piece of executable software with a published interface. Component-based software engineering (CBSE) has become recognized as a new sub-discipline of software engineering. In the component-based software development, components cannot be completely secure and thus easily become vulnerable. Some researchers have investigated this issue and proposed approaches to detect component intrusions or protect distributed components. Software security also refers to the process of creating software that is considered secure.The terms “dependability”, “trustworthiness”, and “survivability” are used interchangeably to describe the properties of software security. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=component-based%20software%20development" title="component-based software development">component-based software development</a>, <a href="https://publications.waset.org/abstracts/search?q=component-based%20software%20engineering" title=" component-based software engineering "> component-based software engineering </a>, <a href="https://publications.waset.org/abstracts/search?q=software%20security%20attributes" title="software security attributes">software security attributes</a>, <a href="https://publications.waset.org/abstracts/search?q=dependability" title=" dependability"> dependability</a>, <a href="https://publications.waset.org/abstracts/search?q=component" title=" component"> component</a> </p> <a href="https://publications.waset.org/abstracts/26037/influence-of-security-attributes-in-component-based-software-development" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/26037.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">559</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4789</span> A 'Four Method Framework' for Fighting Software Architecture Erosion</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sundus%20Ayyaz">Sundus Ayyaz</a>, <a href="https://publications.waset.org/abstracts/search?q=Saad%20Rehman"> Saad Rehman</a>, <a href="https://publications.waset.org/abstracts/search?q=Usman%20Qamar"> Usman Qamar</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Architecture is the basic structure of software that states the development and advancement of a software system. Software architecture is also considered as a significant tool for the construction of high quality software systems. A clean design leads to the control, value and beauty of software resulting in its longer life while a bad design is the cause of architectural erosion where a software evolution completely fails. This paper discusses the occurrence of software architecture erosion and presents a set of methods for the detection, declaration and prevention of architecture erosion. The causes and symptoms of architecture erosion are observed with the examples of prescriptive and descriptive architectures and the practices used to stop this erosion are also discussed by considering different types of software erosion and their affects. Consequently finding and devising the most suitable approach for fighting software architecture erosion and in some way reducing its affect is evaluated and tested on different scenarios. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20architecture" title="software architecture">software architecture</a>, <a href="https://publications.waset.org/abstracts/search?q=architecture%20erosion" title=" architecture erosion"> architecture erosion</a>, <a href="https://publications.waset.org/abstracts/search?q=prescriptive%20architecture" title=" prescriptive architecture"> prescriptive architecture</a>, <a href="https://publications.waset.org/abstracts/search?q=descriptive%20architecture" title=" descriptive architecture"> descriptive architecture</a> </p> <a href="https://publications.waset.org/abstracts/19650/a-four-method-framework-for-fighting-software-architecture-erosion" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/19650.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">500</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4788</span> Reasons for Non-Applicability of Software Entropy Metrics for Bug Prediction in Android </h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Arvinder%20Kaur">Arvinder Kaur</a>, <a href="https://publications.waset.org/abstracts/search?q=Deepti%20Chopra"> Deepti Chopra</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Entropy Metrics for bug prediction have been validated on various software systems by different researchers. In our previous research, we have validated that Software Entropy Metrics calculated for Mozilla subsystem’s predict the future bugs reasonably well. In this study, the Software Entropy metrics are calculated for a subsystem of Android and it is noticed that these metrics are not suitable for bug prediction. The results are compared with a subsystem of Mozilla and a comparison is made between the two software systems to determine the reasons why Software Entropy metrics are not applicable for Android. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=android" title="android">android</a>, <a href="https://publications.waset.org/abstracts/search?q=bug%20prediction" title=" bug prediction"> bug prediction</a>, <a href="https://publications.waset.org/abstracts/search?q=mining%20software%20repositories" title=" mining software repositories"> mining software repositories</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20entropy" title=" software entropy"> software entropy</a> </p> <a href="https://publications.waset.org/abstracts/49619/reasons-for-non-applicability-of-software-entropy-metrics-for-bug-prediction-in-android" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/49619.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">578</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4787</span> Revolutionary Solutions for Modeling and Visualization of Complex Software Systems</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Jay%20Xiong">Jay Xiong</a>, <a href="https://publications.waset.org/abstracts/search?q=Li%20Lin"> Li Lin</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Existing software modeling and visualization approaches using UML are outdated, which are outcomes of reductionism and the superposition principle that the whole of a system is the sum of its parts, so that with them all tasks of software modeling and visualization are performed linearly, partially, and locally. This paper introduces revolutionary solutions for modeling and visualization of complex software systems, which make complex software systems much easy to understand, test, and maintain. The solutions are based on complexity science, offering holistic, automatic, dynamic, virtual, and executable approaches about thousand times more efficient than the traditional ones. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=complex%20systems" title="complex systems">complex systems</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20maintenance" title=" software maintenance"> software maintenance</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20modeling" title=" software modeling"> software modeling</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20visualization" title=" software visualization"> software visualization</a> </p> <a href="https://publications.waset.org/abstracts/41451/revolutionary-solutions-for-modeling-and-visualization-of-complex-software-systems" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/41451.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">401</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4786</span> Towards Development of a Framework for Saudi Education Software Ecosystem</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Fazal-e-Amin">Fazal-e-Amin</a>, <a href="https://publications.waset.org/abstracts/search?q=Abdullah%20S.%20Alghamdi"> Abdullah S. Alghamdi</a>, <a href="https://publications.waset.org/abstracts/search?q=Iftikhar%20Ahmad"> Iftikhar Ahmad</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software ecosystems’ concept is an inspiration from the natural ecosystem. Software ecosystems refer to large systems developed on top of a platform composed of different components developed by different entities of that ecosystem. Ecosystems improve information access, dissemination and coordination considerably. The ability to evolve and accommodate new subsystems gives a boost to the software ecosystems. In this paper, Saudi education software ecosystem is discussed and its need and potential benefits are highlighted. This work will provide a basis for further research in this area and foundation in development of Saudi education ecosystem. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20ecosystem" title="software ecosystem">software ecosystem</a>, <a href="https://publications.waset.org/abstracts/search?q=education%20software" title=" education software"> education software</a>, <a href="https://publications.waset.org/abstracts/search?q=framework" title=" framework"> framework</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a> </p> <a href="https://publications.waset.org/abstracts/5173/towards-development-of-a-framework-for-saudi-education-software-ecosystem" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/5173.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">531</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4785</span> Analyzing the Effectiveness of Different Testing Techniques in Ensuring Software Quality</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=R.%20M.%20P.%20C.%20Bandara">R. M. P. C. Bandara</a>, <a href="https://publications.waset.org/abstracts/search?q=M.%20L.%20L.%20Weerasinghe"> M. L. L. Weerasinghe</a>, <a href="https://publications.waset.org/abstracts/search?q=K.%20T.%20C.%20R.%20Kumari"> K. T. C. R. Kumari</a>, <a href="https://publications.waset.org/abstracts/search?q=A.%20G.%20D.%20R.%20Hansika"> A. G. D. R. Hansika</a>, <a href="https://publications.waset.org/abstracts/search?q=D.%20I.%20De%20Silva"> D. I. De Silva</a>, <a href="https://publications.waset.org/abstracts/search?q=D.%20M.%20T.%20H.%20Dias"> D. M. T. H. Dias</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software testing is an essential process in software development that aims to identify defects and ensure that software is functioning as intended. Various testing techniques are employed to achieve this goal, but the effectiveness of these techniques varies. This research paper analyzes the effectiveness of different testing techniques in ensuring software quality. The paper explores different testing techniques, including manual and automated testing, and evaluates their effectiveness in terms of identifying defects, reducing the number of defects in software, and ensuring that software meets its functional and non-functional requirements. Moreover, the paper will also investigate the impact of factors such as testing time, test coverage, and testing environment on the effectiveness of these techniques. This research aims to provide valuable insights into the effectiveness of different testing techniques, enabling software development teams to make informed decisions about the testing approach that is best suited to their needs. By improving testing techniques, the number of defects in software can be reduced, enhancing the quality of software and ultimately providing better software for users. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20life%20cycle" title="software testing life cycle">software testing life cycle</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20techniques" title=" software testing techniques"> software testing techniques</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20testing%20strategies" title=" software testing strategies"> software testing strategies</a>, <a href="https://publications.waset.org/abstracts/search?q=effectiveness" title=" effectiveness"> effectiveness</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title=" software quality"> software quality</a> </p> <a href="https://publications.waset.org/abstracts/166772/analyzing-the-effectiveness-of-different-testing-techniques-in-ensuring-software-quality" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/166772.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">84</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4784</span> Software Quality Assurance in Component Based Software Development – a Survey Analysis</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Abeer%20Toheed%20Quadri">Abeer Toheed Quadri</a>, <a href="https://publications.waset.org/abstracts/search?q=Maria%20Abubakar"> Maria Abubakar</a>, <a href="https://publications.waset.org/abstracts/search?q=Mehreen%20Sirshar"> Mehreen Sirshar</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Component Based Software Development (CBSD) is a new trend in software development. Selection of quality components is not enough to ensure software quality in Component Based Software System (CBSS). A software product is considered to be a quality product if it satisfies its customer’s needs and has minimum defects. Authors’ survey different research papers and analyzes various techniques which ensure software quality in component based software development. This paper includes an investigation about how to improve the quality of a component based software system without effecting quality attributes. The reported information is identified from literature survey. The developments of component based systems are rising as they reduce the development time, effort and cost by means of reuse. After analysis, it has been explored that in order to achieve the quality in a CBSS we need to have the components that are certified through software measure because the predictability of software quality attributes of system depend on the quality attributes of the constituent components, integration process and the framework used. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=CBSD%20%28component%20based%20software%20development%29" title="CBSD (component based software development)">CBSD (component based software development)</a>, <a href="https://publications.waset.org/abstracts/search?q=CBSS%20%28component%20based%20software%20system%29" title=" CBSS (component based software system)"> CBSS (component based software system)</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20components" title=" quality components"> quality components</a>, <a href="https://publications.waset.org/abstracts/search?q=SQA%20%28software%20quality%20assurance%29" title=" SQA (software quality assurance)"> SQA (software quality assurance)</a> </p> <a href="https://publications.waset.org/abstracts/26167/software-quality-assurance-in-component-based-software-development-a-survey-analysis" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/26167.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">413</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4783</span> Some Pertinent Issues and Considerations on CBSE</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Anil%20Kumar%20Tripathi">Anil Kumar Tripathi</a>, <a href="https://publications.waset.org/abstracts/search?q=Ratneshwer%20Gupta"> Ratneshwer Gupta</a> </p> <p class="card-text"><strong>Abstract:</strong></p> All the software engineering researches and best industry practices aim at providing software products with high degree of quality and functionality at low cost and less time. These requirements are addressed by the Component Based Software Engineering (CBSE) as well. CBSE, which deals with the software construction by components’ assembly, is a revolutionary extension of Software Engineering. CBSE must define and describe processes to assure timely completion of high quality software systems that are composed of a variety of pre built software components. Though these features provide distinct and visible benefits in software design and programming, they also raise some challenging problems. The aim of this work is to summarize the pertinent issues and considerations in CBSE to make an understanding in forms of concepts and observations that may lead to development of newer ways of dealing with the problems and challenges in CBSE. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20component" title="software component">software component</a>, <a href="https://publications.waset.org/abstracts/search?q=component%20based%20software%20engineering" title=" component based software engineering"> component based software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20process" title=" software process"> software process</a>, <a href="https://publications.waset.org/abstracts/search?q=testing" title=" testing"> testing</a>, <a href="https://publications.waset.org/abstracts/search?q=maintenance" title=" maintenance"> maintenance</a> </p> <a href="https://publications.waset.org/abstracts/21943/some-pertinent-issues-and-considerations-on-cbse" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/21943.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">401</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4782</span> Effectiveness of Software Quality Assurance in Offshore Development Enterprises in Sri Lanka</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Malinda%20Gayan%20Sirisena">Malinda Gayan Sirisena</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The aim of this research is to evaluate the effectiveness of software quality assurance approaches of Sri Lankan offshore software development organizations, and to propose a framework which could be used across all offshore software development organizations. An empirical study was conducted using derived framework from popular software quality evaluation models. The research instrument employed was a questionnaire survey among thirty seven Sri Lankan registered offshore software development organizations. The findings demonstrate a positive view of Effectiveness of Software Quality Assurance – the stronger predictors of Stability, Installability, Correctness, Testability and Changeability. The present study’s recommendations indicate a need for much emphasis on software quality assurance for the Sri Lankan offshore software development organizations. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20quality%20assurance%20%28SQA%29" title="software quality assurance (SQA)">software quality assurance (SQA)</a>, <a href="https://publications.waset.org/abstracts/search?q=offshore%20software%20development" title=" offshore software development"> offshore software development</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20assurance%20evaluation%20models" title=" quality assurance evaluation models"> quality assurance evaluation models</a>, <a href="https://publications.waset.org/abstracts/search?q=effectiveness%20of%20quality%20assurance" title=" effectiveness of quality assurance"> effectiveness of quality assurance</a> </p> <a href="https://publications.waset.org/abstracts/8370/effectiveness-of-software-quality-assurance-in-offshore-development-enterprises-in-sri-lanka" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/8370.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">421</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4781</span> Improving Security by Using Secure Servers Communicating via Internet with Standalone Secure Software</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Carlos%20Gonzalez">Carlos Gonzalez</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper describes the use of the Internet as a feature to enhance the security of our software that is going to be distributed/sold to users potentially all over the world. By placing in a secure server some of the features of the secure software, we increase the security of such software. The communication between the protected software and the secure server is done by a double lock algorithm. This paper also includes an analysis of intruders and describes possible responses to detect threats. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=internet" title="internet">internet</a>, <a href="https://publications.waset.org/abstracts/search?q=secure%20software" title=" secure software"> secure software</a>, <a href="https://publications.waset.org/abstracts/search?q=threats" title=" threats"> threats</a>, <a href="https://publications.waset.org/abstracts/search?q=cryptography%20process" title=" cryptography process"> cryptography process</a> </p> <a href="https://publications.waset.org/abstracts/59586/improving-security-by-using-secure-servers-communicating-via-internet-with-standalone-secure-software" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/59586.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">333</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4780</span> A Software Engineering Methodology for Developing Secure Obfuscated Software</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Carlos%20Gonzalez">Carlos Gonzalez</a>, <a href="https://publications.waset.org/abstracts/search?q=Ernesto%20Linan"> Ernesto Linan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> We propose a methodology to conciliate two apparently contradictory processes in the development of secure obfuscated software and good software engineered software. Our methodology consists first in the system designers defining the type of security level required for the software. There are four types of attackers: casual attackers, hackers, institution attack, and government attack. Depending on the level of threat, the methodology we propose uses five or six teams to accomplish this task. One Software Engineer Team and one or two software Obfuscation Teams, and Compiler Team, these four teams will develop and compile the secure obfuscated software, a Code Breakers Team will test the results of the previous teams to see if the software is not broken at the required security level, and an Intrusion Analysis Team will analyze the results of the Code Breakers Team and propose solutions to the development teams to prevent the detected intrusions. We also present an analytical model to prove that our methodology is no only easier to use, but generates an economical way of producing secure obfuscated software. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=development%20methodology" title="development methodology">development methodology</a>, <a href="https://publications.waset.org/abstracts/search?q=obfuscated%20software" title=" obfuscated software"> obfuscated software</a>, <a href="https://publications.waset.org/abstracts/search?q=secure%20software%20development" title=" secure software development"> secure software development</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a> </p> <a href="https://publications.waset.org/abstracts/78465/a-software-engineering-methodology-for-developing-secure-obfuscated-software" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/78465.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">250</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4779</span> Heterogeneous Artifacts Construction for Software Evolution Control</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Mounir%20Zekkaoui">Mounir Zekkaoui</a>, <a href="https://publications.waset.org/abstracts/search?q=Abdelhadi%20Fennan"> Abdelhadi Fennan </a> </p> <p class="card-text"><strong>Abstract:</strong></p> The software evolution control requires a deep understanding of the changes and their impact on different system heterogeneous artifacts. And an understanding of descriptive knowledge of the developed software artifacts is a prerequisite condition for the success of the evolutionary process. The implementation of an evolutionary process is to make changes more or less important to many heterogeneous software artifacts such as source code, analysis and design models, unit testing, XML deployment descriptors, user guides, and others. These changes can be a source of degradation in functional, qualitative or behavioral terms of modified software. Hence the need for a unified approach for extraction and representation of different heterogeneous artifacts in order to ensure a unified and detailed description of heterogeneous software artifacts, exploitable by several software tools and allowing to responsible for the evolution of carry out the reasoning change concerned. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=heterogeneous%20software%20artifacts" title="heterogeneous software artifacts">heterogeneous software artifacts</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20evolution%20control" title=" software evolution control"> software evolution control</a>, <a href="https://publications.waset.org/abstracts/search?q=unified%20approach" title=" unified approach"> unified approach</a>, <a href="https://publications.waset.org/abstracts/search?q=meta%20model" title=" meta model"> meta model</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20architecture" title=" software architecture"> software architecture</a> </p> <a href="https://publications.waset.org/abstracts/13647/heterogeneous-artifacts-construction-for-software-evolution-control" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/13647.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">445</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4778</span> Neural Network Based Approach of Software Maintenance Prediction for Laboratory Information System</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Vuk%20M.%20Popovic">Vuk M. Popovic</a>, <a href="https://publications.waset.org/abstracts/search?q=Dunja%20D.%20Popovic"> Dunja D. Popovic</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software maintenance phase is started once a software project has been developed and delivered. After that, any modification to it corresponds to maintenance. Software maintenance involves modifications to keep a software project usable in a changed or a changing environment, to correct discovered faults, and modifications, and to improve performance or maintainability. Software maintenance and management of software maintenance are recognized as two most important and most expensive processes in a life of a software product. This research is basing the prediction of maintenance, on risks and time evaluation, and using them as data sets for working with neural networks. The aim of this paper is to provide support to project maintenance managers. They will be able to pass the issues planned for the next software-service-patch to the experts, for risk and working time evaluation, and afterward to put all data to neural networks in order to get software maintenance prediction. This process will lead to the more accurate prediction of the working hours needed for the software-service-patch, which will eventually lead to better planning of budget for the software maintenance projects. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=laboratory%20information%20system" title="laboratory information system">laboratory information system</a>, <a href="https://publications.waset.org/abstracts/search?q=maintenance%20engineering" title=" maintenance engineering"> maintenance engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=neural%20networks" title=" neural networks"> neural networks</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20maintenance" title=" software maintenance"> software maintenance</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20maintenance%20costs" title=" software maintenance costs"> software maintenance costs</a> </p> <a href="https://publications.waset.org/abstracts/68789/neural-network-based-approach-of-software-maintenance-prediction-for-laboratory-information-system" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/68789.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">358</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4777</span> Software Quality Measurement System for Telecommunication Industry in Malaysia</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Nor%20Fazlina%20Iryani%20Abdul%20Hamid">Nor Fazlina Iryani Abdul Hamid</a>, <a href="https://publications.waset.org/abstracts/search?q=Mohamad%20Khatim%20Hasan"> Mohamad Khatim Hasan </a> </p> <p class="card-text"><strong>Abstract:</strong></p> Evolution of software quality measurement has been started since McCall introduced his quality model in year 1977. Starting from there, several software quality models and software quality measurement methods had emerged but none of them focused on telecommunication industry. In this paper, the implementation of software quality measurement system for telecommunication industry was compulsory to accommodate the rapid growth of telecommunication industry. The quality value of the telecommunication related software could be calculated using this system by entering the required parameters. The system would calculate the quality value of the measured system based on predefined quality metrics and aggregated by referring to the quality model. It would classify the quality level of the software based on Net Satisfaction Index (NSI). Thus, software quality measurement system was important to both developers and users in order to produce high quality software product for telecommunication industry. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title="software quality">software quality</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20measurement" title=" quality measurement"> quality measurement</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20model" title=" quality model"> quality model</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20metric" title=" quality metric"> quality metric</a>, <a href="https://publications.waset.org/abstracts/search?q=net%20satisfaction%20index" title=" net satisfaction index"> net satisfaction index</a> </p> <a href="https://publications.waset.org/abstracts/15875/software-quality-measurement-system-for-telecommunication-industry-in-malaysia" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/15875.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">592</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4776</span> The Comparison of Open Source Software for Digital Libraries</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Kanita%20Be%C5%A1irevi%C4%87">Kanita Beširević</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Open-source software development activities highly rely on Internet gathering communities volunteering in software development projects. Additionally, the libraries and cultural institutions share their metadata in the form of linked metadata to enable dissemination and enrichment. The open-source software provides free alternatives to traditional software solutions. The article aims to investigate the ever-increasing options for the digital library open source software adoption. The software available is presented and compared to other software solutions as well as to their previous versions. The top three open-source digital library software solutions are presented and compared. The comparison criteria are adopted from the UNESCO study by Bankier, J., & Gleason, K. Institutional Repository Software Comparison comprising of twelve criteria to appraise software, namely: infrastructure, front-end design, content discovery, publication tools, interoperability, and preservation. This article adopts a descriptive methodology based on data and information collected through selected software websites and the literature review. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=open%20source%20software" title="open source software">open source software</a>, <a href="https://publications.waset.org/abstracts/search?q=digital%20library" title=" digital library"> digital library</a>, <a href="https://publications.waset.org/abstracts/search?q=DSpace" title=" DSpace"> DSpace</a>, <a href="https://publications.waset.org/abstracts/search?q=Fedora" title=" Fedora"> Fedora</a>, <a href="https://publications.waset.org/abstracts/search?q=Greenstone" title=" Greenstone"> Greenstone</a> </p> <a href="https://publications.waset.org/abstracts/155592/the-comparison-of-open-source-software-for-digital-libraries" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/155592.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">116</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4775</span> Importance of Hardware Systems and Circuits in Secure Software Development Life Cycle</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Mir%20Shahriar%20Emami">Mir Shahriar Emami</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Although it is fully impossible to ensure that a software system is quite secure, developing an acceptable secure software system in a convenient platform is not unreachable. In this paper, we attempt to analyze software development life cycle (SDLC) models from the hardware systems and circuits point of view. To date, the SDLC models pay merely attention to the software security from the software perspectives. In this paper, we present new features for SDLC stages to emphasize the role of systems and circuits in developing secure software system through the software development stages, the point that has not been considered previously in the SDLC models. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=SDLC" title="SDLC">SDLC</a>, <a href="https://publications.waset.org/abstracts/search?q=SSDLC" title=" SSDLC"> SSDLC</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20security" title=" software security"> software security</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20process%20engineering" title=" software process engineering"> software process engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=hardware%20systems%20and%20circuits%20security" title=" hardware systems and circuits security"> hardware systems and circuits security</a> </p> <a href="https://publications.waset.org/abstracts/55558/importance-of-hardware-systems-and-circuits-in-secure-software-development-life-cycle" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/55558.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">261</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4774</span> Four Phase Methodology for Developing Secure Software</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Carlos%20Gonzalez-Flores">Carlos Gonzalez-Flores</a>, <a href="https://publications.waset.org/abstracts/search?q=Ernesto%20Li%C3%B1an-Garc%C3%ADa"> Ernesto Liñan-García</a> </p> <p class="card-text"><strong>Abstract:</strong></p> A simple and robust approach for developing secure software. A Four Phase methodology consists in developing the non-secure software in phase one, and for the next three phases, one phase for each of the secure developing types (i.e. self-protected software, secure code transformation, and the secure shield). Our methodology requires first the determination and understanding of the type of security level needed for the software. The methodology proposes the use of several teams to accomplish this task. One Software Engineering Developing Team, a Compiler Team, a Specification and Requirements Testing Team, and for each of the secure software developing types: three teams of Secure Software Developing, three teams of Code Breakers, and three teams of Intrusion Analysis. These teams will interact among each other and make decisions to provide a secure software code protected against a required level of intruder. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=secure%20software" title="secure software">secure software</a>, <a href="https://publications.waset.org/abstracts/search?q=four%20phases%20methodology" title=" four phases methodology"> four phases methodology</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=code%20breakers" title=" code breakers"> code breakers</a>, <a href="https://publications.waset.org/abstracts/search?q=intrusion%20analysis" title=" intrusion analysis"> intrusion analysis</a> </p> <a href="https://publications.waset.org/abstracts/38126/four-phase-methodology-for-developing-secure-software" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/38126.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">399</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4773</span> Investigating Software Engineering Challenges in Game Development</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Fawad%20Zaidi">Fawad Zaidi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper discusses a variety of challenges and solutions involved with creating computer games and the issues faced by the software engineers working in this field. This review further investigates the articles coverage of project scope and the problem of feature creep that appears to be inherent with game development. The paper tries to answer the following question: Is this a problem caused by a shortage, or bad software engineering practices, or is this outside the control of the software engineering component of the game production process? <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title="software engineering">software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=computer%20games" title=" computer games"> computer games</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20applications" title=" software applications"> software applications</a>, <a href="https://publications.waset.org/abstracts/search?q=development" title=" development"> development</a> </p> <a href="https://publications.waset.org/abstracts/1774/investigating-software-engineering-challenges-in-game-development" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/1774.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">475</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4772</span> Software Quality Promotion and Improvement through Usage of a PSP Oriented Information System </h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Gaoussou%20Doukoure%20Abdel%20Kader">Gaoussou Doukoure Abdel Kader</a>, <a href="https://publications.waset.org/abstracts/search?q=Mnkandla%20Ernest"> Mnkandla Ernest</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This research aims to investigate the usage of a personal software process oriented information system in order to facilitate the promotion of software quality and its improvement in organizations. In this light, at the term of a literature review on software quality and related concepts, the personal software process is discussed, more particularly in terms of software quality. Semi-structured interviews will be conducted with a team of software engineers on the first hand to establish a baseline on their understanding of what quality entails for them. The PSP methodology will then be presented to the engineers in its most basic aspects. The research will then proceed to practical case study where a PSP oriented information system is submitted to engineers for usage throughout their development process. Reports from the PSP information system as well as feedback from the engineers will be used in conjunction with the theoretical foundation to establish a PSP inspired framework for software quality promotion and improvement. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=information%20communication%20technology" title="information communication technology">information communication technology</a>, <a href="https://publications.waset.org/abstracts/search?q=personal%20software%20process" title=" personal software process"> personal software process</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title=" software quality"> software quality</a>, <a href="https://publications.waset.org/abstracts/search?q=process%20quality" title=" process quality"> process quality</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering" title=" software engineering"> software engineering</a> </p> <a href="https://publications.waset.org/abstracts/12761/software-quality-promotion-and-improvement-through-usage-of-a-psp-oriented-information-system" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/12761.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">494</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4771</span> Effectiveness of Adopting Software Quality Frameworks in Software Organizations: A Qualitative Review</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sarah%20K.%20Amer">Sarah K. Amer</a>, <a href="https://publications.waset.org/abstracts/search?q=Nagwa%20Badr"> Nagwa Badr</a>, <a href="https://publications.waset.org/abstracts/search?q=Osman%20Ibrahim"> Osman Ibrahim</a>, <a href="https://publications.waset.org/abstracts/search?q=Ahmed%20Hamad"> Ahmed Hamad</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper surveys the effectiveness of software process quality assurance frameworks, with some focus on Capability Maturity Model Integration (CMMI) - a framework that has become widely adopted in software organizations. The importance of quality improvement in software development, and the differences in the outcomes of quality framework implementation between Middle Eastern and North African (MENA-region) countries and non-MENA-region countries are discussed. The greatest challenges met in the MENA region are identified, with particular focus on Egypt and its rising software development industry. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20quality" title="software quality">software quality</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20process%20improvement" title=" software process improvement"> software process improvement</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20development%20methodologies" title=" software development methodologies"> software development methodologies</a>, <a href="https://publications.waset.org/abstracts/search?q=capability%20maturity%20model%20integration" title=" capability maturity model integration"> capability maturity model integration</a> </p> <a href="https://publications.waset.org/abstracts/54810/effectiveness-of-adopting-software-quality-frameworks-in-software-organizations-a-qualitative-review" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/54810.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">354</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4770</span> Software Obsolescence Drivers in Aerospace: An Industry Analysis</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ra%C3%BAl%20Gonz%C3%A1lez%20Mu%C3%B1oz">Raúl González Muñoz</a>, <a href="https://publications.waset.org/abstracts/search?q=Essam%20Shehab"> Essam Shehab</a>, <a href="https://publications.waset.org/abstracts/search?q=Martin%20Weinitzke"> Martin Weinitzke</a>, <a href="https://publications.waset.org/abstracts/search?q=Chris%20Fowler"> Chris Fowler</a>, <a href="https://publications.waset.org/abstracts/search?q=Paul%20Baguley"> Paul Baguley</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software applications have become crucial for the aerospace industry, providing a wide range of functionalities and capabilities. However, due to the considerable time difference between aircraft and software life cycles, obsolescence has turned into a major challenge for industry in last decades. This paper aims to provide a view on the different causes of software obsolescence within aerospace industry, as well as a perception on the importance of each of them. The key research question addressed is what drives software obsolescence in the aerospace industry, managing large software application portfolios. This question has been addressed by conducting firstly an in depth review of current literature and secondly by arranging an industry workshop with professionals from aerospace and consulting companies. The result is a set of drivers of software obsolescence, distributed among three different environments and several domains. By incorporating monitoring methodologies to assess those software obsolescence drivers, benefits in maintenance efforts and operations disruption avoidance are expected. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=aerospace%20industry" title="aerospace industry">aerospace industry</a>, <a href="https://publications.waset.org/abstracts/search?q=obsolescence%20drivers" title=" obsolescence drivers"> obsolescence drivers</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20lifecycle" title=" software lifecycle"> software lifecycle</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20obsolescence" title=" software obsolescence"> software obsolescence</a> </p> <a href="https://publications.waset.org/abstracts/72049/software-obsolescence-drivers-in-aerospace-an-industry-analysis" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/72049.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">411</span> </span> </div> </div> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">4769</span> Supporting Embedded Medical Software Development with MDevSPICE® and Agile Practices</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Surafel%20Demissie">Surafel Demissie</a>, <a href="https://publications.waset.org/abstracts/search?q=Frank%20Keenan"> Frank Keenan</a>, <a href="https://publications.waset.org/abstracts/search?q=Fergal%20McCaffery"> Fergal McCaffery</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Emerging medical devices are highly relying on embedded software that runs on the specific platform in real time. The development of embedded software is different from ordinary software development due to the hardware-software dependency. MDevSPICE<sup>®</sup> has been developed to provide guidance to support such development. To increase the flexibility of this framework agile practices have been introduced. This paper outlines the challenges for embedded medical device software development and the structure of MDevSPICE<sup>® </sup>and suggests a suitable combination of agile practices that will help to add flexibility and address corresponding challenges of embedded medical device software development. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=agile%20practices" title="agile practices">agile practices</a>, <a href="https://publications.waset.org/abstracts/search?q=challenges" title=" challenges"> challenges</a>, <a href="https://publications.waset.org/abstracts/search?q=embedded%20software" title=" embedded software"> embedded software</a>, <a href="https://publications.waset.org/abstracts/search?q=MDevSPICE%C2%AE" title=" MDevSPICE®"> MDevSPICE®</a>, <a href="https://publications.waset.org/abstracts/search?q=medical%20device" title=" medical device"> medical device</a> </p> <a href="https://publications.waset.org/abstracts/61039/supporting-embedded-medical-software-development-with-mdevspice-and-agile-practices" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/61039.pdf" target="_blank" class="btn btn-primary btn-sm">PDF</a> <span class="bg-info text-light px-1 py-1 float-right rounded"> Downloads <span class="badge badge-light">265</span> </span> </div> </div> <ul class="pagination"> <li class="page-item disabled"><span class="page-link">&lsaquo;</span></li> <li class="page-item active"><span class="page-link">1</span></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=2">2</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=3">3</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=4">4</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=5">5</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=6">6</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=7">7</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=8">8</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=9">9</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=10">10</a></li> <li class="page-item disabled"><span class="page-link">...</span></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=159">159</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=160">160</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20refactoring&page=2" rel="next">&rsaquo;</a></li> </ul> </div> </main> <footer> <div id="infolinks" class="pt-3 pb-2"> <div class="container"> <div style="background-color:#f5f5f5;" class="p-3"> <div class="row"> <div class="col-md-2"> <ul class="list-unstyled"> About <li><a href="https://waset.org/page/support">About Us</a></li> <li><a href="https://waset.org/page/support#legal-information">Legal</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/WASET-16th-foundational-anniversary.pdf">WASET celebrates its 16th foundational anniversary</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Account <li><a href="https://waset.org/profile">My Account</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Explore <li><a href="https://waset.org/disciplines">Disciplines</a></li> <li><a href="https://waset.org/conferences">Conferences</a></li> <li><a href="https://waset.org/conference-programs">Conference Program</a></li> <li><a href="https://waset.org/committees">Committees</a></li> <li><a href="https://publications.waset.org">Publications</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Research <li><a href="https://publications.waset.org/abstracts">Abstracts</a></li> <li><a href="https://publications.waset.org">Periodicals</a></li> <li><a href="https://publications.waset.org/archive">Archive</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Open Science <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Open-Science-Philosophy.pdf">Open Science Philosophy</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Open-Science-Award.pdf">Open Science Award</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Open-Society-Open-Science-and-Open-Innovation.pdf">Open Innovation</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Postdoctoral-Fellowship-Award.pdf">Postdoctoral Fellowship Award</a></li> <li><a target="_blank" rel="nofollow" href="https://publications.waset.org/static/files/Scholarly-Research-Review.pdf">Scholarly Research Review</a></li> </ul> </div> <div class="col-md-2"> <ul class="list-unstyled"> Support <li><a href="https://waset.org/page/support">Support</a></li> <li><a href="https://waset.org/profile/messages/create">Contact Us</a></li> <li><a href="https://waset.org/profile/messages/create">Report Abuse</a></li> </ul> </div> </div> </div> </div> </div> <div class="container text-center"> <hr style="margin-top:0;margin-bottom:.3rem;"> <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" class="text-muted small">Creative Commons Attribution 4.0 International License</a> <div id="copy" class="mt-2">© 2024 World Academy of Science, Engineering and Technology</div> </div> </footer> <a href="javascript:" id="return-to-top"><i class="fas fa-arrow-up"></i></a> <div class="modal" id="modal-template"> <div class="modal-dialog"> <div class="modal-content"> <div class="row m-0 mt-1"> <div class="col-md-12"> <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button> </div> </div> <div class="modal-body"></div> </div> </div> </div> <script src="https://cdn.waset.org/static/plugins/jquery-3.3.1.min.js"></script> <script src="https://cdn.waset.org/static/plugins/bootstrap-4.2.1/js/bootstrap.bundle.min.js"></script> <script src="https://cdn.waset.org/static/js/site.js?v=150220211556"></script> <script> jQuery(document).ready(function() { /*jQuery.get("https://publications.waset.org/xhr/user-menu", function (response) { jQuery('#mainNavMenu').append(response); });*/ jQuery.get({ url: "https://publications.waset.org/xhr/user-menu", cache: false }).then(function(response){ jQuery('#mainNavMenu').append(response); }); }); </script> </body> </html>