Requirements Elicitation Techniques in Mobile Applications

The common view of requirements engineering consists of requirement elicitation, specification, validation, and evolution. Requirement elicitation is a significant stage to assure the quality of the requirement documentations and would affect the project success or failure. There are different techniques to elicit the requirements. Each technique has its advantages and disadvantages. Thus, it is important to adopt more than one kind of technique to describe a system clearly from different viewpoints. This study prospected some of the research papers in the same field to display the requirements elicitation techniques that are used in developing mobile applications from a variety of research disciplines. It suggests some requirements elicitation concepts to guide software engineers in selecting the techniques according to customers' needs and to show the common challenges that they face.

Reliable Requirements Engineering Practices for COVID-19 Using Blockchain

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.

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

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.

An Approach for Selecting the Suitable Requirement Elicitation Technique

Requirements elicitation is an initial phase in software development. In this phase, requirements engineers gather the requirements of the software under development from users, stakeholders and customers. The techniques used for gathering requirements have a big influence on the quality of requirements and the success of project. Many requirements elicitation techniques (RET) such as: interview, prototype and observation can be used for requirements gathering process. However, one technique is not suitable for all different projects. Usually requirement engineers select the RET based on personal preferences and assumptions such as; this is the only technique which they know. However, this subjective decision can result in using inappropriate RET. Using unsuitable RET may decrease the quality of elicited requirements. Even though researchers have proposed many techniques for elicitation, one of the challenging issues is to choose the suitable RET for specific situations. The purpose of this paper is to help requirement engineers to choose suitable RET. To do that firstly, we identify factors that affect in selecting RET. Secondly, an approach to select suitable RET is proposed. Thirdly, a prototype is developed to help requirements engineers and to ease the process of selectingelicitation technique. Lastly, experts evaluate the proposed approach and the prototype.