In order to evaluate whether the project has been successful or not, I shall set some criteria in place which I can I use as benchmarks to determine whether the end result achieves what the project set out to achieve or not. These criteria are listed below:
USABILITY
I need to ensure that the system is easy to use and will be suitable for use within Quick Quotes. To this end, I will conduct some alpha testing by writing out a questionnaire and asking some of my colleagues what they thought of my system after using it. I will ask my colleagues such questions as “Did you feel the instructions were clear enough when you were not certain how to proceed?” or “Did learning how to use the system feel intuitive?”
SUCCESS CRITERIA:
The questionnaire will be graded on a 10 point scale, and I will ask five of my colleagues. If the average score on each question of all of my colleagues’ responses is more than or equal to 8, I will consider this area to be a success.
SUITABILITY
I need to ensure that the system meets the needs of the company and does what it was originally set out to do. To assess this, I will look back at the objectives I set for the project earlier on in the document and check to see whether these objectives have been met.
SUCCESS CRITERIA:
If at least 80% of the objectives have been met I will consider this area of the project to be a success.
PERFORMANCE
I need to ensure that the system performs at optimal capacity and runs as intended. To judge this, I will undertake a testing processing of the system, using a thorough test plan and a set of test data that will be able to discern any errors there might be in the functionality and logic of the system, if there are any. These will of course include typical, extreme and incorrect items of data.
SUCCESS CRITERIA:
If the testing process is successful them the system can be judged to be performing as required. If any problems are identified during the testing process I will have to carry out corrective maintenance on the system to correct the errors.