Group 8: Shenanigans

1. Group 8:Shenanigans Mike Ostrowski Josh Patsey Michelle Boomer Tom Parks Levent Niazi

2. Overview • Our goal was to design and implement software that would modernize restaurant service.

3. Program Features: -Ability to automate ordering -Automated payments -Convenient electronic bookkeeping -Viewing menu electronically (easier to update)

4. Overview

5. Waterfall Model • We used the Waterfall model, and did not include the system testing, acceptance testing, or maintenance in our third phase because of time restraints.

6. Determined Requirements Reviewed Requirements Produced an SRS and User’s Guide Phase 1

7. Phase 1:Requirements Example • The system shall allow the Host to see open and closed tables. Description: The system shall provide a window in which the Host will be able to see open and closed tables. • Inputs: N/A. • Outputs: The open and closed tables are displayed. The open and closed tables have a corresponding table name. • Interfaces: All the tables will be displayed in a grid fashion. Open tables will be green and closed tables will be red. The queue for when all tables are full is in the right side and shows the party’s name and size. In the lower right is the current wait time for a new party. The list of tables will be shows on a screen for the hosts and Wait-staff to see. Performance Requirements: N/A

8. Created an Object Model Created a Use Case Diagram Started designing the program Risk Management completed Made corrections to Phase 1 Created a Test Plan Unit Testing Integration Testing Validation Testing Phase 2

9. Phase 2:Risk Management • Team is Reorganized • Requirements Creep • Unable to Use GUI • Team Member Drops Class • HD Crash

11. Phase 2:Use Cases Examples • Seat Customers • Participating Actor: Host • Entry Condition(s): • ·The Host main window is displayed. • ·There is an available table • ·There is a customer waiting to be seated. • Exit Condition(s): • ·A customer is seated and the table is closed. • Event Flow: • 1. The Host selects the party to be seated from the list on the right. • 2. The Host then clicks on the table where the Customer is to be seated.

12. Phase 3 • Create a schedule for the remainder of the project • Code the program • Make adjustments to the object model and users guide to reflect changes in implementation • Follow the test plan from phase 2 to test the program • Demonstrate the program to verify it’s functionality for the customer • Produce a “Lessons Learned” document to explain what we’ve gained from completing the project • Create a new schedule which accurately reflects how tasks were actually completed and analyzes the time spent • Prepare this presentation for your viewing pleasure

13. GOOD Meeting 3 or more days a week. Developing a way to communicate constantly (ie. email, cell phones, message board) Everyone looks over each others work. BAD Start on code after Phase 2. Integration testing was done too late. Not having set agendas for our meetings. Lessons Learned

14. Conclusion • This project taught us valuable skills for software development including important team skills. • We learned the necessity of accurately determining and understanding requirements at the beginning of any software project. • Our group also realized the importance of planning.

15. Login Screen with Table Number and Customer Menu option Screen Shots

16. Host Screen with Table Availability and Parties Waiting List. Screen Shots

17. Screen Shots • Menu screen with special instructions listed

18. Screen Shots • Customer payment screen

19. GROUP 8 Q & A Josh Levent Tom Michelle Mike