Development of framework to support software requirement elicitation using a domain ontology

2021 ◽  
pp. 98-102

One of the main goals of Software Requirements Engineering is to understand customers' needs and to put their customer needs in requirement. The requirement engineering has several processes one of them are requirement elicitation the requirement elicitation considered as one process of requirement engineering and also considered as important process so the process of elicit the requirement has difficult, due to the incompleteness problem, ontology has player important rule to helps the requirement elicitation by adding more information about the words. in this paper implementing framework by using domain ontology, the framework implements using java and ontology using protégé, the framework evaluated using requirement in in banking domain, and show the results helps the software developer to choose the requirement.

2016 ◽  
Vol 15 (7) ◽  
pp. 6940-6946
Author(s):  
Sidra Arshad ◽  
Hafiza Tahira Fazal ◽  
Tahir Nawaz

The performance of Requirement Engineering is like framework for software development process. All-inclusive software has four mainstays of requirement engineering processes i.e. Functional and non-functional requirements, design,implementation and testing build the complete software fortification on top of the mainstays. Requirement engineers have to face numerous challenges to develop successful and impressive software. Requirements Engineering (RE) leads software development process. Different constraints and needs of users are explored as well as hitches in previous system are depicted. The scope of this study is to exemplify the difficulties faced by users in the utmost maiden phase of RE Requirements Elicitation and a framework is presented as well. A survey was conducted in different campuses of Universities in Pakistan for this purpose. Questionnaire was distributed among project development students of various disciplines to gather and highlighted the problems during Requirements Elicitation. Finally the predictive statistical software SPSS was used to input the collected data for more precise calculations, the results of which are discussed in section 3.


1976 ◽  
Author(s):  
M. D. Richter ◽  
J. D. Mason ◽  
M. W. Alford ◽  
I. F. Burns ◽  
H. A. Helton

Author(s):  
Samina Saghir ◽  
Tasleem Mustafa

<p>Increase in globalization of the industry of software requires an exploration of requirements engineering (RE) in software development institutes at multiple locations. Requirements engineering task is very complicated when it is performed at single site, but it becomes too much complex when stakeholder groups define well-designed requirements under language, time zone and cultural limits. Requirements prioritization (RP) is considered as an imperative part of software requirements engineering in which requirements are ranked to develop best-quality software. In this research, a comparative study of the requirements prioritization techniques was done to overcome the challenges initiated by the corporal distribution of stakeholders within the organization at multiple locations. The objective of this study was to make a comparison between five techniques for prioritizing software requirements and to discuss the results for global software engineering. The selected techniques were Analytic Hierarchy Process (AHP), Cumulative Voting (CV), Value Oriented Prioritization (VOP), Binary Search Tree (BST), and Numerical Assignment Technique (NAT). At the end of the research a framework for Global Software Engineering (GSE) was proposed to prioritize the requirements for stakeholders at distributed locations.<strong></strong></p>


2021 ◽  
Vol 13 (12) ◽  
pp. 6748
Author(s):  
Basit Shahzad ◽  
Iqra Javed ◽  
Asadullah Shaikh ◽  
Adel Sulaiman ◽  
Ahsanullah Abro ◽  
...  

Improvement in the requirements for engineering practices is needed in areas such as requirement elicitation, validation, prioritization, and negotiations between stakeholders to create successful projects for COVID-19 (coronavirus disease 2019) software. Many algorithms and techniques are used to create quality software projects, but they still need more improvement to work effectively for global pandemic COVID-19 software. By improving the reliability of requirement engineering practices using blockchain-based technology, the software will be reliable and will make it easier for the users working in a lockdown situation because of COVID-19. Therefore, our purpose is to identify the factors for reliable software engineering practices using blockchain-oriented technology for COVID-19 software. A systematic literature review is conducted to identify challenges and offer solutions. Through using blockchain-based technology for requirement engineering practices, the requirements will be gathered accurately and validated, and the conflicts between stakeholders will also be solved. It will improve the quality and reliability of COVID-19 software projects, which will help society work effectively from home. Improvement in the quality and reliability of COVID-19 software will improve users’ interest, and their working capacity will be increased.


Author(s):  
M J Darlington ◽  
S J Culley

The design requirement is a description of the desired solution to a problem. In engineering design, as in all other, a clear expression of a well-formulated design goal is vital for successful and efficient completion of the design task. The nature of the design requirement and the processes by which it is achieved have been the subject of a wide variety of research. The purpose of the paper is twofold. Firstly, it sets out to collate and discuss representative research in this area in order to give an overview of the current scope of the work. Secondly, it seeks to draw a comparison with the task of developing the design requirement for software and information systems and to initiate a discussion that considers to what extent the substantial body of research in software requirements engineering might help to give an understanding of the design requirement for the engineering design domain. A tentative characterization of the differences between the tasks in the two domains is presented, and representative papers from requirements engineering are used to suggest areas of overlap as a starting point for further investigation.


Author(s):  
Päivi Parviainen ◽  
Maarit Tihinen ◽  
Marco Lormanms ◽  
Rini van Solingen

This chapter introduces requirements engineering for sociotechnical systems. Requirements engineering for sociotechnical systems is a complex process that considers product demands from a vast number of viewpoints, roles, responsibilities, and objectives. This chapter explains the requirements engineering terminology and describes the requirements engineering process in detail, with examples of available methods for the main process activities. The main activities described include system requirements development, requirements allocation and flow-down, software requirements development, and continuous activities, including requirements documentation, requirements validation and verification, and requirements management. As requirements engineering is the process with the largest impact on the end product, it is recommended to invest more effort in both industrial application as well as research to increase understanding and deployment of the concepts presented in this chapter.


Sign in / Sign up

Export Citation Format

Share Document