Group 8:Group 8:ShenanigansShenanigans

Mike OstrowskiMike OstrowskiJosh PatseyJosh Patsey

Michelle BoomerMichelle BoomerTom ParksTom Parks

Levent NiaziLevent Niazi

OverviewOverview

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

Program Features:Program Features:

-Ability to automate ordering-Ability to automate ordering

-Automated payments-Automated payments

-Convenient electronic bookkeeping-Convenient electronic bookkeeping

-Viewing menu electronically -Viewing menu electronically (easier to update)(easier to update)

OverviewOverview

Waterfall ModelWaterfall Model

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

Phase 1Phase 1

Determined RequirementsDetermined Requirements Reviewed RequirementsReviewed Requirements Produced an SRS and User’s GuideProduced an SRS and User’s Guide

Phase 1:Phase 1:Requirements ExampleRequirements Example The system shall allow the Host to see open and closed tables.The system shall allow the Host to see open and closed tables.

Description:Description: The system shall provide a window in which the Host The system shall provide a window in which the Host will be able to see open and closed tables.will be able to see open and closed tables.

Inputs:Inputs: N/A. N/A. Outputs:Outputs: The open and closed tables are displayed. The open and The open and closed tables are displayed. The open and

closed tables have a corresponding table name.closed tables have a corresponding table name. Interfaces:Interfaces: All the tables will be displayed in a grid fashion. Open All the tables will be displayed in a grid fashion. Open

tables will be green and closed tables will be red. The queue for 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 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. 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-The list of tables will be shows on a screen for the hosts and Wait-staff to see.staff to see.

Performance Requirements:Performance Requirements: N/A N/A

Phase 2Phase 2

Created an Created an Object ModelObject Model

Created a Use Created a Use Case DiagramCase Diagram

Started designing Started designing the programthe program

Risk Risk Management Management completedcompleted

Made corrections Made corrections to Phase 1to Phase 1

Created a Test Created a Test PlanPlan– Unit TestingUnit Testing– Integration Integration

TestingTesting– Validation TestingValidation Testing

Phase 2:Phase 2:Risk ManagementRisk Management Team is ReorganizedTeam is Reorganized Requirements CreepRequirements Creep Unable to Use GUIUnable to Use GUI Team Member Drops ClassTeam Member Drops Class HD CrashHD Crash

Phase 2:Phase 2:Use Cases ExamplesUse Cases Examples Seat CustomersSeat Customers Participating ActorParticipating Actor: Host: Host    Entry Condition(s):Entry Condition(s):                 The Host main window is displayed.The Host main window is displayed.                 There is an available tableThere is an available table                 There is a customer waiting to be seated.There is a customer waiting to be seated.    Exit Condition(s):Exit Condition(s):                 A customer is seated and the table is closed.A customer is seated and the table is closed.    Event Flow:Event Flow: 1. The Host selects the party to be seated from the list on the right.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 2. The Host then clicks on the table where the Customer is to be

seated.seated.

Phase 3Phase 3

Create a schedule for the remainder of the projectCreate a schedule for the remainder of the project Code the programCode the program Make adjustments to the object model and users Make adjustments to the object model and users

guide to reflect changes in implementationguide to reflect changes in implementation Follow the test plan from phase 2 to test the programFollow the test plan from phase 2 to test the program Demonstrate the program to verify it’s functionality Demonstrate the program to verify it’s functionality

for the customerfor the customer Produce a “Lessons Learned” document to explain Produce a “Lessons Learned” document to explain

what we’ve gained from completing the projectwhat we’ve gained from completing the project Create a new schedule which accurately reflects how Create a new schedule which accurately reflects how

tasks were actually completed and analyzes the time tasks were actually completed and analyzes the time spentspent

Prepare this presentation for your viewing pleasurePrepare this presentation for your viewing pleasure

Lessons LearnedLessons Learned

GOODGOOD Meeting 3 or more Meeting 3 or more

days a week.days a week. Developing a way to Developing a way to

communicate communicate constantly (ie. constantly (ie. email, cell phones, email, cell phones, message board)message board)

Everyone looks over Everyone looks over each others work.each others work.

BADBAD Start on code Start on code

after Phase 2.after Phase 2. Integration Integration

testing was done testing was done too late.too late.

Not having set Not having set agendas for our agendas for our meetings.meetings.

ConclusionConclusion

This project taught us valuable skills This project taught us valuable skills for software development including for software development including important team skills.important team skills.

We learned the necessity of accurately We learned the necessity of accurately determining and understanding determining and understanding requirements at the beginning of any requirements at the beginning of any software project.software project.

Our group also realized the importance Our group also realized the importance of planning.of planning.

Screen ShotsScreen Shots

Login Screen Login Screen with Table with Table Number and Number and Customer Menu Customer Menu optionoption

Screen ShotsScreen Shots

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

Screen ShotsScreen Shots

Menu Menu screen screen with with special special instructioinstructions listedns listed

Screen ShotsScreen Shots

Customer Customer payment payment screenscreen

GROUP 8 GROUP 8 Q & AQ & A

Josh Levent

Tom

Michelle Mike