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 requirement engineering</title> <meta name="description" content="Search results for: software requirement engineering"> <meta name="keywords" content="software requirement 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 requirement 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 requirement 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> 8344</div> </div> </div> </div> <h1 class="mt-3 mb-3 text-center" style="font-size:1.6rem;">Search results for: software requirement engineering</h1> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">8344</span> Adaptation of Requirement Engineering Practices in Pakistan</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Waqas%20Ali">Waqas Ali</a>, <a href="https://publications.waset.org/abstracts/search?q=Nadeem%20Majeed"> Nadeem Majeed</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirement engineering is an essence of software development life cycle. The more time we spend on requirement engineering, higher the probability of success. Effective requirement engineering ensures and predicts successful software product. This paper presents the adaptation of requirement engineering practices in small and medium size companies of Pakistan. The study is conducted by questionnaires to show how much of requirement engineering models and practices are followed in Pakistan. <p class="card-text"><strong>Keywords:</strong> <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=Pakistan" title=" Pakistan"> Pakistan</a>, <a href="https://publications.waset.org/abstracts/search?q=models" title=" models"> models</a>, <a href="https://publications.waset.org/abstracts/search?q=practices" title=" practices"> practices</a>, <a href="https://publications.waset.org/abstracts/search?q=organizations" title=" organizations"> organizations</a> </p> <a href="https://publications.waset.org/abstracts/1641/adaptation-of-requirement-engineering-practices-in-pakistan" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/1641.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">719</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">8343</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">104</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">8342</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">8341</span> Requirement Analysis for Emergency Management Software</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Tom%C3%A1%C5%A1%20Lud%C3%ADk">Tomáš Ludík</a>, <a href="https://publications.waset.org/abstracts/search?q=Ji%C5%99%C3%AD%20Barta"> Jiří Barta</a>, <a href="https://publications.waset.org/abstracts/search?q=Sabina%20Chytilov%C3%A1"> Sabina Chytilová</a>, <a href="https://publications.waset.org/abstracts/search?q=Josef%20Navr%C3%A1til"> Josef Navrátil</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Emergency management is a discipline of dealing with and avoiding risks. Appropriate emergency management software allows better management of these risks and has a direct influence on reducing potential negative impacts. Although there are several emergency management software products in the Czech Republic, they cover user requirements from the emergency management field only partially. Therefore, the paper focuses on the issues of requirement analysis within development of emergency management software. Analysis of the current state describes the basic features and properties of user requirements for software development as well as basic methods and approaches for gathering these requirements. Then, the paper presents more specific mechanisms for requirement analysis based on chosen software development approach: structured, object-oriented or agile. Based on these experiences it is designed new methodology for requirement analysis. Methodology describes how to map user requirements comprehensively in the field of emergency management and thus reduce misunderstanding between software analyst and emergency manager. Proposed methodology was consulted with department of fire brigade and also has been applied in the requirements analysis for their current emergency management software. The proposed methodology has general character and can be used also in other specific areas during requirement analysis. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=emergency%20software" title="emergency software">emergency software</a>, <a href="https://publications.waset.org/abstracts/search?q=methodology" title=" methodology"> methodology</a>, <a href="https://publications.waset.org/abstracts/search?q=requirement%20analysis" title=" requirement analysis"> requirement analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=stakeholders" title=" stakeholders"> stakeholders</a>, <a href="https://publications.waset.org/abstracts/search?q=use%20case%20diagram" title=" use case diagram"> use case diagram</a>, <a href="https://publications.waset.org/abstracts/search?q=user%20stories" title=" user stories"> user stories</a> </p> <a href="https://publications.waset.org/abstracts/15704/requirement-analysis-for-emergency-management-software" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/15704.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">540</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">8340</span> Critical Success Factors Quality Requirement Change Management</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Jamshed%20Ahmad">Jamshed Ahmad</a>, <a href="https://publications.waset.org/abstracts/search?q=Abdul%20Wahid%20Khan"> Abdul Wahid Khan</a>, <a href="https://publications.waset.org/abstracts/search?q=Javed%20Ali%20Khan"> Javed Ali Khan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Managing software quality requirements change management is a difficult task in the field of software engineering. Avoiding incoming changes result in user dissatisfaction while accommodating to many requirement changes may delay product delivery. Poor requirements management is solely considered the primary cause of the software failure. It becomes more challenging in global software outsourcing. Addressing success factors in quality requirement change management is desired today due to the frequent change requests from the end-users. In this research study, success factors are recognized and scrutinized with the help of a systematic literature review (SLR). In total, 16 success factors were identified, which significantly impacted software quality requirement change management. The findings show that Proper Requirement Change Management, Rapid Delivery, Quality Software Product, Access to Market, Project Management, Skills and Methodologies, Low Cost/Effort Estimation, Clear Plan and Road Map, Agile Processes, Low Labor Cost, User Satisfaction, Communication/Close Coordination, Proper Scheduling and Time Constraints, Frequent Technological Changes, Robust Model, Geographical distribution/Cultural differences are the key factors that influence software quality requirement change. The recognized success factors and validated with the help of various research methods, i.e., case studies, interviews, surveys and experiments. These factors are then scrutinized in continents, database, company size and period of time. Based on these findings, requirement change will be implemented in a better way. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=global%20software%20development" title="global software development">global software development</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=systematic%20literature%20review" title=" systematic literature review"> systematic literature review</a>, <a href="https://publications.waset.org/abstracts/search?q=success%20factors" title=" success factors"> success factors</a> </p> <a href="https://publications.waset.org/abstracts/132539/critical-success-factors-quality-requirement-change-management" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/132539.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">197</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">8339</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">225</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">8338</span> Object Oriented Software Engineering Approach to Industrial Information System Design and Implementation</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Issa%20Hussein%20Manita">Issa Hussein Manita </a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper presents an example of industrial information system design and implementation (IIDC), the most common software engineering design steps that are applied to the different design stages. We are going through the life cycle of software system development. We start by a study of system requirement and end with testing and delivering system, going by system design and coding, program integration and system integration step. The most modern software design tools available used in the design this includes, but not limited to, Unified Modeling Language (UML), system modeling, SQL server side application, uses case analysis, design and testing as applied to information processing systems. The system is designed to perform tasks specified by the client with real data. By the end of the implementation of the system, default or user defined acceptance policy to provide an overall score as an indication of the system performance is used. To test the reliability of he designed system, it is tested in different environment and different work burden such as multi-user environment. <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=design" title=" design"> design</a>, <a href="https://publications.waset.org/abstracts/search?q=system%20requirement" title=" system requirement"> system requirement</a>, <a href="https://publications.waset.org/abstracts/search?q=integration" title=" integration"> integration</a>, <a href="https://publications.waset.org/abstracts/search?q=unified%20modeling%20language" title=" unified modeling language"> unified modeling language</a> </p> <a href="https://publications.waset.org/abstracts/17603/object-oriented-software-engineering-approach-to-industrial-information-system-design-and-implementation" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/17603.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">570</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">8337</span> State of Art in Software Requirement Negotiation Process Models</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Shamsu%20Abdullahi">Shamsu Abdullahi</a>, <a href="https://publications.waset.org/abstracts/search?q=Nazir%20Yusuf"> Nazir Yusuf</a>, <a href="https://publications.waset.org/abstracts/search?q=Hazrina%20Sofian"> Hazrina Sofian</a>, <a href="https://publications.waset.org/abstracts/search?q=Abubakar%20Zakari"> Abubakar Zakari</a>, <a href="https://publications.waset.org/abstracts/search?q=Amina%20Nura"> Amina Nura</a>, <a href="https://publications.waset.org/abstracts/search?q=Salisu%20Suleiman"> Salisu Suleiman</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirements negotiation process models help in resolving conflicting requirements of the heterogeneous stakeholders in the software development industry. This is to achieve a shared vision of software projects to be developed by the industry. Negotiating stakeholder agreements is a serious and difficult task in the software development process. There are many requirements negotiation process models that effectively negotiate stakeholder agreements that have been proposed by the research community. Other issues in the requirements negotiation research domain include stakeholder communication, decision-making, lack of negotiation interoperability, and managing requirement changes and analysis. This study highlights the current state of the art in the existing software requirements negotiation process models. The study also describes the issues and limitations in the software requirements negotiations process models. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=requirements" title="requirements">requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=negotiation" title=" negotiation"> negotiation</a>, <a href="https://publications.waset.org/abstracts/search?q=stakeholders" title=" stakeholders"> stakeholders</a>, <a href="https://publications.waset.org/abstracts/search?q=agreements" title=" agreements"> agreements</a> </p> <a href="https://publications.waset.org/abstracts/161397/state-of-art-in-software-requirement-negotiation-process-models" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/161397.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">197</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">8336</span> An Approach to Specify Software Requirements in Semantic Form</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Deepa%20Vijay">Deepa Vijay</a>, <a href="https://publications.waset.org/abstracts/search?q=Chellammal%20Surianarayanan"> Chellammal Surianarayanan</a>, <a href="https://publications.waset.org/abstracts/search?q=Gopinath%20Ganapathy"> Gopinath Ganapathy</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirements of a software project serve as a guideline for the entire project team which enable the team towards producing the right outcome. As requirements are the key in deciding the success of the project, it should be specified in an unambiguous manner. Also, the requirements should be complete and consistent. It should be interpreted in the same way by the entire software project team as the customer interprets. Specifying requirements in textual manner is common in software development. This leads to poor understanding of the requirements which results in more errors and degraded quality. There are some literatures which focus on semantic way of specifying functional requirement which ensure the consistency and completeness of requirements. Alternately in the work, a method is proposed to map the syntactic requirements with corresponding semantics in the form of ontologies. This improves the understanding of requirements, prevents errors and improves quality. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=functional%20requirement" title="functional requirement">functional requirement</a>, <a href="https://publications.waset.org/abstracts/search?q=ontology" title=" ontology"> ontology</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements%20management" title=" requirements management"> requirements management</a>, <a href="https://publications.waset.org/abstracts/search?q=semantics" title=" semantics"> semantics</a> </p> <a href="https://publications.waset.org/abstracts/35649/an-approach-to-specify-software-requirements-in-semantic-form" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/35649.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">364</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">8335</span> Elicitation Methods of Requirements Gathering in Shopping Mobile Application Development</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Xiao%20Yihong">Xiao Yihong</a>, <a href="https://publications.waset.org/abstracts/search?q=Li%20Zhixuan"> Li Zhixuan</a>, <a href="https://publications.waset.org/abstracts/search?q=Wong%20Kah%20Seng"> Wong Kah Seng</a>, <a href="https://publications.waset.org/abstracts/search?q=Shen%20Xingcang"> Shen Xingcang</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirement Elicitation is one of the important factors in developing any new application. Most systems fail just because of wrong elicitation practice. As a result, developers always choose different methods in different fields to achieve optimal results. This paper analyses four cases to understand the effectiveness of different requirement elicitation methods in the field of mobile shopping applications. The elicitation methods we studied included interviews, questionnaires, prototypes, analysis of existing systems, focus groups, brainstorming, and so on. Through the research and analysis results, we ensured the need for a mixture of elicitation methods. Meanwhile, the method adopted should be determined according to the scale of the project and be operated in a reasonable order to ensure the high efficiency of requirement elicitation. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=requirements%20elicitation%20method" title="requirements elicitation method">requirements elicitation method</a>, <a href="https://publications.waset.org/abstracts/search?q=shopping" title=" shopping"> shopping</a>, <a href="https://publications.waset.org/abstracts/search?q=mobile%20application" title=" mobile application"> mobile application</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering" title=" software requirement engineering"> software requirement engineering</a> </p> <a href="https://publications.waset.org/abstracts/155627/elicitation-methods-of-requirements-gathering-in-shopping-mobile-application-development" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/155627.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">124</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">8334</span> Impact Analysis Based on Change Requirement Traceability in Object Oriented Software Systems</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Sunil%20Tumkur%20Dakshinamurthy">Sunil Tumkur Dakshinamurthy</a>, <a href="https://publications.waset.org/abstracts/search?q=Mamootil%20Zachariah%20Kurian"> Mamootil Zachariah Kurian</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Change requirement traceability in object oriented software systems is one of the challenging areas in research. We know that the traces between links of different artifacts are to be automated or semi-automated in the software development life cycle (SDLC). The aim of this paper is discussing and implementing aspects of dynamically linking the artifacts such as requirements, high level design, code and test cases through the Extensible Markup Language (XML) or by dynamically generating Object Oriented (OO) metrics. Also, non-functional requirements (NFR) aspects such as stability, completeness, clarity, validity, feasibility and precision are discussed. We discuss this as a Fifth Taxonomy, which is a system vulnerability concern. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=artifacts" title="artifacts">artifacts</a>, <a href="https://publications.waset.org/abstracts/search?q=NFRs" title=" NFRs"> NFRs</a>, <a href="https://publications.waset.org/abstracts/search?q=OO%20metrics" title=" OO metrics"> OO metrics</a>, <a href="https://publications.waset.org/abstracts/search?q=SDLC" title=" SDLC"> SDLC</a>, <a href="https://publications.waset.org/abstracts/search?q=XML" title=" XML"> XML</a> </p> <a href="https://publications.waset.org/abstracts/58275/impact-analysis-based-on-change-requirement-traceability-in-object-oriented-software-systems" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/58275.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">342</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">8333</span> Knowledge Audit Model for Requirement Elicitation Process</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Laleh%20Taheri">Laleh Taheri</a>, <a href="https://publications.waset.org/abstracts/search?q=Noraini%20C.%20Pa"> Noraini C. Pa</a>, <a href="https://publications.waset.org/abstracts/search?q=Rusli%20Abdullah"> Rusli Abdullah</a>, <a href="https://publications.waset.org/abstracts/search?q=Salfarina%20Abdullah"> Salfarina Abdullah</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Knowledge plays an important role to the success of any organization. Software development organizations are highly knowledge-intensive organizations especially in their Requirement Elicitation Process (REP). There are several problems regarding communicating and using the knowledge in REP such as misunderstanding, being out of scope, conflicting information and changes of requirements. All of these problems occurred in transmitting the requirements knowledge during REP. Several researches have been done in REP in order to solve the problem towards requirements. Knowledge Audit (KA) approaches were proposed in order to solve managing knowledge in human resources, financial, and manufacturing. There is lack of study applying the KA in requirements elicitation process. Therefore, this paper proposes a KA model for REP in supporting to acquire good requirements. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=knowledge%20audit" title="knowledge audit">knowledge audit</a>, <a href="https://publications.waset.org/abstracts/search?q=requirement%20elicitation%20process" title=" requirement elicitation process"> requirement elicitation process</a>, <a href="https://publications.waset.org/abstracts/search?q=KA%20model" title=" KA model"> KA model</a>, <a href="https://publications.waset.org/abstracts/search?q=knowledge%20in%20requirement%20elicitation" title=" knowledge in requirement elicitation"> knowledge in requirement elicitation</a> </p> <a href="https://publications.waset.org/abstracts/4339/knowledge-audit-model-for-requirement-elicitation-process" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/4339.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">345</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">8332</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">8331</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">8330</span> CMMI Key Process Areas and FDD Practices</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Rituraj%20Deka">Rituraj Deka</a>, <a href="https://publications.waset.org/abstracts/search?q=Nomi%20Baruah"> Nomi Baruah</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The development of information technology during the past few years resulted in designing of more and more complex software. The outsourcing of software development makes a higher requirement for the management of software development project. Various software enterprises follow various paths in their pursuit of excellence, applying various principles, methods and techniques along the way. The new research is proving that CMMI and Agile methodologies can benefit from using both methods within organizations with the potential to dramatically improve business performance. The paper describes a mapping between CMMI key process areas (KPAs) and Feature-Driven Development (FDD) communication perspective, so as to increase the understanding of how improvements can be made in the software development process. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=Agile" title="Agile">Agile</a>, <a href="https://publications.waset.org/abstracts/search?q=CMMI" title=" CMMI"> CMMI</a>, <a href="https://publications.waset.org/abstracts/search?q=FDD" title=" FDD"> FDD</a>, <a href="https://publications.waset.org/abstracts/search?q=KPAs" title=" KPAs "> KPAs </a> </p> <a href="https://publications.waset.org/abstracts/17130/cmmi-key-process-areas-and-fdd-practices" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/17130.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">458</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">8329</span> Requirement Engineering for Intrusion Detection Systems in Wireless Sensor Networks</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Afnan%20Al-Romi">Afnan Al-Romi</a>, <a href="https://publications.waset.org/abstracts/search?q=Iman%20Al-Momani"> Iman Al-Momani</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The urge of applying the Software Engineering (SE) processes is both of vital importance and a key feature in critical, complex large-scale systems, for example, safety systems, security service systems, and network systems. Inevitably, associated with this are risks, such as system vulnerabilities and security threats. The probability of those risks increases in unsecured environments, such as wireless networks in general and in Wireless Sensor Networks (WSNs) in particular. WSN is a self-organizing network of sensor nodes connected by wireless links. WSNs consist of hundreds to thousands of low-power, low-cost, multi-function sensor nodes that are small in size and communicate over short-ranges. The distribution of sensor nodes in an open environment that could be unattended in addition to the resource constraints in terms of processing, storage and power, make such networks in stringent limitations such as lifetime (i.e. period of operation) and security. The importance of WSN applications that could be found in many militaries and civilian aspects has drawn the attention of many researchers to consider its security. To address this important issue and overcome one of the main challenges of WSNs, security solution systems have been developed by researchers. Those solutions are software-based network Intrusion Detection Systems (IDSs). However, it has been witnessed, that those developed IDSs are neither secure enough nor accurate to detect all malicious behaviours of attacks. Thus, the problem is the lack of coverage of all malicious behaviours in proposed IDSs, leading to unpleasant results, such as delays in the detection process, low detection accuracy, or even worse, leading to detection failure, as illustrated in the previous studies. Also, another problem is energy consumption in WSNs caused by IDS. So, in other words, not all requirements are implemented then traced. Moreover, neither all requirements are identified nor satisfied, as for some requirements have been compromised. The drawbacks in the current IDS are due to not following structured software development processes by researches and developers when developing IDS. Consequently, they resulted in inadequate requirement management, process, validation, and verification of requirements quality. Unfortunately, WSN and SE research communities have been mostly impermeable to each other. Integrating SE and WSNs is a real subject that will be expanded as technology evolves and spreads in industrial applications. Therefore, this paper will study the importance of Requirement Engineering when developing IDSs. Also, it will study a set of existed IDSs and illustrate the absence of Requirement Engineering and its effect. Then conclusions are drawn in regard of applying requirement engineering to systems to deliver the required functionalities, with respect to operational constraints, within an acceptable level of performance, accuracy and reliability. <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=requirement%20engineering" title=" requirement engineering"> requirement engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=Intrusion%20Detection%20System" title=" Intrusion Detection System"> Intrusion Detection System</a>, <a href="https://publications.waset.org/abstracts/search?q=IDS" title=" IDS"> IDS</a>, <a href="https://publications.waset.org/abstracts/search?q=Wireless%20Sensor%20Networks" title=" Wireless Sensor Networks"> Wireless Sensor Networks</a>, <a href="https://publications.waset.org/abstracts/search?q=WSN" title=" WSN"> WSN</a> </p> <a href="https://publications.waset.org/abstracts/29665/requirement-engineering-for-intrusion-detection-systems-in-wireless-sensor-networks" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/29665.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">322</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">8328</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">8327</span> Component Based Testing Using Clustering and Support Vector Machine </h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Iqbaldeep%20Kaur">Iqbaldeep Kaur</a>, <a href="https://publications.waset.org/abstracts/search?q=Amarjeet%20Kaur"> Amarjeet Kaur</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Software Reusability is important part of software development. So component based software development in case of software testing has gained a lot of practical importance in the field of software engineering from academic researcher and also from software development industry perspective. Finding test cases for efficient reuse of test cases is one of the important problems aimed by researcher. Clustering reduce the search space, reuse test cases by grouping similar entities according to requirements ensuring reduced time complexity as it reduce the search time for retrieval the test cases. In this research paper we proposed approach for re-usability of test cases by unsupervised approach. In unsupervised learning we proposed k-mean and Support Vector Machine. We have designed the algorithm for requirement and test case document clustering according to its tf-idf vector space and the output is set of highly cohesive pattern groups. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=software%20testing" title="software testing">software testing</a>, <a href="https://publications.waset.org/abstracts/search?q=reusability" title=" reusability"> reusability</a>, <a href="https://publications.waset.org/abstracts/search?q=clustering" title=" clustering"> clustering</a>, <a href="https://publications.waset.org/abstracts/search?q=k-mean" title=" k-mean"> k-mean</a>, <a href="https://publications.waset.org/abstracts/search?q=SVM" title=" SVM "> SVM </a> </p> <a href="https://publications.waset.org/abstracts/32164/component-based-testing-using-clustering-and-support-vector-machine" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/32164.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">430</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">8326</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">8325</span> Early Requirement Engineering for Design of Learner Centric Dynamic LMS</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Kausik%20Halder">Kausik Halder</a>, <a href="https://publications.waset.org/abstracts/search?q=Nabendu%20Chaki"> Nabendu Chaki</a>, <a href="https://publications.waset.org/abstracts/search?q=Ranjan%20Dasgupta"> Ranjan Dasgupta</a> </p> <p class="card-text"><strong>Abstract:</strong></p> We present a modelling framework that supports the engineering of early requirements specifications for design of learner centric dynamic Learning Management System. The framework is based on i* modelling tool and Means End Analysis, that adopts primitive concepts for modelling early requirements (such as actor, goal, and strategic dependency). We show how pedagogical and computational requirements for designing a learner centric Learning Management system can be adapted for the automatic early requirement engineering specifications. Finally, we presented a model on a Learner Quanta based adaptive Courseware. Our early requirement analysis shows that how means end analysis reveals gaps and inconsistencies in early requirements specifications that are by no means trivial to discover without the help of formal analysis tool. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=adaptive%20courseware" title="adaptive courseware">adaptive courseware</a>, <a href="https://publications.waset.org/abstracts/search?q=early%20requirement%20engineering" title=" early requirement engineering"> early requirement engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=means%20end%20analysis" title=" means end analysis"> means end analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=organizational%20modelling" title=" organizational modelling"> organizational modelling</a>, <a href="https://publications.waset.org/abstracts/search?q=requirement%20modelling" title=" requirement modelling"> requirement modelling</a> </p> <a href="https://publications.waset.org/abstracts/8626/early-requirement-engineering-for-design-of-learner-centric-dynamic-lms" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/8626.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">8324</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">8323</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">8322</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">8321</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">8320</span> The Impacts of Local Decision Making on Customisation Process Speed across Distributed Boundaries</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Abdulrahman%20M.%20Qahtani">Abdulrahman M. Qahtani</a>, <a href="https://publications.waset.org/abstracts/search?q=Gary.%20B.%20Wills"> Gary. B. Wills</a>, <a href="https://publications.waset.org/abstracts/search?q=Andy.%20M.%20Gravell"> Andy. M. Gravell</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Communicating and managing customers’ requirements in software development projects play a vital role in the software development process. While it is difficult to do so locally, it is even more difficult to communicate these requirements over distributed boundaries and to convey them to multiple distribution customers. This paper discusses the communication of multiple distribution customers’ requirements in the context of customised software products. The main purpose is to understand the challenges of communicating and managing customisation requirements across distributed boundaries. We propose a model for Communicating Customisation Requirements of Multi-Clients in a Distributed Domain (CCRD). Thereafter, we evaluate that model by presenting the findings of a case study conducted with a company with customisation projects for 18 distributed customers. Then, we compare the outputs of the real case process and the outputs of the CCRD model using simulation methods. Our conjecture is that the CCRD model can reduce the challenge of communication requirements over distributed organisational boundaries, and the delay in decision making and in the entire customisation process time. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=customisation%20software%20products" title="customisation software products">customisation software products</a>, <a href="https://publications.waset.org/abstracts/search?q=global%20software%20engineering" title=" global software engineering"> global software engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=local%20decision%20making" title=" local decision making"> local decision making</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=simulation%20model" title=" simulation model"> simulation model</a> </p> <a href="https://publications.waset.org/abstracts/17567/the-impacts-of-local-decision-making-on-customisation-process-speed-across-distributed-boundaries" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/17567.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">429</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">8319</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">8318</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">8317</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">8316</span> Determination of Optimum Water Consumptive Using Deficit Irrigation Model for Barely: A Case Study in Arak, Iran</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Mohsen%20Najarchi">Mohsen Najarchi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This research was carried out in five fields (5-15 hectares) in Arak located in center of Iran, to determine optimum level of water consumed for Barely in four stages growth (vegetative, yield formation, flowering, and ripening). Actual evapotranspiration was calculated using measured water requirement in the fields. Five levels of water requirement equal to 50, 60, 70, 80, and 90 percents formed the treatments. To determine the optimum level of water requirement linear programming was used. The study showed 60 percent water requirement (40 percent deficit irrigation) has been the optimum level of irrigation for winter wheat in four stages of growth. Comparison between all of the treatments indicated above with normal condition (100% water requirement) shows increasing in water use efficiency. Although 40% deficit irrigation treatment lead to decrease of 38% in yield, net benefit was increasing in 11.37%. Furthermore, in comparison with normal condition, 70% of water requirement increased water use efficiency as 30%. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=optimum" title="optimum">optimum</a>, <a href="https://publications.waset.org/abstracts/search?q=deficit%20irrigation" title=" deficit irrigation"> deficit irrigation</a>, <a href="https://publications.waset.org/abstracts/search?q=water%20use%20efficiency" title=" water use efficiency"> water use efficiency</a>, <a href="https://publications.waset.org/abstracts/search?q=evapotranspiration" title=" evapotranspiration"> evapotranspiration</a> </p> <a href="https://publications.waset.org/abstracts/14760/determination-of-optimum-water-consumptive-using-deficit-irrigation-model-for-barely-a-case-study-in-arak-iran" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/14760.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">396</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">8315</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> <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%20requirement%20engineering&page=2">2</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=3">3</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=4">4</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=5">5</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=6">6</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=7">7</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=8">8</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=9">9</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%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%20requirement%20engineering&page=278">278</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%20engineering&page=279">279</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=software%20requirement%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>