Software Requirement Specification

advertisement
SOFTWARE
REQUIREMENT
SPECIFICATION
Cortes, Hector
Lachica, Joshua
Salde, Rew
Sim, Jason
COMPANY BACKGROUND
• Conceptualized in the year 2003 by Mr.
Aries Christopher Alvarez.
• Fast-food restaurant, Filipino food and
Filipino style chicken barbeque.
Ms. Daryll
Tan
Manager
Mr. Regan
Ocampo
Head Chef
Mr. Raymond
Abeliena
Staff
Mr. Andy
Castillo
Staff
Mr. Jetro
Porta
Staff
Mr. Alfo
Vinas
Staff
Ms. Joy
Darangon
Staff
Ms. KC
Villoria
• 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.
Staff
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
PROBLEM DESCRIPTION
Problems
Root Cause
Data accuracy
Tracking of their
sales information is
a bit unorganized
though they write
their customer
transactions on
receipt and on a
spreadsheet file.
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.
Symptoms and
Frequency
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.
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.
Business Impact
Inaccurate
calculations for sales
record would mean
potential loss on
profits for the
company.
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.
OBJECTIVES
Sales Transaction
• Calculate the expected income
based on the compiled order
reports.
User Profile
• Profile management which control
access to system functionalities.
Inventory Management
• Product maintenance such as creation,
deletion and updating of product
information.
Ordering
• To keep track of each product’s
• Create new orders.
quantity in the inventory.
• Update existing order details.
• Calculate and display the final bill based
Report Generation
on the placed order;
• Generate different kinds of report:
• Inventory Information Report
• Sales Transaction Report
• Order Report
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.
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
USER TYPE AND DESCRIPTION
• There are two types of user, the manager and the staff.
Manager
• Can take orders and manager the cashier.
• Full access rights.
• Access to all system functions.
Staff
• Take orders of customers.
• Limited access rights.
• Access limited to ordering module.
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.
REPORT TYPES AND DESCRIPTION
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.
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.
Inventory Information Report
• Information about a product and its quantity.
• Generated on a daily basis.
• Includes product code, product name, unit price
and quantity.
USE CASE DIAGRAM - MANGER
USE CASE DIAGRAM - STAFF
USE CASE DESCRIPTION
Use Case: Login Account
User will
select his or
her user type
and type in
their
password.
The user
selects
SUBMIT.
Use Case: Validate User
Check if the
password
exists.
Check if
password is
consistent
with the
username.
Include
(Validate
User).
User is
logged either
as manger or
staff
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.
USE CASE DESCRIPTION
Use Case: View Sales Module
User selects
Sales from the
system.
System verifies
if the user is a
manager
System shows
Sales Module.
USE CASE DESCRIPTION
Use Case: Add Menu
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: Edit Menu
User is asked to input item
code he or she wants to
modify.
User selects OK.
Include (Add Menu).
Use Case: View Menu
The user can view the tabulated form of the menu.
Use Case: Validate Input
Check if the product already exists in the inventory.
USE CASE DESCRIPTION
Use Case: Delete Menu
Prompted to input product code to be deleted.
User selects OK.
Include (Validate Input).
Verify if the user wants to delete the item.
Item is successfully deleted in the system.
Informs the user that the item is successfully removed.
Asked user whether to delete another item.
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.
USE CASE DESCRIPTION
Use Case: Add Order
1
2
• User is asked to input the necessary
information about the order.
Use Case: Edit Order
1
• User is asked to input
order number code he
or she wants to modify.
• 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.
2
3
• User selects OK.
• Include (Add Order).
USE CASE DESCRIPTION
Use Case: Delete Order
1
2
3
4
5
6
• User is asked to input order code of the order he or she wants to delete.
• User selects OK.
• The system will verify if the user wants to delete the order.
• The order is successfully deleted in the system.
• The system informs the user that the order is successfully removed.
• The user is asked if he or she wants to delete another item.
Download
Related flashcards
Create Flashcards