Abstract
Requirement Engineering (RE) is one of the crucial elements for successful software development. Nevertheless, in terms of research discussing the failure or success of various products, little has been undertaken to examine this area as it pertains to the Gulf Cooperation Council (GCC) nations, i.e. Saudi Arabia (KSA), Kuwait, United Arab Emirates (UAE), Bahrain, Qatar, and Oman. The aim of this research is to present an analysis of the current ways in which software is developed in these nations. The researchers undertook a survey of practitioners in software development, asking questions regarding their recent work. The survey was based on an extensive survey that was adapted in view of contemporary software development practice. The research reports on requirement practices and how they relate to project sponsors/customers/users and project management. The respondents came from GCC nation companies, most of whom worked on developing software in-house. The outcomes demonstrate that the majority of IT companies in these nations do not employ the optimal methodologies for requirement engineering processes, using their own. In addition, project managers are often lacking in complete authority. Making comparisons between our findings and past research, requirements engineering practices is still inadequate in these nations. Thus the research results are particularly useful as the data is derived from countries where published research about software development practices is scant.
Highlights
IntroductionPast research has demonstrated that accuracy and completeness in the requirements engineering (RE) practices of developers play a significant part in the success or failure [4,5,6]
A considerable amount of research has been undertaken with the aim of designing novel improved solutions to address software development (SD) difficulties [1,2,3], it is crucial to develop an understanding of contemporary software development methods and which of them offers optimal outcomes
For the IT projects in this research sample, found that project success has a negative correlation with project manager‘s experience and that the best predictor of successful projects is that requirements should be complete and accurate
Summary
Past research has demonstrated that accuracy and completeness in the requirements engineering (RE) practices of developers play a significant part in the success or failure [4,5,6]. To improve the RE practices Pandey et al [23] proposed a method for requirements gathering and management. It is possible to split up the requirements of a project into smaller sections and address them in a gradual manner. This method removes the need to define all of the system requirements initially, and makes it easier to correct errors as they arise. If a developer doesn't/can't have enough dialogue with the client to enable them to correctly define the requirements of the system, agile methods will often lead to a project stalling [33]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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 callMore From: International Journal of Advanced Computer Science and Applications
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.
