1 / 24

FIPOS:Food Industry Point Of Sale

FIPOS:Food Industry Point Of Sale. Final Project Presentation April 26, 2011. Presentation. Initial Idea Scope of the project Iteration Process System Architecture Use Cases. Initial Idea. The restaurant business has a need for a system to run the business efficiently

jody
Download Presentation

FIPOS:Food Industry Point Of Sale

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIPOS:Food Industry Point Of Sale Final Project Presentation April 26, 2011

  2. Presentation • Initial Idea • Scope of the project • Iteration Process • System Architecture • Use Cases

  3. Initial Idea • The restaurant business has a need for a system to run the business efficiently • The software should be open source, so it can be modified and continually improved • This should be role based, with users having only required privileges • The system should use an external database

  4. Project Scope • The system will reside on the local Intranet. • Be accessible from a computer with an internet connection using a web browser. • Allow a user to be created, removed, modified, viewed, and searched. • Allow a user to login and logout of the system. • Allow the user to perform tasks that their role will allow (defined in use cases). • Provide a role hierarchy in order to limit user privileges and keep the system secure. • Allow the management to generate reports based on the register data. • Keep track of store discounts. • Provide menu item driven sale entry methods. • Maintain user-entered data in a database structure.

  5. Iteration Process

  6. System Architecture Class Diagram r.171

  7. System Architecture Class Diagram r.179

  8. System Architecture Class Diagram r.180

  9. System Architecture Class Diagram r.204

  10. Functional Requirements • System shall authenticate a user and record “login” and “logout” times. • Register and Management Users shall be able to view, create, and modify Orders. • Management Users shall be able to void orders and manage reports, users, discounts, menu items, and configure local sales taxes • Service Line Users shall be able to view a static representation of an Order and mark an order as completed. • System shall provide searching and sorting functionality for orders, discounts, menu items, and users. • System shall have the ability to back up data.

  11. Non-Functional Requirements • The Database shall manage the system data. • Database shall not store authentication information in plain text. • Database shall provide an interface for manipulating system data. • System shall be accessible to all authorized users from anywhere within the restaurant intranet. • System shall be accessible from a computer with an intranet connection using a web browser. • System shall provide a role hierarchy in order to limit user privileges and keep the system secure.

  12. Actors Insert text here about general user. Insert text here about register user. Insert text here about service line user. Insert text here about management user.

  13. System Architecture 1/2 • Add text about top level package view here.

  14. System Architecture 2/2

  15. Top Level Use Case Diagram

  16. Activation Use Case (UCD-1) • Text about UCD-1

  17. Manage Users Use Case (UCD-2) • Text about UCD-2

  18. Manage Store Data Use Case (UCD-4) • Text about UCD-4

  19. Mange Order Use Case (UCD-5) • Text about UCD-5

  20. Manage Reports Use Case (UCD-6) • Text about UCD-6

  21. Manage Register Use Case (UCD-7) • Text about UCD-7

  22. Future Upgrades

  23. Lessons Learned

  24. Conclusion

More Related