2.  Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found until it is being used by a large number of people or an unusual situation occurs.  Evaluation is really re-analysing - starting the same systems analysis process all over again. Many of the same techniques can be used, such as interviewing staff or sending out questionnaires.

3.  Efficiency  Ease of use  Appropriateness of the solution Systems analysis and design is a cycle and ends with evaluation which might then become the first stage in the new cycle.

4. Compare the final solution with the design objectives i.e the original task requirements - A good evaluation will always start by comparing the system which has been produced with the original problem and requirements of the solution. Ensure that the solution does the job it’s meant to do in the way it’s meant to do it, as recorded in the analysis and the requirements specification Establish any limitations of the system and any improvements that may need to be made to the system. This is the point at which faults with the system (found during the testing stage) are identified. There should then be suggestions as to how these faults should be rectified. Evaluate the users‘ responses to the system. As well as testing the system with data, the future users of this system need to have the opportunity to test it out and identify problems which the systems analyst might have failed to spot.

6.  User documentation will be written to help users become familiar with the new system.  There is often two types of documentation:  User manual  Technical manual

7. User manualTechnical manual The purpose of the program Loading and running the programHardware and software requirements How to use the program: entering data, saving, editing, sorting, printing... Limitations of the program Input and output formatsFile structures Hardware and software requirementsProgram coding Limitations of the programVariables Error messagesDataflow diagrams TroubleshootingValidation routines Frequently asked questionsProgram and system flowcharts

8.  Once a system is running correctly it can still need maintenance. This may be because a bug is found or because the company needs a new feature.

9.  Testing  Systems are tested to ensure they work properly  There are 3 types of data which can be used to test a system – Typical, extreme and invalid / erroneous.  Evaluation  Systems should be evaluated to ensure that they meet the objectives set. This could be done through interviews, surveys or questionnaires.  Documentation  User manuals and technical manuals are produced to help the people who work with the software.

10. Problem identification Analysis & feasibility study Design Development and testing Implementation Maintenence

11.  http://www.igcseict.info/theory/8/test/  http://www.igcseict.info/theory/8/eval/  http://www.igcseict.info/theory/8/docs/