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: requirements</title> <meta name="description" content="Search results for: requirements"> <meta name="keywords" content="requirements"> <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="requirements" 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="requirements"> <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> 2490</div> </div> </div> </div> <h1 class="mt-3 mb-3 text-center" style="font-size:1.6rem;">Search results for: requirements</h1> <div class="card paper-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">2490</span> Conflicts Identification Approach among Stakeholders in Goal-Oriented Requirements Analysis </h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Muhammad%20Suhaib">Muhammad Suhaib</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirements Analysis are the most important part of software Engineering for both system application development, and project requirements. Conflicts often arise during the requirements gathering and analysis phase. This research aims to identify conflicts during the requirements gathering phase in software development life cycle, Research, Development, and Technology converted the world into a global village. During requirements elicitation/gathering phase it’s very difficult to understand the main objective of stakeholders, after completion of requirements elicitation task final results are used for Software Requirements Specification (SRS), SRS is the highly important outcome of the requirements analysis phase. this is the foundation between the developers and stakeholders or customers, proposed methodology will be helpful to identify those conflicts in a very easy manner during the initial phase of the project. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=goal%20oriented%20requirements%20analysis" title="goal oriented requirements analysis">goal oriented requirements analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=conflicts%20identification%20model" title=" conflicts identification model"> conflicts identification model</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements%20analysis" title=" requirements analysis"> requirements analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements%20engineering" title=" requirements engineering"> requirements engineering</a> </p> <a href="https://publications.waset.org/abstracts/103309/conflicts-identification-approach-among-stakeholders-in-goal-oriented-requirements-analysis" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/103309.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">134</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">2489</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">2488</span> Teaching Students Collaborative Requirements Engineering: Case Study of Red:Wire</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Dagmar%20Monett">Dagmar Monett</a>, <a href="https://publications.waset.org/abstracts/search?q=Sven-Erik%20Kujat"> Sven-Erik Kujat</a>, <a href="https://publications.waset.org/abstracts/search?q=Marvin%20Hartmann"> Marvin Hartmann</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper discusses the use of a template-based approach for documenting high-quality requirements as part of course projects in an undergraduate Software Engineering course. In order to ease some of the Requirements Engineering activities that are performed when defining requirements by using the template, a new CASE tool, RED:WIRE, was first developed and later tested by students attending the course. Two questionnaires were conceived around a study that aims to analyze the new tool’s learnability as well as other obtained results concerning its usability in particular and the Requirements Engineering skills developed by the students in general. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=CASE%20tool" title="CASE tool">CASE tool</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=SOPHIST%20template" title=" SOPHIST template"> SOPHIST template</a>, <a href="https://publications.waset.org/abstracts/search?q=undergraduate%20course" title=" undergraduate course"> undergraduate course</a> </p> <a href="https://publications.waset.org/abstracts/41626/teaching-students-collaborative-requirements-engineering-case-study-of-redwire" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/41626.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">376</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">2487</span> Classification of Impact Damages with Respect of Damage Tolerance Design Approach and Airworthiness Requirements</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=T.%20Mrna">T. Mrna</a>, <a href="https://publications.waset.org/abstracts/search?q=R.%20Doubrava"> R. Doubrava</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper describes airworthiness requirements with respect damage tolerance. Damage tolerance determines the amount and magnitude of damage on parts of the airplane. Airworthiness requirements determine the amount of damage that can still be in flight capable of the condition. Component damage can be defined as barely visible impact damage, visible impact damage or clear visible impact damage. Damage is also distributed it according to the velocity. It is divided into low or high velocity impact damage. The severity of damage to the part of airplane divides the airworthiness requirements into several categories according to severity. Airworthiness requirements are determined by type airplane. All types of airplane do not have the same conditions for airworthiness requirements. This knowledge is important for designing and operating an airplane. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=airworthiness%20requirements" title="airworthiness requirements">airworthiness requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=composite" title=" composite"> composite</a>, <a href="https://publications.waset.org/abstracts/search?q=damage%20tolerance" title=" damage tolerance"> damage tolerance</a>, <a href="https://publications.waset.org/abstracts/search?q=low%20and%20high%20velocity%20impact" title=" low and high velocity impact"> low and high velocity impact</a> </p> <a href="https://publications.waset.org/abstracts/82178/classification-of-impact-damages-with-respect-of-damage-tolerance-design-approach-and-airworthiness-requirements" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/82178.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">569</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">2486</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">2485</span> Rating the Importance of Customer Requirements for Green Product Using Analytic Hierarchy Process Methodology</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Lara%20F.%20Horani">Lara F. Horani</a>, <a href="https://publications.waset.org/abstracts/search?q=Shurong%20Tong"> Shurong Tong</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Identification of customer requirements and their preferences are the starting points in the process of product design. Most of design methodologies focus on traditional requirements. But in the previous decade, the green products and the environment requirements have increasingly attracted the attention with the constant increase in the level of consumer awareness towards environmental problems (such as green-house effect, global warming, pollution and energy crisis, and waste management). Determining the importance weights for the customer requirements is an essential and crucial process. This paper used the analytic hierarchy process (AHP) approach to evaluate and rate the customer requirements for green products. With respect to the ultimate goal of customer satisfaction, surveys are conducted using a five-point scale analysis. With the help of this scale, one can derive the weight vectors. This approach can improve the imprecise ranking of customer requirements inherited from studies based on the conventional AHP. Furthermore, the AHP with extent analysis is simple and easy to implement to prioritize customer requirements. The research is based on collected data through a questionnaire survey conducted over a sample of 160 people belonging to different age, marital status, education and income groups in order to identify the customer preferences for green product requirements. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=analytic%20hierarchy%20process%20%28AHP%29" title="analytic hierarchy process (AHP)">analytic hierarchy process (AHP)</a>, <a href="https://publications.waset.org/abstracts/search?q=green%20product" title=" green product"> green product</a>, <a href="https://publications.waset.org/abstracts/search?q=customer%20requirements%20for%20green%20design" title=" customer requirements for green design"> customer requirements for green design</a>, <a href="https://publications.waset.org/abstracts/search?q=importance%20weights%20for%20the%20customer%20requirements" title=" importance weights for the customer requirements"> importance weights for the customer requirements</a> </p> <a href="https://publications.waset.org/abstracts/81006/rating-the-importance-of-customer-requirements-for-green-product-using-analytic-hierarchy-process-methodology" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/81006.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">243</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">2484</span> Requirements Gathering for Improved Software Usability and the Potential for Usage-Centred Design</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Kholod%20J.%20Alotaibi">Kholod J. Alotaibi</a>, <a href="https://publications.waset.org/abstracts/search?q=Andrew%20M.%20Gravell"> Andrew M. Gravell</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Usability is an important software quality that is often neglected at the design stage. Although methods exist to incorporate elements of usability engineering, there is a need for more balanced usability focused methods that can enhance the experience of software usability for users. In this regard, the potential for Usage-Centered Design is explored with respect to requirements gathering and is shown to lead to high software usability besides other benefits. It achieves this through its focus on usage, defining essential use cases, by conducting task modeling, encouraging user collaboration, refining requirements, and so on. The requirements gathering process in UgCD is described in detail. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=requirements%20gathering" title="requirements gathering">requirements gathering</a>, <a href="https://publications.waset.org/abstracts/search?q=usability" title=" usability"> usability</a>, <a href="https://publications.waset.org/abstracts/search?q=usage-centred%20design" title=" usage-centred design"> usage-centred design</a>, <a href="https://publications.waset.org/abstracts/search?q=computer%20science" title=" computer science"> computer science</a> </p> <a href="https://publications.waset.org/abstracts/2468/requirements-gathering-for-improved-software-usability-and-the-potential-for-usage-centred-design" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/2468.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">2483</span> Requirements Management in Agile</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ravneet%20Kaur">Ravneet Kaur</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The concept of Agile Requirements Engineering and Management is not new. However, the struggle to figure out how traditional Requirements Management Process fits within an Agile framework remains complex. This paper talks about a process that can merge the organization’s traditional Requirements Management Process nicely into the Agile Software Development Process. This process provides Traceability of the Product Backlog to the external documents on one hand and User Stories on the other hand. It also gives sufficient evidence that the system will deliver the right functionality with good quality in the form of various statistics and reports. In the nutshell, by overlaying a process on top of Agile, without disturbing the Agility, we are able to get synergic benefits in terms of productivity, profitability, its reporting, and end to end visibility to all Stakeholders. The framework can be used for just-in-time requirements definition or to build a repository of requirements for future use. The goal is to make sure that the business (specifically, the product owner) can clearly articulate what needs to be built and define what is of high quality. To accomplish this, the requirements cycle follows a Scrum-like process that mirrors the development cycle but stays two to three steps ahead. The goal is to create a process by which requirements can be thoroughly vetted, organized, and communicated in a manner that is iterative, timely, and quality-focused. Agile is quickly becoming the most popular way of developing software because it fosters continuous improvement, time-boxed development cycles, and more quickly delivering value to the end users. That value will be driven to a large extent by the quality and clarity of requirements that feed the software development process. An agile, lean, and timely approach to requirements as the starting point will help to ensure that the process is optimized. <p class="card-text"><strong>Keywords:</strong> <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=Agile" title=" Agile"> Agile</a> </p> <a href="https://publications.waset.org/abstracts/16174/requirements-management-in-agile" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/16174.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">370</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">2482</span> User Requirements Analysis for the Development of Assistive Navigation Mobile Apps for Blind and Visually Impaired People</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Paraskevi%20Theodorou">Paraskevi Theodorou</a>, <a href="https://publications.waset.org/abstracts/search?q=Apostolos%20Meliones"> Apostolos Meliones</a> </p> <p class="card-text"><strong>Abstract:</strong></p> In the context of the development process of two assistive navigation mobile apps for blind and visually impaired people (BVI) an extensive qualitative analysis of the requirements of potential users has been conducted. The analysis was based on interviews with BVIs and aimed to elicit not only their needs with respect to autonomous navigation but also their preferences on specific features of the apps under development. The elicited requirements were structured into four main categories, namely, requirements concerning the capabilities, functionality and usability of the apps, as well as compatibility requirements with respect to other apps and services. The main categories were then further divided into nine sub-categories. This classification, along with its content, aims to become a useful tool for the researcher or the developer who is involved in the development of digital services for BVI. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=accessibility" title="accessibility">accessibility</a>, <a href="https://publications.waset.org/abstracts/search?q=assistive%20mobile%20apps" title=" assistive mobile apps"> assistive mobile apps</a>, <a href="https://publications.waset.org/abstracts/search?q=blind%20and%20visually%20impaired%20people" title=" blind and visually impaired people"> blind and visually impaired people</a>, <a href="https://publications.waset.org/abstracts/search?q=user%20requirements%20analysis" title=" user requirements analysis"> user requirements analysis</a> </p> <a href="https://publications.waset.org/abstracts/114395/user-requirements-analysis-for-the-development-of-assistive-navigation-mobile-apps-for-blind-and-visually-impaired-people" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/114395.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">123</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">2481</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">2480</span> From User's Requirements to UML Class Diagram</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Zeineb%20Ben%20Azzouz">Zeineb Ben Azzouz</a>, <a href="https://publications.waset.org/abstracts/search?q=Wahiba%20Ben%20Abdessalem%20Karaa"> Wahiba Ben Abdessalem Karaa</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The automated extraction of UML class diagram from natural language requirements is a highly challenging task. Many approaches, frameworks and tools have been presented in this field. Nonetheless, the experiments of these tools have shown that there is no approach that can work best all the time. In this context, we propose a new accurate approach to facilitate the automatic mapping from textual requirements to UML class diagram. Our new approach integrates the best properties of statistical Natural Language Processing (NLP) techniques to reduce ambiguity when analysing natural language requirements text. In addition, our approach follows the best practices defined by conceptual modelling experts to determine some patterns indispensable for the extraction of basic elements and concepts of the class diagram. Once the relevant information of class diagram is captured, a XMI document is generated and imported with a CASE tool to build the corresponding UML class diagram. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=class%20diagram" title="class diagram">class diagram</a>, <a href="https://publications.waset.org/abstracts/search?q=user%E2%80%99s%20requirements" title=" user’s requirements"> user’s requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=XMI" title=" XMI"> XMI</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/7098/from-users-requirements-to-uml-class-diagram" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/7098.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">471</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">2479</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">2478</span> Methods Used to Perform Requirements Elicitation for FinTech Application Development</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Zhao%20Pengcheng">Zhao Pengcheng</a>, <a href="https://publications.waset.org/abstracts/search?q=Yin%20Siyuan"> Yin Siyuan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Fintech is the new hot topic of the 21st century, a discipline that combines financial theory with computer modelling. It can provide both digital analysis methods for investment banks and investment decisions for users. Given the variety of services available, it is necessary to provide a superior method of requirements elicitation to ensure that users' needs are addressed in the software development process. The accuracy of traditional software requirements elicitation methods is not sufficient, so this study attempts to use a multi-perspective based requirements heuristic framework. Methods such as interview and questionnaire combination, card sorting, and model driven are proposed. The collection results from PCA show that the new methods can better help with requirements elicitation. However, the method has some limitations and, there are some efficiency issues. However, the research in this paper provides a good theoretical extension that can provide researchers with some new research methods and perspectives viewpoints. <p class="card-text"><strong>Keywords:</strong> <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=FinTech" title=" FinTech"> FinTech</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=survey" title=" survey"> survey</a>, <a href="https://publications.waset.org/abstracts/search?q=interview" title=" interview"> interview</a>, <a href="https://publications.waset.org/abstracts/search?q=model-driven" title=" model-driven"> model-driven</a> </p> <a href="https://publications.waset.org/abstracts/158707/methods-used-to-perform-requirements-elicitation-for-fintech-application-development" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/158707.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">2477</span> A Causal Model for Environmental Design of Residential Community for Elderly Well-Being in Thailand</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Porntip%20Ruengtam">Porntip Ruengtam</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This article is an extension of previous research presenting the relevant factors related to environmental perceptions, residential community, and the design of a healing environment, which have effects on the well-being and requirements of Thai elderly. Research methodology began with observations and interviews in three case studies in terms of the management processes and environment design of similar existing projects in Thailand. The interview results were taken to summarize with related theories and literature. A questionnaire survey was designed for data collection to confirm the factors of requirements in a residential community intended for the Thai elderly. A structural equation model (SEM) was formulated to explain the cause-effect factors for the requirements of a residential community for Thai elderly. The research revealed that the requirements of a residential community for Thai elderly were classified into three groups when utilizing a technique for exploratory factor analysis. The factors were comprised of (1) requirements for general facilities and activities, (2) requirements for facilities related to health and security, and (3) requirements for facilities related to physical exercise in the residential community. The results from the SEM showed the background of elderly people had a direct effect on their requirements for a residential community from various aspects. The results should lead to the formulation of policies for design and management of residential communities for the elderly in order to enhance quality of life as well as both the physical and mental health of the Thai elderly. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=elderly" title="elderly">elderly</a>, <a href="https://publications.waset.org/abstracts/search?q=environmental%20design" title=" environmental design"> environmental design</a>, <a href="https://publications.waset.org/abstracts/search?q=residential%20community" title=" residential community"> residential community</a>, <a href="https://publications.waset.org/abstracts/search?q=structural%20equation%20modeling" title=" structural equation modeling"> structural equation modeling</a> </p> <a href="https://publications.waset.org/abstracts/67200/a-causal-model-for-environmental-design-of-residential-community-for-elderly-well-being-in-thailand" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/67200.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">313</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">2476</span> Adaptive Routing Protocol for Dynamic Wireless Sensor Networks</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Fayez%20Mostafa%20Alhamoui">Fayez Mostafa Alhamoui</a>, <a href="https://publications.waset.org/abstracts/search?q=Adnan%20Hadi%20Mahdi%20Al-%20Helali"> Adnan Hadi Mahdi Al- Helali</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The main issue in designing a wireless sensor network (WSN) is the finding of a proper routing protocol that complies with the several requirements of high reliability, short latency, scalability, low power consumption, and many others. This paper proposes a novel routing algorithm that complies with these design requirements. The new routing protocol divides the WSN into several sub-networks and each sub-network is divided into several clusters. This division is designed to reduce the number of radio transmission and hence decreases the power consumption. The network division may be changed dynamically to adapt with the network changes and allows the realization of the design requirements. <p class="card-text"><strong>Keywords:</strong> <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=routing%20protocols" title=" routing protocols"> routing protocols</a>, <a href="https://publications.waset.org/abstracts/search?q=AD%20HOC%20topology" title=" AD HOC topology"> AD HOC topology</a>, <a href="https://publications.waset.org/abstracts/search?q=cluster" title=" cluster"> cluster</a>, <a href="https://publications.waset.org/abstracts/search?q=sub-network" title=" sub-network"> sub-network</a>, <a href="https://publications.waset.org/abstracts/search?q=WSN%20design%20requirements" title=" WSN design requirements"> WSN design requirements</a> </p> <a href="https://publications.waset.org/abstracts/37365/adaptive-routing-protocol-for-dynamic-wireless-sensor-networks" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/37365.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">537</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">2475</span> JREM: An Approach for Formalising Models in the Requirements Phase with JSON and NoSQL Databases</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Aitana%20Alonso-Nogueira">Aitana Alonso-Nogueira</a>, <a href="https://publications.waset.org/abstracts/search?q=Helia%20Est%C3%A9vez-Fern%C3%A1ndez"> Helia Estévez-Fernández</a>, <a href="https://publications.waset.org/abstracts/search?q=Isa%C3%ADas%20Garc%C3%ADa"> Isaías García</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper presents an approach to reduce some of its current flaws in the requirements phase inside the software development process. It takes the software requirements of an application, makes a conceptual modeling about it and formalizes it within JSON documents. This formal model is lodged in a NoSQL database which is document-oriented, that is, MongoDB, because of its advantages in flexibility and efficiency. In addition, this paper underlines the contributions of the detailed approach and shows some applications and benefits for the future work in the field of automatic code generation using model-driven engineering tools. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=conceptual%20modelling" title="conceptual modelling">conceptual modelling</a>, <a href="https://publications.waset.org/abstracts/search?q=JSON" title=" JSON"> JSON</a>, <a href="https://publications.waset.org/abstracts/search?q=NoSQL%20databases" title=" NoSQL databases"> NoSQL databases</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%20development" title=" software development"> software development</a> </p> <a href="https://publications.waset.org/abstracts/58140/jrem-an-approach-for-formalising-models-in-the-requirements-phase-with-json-and-nosql-databases" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/58140.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">378</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">2474</span> Worldwide Overview of Homologation for Radio Products</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Nekzad%20R%20Doctor">Nekzad R Doctor</a>, <a href="https://publications.waset.org/abstracts/search?q=Shubham%20Bhonde"> Shubham Bhonde</a>, <a href="https://publications.waset.org/abstracts/search?q=Shashwat%20Gawande"> Shashwat Gawande</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The homologation, also known as “type approval,” describes primarily the granting of approval by an official authority. For the use and the import of Keys & ID transmitters as well as Body Control Modules with radio transmission around the globe, homologation is necessary. Depending on country requirements or technical properties (e.g., frequency or transmission power), different approaches need to be fulfilled. The requirements could vary in the form of certifications requirement or exemptions, any technologies forbidden, additional legal requirements and type approval for manufacturing locations. This research will give an overview of all different types of approval and technical requirement for worldwide countries.Information is not available for a lot of countries which is challenging for an entrant in the field of homologation. Also, even if the information is available, there could be a language barrier as different countries sometimes upload their regulations in a local language. Also, there is a lot of unclarity in many countries regarding type approval requirements (Safety, EMC certification,2nd factory certification). To have a clear overview and understanding of type approval requirements, in this document, the Worldwide country will be divided into 4 groups based on technology. After which, a region country-specific type approval requirement will be checked in detail. This document will facilitate in providing global Homologation requirements. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=homologation" title="homologation">homologation</a>, <a href="https://publications.waset.org/abstracts/search?q=type%20approval" title=" type approval"> type approval</a>, <a href="https://publications.waset.org/abstracts/search?q=EMC" title=" EMC"> EMC</a>, <a href="https://publications.waset.org/abstracts/search?q=body%20control%20modules" title=" body control modules"> body control modules</a> </p> <a href="https://publications.waset.org/abstracts/151437/worldwide-overview-of-homologation-for-radio-products" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/151437.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">96</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">2473</span> A Framework for Teaching Distributed Requirements Engineering in Latin American Universities</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=G.%20Sevilla">G. Sevilla</a>, <a href="https://publications.waset.org/abstracts/search?q=S.%20Zapata"> S. Zapata</a>, <a href="https://publications.waset.org/abstracts/search?q=F.%20Giraldo"> F. Giraldo</a>, <a href="https://publications.waset.org/abstracts/search?q=E.%20Torres"> E. Torres</a>, <a href="https://publications.waset.org/abstracts/search?q=C.%20Collazos"> C. Collazos</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This work describes a framework for teaching of global software engineering (GSE) in university undergraduate programs. This framework proposes a method of teaching that incorporates adequate techniques of software requirements elicitation and validated tools of communication, critical aspects to global software development scenarios. The use of proposed framework allows teachers to simulate small software development companies formed by Latin American students, which build information systems. Students from three Latin American universities played the roles of engineers by applying an iterative development of a requirements specification in a global software project. The proposed framework involves the use of a specific purpose Wiki for asynchronous communication between the participants of the process. It is also a practice to improve the quality of software requirements that are formulated by the students. The additional motivation of students to participate in these practices, in conjunction with peers from other countries, is a significant additional factor that positively contributes to the learning process. The framework promotes skills for communication, negotiation, and other complementary competencies that are useful for working on GSE scenarios. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=requirements%20analysis" title="requirements analysis">requirements analysis</a>, <a href="https://publications.waset.org/abstracts/search?q=distributed%20requirements%20engineering" title=" distributed requirements engineering"> distributed requirements engineering</a>, <a href="https://publications.waset.org/abstracts/search?q=practical%20experiences" title=" practical experiences"> practical experiences</a>, <a href="https://publications.waset.org/abstracts/search?q=collaborative%20support" title=" collaborative support"> collaborative support</a> </p> <a href="https://publications.waset.org/abstracts/97296/a-framework-for-teaching-distributed-requirements-engineering-in-latin-american-universities" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/97296.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">204</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">2472</span> A Systematic Literature Review on Changing Customer Requirements for Sustainable Design over Time</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Lara%20F.%20Horani">Lara F. Horani</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Design is one of the most important stages in the process of product development. Product design has experienced significant changes over the years ranging from concentrating on cost and performance to combining economic, environmental and social considerations in customer requirements. Its evolution is in accordance with rapidly changing technology, economic situations, and climate change and environmental issues, as well as social context. Within product design, sustainability is a concept that balances economic, social and environmental aspects. This research aims to express changes in customer requirements over time from the viewpoint of sustainable design. It does so by systematically reviewing a broad scope of sustainable design literature. There is a need for a model to consider the changes that take place in customer requirements over time to build a successful relationship with customers which has been presented. Today’s literature does very little to even mention it, let alone present any progress in it. Systematic literature reviews are conducted primarily to: summarize the existing literature around a subject, highlight commonalities to build consensus, illuminate differences, identify gaps that can be filled, provide a background to position future research, and build a framework that can help designers meet the challenges of sustainable design. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=sustainable%20design" title="sustainable design">sustainable design</a>, <a href="https://publications.waset.org/abstracts/search?q=customer%20requirements%20for%20sustainable%20design" title=" customer requirements for sustainable design"> customer requirements for sustainable design</a>, <a href="https://publications.waset.org/abstracts/search?q=systematic%20literature%20reviews" title=" systematic literature reviews"> systematic literature reviews</a>, <a href="https://publications.waset.org/abstracts/search?q=changing%20customer%20requirements" title=" changing customer requirements"> changing customer requirements</a> </p> <a href="https://publications.waset.org/abstracts/67500/a-systematic-literature-review-on-changing-customer-requirements-for-sustainable-design-over-time" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/67500.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">374</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">2471</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">2470</span> New Formula for Revenue Recognition Likely to Change the Prescription for Pharma Industry</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Shruti%20Hajirnis">Shruti Hajirnis</a> </p> <p class="card-text"><strong>Abstract:</strong></p> In May 2014, FASB issued Accounting Standards Update (ASU) 2014-09, Revenue from Contracts with Customers (Topic 606), and the International Accounting Standards Board (IASB) issued International Financial Reporting Standards (IFRS) 15, Revenue from Contracts with Customers that will supersede virtually all revenue recognition requirements in IFRS and US GAAP. FASB and the IASB have basically achieved convergence with these standards, with only some minor differences such as collectability threshold, interim disclosure requirements, early application and effective date, impairment loss reversal and nonpublic entity requirements. This paper discusses the impact of five-step model prescribed in new revenue standard on the entities operating in Pharma industry. It also outlines the considerations for these entities while implementing the new standard. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=revenue%20recognition" title="revenue recognition">revenue recognition</a>, <a href="https://publications.waset.org/abstracts/search?q=pharma%20industry" title=" pharma industry"> pharma industry</a>, <a href="https://publications.waset.org/abstracts/search?q=standard" title=" standard"> standard</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements" title=" requirements"> requirements</a> </p> <a href="https://publications.waset.org/abstracts/20117/new-formula-for-revenue-recognition-likely-to-change-the-prescription-for-pharma-industry" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/20117.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">444</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">2469</span> Going beyond Stakeholder Participation</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Florian%20Engel">Florian Engel</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Only with a radical change to an intrinsically motivated project team, through giving the employees the freedom for autonomy, mastery and purpose, it is then possible to develop excellent products. With these changes, combined with using a rapid application development approach, the group of users serves as an important indicator to test the market needs, rather than only as the stakeholders for requirements. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=intrinsic%20motivation" title="intrinsic motivation">intrinsic motivation</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements%20elicitation" title=" requirements elicitation"> requirements elicitation</a>, <a href="https://publications.waset.org/abstracts/search?q=self-directed%20work" title=" self-directed work"> self-directed work</a>, <a href="https://publications.waset.org/abstracts/search?q=stakeholder%20participation" title=" stakeholder participation"> stakeholder participation</a> </p> <a href="https://publications.waset.org/abstracts/29706/going-beyond-stakeholder-participation" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/29706.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">2468</span> Defining a Holistic Approach for Model-Based System Engineering: Paradigm and Modeling Requirements</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Hycham%20Aboutaleb">Hycham Aboutaleb</a>, <a href="https://publications.waset.org/abstracts/search?q=Bruno%20Monsuez"> Bruno Monsuez</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Current systems complexity has reached a degree that requires addressing conception and design issues while taking into account all the necessary aspects. Therefore, one of the main challenges is the way complex systems are specified and designed. The exponential growing effort, cost and time investment of complex systems in modeling phase emphasize the need for a paradigm, a framework and a environment to handle the system model complexity. For that, it is necessary to understand the expectations of the human user of the model and his limits. This paper presents a generic framework for designing complex systems, highlights the requirements a system model needs to fulfill to meet human user expectations, and defines the refined functional as well as non functional requirements modeling tools needs to meet to be useful in model-based system engineering. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=system%20modeling" title="system modeling">system modeling</a>, <a href="https://publications.waset.org/abstracts/search?q=modeling%20language" title=" modeling language"> modeling language</a>, <a href="https://publications.waset.org/abstracts/search?q=modeling%20requirements" title=" modeling requirements"> modeling requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=framework" title=" framework"> framework</a> </p> <a href="https://publications.waset.org/abstracts/25771/defining-a-holistic-approach-for-model-based-system-engineering-paradigm-and-modeling-requirements" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/25771.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">532</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">2467</span> A Survey on Requirements and Challenges of Internet Protocol Television Service over Software Defined Networking</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Esmeralda%20Hysenbelliu">Esmeralda Hysenbelliu</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Over the last years, the demand for high bandwidth services, such as live (IPTV Service) and on-demand video streaming, steadily and rapidly increased. It has been predicted that video traffic (IPTV, VoD, and WEB TV) will account more than 90% of global Internet Protocol traffic that will cross the globe in 2016. Consequently, the importance and consideration on requirements and challenges of service providers faced today in supporting user’s requests for entertainment video across the various IPTV services through virtualization over Software Defined Networks (SDN), is tremendous in the highest stage of attention. What is necessarily required, is to deliver optimized live and on-demand services like Internet Protocol Service (IPTV Service) with low cost and good quality by strictly fulfill the essential requirements of Clients and ISP’s (Internet Service Provider’s) in the same time. The aim of this study is to present an overview of the important requirements and challenges of IPTV service with two network trends on solving challenges through virtualization (SDN and Network Function Virtualization). This paper provides an overview of researches published in the last five years. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=challenges" title="challenges">challenges</a>, <a href="https://publications.waset.org/abstracts/search?q=IPTV%20service" title=" IPTV service"> IPTV service</a>, <a href="https://publications.waset.org/abstracts/search?q=requirements" title=" requirements"> requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=software%20defined%20networking%20%28SDN%29" title=" software defined networking (SDN)"> software defined networking (SDN)</a> </p> <a href="https://publications.waset.org/abstracts/49752/a-survey-on-requirements-and-challenges-of-internet-protocol-television-service-over-software-defined-networking" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/49752.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">271</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">2466</span> A Survey of Attacks and Security Requirements 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=Vishnu%20Pratap%20Singh%20Kirar">Vishnu Pratap Singh Kirar</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Wireless sensor network (WSN) is a network of many interconnected networked systems, they equipped with energy resources and they are used to detect other physical characteristics. On WSN, there are many researches are performed in past decades. WSN applicable in many security systems govern by military and in many civilian related applications. Thus, the security of WSN gets attention of researchers and gives an opportunity for many future aspects. Still, there are many other issues are related to deployment and overall coverage, scalability, size, energy efficiency, quality of service (QoS), computational power and many more. In this paper we discus about various applications and security related issue and requirements of WSN. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=wireless%20sensor%20network%20%28WSN%29" title="wireless sensor network (WSN)">wireless sensor network (WSN)</a>, <a href="https://publications.waset.org/abstracts/search?q=wireless%20network%20attacks" title=" wireless network attacks"> wireless network attacks</a>, <a href="https://publications.waset.org/abstracts/search?q=wireless%20network%20security" title=" wireless network security"> wireless network security</a>, <a href="https://publications.waset.org/abstracts/search?q=security%20requirements" title=" security requirements"> security requirements</a> </p> <a href="https://publications.waset.org/abstracts/22341/a-survey-of-attacks-and-security-requirements-in-wireless-sensor-networks" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/22341.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">491</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">2465</span> An Analysis of Business Intelligence Requirements in South African Corporates</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Adheesh%20Budree">Adheesh Budree</a>, <a href="https://publications.waset.org/abstracts/search?q=Olaf%20Jacob"> Olaf Jacob</a>, <a href="https://publications.waset.org/abstracts/search?q=Louis%20CH%20Fourie"> Louis CH Fourie</a>, <a href="https://publications.waset.org/abstracts/search?q=James%20Njenga"> James Njenga</a>, <a href="https://publications.waset.org/abstracts/search?q=Gabriel%20D%20Hoffman"> Gabriel D Hoffman</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Business Intelligence (BI) is implemented by organisations for many reasons and chief among these is improved data support, decision support and savings. The main purpose of this study is to determine BI requirements and availability within South African organisations. The study addresses the following areas as identified as part of a literature review; assessing BI practices in businesses over a range of industries, sectors and managerial functions, determining the functionality of BI (technologies, architecture and methods). It was found that the overall satisfaction with BI in larger organisations is low due to lack of ability to meet user requirements. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=business%20intelligence" title="business intelligence">business intelligence</a>, <a href="https://publications.waset.org/abstracts/search?q=business%20value" title=" business value"> business value</a>, <a href="https://publications.waset.org/abstracts/search?q=data%20management" title=" data management"> data management</a>, <a href="https://publications.waset.org/abstracts/search?q=South%20Africa" title=" South Africa"> South Africa</a> </p> <a href="https://publications.waset.org/abstracts/24373/an-analysis-of-business-intelligence-requirements-in-south-african-corporates" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/24373.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">577</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">2464</span> A Six-Year Case Study Evaluating the Stakeholders’ Requirements and Satisfaction in Higher Educational Establishments</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ioannis%20I.%20%CE%91ngeli">Ioannis I. Αngeli</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Worldwide and mainly in the European Union, many standards, regulations, models and systems exists for the evaluation and identification of stakeholders’ requirements of individual universities and higher education (HE) in general. All systems are targeting to measure or evaluate the Universities’ Quality Assurance Systems and the services offered to the recipients of HE, mainly the students. Numerous surveys were conducted in the past either by each university or by organized bodies to identify the students’ satisfaction or to evaluate to what extent these requirements are fulfilled. In this paper, the main results of an ongoing 6-year joint research will be presented very briefly. This research deals with an in depth investigation of student’s satisfaction, students personal requirements, a cup analysis among these two parameters and compares different universities. Through this research an attempt will be made to address four very important questions in higher education establishments (HEE): (1) Are there any common requirements, parameters, good practices or questions that apply to a large number of universities that will assure that students’ requirements are fulfilled? (2) Up to what extent the individual programs of HEE fulfil the requirements of the stakeholders? (3) Are there any similarities on specific programs among European HEE? (4) To what extent the knowledge acquired in a specific course program is utilized or used in a specific country? For the execution of the research an internationally accepted questionnaire(s) was used to evaluate up to what extent the students’ requirements and satisfaction were fulfilled in 2012 and five years later (2017). Samples of students and or universities were taken from many European Universities. The questionnaires used, the sampling method and methodology adopted, as well as the comparison tables and results will be very valuable to any university that is willing to follow the same route and methodology or compare the results with their own HHE. Apart from the unique methodology, valuable results are demonstrated from the four case studies. There is a great difference between the student’s expectations or importance from what they are getting from their universities (in all parameters they are getting less). When there is a crisis or budget cut in HEE there is a direct impact to students. There are many differences on subjects taught in European universities. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=quality%20in%20higher%20education" title="quality in higher education">quality in higher education</a>, <a href="https://publications.waset.org/abstracts/search?q=students%27%20requirements" title=" students' requirements"> students' requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=education%20standards" title=" education standards"> education standards</a>, <a href="https://publications.waset.org/abstracts/search?q=student%27s%20survey" title=" student's survey"> student's survey</a>, <a href="https://publications.waset.org/abstracts/search?q=stakeholder%27s%20requirements" title=" stakeholder's requirements"> stakeholder's requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=mechanical%20engineering%20courses" title=" mechanical engineering courses"> mechanical engineering courses</a> </p> <a href="https://publications.waset.org/abstracts/99932/a-six-year-case-study-evaluating-the-stakeholders-requirements-and-satisfaction-in-higher-educational-establishments" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/99932.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">157</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">2463</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">2462</span> Security of Internet of Things: Challenges, Requirements and Future Directions</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Amjad%20F.%20Alharbi">Amjad F. Alharbi</a>, <a href="https://publications.waset.org/abstracts/search?q=Bashayer%20A.%20Alotaibi"> Bashayer A. Alotaibi</a>, <a href="https://publications.waset.org/abstracts/search?q=Fahd%20S.%20Alotaibi"> Fahd S. Alotaibi</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The emergence of Internet of Things (IoT) technology provides capabilities for a huge number of smart devices, services and people to be communicate with each other for exchanging data and information over existing network. While as IoT is progressing, it provides many opportunities for new ways of communications as well it introduces many security and privacy threats and challenges which need to be considered for the future of IoT development. In this survey paper, an IoT security issues as threats and current challenges are summarized. The security architecture for IoT are presented from four main layers. Based on these layers, the IoT security requirements are presented to insure security in the whole system. Furthermore, some researches initiatives related to IoT security are discussed as well as the future direction for IoT security are highlighted. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/abstracts/search?q=Internet%20of%20Things%20%28IoT%29" title="Internet of Things (IoT)">Internet of Things (IoT)</a>, <a href="https://publications.waset.org/abstracts/search?q=IoT%20security%20challenges" title=" IoT security challenges"> IoT security challenges</a>, <a href="https://publications.waset.org/abstracts/search?q=IoT%20security%20requirements" title=" IoT security requirements"> IoT security requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=IoT%20security%20architecture" title=" IoT security architecture"> IoT security architecture</a> </p> <a href="https://publications.waset.org/abstracts/71488/security-of-internet-of-things-challenges-requirements-and-future-directions" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/71488.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">375</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">2461</span> Web Service Architectural Style Selection in Multi-Criteria Requirements</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/abstracts/search?q=Ahmad%20Mohsin">Ahmad Mohsin</a>, <a href="https://publications.waset.org/abstracts/search?q=Syda%20Fatima"> Syda Fatima</a>, <a href="https://publications.waset.org/abstracts/search?q=Falak%20Nawaz"> Falak Nawaz</a>, <a href="https://publications.waset.org/abstracts/search?q=Aman%20Ullah%20Khan"> Aman Ullah Khan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Selection of an appropriate architectural style is vital to the success of target web service under development. The nature of architecture design and selection for service-oriented computing applications is quite different as compared to traditional software. Web Services have complex and rigorous architectural styles to choose. Due to this, selection for accurate architectural style for web services development has become a more complex decision to be made by architects. Architectural style selection is a multi-criteria decision and demands lots of experience in service oriented computing. Decision support systems are good solutions to simplify the selection process of a particular architectural style. Our research suggests a new approach using DSS for selection of architectural styles while developing a web service to cater FRs and NFRs. Our proposed DSS helps architects to select right web service architectural pattern according to the domain and non-functional requirements. In this paper, a rule base DSS has been developed using CLIPS (C Language Integrated Production System) to support decisions using multi-criteria requirements. This DSS takes architectural characteristics, domain requirements and software architect preferences for NFRs as input for different architectural styles in use today in service-oriented computing. Weighted sum model has been applied to prioritize quality attributes and domain requirements. Scores are calculated using multiple criterions to choose the final architecture style. <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=web-service" title=" web-service"> web-service</a>, <a href="https://publications.waset.org/abstracts/search?q=rule-based" title=" rule-based"> rule-based</a>, <a href="https://publications.waset.org/abstracts/search?q=DSS" title=" DSS"> DSS</a>, <a href="https://publications.waset.org/abstracts/search?q=multi-criteria%20requirements" title=" multi-criteria requirements"> multi-criteria requirements</a>, <a href="https://publications.waset.org/abstracts/search?q=quality%20attributes" title=" quality attributes"> quality attributes</a> </p> <a href="https://publications.waset.org/abstracts/46346/web-service-architectural-style-selection-in-multi-criteria-requirements" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/abstracts/46346.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> <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=requirements&page=2">2</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=3">3</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=4">4</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=5">5</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=6">6</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=7">7</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=8">8</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=9">9</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&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=requirements&page=82">82</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&page=83">83</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/abstracts/search?q=requirements&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>