Professional Documents
Culture Documents
Software Requirements Specifications
Software Requirements Specifications
Software Requirements Specifications
in Partial Fulfillment
of the requirements of the course
INTROSE
by
Ang, Sofia Indira Odessa G.
Bigtas, Nikko Miyagee C.
Tiam-Lee, Thomas James Z.
Table of Contents
1. Introduction....................................................................................................................................3
1.1. Overview........................................................................................................................................3
1.1.1. Company Background...........................................................................................................3
1.1.2. Organizational Chart............................................................................................................. 3
1.1.3. Business Process................................................................................................................... 4
1.1.4. Problem Description............................................................................................................. 5
1.2. Objectives, Scope, and Limitations................................................................................................ 5
1.2.1. Objectives............................................................................................................................. 5
1.2.2. Scope and Limitations..6
2. Functional Requirements......................................................................................................................6
2.1. Software Functions........................................................................................................................ 6
2.2. User Types and Their Descriptions.................................................................................................8
2.3. Data Files and Their Descriptions.................................................................................................. 9
2.4. Report Types and Their Descriptions........................................................................................... 10
2.5. Use Case Diagrams.......................................................................................................................11
2.6. Use Case Descriptions..................................................................................................................12
References..............................................................................................................................................17
1. Introduction
1.1. Overview
1.1.1. Company Background
On November 2009, a group of young entrepreneurs founded Poker Royale. Poker Royale
is a PAGCOR-registered gaming establishment located at 1712 Roxas Boulevard Pasay City, just
beside Traders Hotel and right across Star City. To give players an immersive experience, Poker
Royale runs a mini bar/restaurant within the establishment so that players could enjoy food and
drinks while they entertain themselves. The mini bar and restaurant was a success that it has
been expanded and now occupies the entire second floor besides the corner they have in the
ground floor. The mini bar/restaurant is now called Poker Royale Lounge.
This project proposal aims to propose a more efficient way of managing their
bar/restaurants expanding business. As such, all the business processes, issues, problems, and
descriptions within this document shall only pertain to those of the bar/restaurant and nothing
more.
1.1.2. Organizational Chart
The operations of Poker Royale Lounge are headed by the operations manager. Under
him are several other employees who have their designated tasks in running the establishment.
Shown here are the key people in the hierarchy which are relevant to the system described
within this document.
The waiters name and the customers order are recorded in an order slip
The waiter, cashier, kitchen, and bar requires a copy of the order slip
The waiter personally hands copies of the order slip to the departments
Sales are manually deducted from the inventory and recorded by each department
Serving Orders
Waiter manually keeps track of these time intervals to know when an order is
ready to be served
Bill Out
Waiter copy of order slips for a customer are compiled, total amount is computed,
and then presented to the customer
Operations manager manually organizes data from the order slip records and
inventory records into a report
Report must include number of sales for each item, total sales, and number of
transactions served by the waiter
Root Cause
Copious items
purchased by the
customers lead to
confusion, disorder
and unsystematic
way of tracking the
items.
Filing all
There are countless
transactions with transactions to be
customers
filed on such a short
period of time.
Engendering
accurate and
comprehensive
report
Incompetent
employees
To provide a flexible sales report tool that can generate various views on the
same data
1.1.2. Scopes and Limitations
In recording the purchases made by customers, the following information are stored:
(1) a unique transaction number assigned to every transaction, (2) the name of the customer,
(3) the name of the waiter, (4) the items purchased and their prices, (5) the date and time of the
transaction, (6) discounts applied to the transaction (if any), (7) the total price of all the items
bought or ordered after applying the discounts (if any).
For the database of items, the system will only store information about the items
offered in the lounge. Data regarding the number of stock for each item is not covered since an
inventory system is no longer in our scope. The following information are stored for each item in
the database: (1) the unique product identification number, (2) the product name, (3) item type,
(4) category, (5) the price the item was bought, and (6) the selling price. The item type is either
Food or Drinks. The category may be any one of the following: appetizer, chefs special, noodles,
starters, sandwich, sizzler, seafood, for Food item-type; Cocktail, beer, liquor, shooters, on-therocks, beverages, fruit shakes, for Drinks item-type.
In generating reports on sales, the system can show detailed reports on the sales made
on a daily, weekly, monthly, or cumulative basis. The user can view this report any time he
wishes. To do so, he or she must input a specific day (for daily), a starting day for a week (for
weekly), or a month (for monthly). All transactions are stored by the system for future
reference. Each transaction has (1) the waiter name, (2) the items purchased, (3) the discounts
applied, and (4) the prices.
2. Functional Requirements
2.1. Software Functions
Our point of sale system is divided into three modules: the Transactions module, the
Administration module, and the Reports module.
2.1.1. Transactions Module
The Transactions Module provides facilities for the waiter to record and manage
customer orders.
Add order. This function allows waiters to input the customers order in the
system by inputting an identifier for the customer or by selecting from the
6
suggested active customers, selecting which items from an existing list (with
filtering by item type, and sorting item name and price) or by inputting the item
name in the search input that instantly displays results as one types. The
customer order will be marked as Active and displayed in the list of active
orders.
Cancel order. This function allows items in an active order to be cancelled in
case the customer wishes to change what he has ordered provided that that
those items have not been prepared yet.
Bill out. This function computes the total amount to be paid by a customer
before leaving the restaurant. It will also display all the consolidated orders
made by the customer and their corresponding price, as well as the total
amount. Once the items have been paid for, the transaction is considered
complete and is stored in the database.
2.1.2. Administration Module
The Administration Module provides facilities for the administrator to manage
the menu and item details.
Add item. This function allows new items in the menu to be recorded in the
system. The admin must provide the following details: item name, item
description, and price. The admin must also specify an item type (food or drink)
and a category (appetizer, chefs special, noodles, starters, sandwich, sizzler,
seafood for food and cocktail, beer, liquor, shooters, on-the-rocks, beverages,
fruit shakes for drinks) by selecting from the drop-down menu or by inputting a
new item-type if it doesnt exist yet.
Edit item. This function allows the modification of an items name, description,
price, and type. Editing an item will not affect previous transactions.
Delete item. This function allows items to be deleted. Deleting an item will also
not affect previous transactions.
Create new account. Initially, there is only one account for one administrator.
An administrator account can add new accounts for new waiters and
administrators who would be using the system. The administrator must fill the
necessary information requested in the form to create a new account.
2.1.3. Reports Module
The reports module provides facilities for the administrator to view sales report,
view transactions log, and track waiter performance.
7
View sales report. This function generates sales report either on a daily, weekly,
monthly, or cumulative basis by selecting or inputting month, day, or year
involved. Report on the number of pieces sold for each item will be provided in
tabular format and graphical format (e.g. bar graph). Filters and sorting
functionalities (as discussed in the Transaction Module -> Add order) will also be
implemented here with the addition that the user can make a selection on
which particular products to generate report on. Consolidated daily, weekly, and
monthly reports are also supported.
View transaction log. This function displays the transaction history over a
specified period by selecting or inputting the start and end date. Each
transaction will display the waiter-in-charge, the items ordered, price, discounts
(if any), and total amount. Filters according to which waiter will also be
implemented to easily view transactions by each waiter.
View waiter performance report. This function generates waiter performance
report through deriving the number of transactions by each waiter. Similar to
the above functionality, reports may be on a daily, weekly, monthly, or
cumulative basis. Consolidation of reports is also supported.
2.2. User Types and Their Descriptions
These are the different users that will be using the system.
2.2.1. Administrator
The administrator is one of the two users of the system. In this case, the
administrator is the operations manager of the bar and restaurant. However, there can
be more than one administrator. Other users can also become administrators provided
that they are qualified and authorized. Administrators can access the administration
module and the reports module. They are permitted to add new item, edit and update
item details. Moreover, they are also allowed to generate sales and waiter performance
reports.
2.2.2. Waiter
The waiter is the second user of the system. The waiters are responsible for the
transactions made with the customers. Thus, they are limited to accessing transaction
module only. They can view, add, edit and cancel orders. They use the system for every
transaction created.
2.3. Data Files and Their Descriptions
These are the files that would be used in the system:
8
and birthdate are personal information which are needed for the particular waiter's
profile.
2.4. Report Types and Their Descriptions
2.4.1. Sales Report
The sales report aims to help the administrator analyze sales and adjust well to
demands. The system provides the administrator with a flexible sales reporting tool.
Sales report may be generated in a daily, weekly, monthly, or cumulative basis. The
report focuses on the items and how well they sell. Sales income is only secondary.
Reports are presented in tabular format and graphical format to provide detailed and
visual presentation of the data. Sales can be viewed by item type, or a user-selection of
items. Consolidation of daily, weekly, or monthly reports presents the trend and
enables the administrator to make wiser decisions.
2.4.2. Transaction Log
The transaction log simply provides the administrator a history of transactions.
Each transaction contains the customer identifier, items order, their prices, discounts (if
any), total amount, and the waiter-in-charge. The transaction log may be filtered
according to span of days, and the waiter responsible. The transaction log may be used
for counter-checking transactions against cashier and other department records, or
devising promo schemes.
2.4.3. Waiter Performance Report
The waiter performance report aims to provide the administrator an effective
way of tracking waiter performance by keeping track of the number of transactions
made by each. Tracking waiter performance allows the administrator to commend
waiters and award them incentives for good performance or provide more training if
they do not fare very well.
10
Precondition:
11
Exceptional Flow:
1. If the user clicks Submit and the customer
identifier is blank, the system will prompt the
user that this is not possible.
2. If the user clicks Submit and there is no item
specified, the system will prompt the user that
this is not possible.
Use Case: Cancel Order
Precondition:
1. The user must be logged in as waiter.
2. The user must select the Delete Order
option from the Manage Orders menu form.
Flow:
1. The user selects the order to be deleted
2. The user clicks on the Delete option to
remove the selected order.
3. The system updates the database by marking
the status of the order removed.
Alternative Flow: Back Option
1. If the user selects Back Option, the user will
be redirected to the Waiter Main window.
Exceptional Flow:
1. If the user clicks the Delete Option without
selecting any item, the system will display a
pop-up window informing the user that there
is no selected item to be deleted.
Use Case: Bill Out
Precondition:
1. The user must be logged in as waiter.
2. The user must select the Bill Out option from
the Waiter Main window.
Flow:
1. The user selects the customer identifier
associated with the customer who wants to bill
out.
2. The system displays all orders of the said
customer marked as active.
15
16
References
Ang, S. (21 September, 2010). CEO, Poker Royale. Interview.