1. Touch ‘N’ Serve By: Komal Sharma 101191 Presented to: Dr. Robert Zhu Vasudha Godugu 102144 Vishwada Godugu 102145 Avantt Karra 101262 Rakesh Kumar Gunda 101196

2. Introduction: Project scope: Used for restaurants. Changing some dll files this software can be used for any organization. Existing System: Delay in serving Misconception of order More requirement of man power. Proposed System: Enables customer to view the menu on the touch screen and order the items by himself. Customer order is automatically displayed at cook station. Avoids misconception in the bill.

3. Requirement Analysis: Functional Requirements: Central Administration System Table terminal Kitchen Production System Non-functional Requirements: Design constraints: The software is designed in such a way that the customer can easily interact with the GUI. Hardware constraint: LAN card  Cables  Hubs  Switches.

4. Computational Requirements:  Server:  RAM (256MB or 512MB).  Hard disk- 1.5 GB  Pentium 4 processor or higher.  Client:  RAM (128MB or 256MB)  Pentium 3 or Pentium 4 processor.

5. Life-cycle model: Requirements analysis design implementation testing deployment P4 processor, windows XP,.Net, 256MB RAM Uml diagrams Implementing the classes Testing all functionalities Deliver the software

6. Technical Architecture: Admin Terminal: Admin Terminal Database IN T E R F A C EIN T E R F A C E

7. Table Terminal: Table Terminal Database I N T E R F A C EI N T E R F A C E

8. Kitchen terminal: Kitchen Terminal Database I N T E R F A C EI N T E R F A C E

9. Design: Objective: UML represents the collection of best engineering practices that have proven successful in the modeling of large & complex systems. Very important part of developing object oriented & software development process. Helps project teams to communicate, explore potential designs & validate the architectural design of the software.

10. Uml diagrams: Use case diagram: Customer:

11. Kitchen system: Administration system:

12. Class diagram:

13. Sequence diagram: Customer:

14. Central administration system:

15. Kitchen Production System:

16. Activity diagram: Customer:

17. Central Administration System: Kitchen Production System:

18. Screen shots: Welcome Screen – The first screen on the table terminal

19. KPS Terminal – screen showing the items received from table 1. Observe the color change – items in red are order first and items in blue are order just now.

20. Admin terminal: screen showing table status

21. Survey We have been to “Peacock Restaurant” based in fremont where we could collect enough information such as: No.of tables, No. of employees, Salary package…….. What are the requirements?

22. Conclusion: It can be configured for fine dining restaurants, bars & lounges, discos & night clubs and food court with prepaid system, home delivery, quick service/ fast food and cafeterias.