ERP systems implementation
•Descargar como PPT, PDF•
2 recomendaciones•3,088 vistas
![INTRODUCTION- ERP SOFTWARE SOLUTION ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a ERP systems implementation
Similar a ERP systems implementation (20)
Más de Dr. C.V. Suresh Babu
Más de Dr. C.V. Suresh Babu (20)
Último
Último (20)
ERP systems implementation
- 3. Dietmar-Hopp-Allee 16 69190 Walldorf, Germany
- 8. R/3
- 9. Module
- 10. R/3 Real Time Three Tier Architecture
- 11. Architecture
- 15. DeLone & McLean (Updated) Model of Information Systems Success
- 16. Unified Theory of Use and Acceptance of Technology (UTAUT)
- 20. Playing Catch-up with User Needs FUNCTIONALITY TIME User Needs Actual System Capabilities t 0 t 1 t 3 t 2 t 5 t 4
- 21. SAP R/3 TYPICAL BUSINESS BLUEPRINT
- 23. ERP Critical Success Factors
- 24. THANK YOU
Notas del editor
- Standish Group International (1995) CHAOS Report
- Keen, P. G. W. (1991) Relevance and Rigor in Information Systems Research: Improving Quality, Confidence, Cohesion and Impact. In Nisson, H.-E. et al. (eds), Information Systems Research: Contemporary Approaches and Emergent Traditions, pp. 27-49. Elsevier Science Publishers.
- At time t0, the need for a system is recognised and development commences, with relatively incomplete knowledge of the real user needs at that time. By t1, an operational system has been produced, but not only does it fail to satisfy user needs at t1, it fails even to satisfy needs as specified at t0. The system is then subjected to a series of maintenance enhancements between t1 and t3, which enable it to satisfy the original needs (at t2). At time t3, the cost of reworking the system is so great that it is decided to rebuild from scratch. This redevelopment is complete by t4, and the cycle recommences. Davis, A.M., Bersoff, E. H. & Comer, E. R. (1988) A Strategy for Comparing Alternative Software Development Lifecycle Models, IEEE Transactions on Software Engineering , 14(10) October Xeno’s Paradox: the tortoise is given a significant headstart; once the hare has covered the initial distance that separated him from the tortoise, the tortoise is no longer there and has moved a little further; again, once the hare covers that marginal distance, the tortoise has moved a little further still, so how does he ever catch the tortoise ? (easily dispelled by Newton’s Laws of Motion)
- Motwani, J., Subramanian, R. & Gopalakrishna, P. (2005) Critical factors for successful ERP implementation: Exploratory findings from four case studies. Computers in Industry. 56(6), 529-544.
- Finney, S. & Corbett, M. (2007) ERP implementation: a compilation and analysis of critical success factors. Business Process Management Journal. 13(3), 329-347.