Please enable JavaScript.

Coggle requires JavaScript to display documents.

Testing and Installation (Testing (Types of Testing (Unit Testing (Testing…

- - - - Testing each parts of the system to verify that each part is working properly.
    - - Units are combined and tested as a group, it also tests if the link between the units are also working.
    - - Testing hardware and software and test the system as a whole.
    - - Testing the system in its operating environment by users and making sure the requirements are met.
    - - Testing by the developers which will allow to find errors.
    - - Performed by the developer and data chosen by the developer. They build tests to identify errors.
    - - Users tests the system in their operating environment using live data.
- - - - New system available to client and users immediately.
      - The cheapest method.
      - No need to keep duplicate sets of data.
    - - The most risky method as there is now system to fall back on if new system fails.
      - Have to transfer all data from old to new.
      - Period of time there is no system as the old has to be turned off for new to be turned on.
  - - - Less risky as there is the old one to fall back on if the new one fails.
      - Less stress for staff as they still have the security of the old system.
      - Staff have to take their time learning to use the new system.
    - - Time consuming.
      - One system may be out of sync.
      - Extra cost for maintaining 2 systems
  - - - Small part of the company is affected.
      - Any problems are identified without affecting the whole company.
    - - Extra work for IT staff.
      - The chosen department will have the same disadvantages of direct.
  - - - Less risk of the whole system going wrong.
      - Staffs are introduced to the changes in small stages.
    - - Takes a long period of time.
      - Users ask for changes and hold up the installation of the next phase.
      - Difficult to integrate the old and the new system.