evaluation

Read each statement and identify which is the correct one in relation to the ‘Evaluation’ stage.

• • Look at different solutions to solve the problem.

• • Document the opinions of users and testers using the solution.  

• • Test your solution following a test strategy stated in the design section.

Read each statement and identify which is the correct one in relation to the ‘Evaluation’ stage.

• • Define the problem.

• • Choose one solution and justify choice.

• • Compare final solution with the objectives set out in the analysis section.

Read each statement and identify which is the correct one in relation to the ‘Evaluation’ stage.

• • State any enhancements and improvements that could be implemented.

• • Use diagrams to illustrate success with the solution.

• • Use validation techniques to ensure everything is working.

• Can you pick out those that apply particularly to the evaluation stage?

• • Ensure all staff are trained to operate the new system.

• • Outline the objectives of the system proposed.

• • Find any hardware faults or software bugs and correct them.

Can you pick out those that apply particularly to the evaluation stage?

• • Identify any limitations and necessary improvements to the system.

• • Test the system before implementation.

• • Identify the inputs, outputs and processing of the current system.

Can you pick out those that apply particularly to the evaluation stage?

• • Document the opinions of users and testers using the solution.

• • Design a complete test strategy for a system.

• • Ensure results produced match the design section predicted outcomes.

Can you pick out those that apply particularly to the evaluation stage?

• • Use interview techniques to find out who the potential users are going to be.

• • Justify the choice of the system.

• • Record the efficiency and appropriateness of the solution.

Name the stage of the SDLC where recommendations are made to change or update the hardware, software, systems or working procedures.

Identify which of the following questions would not be asked when evaluating a system.

• How many lines of program code does the software have?

• Is the system efficient?

• Does it meet the user’s requirements?

• Is it easy to use?

Typical evaluation approaches may include:

• ​ (a)    the system to generate performance and usage reports.

• Reviewing the system for ​ (b)   and ease of use.

• Gathering user ​ (c)   to identify and fix any problems.

• Identifying any ​ (d)   the system may have and taking appropriate remedial action.

• ​ (e)    the system to the originally documented to ensure.

• requirements to ensure they have been fully implemented.

• Monitoring
• efficiency
• feedback
• limitations
• Comparing