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 engineering</title> <meta name="description" content="Search results for: software engineering"> <meta name="keywords" content="software engineering"> <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 engineering" 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 engineering"> <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> 7447</div> </div> </div> </div> <h1 class="mt-3 mb-3 text-center" style="font-size:1.6rem;">Search results for: software engineering</h1> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">7447</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">7446</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">558</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">7445</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">7444</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">7443</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">7442</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">548</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">7441</span> FreGsd: A Framework for Golbal Software Requirement Engineering</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Alsahli%20Abdulaziz%20Abdullah">Alsahli Abdulaziz Abdullah</a>, <a href="https://publications.waset.org/abstracts/search?q=Hameed%20Ullah%20Khan"> Hameed Ullah Khan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software development nowadays is more and more using global ways of development instead of normal development enviroment where development occur in one location. This paper is a aimed to propose a Requirement Engineering framework to support Global Software Development environment with regards to all requirment engineering activities from elicitation to fially magning requirment change. Global software enviroment is more and more gaining better reputation in software developmet with better quality is resulting from developing in this eviroment yet with lower cost.However, failure rate developing in this enviroment is high due to inapproprate requirment development and managment.This paper will add to the software engineering development envrioments discipline and many developers in GSD will benefit from it. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=global%20software%20development%20environment" title="global software development environment">global software development environment</a>, <a href="https://publications.waset.org/abstracts/search?q=GSD" title=" GSD"> GSD</a>, <a href="https://publications.waset.org/abstracts/search?q=requirement%20engineering" title=" requirement engineering"> requirement engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=FreGsd" title=" FreGsd"> FreGsd</a>, <a href="https://publications.waset.org/abstracts/search?q=computer%20engineering" title=" computer engineering"> computer engineering</a> </p> <a href="https://publications.waset.org/abstracts/18467/fregsd-a-framework-for-golbal-software-requirement-engineering" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/18467.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">7440</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">7439</span> A Software Product Engineering Process for Commercial Success in Start-Up and Cases</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Javed%20Ahsan">Javed Ahsan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software engineers strive for technical sophistication with a dream of finding commercial success in their start-up business. But they may find their much technically sophisticated software products failing in industry in competition with lesser sophisticated products. This is because of not maintaining a clear focus on complimenting and leading commercial success through technical sophistication. This can be achieved through a software engineering specific product development process suggested in this paper. This process is about evolving a software product through specific phases and iterations until commercial triumph falls on software engineer’s feet. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software" title="software">software</a>, <a href="https://publications.waset.org/abstracts/search?q=product" title=" product"> product</a>, <a href="https://publications.waset.org/abstracts/search?q=engineering" title=" engineering"> engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=commercialization" title=" commercialization"> commercialization</a>, <a href="https://publications.waset.org/abstracts/search?q=start-up" title=" start-up"> start-up</a>, <a href="https://publications.waset.org/abstracts/search?q=competitiveness" title=" competitiveness"> competitiveness</a>, <a href="https://publications.waset.org/abstracts/search?q=industry" title=" industry"> industry</a> </p> <a href="https://publications.waset.org/abstracts/60147/a-software-product-engineering-process-for-commercial-success-in-start-up-and-cases" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/60147.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">356</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">7438</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">7437</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">7436</span> D6tions: A Serious Game to Learn Software Engineering Process and Design</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Hector%20G.%20Perez-Gonzalez">Hector G. Perez-Gonzalez</a>, <a href="https://publications.waset.org/abstracts/search?q=Miriam%20Vazquez-Escalante"> Miriam Vazquez-Escalante</a>, <a href="https://publications.waset.org/abstracts/search?q=Sandra%20E.%20Nava-Mu%C3%B1oz"> Sandra E. Nava-Muñoz</a>, <a href="https://publications.waset.org/abstracts/search?q=%E2%80%A8%20Francisco%20E.%20Martinez-Perez">  Francisco E. Martinez-Perez</a>, <a href="https://publications.waset.org/abstracts/search?q=Alberto%20S.%20Nunez-Varela"> Alberto S. Nunez-Varela</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The software engineering teaching process has been the subject of many studies. To improve this process, researchers have proposed merely illustrative techniques in the classroom, such as topic presentations and dynamics between students on one side or attempts to involve students in real projects with companies and institutions to bring them to a real software development problem on the other hand. Simulators and serious games have been used as auxiliary tools to introduce students to topics that are too abstract when these are presented in the traditional way. Most of these tools cover a limited area of the huge software engineering scope. To address this problem, we have developed D6tions, an educational serious game that simulates the software engineering process and is designed to experiment the different stages a software engineer (playing roles as project leader or as a developer or designer) goes through, while participating in a software project. We describe previous approaches to this problem, how D6tions was designed, its rules, directions, and the results we obtained of the use of this game involving undergraduate students playing the game. <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=software%20engineering" title=" software engineering"> software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering%20education" title=" software engineering education"> software engineering education</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering%20teaching%20process" title=" software engineering teaching process"> software engineering teaching process</a> </p> <a href="https://publications.waset.org/abstracts/37912/d6tions-a-serious-game-to-learn-software-engineering-process-and-design" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/37912.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">493</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">7435</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">7434</span> Strategies to Improve Learning and Teaching of Software Packages Among Undergraduate Students</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sara%20Moridpour">Sara Moridpour</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Engineering students need to learn different software packages to meet the emerging industry needs. Face-to-face lectures provide an interactive environment for learning software packages. However, COVID changed expectations of face-to-face learning and teaching. It is essential to enhance the interaction among students and teachers in online and virtual learning and teaching of software packages. The proposed study introduces strategies for teaching engineering software packages in online and hybrid environments and evaluates students’ skills by an authentic assignment. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=teaching%20software%20packages" title="teaching software packages">teaching software packages</a>, <a href="https://publications.waset.org/abstracts/search?q=authentic%20assessment." title=" authentic assessment."> authentic assessment.</a>, <a href="https://publications.waset.org/abstracts/search?q=engineering" title=" engineering"> engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=undergraduate%20students" title=" undergraduate students"> undergraduate students</a> </p> <a href="https://publications.waset.org/abstracts/148220/strategies-to-improve-learning-and-teaching-of-software-packages-among-undergraduate-students" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/148220.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">139</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">7433</span> An Orphan Software Engineering Course: Supportive Ways toward a True Software Engineer</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Haya%20Sammana">Haya Sammana</a> </p> <p class="card-text"><strong>Abstract:</strong></p> A well-defined curricula must be adopted to meet the increasing complexity and diversity in the software applications. In reality, some IT majors such as computer science and computer engineering receive the software engineering education in a single course which is considered as a big challenged for the instructors and universities. Also, it requires students to gain the most of practical experiences that simulate the real work in software companies. Furthermore, we have noticed that there is no consensus on how, when and what to teach in that introductory course to gain the practical experiences that are required by the software companies. Because all of software engineering disciplines will not fit in just one course, so the course needs reasonable choices in selecting its topics. This arises an important question which is an essential one to ask: Is this course has the ability to formulate a true software engineer that meets the needs of industry? This question arises a big challenge in selecting the appropriate topics. So answering this question is very important for the next undergraduate students. During teaching this course in the curricula, the feedbacks from an undergraduate students and the keynotes of the annual meeting for an advisory committee from industrial side provide a probable answer for the proposed question: it is impossible to build a true software engineer who possesses all the essential elements of software engineering education such teamwork, communications skills, project management skills and contemporary industrial practice from one course and it is impossible to have a one course covering all software engineering topics. Besides the used teaching approach, the author proposes an implemented three supportive ways aiming for mitigating the expected risks and increasing the opportunity to build a true software engineer. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20engineering%20course" title="software engineering course">software engineering course</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20engineering%20education" title=" software engineering education"> software engineering education</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20experience" title=" software experience"> software experience</a>, <a href="https://publications.waset.org/abstracts/search?q=supportive%20approach" title=" supportive approach"> supportive approach</a> </p> <a href="https://publications.waset.org/abstracts/36629/an-orphan-software-engineering-course-supportive-ways-toward-a-true-software-engineer" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/36629.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">7432</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">432</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">7431</span> Assessing the Current State of Software Engineering and Information Technology in Ghana</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=David%20Yartel">David Yartel</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Drawing on the current state of software engineering and information technology in Ghana, the study documents its significant contribution to the development of Ghanaian industries. The study focuses on the application of modern trends in technology and the barriers faced in the area of software engineering and information technology. A thorough analysis of a dozen of interviews with stakeholders in software engineering and information technology via interviews reveals how modern trends in software engineering pose challenges to the industry in Ghana. Results show that to meet the expectation of modern software engineering and information technology trends, stakeholders must have skilled professionals, adequate infrastructure, and enhanced support for technology startups. Again, individuals should be encouraged to pursue a career in software engineering and information technology, as it has the propensity to increase the efficiency and effectiveness of work-related activities. This study recommends that stakeholders in software engineering and technology industries should invest enough in training more professionals by collaborating with international institutions well-versed in the area by organizing frequent training and seminars. The government should also provide funding opportunities for small businesses in the technology sector to drive creativity and development in order to bring about growth and development. <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=information%20technology" title=" information technology"> information technology</a>, <a href="https://publications.waset.org/abstracts/search?q=Ghana" title=" Ghana"> Ghana</a>, <a href="https://publications.waset.org/abstracts/search?q=development" title=" development"> development</a> </p> <a href="https://publications.waset.org/abstracts/164921/assessing-the-current-state-of-software-engineering-and-information-technology-in-ghana" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/164921.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">94</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">7430</span> Requirement Engineering Within Open Source Software Development: A Case Study</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Kars%20Beek">Kars Beek</a>, <a href="https://publications.waset.org/abstracts/search?q=Remco%20Groeneveld"> Remco Groeneveld</a>, <a href="https://publications.waset.org/abstracts/search?q=Sjaak%20Brinkkemper"> Sjaak Brinkkemper</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Although there is much literature available on requirement documentation in traditional software development, few studies have been conducted about this topic in open source software development. While open-source software development is becoming more important, the software development processes are often not as structured as corporate software development processes. Papers show that communities, creating open-source software, often lack structure and documentation. However, most recent studies about this topic are often ten or more years old. Therefore, this research has been conducted to determine if the lack of structure and documentation in requirement engineering is currently still the situation in these communities. Three open-source products have been chosen as subjects for conducting this research. The data for this research was gathered based on interviews, observations, and analyses of feature proposals and issue tracking tools. In this paper, we present a comparison and an analysis of the different methods used for requirements documentation to understand the current practices of requirements documentation in open source software development. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=case%20study" title="case study">case study</a>, <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=open%20source%20software%20development" title=" open source software development"> open source software development</a>, <a href="https://publications.waset.org/abstracts/search?q=requirement%20elicitation" title=" requirement elicitation"> requirement elicitation</a>, <a href="https://publications.waset.org/abstracts/search?q=requirement%20engineering" title=" requirement engineering"> requirement engineering</a> </p> <a href="https://publications.waset.org/abstracts/143917/requirement-engineering-within-open-source-software-development-a-case-study" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/143917.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">103</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">7429</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">7428</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">7427</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">7426</span> Inadequate Requirements Engineering Process: A Key Factor for Poor Software Development in Developing Nations: A Case Study</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=K.%20Adu%20Michael">K. Adu Michael</a>, <a href="https://publications.waset.org/abstracts/search?q=K.%20Alese%20Boniface"> K. Alese Boniface</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Developing a reliable and sustainable software products is today a big challenge among up–coming software developers in Nigeria. The inability to develop a comprehensive problem statement needed to execute proper requirements engineering process is missing. The need to describe the ‘what’ of a system in one document, written in a natural language is a major step in the overall process of Software Engineering. Requirements Engineering is a process use to discover, analyze and validate system requirements. This process is needed in reducing software errors at the early stage of the development of software. The importance of each of the steps in Requirements Engineering is clearly explained in the context of using detailed problem statement from client/customer to get an overview of an existing system along with expectations from the new system. This paper elicits inadequate Requirements Engineering principle as the major cause of poor software development in developing nations using a case study of final year computer science students of a tertiary-education institution in Nigeria. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=client%2Fcustomer" title="client/customer">client/customer</a>, <a href="https://publications.waset.org/abstracts/search?q=problem%20statement" title=" problem statement"> problem statement</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements%20engineering" title=" requirements engineering"> requirements engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20developers" title=" software developers"> software developers</a> </p> <a href="https://publications.waset.org/abstracts/12777/inadequate-requirements-engineering-process-a-key-factor-for-poor-software-development-in-developing-nations-a-case-study" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/12777.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">405</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">7425</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">7424</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">7423</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">7422</span> A Case Study on Evaluating and Selecting Soil /Pipeline Interaction Analysis Software for the Oil and Gas Industry</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Abdinasir%20Mohamed">Abdinasir Mohamed</a>, <a href="https://publications.waset.org/abstracts/search?q=Ashraf%20El-Hamalawi"> Ashraf El-Hamalawi</a>, <a href="https://publications.waset.org/abstracts/search?q=Steven%20Yeomans"> Steven Yeomans</a>, <a href="https://publications.waset.org/abstracts/search?q=Matthew%20Frost"> Matthew Frost</a>, <a href="https://publications.waset.org/abstracts/search?q=Andy%20Connell"> Andy Connell</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The evaluation and selection of appropriate software solutions to meet with an organisation’s inherent business requirements can be a problematic software engineering process that if done incorrectly can have a significant, costly and adverse effect on the business and its processes. The aim of this paper is to show the process and evaluation criteria followed to select the right engineering solution for the identified business requirement. The research adopted an action research method within an organisation in the oil and gas industry, which required a solution suitable for conducting stress analysis for soil-pipeline interaction analysis (SPIA). Through the use of the presented software selection and evaluation approach, to capture and measure key requirements, it was possible to determine a suitable software for the organisation. This paper investigates methodologies for selecting software packages, software evaluation techniques, and software evaluation criteria in evaluating software packages before providing an explanation of the developed methodology adopted. The key findings of the study are: (1) that there is a need to create a framework for software selection methodologies, (2) there are no universal selection criteria in the engineering industry, and (3) there is a need to validate the findings by creating an application based on the evaluation technique and evaluation criteria for selecting software packages for the engineering industry. The findings of the study are offered to support organisations in the oil and gas sector improve software selection methodologies for SPIA. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20evaluation" title="software evaluation">software evaluation</a>, <a href="https://publications.waset.org/abstracts/search?q=end%20user%20programs" title=" end user programs"> end user programs</a>, <a href="https://publications.waset.org/abstracts/search?q=soil%20pipeline%20analysis" title=" soil pipeline analysis"> soil pipeline analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20selection" title=" software selection"> software selection</a> </p> <a href="https://publications.waset.org/abstracts/81797/a-case-study-on-evaluating-and-selecting-soil-pipeline-interaction-analysis-software-for-the-oil-and-gas-industry" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/81797.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">192</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">7421</span> Improving Learning and Teaching of Software Packages among Engineering Students</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sara%20Moridpour">Sara Moridpour</a> </p> <p class="card-text"><strong>Abstract:</strong></p> To meet emerging industry needs, engineering students must learn different software packages and enhance their computational skills. Traditionally, face-to-face is selected as the preferred approach to teaching software packages. Face-to-face tutorials and workshops provide an interactive environment for learning software packages where the students can communicate with the teacher and interact with other students, evaluate their skills, and receive feedback. However, COVID-19 significantly limited face-to-face learning and teaching activities at universities. Worldwide lockdowns and the shift to online and remote learning and teaching provided the opportunity to introduce different strategies to enhance the interaction among students and teachers in online and virtual environments and improve the learning and teaching of software packages in online and blended teaching methods. This paper introduces a blended strategy to teach engineering software packages to undergraduate students. This article evaluates the effectiveness of the proposed blended learning and teaching strategy in students’ learning by comparing the impact of face-to-face, online and the proposed blended environments on students’ software skills. The paper evaluates the students’ software skills and their software learning through an authentic assignment. According to the results, the proposed blended teaching strategy successfully improves the software learning experience among undergraduate engineering students. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=teaching%20software%20packages" title="teaching software packages">teaching software packages</a>, <a href="https://publications.waset.org/abstracts/search?q=undergraduate%20students" title=" undergraduate students"> undergraduate students</a>, <a href="https://publications.waset.org/abstracts/search?q=blended%20learning%20and%20teaching" title=" blended learning and teaching"> blended learning and teaching</a>, <a href="https://publications.waset.org/abstracts/search?q=authentic%20assessment" title=" authentic assessment"> authentic assessment</a> </p> <a href="https://publications.waset.org/abstracts/160407/improving-learning-and-teaching-of-software-packages-among-engineering-students" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/160407.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">7420</span> Requirement Engineering and Software Product Line Scoping Paradigm</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ahmed%20Mateen">Ahmed Mateen</a>, <a href="https://publications.waset.org/abstracts/search?q=Zhu%20Qingsheng"> Zhu Qingsheng</a>, <a href="https://publications.waset.org/abstracts/search?q=Faisal%20Shahzad"> Faisal Shahzad</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirement Engineering (RE) is a part being created for programming structure during the software development lifecycle. Software product line development is a new topic area within the domain of software engineering. It also plays important role in decision making and it is ultimately helpful in rising business environment for productive programming headway. Decisions are central to engineering processes and they hold them together. It is argued that better decisions will lead to better engineering. To achieve better decisions requires that they are understood in detail. In order to address the issues, companies are moving towards Software Product Line Engineering (SPLE) which helps in providing large varieties of products with minimum development effort and cost. This paper proposed a new framework for software product line and compared with other models. The results can help to understand the needs in SPL testing, by identifying points that still require additional investigation. In our future scenario, we will combine this model in a controlled environment with industrial SPL projects which will be the new horizon for SPL process management testing strategies. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=requirements%20engineering" title="requirements engineering">requirements engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20product%20lines" title=" software product lines"> software product lines</a>, <a href="https://publications.waset.org/abstracts/search?q=scoping" title=" scoping"> scoping</a>, <a href="https://publications.waset.org/abstracts/search?q=process%20structure" title=" process structure"> process structure</a>, <a href="https://publications.waset.org/abstracts/search?q=domain%20specific%20language" title=" domain specific language"> domain specific language</a> </p> <a href="https://publications.waset.org/abstracts/87393/requirement-engineering-and-software-product-line-scoping-paradigm" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/87393.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">224</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">7419</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">7418</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> <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%20engineering&page=2">2</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=3">3</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=4">4</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=5">5</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=6">6</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=7">7</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=8">8</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=9">9</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&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%20engineering&page=248">248</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&page=249">249</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20engineering&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>