The Living Requirements Space: Towards the Collaborative Development of Requirements for Future ERP Systems (original) (raw)
Related papers
Management of requirements in ERP development
Proceedings of the 2009 ACM symposium on Applied Computing - SAC '09, 2009
Identification and specification of business requirements are extremely important when development of Enterprise Resource Planning systems (ERPs) take place. It can be stated that this is still a problematic area not well researched and, as a result from that, it does not exist much guidance on how to deal with requirements. In this paper we discuss if existing problems of requirements management are the same or if they differ according to the type of development: closed source (proprietary) or open source ERP. The reason is that it is possible that these two approaches can promote each other in how to improve the first phase in ERP development. From the discussion about similarities and differences between the two approaches it is suggested further research in this area that could end up in some more practical guidelines on how to do the requirements definition so that the finally developed ERPs better support adopters' needs.
Requirements Management for ERP Projects
Organizational Advancements through Enterprise Information Systems
ERP software standardizes an enterprise’s business processes and data. The software converts transactional data into useful information and collates the data so that they can be analyzed. Requirements engineering is an important component of ERP projects. In this paper, we propose: (1) An ERP maturity model (EMM) for assessing the ERP maturity within the organization and (2) A Requirements Engineering Method (REM) for ERP system requirements to capture the requirements from the different types of users of an ERP system, verifying and validating them. The EMM consists of three levels and each level has a focus and a key process area. Key indicators of ERP functionality identified by a major ERP vendor have been used to apply the EMM to an enterprise. This identifies the level of the EMM to which an enterprise belongs. Then the REM is used to enable the enterprise to assess its ERP system requirements and refine it using a knowledge database to reach a higher level in the EMM than the...
The Brave New World of Information Systems and Business Software Requirements: Four Key Principles
Abstract Despite undoubted successes in the last decades, requirements engineering needs a better alignment between research and its grounding in practical needs by refocusing its research agenda. We explore seven requirements issues that currently influence the discovery and management of design requirements. The exploration is based on a field study and expert discussions that took place during a workshop held in June 2007 and funded by the US National Science Foundation's Science of Design Program.
Integration of Requirement Engineering Challenges with Its Practices in ERP Systems
This study focuses on the problems and solutions that are useful and insightful evaluated. Requirement Engineering of the standard model of the process of life, in spite of the high degree of implementation, I know very little about the problems that arise and I make the process work better. And besides, many of these specific issues and discuss ways to improve them. I have tried to categorize the types of challenges because of their similarities are connected. And again, I talked about many of these general issues and their application to do so.
Information Requirements for Enterprise Systems
Lecture Notes in Computer Science, 2012
In this paper, we discuss an approach to system requirements engineering, which is based on using models of the responsibilities assigned to agents in a multi-agency system of systems. The responsibility models serve as a basis for identifying the stakeholders that should be considered in establishing the requirements and provide a basis for a structured approach, described here, for information requirements elicitation. We illustrate this approach using a case study drawn from civil emergency management.
Online Information …, 2010
Purpose -This paper aims to discuss a new tool for requirements gathering in the Web 2.0 era. It seeks to investigate the features that this kind of tool should have in order to be as widely applicable and useful as possible. Further, it aims to explore the extent to which business requirements for enterprise resource planning (ERP) systems can be collected and discussed collaboratively in a worldwide community of business process experts. Design/methodology/approach -The paper is a combination of empirical research, hermeneutics and design research. Findings -The proposed Living Requirements Space (LRS) platform has the potential of becoming an international forum for collecting and discussing business requirements for ERP systems. Practical implications -The LRS platform will allow ERP developers, ERP systems implementers, and academics to better understand the evolution of business requirements for ERP systems. It will create a knowledge base of ERP business requirements, that is, a repository that guarantees open and unrestricted access to content. It will thus allow for more international ERP systems and far more comprehensive education on and understanding of business processes and ERP systems. Originality/value -LRS is an open access tool that allows for the gathering of ERP systems requirements in a vendor-and project-independent approach that is unbiased towards any geographic region.
ERP requirements engineering practice: lessons learned
2004
Abstract Standard off-the-shelf requirements engineering processes have become a key to conceptualizing any integrated, corporate-wide solution based on packaged enterprise resource planning software. A generic RE model offers defined processes, suggests process stakeholders, specifies steps to accomplish tasks, indicates task dependencies, and provides standard tool support for ERP RE.
International Journal of Advanced Computer Science and Applications
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.
Management of requirements in ERP development: a comparison between proprietary and open source ERP
Proceedings of the 2009 Acm Symposium on Applied Computing, 2009
Identification and specification of business requirements are extremely important when development of Enterprise Resource Planning systems (ERPs) take place. It can be stated that this is still a problematic area not well researched and, as a result from that, it does not exist much guidance on how to deal with requirements. In this paper we discuss if existing problems of requirements management are the same or if they differ according to the type of development: closed source (proprietary) or open source ERP. The reason is that it is possible that these two approaches can promote each other in how to improve the first phase in ERP development. From the discussion about similarities and differences between the two approaches it is suggested further research in this area that could end up in some more practical guidelines on how to do the requirements definition so that the finally developed ERPs better support adopters' needs.