Abstract

During requirements elicitation stage, requirements engineers gather system requirements and drive stakeholders to convey needs and desired software functionality. The elicitation techniques used to acquire software requirements significantly impact the quality of elicited requirements. Several elicitation techniques have been proposed for the Requirement Engineering (RE) process; however, these techniques are rarely used in reality due to a lack of empirical and relative appraisals to assist software team members in deciding on the most appropriate technique. Re-quirement engineers encounter difficulty in deciding the suitable elicitation technique to adopt for a certain software project. This difficulty is due to a lack of knowledge regarding the available elicitation techniques, their efficacy, and how appropriate they are for a certain project. According to the literature, requirements engineering processes benefit from the use of Multi-Criteria Decision-Making (MCDM) approaches within particular contexts. An optimal structure is constitutionally presented within the area of the requirements engineering process; hence, the demonstra-tion of a robust decision-making method in the requirements engineering process should motivate a higher level of satisfaction with software projects developed in this way. This study proposes an approach for using the MCDM method in the requirements engineering process. The study contains a model for investigating the selection of an appropriate elicitation technique based on a decision-making method, namely, the Best-Worst Method (BWM). The findings of the proposed model demonstrate the BWM’s power in solving complex decision problems involving several criteria and alternatives.

Highlights

  • In Software Engineering (SE), the software requirements are the services that the software provides to customers to satisfy their needs

  • The focused investigation seeks to answer general queries, such as: does the software contribute to the goals of the company? Is the implementation plan appropriate considering the budget and schedule [1]? Requirement Engineering (RE) activities are introduced at the initial phase of the Software Development Life Cycle (SDLS), which allows the development team to draw a clear view of the functionalities and benefits that the system could provide

  • The aggregated result based on 27 domain experts shows that the Availability of Key Stakeholders (ASTK) criterion was evaluated as the most significant attribute for selecting the appropriate elicitation technique

Read more

Summary

Introduction

In Software Engineering (SE), the software requirements are the services that the software provides to customers to satisfy their needs. Requirements engineering is the process of analyzing and determining these software services and constraints. A focused investigation takes place as a pre-step at the RE stage. The focused investigation seeks to answer general queries, such as: does the software contribute to the goals of the company? The requirements elicitation activity allows developers to better understand the stakeholders’ needs and how they can benefit from using the new system. This is achieved by working with both stakeholders and developers in order to analyze the problem domain and the current limitations, along with the services and work activities that stakeholders needs

Objectives
Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.