Chapter - 1

Software Requirements Specification

1. Introduction
The introduction of the Software Requirements Specification (SRS) provides an overview of the
entire SRS with purpose, scope, definitions, acronyms, abbreviations, references and overview of the
SRS. The aim of this document is to gather and analyze and give an in-depth insight of the complete
SHOPAHOLIC by defining the problem statement in detail. Nevertheless, it also concentrates on the
capabilities required by stakeholders and their needs while defining high-level product features. The
detailed requirements of the SHOPAHOLIC are provided in this document.

1.1 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come up to define
the system, its requirements with respect to consumers. Also, we shall predict and sort out how we
hope this product will be used in order to gain a better understanding of the project, outline concepts
that may be developed later, and document ideas that are being considered, but may be discarded as
the product develops.

In short, the purpose of this SRS document is to provide a detailed overview of our software product,
its parameters and goals. This document describes the project's target audience and its user interface,
hardware and software requirements. It defines how our client, team and audience see the product and
its functionality. Nonetheless, it helps any designer and developer to assist in software delivery
lifecycle (SDLC) processes.

1.2 Document Conventions

While writing this SRS, the basic convention of headings being larger in font size than the text,
and making them bold to give an organized look, as well as providing them with numbered
bullets, was followed.

 All the text in this SRS is written in Times font.

 The headings have the font size 20.

 The sub-headings will have font size 18.

 The text is written in font size 16.

 Important points are written in bullets.

1.3 Intended Audience and Reading Suggestions

This is suitable for the project manager, developer and the client to well understand the project
requirements and thus change them accordingly.

 Developers - Take into consideration the objective of the project.

 Project Manager - The development should take place stepwise.

 Users - Read the working of the project.

1.4 Project Scope
Shopping cart is one of the important facility provided in online shopping, this lets customer to
browse different goods and services and once they select an item to purchase they can place the item
in shopping cart, and continue browsing till the final selection. Customers can even remove the items
from shopping cart that were selected earlier before they place the final order. It reminds us of
shopping basket that we carry in departmental store.

References

 www.google.co.in
 www.wikipedia.com
 http://srs-onlineshopping.blogspot.in

2. Overall Description
2.1 Product Perspective
Relationship with other products and principal interfaces The interface will be in 2 basic parts

1. The businessman interface for data deletion, entry and the management of the policy set. The
above encompasses all shopkeeper functions such as changing the item information, managing the
dispatch time-table and others.

2. The customers interface for buying goods and querying. This shall also include a bulletin board
which shall serve as a platform for selling goods and by extension thereby, auctions.The interface will
provide for an easy search so that the customer will be able to locate the product of his choice
easily.

2.2 Product Features

The online shopping-cart application would have the following basic features:

1. Display all the categories available for shopping on the system’s main page.

2. Display all the items linked to each category listed on the main page.

3. Allow the administrator to add new items to the existing list of available items.

4. Allow users/administrator to remove items.

5. Allow the administrator to modify the price of each item.

6. Allow the administrator to update the description about each item.

7. Allow the administrator to view and edit information about each user that checkouts the items

from the system.

2.3 User Classes and Characteristics
The users of the online shopping-cart application, based on their roles, are customers (users) and the
administrator (owner). These users are identified based on their experience and technical expertise.

1. Admin: The administrator is the owner of this online shopping-cart application. One must have a
basic understanding of computers and the internet as well as prior knowledge for operating the
eclipse and Java programming languages. The administrator is responsible for maintaining all the
training documents required for the system. The administrator can perform the following functions:

 Assign or change the price of the items, update the items in the list, and delete the items.

 Assign sales tax for different states at the time of checkout.

 View the history of the customers who purchased the items.

2. Users: The users of this online shopping-cart application are all customers who would shop to test
the application. These users are anyone with shopping experience and the know-how to browse
through a shopping-cart application. They must have basic understandings about computers and the
internet. The users should be able to perform the following functions using this system:

 View, browse, and select a category on the home page.

 View, add, and update items in the cart.

 Delete items from the cart.

 Check out the items from the application or continue shopping

 Sign-on/login using a username and password.

 Place the order by completing the order form.

2.4 Operating Environment

1. Hardware requirements

Number Description Alternative(If any)

1. PC with 80 GB hard-disk Not-Applicable

and 512 MB RAM

2. Software requirements

Number Name Description Alternatives(If any)

1 Operating System Windows operating system Not-Applicable

2 Front- End HTML

3 Back- End Derby

4 Web server GlassFish

3. Internet connection

An internet connection is required to use Facility Access for the Web. A broadband (DSL or cable) or
faster connection is recommended.

2.5 Design and Implementation Constraints

The speed limitations i.e. the content that can be placed on a page was kept as less as possible so
that the pages were light enough. Also the security limitations did not allow to create many
functions.

 Security: The files in which the information regarding account should be secured against
malicious deformations.
 Fault Tolerance: Data should not become corrupted in case of system crash or power failure.
2.6 User Documentation

The web site in itself is really user friendly. So there is no need for anyone to have any
tutorial or any kind of a user manual.

2.7 Assumptions and Dependencies

The assumptions and dependencies are as follows:

1. Users and the administrator are accustomed to the paper-based system and would require
training to use the online shopping-cart application.

2. The system is dependent on the availability of an Apache Tomcat Server to run.

3. We assume that system users adhere to the system’s minimum software and hardware
requirements.

4. This system will use third-party software, and it is assumed that system users are familiar with the
software.

3. System Features
3.1 Secure login to Interface
3.1.1 Description and Priority
This feature will give the user a secure and simple login screen. It is based on professor
Cubert’s exclusionary principle. This means rather than creating try catches for a handful of
error types, it just has only a handful of available and possible inputs, to prevent any improper
logging in, which might cause unexpected errors, and therefore limiting the system’s
capabilities.
 3.1.2 Stimulus/Response Sequences
It will consist of two basic fields, Username and Password. There are two buttons: Login and
Lost or Forgot Password. Login will submit the entered data for approval followed by access,
and the forgot password will direct the user to access his/her password which has been
forgotten.
3.1.3 Functional Requirements
1. Sell Configured to Ordered Products.

2. Provide comprehensive product details.

3. Detailed product Categorization

4. Provide Search facility.

5. Maintain customer profile

6. Provide personalized profile

7. Provide Customer Support

8. Email confirmation

9. Detailed invoice for customer.

10. Provide shopping cart facility

11. Provide multiple shipping methods

12. Online tracking of shipments

13. Provide online Tax Calculations

14. Allow multiple payment methods

15. Allow online change or cancellation of order

16. Allow Online Product reviews and ratings

17. Offer financing options.

18. Provide detailed sitemap.

19. Offer online promotions and rewards.

20. Online Purchase of products.

4. External Interface Requirements

4.1 User Interfaces
The user interface for the software shall be compatible to any browser such as Internet Explorer,
Mozilla or Netscape Navigator by which user can access to the system.
The user interface shall be implemented using any tool or software package like Java Applet, MS
Front Page, EJB etc.

4.2 Hardware Interfaces

Since the application must run over the internet, all the hardware shall require to connect internet will
be hardware interface for the system. As for e.g. Modem, WAN - LAN, Ethernet Cross-Cable.
4.3 Software Interfaces

1. The e-store system shall communicate with the Configurator to identify all the available
components to configure the product.

2. The e-store shall communicate with the content manager to get the product specifications,
offerings and promotions.

3. The e-store system shall communicate with bill pay system to identify available payment
methods, validate the payments and process payment.

4. The e-store system shall communicate to credit management system for handling
financing options.

5. The e-store system shall communicate with CRM system to provide support.
6. The e-store system shall communicate with Sales system for order management.
7. The e-store system shall communicate with shipping system for tracking orders and
updating of shipping methods.

8. The e-store system shall communicate with external Tax system to calculate tax.
9. The e-store system shall communicate with export regulation system to validate export
regulations.

10. The system shall be VeriSign like software which shall allow the users to complete
secured transaction. This usually shall be the third party software system which is widely
used for internet transaction.

4.4 Communications Interfaces

The e-store system shall use the HTTP protocol for communication over the internet and for
the intranet communication will be through TCP/IP protocol suite.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
The product shall be based on web and has to be run from a web server.

The product shall take initial load time depending on internet connection strength which also depends
on the media from which the product is run.

The performance shall depend upon hardware components of the client/customer.

5.2 Safety Requirements
The database may get crashed at any certain time due to operating system failure or virus. Therefore,
it is required to take the database backup or to use any Standby Server so that there is no chances
that our database will destroy.

5.3 Security Requirements

Data Transfer
The system shall use secure sockets in all transactions that include any confidential customer
information.

The system shall automatically log out all customers after a period of inactivity.

The system shall confirm all transactions with the customer's web browser.

The system shall not leave any cookies on the customer's computer containing the user's password.

The system shall not leave any cookies on the customer's computer containing any of the user's
confidential information.
Data Storage
The customer's web browser shall never display a customer's password. It shall always be echoed
with special characters representing typed characters

The customer's web browser shall never display a customer's credit card number after retrieving from
the database. It shall always be shown with just the last 4 digits of the credit card number.

The system's back-end servers shall never display a customer's password. The customer's password
may be reset but never shown.

The system's back-end servers shall only be accessible to authenticated administrators.

The system's back-end databases shall be encrypted .

5.4 Software Quality Attributes

1. Integrity

 QA01: The authorized user shall be allowed to access the online shopping-cart
application.

 QA02: Based on the user type, the online shopping cart application shall provide a
userspecific interface.

2. Correctness

 QA03: The assigned task should be received by the specified user.

3. Availability

 QA04: The system shall be made available to the user/administrator year round.

4. Robustness

 QA05: The system shall be able to save items to the shopping cart.
6. Other Requirements
 A presentable, fast and easy user interface

 Members displayed on the main page

 The presentable appeal of the web pages

 Easy navigation so that the users do not have to fumble through much