Homework1

Homework 1

List of user roles

• Trainee (demo functionality)
• Waiter (limited functionality)
• Head waiter (extended functionality)
• Restaurant administrator (full control of his restaurant)
• Company administrator (full control of all company restaurants)
• Company financial specialist (limited, access to all reports)
• System administrator (technician with full access)

Waiter interview

1. Do clients have to pay for the order immediately, or the bill can be left open? -- They can pay immediately, but they don't have to.
2. Should the POS system calculate the money to give back to the client? -- Yes, it should definitely do that.
3. Can the bill be divided into several bills later? -- Yes, of course.
4. Should waiters be able to hand the bill over to the other waiter? -- Yes, they should.
5. Should the system support credit cards? If yes, then which credit cards? -- Yes, we should support Visa, MasterCard and American Express.
6. Is it possible to change an order? -- Yes, of course.
7. Should we support the printing of bills? -- Yes.
8. Must there be automatic fraud prevention in place? -- No, it must not.
9. Should we include credit card tipping feature? -- Yes.
10. Should we include an option of sending receipts to email? -- Yes, we should
11. Should it be possible to undo anything after payment has been accepted? -- No, this kind of action is a head waiters privilege.
12. Should clients get discounts? -- Yes. Discount is applied through reading the client's partner card.
13. Should the POS solution feature a barcode scanner? -- No.
14. How many transactions are usually processed at a time at peak load? -- Around 25.
15. The POS software should be portable so waiter can use it on the go on a smartphone or tablet. -- Yes, of course.
16. Do you prefer a browser version or an offline cloud solution? -- I don't really care but, if I have to choose then the offline cloud solution.
17. If there is a need for apps, should they be for Android or iPhone? -- Both. Windows Mobile as well.
18. Should menu items be (re)arranged by the waiter? -- Yes, they should have option to rearrange items.
19. Should the waiter get alerts when some products are out of stock? -- Yes, of course.
20. Should the POS help the waiter make suggestions to clients? -- No.
21. I presume you want an "intuitive user interface"? -- It should be easy enough.
22. Should our company provide training for you? -- No, I get training from restaurant staff.
23. Should we make the interface customizable? -- Well, yes it would be cool, but not so important.
24. Should the POS system give a notification when the waiter is out of change money? -- Yes.

Head waiter interview

1. Should the POS system be integrated with a smart cash drawer device? -- Yes, it would be comfortable.
2. Should the information on initial and final states automatically be submitted to management? -- It would be nice.
3. Should the information be stored in history? -- Yes, but longer than three months is not necessary.
4. Should the opening and closing of the cash register drawer be controlled by the software? -- Yes, there should be a button for it.
5. Should we include a “training mode” feature? -- Yes, maybe for a special user (student), to try out the system, but not to actually interact with the real one.
6. Do you need documentation and tutorials in many languages? -- No, English is enough.
7. Do you need us to organize training for head waiters? -- The first training, yes, and if needed, some more after.
8. Should the head waiters get to track what the waiters are doing in real time? -- No, I don’t think that is important.
9. Should the POS software allow the head waiter to take reservations? -- Yes, it is very important.
10. Should the POS software help the head waiter take the reserved guests to their tables? -- No, that is not important.
11. Is there going to be a guest blacklist (e.g. beer addicts and bad check givers)? -- Yes, it should alert, if there is a blacklist person trying to get a reservation.
12. Is there going to be a VIP list (best customers that make big orders)? -- Yes, it should alert if a VIP makes a reservation.
13. Should the head waiter be able to distribute tasks to the waiters with the POS software? -- Yes.
14. Should the POS software help monitor air conditioning, beer temperature etc? -- That would be nice.
15. Should the POS software help the head waiter to arrange tables and chairs? -- No, that is not necessary.
16. Should the POS system register any customer complaints? -- That would be helpful.
17. Should the system send a notification when the summary of the day is done? -- Yes, it is very useful if head waiter cannot make a summary himself.
18. Should the POS system help to count waiters work hours? -- Yes, it should
19. Should the POS system count working overtime as well? -- Yes, of course.
20. Can head waiter edit product prices? -- Yes.

Restaurant manager interview

1. Should the system generate individual employee performance reports? -- Yes.
2. Can employees themselves see how they compare to others? -- No.
3. Should the POS software help find out which products are popular? -- Yes, that is important.
4. Should it provide forecasting analytics on that? -- Yes, it should.
5. Should the POS system alert the restaurant manager when stock levels are low? -- Yes, and head waiter as well.
6. Is there a need for an automated stock replenishment solution? -- No, not needed. Notifications shall do.
7. Should the POS software keep track of the stock state of secondary goods such as glasses, paper napkins and cleaning supplies? -- Yes, it should.
8. Are there going to be marketing materials sent to customers? -- Yes.
9. Can clients decline being sent advertisements (unsubscribe)? -- Yes, if they want to.
10. Should the POS software help post social network updates? -- No, that is not important.
11. Should the POS software store a detailed sales history for each client? -- Yes, it should be tracked through the partner card.
12. Is there a need for customer-specific pricing? -- No, there is not.
13. Should the POS software be linked to accounting software? -- Yes, it should, but only daily submissions are important.
14. Is there a need for payroll integration? -- No need for that.
15. Should the software help meet local financial reporting requirements? -- No, this is not important.
16. Should the system help to generate financial reports on sales summary, hourly income etc? -- Hourly summaries are not needed, but the POS software should have an opportunity to see sales summaries when needed.
17. Should the POS software help compile staff control and drink/food control reports? -- No this is not needed.
18. Should it generate stock status reports? -- Yes, it should.
19. Should each waiter have a profile? Should it be easy to add new instances of waiters, remove old ones etc? -- Yes, profiles are necessary.
20. Should the POS software help manage a weekly schedule of tasks and coordinate the operation of the entire restaurant in real time? -- No, this is not necessary.
21. Should there be some features to help recruit and train staff? -- Help in recruit is not necessary, but a student account for learning is good to have.
22. Can waiters change the menu if needed? -- Only head waiters.
23. Should it be possible to group beers by brand, type and alcohol percentage? -- Yes, this is a good feature.
24. Should there be an option to print menus or export the list for use in Photoshop to design the menus? -- Yes, it should be possible.

Company administrator interview

1. Should the POS system feature national comparison? -- No comparison needed.
2. Should the POS system generate detailed sales summaries? -- Yes, this is necessary.
3. Should it provide hourly statistics? -- No hourly statics needed, daily or even monthly preferred.
4. Should it provide merchandising reports? -- No, not needed.
5. Should the reports be exportable to Excel? -- Yes, it should.
6. Should the system support different interface languages for different countries? -- Yes.
7. Should the company administrator have a feature to give permissions to the restaurant manager to use POS system? -- Yes, the company administrator should have a feature to give and take away permissions of a certain restaurant manager.
8. Should there be different regional price lists? -- Yes there should be. e.g. there should higher prices in the regions where the welfare is better.
9. Should it have multi tax rate support? -- Yes, it is needed, if you use the POS system in a different country and the tax rate system needs to be altered. Restaurant manager can change it manually.
10. Should it have multi currency support? -- Yes, the same as tax rate system.
11. Should it meet corporate financial reporting requirements? -- Yes.
12. Should it give an overview about worker in the company? -- Yes, it should.
13. Should there be a supplier database of prices etc? -- If possible, this would be good.
14. Should it generate vendor comparison reports? -- Also if possible.
15. Should it allow management of multiple stock locations? -- Yes, it would be comfortable.
16. Should it allow to manage transfers between locations? -- Yes, it should be allowed. If one restaurant needs something then it should send a request to stock manager.
17. Should it be easy to add functions? -- That would be very good for the future.
18. Should it allow new restaurants and new countries to be added? -- Yes, it should.
19. Should it be portable on different platforms? -- Yes, it should.
20. Which ones? -- It should be available for use on a mobile phone or tablet as well.

Functional requirements (waiter)

1. The POS system should print out bills right after the clients pay.
2. The POS system should be able to print out additional bills if the staff needs it.
3. The POS system should be able to send the bill to an e-mail account if needed.
4. The POS system should support dividing the bill.
5. The POS system should calculate the money to give back to the client.
6. The POS system be able to add an arbitrary tip to the bill when paying with credit card.
7. The POS system should be able to exchange open bills within the personal.
8. The POS system should read partner cards and make discounts.
9. The POS system should be able to alert the waiters if something is out of stock.
10. The POS system should be able to change the order.

Functional requirements (head waiter)

1. Head waiter should be able to record cash register initial and final states.
2. The POS system should keep a record of all actions for at least three months.
3. The POS system should help the head waiter with the training of new people with a student mode or account, without making any real actions.
4. The POS system should help the head waiter to take reservations and manage the reservations.
5. The POS system should notify about VIP people and blacklist people reservations.
6. The POS system should allow the head waiter to give orders and tasks to other restaurant staff.
7. The POS system should help with the restaurant atmosphere, like lighting, music and temperature.
8. The head waiter should be able to register customer complaints in POS system.
9. The POS system should help the head waiter to keep track with the staff working hours and overtime hours.
10. The POS system should give the head waiter the statistics of the day at the end of the shift.

Functional requirements (restaurant manager)

1. Restaurant manager should be able to order goods with the POS system from the warehouse.
2. The POS system should generate individual employee performance reports.
3. The POS software should track which products are popular and it should provide forecasting analytics on that.
4. The POS system should alert the restaurant manager and head waiter when stock levels are low.
5. The POS software should keep track of the stock state of secondary goods such as glasses, paper napkins and cleaning supplies.
6. The POS software should help send advertisements and special offers to customers patrons via email.
7. The POS system should facilitate price list management. It should allow local management to change regular prices, happy hour prices etc.
8. The POS software should send daily submission to accounting software.
9. The POS software should have an opportunity to see sales summaries when needed.
10. The POS system should generate stock status reports.
11. The POS software should facilitate employee and task management. It should have an opportunity for waiters to have a profile and manager should have easy option to add new instances of waiters or remove old ones etc.
12. The POS System should have an option to print and design menus.

Functional requirements (company administrator)

1. POS should support multiple interface languages for different countries.
2. The POS software should enable company administration to get different reports for each particular restaurant and arbitrary groups of restaurants.
3. The POS system should generate detailed sales summaries.
4. The POS system should export reports into Excel.
5. The POS system should help the company administrator to give permissions to the restaurant manager to use POS system.
6. The POS software should help to design and put different price lists in different regions.
7. The POS system should support multi tax rate system.
8. The POS system should support different currencies.
9. The POS Software should help to meet corporate financial reporting requirements.
10. The POS system should help to have an overview of workers in the company.
11. The POS system should allow all roles to be able to add new customers to customer database.
12. The POS system should have a supplier database of prices.
13. The POS system should generate vendor comparison reports.
14. The POS system should allow managing multiple stock locations.
15. The POS software should allow transfers between different stocking locations if restaurant manager sends a request.
16. It should be easy to add functions to POS system.
17. The POS system should allow new restaurants and new countries be added.
18. The POS system should be portable on different platforms.

SMART usability

1. The system should support both touch-screen input and mouse input.
2. The system should run on iPhone, iPad and Android devices.
3. System font should support Unicode characters.
4. No orderable item should be deeper than 4 layers of menus.
5. Should be easy enough to learn with 3 hours.

SMART performance

1. Standard display resolution should be 1024 pixels wide.
2. System should be working in real time.
3. In case of system update system should not freeze for more than 5 minutes.
4. System should take maximum 5 seconds to update stock numbers in the database.
5. System should be able to service at least 25 concurrent operations (for stability during rush hours).