To see the other types of publications on this topic, follow the link: Requirement elicitation model.
Journal articles on the topic 'Requirement elicitation model'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 journal articles for your research on the topic 'Requirement elicitation model.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.
1
Muhammad, Yaseen, and Farooq Umar. "Requirement Elicitation Model (REM) in the Context of Global Software Development." International Journal of Advances in Applied Sciences (IJAAS) 7, no. 3 (2018): 303–8. https://doi.org/10.11591/ijaas.v7.i3.pp303-308.
Full textAbstract:
Contxext:Requirement elicitation is difficult and critical phase of requirement engineering and the case is worst in global software development (GSD). The study is about requirement elicitation in the context of GSD. Objective: Development of requirement elicitation model (REM) which can address the factors that have positive impact and the factors that have negative impact during elicitation in GSD. The propose model will give solutions and practices to the challenges during elicitation. Method: Systematic literature review (SLR) and empirical research study will be used for achieving the goals and objectives. Expected outcomes: The expected results of this study will be REM that will help vendor organizations for better elicitation during GSD.
2
Yaseen, Muhammad, and Umar Farooq. "Requirement Elicitation Model (REM) in the Context of Global Software Development." International Journal of Advances in Applied Sciences 7, no. 3 (2018): 303. http://dx.doi.org/10.11591/ijaas.v7.i3.pp303-308.
Full textAbstract:
<p>Requirement elicitation is difficult and critical phase of requirement engineering and the case is worst in global software development (GSD). The study is about requirement elicitation in the context of GSD. Development of requirement elicitation model (REM) which can address the factors that have positive impact and the factors that have negative impact during elicitation in GSD. The propose model will give solutions and practices to the challenges during elicitation. Systematic literature review (SLR) and empirical research study will be used for achieving the goals and objectives. The expected results of this study will be REM that will help vendor organizations for better elicitation during GSD.</p>
3
Barefah, Allaa, and Maryam Altalhi. "Exploring the Critical Benefits and Challenges of Social Network Site-Based Requirement Elicitation in Saudi Arabia." Sustainability 16, no. 22 (2024): 9794. http://dx.doi.org/10.3390/su16229794.
Full textAbstract:
The digital transformation and proliferation of social network sites (SNSs) have created new opportunities to consider digital sources to support the development of software systems. Social network sites (SNSs), such as Twitter and Facebook, can be major sources used during the process of requirement elicitation to identify and extract users’ requirements. The primary objective of SNS-based requirement elicitation is to overcome the limitations of the traditional requirement elicitation methods. However, these valued resources for requirement elicitation are yet to be fully exploited. Software products might not fulfill users’ needs owing to the numerous challenges in processing the data effectively. This study aims to explore the actual use, benefits, and challenges of SNS-based requirement elicitation. Twenty-five practitioners in the software companies in Saudi Arabia were interviewed, and thematic analysis was conducted on the interview data. With the application of the TOE model, five critical benefits and nine challenges were identified and classified into technological, organizational, and environmental contexts. The findings of this study offer valuable implications for researchers and practitioners by providing fine-grained details about the adoption of SNS-based requirement elicitation that could eventually facilitate its implementation effectively.
4
Oladapo, Adeboye Popoola, Ejiga Adama Henry, David Okeke Chukwuekem, and Emmanuel Akinoso Abiodun. "Advancements and innovations in requirements elicitation: Developing a comprehensive conceptual model." World Journal of Advanced Research and Reviews 22, no. 1 (2024): 1209–20. https://doi.org/10.5281/zenodo.14215284.
Full textAbstract:
Requirements elicitation is a crucial phase in the software development lifecycle, ensuring that stakeholders' needs are understood and translated into system specifications. Traditional methods often face challenges such as ambiguity, inconsistency, and evolving requirements, leading to project delays and cost overruns. This review proposes a conceptual model that integrates advancements and innovations in requirements elicitation to address these challenges comprehensively. The proposed model leverages various techniques, including but not limited to, natural language processing (NLP), machine learning (ML), and human-computer interaction (HCI), to enhance the accuracy and efficiency of requirements elicitation. NLP techniques enable automated analysis of textual requirements documents, extracting key information and identifying implicit requirements. ML algorithms facilitate the prediction of potential changes in requirements based on historical data and project context, enabling proactive management of evolving requirements. Moreover, the integration of HCI principles in the requirements elicitation process enhances stakeholder engagement and collaboration. Interactive interfaces and visualization tools enable stakeholders to provide feedback in real-time, fostering a more iterative and participatory approach to requirement gathering. Additionally, techniques such as prototyping and simulation facilitate early validation of requirements, reducing the risk of misinterpretation and ensuring alignment with stakeholders' expectations. Furthermore, the proposed model emphasizes the importance of context-awareness in requirements elicitation. By considering the organizational, cultural, and environmental context of a project, the model adapts its elicitation strategies and techniques to suit specific needs and constraints. Context-awareness also enables the identification of implicit requirements that may not be explicitly stated but are crucial for the success of the system. The model also addresses the challenge of managing conflicting requirements by introducing a systematic approach to requirements prioritization and negotiation. By employing multi-criteria decision-making techniques, stakeholders can collaboratively prioritize requirements based on their importance, feasibility, and impact on project objectives. Conflict resolution mechanisms facilitate consensus-building and trade-off analysis, ensuring that the final set of requirements reflects the collective interests of all stakeholders. Additionally, the proposed model emphasizes the iterative nature of requirements elicitation, advocating for continuous refinement and validation of requirements throughout the development lifecycle. Feedback loops enable stakeholders to review and revise requirements based on evolving needs and changing circumstances, thereby enhancing the adaptability and resilience of the system. The conceptual model presented in this review represents a holistic approach to requirements elicitation, leveraging advancements and innovations in technology, human interaction, and context-awareness. By integrating these elements, the model aims to enhance the accuracy, efficiency, and stakeholder satisfaction in the requirements elicitation process, ultimately contributing to the successful delivery of high-quality software systems.
5
Dafaalla, Hatim, Mohammed Abaker, Abdelzahir Abdelmaboud, et al. "Deep Learning Model for Selecting Suitable Requirements Elicitation Techniques." Applied Sciences 12, no. 18 (2022): 9060. http://dx.doi.org/10.3390/app12189060.
Full textAbstract:
Requirement elicitation represents one of the most vital phases in information system (IS) and software development projects. Selecting suitable elicitation techniques is critical for eliciting the correct specification in various projects. Recent studies have revealed that improper novice practices in this phase have increased the failure rate in both IS and software development projects. Previous research has primarily relied on creating procedural systems based on contextual studies of elicitation properties. In contrast, this paper introduces a deep learning model for selecting suitable requirement elicitation. An experiment was conducted wherein a collected dataset of 1684 technique selection attributes were investigate with respect to 14 elicitation techniques. The study adopted seven criteria to evaluate predictive model performance using confusion matrix accuracy, precision, recall, F1 Score, and area under the ROC curve (AUC) and loss curve. The model scored prediction accuracy of 82%, precision score of 0.83, recall score of 0.83, F1 score of 0.82, cross-validation score of 0.82 (± 0.10), One-vs-One ROC AUC score of 0.74, and One-vs-Rest ROC AUC score of 0.75 for each label. Our results indicate the model’s high prediction ability. The model provides a robust decision-making process for delivering correct elicitation techniques and lowering the risk of project failure. The implications of this study can be used to promote the automatization of the elicitation technique selection process, thereby enhancing current required elicitation industry practices.
6
Taheri, Laleh, Mohammad Yasser Shafazand, Noraini Che Pa, Rusli Abdullah, and Salfarina Abdullah. "A knowledge audit model for requirement elicitation: A case study to assess knowledge in requirement elicitation." Knowledge and Process Management 24, no. 4 (2017): 257–68. http://dx.doi.org/10.1002/kpm.1553.
Full text
7
Nasim, Sharoon, Zainab Zahid, and Nosheen Sabahat. "Requirement Elicitation using Natural Language Processing." Lahore Garrison University Research Journal of Computer Science and Information Technology 7, no. 01 (2023): 1–6. http://dx.doi.org/10.54692/lgurjcsit.2023.0701316.
Full textAbstract:
—This paper is the outcome of the research conductedto investigate the affective requirement engineering techniquesproposed and used for developing software projects. We haveassessed traditional methods and proposed an approach thatcovers various aspects for generating a successful project. AnNLP-based model is designed that takes input from the user andgives the output in the form of a text document after processingit. We have set a 62% similarity index to achieve the maximumrequirements of the required system. These requirements, inreturn, help the developers to develop the product with morefunctionality and productivity.
8
Fan, Zhi Jun, and Zhao Liang Jiang. "Ontology-Driven Requirements Elicitation Based on Scenario." Advanced Materials Research 542-543 (June 2012): 1459–62. http://dx.doi.org/10.4028/www.scientific.net/amr.542-543.1459.
Full textAbstract:
For the completeness and accuracy of customers' requirements information in the mass customization paradigm, a method of ontology-driven personal requirements elicitation based on scenario was proposed. Firstly, customer scenario model and product requirements model based on ontology theory were constructed respectively. Association rules were mined with Apriori algorithm using the method of metarule. Scenario ontology was mapped to requirement ontology completely. Then, customers' personal requirements information was elicited completely and accurately. Finally, industrial case study has been performed to demonstrate the practicality and effectiveness of the proposed approach.
9
Solovei, Olga, and Denys Gobov. "PARSIMONIOUS MACHINE LEARNING MODELS IN REQUIREMENTS ELICITATION TECHNIQUES SELECTION." Bulletin of National Technical University "KhPI". Series: System Analysis, Control and Information Technologies, no. 1 (9) (July 15, 2023): 82–88. http://dx.doi.org/10.20998/2079-0023.2023.01.13.
Full textAbstract:
The subject of research in the article is machine learning algorithms used for requirement elicitation technique selection. The goal of the work is to build effective parsimonious machine learning models to predict the using particular elicitation techniques in IT projects that allow using as few predictor variables as possible without a significant deterioration in the prediction quality. The following tasks are solved in the article: design an algorithm to build parsimonious machine learning candidate models for requirement elicitation technique selection based on gathered information on practitioners' experience, assess parsimonious machine learning model accuracy, and design an algorithm for the best candidate model selection. The following methods are used: algorithm theory, statistics theory, sampling techniques, data modeling theory, and science experiments. The following results were obtained: 1) parsimonious machine learning candidate models were built for the requirement elicitation technique selection. They included less number of features that helps in the future to avoid overfitting problems associated with the best-fit models; 2) according to the proposed algorithm for best candidate selection – a single parsimonious model with satisfied performance was chosen. Conclusion: An algorithm is proposed to build parsimonious candidate models for requirement elicitation technique selection that avoids the overfitting problem. The algorithm for the best candidate model selection identifies when a parsimonious model's performance is degraded and decides on the suitable model's selection. Both proposed algorithms were successfully tested with four datasets and can be proposed for their extensions to others.
10
Shahidi, Shahwali. "Comparing the effectiveness of conventional and Kano model questionnaire for gathering requirement of online bus reservation system." International Journal of Innovative Research and Scientific Studies 3, no. 1 (2020): 27–32. http://dx.doi.org/10.53894/ijirss.v3i1.30.
Full textAbstract:
Software development is the activity of creating a software system that when used, solves some unsolved problem. It consists many knowledge intensive processes, among which requirement elicitation process is perhaps the most critical for the success of the software system. The success or failure of the system is related to the quality of the elicitation process and to the method used for gathering user needs. This study examines combined approaches to identify and classify the requirements and investigates the importance of customer satisfaction in requirement elicitation for online bus reservation system. The context of this work is University Malaysia Pahang (UMP). The target audiences are public who uses bus services. A total 63 out of 70 questionnaire are answered by the people. To do this, the design of two types of questionnaires: conventional and Kano questionnaire is done and implemented to identify the correct requirements for the selected system and then to compare the effectiveness of these two approaches. This study found that, both conventional method and Kano model are suitable to find and classify the requirements, but for deeper understanding of requirements which have the greatest influence on the customer's satisfaction, Kano model is more effective, because Kano's method provides valuable help when trade-off is needed for designing the product development.
11
Oladapo Adeboye Popoola, Henry Ejiga Adama, Chukwuekem David Okeke, and Abiodun Emmanuel Akinoso. "Advancements and innovations in requirements elicitation: Developing a comprehensive conceptual model." World Journal of Advanced Research and Reviews 22, no. 1 (2024): 1209–20. http://dx.doi.org/10.30574/wjarr.2024.22.1.1202.
Full textAbstract:
Requirements elicitation is a crucial phase in the software development lifecycle, ensuring that stakeholders' needs are understood and translated into system specifications. Traditional methods often face challenges such as ambiguity, inconsistency, and evolving requirements, leading to project delays and cost overruns. This review proposes a conceptual model that integrates advancements and innovations in requirements elicitation to address these challenges comprehensively. The proposed model leverages various techniques, including but not limited to, natural language processing (NLP), machine learning (ML), and human-computer interaction (HCI), to enhance the accuracy and efficiency of requirements elicitation. NLP techniques enable automated analysis of textual requirements documents, extracting key information and identifying implicit requirements. ML algorithms facilitate the prediction of potential changes in requirements based on historical data and project context, enabling proactive management of evolving requirements. Moreover, the integration of HCI principles in the requirements elicitation process enhances stakeholder engagement and collaboration. Interactive interfaces and visualization tools enable stakeholders to provide feedback in real-time, fostering a more iterative and participatory approach to requirement gathering. Additionally, techniques such as prototyping and simulation facilitate early validation of requirements, reducing the risk of misinterpretation and ensuring alignment with stakeholders' expectations. Furthermore, the proposed model emphasizes the importance of context-awareness in requirements elicitation. By considering the organizational, cultural, and environmental context of a project, the model adapts its elicitation strategies and techniques to suit specific needs and constraints. Context-awareness also enables the identification of implicit requirements that may not be explicitly stated but are crucial for the success of the system. The model also addresses the challenge of managing conflicting requirements by introducing a systematic approach to requirements prioritization and negotiation. By employing multi-criteria decision-making techniques, stakeholders can collaboratively prioritize requirements based on their importance, feasibility, and impact on project objectives. Conflict resolution mechanisms facilitate consensus-building and trade-off analysis, ensuring that the final set of requirements reflects the collective interests of all stakeholders. Additionally, the proposed model emphasizes the iterative nature of requirements elicitation, advocating for continuous refinement and validation of requirements throughout the development lifecycle. Feedback loops enable stakeholders to review and revise requirements based on evolving needs and changing circumstances, thereby enhancing the adaptability and resilience of the system. The conceptual model presented in this review represents a holistic approach to requirements elicitation, leveraging advancements and innovations in technology, human interaction, and context-awareness. By integrating these elements, the model aims to enhance the accuracy, efficiency, and stakeholder satisfaction in the requirements elicitation process, ultimately contributing to the successful delivery of high-quality software systems.
12
Muqeem, Md. "NVC Based Model for Selecting Effective Requirement Elicitation Technique." International Journal of Software Engineering & Applications 3, no. 5 (2012): 157–65. http://dx.doi.org/10.5121/ijsea.2012.3513.
Full text
13
Sarrab, Mohamed, Youcef Baghdadi, Hafedh Al Shihi, and Hadj Bourdoucen. "A model for mobile learning non-functional requirement elicitation." International Journal of Mobile Learning and Organisation 10, no. 3 (2016): 129. http://dx.doi.org/10.1504/ijmlo.2016.077862.
Full text
14
Faroom, Saeed. "A Review of Requirement Engineering Process Models, Tools & Methodologies." International Journal of Energetica 4, no. 1 (2019): 44. http://dx.doi.org/10.47238/ijeca.v4i1.86.
Full textAbstract:
As we are living in the Era of Computer Science and almost all individuals and the organizations are completely relying on software systems. The requirement engineering is the most vital and important aspect in the success of any software engineering project. Requirement Engineering is a set of different process that works at different levels, which are incorporated at individual and organizational level Projects We need to consult different sources to find requirements. We need to involve personals from the different fields to find a set of quality requirements. The security issues undergoes as soon as early in the 1st phase of requirements. It is shown from the studies that if we consider Quality Process of Requirement Engineering at the phase it results in saving of million dollars. This paper contains the details study and comparison of different RE Process Models and Requirement Elicitation techniques. This paper elaborates the vital aspects of different Requirement Engineering Process models that help in the selection of appropriate model for the Requirement Engineers and practitioners working in the industry. This Paper also Focus on the giving a detailed view of Elicitation techniques and comparative study including the characteristics and their strengths and weakness. Some strengths and weakness found during detailed study are also structured and listed that is also the helpful for the Appropriate selection of RE Process model.
15
Prodanović, Radomir, Dejan Rančić, Ivan Vulić, and Dušan Bogićević. "THE APPROACH TO MEASUREMENT OF REQUIREMENT QUALITY BY APPLICATION OF GENERALIZED PRIORITIZED FUZZY CONSTRAINT SATISFACTION PROBLEM." Facta Universitatis, Series: Automatic Control and Robotics 19, no. 3 (2021): 175. http://dx.doi.org/10.22190/fuacr2003175p.
Full textAbstract:
The requirement quality affects product development at all lifecycle stages, as well as the end product. Poorly defined requirements bring to extended deadlines, increased financial costs, even to project disruption. Current researches related to the good quality of requirements include characteristics of good requirements and the development of new elicitation techniques. Requirement quality evaluation should be tailored both to the professionals and users who defined requirements according to their needs. Therefore, the model is designed for requirement quality measurement based on the characteristics of good requirements by application of the Generalized Prioritized Fuzzy Constraint Satisfaction Problem. The model enables the participation of selected characteristics of good requirements in quality evaluation, according to priorities. The evaluator obtains information if the requirement satisfies the given quality satisfaction threshold based on the degree of fulfillment of selected characteristics of a good requirement. The model is applied to all types of requirements, as well as to the evaluation of requirements at all software development lifecycle stages.
16
Kartiko, Condro, Ariq Cahya Wardhana, and Wahyu Andi Saputra. "Requirements Engineering of Village Innovation Application Using Goal-Oriented Requirements Engineering (GORE)." JURNAL INFOTEL 13, no. 2 (2021): 38–46. http://dx.doi.org/10.20895/infotel.v13i2.602.
Full textAbstract:
The delay in the absorption of village funds from the central government to the village government is due to the village government's difficulty preparing village development innovation programs. The innovation tradition will grow if the cycle of transformation of knowledge and acceptable practices from one village to another, especially villages with similar conditions and problems, can run smoothly. For the process of exchanging knowledge and experiences between villages to run smoothly, it is necessary to codify best practices in a structured, documented, and disseminated manner. This research aims to design an application that functions as a medium for sharing knowledge about the use of village funds through government innovation narratives. The application is expected to become a reference for villages to carry out innovative practices by conducting replication studies and replicating acceptable practices that other villages have done. Therefore, it is necessary to have a system requirements elicitation method that can explore the village's requirements in sharing knowledge so that the resulting system is of high quality and by the objectives of being developed. There are several Goal-Oriented Requirements Engineering (GORE) methods used, such as Knowledge Acquisition in Automated Specification (KAOS) and requirements engineering based on business processes. In this research, the KAOS method was demonstrated as the elicitation activity of a village innovation system. Then the results were stated in the Goal Tree Model (GTM). Model building begins with discussions with the manager of the village innovation program to produce goals. The goals are then broken down into several sub-goals using the KAOS method. The KAOS method is used for the requirements elicitation process resulting in functional and non-functional requirements. This research is the elicitation of the requirement for the village innovation system so that it can demonstrate the initial steps in determining the requirements of the village innovation system before carrying out the design process and the system creation process. The results of this requirement elicitation can be used further in the software engineering process to produce quality and appropriate village innovation applications.
17
Altaf, Sohaib, Asadullah Shah, Najma Imtiaz, Abdul Salaam Shah, and Syed Faiz Ahmed. "Unstructured source artifacts ontology for requirement validation in GDSD." International Journal of Engineering & Technology 7, no. 2.5 (2018): 37. http://dx.doi.org/10.14419/ijet.v7i2.5.10051.
Full textAbstract:
Analyst while transformation, may not capture true representation of user opinion thus creating deviation from actual user needs. Role of stakeholder is primary in both requirement elicitation and validation process. In elicitation stage they are initiator whereas in validation stage they are authenticator of their needs. Invalid requirements if verified may not be a deviation from specified behavior but deviation from user needs. Requirement validation process ensure that requirements should be representing all primary and intermediary artifacts as well a shared opinions of their contributors. This highlights the importance of source artifacts without which requirement validation cannot assured. Researchers didn’t propose any framework for requirement validation in context of GDSD in which source artifacts grows exponentially, and stakeholders are located in diversified locations. Due to unstructured nature of source artifacts, they are not electronically indexed and versioned controlled and this makes difficulty in preserving them. Requirement validation is not possible when source artifacts are not available along with their contributors. The major contribution of this paper to address problem of requirement validation in GDSD in absence of stakeholder to make it collocating environment. This paper introduced ontological solution of requirement validation in which target artifacts are validated against source artifact using their semantic relationship. This paper proposed an unstructured source artifact based ontological model for requirement validation in GDSD environment.
18
Alexa, Lidia, and Silvia Avasilcai. "The requirement elicitation process of designing a collaborative environment – The CRE@TIVE.BIZ case." MATEC Web of Conferences 184 (2018): 04010. http://dx.doi.org/10.1051/matecconf/201818404010.
Full textAbstract:
The software development industry is one that is under a constant pressure to deliver products that are innovative, fast to market and better suited to the costumers’ needs and expectations. In this context, the traditional approaches to product development can become obsolete, as the market and the end-users are dynamic and rather unpredictable and the latter’s active participation can sometimes make the difference between success and failure. The Agile approach, on the other hand considers extensive collaboration with all stakeholders paramount in all the stages of the software development process and for this, a variety of requirements elicitations techniques are used in order to obtain extensive input that leads to designing and developing enhanced products and applications. This paper presents the requirement elicitation process and techniques used in the development process of an open collaboration and innovation platform – CRE@TIVE.BIZ which is an experimental model dedicated to create a community where all relevant stakeholders from three specific creative industries, namely design, fashion design and crafts, can meet, interact, gain access and share information, knowledge and resources.
19
Salleh, Narishah Mohamed, and Puteri N. E. Nohuddin. "Optimization of software requirement process: An integrated conceptual model of lean six sigma and requirement planning." International Review of Applied Sciences and Engineering 10, no. 2 (2019): 125–33. http://dx.doi.org/10.1556/1848.2019.0015.
Full textAbstract:
Providing quality requirements in Software Engineering is vital to ensure the product developed is able to deploy and function to meet the operational objectives. Software Requirement Engineering is the most complex process because it involves the integration of human, logics and process. Extracting or capturing what customers need and want is called Requirement Elicitation (RE) and it is the most crucial process in requirement engineering. If handled poorly, the cost of the failures would be very expensive. Most of the software projects that failed were due to poor requirements which occurred at RE phase. Thus, enhancing and optimizing the RE methods have been subject to a long research debate to ensure quality requirements are captured. Recently, Lean Six Sigma (LSS) had emerged as part of a continuous improvement in Software Development Life Cycles (SDLC). LSS is known for a systematic and structure business improvement successfully deployed in many fields of industry that contributes a significant gain not only in quality of products and services but also in operational costs and delivery. The objective of the research is to develop an integrated conceptual framework of LSS principles with Software Requirement Engineering methodology to optimize RE process. The article will produce conceptual framework as the comprehensive guidelines to capture quality software requirements.
20
Ali Ramdhani, Muhammad, Dian Sa’adillah Maylawati, Abdusy Syakur Amin, and Hilmi Aulawi. "Requirements Elicitation in Software Engineering." International Journal of Engineering & Technology 7, no. 2.29 (2018): 772. http://dx.doi.org/10.14419/ijet.v7i2.29.14254.
Full textAbstract:
Software Engineering (SE) is a discipline, concept, method that focus on all aspects related to software production. SE must adapt organized system and approach in building software. The objective of this article is to discuss needs elicitation in SE, so that the design can be done through utilizing appropriate tools and techniques based on the problem to be solved, restrictions and need that must be met, as well as resource availability. The method used in this article is literature review as a major source of problem analysis. In the next phase, the main topic of the article is clarified, validated, and verified by the model of the Focus Group Discussion (FGD). The respondents of FGD are lecturers of Informatics Department at UIN Sunan Gunung Djati Bandung. Requirements elicitation is in-dept and comprehensive process of finding information from all stakeholders in relation to the built software. The result of requirements elicitation is the explanation from every stakeholder with natural language related to the will and interest of the built software. The mechanism of finding information can be done through observation, questionnaire, interview, and documentary study, which are then tested with data validation and verification in FGD. The product of requirements elicitation is the User Requirement Document (URD) that can be used as an early artifact in software development process. Furthermore, URD is used as a reference in tracking the suitability between the function of software and the needs of stakeholder. This article formulated analysis approach of SE need, so that it is easily modified, adaptive to growing software complexity, and connected with the analysis of hardware.
21
Ali Shah, Syed Osama. "ADVANCED TECHNIQUE FOR REQUIREMENT ANALYSIS OF SOFTWARE PROJECTS." International Journal of Trendy Research in Engineering and Technology 08, no. 05 (2024): 38–41. http://dx.doi.org/10.54473/ijtret.2024.8507.
Full textAbstract:
Following the requirements elicitation activity, the team will then carry out the requirements analysis to identify the requirements that have the potential to cause issues in the future. There are several different approaches to requirement analysis that can be used to determine the specific requirements that may either compete with or overlap with those of other requirements. We can perform requirement analysis in a better and more efficient manner with the help of the mode proposed in this paper. Requirement analysis is an important activity after requirement analysis and a proper mechanism is required to make this activity more precise and efficient. In this paper, we present a model that can be used to perform an analysis of requirements and highlight those that overlap with or are in direct opposition to the requirements of another requirement. Any requirements that are incompatible with one another or that overlap will be called out. Following the calculation of the overlapping and conflicting fitness of each of the requirements. we will be able to identify all the requirements that have a higher rate of overlapping or conflicting.
22
Bano, Jameela, L. S. S. Reddy, and Hedi Khammari. "Fishbone Methodology: An Improved Goal-Oriented Framework for Requirements Engineering." International Journal of Engineering & Technology 7, no. 4.19 (2018): 440–44. http://dx.doi.org/10.14419/ijet.v7i4.19.23183.
Full textAbstract:
Goals are a reasonable system intended for recognizing, arranging and mitigating software supplies. The word Goal is continuously used in Requirement Engineering (RE). Ended the historical ten years, the supplies manufacturing (RE) society consumes constantly extended hers acceptance then version of goal-oriented methods to equally useful and non-functional supplies (NFRs). Goal-Oriented obligation engineering (GORE) gives an imperceptible method aimed at elicitation, investigation, clarification & modification, pattern and modeling of requirements. Different methods of G.O.R.E are exists for these processes of requirement engineering based on confident underlying concepts and principles. Founded on our literature appraisal, we recognize that prevailing penalty area concerned with requirement elicitation procedure do not sustain to prioritize the supplies when the stakeholders view are frequently unclear and contain ambiguity. Therefore, we presented improved goal-oriented Approach called Fishbone Methodology for requirement engineering in this paper. The objective of this research article is to understand the needs of stakeholders and accordingly provide services to develop the increments of RE processes which results in building a prototype model of the software. We talk about goalmouths after the viewpoint of 2 themes: goal inspection and goal progression. Finally, our proposed method provides appropriate representation mechanisms to enhance stakeholder comprehension and facilitate communication between analysts and stakeholders. Â
23
Sánchez, Óscar, Fernando Molina, Jesús García-Molina, and Ambrosio Toval. "ModelSec: A Generative Architecture for Model-Driven Security." JUCS - Journal of Universal Computer Science 15, no. (15) (2009): 2957–80. https://doi.org/10.3217/jucs-015-15-2957.
Full textAbstract:
Increasingly, the success of software systems depends largely on how their security requirements are satisfied. However, developers are challenged in implementing these requirements, mainly because of the gap between the specification and implementation, and the technical complexities of the current software infrastructures. Recently, Model-Driven Security has emerged as a new software development area aimed at overcoming these difficulties. This new paradigm takes advantage of the benefits of the model driven software development techniques for modeling and implementing security concerns. Following this trend, this paper proposes a model driven security approach named ModelSec that offers a generative architecture for managing security requirements, from the requirement elicitation to the implementation stage. This architecture automatically generates security software artifacts (e.g. security rules) by means of a model transformation chain composed of two-steps. Firstly, a security infrastructure dependent model is derived from three models, which express the security restrictions, the design decisions and the information needed on the target platform. Then, security software artifacts are produced from the previously generated model. A Domain-Specific Language for security requirements management has been built, which is based on a metamodel specifically designed for this purpose. An application example that illustrates the approach and the Eclipse tools implemented to support it are also shown.
24
Dong, Yuanfa, Gang Guo, and Wenrong Liu. "Requirement elicitation in product emotional design using fuzzy clustering and fuzzy cognitive model." Proceedings of the Institution of Mechanical Engineers, Part B: Journal of Engineering Manufacture 228, no. 1 (2013): 156–60. http://dx.doi.org/10.1177/0954405413498732.
Full text
25
Khan, Saad Mujahid. "MiniPI: Minimizing the Power Imbalance among Stakeholders." Quaid-e-Awam University Research Journal of Engineering, Science & Technology 20, no. 2 (2022): 48–54. http://dx.doi.org/10.52584/qrj.2002.07.
Full textAbstract:
The role of requirements elicitation is crucial in the software requirement engineering process as the requirement engineer has to extract the accurate requirements from different stakeholders. However, the problem emerges when the requirement team could not prioritize the extracted requirements because the requirement’s nature may vary as different categories of stakeholders have their own perspectives. This ultimately produces a power imbalance among stakeholders. Therefore, minimizing the power imbalance of software requirements among different categories of stakeholders is fundamentally important for a quality software product. Although many contributions have been made to this subject in the past, there is still a research gap available for minimizing the power imbalance among stakeholders. In this paper, we present a novel approach for minimizing the effects of power imbalance by age-sampling among different categories of stakeholders into three groups and then by age-mapping the requirements. After gathering questionnaires from stakeholders, the concerned parties determine the attributes of the Kano model through the filled Kano’s questionnaires and afterward, the satisfaction index is calculated by taking the values of the relevant age group into account, which eventually minimizes the power imbalance among stakeholders. In order to verify our methodology, we have performed quantitative analysis by calculating index values and applied verified Kano’s satisfaction formula to calculate the overall satisfaction index which improves the quality level of a software product.
26
Beckers, Kristian, Isabelle Côté, Ludger Goeke, Selim Güler, and Maritta Heisel. "A Structured Method for Security Requirements Elicitation concerning the Cloud Computing Domain." International Journal of Secure Software Engineering 5, no. 2 (2014): 20–43. http://dx.doi.org/10.4018/ijsse.2014040102.
Full textAbstract:
Cloud computing systems offer an attractive alternative to traditional IT-systems, because of economic benefits that arise from the cloud's scalable and flexible IT-resources. The benefits are of particular interest for SME's. The reason is that using Cloud Resources allows an SME to focus on its core business rather than on IT-resources. However, numerous concerns about the security of cloud computing services exist. Potential cloud customers have to be confident that the cloud services they acquire are secure for them to use. Therefore, they have to have a clear set of security requirements covering their security needs. Eliciting these requirements is a difficult task, because of the amount of stakeholders and technical components to consider in a cloud environment. Therefore, the authors propose a structured, pattern-based method supporting eliciting security requirements and selecting security measures. The method guides potential cloud customers to model the application of their business case in a cloud computing context using a pattern-based approach. Thus, a potential cloud customer can instantiate our so-called Cloud System Analysis Pattern. Then, the information of the instantiated pattern can be used to fill-out our textual security requirements patterns and individual defined security requirement patterns, as well. The presented method is tool-supported. Our tool supports the instantiation of the cloud system analysis pattern and automatically transfers the information from the instance to the security requirements patterns. In addition, they have validation conditions that check e.g., if a security requirement refers to at least one element in the cloud. The authors illustrate their method using an online-banking system as running example.
27
Filipović, Milorad, Željko Vuković, Igor Dejanović, and Gordana Milosavljević. "Rapid Requirements Elicitation of Enterprise Applications Based on Executable Mockups." Applied Sciences 11, no. 16 (2021): 7684. http://dx.doi.org/10.3390/app11167684.
Full textAbstract:
Software development begins with the requirements. Misunderstandings with customers in this early phase of development result in wasted development time. This work investigates the possibility of using executable UI mockups in the initial phases of functional requirements elicitation during the development of business applications. Although there has been a lot of research in the field in recent years, we find that there is still a need to improve model-driven tool design in order to enable customer participation from the initial phases of requirement specifications based on working prototypes. These prototypes can directly be reused in the rest of the development process. To meet the goal, we have been developing an open-source solution called Kroki that enables rapid collaborative development. We conducted a series of 10 joint user sessions with domain experts from different domains and backgrounds, resulting in the prototype specifications ranging from 7 to 20 screen mockups accompanied with domain models, developed in two-hour time frames. In this paper, we present our tool design that contributes to rapid joint development, and the results from the user sessions.
28
Sankhe, Purvi, and Mukesh Dixit. "Analysis of Traditional and Agile Software Development Process for Developing Recommender Model using Machine Learning." Indian Journal Of Science And Technology 17, no. 19 (2024): 1983–93. http://dx.doi.org/10.17485/ijst/v17i19.833.
Full textAbstract:
Objective: To create an AI-powered recommendation system that is designed for IT professionals to help them choose the best software development approaches. Through the use of specified data parameters. Methods: The recommendation system will make use of machine learning algorithms and data analysis methods to examine team dynamics, project needs, and other variables. The technology will enable developers to improve the quality of products and speed up the development process by recommending suitable development methodologies. Data parameters considered for the development of the recommendation model fall into four categories: requirements, user involvement, development team, type of project, and risk associated with it. Findings: Existing recommendation systems developed by different researchers are applicable for only requirement elicitation and to recommend different phases of the development process, whereas systems that will help select development methodology are not available in the existing systems. Among the five machine learning algorithms applied in the recommender system building process, the DecisionTree Classifier and RandomForest Classifier exhibit superior performance, achieving 100% accuracy, while the Kneighbors Classifier indicates 94.74% accuracy. Novelty: This study of systems introduces a novel approach to software development methodology, a recommender system, which helps IT developers select the best appropriate development approach for the development of a software product or project based on the type of project to be built and other data parameters. Keywords: Agile, Development, Requirements, Methodology, User, Customer
29
Bashari, Mahdi, Mahdi Noorian, and Ebrahim Bagheri. "Product Line Stakeholder Preference Elicitation via Decision Processes." International Journal of Knowledge and Systems Science 5, no. 4 (2014): 35–51. http://dx.doi.org/10.4018/ijkss.2014100103.
Full textAbstract:
In the software product line configuration process, certain features are selected based on the stakeholders' needs and preferences regarding the available functional and quality properties. This book chapter presents how a product configuration can be modeled as a decision process and how an optimal strategy representing the stakeholders' desirable configuration can be found. In the decision process model of product configuration, the product is configured by making decisions at a number of decision points. The decisions at each of these decision points contribute to functional and quality attributes of the final product. In order to find an optimal strategy for the decision process, a utility-based approach can be adopted, through which, the strategy with the highest utility is selected as the optimal strategy. In order to define utility for each strategy, a multi-attribute utility function is defined over functional and quality properties of a configured product and a utility elicitation process is then introduced for finding this utility function. The utility elicitation process works based on asking gamble queries over functional and quality requirement from the stakeholder. Using this utility function, the optimal strategy and therefore optimal product configuration is determined.
30
Hasan, Nazmul, and Manisha J. Nene. "ICT Based Learning Solutions for Children with ASD: A Requirement Engineering Study." International Journal of Special Education (IJSE) 37, no. 1 (2022): 112–26. http://dx.doi.org/10.52291/ijse.2022.37.31.
Full textAbstract:
"This research explores the explicit requirements to design and develop ICTbased learning solutions for children with Autism Spectrum Disorder (ASD). A requirement elicitation study has been conducted for six weeks of the study’s in Pune, India. The study sample size is fifteen (N=15), with an age limit between five to twelve years old. All the participants have been diagnosed with ASD and undergoing a skills development process in the same institution for at least six months. The outcomes of this research are tri-fold. Firstly, identify the twelve explicit requirements to design and develop ICT-based learning solutions considering the challenges due to autism. Secondly, conformity to the existing Multi Agent based Persuasive Education (MAPE) model with revealed requirements. Thirdly, propose an Internet of Things (IoT) based framework to observe and record the learning performance of ASD-affected children. The unique contribution of this study is to develop a Level-5 IoT framework to incorporate the requirements revealed through the participatory design approach for implementing ICT-based learning solutions. The proposed framework forms the basis for developing a dataset to identify the learning patterns and new requirements for ASD-affected children through Artificial Intelligence (AI) and Machine Learning (ML)."
31
Delima, Rosa, Retantyo Wardoyo, and Khabib Mustofa. "Requirements Conflict Detection and Resolution in AREM Using Intelligence System Approach." JUITA : Jurnal Informatika 10, no. 2 (2022): 191. http://dx.doi.org/10.30595/juita.v10i2.14855.
Full textAbstract:
Requirements engineering (RE) is the process of defining user requirements that are used as the main reference in the system development process. The quality of the RE results is measured based on the consistency and completeness of the requirements. The collection of requirements from multiple stakeholders can cause requirements conflict and have an impact on the inconsistency and incompleteness of the resulting requirements model. In this study, a method for automatic conflict detection and resolution in the Automatic Requirements Engineering Model (AREM) was developed. AREM is a model that automates the process of elicitation, analysis, validation, and requirements specification. The requirement conflict detection method was developed using an intelligent agent approach combined with a Weighted Product approach. Meanwhile, Conflict resolution is made automatically using a rule-based model and clustering method. Testing the ability of the method to detect and resolve conflicting requirements was carried out through five data sets of requirements from five system development projects. Based on the test results, it is known that the system is able to produce a set of objects that have conflicts in the data requirements. For conflict resolution, experiments were conducted with five conflict resolution scenarios. The experimental results show that the method is able to resolve conflicts by producing the highest completeness value, but the results of conflict resolution also produce a number of soft goals. The success of the method in detecting and resolving conflicts in the model is able to overcome the problem of inconsistencies and incompleteness in the requirements model.
32
Tjiptabudi, Fransiskus Mario Hartono. "Integrated Information and Communication Media Based on Organization Goal-Oriented Requirement Engineering (OGORE)." Jurnal Sistem Informasi 19, no. 1 (2023): 28–42. http://dx.doi.org/10.21609/jsi.v19i1.1198.
Full textAbstract:
The BPD NTT pension fund is a company incorporated as a legal entity that manages and runs a pension benefit program for BPD NTT employees. In its current business process, BPD NTT does not yet have a capable media to accommodate the information and communication needs of participants and interested parties, as a business branding and service facility for the participants. The problem that occurs is in the need elicitation stage when developing the information and communication media. For example, if the development is carried out by applying the Global eXtreme Programming (GXP) model, in the exploration phase the Organizational Goal-Oriented Requirement Engineering (OGORE) method will be applied to elicit needs that base each activity on organizational goals. The results of the research are in the form of web-based information and communication media modeling based on IT goals which are described in various tasks equipped with actors and resources used as well as KPIs that are integrated into each goal.
33
Iqtiar, Md Siddique. "Systems Engineering in Complex Systems: Challenges and Strategies for Success." European Journal of Advances in Engineering and Technology 9, no. 9 (2022): 61–66. https://doi.org/10.5281/zenodo.11545350.
Full textAbstract:
Requirement engineering plays a pivotal role in the development of complex systems, ensuring that stakeholder needs are effectively captured and translated into system specifications. However, the inherent complexity of modern systems presents unique challenges that can impede the requirements engineering process. This journal article explores the key challenges encountered in requirements engineering for complex systems and proposes strategies for success. The challenges include managing the intricacies of system interactions, dealing with uncertainty and ambiguity in requirements elicitation, addressing evolving requirements, ensuring stakeholder alignment, and accommodating non-functional requirements. To overcome these challenges, various strategies are discussed, including the adoption of agile and iterative approaches, the utilization of model-based requirements engineering techniques, effective stakeholder engagement strategies, leveraging tools and technologies for requirements management, and incorporating risk management practices. Case studies from diverse domains such as aerospace, healthcare, and automotive systems provide practical insights into the application of these strategies in real-world scenarios. Additionally, the article highlights future directions and emerging trends in requirements engineering, including the integration of artificial intelligence and machine learning, advancements in requirements visualization and communication, and considerations for ethical and regulatory aspects. By addressing the challenges and implementing effective strategies, practitioners can navigate the complexities of requirements engineering in complex systems and ensure the success of system development projects.
34
Purvi, Sankhe, and Dixit Mukesh. "Analysis of Traditional and Agile Software Development Process for Developing Recommender Model using Machine Learning." Indian Journal of Science and Technology 17, no. 19 (2024): 1983–93. https://doi.org/10.17485/IJST/v17i19.833.
Full textAbstract:
Abstract <strong>Objective:</strong> To create an AI-powered recommendation system that is designed for IT professionals to help them choose the best software development approaches. Through the use of specified data parameters. <strong>Methods:</strong> The recommendation system will make use of machine learning algorithms and data analysis methods to examine team dynamics, project needs, and other variables. The technology will enable developers to improve the quality of products and speed up the development process by recommending suitable development methodologies. Data parameters considered for the development of the recommendation model fall into four categories: requirements, user involvement, development team, type of project, and risk associated with it. <strong>Findings:</strong> Existing recommendation systems developed by different researchers are applicable for only requirement elicitation and to recommend different phases of the development process, whereas systems that will help select development methodology are not available in the existing systems. Among the five machine learning algorithms applied in the recommender system building process, the DecisionTree Classifier and RandomForest Classifier exhibit superior performance, achieving 100% accuracy, while the Kneighbors Classifier indicates 94.74% accuracy. <strong>Novelty:</strong> This study of systems introduces a novel approach to software development methodology, a recommender system, which helps IT developers select the best appropriate development approach for the development of a software product or project based on the type of project to be built and other data parameters. <strong>Keywords:</strong> Agile, Development, Requirements, Methodology, User, Customer
35
Kumar, Devendra, Anil Kumar, and Laxman Singh. "Non-functional Requirements Elicitation in Agile Base Models." Webology 19, no. 1 (2022): 1992–2018. http://dx.doi.org/10.14704/web/v19i1/web19135.
Full textAbstract:
The elicitation of non-functional and functional needs is one of the most critical jobs of a requirement engineer. This scenario involves the imposition of limits on non-functional needs, whereas functional requirements call for the operation of a system in order to carry out functionality. Over the last few years, agile software development approaches have gained widespread acceptance in the software industry as a problem-solving paradigm. Non-functional requirements (NFRs) are frequently cited as a point of contention in non-functional requirements (NFR) approaches. As well as functional requirements like speed and efficiency, security is desired, amongst a host of other things. Aspects like usability, security, and privacy must all be taken into account. Functional needs must be treated as though they were first-class under the current industry standard of practice. Functional requirements are distinguished from non-functional requirements by the fact that only implemented requirements can be evaluated. To give an example, this method attracts the attention of the system's end users to a critical defect in its architecture. Projects of this type frequently fail because to dissatisfaction among the target audience. If you'd like a great demonstration, consider the London Ambulance System. When dealing with non-compliance to the necessary degree of detail, it is feasible to raise the likelihood of software success this is the first study of its kind in its sector to bring attention to the most critical NFR issues. The problems that arise during the elicitation stage of requirement engineering in agile base models. It also outlines the techniques and strategies that are being considered. Proposed in the literature as a means of dealing with these problems.
36
Hastie, Kathryn M., Lilia I. Melnik, Robert W. Cross, et al. "The Arenaviridae Family: Knowledge Gaps, Animal Models, Countermeasures, and Prototype Pathogens." Journal of Infectious Diseases 228, Supplement_6 (2023): S359—S375. http://dx.doi.org/10.1093/infdis/jiac266.
Full textAbstract:
Abstract Lassa virus (LASV), Junin virus (JUNV), and several other members of the Arenaviridae family are capable of zoonotic transfer to humans and induction of severe viral hemorrhagic fevers. Despite the importance of arenaviruses as potential pandemic pathogens, numerous gaps exist in scientific knowledge pertaining to this diverse family, including gaps in understanding replication, immunosuppression, receptor usage, and elicitation of neutralizing antibody responses, that in turn complicates development of medical countermeasures. A further challenge to the development of medical countermeasures for arenaviruses is the requirement for use of animal models at high levels of biocontainment, where each model has distinct advantages and limitations depending on, availability of space, animals species-specific reagents, and most importantly the ability of the model to faithfully recapitulate human disease. Designation of LASV and JUNV as prototype pathogens can facilitate progress in addressing the public health challenges posed by members of this important virus family.
37
Simijaya, Mesakh Septiadi, and Aditiya Hermawan. "Stocks Saving Simulation based on Historical Data Web-based." Tech-E 5, no. 2 (2022): 93–102. http://dx.doi.org/10.31253/te.v5i1.622.
Full textAbstract:
This study aims to simulate the calculation of saving stocks based on historical data for the past 10 years for the period January 2010 - January 2020, because saving simulations based on historical data are still very rare, so a simulation application for saving stock calculations based on historical data is made that can help customers. investors in simulating the calculation of saving stocks so that it can be used as learning to determine how to save the right way that can produce a good return. This application is created using a waterfall model. From the application made, it is expected to know the good return results of the 10 issuers used in this study, and in making basic applications on user requirements obtained through several respondents through online questionnaires and processed with requirement elicitation techniques. With the application of a stock saving calculation simulation application, it is hoped that it can be a lesson for investors in saving stocks and can also be a lesson for potential investors and can also make it easier for investors to do calculations because the calculation process is computerized.
38
Yang, Wenchao, Wenfeng Li, Yulian Cao, Yun Luo, and Lijun He. "Real-Time Production and Logistics Self-Adaption Scheduling Based on Information Entropy Theory." Sensors 20, no. 16 (2020): 4507. http://dx.doi.org/10.3390/s20164507.
Full textAbstract:
In recent years, the individualized demand of customers brings small batches and diversification of orders towards enterprises. The application of enabling technologies in the factory, such as the industrial Internet of things (IIoT) and cloud manufacturing (CMfg), enhances the ability of customer requirement automatic elicitation and the manufacturing process control. The job shop scheduling problem with a random job arrival time dramatically increases the difficulty in process management. Thus, how to collaboratively schedule the production and logistics resources in the shop floor is very challenging, and it has a fundamental and practical significance of achieving the competitiveness for an enterprise. To address this issue, the real-time model of production and logistics resources is built firstly. Then, the task entropy model is built based on the task information. Finally, the real-time self-adaption collaboration of production and logistics resources is realized. The proposed algorithm is carried out based on a practical case to evaluate its effectiveness. Experimental results show that our proposed algorithm outperforms three existing algorithms.
39
Fanmuy, Gauthier, and Bassem Hassan. "ASPICE compliance development of Cyber‐Physical Systems by using Model‐Based Systems Engineering." INCOSE International Symposium 33, no. 1 (2023): 416–30. http://dx.doi.org/10.1002/iis2.13030.
Full textAbstract:
AbstractCurrent automotive Industry is facing numerous challenges. Business model is transitioning from ownership to shared mobility. Mobility of the future is becoming smarter, safer, more secured and connected. Distributed interconnected automotive systems will deliver added‐value mobility services. In the meantime, industrial standards require description of systems engineering practices as well as the practices justification. Automotive SPICE (ASPICE), a standard of software development best practices for automotive industry, for example, was one of the first to support the development of system and software now include hardware and cybersecurity. Traditional systems engineering development approaches are not any more appropriate. The current automotive system complexity requires new approaches like Model‐Based Systems Engineering (MBSE), using modeling and simulation. To address compliance to industry standards, traditional quality approaches consisting of or defining a quality system with a set of processes (e.g. Requirement elicitation process, documentation process…) are no more sufficient. Addressing these challenges require a digital transformation with two pillars. The first pillar is an MBSE methodology such as Cyber MagicGrid (Dassault Systèmes MBSE method) to define a set of best practices to develop a system. The second pillar is a quality management system that relies on the MBSE methodology rather than on a set of enterprise processes to address compliance with standards. Benefits of this approach is in acceleration of the digital enterprise transformation which is achieved by capitalizing the know‐how and considering the industry standards constraints.
40
Zawojska, Ewa. "A Consequential Contingent Valuation Referendum: Still Not Enough to Elicit True Preferences for Public Goods!" Central European Economic Journal 2, no. 49 (2018): 73–90. http://dx.doi.org/10.1515/ceej-2017-0012.
Full textAbstract:
Abstract Whether respondents disclose their preferences truthfully in surveys that are used to assess the values of public goods remains a crucial question for the practical application of stated preference methods. The literature suggests that in order to elicit true preferences, respondents should see a valuation survey as consequential: they must believe in the actual consequences that may follow from the survey result. Drawing on recent empirical findings, we develop a model depicting the importance of the consequentiality requirement for truthful preference disclosure in a survey that evaluates a public policy project based on a referendum-format value elicitation question. First, we show that a respondent’s belief that his vote may influence the outcome of the referendum plays a central role for revealing his preferences truthfully. Second, we find that the subjectively perceived probabilities of the successful provision of the public good and of the collection of the payment related to the project implementation not only need to be positive but also to be in a particular relationship with each other. This relationship varies in respondents’ preferences towards risk.
41
Aminah, Rezqallah Malkawi, Shahbani Abu Bakar Muhamad, and Dahalin Zulkhairi. "Review of cloud computing models in education and the unmet needs." IAES International Journal of Artificial Intelligence (IJ-AI) 13, no. 4 (2024): 4029–36. https://doi.org/10.11591/ijai.v13.i4.pp4029-4036.
Full textAbstract:
This article thoroughly examines recently proposed cloud computing (CC) models used within the higher educational institutions (HEI) field, scrutinizing their objectives, structures, and incorporated requirements. Each model's unique architecture and functionality are analyzed to understand their potential educational contributions. Beyond technical considerations, the study explores nuanced requirements essential for successful integration in educational settings. The review exposes diverse aims pursued by the models, such as enhanced scalability, collaborative learning, and resource management, emphasizing their capacity to reshape traditional educational paradigms. However, a notable gap emerges-the absence of cultural and requirement elicitation models within the frameworks. Despite growing cultural diversity and varied educational needs, most models lack components addressing cultural nuances and robust requirement elicitation. In conclusion, the paper identifies a pressing need for a transformative shift in developing CC models for education. The absence of dedicated cultural and requirement elicitation models challenges the holistic effectiveness of these frameworks. Future efforts should prioritize integrating culturally sensitive components and comprehensive requirement elicitation strategies to create adaptive, universally applicable, and inclusive CC educational environments. Addressing these gaps will pave the way for a nuanced and responsive integration of CC technologies in diverse educational settings.
42
Alzayed, Asaad. "Evaluating the Role of Requirements Engineering Practices in the Sustainability of Electronic Government Solutions." Sustainability 16, no. 1 (2024): 433. http://dx.doi.org/10.3390/su16010433.
Full textAbstract:
The efficacy of electronic government (E-Government) initiatives relies significantly on requirements engineering (RE). Every government wants sustainable solutions in the implementation of E-Government projects. The current research has adopted a mix of research methods. After conducting a comprehensive systematic literature review (SLR), the author conducted a case study to evaluate the proposed model. This research conducts an SLR of the contemporary literature on the success and failure factors of E-Government projects. Additionally, there is an association between the failure factors and the utilization of RE practices. A comprehensive search of electronic databases yielded a total of 71 pertinent articles. After meticulous screening and quality assessment, the data were extracted for analysis. A total of 62 papers were eventually selected. The SLR addressed the distinct hurdles encountered by government bodies. The findings indicated a positive relationship between the utilization of RE practices and the attainment of project success. Various aspects, such as project management practices, stakeholder engagement, and effective communication, were identified as factors that can reduce failures in E-Government projects. The deficiencies observed in E-Government initiatives were linked to inadequacies in implementing RE practices. The other issues identified were insufficient requirement elicitation, limited stakeholder involvement, and inadequate validation and verification of requirements. This study also presented a conceptual framework illustrating the difficulties in E-Government and the practices of RE. Statistical data analysis techniques were employed to examine this conceptual framework. This study suggests that managers examine and evaluate their E-Government project failure reasons and factors on a periodic basis to sustain and continuously enhance E-Government project success.
43
Rezqallah Malkawi, Aminah, Muhamad Shahbani Abu Bakar, and Zulkhairi Dahalin. "Review of cloud computing models in education and the unmet needs." IAES International Journal of Artificial Intelligence (IJ-AI) 13, no. 4 (2024): 4029. http://dx.doi.org/10.11591/ijai.v13.i4.pp4029-4036.
Full textAbstract:
<p>This article thoroughly examines recently proposed cloud computing (CC) models used within the higher educational institutions (HEI) field, scrutinizing their objectives, structures, and incorporated requirements. Each model's unique architecture and functionality are analyzed to understand their potential educational contributions. Beyond technical considerations, the study explores nuanced requirements essential for successful integration in educational settings. The review exposes diverse aims pursued by the models, such as enhanced scalability, collaborative learning, and resource management, emphasizing their capacity to reshape traditional educational paradigms. However, a notable gap emerges-the absence of cultural and requirement elicitation models within the frameworks. Despite growing cultural diversity and varied educational needs, most models lack components addressing cultural nuances and robust requirement elicitation. In conclusion, the paper identifies a pressing need for a transformative shift in developing CC models for education. The absence of dedicated cultural and requirement elicitation models challenges the holistic effectiveness of these frameworks. Future efforts should prioritize integrating culturally sensitive components and comprehensive requirement elicitation strategies to create adaptive, universally applicable, and inclusive CC educational environments. Addressing these gaps will pave the way for a nuanced and responsive integration of CC technologies in diverse educational settings.</p>
44
Smita, Raj*. "SW REQUIREMENT ENGINEERING IN PRACTICE." Global Journal of Engineering Science and Research Management 3, no. 12 (2016): 41–49. https://doi.org/10.5281/zenodo.199474.
Full textAbstract:
Requirements engineering is the engineering discipline of establishing user requirements and specifying software systems. It refers to the process of formulating, documenting and maintaining the SW requirements and to the subpart of SW Engineering pertaining to this process. Requirement engineering continues through the lifetime of the system. Requirement engineering is very critical to the success of software project or product. Requirement should be capable of being measured, testable, traceable, action oriented w.r.t. the business need and opportunities. Besides, Requirement should be properly furnished with details which are sufficient for system design. To derive the requirements user need to have clear and thorough understanding of the product(s) to be developed. Preparation of requirements can be done after detail discussion with team members and end user.
45
HICKEY, ANN M., and ALAN M. DAVIS. "A Unified Model of Requirements Elicitation." Journal of Management Information Systems 20, no. 4 (2004): 65–84. http://dx.doi.org/10.1080/07421222.2004.11045786.
Full text
46
Serna M., Edgar, and Alexei Serna A. "A Model for Documenting Requirements Elicitation." Ingeniería 28, no. 2 (2023): e19411. http://dx.doi.org/10.14483/23448393.19411.
Full textAbstract:
Context: This work proposes a model to document the elicitation of requirements in the field of Requirements Engineering. Method: A systematic review of the literature was conducted to determine the validity and effectiveness of the existing models for documenting requirements elicitation. Results: By analyzing the results of this review, it was concluded that it is possible – and that is required – to take the best documented practices and add principles from logic, abstraction, and formal methods to them in order to structure a semi-formal model for documenting elicitation. Those currently proposed focus on techniques to collect information and pay little attention to documentation. In addition, these models are mainly based on natural language, which makes their interpretation difficult, and they generate re-processing in later stages of the life cycle due to ambiguities. Conclusions: This article describes a structured model, as well as its application and validation, by comparing it against five models found in the review.
47
Messaoudi, Mohammed. "A Model for Viewpoint Control in Requirements Elicitation." Journal of Computer Science and Technology Studies 4, no. 1 (2022): 73–78. http://dx.doi.org/10.32996/jcsts.2022.4.1.8.
Full textAbstract:
Requirements elicitation from multiple human sources involves uncertainty management. Most requirements analysis methods focus on expressing the requirements and ignore the uncertainty inherent in the process of requirements elicitation. This paper proposed a model for requirements elicitation from multiple viewpoints. The model is based on the idea of building internal models of the viewpoints that record their performance in providing information, assessing information, and resolving conflicts between viewpoints. The paper argues that the proposed approach provides a better mechanism in information validation and conflicts resolution. The paper is part of the work reported by the author in Messaoudi (1994).
48
JIN, Z., D. A. BELL, F. G. WILKIE, and D. G. LEAHY. "AUTOMATED REQUIREMENTS ELICITATION: COMBINING A MODEL-DRIVEN APPROACH WITH CONCEPT REUSE." International Journal of Software Engineering and Knowledge Engineering 13, no. 01 (2003): 53–82. http://dx.doi.org/10.1142/s0218194003001147.
Full textAbstract:
Extracting pertinent and useful information from customers has long plagued the process of requirements elicitation. This paper presents a new approach to support the elicitation process. This approach combines various techniques for requirements elicitation which include model-based concept acquisition, goal-driven structured interview and concept reuse. Compared with the available approaches for requirements elicitation, the most significant feature of our approach is that it supports both the automation of interaction with customers by using domain terminology, not software terminology and the automated construction of application requirements models using model-based concept elicitation and concept reuse. The capacity of this approach comes from its rich knowledge which is clustered into several abstract levels.
49
Anwar, Fares, and Rozilawati Razali. "Stakeholders Selection Model for Software Requirements Elicitation." American Journal of Applied Sciences 13, no. 6 (2016): 726–38. http://dx.doi.org/10.3844/ajassp.2016.726.738.
Full text
50
Waite, Michael, Paul Logan, and David Harvey. "Model-Based Stakeholder Needs and Requirements Elicitation." INSIGHT 17, no. 4 (2014): 35–37. http://dx.doi.org/10.1002/inst.201417435.
Full text