Systems Life Cycle: Evaluation
Assess the efficiency of the solution:
- Evaluate the system's performance in terms of resource usage, time, and cost. Consider whether the system is operating optimally or if improvements could be made to its efficiency
- Provide examples of specific aspects that contribute to the system's efficiency
- Identify areas that may be consuming excessive resources or time, and suggest ways to optimise them
- Questions to ask:
- Does it operate quicker than the previous system?
- Does it operate by reducing staff time in making bookings?
- Does it operate by reducing staff costs?
- Does it operate quicker than the previous system?
Evaluate the ease of use
- Examine how user-friendly and accessible the solution is for its intended audience. Assess whether the system is easy to learn and use, and if users can accomplish their tasks without difficulty
- Describe the user interface and how it facilitates interaction with the system
- Mention any feedback from users regarding their experience with the system, and address any issues they encountered
- Questions to ask:
- Are all the users able to use the system and make bookings easily?
- Are all the users able to change and cancel bookings easily?
- Can all staff understand how to use the system with minimal training?
- Are all the users able to use the system and make bookings easily?
Determine the appropriateness of the solution:
- Compare the implemented solution with the original task requirements and evaluate how well it meets the intended purpose
- Outline the initial objectives of the system and discuss how the solution addresses each one
- Highlight any requirements that may not have been fully met and discuss possible reasons for this
- Questions to ask:
- Is the system suitable for each of the departments?
- Does it meet the needs of the customers?
- Does it meet the needs of the staff?
- Does the solution match the original requirements?
- Is the system suitable for each of the departments?
Gather and analyse user feedback:
- Collect users' responses to the results of testing the system. Their feedback can provide insights into potential issues and improvements, and help determine overall user satisfaction
- Summarise the testing process, including test data, expected outcomes, and actual outcomes
- Discuss users' reactions to the system, addressing any concerns or suggestions they may have
Identify limitations and propose improvements:
- Based on the analysis of efficiency, ease of use, appropriateness, and user feedback, identify any limitations in the system and suggest necessary improvements
- List the limitations and provide explanations for each one
- Recommend specific changes or enhancements that could address these limitations and improve the system
Worked example
Tick three evaluation strategies that need to be carried out following the implementation of the new system.
[3]
| Tick | |
| Observe users operating the old system. | |
| Compare the final solution with the original requirements. | |
| Design the report layout. | |
| Check user documentation to see if it is correct. | |
| Interview users to gather responses about how well the new system works. | |
| Test the system works correctly. | |
| Identify any necessary improvements that need to be made. | |
| Design error handling. |
| Tick | |
| Observe users operating the old system. | |
| Compare the final solution with the original requirements. | χ |
| Design the report layout. | |
| Check user documentation to see if it is correct. | |
| Interview users to gather responses about how well the new system works. | χ |
| Test the system works correctly. | |
| Identify any necessary improvements that need to be made. | χ |
| Design error handling. |
