Systems Implementation Techniques

Systems Implementation Techniques

Implementation Approaches

  • Direct changeover entails replacing an old system with a new one instantly. High risks are involved due to the sudden shift.
  • Parallel running sees an organisation running both the old and new systems together, ensuring the new system works correctly before the old one is retired.
  • Phased implementation involves implementing parts of the new system gradually, which can help to minimise disruption but may be lengthy.
  • Pilot implementation runs the new system within a small section of the organisation before a full rollout.

Programming Tools and Techniques

  • Integrated Development Environments (IDEs) combine programming tools in a single graphical user interface to increase developer productivity.
  • Object-oriented programming (OOP) allows the building of complex systems using objects and classes, promoting code reuse and encapsulation.
  • Procedural programming structures code into procedures or functions, which is useful when multiple routines share code.
  • Declarative programming focuses on what the program should accomplish without specifying how, primarily used in databases and logic programming.

Systems Testing

  • Unit testing validates each piece of a system for functionality. This is the first level of testing, done at a microscopic level.
  • Integration testing combines individual units and tests them as a group to expose faults in the interaction between units.
  • System testing assesses whether the whole system meets the specified requirements, often done by independent testers.
  • Acceptance testing checks if the system satisfies the customer requirements, usually done by the end-users.

Maintenance Techniques

  • Corrective maintenance includes modifications and updates done to make the systems functional and effective after delivery.
  • Adaptive maintenance involves adapting the system to any changes in the software environment (e.g., system software, hardware, external interfaces)
  • Perfective maintenance includes enhancements, new functionalities, optimisation, and modifications based on customer feedback.
  • Preventive maintenance aims to identify and correct latent faults in the system before they become effective faults.

Documentation

  • User manuals guide users on how to use the software and troubleshoot common issues.
  • Technical documentation assists developers in understanding, maintaining, and updating the software. It includes software architecture, code, and API documentation.
  • Maintenance documentation provides information necessary for system support and preventive activities, including a detailed description of the system and its components, and end-user feedback.