Software Requirement Engineering Lab

Experiment - 7
E-commerce Website - Software Requirement Specification Document

Priyanshi Anand - 2K20/SE/101

Shivya – 2K20/SE/130

1. INTRODUCTION
This system is designed for an E-commerce website which helps them to save the records of the
customers and their purchases. It also helps us save, access and modify product information. It
helps them from the manual work from which it is very difficult to find the record of a customer,
their purchases, complaints, refunds and and all the records. E-commerce provides an easy way to
sell products to a large customer base. However, there is a lot of competition among multiple e-
commerce sites. When users land on an e-commerce site, they expect to find what they are looking
for quickly and easily. Also, users are not sure about the brands or the actual products they want
to purchase. They have a very broad idea about what they want to buy.

1.1 Purpose
The Software Requirements Specification (SRS) will provide a detailed description of the
E-commerce website requirements. This SRS will allow for a complete
understanding of what is to be expected from the website which is to be
constructed. A clear understanding of the system and its functionality will allow for the correct
software to be developed for the end user and will be used for the development of the future stages
of the project. This SRS will provide the foundation for the project. From this SRS, the E-
commerce websites can be designed, constructed, and finally tested. This SRS will be used by the
system development team which is constructing the E-commerce website and the Website
customers. The Project team will use the SRS to fully understand the expectations of this E-
commerce website to construct the appropriate software. The customers will be able to use this
SRS as a “test” to see if the constructing team will be constructing the system to their expectations.
If it is not to their expectations, the end users can specify how it is not to their liking, and the team
will change the SRS to fit the end users’ needs.

1.2. Intended Audience and Reading Suggestions

The intended audience of this document would be the administrator and the customers/website
users and the project team to refer and analyze the sales, profits and other data.. The SRS document
can be used in any case regarding the requirements of the project and the solutions that have been
taken. The document would finally provide a clear idea about the system that is being built.
A brief outline of the document is:
 1. Overall Description
2. System Features
3. External Interface Requirements
4. Non-Functional Requirements

1.3. Scope
The introducing software, E-commerce website can be used as a template to create any kind of E-
commerce website, this will automate all the operations of offline shopping online so that people
can check out and buy things from the comfort of their home, or any remote place. The login
system helps a pre registered user login in to his/her account and then proceed with using the
website. The sign up/create account system helps a new user create an account and then use the
website. A user can use the website even if they haven't created an account, but they can't buy/save
things until they have logged in. The database will store all the user information, profile data, as
well as all the product information. There are two end Users for E-commerce website. The End
Users
are the Administrator (works at the company whose website it is) and the customers/users. The
administrator can access all the product information without any restriction, they can also access
the user information, but cannot edit the personal details, they can manage the user order details.
The end user can access the user profile, edit only the personal information, user can also access
the products but they will only have a view only accessibility, can't edit the details.
Login functions are used to keep restrictions for each End User level.
The objective of the automated Hotel Management System is to simplify the day-to-day
Shopping work. The system will be able to handle many services to take care of all customers in a
quick manner. As a solution to a large amount of file handling happening at the offline stores or
other shopping facilities, this software will be used to overcome those drawbacks. Safety, ease of
use and most importantly the efficiency of information retrieval are some benefits the development
team is going to present with this system. The system should be user appropriate, easy to use,
provide easy recovery of errors and have an overall end-user high subjective satisfaction.

1.4. Definitions & Abbreviations

● SRS: Software requirement specification
● System operator: System administrator
● RAM: Random access memory
● MERN: MongoDB, Express.js, React.js, Node.js tech stack.
● Customer: The user has the privilege to buy, return, replace products. They can also
add products to the wishlist.

1.5. References
Books:
[1] IanSommerville,Software Engineering 8th edition.Pearson education,2008.
[2] ElmasriNavathe,Fundamentals of Database System 3rd edition.Pearson education,2000.
[3] RaguRamakrishnan/JohnesGehrke,Database Management Systems
3rdedition.McGrow-HILL,2003.

2. OVERALL DESCRIPTION

2.1 Product Perspective

2.1.1 Hardware Interfaces
The requirements of a desktop computer are to access the web browser where the system will run.
A specific computer must match with the above-mentioned requirements to gain the maximum
benefits from the system efficiently. The order tracking details and information are sent to the user
email id, so there is a need for a broadband internet connection. Clients should be able to keep a
stable internet connection. A printer will be needed when printing bills and several reports.
● Intel x86 or compatible processor
● Minimum of 512 MB RAM
● Minimum of 50 MB hard drive space
● TCP/IP protocol support
● Compatible operating systems:
● An x86 Linux operating system.
● A 64-bit Windows operating system such as Windows Vista, Windows 7, Windows
8,
● Windows 10, Windows Server 2008 or Windows Server 2012.
● An OS X operating system x64.

2.1.2. Software Interfaces

The MERN stack is a complete open source combination, all JavaScript-related technologies are
also the hottest today: MongoDB, Express.js, React / React Native, NodeJS.
● MongoDB is an open source database; it is also the leading NoSQL (*) database currently
used by millions of people. It is written in one of the most popular programming languages
today. In addition, MongoDB is cross-platform data that operates on the concepts of
Collections and Documents, providing high performance with high availability and ease of
expansion.
● Express.js is a framework built on top of Nodejs. It provides powerful features for web or
mobile development. Express.js supports HTTP and middleware methods, making the API
extremely powerful and easy to use.
● React. js is an open-source JavaScript library used to build user interfaces specifically for
single-page applications. It's used for handling the view layer for web and mobile apps.
● Node.js is an open source, a system application and furthermore, is an environment for
servers. Nodejs is an independent development platform built on Chrome's JavaScript
 Runtime that can build network applications quickly and easily. Google V8 JavaScript
engine is used by Node.js to execute code. Moreover, a huge proportion of essential
modules are written in JavaScript.

2.1.3. Communications Interfaces

When a specific product is ordered at the same time an email notification will be sent to the
customers’ mail ID. The customer will be notified about the order status, and will be able to track
the product. To achieve that functionality, it requires having a stable internet connection. Mostly
a broadband connection with the client’s computer will provide the efficient service.

2.1.4 User Interfaces

● User friendly homepage
● User profile
● Payment page
● Product list - category wise
● Individual product details
● Accessing and updating the cart and wishlists
● Return/cancellation page.
● Posting/viewing product reviews.

2.2 Product Functions

● Search for product
● View product information
● Manage products (add, update, remove)
● Create account
● Update account information
● Login using existing account
● Manage customers (update order details, process the complaint requests)
● Place an order and pay for it
● Track order
● Return and refund order
● Replace order
● View/post product details

2.3 User Characteristics

Administrator:
The administrator has the privilege of doing all the tasks related to the website and the
products. He can access every function performed by the system. As the administrator he
will have the power to add, delete, update the products. Manage customer requests like
return, replace or refund requests. The administrator can generate reports regarding
products and user reports as well. He’ll also have the power to remove a user from the
database if they violate any basic terms of the website. Taking backups of the system and
restoring the system can also be done by the admin.

Customer:
The customer can create an account, and then login using the registered number or email
ID. Then the customer can view products category wise on the homepage, and proceed to
check a subcategory or any specific product. The customer can also add the products to
cart or wishlist. If the customer wants to buy a product he can go to the checkout page and
make the payment. A customer can also post or view product reviews. If the customer faces
any issues, he/she can file a complaint for a return, refund or cancellation of the order.

2.4. Constraints
Software development crew provides their best effort in developing the system. In order to
maintain the reliability and durability of the website, some design and implementation
constraints are applied. Availability of an android app for E-commerce could make the
system portable but due to time constraint it is not possible. System will need a minimum
memory of 512MB. But it is recommended to have a memory of 1GB. When designing
interfaces of websites, we had the capability of working with new tools such as Dev
Express. Considering the client’s budget we decided to create those interfaces in a simple
realistic manner using affordable
technology.

2.5. Assumptions and Dependencies

Some software used in implementing the system is with high cost and the client has agreed
to afford the amount of money needed to purchase them. It’s assumed that the client won’t
change that decision on the next phases of the software development. Although we assume
that the client is using windows 7,8 or 10. Otherwise, if the client uses an open-source
operating system, there is a need to change the SRS accordingly.
 3. SPECIFIC REQUIREMENTS
This system is designed for an E-commerce website which helps them to save the records of the
customers and their purchases. It also helps us save, access and modify product information. It
helps them from the manual work from which it is very difficult to find the record of a customer,
their purchases, complaints, refunds and and all the records. E-commerce provides an easy way to
sell products to a large customer base. However, there is a lot of competition among multiple e-
commerce sites. When users land on an e-commerce site, they expect to find what they are looking
for quickly and easily. Also, users are not sure about the brands or the actual products they want
to purchase. They have a very broad idea about what they want to buy.

3.1. External Interfaces

The E-commerce Website will use the standard input/output devices for
personal computers. This includes the following:

● Keyboard
● Mouse
● Monitor
● Printer
3.1.1 User Interfaces
● User friendly homepage
● User profile
● Payment page
● Product list - category wise
● Individual product details
● Accessing and updating the cart and wishlists
● Return/cancellation page.
● Posting/viewing product reviews.

3.1.2. Software Interfaces

The MERN stack is a complete open source combination, all JavaScript-related
technologies are also the hottest today: MongoDB, Express.js, React / React Native,
NodeJS.
● MongoDB is an open source database; it is also the leading NoSQL (*) database
currently used by millions of people. It is written in one of the most popular
programming languages today. In addition, MongoDB is cross-platform data that
operates on the concepts of Collections and Documents, providing high
performance with high availability and ease of expansion.
● Express.js is a framework built on top of Nodejs. It provides powerful features for
web or mobile development. Express.js supports HTTP and middleware methods,
making the API extremely powerful and easy to use.
 ● React. js is an open-source JavaScript library used to build user interfaces
specifically for single-page applications. It's used for handling the view layer for
web and mobile apps.
● Node.js is an open source, a system application and furthermore, is an environment
for servers. Nodejs is an independent development platform built on Chrome's
JavaScript Runtime that can build network applications quickly and easily. Google
V8 JavaScript engine is used by Node.js to execute code. Moreover, a huge
proportion of essential modules are written in JavaScript.

3.1.3. Communications Interfaces

When a specific product is ordered at the same time an email notification will be sent to
the customers’ mail ID. The customer will be notified about the order status, and will be
able to track the product. To achieve that functionality, it requires having a stable internet
connection. Mostly a broadband connection with the client’s computer will provide the
efficient service.

3.2 Product Functions

● Search for product
● View product information
● Manage products (add, update, remove)
● Create account
● Update account information
● Login using existing account
● Manage customers (update order details, process the complaint requests)
● Place an order and pay for it
● Track order
● Return and refund order
● Replace order
● View/post product details

3.3. Performance Requirements

Performance requirements define acceptable response times for system
functionality.
● The load time for user interface screens shall take no longer than two
second.
● The log in information shall be verified within five seconds.
● Queries shall return results within five seconds.
3.4. Logical Database Requirements

The logical database requirements include the retention of the following data
elements. This list is not a complete list and is designed as a starting point for
development.

Booking/Reservation System

● Customer-first name
● Customer last name
● Customer address
● Customer phone number
● Number of occupants
● Assigned room
● Default room rate
● Price description
● Checkout details(yes/no)
● Credit card number
● Confirmation number
● Automatic cancellation date
● Purchase date
● Return filed / Return date
● Customer feedback
● Payment received (yes/no)
● Payment type
● Total Bill

3.5. Design Constraints

3.5.1. Standards Compliance

There shall be consistency in variable names within the system. The graphical user
interface shall have a consistent look and feel.

3.6. Software System Attributes

3.6.1. Reliability

Specify the factors required to establish the required reliability of the software system
at time of delivery.
 3.6.2. Availability

The system shall be available at all hours of operation.

3.6.3. Security

Customer Service Representatives and Managers will be able to log in to the E-commerce
Website. Customer Service Representatives will have access to the Order and the cart
details. Managers will have access to the Management subsystem as well as the user
details. Access to the various subsystems will be protected by a user login screen that
requires a username and password.

3.6.4. Maintainability

The E-commerce Website is being developed in MERN Stack.

3.6.5. Portability

The E-commerce Website shall run in any desktop environment which supports a
browser that can run MERN Stack based web applications.

3.7. Organizing the specific requirements

3.7.1. System mode

The system performs as expected in all supported browsers in online mode.

3.7.2. User Class

Admin: Admin has the privilege of Monitoring and authorization of all the tasks handled
by the system. He can access every function performed by the system. Owner of the
company as well as the system can access the administration panel which is considered
the core of the system. As the main authorized person of the company, the owner gets the
ability to manage the other users including their user levels and privileges. Taking
backups of the system and restoring the system can also be done by the Owner.
Meanwhile he will be able to take all the kinds of reports available in the system. As the
owner of the system and the company he has the power to set room rates as well. Hotel
owners have the sole right of deleting a staff member from the system database.
User: The user has the power to order a product as well as return or cancel the order. I: f
the product order is placed mistakenly. The user can easily sort all the products on the
categorial basis. The user can simply manage the cart and can easily perform actions such
as deletion of product from the cart, making payment for the given product. The user will
be having a profile which can be managed easily, and can simply edit the profile as the
user comforts.

3.7.3. Feature

a) Validity Checks: JavaScript provides validity checks for various fields in the forms.

b) Sequencing Information: All the information regarding room details, guest list,
food details, and display of booking details should be handled sequentially that is, data
should be stored only in a particular sequence to avoid any inconvenience

c) Error Handling: If any validations or sequencing flows do not hold true, then
appropriate error messages will be prompted to the user for doing the needful.

3.7.4. Functional Hierarchy

Hierarchically at the top, admin has all the authority to manage the other users including
their user levels and privileges. Taking backups of the system and restoring the system
can also be done by the owner. Meanwhile he will be able to take all the kinds of reports
available in the system. The user will place an order after successfully completing the
payment, then the user product will be added to the cart of the user. The storehouse will
be given an alert to deliver the product within the given time range. The user can also
return the product easily. In case of return the return alert will be generated if the user is
allowed to return the product, then the return handling department will be notified about
the return to be taken by the delivery person.

3.8. Additional Comments

We may choose any one organization and the selection is dependent on the developer’s
expertise, previous experience, customer’s expectations, available technologies, etc.
Sometimes, more than one organization may also be used for organizing section 3 of the
SRS document.
 4. SUPPORTING INFORMATION
A system context diagram as well as use cases and use case descriptions, table of contents
have been developed in separate documents.

4.1. Table of Contents

S. No. Document Outlines Page No.

1 Introduction 1-3
1.1 Purpose
1.2 Intended audience and reading suggestions
1.3 Scope
1.4 Definitions, acronyms and abbreviations
1.5 References

2 Overall Description
2.1 Product Perspective 4-6
2.1.1 Hardware Interfaces
2.1.2 Software Interfaces
2.1.3 Communications Interfaces
2.1.4 User Interfaces
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions And Dependencies

3 Specific Requirements 7-12

3.1 External Interfaces
3.1.1 User Interfaces
3.1.2 Software Interfaces
3.1.3 Communications Interfaces
3.2 Product Functions
3.3 Performance Requirements
3.4 Logical Database Requirements
 3.5 Design Constraints
3.5.1 Standards Compliance
3.6Software System Attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organizing The Specific Requirements
3.7.1 System Mode
3.7.2 User Class
3.7.3 Feature
3.7.4 Functional Hierarchy
3.8 Additional Comments

4 Supporting Information 13-14

4.1 Table Of Contents