1. SOFTWARE REQUIREMENT SPECIFICATION Cortes, Hector Lachica, Joshua Salde, Rew Sim, Jason

2. COMPANY BACKGROUND Ms. Daryll Tan Manager Mr. Raymond Abeliena Staff Mr. Andy Castillo Staff Mr. Jetro Porta Staff Mr. Alfo Vinas Staff Ms. Joy Darangon Staff Ms. KC Villoria Staff Mr. Regan Ocampo Head Chef EGI Taft branch is managed by Ms. Daryll Tan. They employ Mr. Regan Ocampo, the head chef and 6 other employees. Customers – De La Salle Students and tenants of EGI Taft building. Conceptualized in the year 2003 by Mr. Aries Christopher Alvarez. Fast-food restaurant, Filipino food and Filipino style chicken barbeque.

3. BUSINESS PROCESS Divided into three process order process, inventory management process and sales transaction process. Order Process in Chicken Ati-atihan done in two ways. Dine-in Order Delivery Order Inventory management involves different process. Creating new record Removing existing record Updating current record

4. PROBLEM DESCRIPTION ProblemsRoot CauseSymptoms and Frequency Business Impact Data accuracyTracking of their sales information is a bit unorganized though they write their customer transactions on receipt and on a spreadsheet file. Because their business uses paper work and at the same time updating the spreadsheet file, they will have to acquire more of accuracy and efficiency in handling sales data input. Inaccurate calculations for sales record would mean potential loss on profits for the company. Difficulty of understanding and using the current software. They are currently using a spreadsheet program namely Microsoft Excel as a profit on sales or accounting system. They are having difficulty using it to keep track the sales and inventory of the company. The cashier or manager is having a difficult time inputting every order and sales record in the spreadsheet file. Also it can also be seen in their records that there are only using letters to indicate each item on file which makes it looks disorganized. It will be harder for other people to actually check and indicate the information on excel file if the manager or the cashier is not present at the branch for a period of time.

5. OBJECTIVES Sales Transaction Calculate the expected income based on the compiled order reports. Report Generation Generate different kinds of report: Inventory Information Report Sales Transaction Report Order Report Inventory Management Product maintenance such as creation, deletion and updating of product information. To keep track of each product’s quantity in the inventory. Ordering Create new orders. Update existing order details. Calculate and display the final bill based on the placed order; User Profile Profile management which control access to system functionalities.

6. SCOPE AND LIMITATIONS Computer must be equipped with Microsoft Windows’ operating system, Sun Microsystems' JRE and MySQL. The system assumes all transactions are in cash. The ordering module does not include a customer database. For delivery, it records customers location. The inventory module is limited to tracking of finished products' only. The sales module will not include computations for tax. The system includes a login function, to control access to programs functionalities. The system does not print receipts or sales report.

7. SOFTWARE FUNCTIONS Has four modules: ordering module, inventory management module, sales transaction module and user profile management module Ordering Module Provides facility for customer transactions. Has features like: Add Order Edit Order View Order Cancel Order Inventory Management Module Provides facilities for product management and maintenance in the stock. Has features like: Create New Menu Product Remove Menu Product Update Existing Menu Product Re-stock Product Sales Transaction Module Provides facilities for computation of product sales and viewing sales report. Has features like: View Daily Sales View Sales by Product User Profile Management Module Provides user login function and editing of user’s password. Has features like: Edit Password

8. USER TYPE AND DESCRIPTION Staff Take orders of customers. Limited access rights. Access limited to ordering module. Manager Can take orders and manager the cashier. Full access rights. Access to all system functions. There are two types of user, the manager and the staff.

9. DATA FILES AND DESCRIPTION Product File This file contains product information the restaurant caters. Stores product code, product name, unit price and quantity. Order File All data about order transactions. Stores order number, product name, product quantity, unit price, product price, total and date. User Account File Contains store manager’s information and password and staff’s personal information. Sales File Sales transactions made with the restaurant. Includes product name, product quantity, unit price, product price, total and date.

10. REPORT TYPES AND DESCRIPTION Sales Transaction Report Compiled order reports. Can be generated on a daily or monthly basis. Includes product name, product quantity, unit price, product price, total and date. Ordering Report Tracking of customer orders. Generated on a daily basis. Includes order number, date, product name, product quantity, unit price, product price and total. Inventory Information Report Information about a product and its quantity. Generated on a daily basis. Includes product code, product name, unit price and quantity.

11. USE CASE DIAGRAM - MANGER

12. USE CASE DIAGRAM - STAFF

13. USE CASE DESCRIPTION User will select his or her user type and type in their password. The user selects SUBMIT. Include (Validate User). User is logged either as manger or staff Use Case: Login Account Use Case: Validate User Check if the password exists. Check if password is consistent with the username. Use Case: Logout Account User selects log-out from the system. Verifies if the user wants to log-out. User is logged out from the system.

14. USE CASE DESCRIPTION User selects Sales from the system. System verifies if the user is a manager System shows Sales Module. Use Case: View Sales Module

15. USE CASE DESCRIPTION User is asked to input the necessary information about the Menu. User selects OK. Include (Validate Input). The menu item is successfully added to the system. User is asked if he or she wants to add another menu. Use Case: Add Menu User is asked to input item code he or she wants to modify. User selects OK.Include (Add Menu). Use Case: Edit Menu The user can view the tabulated form of the menu. Use Case: View Menu Check if the product already exists in the inventory. Use Case: Validate Input

16. USE CASE DESCRIPTION Asked user whether to delete another item. Informs the user that the item is successfully removed. Item is successfully deleted in the system. Verify if the user wants to delete the item. Include (Validate Input). User selects OK. Prompted to input product code to be deleted. Use Case: Delete Menu

17. USE CASE DESCRIPTION Use Case: Edit Password The user inputs new password. The system will verify if the user wants to change password. The password is successfully updated.

18. USE CASE DESCRIPTION Use Case: Add Order 1 User is asked to input the necessary information about the order. 2 User selects OK. 3 The order is successfully added to the system. 4 User is asked if he or she wants to add another order. Use Case: Edit Order 1 User is asked to input order number code he or she wants to modify. 2 User selects OK. 3 Include (Add Order).

19. USE CASE DESCRIPTION Use Case: Delete Order 1 User is asked to input order code of the order he or she wants to delete. 2 User selects OK. 3 The system will verify if the user wants to delete the order. 4 The order is successfully deleted in the system. 5 The system informs the user that the order is successfully removed. 6 The user is asked if he or she wants to delete another item.