Restaurant Management System (RMS)
Version 1.0 dated: 2/3/2004
(This version includes some changes and formalizes the original concept)
I will serve as your customer and end-user.
Do NOT hesitate to query me on any points that are unclear. True to software development and working with clients, I too will not be able to articulate everything I need and the degree / detail to which I need it. But I will try… Ok, here goes…
The RMS is to be a web-based application that provides me, the customer and end-user, with considerable capabilities. I will attempt to address ‘my’ needs ‘by area.’
Maintain Menu:
My customers will want to be able to see a menu on-line.
Because I have ‘take out service’ (no delivery), the application must be able to support ordering, computing of cost, 8.5% tax, and also be able to afford the customer the option of including text, such as (no onions, blacken the fish, or anything special).
As owner, I need to be able to access the system and update the menu. I may designate someone to do this for me, though. In fact, I need to have a series of menus. See Version 1 Supp 1, dated 2/4/2004.
I need to be able to display a menu and progress from page to page. Menu should have page numbers citing Page 1 of 4 – or what have you.
Menu must have current date and other things cited elsewhere…
I need to be able to print off copies of the menus in order to put these on the tables.
Schedule Workers
I need to be able to schedule my workers.
My hours of operation are 4pm to 10pm on weekdays and 11 to 10 on weekends (Sat and Sun) from November through February. March through October my hours are 11am to 10pm every day.
I need to see some kind of schedule categorized by ‘type of worker’ and ‘by day’ and ‘by hour.’ Maybe the columns of the schedule could represent the day (across the top of the screen) and the names of workers down the left column. Group the workers by ‘type of worker.’
Types of workers include:
owner
manager
manager assistant
hostess
head waitress
waitresses (1..n)
bus boys (1..n)
cooks (1..n)
bartenders (1..n)
bar backs (1..n)
clean up crew (1..n)
The owner, manager, and manager assistant should be the only ones who can enter and change this schedule data as well as menu data.
I would like the menu and schedule accessible only to the owner, manager, and manager assistant.
I need to be able to print off hard copies of the schedules.
Finances
Accounts Receivables
Gross Receipts
each night
various categories
by week
same categories…
by month
by year
See Supp 1 for additional groupings.
Accounts Payable:
Food costs – more…
sources/vendors
Utilities –
electricity
water
sewerage
refuge / garbage
Grounds maintenance
property taxes
insurance on property / contents
Payroll:
Salaries: Need to be able to manage salaries of employees
Some are salaried, but most are hourly-workers.
I need to pay employee social security, workman’s compensation, …
Need to be able to compute weekly wages
State income tax is 5.5%
Federal income tax is nominally 15%
Some basic provisions for claiming number of exemptions should also
be included.
Need some additional parameters – to be discussed
medical insurance?
Social Security.
Owner
manager
manager’s assistant
hostess
head waitress
waitresses (1..n)
bus boys (1..n)
cooks (1..n)
bartenders (1..n)
bar –backs
clean up crew
Need to be able to access all these online
Need to be able to print out schedules, … from above.
All reports are to be suitably formatted with professional appearance (headers, page numbers, prepared dates, as of dates, etc.)
Construction: (Future Considerations)
additional property
parking lot
other additions – like lights on dock, etc.
Constraints
I will need the corresponding databases to support these needs.
Application is to include an on-line help function for the end users (employees only) and a short FAQ for users and customers
The system is not to be distributed.
The database component is to be a relational database system.
You may program the application server (web server) using jsp or php, and your database should be either MySQL or Oracle 9. Programming will be accommodated in java – as appropriate.
You will need knowledge of Object Oriented Software Development
You will need knowledge of the IBM-Rational Unified Process.
You will need to visually model all activities using Rose.
You will need to use the use case view and the logical view in Rose’s browser.
User requirements are to be captured and modeled using use cases.
Business Modeling will precede Application Modeling.
Use case models are to be accommodated in a package in Rose.