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.

Highlights

  • Requirement is something needed in order to meet an objective

  • 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 it‟s very vital for all the project team members and stakeholders to thoroughly adjust to the requirement changes where it‟s essential

  • Business requirements are to be well-defined for Enterprise Resource Planning (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

Read more

Summary

INTRODUCTION

Requirements management demonstrates that organization ensures and meets the needs of its all customers and stakeholders. 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. Customer relationship ought to be the most important factor while gathering business requirements, as requirements keep on changing throughout the overall requirement engineering process. The BRD document ensures the accuracy of business requirements from the business perspective for a customer [8]. Business objective defines “what does the organization wants to be or what is the organization mission” whereas “the technical objective provides the ground where the business objectives are met”

REQUIREMENTS MANAGEMENT
ERP SYSTEMS
METHODS AND MATERIALS
Formalizing Requirements in ERP Software Implementations
Enterprise Resource Planning Classifications
REQUIREMENTS MANAGEMENT IN ERP
Limitations
VIII. EFFECT OF CHANGE MANAGEMENT TO ERP
ERP CHECKLIST
Financial Accounting Module
Sales and Inventory Module
Customer Relationship Module
Supply Chain Module
CONCLUSION

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.