4.3.9 - SDLC - Systems Implementation

HideShow resource information
  • Created by: Annie
  • Created on: 13-05-13 20:01
View mindmap
  • Systems Implementation
    • Parallel Changeover
      • The old system continues to run alongside the new system until the new system is running smoothly
        • The old system is then deactivated
      • Advantage
        • Few chances of disruption to business during the changeover period
      • Disadvantage
        • Problems with keeping data synchronised on two systems
        • Costs of hardware and personnel in running two systems, potentially with each task being done twice
    • Phased Changeover
      • Different parts of the system are brought online on a time schedule
      • Advantage
        • This method allows each module to be separately checked in a "live" environment, reducing the potential disruption from problems that may occur
      • Disadvantage
        • Overall implementation can take a long time
        • Only suitable for systems which can be easily divided into modules
        • Getting the old and new system to work in harmony
  • What is it?
    • Systems Implementation
      • Parallel Changeover
        • The old system continues to run alongside the new system until the new system is running smoothly
          • The old system is then deactivated
        • Advantage
          • Few chances of disruption to business during the changeover period
        • Disadvantage
          • Problems with keeping data synchronised on two systems
          • Costs of hardware and personnel in running two systems, potentially with each task being done twice
      • Phased Changeover
        • Different parts of the system are brought online on a time schedule
        • Advantage
          • This method allows each module to be separately checked in a "live" environment, reducing the potential disruption from problems that may occur
        • Disadvantage
          • Overall implementation can take a long time
          • Only suitable for systems which can be easily divided into modules
          • Getting the old and new system to work in harmony
    • The full working version of the system is now created following the Design Specification
      • This is usually done on separate hardware to the existing live system to allow for extensive testing
        • Testing is done on each part of the system as it is created using "real" data
          • Invalid, correct and extreme data are used for validation testing
            • Testing is then done on the complete system
  • Direct Changeover
    • The company shuts down the old system (at the end of one day) and starts using the new system (the following day)
    • Disadvantage
      • Significant risk of unforeseen problems with the new system meaning you cannot carry on your normal business. If this is the first system of its kind, this is very high risk
  • Pilot Changeover
    • The whole system is implemented at one time but in different branches of the business
      • Usually common in retail businesses where each shop is upgraded to the new system at one time
    • Advantage
      • Technical and training support can be focused upon small parts of the business, gaining expertise in possible problems whilst limiting the potential disruptive effects
    • Disadvantage
      • The time taken for a full changeover can be many months for a large business
        • The old and new systems must be capable of being linked together
  • Advantage
    • Direct Changeover
      • The company shuts down the old system (at the end of one day) and starts using the new system (the following day)
      • Disadvantage
        • Significant risk of unforeseen problems with the new system meaning you cannot carry on your normal business. If this is the first system of its kind, this is very high risk
    • Lower cost with only one set of hardware needed and running multiple systems at one time also requires more personnel

Comments

No comments have yet been made

Similar resources:

See all resources »See all resources »