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/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> 1043</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 publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1043</span> An Evaluation of Requirements Management and Traceability Tools</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Muhammad%20Shahid">Muhammad Shahid</a>, <a href="https://publications.waset.org/search?q=Suhaimi%20Ibrahim"> Suhaimi Ibrahim</a>, <a href="https://publications.waset.org/search?q=Mohd%20Naz%27ri%20Mahrin"> Mohd Naz'ri Mahrin</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Requirements management is critical to software delivery success and project lifecycle. Requirements management and their traceability provide assistance for many software engineering activities like impact analysis, coverage analysis, requirements validation and regression testing. In addition requirements traceability is the recognized component of many software process improvement initiatives. Requirements traceability also helps to control and manage evolution of a software system. This paper aims to provide an evaluation of current requirements management and traceability tools. Management and test managers require an appropriate tool for the software under test. We hope, evaluation identified here will help to select the efficient and effective tool. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Requirements%20Traceability" title="Requirements Traceability">Requirements Traceability</a>, <a href="https://publications.waset.org/search?q=Requirements%20TraceabilityTools%3B%20Requirements%20Management" title=" Requirements TraceabilityTools; Requirements Management"> Requirements TraceabilityTools; Requirements Management</a>, <a href="https://publications.waset.org/search?q=Requirement%20Engineering" title=" Requirement Engineering"> Requirement Engineering</a> </p> <a href="https://publications.waset.org/15009/an-evaluation-of-requirements-management-and-traceability-tools" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/15009/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/15009/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/15009/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/15009/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/15009/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/15009/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/15009/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/15009/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/15009/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/15009/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/15009.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">4020</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1042</span> Suitability of Requirements Abstraction Model (RAM) Requirements for High-Level System Testing</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Naeem%20Muhammad">Naeem Muhammad</a>, <a href="https://publications.waset.org/search?q=Yves%20Vandewoude"> Yves Vandewoude</a>, <a href="https://publications.waset.org/search?q=Yolande%20Berbers"> Yolande Berbers</a>, <a href="https://publications.waset.org/search?q=Robert%20Feldt"> Robert Feldt</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>The Requirements Abstraction Model (RAM) helps in managing abstraction in requirements by organizing them at four levels (product, feature, function and component). The RAM is adaptable and can be tailored to meet the needs of the various organizations. Because software requirements are an important source of information for developing high-level tests, organizations willing to adopt the RAM model need to know the suitability of the RAM requirements for developing high-level tests. To investigate this suitability, test cases from twenty randomly selected requirements were developed, analyzed and graded. Requirements were selected from the requirements document of a Course Management System, a web based software system that supports teachers and students in performing course related tasks. This paper describes the results of the requirements document analysis. The results show that requirements at lower levels in the RAM are suitable for developing executable tests whereas it is hard to develop from requirements at higher levels.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Market-driven%20requirements%20engineering" title="Market-driven requirements engineering">Market-driven requirements engineering</a>, <a href="https://publications.waset.org/search?q=requirements%20abstraction%20model" title=" requirements abstraction model"> requirements abstraction model</a>, <a href="https://publications.waset.org/search?q=requirements%20abstraction" title=" requirements abstraction"> requirements abstraction</a>, <a href="https://publications.waset.org/search?q=system%20testing." title=" system testing."> system testing.</a> </p> <a href="https://publications.waset.org/11418/suitability-of-requirements-abstraction-model-ram-requirements-for-high-level-system-testing" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/11418/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/11418/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/11418/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/11418/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/11418/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/11418/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/11418/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/11418/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/11418/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/11418/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/11418.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">1974</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1041</span> Requirements Management in a Distributed Agile Environment </h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Paul%20Prior">Paul Prior</a>, <a href="https://publications.waset.org/search?q=Frank%20Keenan"> Frank Keenan </a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>The importance of good requirements engineering is well documented. Agile practices, promoting collaboration and communications, facilitate the elicitation and management of volatile requirements. However, current Agile practices work in a well-defined environment. It is necessary to have a co-located customer. With distributed development it is not always possible to realize this co-location. In this environment a suitable process, possibly supported by tools, is required to support changing requirements. This paper introduces the issues of concern when managing requirements in a distributed environment and describes work done at the Software Technology Research Centre as part of the NOMAD project.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Agile" title="Agile">Agile</a>, <a href="https://publications.waset.org/search?q=Distributed" title=" Distributed"> Distributed</a>, <a href="https://publications.waset.org/search?q=Requirements%20Management" title=" Requirements Management"> Requirements Management</a>, <a href="https://publications.waset.org/search?q=XP." title=" XP."> XP.</a> </p> <a href="https://publications.waset.org/8722/requirements-management-in-a-distributed-agile-environment" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/8722/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/8722/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/8722/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/8722/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/8722/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/8722/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/8722/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/8722/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/8722/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/8722/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/8722.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">1807</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1040</span> Requirements Management as a Competitive Factor in the it Mid Tier Business Concerning the Implementation of Erp-Software</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Oliver%20Gr%C3%BCn">Oliver Gr眉n</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The success of IT-projects concerning the implementation of business application Software is strongly depending upon the application of an efficient requirements management, to understand the business requirements and to realize them in the IT. But in fact, the Potentials of the requirements management are not fully exhausted by small and medium sized enterprises (SME) of the IT sector. To work out recommendations for action and furthermore a possible solution, allowing a better exhaust of potentials, it shall be examined in a scientific research project, which problems occur out of which causes. In the same place, the storage of knowledge from the requirements management, and its later reuse are important, to achieve sustainable improvements of the competitive of the IT-SMEs. Requirements Engineering is one of the most important topics in Product Management for Software to achieve the goal of optimizing the success of the software product. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=ERP" title="ERP">ERP</a>, <a href="https://publications.waset.org/search?q=Requirements%20Management" title=" Requirements Management"> Requirements Management</a> </p> <a href="https://publications.waset.org/13428/requirements-management-as-a-competitive-factor-in-the-it-mid-tier-business-concerning-the-implementation-of-erp-software" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/13428/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/13428/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/13428/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/13428/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/13428/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/13428/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/13428/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/13428/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/13428/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/13428/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/13428.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">1139</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1039</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/search?q=Dagmar%20Monett">Dagmar Monett</a>, <a href="https://publications.waset.org/search?q=Sven-Erik%20Kujat"> Sven-Erik Kujat</a>, <a href="https://publications.waset.org/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/search?q=CASE%20tool" title="CASE tool">CASE tool</a>, <a href="https://publications.waset.org/search?q=collaborative%20learning" title=" collaborative learning"> collaborative learning</a>, <a href="https://publications.waset.org/search?q=requirements%0D%0Aengineering" title=" requirements engineering"> requirements engineering</a>, <a href="https://publications.waset.org/search?q=undergraduate%20teaching." title=" undergraduate teaching."> undergraduate teaching.</a> </p> <a href="https://publications.waset.org/10004192/teaching-students-collaborative-requirements-engineering-case-study-of-redwire" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/10004192/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10004192/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10004192/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10004192/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10004192/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10004192/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10004192/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10004192/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10004192/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10004192/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10004192.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">1351</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1038</span> Moving From Problem Space to Solution Space</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Bilal%20Saeed%20Raja">Bilal Saeed Raja</a>, <a href="https://publications.waset.org/search?q=M.%20Ali%20Iqbal"> M. Ali Iqbal</a>, <a href="https://publications.waset.org/search?q=Imran%20Ihsan"> Imran Ihsan</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Extracting and elaborating software requirements and transforming them into viable software architecture are still an intricate task. This paper defines a solution architecture which is based on the blurred amalgamation of problem space and solution space. The dependencies between domain constraints, requirements and architecture and their importance are described that are to be considered collectively while evolving from problem space to solution space. This paper proposes a revised version of Twin Peaks Model named Win Peaks Model that reconciles software requirements and architecture in more consistent and adaptable manner. Further the conflict between stakeholders- win-requirements is resolved by proposed Voting methodology that is simple adaptation of win-win requirements negotiation model and QARCC. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Functional%20Requirements" title="Functional Requirements">Functional Requirements</a>, <a href="https://publications.waset.org/search?q=Non%20Functional%0ARequirements" title=" Non Functional Requirements"> Non Functional Requirements</a>, <a href="https://publications.waset.org/search?q=Twin%20Peaks%20Model" title=" Twin Peaks Model"> Twin Peaks Model</a>, <a href="https://publications.waset.org/search?q=QARCC." title=" QARCC."> QARCC.</a> </p> <a href="https://publications.waset.org/2068/moving-from-problem-space-to-solution-space" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/2068/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/2068/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/2068/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/2068/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/2068/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/2068/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/2068/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/2068/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/2068/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/2068/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/2068.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">1862</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1037</span> Detecting Interactions between Behavioral Requirements with OWL and SWRL</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Haibo%20Hu">Haibo Hu</a>, <a href="https://publications.waset.org/search?q=Dan%20Yang"> Dan Yang</a>, <a href="https://publications.waset.org/search?q=Chunxiao%20Ye"> Chunxiao Ye</a>, <a href="https://publications.waset.org/search?q=Chunlei%20Fu"> Chunlei Fu</a>, <a href="https://publications.waset.org/search?q=Ren%20Li"> Ren Li</a> </p> <p class="card-text"><strong>Abstract:</strong></p> High quality requirements analysis is one of the most crucial activities to ensure the success of a software project, so that requirements verification for software system becomes more and more important in Requirements Engineering (RE) and it is one of the most helpful strategies for improving the quality of software system. Related works show that requirement elicitation and analysis can be facilitated by ontological approaches and semantic web technologies. In this paper, we proposed a hybrid method which aims to verify requirements with structural and formal semantics to detect interactions. The proposed method is twofold: one is for modeling requirements with the semantic web language OWL, to construct a semantic context; the other is a set of interaction detection rules which are derived from scenario-based analysis and represented with semantic web rule language (SWRL). SWRL based rules are working with rule engines like Jess to reason in semantic context for requirements thus to detect interactions. The benefits of the proposed method lie in three aspects: the method (i) provides systematic steps for modeling requirements with an ontological approach, (ii) offers synergy of requirements elicitation and domain engineering for knowledge sharing, and (3)the proposed rules can systematically assist in requirements interaction detection. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Requirements%20Engineering" title="Requirements Engineering">Requirements Engineering</a>, <a href="https://publications.waset.org/search?q=Semantic%20Web" title=" Semantic Web"> Semantic Web</a>, <a href="https://publications.waset.org/search?q=OWL" title=" OWL"> OWL</a>, <a href="https://publications.waset.org/search?q=Requirements%20Interaction%20Detection" title="Requirements Interaction Detection">Requirements Interaction Detection</a>, <a href="https://publications.waset.org/search?q=SWRL." title=" SWRL."> SWRL.</a> </p> <a href="https://publications.waset.org/2555/detecting-interactions-between-behavioral-requirements-with-owl-and-swrl" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/2555/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/2555/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/2555/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/2555/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/2555/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/2555/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/2555/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/2555/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/2555/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/2555/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/2555.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">1797</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1036</span> Conflicts Identification among Non-functional Requirements using Matrix Maps</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Abdul%20H">Abdul H</a>, <a href="https://publications.waset.org/search?q=Jamil%20A"> Jamil A</a>, <a href="https://publications.waset.org/search?q=Imran%20U"> Imran U</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>Conflicts identification among non-functional requirements is often identified intuitively which impairs conflict analysis practices. This paper proposes a new model to identify conflicts among non-functional requirements. The proposed model uses the matrix mechanism to identify the quality based conflicts among non-functional requirements. The potential conflicts are identified through the mapping of low level conflicting quality attributes to low level functionalities using the matrices. The proposed model achieves the identification of conflicts among product and process requirements, identifies false conflicts, decreases the documentation overhead, and maintains transparency of identified conflicts. The attributes are not concomitantly taken into account by current models in practice.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Conflict%20Identification" title="Conflict Identification">Conflict Identification</a>, <a href="https://publications.waset.org/search?q=Matrix%20Maps" title=" Matrix Maps"> Matrix Maps</a>, <a href="https://publications.waset.org/search?q=Non-functional%20Requirements" title=" Non-functional Requirements"> Non-functional Requirements</a>, <a href="https://publications.waset.org/search?q=Requirements%20Analysis" title=" Requirements Analysis"> Requirements Analysis</a>, <a href="https://publications.waset.org/search?q=Software%20Engineering" title=" Software Engineering"> Software Engineering</a> </p> <a href="https://publications.waset.org/10198/conflicts-identification-among-non-functional-requirements-using-matrix-maps" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/10198/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10198/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10198/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10198/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10198/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10198/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10198/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10198/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10198/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10198/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10198.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">2559</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1035</span> Limitations of the Analytic Hierarchy Process Technique with Respect to Geographically Distributed Stakeholders</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Azeem%20Ahmad">Azeem Ahmad</a>, <a href="https://publications.waset.org/search?q=Magnus%20Goransson"> Magnus Goransson</a>, <a href="https://publications.waset.org/search?q=Aamir%20Shahzad"> Aamir Shahzad</a> </p> <p class="card-text"><strong>Abstract:</strong></p> The selection of appropriate requirements for product releases can make a big difference in a product success. The selection of requirements is done by different requirements prioritization techniques. These techniques are based on pre-defined and systematic steps to calculate the requirements relative weight. Prioritization is complicated by new development settings, shifting from traditional co-located development to geographically distributed development. Stakeholders, connected to a project, are distributed all over the world. These geographically distributions of stakeholders make it hard to prioritize requirements as each stakeholder have their own perception and expectations of the requirements in a software project. This paper discusses limitations of the Analytical Hierarchy Process with respect to geographically distributed stakeholders- (GDS) prioritization of requirements. This paper also provides a solution, in the form of a modified AHP, in order to prioritize requirements for GDS. We will conduct two experiments in this paper and will analyze the results in order to discuss AHP limitations with respect to GDS. The modified AHP variant is also validated in this paper. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Requirements%20Prioritization" title="Requirements Prioritization">Requirements Prioritization</a>, <a href="https://publications.waset.org/search?q=GeographicallyDistributed%20Stakeholders" title=" GeographicallyDistributed Stakeholders"> GeographicallyDistributed Stakeholders</a>, <a href="https://publications.waset.org/search?q=AHP" title=" AHP"> AHP</a>, <a href="https://publications.waset.org/search?q=Modified%20AHP." title=" Modified AHP."> Modified AHP.</a> </p> <a href="https://publications.waset.org/8781/limitations-of-the-analytic-hierarchy-process-technique-with-respect-to-geographically-distributed-stakeholders" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/8781/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/8781/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/8781/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/8781/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/8781/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/8781/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/8781/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/8781/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/8781/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/8781/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/8781.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">2864</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1034</span> ReSeT : Reverse Engineering System Requirements Tool</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Rosziati%20Ibrahim">Rosziati Ibrahim</a>, <a href="https://publications.waset.org/search?q=Tiu%20Kian%20Yong"> Tiu Kian Yong</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Reverse Engineering is a very important process in Software Engineering. It can be performed backwards from system development life cycle (SDLC) in order to get back the source data or representations of a system through analysis of its structure, function and operation. We use reverse engineering to introduce an automatic tool to generate system requirements from its program source codes. The tool is able to accept the C碌 programming source codes, scan the source codes line by line and parse the codes to parser. Then, the engine of the tool will be able to generate system requirements for that specific program to facilitate reuse and enhancement of the program. The purpose of producing the tool is to help recovering the system requirements of any system when the system requirements document (SRD) does not exist due to undocumented support of the system. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=System%20Requirements" title="System Requirements">System Requirements</a>, <a href="https://publications.waset.org/search?q=Reverse%20Engineering" title=" Reverse Engineering"> Reverse Engineering</a>, <a href="https://publications.waset.org/search?q=SourceCodes." title=" SourceCodes."> SourceCodes.</a> </p> <a href="https://publications.waset.org/9558/reset-reverse-engineering-system-requirements-tool" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/9558/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/9558/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/9558/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/9558/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/9558/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/9558/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/9558/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/9558/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/9558/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/9558/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/9558.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">1674</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1033</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/search?q=Lara%20F.%20Horani">Lara F. Horani</a>, <a href="https://publications.waset.org/search?q=Shurong%20Tong"> Shurong Tong</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Analytic%20hierarchy%20process" title="Analytic hierarchy process">Analytic hierarchy process</a>, <a href="https://publications.waset.org/search?q=green%20product" title=" green product"> green product</a>, <a href="https://publications.waset.org/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/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/10009004/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/10009004/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10009004/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10009004/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10009004/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10009004/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10009004/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10009004/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10009004/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10009004/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10009004/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10009004.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">889</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1032</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/search?q=Kholod%20J.%20Alotaibi">Kholod J. Alotaibi</a>, <a href="https://publications.waset.org/search?q=Andrew%20M.%20Gravell"> Andrew M. Gravell</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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-Centred 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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Requirements%20gathering" title="Requirements gathering">Requirements gathering</a>, <a href="https://publications.waset.org/search?q=Usability" title=" Usability"> Usability</a>, <a href="https://publications.waset.org/search?q=Usage-Centred%20Design." title=" Usage-Centred Design."> Usage-Centred Design.</a> </p> <a href="https://publications.waset.org/9997189/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/9997189/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/9997189/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/9997189/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/9997189/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/9997189/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/9997189/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/9997189/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/9997189/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/9997189/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/9997189/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/9997189.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">1949</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1031</span> Meta-requirements that Model Change</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Gouri%20Prakash">Gouri Prakash</a> </p> <p class="card-text"><strong>Abstract:</strong></p> One of the common problems encountered in software engineering is addressing and responding to the changing nature of requirements. While several approaches have been devised to address this issue, ranging from instilling resistance to changing requirements in order to mitigate impact to project schedules, to developing an agile mindset towards requirements, the approach discussed in this paper is one of conceptualizing the delta in requirement and modeling it, in order to plan a response to it. To provide some context here, change is first formally identified and categorized as either formal change or informal change. While agile methodology facilitates informal change, the approach discussed in this paper seeks to develop the idea of facilitating formal change. To collect, document meta-requirements that represent the phenomena of change would be a pro-active measure towards building a realistic cognition of the requirements entity that can further be harnessed in the software engineering process. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Change%20Management" title="Change Management">Change Management</a>, <a href="https://publications.waset.org/search?q=Agile%20methodology" title=" Agile methodology"> Agile methodology</a>, <a href="https://publications.waset.org/search?q=Metarequirements" title=" Metarequirements"> Metarequirements</a> </p> <a href="https://publications.waset.org/9533/meta-requirements-that-model-change" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/9533/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/9533/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/9533/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/9533/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/9533/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/9533/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/9533/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/9533/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/9533/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/9533/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/9533.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">1543</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1030</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/search?q=Paraskevi%20Theodorou">Paraskevi Theodorou</a>, <a href="https://publications.waset.org/search?q=Apostolos%20Meliones"> Apostolos Meliones</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Accessibility" title="Accessibility">Accessibility</a>, <a href="https://publications.waset.org/search?q=assistive%20mobile%20apps" title=" assistive mobile apps"> assistive mobile apps</a>, <a href="https://publications.waset.org/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/search?q=user%20requirements%20analysis." title=" user requirements analysis."> user requirements analysis.</a> </p> <a href="https://publications.waset.org/10010981/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/10010981/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10010981/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10010981/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10010981/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10010981/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10010981/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10010981/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10010981/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10010981/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10010981/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10010981.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">947</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1029</span> Individual Configuration of Production Control to Suit Requirements</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Ben%20Muenzberg">Ben Muenzberg</a>, <a href="https://publications.waset.org/search?q=Prof.%20Peter%20Nyhuis"> Prof. Peter Nyhuis</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>The logistical requirements placed on industrial manufacturing companies are steadily increasing. In order to meet those requirements, a consistent and efficient concept is necessary for production control. Set up properly, production control offers considerable potential with respect to achieving the logistical targets. As experience with the many production control methods already in existence and their compatibility is, however, often inadequate, this article describes a systematic approach to the configuration of production control based on the Lödding model. This model enables production control to be set up individually to suit a company and the requirements. It therefore permits today-s demands regarding logistical performance to be met.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Production" title="Production">Production</a>, <a href="https://publications.waset.org/search?q=planning" title=" planning"> planning</a>, <a href="https://publications.waset.org/search?q=control" title=" control"> control</a>, <a href="https://publications.waset.org/search?q=configuration." title=" configuration."> configuration.</a> </p> <a href="https://publications.waset.org/10242/individual-configuration-of-production-control-to-suit-requirements" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/10242/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10242/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10242/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10242/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10242/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10242/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10242/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10242/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10242/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10242/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10242.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">1624</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1028</span> Development of Non-functional Requirements for Decision Support Systems</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Kassem%20Saleh">Kassem Saleh</a> </p> <p class="card-text"><strong>Abstract:</strong></p> Decision Support System (DSS) are interactive software systems that are built to assist the management of an organization in the decision making process when faced with nonroutine problems in a specific application domain. Non-functional requirements (NFRs) for a DSS deal with the desirable qualities and restrictions that the DSS functionalities must satisfy. Unlike the functional requirements, which are tangible functionalities provided by the DSS, NFRs are often hidden and transparent to DSS users but affect the quality of the provided functionalities. NFRs are often overlooked or added later to the system in an ad hoc manner, leading to a poor overall quality of the system. In this paper, we discuss the development of NFRs as part of the requirements engineering phase of the system development life cycle of DSSs. To help eliciting NFRs, we provide a comprehensive taxonomy of NFRs for DSSs. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Decision%20support%20system" title="Decision support system">Decision support system</a>, <a href="https://publications.waset.org/search?q=Development" title=" Development"> Development</a>, <a href="https://publications.waset.org/search?q=Elicitation" title=" Elicitation"> Elicitation</a>, <a href="https://publications.waset.org/search?q=Non-functional%20requirements" title=" Non-functional requirements"> Non-functional requirements</a>, <a href="https://publications.waset.org/search?q=Taxonomy" title=" Taxonomy"> Taxonomy</a> </p> <a href="https://publications.waset.org/8218/development-of-non-functional-requirements-for-decision-support-systems" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/8218/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/8218/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/8218/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/8218/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/8218/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/8218/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/8218/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/8218/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/8218/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/8218/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/8218.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">2469</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1027</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/search?q=K.%20Adu%20Michael">K. Adu Michael</a>, <a href="https://publications.waset.org/search?q=K.%20Alese%20Boniface"> K. Alese Boniface </a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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 <em>‘what’</em> 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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Client%2FCustomer" title="Client/Customer">Client/Customer</a>, <a href="https://publications.waset.org/search?q=Problem%20Statement" title=" Problem Statement"> Problem Statement</a>, <a href="https://publications.waset.org/search?q=Requirements%20Engineering" title=" Requirements Engineering"> Requirements Engineering</a>, <a href="https://publications.waset.org/search?q=Software%20Developers." title=" Software Developers."> Software Developers.</a> </p> <a href="https://publications.waset.org/9999244/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/9999244/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/9999244/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/9999244/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/9999244/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/9999244/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/9999244/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/9999244/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/9999244/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/9999244/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/9999244/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/9999244.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">2456</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1026</span> An Automation of Check Focusing on CRUD for Requirements Analysis Model in UML</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Shinpei%20Ogata">Shinpei Ogata</a>, <a href="https://publications.waset.org/search?q=Yoshitaka%20Aoki"> Yoshitaka Aoki</a>, <a href="https://publications.waset.org/search?q=Hirotaka%20Okuda"> Hirotaka Okuda</a>, <a href="https://publications.waset.org/search?q=Saeko%20Matsuura"> Saeko Matsuura</a> </p> <p class="card-text"><strong>Abstract:</strong></p> A key to success of high quality software development is to define valid and feasible requirements specification. We have proposed a method of model-driven requirements analysis using Unified Modeling Language (UML). The main feature of our method is to automatically generate a Web user interface mock-up from UML requirements analysis model so that we can confirm validity of input/output data for each page and page transition on the system by directly operating the mock-up. This paper proposes a support method to check the validity of a data life cycle by using a model checking tool 鈥淯PPAAL" focusing on CRUD (Create, Read, Update and Delete). Exhaustive checking improves the quality of requirements analysis model which are validated by the customers through automatically generated mock-up. The effectiveness of our method is discussed by a case study of requirements modeling of two small projects which are a library management system and a supportive sales system for text books in a university. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=CRUD" title="CRUD">CRUD</a>, <a href="https://publications.waset.org/search?q=Model%20Checking" title=" Model Checking"> Model Checking</a>, <a href="https://publications.waset.org/search?q=Model%20Driven%0ADevelopment" title=" Model Driven Development"> Model Driven Development</a>, <a href="https://publications.waset.org/search?q=Requirements%20Analysis" title=" Requirements Analysis"> Requirements Analysis</a>, <a href="https://publications.waset.org/search?q=Unified%20Modeling%20Language" title=" Unified Modeling Language"> Unified Modeling Language</a>, <a href="https://publications.waset.org/search?q=UPPAAL." title=" UPPAAL."> UPPAAL.</a> </p> <a href="https://publications.waset.org/7058/an-automation-of-check-focusing-on-crud-for-requirements-analysis-model-in-uml" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/7058/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/7058/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/7058/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/7058/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/7058/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/7058/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/7058/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/7058/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/7058/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/7058/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/7058.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">1673</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1025</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/search?q=Laleh%20Taheri">Laleh Taheri</a>, <a href="https://publications.waset.org/search?q=Noraini%20C.%20Pa."> Noraini C. Pa.</a>, <a href="https://publications.waset.org/search?q=Rusli%20Abdullah"> Rusli Abdullah</a>, <a href="https://publications.waset.org/search?q=Salfarina%20Abdullah"> Salfarina Abdullah</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p class="Abstract" style="text-indent:10.2pt">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.<span style="font-size: 10pt; color: red;"><o:p></o:p></span></p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Knowledge%20Audit" title="Knowledge Audit">Knowledge Audit</a>, <a href="https://publications.waset.org/search?q=Requirement%20Elicitation%20Process" title=" Requirement Elicitation Process"> Requirement Elicitation Process</a>, <a href="https://publications.waset.org/search?q=KA%20Model" title=" KA Model"> KA Model</a>, <a href="https://publications.waset.org/search?q=Knowledge%20in%20Requirement%20Elicitation." title=" Knowledge in Requirement Elicitation."> Knowledge in Requirement Elicitation.</a> </p> <a href="https://publications.waset.org/9997397/knowledge-audit-model-for-requirement-elicitation-process" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/9997397/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/9997397/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/9997397/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/9997397/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/9997397/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/9997397/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/9997397/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/9997397/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/9997397/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/9997397/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/9997397.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">2901</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1024</span> The Influence of EU Regulation of Margin Requirements on Market Stock Volatility</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Nadira%20Kaimova">Nadira Kaimova</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>In this paper it was examined the influence of margin regulation on stock market volatility in EU 1993 – 2014. Regulating margin requirements or haircuts for securities financing transactions has for a long time been considered as a potential tool to limit the build-up of leverage and dampen volatility in financial markets. The margin requirement dictates how much investors can borrow against these securities. Margin can be an important part of investment. Using daily and monthly stock returns and there is no convincing evidence that EU Regulation margin requirements have served to dampen stock market volatility. In this paper was detected the expected negative relation between margin requirements and the amount of margin credit outstanding. Also, it confirmed that changes in margin requirements by the EU regulation have tended to follow than lead changes in market volatility. For the analysis have been used the modified Levene statistics to test whether the standard deviation of stock returns in the 25, 50 and 100 days preceding margin changes is the same as that in the succeeding 25, 50 and 100 days. The analysis started in May 1993 when it was first empowered to set the initial margin requirement and the last sample was in May 2014. To test whether margin requirements influence stock market volatility over the long term, the sample of stock returns was divided into 14 periods, according to the 14 changes in margin requirements.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Levene%20statistic" title="Levene statistic">Levene statistic</a>, <a href="https://publications.waset.org/search?q=Margin%20Regulation" title=" Margin Regulation"> Margin Regulation</a>, <a href="https://publications.waset.org/search?q=Stock%20Market" title=" Stock Market"> Stock Market</a>, <a href="https://publications.waset.org/search?q=Volatility." title=" Volatility."> Volatility.</a> </p> <a href="https://publications.waset.org/9999971/the-influence-of-eu-regulation-of-margin-requirements-on-market-stock-volatility" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/9999971/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/9999971/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/9999971/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/9999971/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/9999971/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/9999971/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/9999971/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/9999971/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/9999971/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/9999971/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/9999971.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">2154</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1023</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/search?q=Fayez%20Mostafa%20Alhamoui">Fayez Mostafa Alhamoui</a>, <a href="https://publications.waset.org/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 subnetworks 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/search?q=Wireless%20sensor%20networks" title="Wireless sensor networks">Wireless sensor networks</a>, <a href="https://publications.waset.org/search?q=routing%20protocols" title=" routing protocols"> routing protocols</a>, <a href="https://publications.waset.org/search?q=ad%20hoc%0D%0Atopology" title=" ad hoc topology"> ad hoc topology</a>, <a href="https://publications.waset.org/search?q=cluster" title=" cluster"> cluster</a>, <a href="https://publications.waset.org/search?q=sub-network" title=" sub-network"> sub-network</a>, <a href="https://publications.waset.org/search?q=WSN%20design%20requirements." title=" WSN design requirements."> WSN design requirements.</a> </p> <a href="https://publications.waset.org/10002590/adaptive-routing-protocol-for-dynamic-wireless-sensor-networks" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/10002590/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10002590/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10002590/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10002590/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10002590/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10002590/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10002590/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10002590/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10002590/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10002590/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10002590.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">1964</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1022</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/search?q=Porntip%20Ruengtam">Porntip Ruengtam</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Elderly" title="Elderly">Elderly</a>, <a href="https://publications.waset.org/search?q=environmental%20design" title=" environmental design"> environmental design</a>, <a href="https://publications.waset.org/search?q=residential%20community" title=" residential community"> residential community</a>, <a href="https://publications.waset.org/search?q=structural%20equation%20modeling." title=" structural equation modeling."> structural equation modeling.</a> </p> <a href="https://publications.waset.org/10007310/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/10007310/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10007310/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10007310/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10007310/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10007310/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10007310/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10007310/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10007310/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10007310/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10007310/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10007310.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">905</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1021</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/search?q=Aitana%20Alonso-Nogueira">Aitana Alonso-Nogueira</a>, <a href="https://publications.waset.org/search?q=Helia%20Est%C3%A9vez-Fern%C3%A1ndez"> Helia Est茅vez-Fern谩ndez</a>, <a href="https://publications.waset.org/search?q=Isa%C3%ADas%20Garc%C3%ADa"> Isa铆as Garc铆a</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Conceptual%20modeling" title="Conceptual modeling">Conceptual modeling</a>, <a href="https://publications.waset.org/search?q=JSON" title=" JSON"> JSON</a>, <a href="https://publications.waset.org/search?q=NoSQL%20databases" title=" NoSQL databases"> NoSQL databases</a>, <a href="https://publications.waset.org/search?q=requirements%20engineering" title=" requirements engineering"> requirements engineering</a>, <a href="https://publications.waset.org/search?q=software%20development." title=" software development. "> software development. </a> </p> <a href="https://publications.waset.org/10006592/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/10006592/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10006592/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10006592/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10006592/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10006592/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10006592/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10006592/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10006592/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10006592/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10006592/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10006592.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">1082</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1020</span> How Prior Knowledge Affects User's Understanding of System Requirements?</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Balsam%20Mustafa">Balsam Mustafa</a>, <a href="https://publications.waset.org/search?q=Safaai%20Deris"> Safaai Deris</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>Requirements are critical to system validation as they guide all subsequent stages of systems development. Inadequately specified requirements generate systems that require major revisions or cause system failure entirely. Use Cases have become the main vehicle for requirements capture in many current Object Oriented (OO) development methodologies, and a means for developers to communicate with different stakeholders. In this paper we present the results of a laboratory experiment that explored whether different types of use case format are equally effective in facilitating high knowledge user-s understanding. Results showed that the provision of diagrams along with the textual use case descriptions significantly improved user comprehension of system requirements in both familiar and unfamiliar application domains. However, when comparing groups that received models of textual description accompanied with diagrams of different level of details (simple and detailed) we found no significant difference in performance.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Prior%20knowledge" title="Prior knowledge">Prior knowledge</a>, <a href="https://publications.waset.org/search?q=requirement%20specification" title=" requirement specification"> requirement specification</a>, <a href="https://publications.waset.org/search?q=usecase%20format" title=" usecase format"> usecase format</a>, <a href="https://publications.waset.org/search?q=user%20understanding." title=" user understanding."> user understanding.</a> </p> <a href="https://publications.waset.org/4046/how-prior-knowledge-affects-users-understanding-of-system-requirements" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/4046/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/4046/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/4046/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/4046/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/4046/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/4046/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/4046/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/4046/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/4046/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/4046/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/4046.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">1239</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1019</span> Bandwidth allocation in ATM Network for different QOS Requirements</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=H.%20El-Madbouly">H. El-Madbouly</a> </p> <p class="card-text"><strong>Abstract:</strong></p> For future Broad band ISDN, Asynchronous Transfer Mode (ATM) is designed not only to support a wide range of traffic classes with diverse flow characteristics, but also to guarantee the different quality of service QOS requirements. The QOS may be measured in terms of cell loss probability and maximum cell delay. In this paper, ATM networks in which the virtual path (VP) concept is implemented are considered. By applying the Markov Deterministic process method, an efficient algorithm to compute the minimum capacity required to satisfy the QOS requirements when multiple classes of on-off are multiplexed on to a single VP. Using the result, we then proposed a simple algorithm to determine different combinations of VP to achieve the optimum of the total capacity required for satisfying the individual QOS requirements (loss- delay). <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Bandwidth%20allocation" title="Bandwidth allocation">Bandwidth allocation</a>, <a href="https://publications.waset.org/search?q=Quality%20of%20services" title=" Quality of services"> Quality of services</a>, <a href="https://publications.waset.org/search?q=ATMNetwork" title=" ATMNetwork"> ATMNetwork</a>, <a href="https://publications.waset.org/search?q=virtual%20path." title=" virtual path."> virtual path.</a> </p> <a href="https://publications.waset.org/15215/bandwidth-allocation-in-atm-network-for-different-qos-requirements" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/15215/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/15215/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/15215/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/15215/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/15215/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/15215/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/15215/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/15215/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/15215/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/15215/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/15215.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">1556</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1018</span> Requirements and Guidelines for the Design of Team Awareness Systems</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Carsten%20R%C3%B6cker">Carsten R枚cker</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper presents a set of guidelines for the design of multi-user awareness systems. In a first step, general requirements for team awareness systems are analyzed. In the second part of the paper, the identified requirements are aggregated and transformed into concrete design guidelines for the development of team awareness systems. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=User%20Interface%20Design" title="User Interface Design">User Interface Design</a>, <a href="https://publications.waset.org/search?q=Awareness%20Systems" title=" Awareness Systems"> Awareness Systems</a>, <a href="https://publications.waset.org/search?q=User-%0ACentered%20Design" title=" User- Centered Design"> User- Centered Design</a>, <a href="https://publications.waset.org/search?q=Human%20Factors." title=" Human Factors."> Human Factors.</a> </p> <a href="https://publications.waset.org/4502/requirements-and-guidelines-for-the-design-of-team-awareness-systems" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/4502/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/4502/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/4502/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/4502/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/4502/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/4502/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/4502/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/4502/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/4502/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/4502/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/4502.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">1496</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1017</span> Testing Database of Information System using Conceptual Modeling</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=Bogdan%20Walek">Bogdan Walek</a>, <a href="https://publications.waset.org/search?q=Cyril%20Klimes"> Cyril Klimes</a> </p> <p class="card-text"><strong>Abstract:</strong></p> This paper focuses on testing database of existing information system. At the beginning we describe the basic problems of implemented databases, such as data redundancy, poor design of database logical structure or inappropriate data types in columns of database tables. These problems are often the result of incorrect understanding of the primary requirements for a database of an information system. Then we propose an algorithm to compare the conceptual model created from vague requirements for a database with a conceptual model reconstructed from implemented database. An algorithm also suggests steps leading to optimization of implemented database. The proposed algorithm is verified by an implemented prototype. The paper also describes a fuzzy system which works with the vague requirements for a database of an information system, procedure for creating conceptual from vague requirements and an algorithm for reconstructing a conceptual model from implemented database. <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=testing" title="testing">testing</a>, <a href="https://publications.waset.org/search?q=database" title=" database"> database</a>, <a href="https://publications.waset.org/search?q=relational%20database" title=" relational database"> relational database</a>, <a href="https://publications.waset.org/search?q=information%0Asystem" title=" information system"> information system</a>, <a href="https://publications.waset.org/search?q=conceptual%20model" title=" conceptual model"> conceptual model</a>, <a href="https://publications.waset.org/search?q=fuzzy" title=" fuzzy"> fuzzy</a>, <a href="https://publications.waset.org/search?q=uncertain%20information" title=" uncertain information"> uncertain information</a>, <a href="https://publications.waset.org/search?q=database%0Atesting" title=" database testing"> database testing</a>, <a href="https://publications.waset.org/search?q=reconstruction" title=" reconstruction"> reconstruction</a>, <a href="https://publications.waset.org/search?q=requirements" title=" requirements"> requirements</a>, <a href="https://publications.waset.org/search?q=optimization" title=" optimization"> optimization</a> </p> <a href="https://publications.waset.org/7241/testing-database-of-information-system-using-conceptual-modeling" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/7241/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/7241/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/7241/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/7241/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/7241/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/7241/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/7241/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/7241/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/7241/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/7241/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/7241.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">1445</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1016</span> Requirements Driven Multiple View Paradigm for Developing Security Architecture</h5> <div class="card-body"> <p class="card-text"><strong>Authors:</strong> <a href="https://publications.waset.org/search?q=K.%20Chandra%20Sekaran">K. Chandra Sekaran</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <p>This paper describes a paradigmatic approach to develop architecture of secure systems by describing the requirements from four different points of view: that of the owner, the administrator, the user, and the network. Deriving requirements and developing architecture implies the joint elicitation and describing the problem and the structure of the solution. The view points proposed in this paper are those we consider as requirements towards their contributions as major parties in the design, implementation, usage and maintenance of secure systems. The dramatic growth of the technology of Internet and the applications deployed in World Wide Web have lead to the situation where the security has become a very important concern in the development of secure systems. Many security approaches are currently being used in organizations. In spite of the widespread use of many different security solutions, the security remains a problem. It is argued that the approach that is described in this paper for the development of secure architecture is practical by all means. The models representing these multiple points of view are termed the requirements model (views of owner and administrator) and the operations model (views of user and network). In this paper, this multiple view paradigm is explained by first describing the specific requirements and or characteristics of secure systems (particularly in the domain of networks) and the secure architecture / system development methodology.</p> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Multiple%20view%20paradigms" title="Multiple view paradigms">Multiple view paradigms</a>, <a href="https://publications.waset.org/search?q=requirements%20model" title=" requirements model"> requirements model</a>, <a href="https://publications.waset.org/search?q=operations%20model" title=" operations model"> operations model</a>, <a href="https://publications.waset.org/search?q=secure%20system" title=" secure system"> secure system</a>, <a href="https://publications.waset.org/search?q=owner" title=" owner"> owner</a>, <a href="https://publications.waset.org/search?q=administrator" title=" administrator"> administrator</a>, <a href="https://publications.waset.org/search?q=user" title=" user"> user</a>, <a href="https://publications.waset.org/search?q=network." title=" network."> network.</a> </p> <a href="https://publications.waset.org/12316/requirements-driven-multiple-view-paradigm-for-developing-security-architecture" class="btn btn-primary btn-sm">Procedia</a> <a href="https://publications.waset.org/12316/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/12316/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/12316/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/12316/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/12316/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/12316/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/12316/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/12316/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/12316/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/12316/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/12316.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">1370</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1015</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/search?q=G.%20Sevilla">G. Sevilla</a>, <a href="https://publications.waset.org/search?q=S.%20Zapata"> S. Zapata</a>, <a href="https://publications.waset.org/search?q=F.%20Giraldo"> F. Giraldo</a>, <a href="https://publications.waset.org/search?q=E.%20Torres"> E. Torres</a>, <a href="https://publications.waset.org/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/search?q=Requirements%20analysis" title="Requirements analysis">Requirements analysis</a>, <a href="https://publications.waset.org/search?q=distributed%20requirements%20engineering" title=" distributed requirements engineering"> distributed requirements engineering</a>, <a href="https://publications.waset.org/search?q=practical%20experiences" title=" practical experiences"> practical experiences</a>, <a href="https://publications.waset.org/search?q=collaborative%20support." title=" collaborative support. "> collaborative support. </a> </p> <a href="https://publications.waset.org/10009860/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/10009860/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10009860/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10009860/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10009860/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10009860/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10009860/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10009860/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10009860/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10009860/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10009860/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10009860.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">705</span> </span> </div> </div> <div class="card publication-listing mb-3 mt-3"> <h5 class="card-header" style="font-size:.9rem"><span class="badge badge-info">1014</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/search?q=Lara%20F.%20Horani">Lara F. Horani</a> </p> <p class="card-text"><strong>Abstract:</strong></p> <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> <p class="card-text"><strong>Keywords:</strong> <a href="https://publications.waset.org/search?q=Sustainable%20design" title="Sustainable design">Sustainable design</a>, <a href="https://publications.waset.org/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/search?q=changing%20customer%20requirements%20for%20sustainable%20design" title=" changing customer requirements for sustainable design"> changing customer requirements for sustainable design</a>, <a href="https://publications.waset.org/search?q=systematic%20literature%20reviews." title=" systematic literature reviews."> systematic literature reviews.</a> </p> <a href="https://publications.waset.org/10007064/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/10007064/apa" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">APA</a> <a href="https://publications.waset.org/10007064/bibtex" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">BibTeX</a> <a href="https://publications.waset.org/10007064/chicago" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Chicago</a> <a href="https://publications.waset.org/10007064/endnote" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">EndNote</a> <a href="https://publications.waset.org/10007064/harvard" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">Harvard</a> <a href="https://publications.waset.org/10007064/json" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">JSON</a> <a href="https://publications.waset.org/10007064/mla" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">MLA</a> <a href="https://publications.waset.org/10007064/ris" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">RIS</a> <a href="https://publications.waset.org/10007064/xml" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">XML</a> <a href="https://publications.waset.org/10007064/iso690" target="_blank" rel="nofollow" class="btn btn-primary btn-sm">ISO 690</a> <a href="https://publications.waset.org/10007064.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">1481</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/search?q=Requirements&page=2">2</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=3">3</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=4">4</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=5">5</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=6">6</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=7">7</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=8">8</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=9">9</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/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/search?q=Requirements&page=34">34</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/search?q=Requirements&page=35">35</a></li> <li class="page-item"><a class="page-link" href="https://publications.waset.org/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>