Software Requirements

Specification
for

Cafeteria Ordering System,

Release 1.0
Version 1.0 approved

Prepared by Karl Wiegers

Process Impact

September 28, 2013

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page ii

Table of Contents
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Project Scope and Product Features............................................................................................1
1.4 References..................................................................................................................................1
2. Overall Description..................................................................................................................1
2.1 Product Perspective....................................................................................................................1
2.2 User Classes and Characteristics................................................................................................2
2.3 Operating Environment..............................................................................................................3
2.4 Design and Implementation Constraints.....................................................................................3
2.5 Assumptions and Dependencies.................................................................................................3
3. System Features.......................................................................................................................3
3.1 Order Meals from Cafeteria........................................................................................................3
3.1.1 Description.............................................................................................................................3
3.1.2 Functional Requirements........................................................................................................3
3.2 Order Meals from Restaurants....................................................................................................5
3.3 Create, View, Modify, and Delete Meal Subscriptions...............................................................5
3.4 Create, View, Modify, and Delete Cafeteria Menus...................................................................5
4. Data Requirements..................................................................................................................6
4.1 Logical Data Model....................................................................................................................6
4.2 Data Dictionary..........................................................................................................................6
4.3 Reports.......................................................................................................................................9
4.3.1 Ordered Meal History Report.................................................................................................9
4.4 Data Integrity, Retention, and Disposal......................................................................................9
5. External Interface Requirements.........................................................................................10
5.1 User Interfaces..........................................................................................................................10
5.2 Software Interfaces...................................................................................................................10
5.3 Hardware Interfaces..................................................................................................................10
5.4 Communications Interfaces......................................................................................................10
6. Quality Attributes..................................................................................................................11
6.1 Usability Requirements............................................................................................................11
6.2 Performance Requirements.......................................................................................................11
6.3 Security Requirements..............................................................................................................11
6.4 Safety Requirements.................................................................................................................11
6.5 Availability Requirements........................................................................................................11
6.6 Robustness Requirements.........................................................................................................11
Appendix A: Analysis Models.....................................................................................................12

Revision History
Name Date Reason For Changes Version
Karl Wiegers 8/15/13 initial draft 1.0 draft 1
Karl Wiegers 9/28/13 baseline following changes after inspection 1.0 approved

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 1

1. Introduction
1.1 Purpose
This SRS describes the functional and nonfunctional requirements for software release 1.0 of the
Online Fashion Shop. This document is intended to be used by the members of the project team
who will implement and verify the correct functioning of the system. Unless otherwise noted, all
requirements specified here are committed for release 1.0.

1.2 Document Conventions

No special typographical conventions are used in this SRS.

1.3 Project Scope and Product Features

Customers can browse through the store and buy them online without having to visit the store.A
detailed description is available in the Online Fashion Shop Management System Vision and Scope
Document [1], along with the features that are scheduled for full or partial implementation in this
release.

1.4 References
1. Group 1. Online Fashion Shop Management System Vision and Scope Document.
2. Beatty, Joy. Process Impact Intranet Development Standard, Version 1.3,
www.processimpact.com/corporate/standards/PI Intranet Development Standard.pdf
3. Rath, Andrew. Process Impact Internet Application User Interface Standard, Version 2.0,
www.processimpact.com/corporate/standards/PI Internet UI Standard.pdf

2. Overall Description
2.1 Product Perspective
Online Fashion Shop Management System is a software for selling fashion product online through
applications or websites on the internet which allowing customers can browse through the store and
buy them online without having to visit the store. The system is expected to grow through a number
of releases and links to credit and debit card authorization services. The context diagram in Figure 1
illustrates the external entities and system interfaces.

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 2

Figure 1. Context diagram for release 1.0 of the Online Fashion Shop Management
System.

2.2 User Classes and Characteristics

Customer Customers who want to buy but do not want to leave the home, customers can browse
through the store and buy them online without having to visit the store. Customers
include all Internet users in Vietnam so there will be a lot of potential customers so
there will be a lot of potential customers which is expected to have 500 visits to the
application or website every day, an estimated 20% of which will place an order, 10%
will return and continue to order (Customer retention).
Fashion shop Online Fashion Shop Management System about 5 Fashion Employees who will
Staff receive orders from COS, confirm orders, prepare products, pack them for delivery and
order delivery. room staff will be trained on the use of hardware and software for COS.
Product The product manager is an authorized employee who manages the quantity of products
Manager that enter and sell to the store. Product management will need to add new products
when a new model is available.
Product When Store Staff prepares an order for delivery, they will issue a delivery request to
Deliverer the delivery service provider. The shipper will receive the product and deliver it to the
customer. A shipper interactions with the OFSMS would be to confirm that a product
was (or was not) delivered.

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 3

2.3 Operating Environment

OE-1: The OFSMS shall operate correctly with the following web browsers: Windows
Internet Explorer versions 7, 8, and 9; Firefox versions 12 through 26; Google
Chrome (all versions); and Apple Safari versions 4.0 through 8.0.
OE-2: The OFSMS shall operate on a server running the current corporate-approved
versions of Red Hat Linux and Apache HTTP Server.
OE-3: The OFSMS shall permit user access from the corporate Intranet, from a VPN
Internet connection, and by Android, iOS, and Windows smartphones and tablets.

2.4 Design and Implementation Constraints

CO-1: The system’s design, code, and maintenance documentation shall conform to the
general rules of the group.
CO-2: The system shall use the current corporate standard SQL Server database engine.
CO-3: All HTML code shall conform to the HTML 5.0 standard.

2.5 Assumptions and Dependencies

AS-1: It is assumed that the hardware designed will work correctly with the third-
party operating system and the developed software The customer has a
computer with browser and have Internet.
AS-2: Each part of the user interface intends to be as user friendly as possible. The
fonts and buttons used will be intended to be very fast and easy to load on
web pages. The pages will be kept light in space so that it won’t take a long
time for the page to load.
AS-3: Users and the administrator are accustomed to the paper-based system and
would require training to use the online shopping-cart application.
AS-4: We assume that system users adhere to the system’s minimum software and
hardware requirements.
AS-5: This system will use third-party software, and it is assumed that system users
are familiar with the software.
DE-1: The details related to the product, customer, payment and service transaction
provided manually.
DE-2: Administrator is created in the system already.
DE-3: Roles and tasks are predefined.
DE-4: The product does require back-end database server SQL Sever for storing the
username and password for different types of user of the system as well as
various databases regarding various insurance information.

3. System Features
3.1 Order Product from OFSMS
3.1.1 Description

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 4

A customer with a verified identity can order products and be shipped to a specific
location. A customer can cancel an order if it has not been confirmed. Priority = High.

3.1.2 Functional Requirements

This section contains the requirements for the online shopping-cart application. The
functional This section contains the requirements for the online shopping-cart application.
The functional requirements, as collected from the users, have been categorized as follows to
support the types of user interactions that the system shall have..
FR01: The developers shall be able to view the source code for the entire
application.
FR02: The developers shall be able to, individually, view and understand the code
for all pieces on the UI.
FR03: The developers shall be able to debug the application’s source code using
Firebug, which is an online tool to inspect, edit, and monitor HTML, CSS,
and JavaScript requests directly on the web page.
User: View Categories and Items: The users shall be able to see the home page of the online
shopping-cart application when they first run the program. The users shall be able to view
the different categories, select categories, browse through the items in each category, and
add items to the shopping cart. The users shall be able to view the shopping cart and more
information about each item.
FR04: The users shall be able to view the categories on the application’s home page.
FR05: The users shall be able to view items in different categories.
FR06: The users shall be able add items to the cart.
FR07: The users shall be able to view more information about an item before adding
it to the cart.
FR08: The users shall be able to able view the shopping cart.
FR09: The users shall be able to browse through the available items.
User: View Shopping Cart: After the first run of the application, the users shall be able to
see their designated home page. After browsing through the items and adding items to the
shopping cart, the users should be able to view the items in the shopping cart. The users
shall
be able to check out or continue shopping. The users shall be able to delete items from the
cart.
FR10: The users shall be able to view the items added to the cart.
FR11: The users shall be able to check out with the current items in the cart.
FR12: The users shall be able to continue shopping.
FR13: The users shall be able to delete items from the cart.
User: Checkout Items
FR14: The users shall be able to check out items only when there are items in the
shopping cart.
Login/ User Authentication
FR15: The users shall login or register using the user authentication form.
FR16: The users shall not login or register if the information is incomplete or
invalid.
User: Place Order

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 5

FR17: The users shall place an order by completing the information in the order
form.
FR18: The users shall not be able to place an order if the information in the order
form is invalid or incomplete.
Admin: View User Information
FR19: The administrator shall be able to view all the users’ information that
completes the order form and the checkout process.
Admin: Add/Update/Delete Shopping Items
FR20: The administrator shall be able to add new items to the list of shopping items.
FR21: The administrator shall be able to modify/update an item’s price and
description.
FR22: The administrator shall be able to delete items from the main page of the
shopping-cart application.
FR23: The administrator shall be able to view the entire history of the checked-out
items.
FR24: The administrator shall be able to view the entire history for the users who
successfully complete the checkout process.

3.2 Order Meals from Restaurants

[Details are not provided in this example. Quite a lot of the functionality described under 3.1
Order Meals from Cafeteria could likely be reused, so this section should just specify the
additional functionality that addresses the restaurant interface.]

3.3 Create, View, Modify, and Delete Meal Subscriptions

[Details are not provided in this example.]

3.4 Create, View, Modify, and Delete Cafeteria Menus

[Details are not provided in this example.]

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 6

4. Data Requirements
4.1 Logical Data Model

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 7

Figure . Partial data model for release 1.0 of the Cafeteria Ordering System.

4.2 Data Dictionary

Data Description Composition or Lengt Values
Element Data Type h
+ customer name
+ customer phone
where and to whom a product
delivery number
is to be delivered, if it isn't
instruction + product date
select for the storage.
+delivery location
+delivery time window
delivery Address which an ordered hyphens and
alphanumeric 500
location product is to be delivered commas permitted
beginning time of from 2 days
to 7 days range on the
delivery time local time; from 2
product date during which an time day
window days to 7 days
ordered product is to be
delivered;
company ID number of the
employee ID customer who placed a integer 6
product order;
product item ext description of a product
alphabetic 200
description item on a menu
product item pre-tax cost of a single unit of
VNĐ 20
price a list product item
default = current
date if the current
time is before the
the date the product is to be
product date date, MM/DD/YYYY 10 order cutoff time,
delivered or picked up
else the next day;
cannot be prior to
current date
product order number
+ order date
details about a product a
product order + product date
Customer ordered
+ delivery instruction
+ product order status
unique ID that COS assigns
product order
to each accepted product integer 7 initial value is 1
number
order
incomplete,
product order status of a product order that accepted, prepared,
alphabetic 30
status a Customer initiated pending delivery,
delivered, canceled

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 8

payment amount
product information about a payment
+ payment method
payment COS accepted for a product
+ transaction number
product item
list product
description of a list item description
item
+ product item price
product order the date on which a customer
date, MM/DD/YYYY 20
date placed a product order
one list product item that a
ordered list product item
customer requested as part of
product item + quantity ordered
a product order
customer name
+ employee ID
a Process Impact employee
+ customer phone
customer who is authorized to order a
number
product
+ customer address
+ customer email
email address of the
customer email customer who placed a alphanumeric 100
product order
customer address of the customer who hyphens and
alphanumeric 100
address placed a product order commas permitted
customer name of the customer who
alphabetic 50
name placed a product order
AA-EE-NNNN-XXX for
telephone number of the area code of
customer
customer who placed a Vietnamese (A), 10
phone number
product order exchange (E), number
(N), and extension (X)
payment total price of an order in VNĐ
VNĐ 20
amount
how the customer is paying cash, credit card,
payment
for a product customer alphabetic 3 debit card
method
ordered
the number of units of each default = 1;
quantity product item that the maximum =
integer 10
ordered Customer is ordering in quantity presently in
product order inventory
unique sequence number that
transaction
COS assigns to each integer 12
number
payment transaction

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 9

4.3 Reports

4.3.1 Ordered Meal History Report

Report ID: COS-RPT-1

Report Title: Ordered Product History
Customer wants to see a list of all product that he had previously ordered
Report Purpose: from the Process Impact store, so customer can choose to buy the
product they liked.
Priority: Medium
Report Users: Customer
Data Sources: Database of previously placed product orders
Frequency and Report is generated on demand by a customer. Data in the report is
Disposition; static. Report is displayed on user's web browser screen on a computer,
tablet, or smartphone. It can be printed if the display device permits
printing.
Latency: Complete report must be displayed to customer within 4 seconds after it
is requested.
Visual Layout: Landscape mode
Header and Footer: Report header shall contain the report title, customer’s name, and date
range specified. If printed, report footer shall show the page number.
Report Body: Fields shown and column headings:
 Order Number
 Product Date
 Items ordered (list all items in the product order, their quantity, and
their prices)
 Total Food Price
 Tax
 Delivery Charge
 Total Price (sum of product item prices, tax, and delivery charge)

Selection Criteria: date range specified by customer, inclusive of end

points
Sort Criteria: reverse chronological order
End-of-Report
None
Indicator:
Interactivity: Customer can drill down to see ingredients and product information for
each item in the order
Security Access
A Customer may retrieve only his own product order history
Restrictions:

[Note: Other COS reports are not provided in this example.]

4.4 Data Integrity, Retention, and Disposal

DI-1: The COS shall retain Individual Customer product orders for 6 months following the
product delivery date.
DI-2: The COS shall retain list product for one year following the list date.

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 10

5. External Interface Requirements

5.1 User Interfaces
UI-1: Online Fashion Shop Management System screen displays shall conform to the
standard user interface of the group.
UI-2: The system will provide a help link from each website displayed and a help form in
the application to explain how to use it.
UI-3: The web pages shall permit complete navigation and product item selection by using
the keyboard, in addition to using mouse and keyboard combinations.

5.2 Software Interfaces

Software required to make working of product is:
SI-1: Operating System: Windows XP/vista/7 or later version, Linux OS which supports
networking.
SI-2: Net development tool kit.
SI-3: Web Brower: Internet Explorer (8.0 and above), Mozilla Firefox (3.0 and above), or
Google Chrome.

5.3 Hardware Interfaces

Hardware requirements for Insurance on internet will be same for both the parties which are
follows:
HI-1: Processor:- Pentium I or above.
HI-2: RAM: - 128 MB or above.
HI-3: HD: - 20 GB or above.
HI-4: NIC: - For each party.

5.4 Communications Interfaces

CI-1: Users can connect with system using browser and internet once user login user can
easily buy clothes.
CI-2: The two parties should be connected through either by LAN or WAN for the
communication.
CI-3: There is no maintainability or backup so availability will get affected.
CI-4: The system is a single user system.
CI-5: GUI features available.

6. Quality Attributes
6.1 Usability Requirements
USE-1: The COS shall allow a Patron to retrieve the previous meal ordered with a single
interaction.

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 11

USE-2: 95% of new users shall be able to successfully order a meal without errors on their
first try.

6.2 Performance Requirements

PER-1: The system shall provide bandwidth for 1000 users to access at the same time.
PER-2: The users shall be able to check out the items in the shopping cart within 10 seconds
after completing the order form.
PER-3: The users shall be able to add an item to the cart in fewer than 5 seconds.
PER-4: The application shall be able to do a validation check on the information provided in
the user-authentication form and the place-order form to avoid false or incomplete
information

6.3 Security Requirements

SEC-1: All transactions related to card information will be via 3rd application, personally
identifiable information shall be encrypted.
SEC-2: Users shall be required to log in to the OFSMS for all operations except viewing list
of product.
SEC-3: Only authorized Product Managers shall be permitted to work with product list.
SEC-4: The system will allow patrons to view only the orders they have placed or the
delivery status of the products they order.

6.4 Safety Requirements

SAF-1: The user shall be able to see a list of all ingredients in any menu items, with
ingredients highlighted that are known to cause allergic reactions in more than 0.5
percent of the North American population.

6.5 Availability Requirements

AVL-1: The system shall be made available to the user/administrator year round.

6.6 Robustness Requirements

ROB-1: If the connection between the user and the OFSMS is broken prior to a new order
being either confirmed or terminated, the OFSMS shall enable the user to recover an
incomplete order and continue working on it.
ROB-2: The system shall be able to save items to the shopping cart.

Copyright © 2013 by Karl Wiegers and Seilevel

Software Requirements Specification for Cafeteria Ordering System Page 12

Appendix A: Analysis Models

Figure 3 is a state-transition diagram that shows the possible meal order statuses and the allowed
changes in status.

Figure 3. State-transition diagram for meal order status.

Copyright © 2013 by Karl Wiegers and Seilevel