The document discusses the evaluation stage of developing a new system. It involves testing the system with end users to determine if it is reliable, easy to use, efficient, and fits its intended purpose. User feedback is collected through observation, interviews, and questionnaires to identify any problems or limitations. The analyst then works to solve issues found during testing and incorporates user recommendations to improve the system based on the feedback. The process may repeat with further development, testing, and evaluation cycles.
2. Introduction on Evaluation Stage:
After finishing from developing, testing and implementing your System, it
must be evaluated, or in other words it must be tested by the workers and
see whether the system is good, easy and reliable.
So the hole process can be done in easy questions:-
Was the system reliable and robust ?
Does the system do what it was intended to do?
Is it Easy to Use ?
Is it efficient ?
Is the solution appropriate ?
3. Solving earlier problems
When an earlier problem found in testing stage, it must be evaluated and
solved.
Records from the test stage will be needed to solve these problems
The analyst will make comparisons and comments to make refinements
For eg:- if a workers gets 900$/week, and outage is 90$, the analyst must
check the formula used.
4. Feedbacks
Do you remember how we collected information in the analysis stage ?
3 ways from collecting information stage can be done in feedback
1- Observation:- the analyst will see by himself the user performing on the
new system, maybe by video recording
2- Interviews:- the analyst will interview the users and see their response on
the system and how easy it is to use
3- questionnaires:- The analyst will do a set of question to see the response of
the users with the system and how easy it is.
5. Identifying Limitations
So now after the analyst got the feedbacks, he will know the further issues he
did now find, and he will know if the system met the expectation of the
users.
He will gain the info for how easy or hard the system is from the user’s view
He will record any recommendation from the users to improve the new
system.
All of this will give him the idea of the limitation in the system he created.
There are 2 types of limitations:- 1- Major, eg:- not being able to produce the
output , 2 Minor, eg: colours of the input screen is distracting
6. Making the Improvements
Users are interviewed for the limitations in the new system, to know where
the weak point is, and to get the info of how it can be solved.
The section where the system will be heavily used will be specifically asked
for the extensions they want to be added.
So the system will be improved after knowing the limitations, and the cycle
will go again, Development, test and evaluation.