(IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 9, No. 8, 2018 247 | Page www.ijacsa.thesai.org Impact and Challenges of Requirements Management in Enterprise Resource Planning (ERP) via ERP Thesaurus Rahat Izhar 1 Research Associate/ ERP Consultant Department of Software Engineering , Bahria University Islamabad, Pakistan Dr. Shahid Nazir Bhatti 2 Associate Professor Department of Software Engineering Bahria University Islamabad, Pakistan Saba Izhar 3 Teaching Associate Department of Management Sciences Bahria University Islamabad, Pakistan Dr. Amr Mohsen Jadi 4 Associate Professor Department of CCSE, University of Hail, KSA Abstract—Managing requirements efficiently aids the system design team to understand the existence and significance of any individual requirement, there are numerous requirements management practices that benefit in decision making but significantly many lacks to account the important factors that have substantial influence in managing requirements in context of ERP systems in particular. As highlighted comprehensively later in literature review section, requirements management failure is one of the pivotal aspects for the project(s) failure. The prime problem/lacking in software design and development is when it comes to requirements management the most vital thing that gets ignored is thinking before performing activities. As it should be the main step to save time, money and efforts. Further prominence other aspects in this are pivotal value about the software’s running in industries, the question arises when their business need ERP system, and when requirements change or new requirements are emerged into the system, what are the obstacles faced and how these obstacles are accomplished. ERP systems are becoming the need of industries nowadays as various industries are facing problems regarding data loss; it is challenging for the owners to fetch all the information when they need it, accounting systems are slower and consuming a lot of time and many other issues likewise. This paper further illustrates in detail the important traits, issues toward businesses may have when ERP is implemented and when requirements are changed or not managed professionally what issues are faced by requirement engineering team and industries and thus how to resolve them. Keywords—Enterprise Resource Planning (ERP); Product Owner (PO); requirements elicitation; requirements management; change management I. INTRODUCTION Requirement is something needed in order to meet an objective. Requirements management demonstrates that organization ensures and meets the needs of its all customers and stakeholders. Requirements Management has a great impact on communication between the team members and all the existing stakeholders as requirements modifications can be added at any stage of project therefore it‟s very vital for all the project team members and stakeholders to thoroughly adjust to the requirement changes where it‟s essential. Firstly business requirements are to be well-defined for ERP, business analysis play a pivotal role in requirements management as it is the responsibility of business analyst to get involved with the stakeholders to create a Requirement Management Plan (RMP) during the planning phase of the project that is ERP system for that specific organization. Requirement management plan includes roles and responsibilities of stakeholder‟s, requirements management process, requirements prioritization, requirements traceability, requirements change and control, requirement management tools, requirement versioning and many more. The business analyst goes about as an extension amongst business and IT, makes the business requirements that could be comprehended by the development engineers and also disclosing to the clients to the technical know-how of system in detail as required. Customer relationship ought to be the most important factor while gathering business requirements, as requirements keep on changing throughout the overall requirement engineering process. One of the key factors for a business analyst is to make sure that requirements are properly visible and understood by all the stakeholders. The high level objective of a system under requirements gathering phase is achieved mainly by precision in business requirements. Lucid business requirements are thus obtained in a way that the end results of the project are crystal clear to the stakeholders [9]. A Business Requirements Document (BRD) must be maintained and iteratively checked by the business analyst because it summarizes the answers to the business questions what are the purely business problems that a customer‟s wants to get solve? For example, what job the customer wants to get accomplish? A business Analyst describes the constraints to a customer on any proposed solution from a business perspective. Thus BRD is formed for the effective communication between internal and external technology providers to provide with the