Abstract
Requirement engineering has taken the attention in both academic and industries, as today’s software’s expected to fulfil and provide highly customers’ centralize functionality and qualities. Requirement elicitation is the main and major step of any software project development life. It has direct impact on development lifecycle of any software. The incomplete or ambiguous requirement create confusion for the stakeholders. This is the step which leads the project to the success or fulfills the desire of user or it is the step or reason which may leads the project to the downfall. In requirement elicitation process there are many factors which effects on requirement elicitation. In this paper we are proposing the impact of Organizational factors on requirement engineering. Stakeholder needs include an initial, but continuous and critical phase in program development. This section of development is characterized by a high degree of error, influencing important factors based on communication problems. Software development is considered as a powerful process in which the needs of change seem to exist inevitable. Software updates are encouraged by all types of changes including changes in requirements. These types of changes cause internal flexibility, which has several implications for software development life cycle. In particular, the findings reveal that the instability of services is at its highest significant impact on time and cost skip to software projects. Our investigation too tested features that contribute to the level of demand flexibility and I found that flexible as common communication between users and developers and the application of a clear approach to needs analysis and modeling contribute to the stability of requirements. The main purpose of this survey is to look for the requirement elicitation process from the intra and extra factors perspective. The quality of services is critical to the success of the project. Negotiation needs, however these are not an easy task. Vision, psychological model and differences in expectations between users and analysts do this work is difficult and controversial. In most cases, clients are completely convinced of their real needs. In others, the current operating procedure does not meet the expectations of management. In this paper we have search the problems, factors of elicitation process.
Keywords: Impact of organizational factors RE; Requirement elicitation; intra organization
References
- Zhang Y Harman, M Finkelstein A and Mansouri A. “Comparing the performance of metaheuristics for the analysis of multi-stakeholder tradeoffs”. Requirements Optimization (2011): 761-773.
- Atladottir G Thora HE and Gunnarsdottir. “Comparing task practicing and prototype fidelities when applying scenario acting to elicit requirements”. Requirements Engineering (2012): 157-170.
- Meth H, Brhel M and Maedche A. “The state of the art in automated requirements elicitation information and Software Technology”. (2013): 1695-1709.
- Pacheco C and Garcia. “A systematic literature review of stakeholder identification methods in requirements elicitation”. Journal of Systems and Software (2012): 2171-2181.
- Sharmila P and R Umarani. “A walkthrough of Requirement Elicitation Techniques”. International Journal of Engineering Research and Applications (2011): 1583-1586.
- Razali R and F Anwar. “Selecting the Right Stakeholders for Requirements Elicitation: A Systematic Approach”. Journal of Theoretical and Applied Information Technology (2011).
- Vlas R and Robinson W. “A rule-based natural language technique for requirements discovery and classification in open-source software development projects”. Proceedings of the 44th Hawaii International Conference on System Sciences. Manoa, Hawaii (2011): 110.
- Aranda G Vizca?no. “A framework to improve communication during the requirements elicitation process in GSD projects”. Requirements Engineering (2010): 397-417.
- Sabahat N., et al. “An iterative approach for global requirements elicitation: a case study analysis”. Proceedings of the IEEE International Conference on Electronics and Information Engineering (ICEIE). Kyoto, Japan (2010): 361-366.
- Sutcliffe A and Maiden N. “The domain theory for requirements engineering”. IEEE Transactions on Software Engineering, IEEE (1998): 174-196.
- Breitman KK, Leite JCSP and Berry DM. “Supporting scenario evolution”. Requirements Engineering (2005): 112131.
- Soltanian A, Binti R and Soltanian H. “WEBSTUIRE: web-based support tool for user interface requirements elicitation”. Proceeding of the International Conference on Computer and Knowledge Engineering (ICCKE). Ferdowsi, Mashhad (2013): 17.
- Fernandes J., et al. “I Think: a game based approach towards improving collaboration and participation in requirement elicitation”. Procedia Computer Science (2013): 66-77.
- Carrizo D, Dieste O and Juristo N. “Systematizing requirements elicitation technique selection”. Journal: Information and Software Technology (2014): 644-669.
- Burnay C and Faulkner S. “What stakeholders will or will not say: A theoretical and empirical study of topic importance in requirements engineering elicitation interviews”. Information Systems (2014): 61-81.
- Castro C and Cleland J. “Utilizing recommender systems to support software requirements elicitation”. Second International Workshop on Recommendation Systems for Software Engineering (RSSE’10). South Africa (2010): 610.
- Wnuk K, Gorschek T and Zahda S. “Obsolete software requirements. Information and Software Technology”. (2013): 921-940.
- Sakhnini V, Mich L and Berry D. “The effectiveness of an optimized EPM create as a creativity enhancement technique for web site requirements elicitation”. Requirements Engineering (2012): 171-186.
- Moros B., et al. “Transforming and tracing reused requirements models to home automation model”. Information and Software Technology (2013): 941-965.
- Lenis R Wong, David S Mauricio and Glen D Rodriguez. “A Systematic Literature Review About: Software Requirements Elicitation”. Journal of Engineering Science and Technology 12 (2017): 296-317.
- Fares Anwar and Rozilawati Razali. “A Practical Guide to Requirements Elicitation Techniques Selection: An Empirical Study”. Middle-East Journal of Scientific Research 11 (2012): 1059-1067.
- Didar Zowghi and N Nurmuliani. “A Study of the Impact of Requirements Volatility on Software Project Performance”. University of Technology, Sydney (2007).
- Jane Coughlan, Mark Lycett and Robert D Macredie. “Communication issues in requirements elicitation: A content analysis of stakeholder experiences”. Information and Software Technology 45 (2003): 525-537.