SlideShare une entreprise Scribd logo
1  sur  6
RESTAURANT MANAGEMENT
SYSTEM
Epics and User Stories
Milind Gokhale; Shruthi Katapally; Vimalendu Shekhar; Shrijith Pillai;
Megha Mukim; Akshay Jarandikar
Abstract
This document outlines the user stories thought so far to accomplish thebasic features of a
restaurantmanagement system.
Epics and User Stories
Contents
Epic 1: Order creation.........................................................................................................................2
Acceptance criteria:........................................................................................................................2
Epic 2: Order queue and delivery.........................................................................................................2
Acceptance criteria:........................................................................................................................2
Epic 3: Order Completion....................................................................................................................2
Acceptance criteria:........................................................................................................................3
Epic 4: Menu Management .................................................................................................................3
Acceptance Criteria:........................................................................................................................3
Epic 5: Manage restaurant information................................................................................................3
Acceptance Criteria:........................................................................................................................3
Epic 6: Reporting per outlet.................................................................................................................3
Acceptance Criteria:........................................................................................................................3
Epic 7: Reporting for chain ..................................................................................................................4
Acceptance Criteria:........................................................................................................................4
Epic 8: Inventory Management for restaurant......................................................................................4
Acceptance criteria:........................................................................................................................4
Future Epics .......................................................................................................................................4
9. Marketing campaign managementfor restaurant outlet................................................................4
10. Marketing campaign management for the chain .........................................................................4
11. Personalization for user/customer by maintaining the order history and preferences ...................4
Epic 1: Order creation
1. as a customer: I should be able to browse through the menu and look at the various food options
available in the restaurant along with the price for each item.
2. as a customer: I should be able to select items from the menu and add them to my cart/order.
3. as a customer: I should have cart containing all the chosen items so far, accessible all the time.
5. as a customer: I should be able to remove items from my cart or increase item count.
6. as a customer: I should be able to cancel my entire order.
7. as a customer:Ishouldbe abletoview theitemizedbillformyorderalongwiththe pricesforeachitem
and the tax applied.
8. as a customer: I should be able to see the approximate delivery time.
4. as a customer:Ishouldbe able toseetopsellingitemsinthe restaurantwhile choosingmyorderitems.
Acceptance criteria:
Categorized Menu with prices is visible and enabled with selection choices, as soon as the customer
chooses items, the order is created in the database and is visible to the customer.
Epic 2: Order queue and delivery
1. as a chef: I should be able to view the current queue of orders.
2. as a chef: I should be able to accept the orders.
3. as a chef: I should be able to update the order status to ready once the order is prepared.
4. as a restaurant manager: I should be able to view the current queue of orders (in read-only mode).
5. as a waiter: I should be able to view the current order queue to see the ready orders for pick up.
6. as a waiter: I should be able to mark the order as picked up on the common queue.
Acceptance criteria:
The order queue isvisible andhaspermissionsof acceptingforchef andpickup forwaiter.
Epic 3: Order Completion
1. as a waiter:Ishouldbe able to mark the orderas complete once the customer has finished ordering.
2. as a customer: I should have an option for providing the tip after my order has been billed.
3. as a customer: I should be able to provide feedback for the service and the food.
4. as a waiter: I should be able to take payment from the customer and thus mark the order as paid.
Acceptance criteria:
The order isbilledanddisplayedtothe customer.There isacapabilitytoaccept paymentfromcustomer
and mark the orderas paid.All the updatestothe orderare updatedinthe database.
Epic 4: Menu Management
1. as a restaurantmanager:I shouldbe able tomodifythe menuitems,addnew items,delete items, and
update descriptions.
2. as a higher management member: I should be able to view the restaurant wise menu.
Acceptance Criteria:
Menu iseditable forrestaurantmanagerandhascapabilitiesof adding,removingandupdatingthe
menuitemswhichappearinthe menudisplayedtocustomer.
Epic 5: Manage restaurant information
1. as a managementmember:I shouldbe able to add, delete andupdate the informationaboutvarious
restaurants.
2. as a restaurant manager: I should be able to update information about my restaurant.
Acceptance Criteria:
The restaurantmanager isable to update informationabouthisoutletandthe highermanagementis
able to add,editor delete restaurantinformationwhichincludeslocation,#of covers,managerand
staff information.
Epic 6: Reporting per outlet
1. as a restaurant manager: I should be able to view weekly sales for my outlet.
2. as a restaurant manager: I should be able to view monthly sales for my outlet.
3. as a restaurant manager: I should be able to view quarter wise sales for my outlet.
4. as a restaurant manager: I should be able to view annual sales for my outlet.
5. as a restaurant manager: I should be able to view the most popular items ordered by the customers,
average bill and least popular items for further actions in menu management.
Acceptance Criteria:
Restaurantmanagerisable to see the restaurantsales onweekly,monthly,quarterlyandannual basis.
Epic 7: Reporting for chain
1. as a member of higher management: I should be able to view restaurant wise weekly sales.
2. as a member of higher management: I should be able to view restaurant wise monthly sales.
3. as a member of higher management: I should be able to view restaurant wise quarterly sales.
4. as a member of higher management: I should be able to view the overall annual sales.
5. as a restaurant manager: I should be able to view the most popular items ordered by the customers,
average bill and leastpopularitemsforfurtheractions inmenumanagementacross the chain as well as
per restaurant.
Acceptance Criteria:
Highermanagementisable tosee the restaurant salesonweekly,monthly,quarterlyandannual basis
for all restaurantsaswell asin a restaurantwise format.
Epic 8: Inventory Management for restaurant
1. as a restaurant manager: I should be able to view the current inventory position of the restaurant
2. as a restaurant manager: I should be able to update the inventory items.
3. as a restaurant manager: I should be able to view the forecast of items in the inventory to be
replenished.
Acceptance criteria:
Restaurantmanagerhas a systemtotrack inventory,add,deleteorupdate itemsandsee the forecastof
the requireditemsinfuture.
Future Epics
9. Marketing campaign management for restaurant outlet
There can be a feature of campaignmanagementforrestaurantswhichwill helpcome upwith
new schemestoattract customersand maintainprofit.These canbe trackedandreviewedforpointing
out useful campaignsoutof all the campaigns.There shouldbe capabilitiestosendemailsandtextsto
customersviathistool and to latergetreportson campaigns.
10. Marketing campaign management for the chain
Alongwiththe restaurantwise campaignmanagement,there canbe chainwide campaigns
whichapplyforall the restaurantsinthe chainor underthe ownershipof the highermanagement.
11. Personalization for user/customer by maintaining the order history and preferences
The customers’informationcanbe trackedinthe systemto analyze the frequentcustomers,
theirbuyingpattern,total salesandfurthermore provide themspecial loyaltyoffers.For the customerit
can helphimorderremotelyorpriorto arrival inthe restaurantandfor managementitwill helpthem
provide betterservicetocustomers.

Contenu connexe

Tendances

Project report final
Project report finalProject report final
Project report final
Jaya Saini
 

Tendances (20)

Onlineshopping
OnlineshoppingOnlineshopping
Onlineshopping
 
Restaurant management presentation
Restaurant management presentationRestaurant management presentation
Restaurant management presentation
 
Srs (Software Requirement Specification Document)
Srs (Software Requirement Specification Document) Srs (Software Requirement Specification Document)
Srs (Software Requirement Specification Document)
 
Restaurant Management System
Restaurant Management SystemRestaurant Management System
Restaurant Management System
 
Software Requirements Specification for restaurant management system
Software Requirements Specification for restaurant management systemSoftware Requirements Specification for restaurant management system
Software Requirements Specification for restaurant management system
 
Online ecommerce website srs
Online ecommerce  website srsOnline ecommerce  website srs
Online ecommerce website srs
 
Food delivery application report
Food delivery application reportFood delivery application report
Food delivery application report
 
College Management System project srs 2015
College Management System project srs 2015College Management System project srs 2015
College Management System project srs 2015
 
Problem statement
Problem statementProblem statement
Problem statement
 
Car rental Project Ppt
Car rental Project PptCar rental Project Ppt
Car rental Project Ppt
 
Project report final
Project report finalProject report final
Project report final
 
online news portal system
online news portal systemonline news portal system
online news portal system
 
Ppt on ONLINE BOOK STORE
Ppt on ONLINE BOOK STOREPpt on ONLINE BOOK STORE
Ppt on ONLINE BOOK STORE
 
Online shopping
Online shoppingOnline shopping
Online shopping
 
iOder (Food Ordering System)
iOder (Food Ordering System)iOder (Food Ordering System)
iOder (Food Ordering System)
 
Ecommerce srs
Ecommerce  srsEcommerce  srs
Ecommerce srs
 
SRS for Hospital Management System
SRS for Hospital Management SystemSRS for Hospital Management System
SRS for Hospital Management System
 
online blogging system
online blogging systemonline blogging system
online blogging system
 
online-shopping-documentation-srs for TYBSCIT sem 6
 online-shopping-documentation-srs for TYBSCIT sem 6 online-shopping-documentation-srs for TYBSCIT sem 6
online-shopping-documentation-srs for TYBSCIT sem 6
 
E Commerce Application Web Design Proposal PowerPoint Presentation Slides
E Commerce Application Web Design Proposal PowerPoint Presentation SlidesE Commerce Application Web Design Proposal PowerPoint Presentation Slides
E Commerce Application Web Design Proposal PowerPoint Presentation Slides
 

En vedette

Agile stories, estimating and planning
Agile stories, estimating and planningAgile stories, estimating and planning
Agile stories, estimating and planning
Dimitri Ponomareff
 
Pharmacy Management System1
Pharmacy Management System1Pharmacy Management System1
Pharmacy Management System1
Nuwan Lansakara
 
Inventory management system
Inventory management systemInventory management system
Inventory management system
copo7475
 

En vedette (9)

Распределенный SCRUM - to be or not to be collocated collocated
Распределенный SCRUM - to be or not to be collocated collocatedРаспределенный SCRUM - to be or not to be collocated collocated
Распределенный SCRUM - to be or not to be collocated collocated
 
Epics and User Stories
Epics and User StoriesEpics and User Stories
Epics and User Stories
 
Agile stories, estimating and planning
Agile stories, estimating and planningAgile stories, estimating and planning
Agile stories, estimating and planning
 
Pharmacy management system Requirement Analysis and Elicitation Document
Pharmacy management system Requirement Analysis and Elicitation Document Pharmacy management system Requirement Analysis and Elicitation Document
Pharmacy management system Requirement Analysis and Elicitation Document
 
The 5 Levels Planning in Agile
The 5 Levels Planning in AgileThe 5 Levels Planning in Agile
The 5 Levels Planning in Agile
 
Product Lifecycle in JIRA
Product Lifecycle in JIRAProduct Lifecycle in JIRA
Product Lifecycle in JIRA
 
Pharmacy Management System1
Pharmacy Management System1Pharmacy Management System1
Pharmacy Management System1
 
Inventory management system
Inventory management systemInventory management system
Inventory management system
 
Agile Program and Portfolio Management
Agile Program and Portfolio ManagementAgile Program and Portfolio Management
Agile Program and Portfolio Management
 

Similaire à Epics and User Stories

HRMPS 12 (MIDTERM)Chapter 4 restaurant operations
HRMPS 12 (MIDTERM)Chapter 4 restaurant operationsHRMPS 12 (MIDTERM)Chapter 4 restaurant operations
HRMPS 12 (MIDTERM)Chapter 4 restaurant operations
Bean Malicse
 
Unit 1. Introduction to Food and Beverage Control.pptx
Unit 1. Introduction to Food and Beverage Control.pptxUnit 1. Introduction to Food and Beverage Control.pptx
Unit 1. Introduction to Food and Beverage Control.pptx
HannaViBPolido
 
multi-vendor-catering-management-sytem.docx
multi-vendor-catering-management-sytem.docxmulti-vendor-catering-management-sytem.docx
multi-vendor-catering-management-sytem.docx
veerdevshreyas1
 
CSP586 Project - Maurya, Shailesh
CSP586 Project - Maurya, ShaileshCSP586 Project - Maurya, Shailesh
CSP586 Project - Maurya, Shailesh
sagar.247
 
Chapter 04 power_point
Chapter 04 power_pointChapter 04 power_point
Chapter 04 power_point
agiuffre
 

Similaire à Epics and User Stories (20)

Sprint Plan1
Sprint Plan1Sprint Plan1
Sprint Plan1
 
HRMPS 12 (MIDTERM)Chapter 4 restaurant operations
HRMPS 12 (MIDTERM)Chapter 4 restaurant operationsHRMPS 12 (MIDTERM)Chapter 4 restaurant operations
HRMPS 12 (MIDTERM)Chapter 4 restaurant operations
 
Responsibilities of F&B Manager .pdf
Responsibilities of F&B Manager .pdfResponsibilities of F&B Manager .pdf
Responsibilities of F&B Manager .pdf
 
Floreant POS
Floreant POSFloreant POS
Floreant POS
 
Eatware
EatwareEatware
Eatware
 
Unit 1. Introduction to Food and Beverage Control.pptx
Unit 1. Introduction to Food and Beverage Control.pptxUnit 1. Introduction to Food and Beverage Control.pptx
Unit 1. Introduction to Food and Beverage Control.pptx
 
Food and BeveragE Cost Control
Food and BeveragE Cost ControlFood and BeveragE Cost Control
Food and BeveragE Cost Control
 
Methodology of F&B Control
Methodology of F&B ControlMethodology of F&B Control
Methodology of F&B Control
 
Unit 1. Introduction to Food and Beverage Control.pptx
Unit 1. Introduction to Food and Beverage Control.pptxUnit 1. Introduction to Food and Beverage Control.pptx
Unit 1. Introduction to Food and Beverage Control.pptx
 
Restaurant365
Restaurant365Restaurant365
Restaurant365
 
Consumer-To-Consumer Food Delivery System on Salesforce.
Consumer-To-Consumer Food Delivery System on Salesforce.Consumer-To-Consumer Food Delivery System on Salesforce.
Consumer-To-Consumer Food Delivery System on Salesforce.
 
Bite A Slice1
Bite A Slice1Bite A Slice1
Bite A Slice1
 
multi-vendor-catering-management-sytem.docx
multi-vendor-catering-management-sytem.docxmulti-vendor-catering-management-sytem.docx
multi-vendor-catering-management-sytem.docx
 
Kitchen Cost Control.
Kitchen Cost Control.Kitchen Cost Control.
Kitchen Cost Control.
 
CSP586 Project - Maurya, Shailesh
CSP586 Project - Maurya, ShaileshCSP586 Project - Maurya, Shailesh
CSP586 Project - Maurya, Shailesh
 
Chapter 04 power_point
Chapter 04 power_pointChapter 04 power_point
Chapter 04 power_point
 
Website user guide
Website user guideWebsite user guide
Website user guide
 
Presentation on iot restaurant project
Presentation on iot restaurant projectPresentation on iot restaurant project
Presentation on iot restaurant project
 
Food Court Business - Operations Manual
 Food Court Business - Operations Manual  Food Court Business - Operations Manual
Food Court Business - Operations Manual
 
restaurant management system for managing restaurant.
restaurant management system for  managing restaurant.restaurant management system for  managing restaurant.
restaurant management system for managing restaurant.
 

Plus de Milind Gokhale

Technology Survey and Design
Technology Survey and DesignTechnology Survey and Design
Technology Survey and Design
Milind Gokhale
 

Plus de Milind Gokhale (20)

Yelp Dataset Challenge 2015
Yelp Dataset Challenge 2015Yelp Dataset Challenge 2015
Yelp Dataset Challenge 2015
 
Collaborative Filtering Recommendation System
Collaborative Filtering Recommendation SystemCollaborative Filtering Recommendation System
Collaborative Filtering Recommendation System
 
Technology Survey and Design
Technology Survey and DesignTechnology Survey and Design
Technology Survey and Design
 
Market Survey Report
Market Survey ReportMarket Survey Report
Market Survey Report
 
Visualforce
VisualforceVisualforce
Visualforce
 
Aloha Social Networking Portal - SRS
Aloha Social Networking Portal - SRSAloha Social Networking Portal - SRS
Aloha Social Networking Portal - SRS
 
Aloha Social Networking Portal - Design Document
Aloha Social Networking Portal - Design DocumentAloha Social Networking Portal - Design Document
Aloha Social Networking Portal - Design Document
 
Wsd final paper
Wsd final paperWsd final paper
Wsd final paper
 
Android games analysis final presentation
Android games analysis final presentationAndroid games analysis final presentation
Android games analysis final presentation
 
Android gamesanalysis hunger-gamesfinal
Android gamesanalysis hunger-gamesfinalAndroid gamesanalysis hunger-gamesfinal
Android gamesanalysis hunger-gamesfinal
 
Buffer Trees - Utility and Applications for External Memory Data Processing
Buffer Trees - Utility and Applications for External Memory Data ProcessingBuffer Trees - Utility and Applications for External Memory Data Processing
Buffer Trees - Utility and Applications for External Memory Data Processing
 
Algorithms for External Memory Sorting
Algorithms for External Memory SortingAlgorithms for External Memory Sorting
Algorithms for External Memory Sorting
 
One sample runs test
One sample runs testOne sample runs test
One sample runs test
 
Building effective teams in Amdocs-TECC - project report
Building effective teams in Amdocs-TECC - project reportBuilding effective teams in Amdocs-TECC - project report
Building effective teams in Amdocs-TECC - project report
 
Building effective teams in Amdocs TECC - Presentation
Building effective teams in Amdocs TECC - PresentationBuilding effective teams in Amdocs TECC - Presentation
Building effective teams in Amdocs TECC - Presentation
 
Internet marketing report
Internet marketing reportInternet marketing report
Internet marketing report
 
Internet marketing
Internet marketingInternet marketing
Internet marketing
 
Indian it industry
Indian it industryIndian it industry
Indian it industry
 
Change: to be or not to be
Change: to be or not to beChange: to be or not to be
Change: to be or not to be
 
Decision Tree Learning
Decision Tree LearningDecision Tree Learning
Decision Tree Learning
 

Epics and User Stories

  • 1. RESTAURANT MANAGEMENT SYSTEM Epics and User Stories Milind Gokhale; Shruthi Katapally; Vimalendu Shekhar; Shrijith Pillai; Megha Mukim; Akshay Jarandikar Abstract This document outlines the user stories thought so far to accomplish thebasic features of a restaurantmanagement system.
  • 2. Epics and User Stories Contents Epic 1: Order creation.........................................................................................................................2 Acceptance criteria:........................................................................................................................2 Epic 2: Order queue and delivery.........................................................................................................2 Acceptance criteria:........................................................................................................................2 Epic 3: Order Completion....................................................................................................................2 Acceptance criteria:........................................................................................................................3 Epic 4: Menu Management .................................................................................................................3 Acceptance Criteria:........................................................................................................................3 Epic 5: Manage restaurant information................................................................................................3 Acceptance Criteria:........................................................................................................................3 Epic 6: Reporting per outlet.................................................................................................................3 Acceptance Criteria:........................................................................................................................3 Epic 7: Reporting for chain ..................................................................................................................4 Acceptance Criteria:........................................................................................................................4 Epic 8: Inventory Management for restaurant......................................................................................4 Acceptance criteria:........................................................................................................................4 Future Epics .......................................................................................................................................4 9. Marketing campaign managementfor restaurant outlet................................................................4 10. Marketing campaign management for the chain .........................................................................4 11. Personalization for user/customer by maintaining the order history and preferences ...................4
  • 3. Epic 1: Order creation 1. as a customer: I should be able to browse through the menu and look at the various food options available in the restaurant along with the price for each item. 2. as a customer: I should be able to select items from the menu and add them to my cart/order. 3. as a customer: I should have cart containing all the chosen items so far, accessible all the time. 5. as a customer: I should be able to remove items from my cart or increase item count. 6. as a customer: I should be able to cancel my entire order. 7. as a customer:Ishouldbe abletoview theitemizedbillformyorderalongwiththe pricesforeachitem and the tax applied. 8. as a customer: I should be able to see the approximate delivery time. 4. as a customer:Ishouldbe able toseetopsellingitemsinthe restaurantwhile choosingmyorderitems. Acceptance criteria: Categorized Menu with prices is visible and enabled with selection choices, as soon as the customer chooses items, the order is created in the database and is visible to the customer. Epic 2: Order queue and delivery 1. as a chef: I should be able to view the current queue of orders. 2. as a chef: I should be able to accept the orders. 3. as a chef: I should be able to update the order status to ready once the order is prepared. 4. as a restaurant manager: I should be able to view the current queue of orders (in read-only mode). 5. as a waiter: I should be able to view the current order queue to see the ready orders for pick up. 6. as a waiter: I should be able to mark the order as picked up on the common queue. Acceptance criteria: The order queue isvisible andhaspermissionsof acceptingforchef andpickup forwaiter. Epic 3: Order Completion 1. as a waiter:Ishouldbe able to mark the orderas complete once the customer has finished ordering. 2. as a customer: I should have an option for providing the tip after my order has been billed. 3. as a customer: I should be able to provide feedback for the service and the food. 4. as a waiter: I should be able to take payment from the customer and thus mark the order as paid.
  • 4. Acceptance criteria: The order isbilledanddisplayedtothe customer.There isacapabilitytoaccept paymentfromcustomer and mark the orderas paid.All the updatestothe orderare updatedinthe database. Epic 4: Menu Management 1. as a restaurantmanager:I shouldbe able tomodifythe menuitems,addnew items,delete items, and update descriptions. 2. as a higher management member: I should be able to view the restaurant wise menu. Acceptance Criteria: Menu iseditable forrestaurantmanagerandhascapabilitiesof adding,removingandupdatingthe menuitemswhichappearinthe menudisplayedtocustomer. Epic 5: Manage restaurant information 1. as a managementmember:I shouldbe able to add, delete andupdate the informationaboutvarious restaurants. 2. as a restaurant manager: I should be able to update information about my restaurant. Acceptance Criteria: The restaurantmanager isable to update informationabouthisoutletandthe highermanagementis able to add,editor delete restaurantinformationwhichincludeslocation,#of covers,managerand staff information. Epic 6: Reporting per outlet 1. as a restaurant manager: I should be able to view weekly sales for my outlet. 2. as a restaurant manager: I should be able to view monthly sales for my outlet. 3. as a restaurant manager: I should be able to view quarter wise sales for my outlet. 4. as a restaurant manager: I should be able to view annual sales for my outlet. 5. as a restaurant manager: I should be able to view the most popular items ordered by the customers, average bill and least popular items for further actions in menu management. Acceptance Criteria: Restaurantmanagerisable to see the restaurantsales onweekly,monthly,quarterlyandannual basis.
  • 5. Epic 7: Reporting for chain 1. as a member of higher management: I should be able to view restaurant wise weekly sales. 2. as a member of higher management: I should be able to view restaurant wise monthly sales. 3. as a member of higher management: I should be able to view restaurant wise quarterly sales. 4. as a member of higher management: I should be able to view the overall annual sales. 5. as a restaurant manager: I should be able to view the most popular items ordered by the customers, average bill and leastpopularitemsforfurtheractions inmenumanagementacross the chain as well as per restaurant. Acceptance Criteria: Highermanagementisable tosee the restaurant salesonweekly,monthly,quarterlyandannual basis for all restaurantsaswell asin a restaurantwise format. Epic 8: Inventory Management for restaurant 1. as a restaurant manager: I should be able to view the current inventory position of the restaurant 2. as a restaurant manager: I should be able to update the inventory items. 3. as a restaurant manager: I should be able to view the forecast of items in the inventory to be replenished. Acceptance criteria: Restaurantmanagerhas a systemtotrack inventory,add,deleteorupdate itemsandsee the forecastof the requireditemsinfuture. Future Epics 9. Marketing campaign management for restaurant outlet There can be a feature of campaignmanagementforrestaurantswhichwill helpcome upwith new schemestoattract customersand maintainprofit.These canbe trackedandreviewedforpointing out useful campaignsoutof all the campaigns.There shouldbe capabilitiestosendemailsandtextsto customersviathistool and to latergetreportson campaigns. 10. Marketing campaign management for the chain Alongwiththe restaurantwise campaignmanagement,there canbe chainwide campaigns whichapplyforall the restaurantsinthe chainor underthe ownershipof the highermanagement. 11. Personalization for user/customer by maintaining the order history and preferences The customers’informationcanbe trackedinthe systemto analyze the frequentcustomers, theirbuyingpattern,total salesandfurthermore provide themspecial loyaltyoffers.For the customerit
  • 6. can helphimorderremotelyorpriorto arrival inthe restaurantandfor managementitwill helpthem provide betterservicetocustomers.