CH 8 Planning, Design, and Implementation of ERP Systems

CH 8 Planning, Design, and Implementation of ERP Systems -...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
Implementation of ERP  Systems
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Traditional System Development Traditional systems development life cycle is the process of automating any legacy system by analyzing the system’s bottlenecks, duplication of effort, inconsistencies, and other problems. The fundamental approach here is to analyze the shortcomings of the system and to develop “new” system, which brings changes in the processes and data and supports the firm’s business requirements. This approach uses process models and data models to analyze current system.
Background image of page 2
Traditional System Development Phases of Traditional System Development Life Cycle are : Step Activities Tools and Techniques Problem definition Identify problems with the current system Interviewing and data collection Feasibility study Asses the need for a system project, including technical, economic, and management feasibility Preliminary cost analysis System analysis Undertake a detailed analysis of the current system, including processes, information flows, and work organization Logical process models- present system; Logical data models- present system; Organization charts (functional hierarchy diagram) System design Development of objectives for the new system; re-engineering of processes and information Logical process model- proposed system; Logical data model- proposed system; Organization charts- proposed systems Detailed design Design of specifications for the proposed system Program design specifications output design; input design database; forms design Implementation Software implementation; training end- users; development of reporting systems; design of controls and security Coding; testing; documentation Maintenance Ongoing technical support; ongoing upgrades and enhancements
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Traditional System Development Traditional systems development life cycle takes too much time and costs too much. It follows a “waterfall” approach, in which there is a sequence of steps, starting with planning and analysis to be followed design, detailed design, and implementation.
Background image of page 4
New Approaches to System Development Traditional systems development life cycle was taking too much time, so new techniques were designed to speed up the development. In late 1980s, Prototyping was introduced as a methodology for obtaining user requirements more quickly and accurately by showing “models” of systems documents to end user. But this approach did not make any significant change in speeding the coding, testing, and debugging phases.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
New Approaches to System Development End-user development was another approach introduced in the mid- to late-1980s. These tools were like packages containing
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 18

CH 8 Planning, Design, and Implementation of ERP Systems -...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online