FastMeal SRS V1.5

Project for CSCE-743 Software Requirements,
University of South Carolina, Columbia.
FastMeal
Requirements Specification
Document
Version: 1.4
This is made solely for academic purpose.

Date: 19 October 2016
Authors: Akhilesh Maloo & Avini Sogani
CSCE-743 Software Requirements
Date
Version
09/07/2016
09/21/2012
10/12/2016
10/24/2016
11/07/2016
11/18/2016
V1.0
V1.1
V1.2
V1.3
V1.4
V1.5
University of South Carolina, Columbia
Description
Initial draft Section 1
Added Section 2 to 5
Version :1.4
Copyright the Atlantic Systems Guild Limited
Author
Akhilesh, Avini
Akhilesh, Avini
Akhilesh, Avini
Akhilesh, Avini
Akhilesh, Avini
Akhilesh, Avini
2
Volere Template V16 /45
Contents
Project Drivers
1. The Purpose of the Project
2. The Stakeholders
Project Constraints
3. Mandated Constraints
4. Naming Conventions and Terminology
5. Relevant Facts and Assumptions
Functional Requirements
6. The Scope of the Work
7. Business Data Model & Data Dictionary
8. The Scope of the Product
9. Functional Requirements
Non-functional Requirements
10. Look and Feel Requirements
11. Usability and Humanity Requirements
12. Performance Requirements
13. Operational and Environmental Requirements
14. Maintainability and Support Requirements
15. Security Requirements
16. Cultural Requirements
17. Legal Requirements
Project Issues
18. Open Issues
19. Off-the-Shelf Solutions
20. New Problems
21. Tasks
22. Migration to the New Product
23. Risks
24. Costs
25. User Documentation and Training
26. Waiting Room
27. Ideas for Solutions
Version :1.4
3
1. The Purpose of the Project

This project is to develop a web application for employees to order food from cafeteria
in most efficient way.
1a. The User Business or Background of the Project Effort

Content
Currently, employees have to visit cafeteria and place manual orders. High
volume of employees at peak hours in cafeteria add up to space constraints and
delay in order processing with high possibility of errors. It causes delay in
receiving orders which results into extra off desk time for employees.
FastMeal web application focuses on simplifying order process with minimal
manual errors and fast delivery. It aims to increase efficiency for both employees
and cafeteria.
Motivation
It will give extra time and convenience to employees which would increase
revenue by maximizing their productivity.
Considerations
It is a significant opportunity to increase availability of employees on desk.
Form
Below business model aims to simplify order process by minimizing manual
efforts.
Version :1.4
4
Employee Authentication
Order Placing
Order Payment
Kitchen Order preparation
Order Completion Alert
Pick up / Delivery of Order
Post Sale Services

Figure 1 Business Process Model FastMeal
Version :1.4
5
1b. Goals of the Project

Content
FastMeal focuses on simplifying order process with minimal manual errors and
fast order delivery. It will help in maximizing revenue by increasing employee
productivity.
Benefits:
1. Reduced manual efforts & time for Order placing Order from Desk.
2. Minimized scope of errors.
3. Fast Order Processing.
4. Increased Availability of employees on desk.
Motivation
We want to provide quick and flaw less online support to employees for placing
order in cafeteria.
Measurement
Factors to measure success of Project.
Revenue Goal:
1. Increment in availability of employees work time on desk.
2. Increase in revenue due to employee productivity improvement.
3. Increase in Revenue of Cafeteria by maximum customer wallet share by
onboarding more employees.
4. Decreased minimum average order execution time.
Service Goal:
a. Increase in positive employee feedback on customer service surveys.
b. Less populated Cafeteria space.
Form
Purpose: FastMeal focuses on simplifying order process with minimal manual
errors and fast order delivery.
Advantage: Increased Revenue and Productivity due to extra employee available
work time on desk.
Measurement: Customer Service Feedback Survey Results.
Version :1.4
6
1. The Stakeholders
2a. The Client & Customer
Content
Stakeholder
Client/Sponsor
Product Line Manager
Name
Srinivasa Guntupalli
Veeraraghavan
Customer
Manasa Suthram
Roles
Business Manager
Cafeteria Manager /
Project Manager
Employees & Contract
staff
Motivation
Business manager is sponsor of project. Cafeteria manager will act as product
line manager who will communicate requirements. Cafeteria manager shall have
final rights to approve the product. This application will be used by all
employees of company so they will also play role of customer.
Considerations
NA
Form
Figure 2: Client Position Chart
Version :1.4
7
Figure 3: Organization Chart
Figure 4: Software Dev Life Cycle & Check Points
Version :1.4
8
2c. Other Stakeholders

Content
Stakeholder
Delivery Partner
Supply Manager
Name
Siddharth Pathak
Amit Bansal
Roles
Delivery Management
Inventory Management
Subject Matter Expert
Sabrina Karim
Domain Consulting
Marketing experts
Uddipan chatterjee
Marketing Management
Business analysts
Akhilesh Maloo/Avini
Sogani
Akhilesh Maloo/Avini
Sogani
Ajay Koduri
IT Team- Dev
Designers and developers &

Testing
Technology Architect
IT Team- Dev
Technical Architecture
Figure 5: Stakeholder Analysis
Version :1.4
9
2d. The Hands-On Users of the Product

Content
Predominantly below stakeholders are main users1. Employees and Contract Staff, Facility Staff.
2. Subject matter experience: can be rated as journeyman.
3. Technological experience: Rate as journeyman for contract staff and master for
employees.
Motivation
Employees & contract staff will utilize this application to order food from
cafeteria in minimal time.
2e. Priorities Assigned to Users

Content
This identifies the importance and precedence of the user. Prioritize the users as
follows:
1. Key users: Employees of Organization, Contract Staff.
2. Secondary users: Cafeteria Management.
3. Unimportant users: Suppliers, Inventory Manager.
2f. User Participation

Content
Key Users are required to highlight expected functionalities. They shall respond
to survey and Interviews scheduled to gather sufficient data. This will help in
maintaining requirement backlog.
2g. Maintenance Users and Service Technicians

Content
Cafeteria Management should play role of maintenance users as they will need to
troubleshoot for key user in down time.
Version :1.4
10
3. Mandated Constraints
3a. Solution Constraints
Content:
Application would serve as web tool. Employees will have to access through
intranet of organization.
1. Description: The product shall use intranet to communicate with the web server.
Rationale: The application is solely made for organization and cannot be used
outside of it.
Fit criterion: All request and responses within application should be from
intranet.
2. Description: The application shall be a web tool.
Rationale: To showcase as organizations own cafeteria ordering software which
all employee can use over intranet.
Fit criterion: All employee should be able to order through intranet website.
Motivation
Application should be intuitive and easy to use.
3b. Implementation Environment of the Current System

Content
This application will be installed on intranet of organization. It will be installed
on organizational server.
Version :1.4
11
3e. Anticipated Workplace Environment

Content
All the employees have desktop connected to intranet of organization where they
can utilize this application.
3f. Schedule Constraints

Content
This application should only be used In between 8:00 AM to 8:00 PM.
It would also require downtime of an hour in a week for maintenance.
Organization is revamping cafeteria and this product shall be required before Jan
2017. There is one month of windows of marketing opportunity before Jan 2017.
Delay in installation of this product will effect current manual order processing
system.
It will also affect the availability of subject matter experts / other knowledge
centers. January is usually a peak business period hence it would be difficult to
find resources to spare their time in that month.
3g. Budget Constraints

Content
Sponsor has approved projected budget of $200k for first release. All
Requirements should be adjusted in same budget.
4. Naming Conventions and Terminology

4a. Definitions of All Terms, Including Acronyms, Used by
Stakeholders Involved in the Project
FastMeal: Name of web application being developed.
5. Relevant Facts and Assumptions

5a. Relevant Facts
Content
Existing solution is manual process. It would require to automate the entire
process by process modeling.
Version :1.4
12
5b. Business Rules

Content
9
10
11
12
13
14
No Alcohol would be served.

Payment should be made in advance.
No show will lead to forfeit of full money.
Cancellation is permissible up to 20 minutes from payment.
Management has final right to decide on dispute.
Every order will have to abide by minimum time of preparation.
5c. Assumptions
Content
1.
Cafeteria is being managed by company itself.
2.
There is no other cafeteria near by organization hence all employees
come to the same cafeteria.

3.
Month of September to December is considered as down time for
company resources which can be utilized toward active requirement gathering.

4.
All employees have access to intranet.
5.
In order to place additional orders, Single user will have to wait for 30
minutes.
Version :1.4
13
6. The Scope of the Work

6a. The Current Situation
Content
Existing business process involves employee to visit cafeteria and place
an order by waiting in order queue. This also involves possibility of error
in placing order. Error at order placing gets bigger till preparation of
order. This scenario not only waste time but also incur huge resource
cost.
Further, Employee has to wait for order to be prepared which might add
into total idle time for employee.
This model is predominantly dependent on attentiveness of employee
and order receiving staff which can not be called reliable.
EMPLOYEE VISIT CAFETERIA

WAIT IN QUEUE FOR TURN
PLACE MANUAL ORDER
ORDER CONFIRMATION
ORDER PAYMENT
ORDER PREPARATION
ACCEPTANCE OF ORDER
DINE IN /TAKE AWAY
Figure 6 :Existing Business Process
Version :1.4
14
6b. The Context of the Work

Content
The work context diagram identifies the boundaries of the work that
FastMeal need to investigate to be able to build the product.
Application
Design
Order
Management
Order Information
System Configuration
Employee
Population
FastMeal
Online
Ordering
Human
Resource
Estimation
Shutdown Period
Lunch /
Dinner hours
Menu Concentration
Order
Execution
Inventory
Management
Supplier & Vendor

(raw Material)
Reception
&
Verification
Order
Delivery
Payment
Mechanism
Billing &
Payments
Figure 7: Work Context Diagram
Version :1.4
15
6c. Work Partitioning

Content
A list showing all business events to which the work responds. Business
events are happenings in the real world that affect the work. It represents
a discrete partition of work that contributes to the total functionality of the
work.
Sr #
Event Name
BU01
Authentication
BU02
Show Catalog
BU03
BU04
BU05
BU06
Add item in Cart

Remove Item
from Cart
Checkout
Payment
BU07
Cancel Order
BU08
Order
Confirmation
Order Execution
BU09
BU10
Inventory
Management
BU11
Purchase
Inventory
Add/Remove
Item in Catalog
BU12
(I)nput / (O)utput /
(P)rocess
Employee Credential
(I)
ItemCode in form of
Menu (O)
ItemCode(I)
ItemCode(I)
Summary of BUC
ItemCode(O)
Amount for Item(O),
Bank Details (I)
Order info(I)
Shows final Items in the Cart

System will show total bill amount and
will facilitate payment through bank.
System will determine cancellation
basis order info and business rules.
System will confirm Order details with
list of item ordered.
System will show items to be executed
in kitchen dept and manage inventory.
Order info(O), Item list

in Cart( O)
ItemCode(O), Order
Status (I) , Manage
Inventory(P)
Material (I) , Inventory
(O)
Material (O)
ItemCode(I)
Version :1.4
Authenticate to use system

System will show Menu items which
can be ordered.
System will add menu item in the cart.
System will remove item from the cart
System will take material as input and

show total available inventory as
output
System will show material which
requires to be replenished
System will Add/Remove Specified
Item in/from catalog.
16
6d. Specifying a Business Use Case (BUC)

BU01: Authentication
Name
Authentication
ID
BU01
Description
Employee has to authenticate to use the system.
Actors
Employee, Database
Triggers
NA
Preconditions
User should be an employee of the organization.
Postconditions
Employee can see the home page.
Main Course
1. System shows login page.

2. Employee enters login details to sign in to the system.
3. System authenticates the login credentials through database (see EX1).
4. System redirects to home page after employee logs in.

Alternate
Courses
NA
Exceptions
EX1: System fails to authenticate.

1. Return to main course step 1 with an error message.

BU02: Show Catalog

Name
Show Catalog
ID
BU02
Description
System will show menu items to be ordered.
Actors
Employee, Database
Triggers
Employee logs into the system.
Preconditions
Employee logs into the system.
Postconditions
Employee can perform various operations like adding or removing item(s) in/from
the cart or checking out.
1. Employee clicks on show catalog button.
2. System will show menu items with description (see EX1).

Main Course
Alternate
Courses
NA
Exceptions
EX1: System fails

1. System is redirected to login page.

Version :1.4
17
BU03: Add Item in Cart

Name
Add Item in Cart
ID
BU03
Description
System will add menu item in the cart.
Actors
Employee, Database
Triggers
NA
Preconditions
Employee logged in to the system and the catalog is shown.
Postconditions
Employee can checkout.
Main Course
1. Employee selects the item to be ordered.

2. Employee adds the item to the cart by clicking on add button (see Ex1, AC1 AC2).
3. System will redirect to cart showing the added item.

Alternate
Courses
NA
Exceptions
EX1: System fails


BU04: Remove Item from Cart

Name
Remove Item from Cart
ID
BU04
Description
Actors
System will remove item from the cart.

Employee, Database
Triggers
NA
Preconditions
Item is added to the cart.
Postconditions
Item is removed successfully from the cart.
Main Course
1. System will show the cart.

2. Employee selects item to be removed from the cart.
3. Employee clicks on remove button.
4. System removes item from the cart (see EX1, AC1).

NA
Alternate
Courses
Exceptions
EX1: System fails


Version :1.4
18
BU05: Checkout
Name
Checkout
ID
BU05
Description
System will show final items in the cart.
Actors
Employee, Database
Triggers
Preconditions
Postconditions
Order is confirmed.
Main Course
1. System will show final items in the cart.

2. Employee verifies all the items in the cart.
3. Employee clicks the checkout button (see AC1, AC2, EX1).
4. System generates the order id and sends it into the database (see EX1).

Alternate
Courses
AC1: Employee may continue ordering by clicking Add More button

1. System is redirected to show catalog page.

AC2: Employee clicks remove button to remove items from cart.
1. System remove item from the cart.

Exceptions
EX1: System fails


BU06: Payment
Name
Payment
ID
Description
BU06
System will show total bill amount and will facilitate payment through bank.
Actors
Employee, Database, Bank
Triggers
Employee checkout.
Preconditions
Employee checkout.
Postconditions
Payment receipt id is generated.
Main Course
1. System displays total bill amount and corresponding order id from database.
2. Employee enters the payment details (see EX1).
3. Bank validates the payment details and processes it (see EX1, EX2).
5. System generates the payment receipt id and sends it to database (see EX1).

Alternate
Courses
NA
Exceptions
EX1: System fails


EX2: Bank rejects the payment details.
1. An error message is sent to the employee.
2. No order is generated.
Version :1.4
19
BU07: Cancel Order

.
Name
Cancel Order
ID
BU07
Description
Actors
This Use case allow employee to cancel order

Employee(I), Database , Bank
Triggers
Employee clicks on Cancel Order Menu.
Preconditions
Order Id must exist in Database. Employee must be logged in.
Post conditions
System will mark order status as cancelled , Refund id would be generated.
Main Course

1.
2.
3.
4.
5.
6.
7.
System will show all orders created in last 2o minutes.

Employee will select order from list.
Employee will click on cancel button.
System will verify order details.
System will mark Order status as cancelled in Database.
System will generate refund id.
Bank will make payment to employee as per refund Id and order details.

Alternate
Courses
AC1: If there are no records available:

1. In step 1, If there are no records available, system will show prompt No
Orders available to Cancel.
2. System will redirect to home page.

AC2: System finds order to be invalid to cancel
1. In Step 4, If System does not verify to cancel the order as per business
rules, system will show error message Order Cant be cancelled.
2. System will redirect to home page.

Exceptions
Global Exception Scenarios

BU08: Order Confirm

Name
Order Confirmation
ID
BU08
Description
This Use case confirm Order and display ITEM code to Kitchen Screen
Actors
Database
Triggers
Payment Receipt Id generated.
Preconditions
Payment must be completed for order.
Post conditions
System update order status to Preparing.
Main Course

1.
2.
3.
Database will show item codes in order id.

System will show ITEM code in Kitchen Screen
System will update Order Status to Preparing.

Alternate
Courses
Exceptions
NA

Version :1.4
20
BU09: Order Execution

Name
Order Execution
ID
Description
BU09
This Use case confirm Order Execution and provide update to employee.
Actors
Database, Kitchen staff(I), Employee
Triggers
Preconditions
Order Item codes are displaying on screen.
Post conditions
System will update order status and send update to employee
Main Course

Alternate
Courses
Exceptions
1.
2.
3.
Kitchen Staff will update Order Status Ready in system.

System will update Inventory in Database.
System will display Order status to User.
NA

BU10: Inventory Management Report

Name
Inventory Management Report
ID
Description
BU10
This Use case will alert Inventory manager to buy material.
Actors
Database, Inventory Manager
Triggers
Order Execution
Preconditions
Post conditions
System will show message to Inventory manager to buy list of material (ingredient)
Main Course

1.
2.
Alternate
Courses
Exceptions
Database will verify after every order execution if material quantity is

above threshold.
Database will show message with material code to Inventory Manager.

NA

Version :1.4
21
BU11: Purchase Inventory

Name
Purchase Inventory
ID
BU11
Description
This use case show how inventory manager will place order.
Actors
Database, Inventory Manager(I), Vendor,Bank.
Triggers
Inventory
Preconditions
Post conditions
Main Course
System will show message to Inventory manager to buy list of material (ingredient)
1. Inventory manager will input material name.
2. Inventory manager will input Quantity Required.
3. Inventory manager will click on buy button.
4. Inventory manger will make payment using bank module.
5. Database will update material status ordered.
6. System will send above information to Vendor.
Alternate
Courses
Exceptions
NA

BU12: Add/Remove Item from Catalog

Name
Add/remove Item from Catalog
ID
BU12
Description
System will add/remove specified item in/from the catalog.
Actors
Cafeteria Manager, Database
Triggers
NA
Preconditions
NA
Postconditions
Item is successfully added/removed from the catalog.
Main Course
1. Cafeteria manager fills item code.

2. Cafeteria manager fills item name.
3. Cafeteria manager fills item description.
4. Cafeteria manager fills price.
5. Cafeteria manager fills material codes of the materials used in this particular
item.
6. Cafeteria manager fills material names.
7. Cafeteria manager clicks on add button (see EX1, EX2).
8. System adds item to the catalog.

NA
Alternate
Courses
Exceptions
EX1: System fails


EX2: Wrong input format
1. An error message for wrong input format is displayed.

Version :1.4
22
7. Business Data Model and Data Dictionary

7a. Business Data Model
Content
A specification of the essential subject matter, business objects, entities, and
classes that are germane to the product. It might take the form of a first-cut
class model, an entity-relationship model, or any other kind of data model.
Version :1.4
23
7b. Data Dictionary

The glossary described earlier in section 4 of the template is the starting point for
establishing common understanding of terminology. As you start to define the scope
of the investigation you define the data inputs and outputs in a formal data dictionary.
The terms that you define in this dictionary, right down to elemental level, are the
same terms that you use when defining detailed atomic requirements.
.
Table Name
catalog
catalog
catalog
catalog
employee
employee
employee
employee
employee
employee
inventory
inventory
inventory
order
order
order
order
payment
payment
payment
Field name
itemcode
item_name
item_desc
price
employee_id
Name
Address
DataType
INT
VARCHAR(45)
VARCHAR(45)
VARCHAR(45)
INT
VARCHAR(45)
VARCHAR(45)
Field Description
Code of Item
Name of Item
Description of Item
Price of Item per unit
Employee ID
Employee Name
Employee Address
Employee Email Address used as
Email
VARCHAR(45) userid
Phone
VARCHAR(45) Employee Phone number
password
VARCHAR(45) Password of Employee
materialcode INT
Ingredient Material code
materialstock INT
Ingredient Material available quantity
materialnam
e
VARCHAR(45) Ingredient Material name
order_id
INT
Order Unique Identification number
order_time
DATETIME
Order Time
Status of Order (Ordered, Preparing,
status
VARCHAR(45) Ready to Deliver)
amount
INT
Total of all Item price in order
receipt_id
INT
Receipt Unique Number
name
VARCHAR(45) Instrument name & Type
amount
VARCHAR(45) Amount paid by employee
8. The Scope of the Product

8a. Product Boundary
A use case diagram identifies the boundaries between the users (actors) and
the product. Please refer section 6.
Version :1.4
24
9. Functional Requirements
9a. Functional Requirements
Requirement #: FR_01
Requirements Type: 1
Use Case: BU01
Date: Oct 12, 2016.

Introduction: Authentication
Rationale: Survey ABC-345 indicates that Employees needed authentication system to login into
company applications.
Author: Team 104
Source: Survey ABC-345
Inputs: Employee UserId & Password.

Requirement Description:
1. The User shall be able to login into system only if.
a. Employee Entered Valid User Id & Password.
2. System will verify credential and redirect to home page.
Outputs: Employee will be able log in.
Persistent Changes: NA
Related Requirements:
Conflicts: None
Support Materials: None
Test Cases: TBD
Version :1.4
25
Use Case: BU02
Date: Oct 12, 2016.

Introduction: Show Catalog
Rationale: Survey ABC-345 indicates that Catalog will aid in selecting order efficiently.
Author: Team 104
Inputs: Item code, Item Price, Item Description, Item name

1. The User shall be able to view catalog only if.
a. Item code & Item Price, Item Description, Item name is valid.
2. System will show all items with details to employee.
Outputs: Employee will be able to see Catalog
Related Requirements: NA
Conflicts: None
Test Cases: TBD
Version :1.4
26
Use Case: BU03
Date: Oct 12, 2016.

Introduction: Add Item in cart
Rationale: Survey ABC-345 indicates that add function can help in better user experience.
Author: Team 104
Inputs: Item Code

1. The User shall be able to add Item code to cart only if.
a. Item code is valid.
2. System will add Item Code in Cart.
Outputs: Item is added to the cart.
Conflicts: None
Test Cases: TBD
Version :1.4
27
Use Case: BU04
Date: Oct 12, 2016.

Introduction: Remove Item from cart
Rationale: Survey ABC-345 indicates that remove function can help in better user experience.
Author: Team 104
Inputs: Item Code

3. The User shall be able to remove Item code from cart only if.
a. Item code is available in cart.
4. System will remove Item Code from Cart.
Outputs: Item is removed from the cart.
Conflicts: None
Test Cases: TBD
Version :1.4
28
Use Case: BU05
Date: Oct 12, 2016.

Introduction: Checkout
Rationale: Survey ABC-345 indicates that check out functionality will ease operation.
Author: Team 104
Inputs: Item Code

1. The User shall be able to checkout only if.
a. Item code must be available in cart.
2. System will create object of item codes and will send to payment.
Outputs: Item is removed from the cart. System will generate Order Id.
Conflicts: None
Test Cases: TBD
Version :1.4
29
Use Case: BU06
Date: Oct 12, 2016.

Introduction: Payment
Rationale: Survey ABC-345 indicates that Payment is utmost required to complete any transaction with
reliability.
Author: Team 104
Inputs: Order Id, Bank Details (Instrument Type, Name ), Amount

1. The User shall be able to make payment only if.
a. Order Id exist in database.
b. Amount is non negative.
c. Bank details are valid and verified by bank.
2. Employee will be allowed to make payment for Items purchased in Order Id.
Outputs: Payment Receipt Id is generated. Order is confirmed.
Conflicts: None
Test Cases: TBD
Version :1.4
30
Use Case: BU07
Date: Oct 12, 2016.

Introduction: Cancel Order
Rationale: Survey ABC-345 indicates that Cancellation is must for customer service and reduced
escalation.
Author: Team 104
Inputs: Order Id, Bank Details

1. The User shall be able to cancel order only if.
b. Payment Receipt time is less than 20 minutes from current time.
c. Bank details are valid and verified by bank.
2. Employee will be allowed to cancel the order. Refund id will be generated.
Outputs: Order Status has been updated to Cancelled. Refund id is used to make payment to employee.
Conflicts: None
Test Cases: TBD
Version :1.4
31
Use Case: BU08, BU09
Date: Oct 12, 2016.

Introduction: Order Confirmation & Execution
Rationale: Survey ABC-345 indicates that Order Management is essential to produce efficient process.
Author: Team 104
Inputs: Order Id, Item Code

1. The Kitchen staff shall be able view order only if.
b. Item Code is valid and available in stock.
2. System will display Order ID & Item Code to Kitchen Staff to prepare the order.
3. Kitchen staff will update Order status to Ready once item is cooked. Employee would be
notified.
Outputs: Order Status has been updated to Ready. Employee will receive update.
Conflicts: None
Test Cases: TBD
Version :1.4
32
Use Case: BU10, BU11
Date: Oct 12, 2016.

Introduction: Inventory Management
Rationale: Survey ABC-345 indicates that Inventory Management will aid in replenishing stock for
smooth run of business.
Author: Team 104
Inputs: Material Code, Material Quantity, Material name, Vendor ID, Bank Details.
1. Inventory manager will be able to view report only if.
a. Material code exist in database
b. Material quantity has reached to minimum threshold.
2. Inventory manager will be able to place new order only if.
a. Vendor Id exist in database.
b. Bank verifies and validate payment.
3. Inventory manager will place order to buy material code displayed in inventory report.
Outputs: Placing order of material to vendor.
Conflicts: None
Test Cases: TBD
Version :1.4
33
Use Case: BU12
Date: Oct 12, 2016.

Introduction: Modify Catalog
Rationale: Survey ABC-345 indicates that Catalog should be regulated timely.
Author: Team 104
Inputs: Item Code, Item Desc, Item name, Item Price, Material Code, Material name
1. Cafeteria manager will be able to add or remove item in/from catalog only if.
a. Item details & Material details are valid.
b.
2. System will add/remove item & Material details in database.
Outputs: System will update catalog item details.
Conflicts: None
Test Cases: TBD
Version :1.4
34
Non-functional Requirements
The following sections 10-17 describe the non-functional requirements. The form of
these requirements is the same as for the functional requirements as described above.
10. Look and Feel Requirements

10a. Appearance Requirements
Requirements
The product shall be attractive and easy to use for employees.

The product shall comply with corporate branding standards.
The product shall be recognizable as a product belonging to the
specific cafeteria.
Fit Criterion
A sampling of representative employee shall, without prompting or
enticement, start using the product within four minutes of their first
encounter with it and shall be able to find out desired function within 1
minute of their menu search.
The office of branding shall certify that the product complies with the
current standards.
Employees are able to recognize the product as belonging to their
cafeteria the first time they use it.
10b. Style Requirements

Requirements
The product shall appear authoritative and secured.
Fit Criterion
After their first encounter with the product, 70 percent of

representative potential customers shall agree they feel they can
trust the product.
Version :1.4
35
11. Usability and Humanity Requirements

This section is concerned with requirements that make the product usable
and ergonomically acceptable to its hands-on users.
11a. Ease of Use Requirements

Examples
The product shall make it easy for the employees to enter his
information and items that he wants to order.
The product shall be easy for people with no strong background of

technology to use. The product shall help the user to avoid making
mistakes.
The product shall make the users want to use it.
The product shall be used by people with no training, and possibly no

understanding of English.
Fit Criterion
The Employees can enter in to the product his employee Id, Item
Code, requested quantity within 10 seconds without any training or
need to consult instructions.
Seventy percent of a test panel of digital immigrants shall be able to
successfully place an order within 4 minutes.
One months use of the product shall result in a total error rate of
less than 5 percent.
An anonymous survey shall show that 85 percent of the intended
users are regularly using the product after a three-week
familiarization period.
Version :1.4
36
11b. Personalization and Internationalization Requirements

Requirements
The Product shall automatically save last placed order.

The product shall show last items ordered in new order menu.
The product shall retain the buyers buying preferences.
The product shall only use English Language.
Fit Criterion
While placing order employee will be able to see a selection from
past order without cancelling order screen.
The product will load last ordered quantity of specific item in order
quantity box while placing new order.
Product shall save last mode of delivery for employee and shall
show the same option every time on checkout.
11c. Learning Requirements

Requirements
The product shall be easy for an employee to learn.

The product shall be used by all employees who will attend one
weeks of training before using the product.
A cafeteria staff shall be able to troubleshoot within a short time.
Fit Criterion
An employee shall order 5 items within 10 minutes of beginning to
use the product, without needing to use the manual.
After receiving 20 hours training a cafeteria staff shall be able to
troubleshoot (resolve any claim) 5 employees per 10 minutes.
11d. Understandability and Politeness Requirements

Requirements
The product shall use icons and words that are naturally
understandable by the employee community.
The product shall hide the details of its construction from the
employee.
Fit Criterion
The product will show relative icons like plate for items, wallet for
payment, cart for order checkout.
The product will only show function name and icon on screen
Version :1.4
37
12. Performance Requirements

12a. Speed and Latency Requirements
Requirements
Any interface between a employee and FastMeal shall have a

maximum response time of 2 seconds.
The response shall be fast enough to avoid interrupting the
employees flow of thought.
The product shall upload the new item catalog within 1 minutes of a
request.
Fit Criterion
The product shall respond in less than 1 second for 90 percent of the
interrogations. No response shall take longer than 2.5 seconds.
New item shall be uploaded in catalog in less than 50 seconds for
95% of the requests made. No request shall take more than 1.5
minutes to upload.
12b. Safety-Critical Requirements

NA
12c. Precision or Accuracy Requirements
Requirements
All monetary amounts shall be accurate to two decimal places.
All Quantities shall be accepted only in real numbers with no

decimal.
Fit Criterion
The product shall round off amount to nearest two decimal place.
The product shall only accept numerical value in quantity box. Non
numeric characters or decimals shall not be allowed.
Version :1.4
38
12d. Reliability and Availability Requirements

Requirements
The product shall be available for use 12 hours per day on official
working day only.
The product shall be available for use between the hours of 8:00 A.M.
and 8:00 P.M.
The product shall achieve 99 percent uptime.
12e. Robustness or Fault-Tolerance Requirements

Requirements
The product shall continue to operate in local mode whenever it

loses its link to the central server.
The Product shall place order only when it is linked to central server.
The product shall save last order placed in cart should it become
disconnected from the electricity source.
12f. Capacity Requirements

Requirements
The product shall cater for 500 simultaneous employees within the
period from 8:00 AM to 10:00 AM (Breakfast time) & 12:00 PM to
2:00PM (Lunch time) Maximum loading at other periods will be 200
simultaneous employees.
During a launch period, the product shall cater for a maximum of 30

employees for delivery of food and shall cater for a maximum of 50
employees for take away.
12g. Scalability or Extensibility Requirements

NA
12h. Longevity Requirements
Requirements
The product shall be expected to operate within the defined

maximum maintenance budget of $50k for a minimum of three
years.
Version :1.4
39
13. Operational and Environmental Requirements

13a. Expected Physical Environment
Requirements
The product shall be used by an employee, sitting, inside office, air

conditioned all the time.
13b. Requirements for Interfacing with Adjacent Systems

Requirements
The products shall work on the last four releases of the popular
browsers IE, Chrome, Safari, Firefox.
Product must be connected with server through company Intranet.
13c. Productization Requirements

Requirements
The product shall be uploaded on company intranet.

The product shall not require any installation on local machine to
start.
13d. Release Requirements

Requirements
The maintenance releases will be offered to end users once in a

4 months.
Each release shall not cause previous features to fail.
Version :1.4
40
14. Maintainability and Support Requirements

14a. Maintenance Requirements
Requirements
Product backlog should be updated in 5 days of requirement

freezing.
Any failure in existing functionality shall be supported with in 24

working hour.
14b. Supportability Requirements

Requirements
The product shall have support team which will operate by email
services. Employee shall escalate issues by email
(customer.carefastmeal@abc.com) and same shall be taken care with in
maximum turn around time of 24 working hours.
Below will be hierarchy of escalation:
Levek
1st Level
2nd Level
3rd Level
Authority
Cafeteria Manager
Cafeteria Product Manager
Ombudsman-Company
14c. Adaptability Requirements

Requirements
The product is expected to run under Windows 7 and MacOSx.
The product is designed to run in offices and also have a version

running in restaurant kitchens.
Fit Criterion
Product shall work on versions of Windows XP and more and
MacOSx LEOPARD version 8.1 and more.
Product will be enhanced for higher version in maximum 2 weeks of
new upgrade of operating system.
Version :1.4
41
15. Security Requirements

15a. Access Requirements
Requirements
Only Cafeteria staff having privilege of Super admin can only access
order modification menu.
Only Cafeteria Product manager can generate all order reports of

employees.
Only Company HR is allowed to view credential of employees.
Fit Criterion
Entity
Employee
Cafeteria Order Staff
Cafeteria Manager
Cafeteria Product Manager
Company HR Manager
Privilege
Basic User
Basic User
Admin
Super Admin
Super Admin
15b. Integrity Requirements

Requirements
The product shall lock employee credential if used more than 3 times
with wrong credential.
The product shall prevent incorrect data from being introduced.
The product shall protect itself from intentional abuse.
15c. Privacy Requirements

Requirements
The product shall reveal private information only in compliance with

the organizations information policy.
The product shall protect private information in accordance with the
relevant privacy laws and the organizations information policy.
Version :1.4
42
15d. Audit Requirements

Requirements
The product shall generate transaction report which will be

presented to company auditory.
Product shall also generate escalation report which will be audited
once in 6 months for actions taken in SLA.
15e. Immunity Requirements

Requirements
The product shall not allow any upload from client server other than
request in form of secured input data.
Product Server shall scan its repositories for viruses or other threats
in every 2 weeks.
Server shall have no open ports / sockets at any unauthorized
activity.
16. Cultural Requirements

16a. Cultural Requirements
NA
Version :1.4
43
17. Legal Requirements

17a. Compliance Requirements
Requirements
All matters will be redirected to company HR manager for final

decision.
Product shall comply to requirements laid by legal department of
company.
The product shall apply same rules and process to all employees.
Product shall also keep record and validate local food license / shop
establishment license of cafeteria.
Personal information shall be implemented so as to comply with the
Data Protection Act.
Product shall not save any illegal product entry in catalog.
Fit Criterion
Company Attorneys opinion that the product does not break any
laws.
Constant validity checks of various licenses stored in product and
alerts for renewal.
List of illegal items which can not be sold or prepared.
All Intellectual Property of product must have owned or legitimately
licensed by company.
17b. Standards Requirements

Requirements
The product shall be developed with CMM level standards.
The product shall comply with food industry standards.
The product shall be developed according to SSADM standard

development steps.
Version :1.4
44
Project Issues
18. Open Issues
Issues that have been raised and do not yet have a conclusion are:
The third-party support may shut down during payment processing
which results in inconvenience to the employees in placing the
order. This may also cause the security threat to the employees
credentials.
Some items shown on the menu may not be available due to
improper updating of the database which may cause inconsistency
in the database.
The software may not work as desired which may affect the
operation of the whole cafeteria.
19. Off-the-Shelf Solutions

19a. Ready-Made Products
Content
The system for authenticating the employees for this product can
be done in a similar way as the organizations authentication
process.
Showing items in the catalog can be taken from the existing
implementations of the requirements.
Adding or removing any item to/from the catalog should be
considered as one of the potential solutions.
Motivation
Feedback results of these potential solutions should be 70% to be used
for this application.
Considerations
New item can be added to the first page of the catalog to be considered
by the employees.
19b. Reusable Components

Content
Inventory Management should be considered as reusable

components and should be modified as per this projects
requirements.
Payment of the orders placed can be used from within the
company for this project.
Checkout also needs to be re-used depending on the
Version :1.4
45
requirements of this project.
Motivation
The reusable components can be used for this project only if they passed
70% of the testing process in their previous projects.
19c. Products That Can Be Copied

Specifications of the third-party support system can be bought from other
company which will reduce the analysis and designing efforts to almost
60 %.
20. New Problems

20a. Effects on the Current Environment
Any update to the database may not be loaded onto the website due to
some potential reasons which may affect the working of the product.
20b. Effects on the Installed Systems
Inventory Management system that is installed should comply with the

specifications of this project to have proper interface with other
components.
The payment system may not be interfacing with the project as required.
20c. Potential User Problems
The existing users may not be able to log into the system due to
authentication failure which should be taken into consideration and
should be recovered soon by fixing the authentication details.
The prospective users may not be able to access the application due to
failure in being added to the database.
20d. Limitations in the Anticipated Implementation

Environment That May Inhibit the New Product
Visitors visiting the company will not be able to access this application.
The project is intended only for potential employees of the organization
which have their own unique username and password and not for the
visitors.
20e. Follow-Up Problems

The project may shut down due to any technical issues.
Version :1.4
46
21. Tasks
21a. Project Planning
Content
The life-cycle of the project is as shown below:
Employee Authentication: Employees must enter their login credentials

to access FastMeal and place order. The credentials will be
authenticated from the organizations database.
Show Catalog, Add/Remove Item to/from Catalog: The catalog should
display all the items that can be ordered by the employees. There should
be feasibility for the Cafeteria Manager for adding and removing items
to/from the catalog.
Add/Remove Item to/from the Cart: Employee while ordering can add
items to the cart and can also remove items from the cart depending on
their choices of ordering. The order history should be maintained
properly.
Order Confirmation & Execution: The order should be confirmed from the
employee before checkout and then, the order is to e sent to the kitchen
for its execution.
Order Status: The order status should be updated every time and should
be accessed by employee, to check the update for his order.
Checkout & Payment: The checkout and payment should be
implemented for different modes and should be secured.
Inventory Management: The inventory should be maintained and
checked for the availability of any item required to prepare the order.
Version :1.4
47
Employee Authentication
Show Catalog,
Add/Remove Item to/from Catalog
Add/Remove Item to/from Cart
Order Confirmation & Execution
Order Status
Checkout & Payment
Inventory Management
Figure 8 Project Planning for FastMeal
Version :1.4
48
Form
ID
#
1
2
3
4
5
6
7
8
9
1
0
1
1
1
2
1
3
1
4
1
5
1
6
1
7
Task Name
Planning Phase
Initiation Process
Requirement Analysis Phase
Project requirement phase for setting meeting review
Revision & final proposal submits
Kickoff Meeting
Start-up Process
Identify Project Manager & Team Member
Identify partner Team: Delivery Partner, Supply Manager, Sales team
and Project Team
Client Communication Plan
Resource
#

R1

R1

R1
R1
R1
Contingency Plan
R1
Create Work Environment
R1
Create Project Binder
R1
Control/Reporting Process
Create Change Control Process
R1
Create Issue Management Process
R1
Create Status Tracking and Reporting Process
R1
Resources
Resource #
R1
R2
R3
R4
R5
R6
R7
R8
R9
R10
R11
R12
Resource Name
Project Manager
Cafeteria Manager
Client
Business Analysts
Employee
Subject Matter Expert
Marketing Expert
Testing
DBA
Technology Architect
Delivery Partner
Supply Manager
Version :1.4
49
21b. Planning of the Development Phases

ID #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Task Name
Development Phase
Design Process
Web Design & Development
Business Process Design

Represent and record required business events

Represent and record business rules and objects

Detail customer profiles

Define database schema

Prepare the requirement document

Take feedback

Present the requirement document for approval
Prepare content plan
Create Entity Relationship Diagram
Start workflow models
Interface Design

Add site elements

Gather basic site requirements

Include best practices for e-commerce
Cafeteria Model

Model interfaces and interactions with key users

Model post sale services
Plan interactions with other applications
Physical Database Design
Design Database Schema
System Design

Decide Acceptance Criteria

Develop User Test Cases

Develop Integration Test Cases

Develop System Use Cases

Plan Defect Management Process
Validation Process

Security Test

Usability & Humanity Test

Performance Test

Operational & Environmental Test

Maintainability & Support Test
Version :1.4
Resource #

R1, R4
R1, R4
R1, R5
R1, R4, R10
R1, R4
R1, R4
R1, R4
R1, R4
R1, R4
R1, R10

R4

R1, R4

R1, R3, R5
R8
R8
R8
R4, R8

R3, R5, R6

R1, R3, R5

R1, R3, R5
50
22. Migration to the New Product

NA
23. Risks
Risk Management
The Risk Management Plan identifies the risks associated with the
project, analyzes them and manages them by following mitigation steps.
Risk Analysis
Inter-Platform Compatibility:
There can be compatibility issues with the project as many employees
may access this application on different platforms.
Contingency Plan: The application may be subject to soe limitations on
features and platforms.
Probability: Medium
Impact: High
Data Security:
The application involves employee login credentials and bank details for
payment. This information needs to be secured to ensure that all the
transactions are carried out in a permissible way.
Contingency Plan: The application is used through intranet of the
organization to have security.
Probability: Medium
Impact: High
High Load:
The application can be used many employees at the same time, for
example, at lunch time. This can make the server slow down as
compared to the regular process.
Contingency Plan: The application should be tested properly during
downtime
Probability: Medium
Impact: Medium
System Reliability:
The application needs proper security to ensure the reliable system as it
involves crucial credentials of the employees.
Contingency Plan: The application needs to be tested properly with
respect to its security, during the regular maintenance.
Probability: Low
Impact: Medium
Version :1.4
51
Management Malpractice:
The Cafeteria staff should manage orders as the employees place them.
There can be possibility of having many orders placed at the same time.
Contingency Plan: The application should prioritize the orders based on
the time of placing.
Probability: Low
Impact: Low
These risks are quantitative risks which means they affect the cost of the
project but there are some risks involved called quantitative risk which
are not mentioned here but may affect the project activity and not cost.
Risk Impact Plan
The following table shows the risk matrix corresponding to the risk
numbers listed as follows:
Risk #
1
2
Risk Name
Inter-Platform Compatibility
Data Security
High Load
System Reliability
Management Malpractice
Version :1.4
52
24. Costs
Function Pointer analysis involves the complexity of function based on
their inputs/outputs and constraints. The UFP (Unadjusted Function
Pointer) for each component, used in this project, is first estimated
roughly. Below is some complexity based on the component.
Sr No
1
2
3
4
5
6
7
8
9
10
11
12
Requirements for Complexity

Bank Details
Employee Credential
ItemCode
Amount for Item
ItemCode in form of Menu
Material
Remove Item from Cart
Cancel Order
Purchase Inventory
Usability
Learning Requirements
Speed and Latency Requirements
Level of Complexity
Component
Simple
Average
Complex
Input Item
Output Item
11
Constraint
12
14
Functional Requirements
10
Non- Functional Requirements
15
The technical complexity factor (TCF) is computed, and degree of influence (DI)
of each component gives the total TCF of component.
TCF= 0.65+.018*DI of each components. Typically varies from 0.65 to 1.35.
Hence, the Function Point (FP) of each component will be:
FP = UFP*TCF.
Based on our calculation for each component, we end up the project cost at
$ 175K.
Version :1.4
53
25. User Documentation and Training

25a. User Documentation Requirements
User manuals.
The purpose of the document System Usability Support
The people who will use the document For now this
document provides information for both customer &
Client. This document will be used to develop separate
manuals for customer (employee) & client (Cafeteria
Staff) in Deployment & User Support Phase.
Maintenance of the document According to Change

Management
FastMeal User Manual.pdf
(Click link to open)
25b. Training Requirements

No training should be necessary for the employees to be able to use
the system. Some training may be necessary for those using the
back-end interface (Cafeteria Staff & Management). Training could
be provided by separate online sessions or videos by Company
Trainers.
26. Waiting Room

There is a Scope of below Business stream as extension to
Cafeteria services which could not be developed at this
release.
1.
Mobile Application Support (BYOD policy) Using Third Party

Framework to aces organization intranet (e.g. worx, citrix etc.)
2.
Onsite Restaurant (DINE IN) Cafeteria User can have extra menu to
add tables on which customer is being served
27. Ideas for Solutions

NA
Version :1.4
54

FastMeal SRS V1.5

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FastMeal SRS V1.5

Uploaded by

Copyright:

Available Formats

Project for CSCE-743 Software Requirements,

University of South Carolina, Columbia.

This is made solely for academic purpose.

CSCE-743 Software Requirements

University of South Carolina, Columbia

CSCE-743 Software Requirements

University of South Carolina, Columbia

CSCE-743 Software Requirements

University of South Carolina, Columbia

1. The Purpose of the Project

1a. The User Business or Background of the Project Effort

CSCE-743 Software Requirements

University of South Carolina, Columbia

Kitchen Order preparation

Order Completion Alert

Pick up / Delivery of Order

Post Sale Services

CSCE-743 Software Requirements

University of South Carolina, Columbia

1b. Goals of the Project

CSCE-743 Software Requirements

University of South Carolina, Columbia

Figure 2: Client Position Chart

CSCE-743 Software Requirements

University of South Carolina, Columbia

Figure 3: Organization Chart

Figure 4: Software Dev Life Cycle & Check Points

CSCE-743 Software Requirements

University of South Carolina, Columbia

2c. Other Stakeholders

Subject Matter Expert

Designers and developers &

Figure 5: Stakeholder Analysis

CSCE-743 Software Requirements

University of South Carolina, Columbia

2d. The Hands-On Users of the Product

2e. Priorities Assigned to Users

2f. User Participation

2g. Maintenance Users and Service Technicians

CSCE-743 Software Requirements

University of South Carolina, Columbia

3b. Implementation Environment of the Current System

CSCE-743 Software Requirements

University of South Carolina, Columbia

3e. Anticipated Workplace Environment

3f. Schedule Constraints

3g. Budget Constraints

4. Naming Conventions and Terminology

5. Relevant Facts and Assumptions

CSCE-743 Software Requirements

University of South Carolina, Columbia

5b. Business Rules

No Alcohol would be served.

Cafeteria is being managed by company itself.

There is no other cafeteria near by organization hence all employees

come to the same cafeteria.

Month of September to December is considered as down time for

company resources which can be utilized toward active requirement gathering.

All employees have access to intranet.

CSCE-743 Software Requirements

University of South Carolina, Columbia

6. The Scope of the Work

EMPLOYEE VISIT CAFETERIA

CSCE-743 Software Requirements