Software Requirements Specification

For

<E-Receipt system for Shinya Ramen House>

Version 1.0 approved

Prepared by <Yunwei Zheng>

<Shinya Ramen House>

<4/30/2019>
 Page ii

Table of Contents

Table of Contents .......................................................................................................................... ii

1. Introduction ..............................................................................................................................1

1.1 Purpose............................................................................................................................................. 1

1.2 Definitions ......................................................................................Error! Bookmark not defined.

1.3 Project Scope ................................................................................................................................... 2

1.4 References ........................................................................................................................................ 2

1.5 Overview of document ..................................................................................................................... 3

2. Overall Description ..................................................................................................................3

2.1 Product Perspective.......................................................................................................................... 3

2.2 Product functions ............................................................................................................................. 4

2.3 User Characteristics ......................................................................................................................... 5

2.4 Operating Environment .................................................................................................................... 5

2.5 Design and Implementation Constraints .......................................................................................... 6

2.6 Assumptions and Dependencies ...................................................................................................... 7

3. System Features .......................................................................................................................7

3.1 System Feature 1 .............................................................................................................................. 7

3.2 System Feature 2 .............................................................................................................................. 8

3.3 System Feature 3 .............................................................................................................................. 8

3.4 System Feature 4 .............................................................................................................................. 9

3.5 System Feature 5 .............................................................................................................................. 9

4. External Interface Requirements ...........................................................................................9

4.1 User Interfaces ................................................................................................................................. 9

 Page iii

4.2 Hardware Interfaces ....................................................................................................................... 10

4.3 Software Interfaces ........................................................................................................................ 10

4.4 Communications Interfaces ........................................................................................................... 10

5. Other Nonfunctional Requirements .....................................................................................11

5.1 Performance Requirements ............................................................................................................ 11

5.2 Safety Requirements ...................................................................................................................... 12

5.3 Security Requirements ................................................................................................................... 12

 Page 1

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of E-receipts system which can

create and manage Shinya Ramen House restaurant E-receipts. It is going to explain this system’

goals and characters, the functions of the system, the interfaces of the system, and the result of the

system try to achieve.

1.2 Definitions

In this project, there are 5 use cases, customer, waiter, cashier, restaurant system, and manager.

Definitions of all these use cases:

 Customer: The person spends money on food or service at Shinya Ramen House and there is

a chance to argue and get refund about their costs.

 Waiter: The person who gives service to customers and directly gets information from the

customer, such as customer name, email, telephone number, etc.

 Cashier: The person who directly deal with the record of customers and payment for the

customer. Moreover, he can store and check customer’s information and create, send E-

receipt to customer.

 Restaurant system: Shinya Ramen House E-receipt system can create and store E-receipt

due to customer cost records.

 Page 2

 Manager: The person who has all access to the system to manage all the information about

restaurant and customer record, including E-receipt record and history of customer spending

information.

1.3 Project Scope

This software system will design to solve all the receipt problems at Shinya Ramen House. This

system will be designed to store all the receipt record by creating E-receipt records and store it into

the database automatically if once payment completed. By managing the E-receipts effectively will

protect the benefits of restaurant and customers.

More specifically, this system can make sure there is an official receipt can check at the restaurant

when customers lost their receipts and need receipts to get their interests. This system can make

sure restaurant benefits from the E- receipt as well. Furthermore, it is a good way to collect

customer data and information by using legal means. Customer information will offer a lot of help

to the restaurant business.

1.4 References

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications.

IEEE Computer Society, 1998.

Valacich, J. S., & George, J. F. (2017). Essentials of Systems Analysis and Design, 8th

Edition. Chapter 13 -System Implementation starting on page 453

Rozanski, N. & Woods, E. (2005). The operational viewpoint. In Software Systems

Architecture, 325 – 352. Boston: Addison-Wesley.

 Page 3

1.5 Overview of the document

There are four chapters in this document. The first chapter describes what this system is, what this

system will do and what definitions in the system. In this second chapter, it will describe details of

the functionality of the product, such, function, User Characteristics, and Design and

Implementation Constraints. For the third chapter, it will focus on use cases in this product, focus

on the priority, action/result, and functional requirements. In the final chapter, external interface

requirements will be discussed and explained.

2. Overall Description

2.1 Product Perspective

This product is independent and totally self-contained for now. It will keep the record of customer

and restaurant to local hardware. An E-receipt system will create and keep the receipt information

of customers. It has functions like this.

 Create E-receipt form:

It can create E-receipt form automatically when the payment is completed. A form will keep

all the matter information for customer and restaurant, like total spending, time, last four number of

card, name of card, and E-receipt ID.

 Memorize the data of E-receipt:

 Page 4

This system not only creates an E-receipt but also keeps it. It is a strong proof when argues

happen. Meantime, it connects with customer information, how much customers total spending,

how often customers come. This information is good for the restaurant ad and business.

 Customer Information database

It includes customers name, email, telephone, address, spending details, coupon information.

2.2 Product functions

From this diagram of process

modeling, it is pretty clear about

what this product functions. This

software will make sure it keeps

customers information properly.

The interface of this product is the

computer in Restaurant.
 Page 5

2.3 User Characteristics

The user of the system should be able to get E-receipt from an email which sends by the employees

of Shinya Ramen House. And this E-receipt will keep all the rights as same as a paper receipt with

signature. There are a few situation customers may use the E-receipt. First, customer can get a

discount or coupon by showing the receipt to the restaurant. Second, customer can get refund when

the wrong payment happens. Third, customers need a receipt to calculate their expense. Therefore,

the customer should be able to do the following functions:

 Get a refund

 Question about tips

 Check spending history

 Get a discount or coupon

The Employee should have the following management functions:

 Get information about customers

 Keep all the data about E-receipts

 Do a refund to customers

2.4 Operating Environment

Operating environment for E-receipt system is as listed below.

 Distributed database

 Local system

 Operating system: Windows

 Database: database
 Page 6

 Platform: Java/ PHP

2.5 Design and Implementation Constraints

2.5.1 User constraints

The Shinya Ramen House is at the 31st south of Chicago where full of Asian, Latino or other

foreigners is. Sometimes part of them does not know they need to sign the receipts since they just

have been here a short time and do not figure out the rules. Near the area, there are a few

universities, so these customers are quite a lot. On the other hand, the other customers do not care

about it, so they just pay the pill and leave. Furthermore, there is a lot of people worry about their

personal information when they give to restaurant, like an email, address, telephone number.

2.5.2 Stakeholder constrains

Shinya Ramen House is a small business which just has a few stakeholders. Change means to spend

money and time. When this system offers to these stakeholders, they worried about it. Even if this

system is applying to the old system, it takes time to convince these stakeholders to accept it.

2.5.3 Employees constrains

The new system means new training. In this case, the cashier will do a little bit more job, and

waiters will get training about it. The problem is their education level is not high, so it indeed needs

time to do.
 Page 7

2.6 Assumptions and Dependencies

Let us assume things will happen.

1. Customers are not willing to give any information to the restaurant including email which

they can get E-receipt from. The restaurant can give a discount or coupon to a customer by

sending these to their email if customers give their email to the restaurant for the first time.

2. Shinya Ramen House lost and damages their local hardware. It is necessary to have a

backup database.

3. Maybe this system will develop an online application to achieve all the goals. Customer can

check their receipts from this app.

3. System Features

This system creates and keeps E-receipts for customers and Shinya Ramen House. This project has

a high priority because Shinya Ramen House gets all problems with receipts every day, like no

signature receipt, refund problem, wrong bill.

3.1 System Feature 1

3.1.1 Description: Adding a new customer

3.1.2 Priority: Top priority

3.1.3 Functional Requirements: customer adds name (first, middle initial and last name),

address (use zip code to fill in the city and state), phone number (use nnn-nnn-nnnn format)
 Page 8

and creates a customer id (6 character string including letters and numbers; must be unique to

the system).

3.2 System Feature 2

3.2.1 Description: Create new E-receipt

3.2.2 Priority: Top priority

3.2.3 Functional Requirements: E-receipt including Restaurant Name (full name), Time

(use YYYY-MM-DD hh:mm:ss. TZD format), Address (Street, City, State, Post number), Card

Number and (xxxx-xxxx-xxxx-0000), AUTH CODE, Server( name and table), Subtotal, Tips, Total,

and Sign of Customer Copy.

3.3 System Feature 3

3.3.1 Description: Send E-receipt to customer email.

3.3.2 Priority: Top priority

3.3.3 Functional Requirements: Email address (all the email address is fine, recommend

customer offer Gmail if customers have), E-receipt, coupon (discount, rules). The Cashier finishes

the payment and sends E-receipt to customers’ email if they are willing to get an E-receipt. Cashier

can directly send email to a customer who is already in the restaurant record system. For new

customer, Cashier needs to store the information of the new customer.

 Page 9

3.4 System Feature 4

3.4.1 Description: Keyword searching.

3.4.2 Priority: High

3.4.3 Functional Requirements: User enters a term into an input box or boxes; system

responds with Aquifer search results that match that term, regardless of where that term appears in

the record.

3.5 System Feature 5

3.5.1 Description: Saved Searches.

3.5.2 Priority: High

3.5.3 Functional Requirements: User can choose which queries in their search history they

want to save across sessions (assumes user accounts). (Also see Obtain for the ability to download

saved searches/records and/or subscribe to saved searches via email.)

4. External Interface Requirements

4.1 User Interfaces

For this system, there are three groups, manager, employees and customers.

Manager and employees can interact with the system by using the restaurant system. They have ID

and password to log in the system and operate it. All the information and process will show on the

screen of restaurant screen.

 Page 10

Customers can interact with the system by using a browser. Such, mobile phone, IPad, and

computer. When they log in their email account, they can check this E-receipt.

4.2 Hardware Interfaces

 Windows

 A browser which supports HTML& JavaScript

4.3 Software Interfaces

Software used:

Operating system: Windows operating system has been chosen for its best support.

Database: To save the customers’ records, payment records, SQL+ database is perfect.

4.4 Communications Interfaces

This system supports local network so far. It may support all types of web browsers in the future.

Once this system running on Shinya Ramen House well, it will become an application which is

suitable online.
 Page 11

5. Other Nonfunctional Requirements

5.1 Performance Requirements

This system must perform the implementation of this. There are access level, management level,

and database level. In the access layer, there are three types of user: manager, cashier and waiter.

Managers have all permission to access. Cashiers have part of them, including pay and input.

Waiters have only one permit to access view information. System management offer services to

managers. The manager can change, rewrite and delete raw data through system management. On

the other hand, the manager needs to check the daily report every day. Customer information is all

the most important information and data for the system. It needs to keep in a secure database.

Restaurants manager can make a discount or advertise according to customers’ information.

 Page 12

5.2 Safety Requirements

If there is extensive damage to a wide portion of the database due to catastrophic failure, the

recovery method restores a past copy of the database that was backed up to archival storage and

reconstructs a more current state by reapplying or redoing the operations of committed transactions

from the backed up log.

5.3 Security Requirements

● Only Manager or Sr Manager has the right to read, create, update and delete Employees

Account Information. This policy is Access Control; it keeps User authorization- to verify the users’

right to access specific information.

● Waiters and Cashiers can read customers information but can’t leak this information to others

who do not belong to this restaurant.

● All Employers or Employees cannot tell other people their password.

● All passwords cannot be less than 8 characters or the same passwords as others’ password.