SMART requirements to usability and performance - alajal/soft6 GitHub Wiki
Usability:
New waiter must be able to perform activities such as taking an order, performing billing etc having familiarized him-/herself with the program for only 30 minutes.
Inserting orders has to be very easy, it has to be possible during the conversation with the customer. The buttons should be big enough to prevent misclicks and this should result in a maximum of 5 user input errors per week.
90% of users have to be able to use the system without asking for help more often than once a month.
All statistics available to administrative personnel should be complemented with graphs and charts.
Filling an order form for goods should take 15 minutes on average. No more than 30 minutes on 99% of the cases.
Performance:
System should be able to handle 50 simultaneous orders in any restaurant without slowdown. It should be able to handle 100 orders with up 50% delay on querying/response times.
Waiter clicks (on tablet when taking order) should show response under 0.5 seconds on 98% of the cases.
Generating sales report for one restaurant (for manager) for one month should take less than 5 seconds on 98% of the cases. Each additional month should add no longer than 1 second to the generation time.
Consecutive system downtime in any restaurant during working hours must not be over 10 minutes. Total downtime for one restaurant during working hours must not be over 1 hour per calendar month.
Waiter tablet must last for 7 hours (one shift) without charging.