A System Development Methodology for ERP Systems

An ERP (Enterprise Resource Planning) project is considered highly risky, since it is large, complex, usually unfamiliar to the organization and implemented under a tight timetable. It usually entails process reengineering and many changes. To reduce the risk and improve the probability of project success, an organization can use a structured development approach for such a project, beginning with the selection stage and culminating in the operation stage. There are several conventional structured development approaches. The major ones are the ISDLC model, the prototyping approach and the software package life cycle model. The implementation of an ERP system requires a new methodology that combines components from each of the above approaches. The model suggested in this paper is comprised of four stages: (1) selection; (2) definition; (3) implementation; and (4) operation. Several organizations that have adopted this structured methodology have evidenced a successful ERP implementation

[1]  Steven L. Alter,et al.  Information Systems: A Management Perspective , 1991 .

[2]  Niv Ahituv,et al.  The benefits of using information systems , 2000, CACM.

[3]  C. Wiseman Strategic Information Systems: Trends and Challenges over the Next Decade. , 1988 .

[4]  Niv Ahituv,et al.  Principles of information systems for management (2nd ed.) , 1986 .

[5]  Maryam Alavi The evolution of information systems development approach: some field observations , 1984, DATB.

[6]  Niv Ahituv,et al.  Identifying the value and importance of an information system application , 1996, Inf. Manag..

[7]  Shouhong Wang,et al.  The Implementation of Business Process Reengineering , 1995, J. Manag. Inf. Syst..

[8]  Justus D. Naumann,et al.  Prototyping: the new paradigm for systems development , 1982 .

[9]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[10]  Henry C. Lucas,et al.  Implementing Packaged Software , 1987, MIS Q..

[11]  Edward J. Garrity,et al.  The Application of Prototyping to Systems Development: A Rationale and Model , 1986, J. Manag. Inf. Syst..

[12]  L. Douglas Smith,et al.  Prototyping for Systems Development: A Critical Appraisal , 1985, MIS Q..

[13]  Edward G. Cale,et al.  Factors affecting the implementation outcome of a mainframe software package: A longitudinal study , 1994, Inf. Manag..

[14]  Charles R. Franz,et al.  User Leadership in the Systems Development Life Cycle: A Contingency Model , 1985, J. Manag. Inf. Syst..

[15]  Michael J. Ginzberg,et al.  Barriers to the Adoption of Application Software Packages , 1984 .

[16]  F. Sample Strategic information systems. , 1994, Medical group management journal.

[17]  Vladimir Zwass,et al.  Foundations of information systems , 1997 .

[18]  S. Hyunsik,et al.  A Process Model of Application Software Package Acquisition and Implementation , 1996, J. Syst. Softw..

[19]  Richard J. Schonberger,et al.  MIS Design: A Contingency Approach , 1980, MIS Q..