Software Requirements Specification

For
Online Shopping For NewShopee

Index
Introduction
Pupose
References
Overview
Overall Description
1. Product Perspective
i.) User interface
ii.) Admin interface
iii.)Hardware interface
iv.) Software interface
Product Functions
Use- Case diagram
ER- Diagram
Specific Requirement
i.) Functional Requirements
ii.) Non-Functional Requirements

Introduction

The Software Requirements Specification is designed to document and

describe the
agreement between the customer and the developer regarding the
specification of the
software product requested . Its primary purpose is to provide a clear and
descriptive
statement of user requirements that can be used as a reference in further
development of the software system. This document is broken into a number of
sections
used to logically separate the software requirements into easily referenced
parts.
This Software Requirements Specification aims to describe the Functionality,
External
Interfaces, Attributes and Design Constraints imposed on Implementation of
the
software system described throughout the rest of the document. Throughout
the
description of the software system, the language and terminology used should
unambiguous and consistent throughout the document.

1.1 Purpose
Defining and describing the functions and specifications of the ECommerce
System is the primary goal of this Software Requirements Specification (SRS).
This Software Requirements Specification illustrates, in clear terms, the
systems primary
uses and required functionality as specified by our customer.
The intended audience of this document is our primary E-Commerce System
customer.

1.2 Scope
The software system being produced is called E-Commerce System. It is
being produced for a customer interested in selling books via the Internet. This
system is
designed to provide automation support for the process of placing various
electronics for sale on
the Internet and facilitating the actual sale. This system is largely crossplatform and is
available to anyone using the Computer Science Departments provided
computer
resources in the MSU Engineering Building. The system will be run on a central

server
with each user having a remote user interface through a web browser to
interact with it.
The Book E-Commerce System will allow any user to create an account to
become a
customer. The customer, through the process of account creation, will have the
option to
become a member of the site. The system will allow customers to browse,
search, select,
and add various lifestyle to a shopping cart. Then, provided they have item in
their shopping cart,
check out the item in shopping cart and decrement the stock that the inventory
the system
maintains. The ECS also allows a manager to manage the inventory with full
create,
retrieve, update and delete (CRUD) functionality with regards to item in the
system. It
will also allow, on an inventory wide basis, customers and managers to interact
with a
promotion system that handles percentage-off promotions that can be applied
to
members orders. This interaction includes the creation (by managers) and the
application
to orders (by customers) of the promotions. The BECS has full email
capabilities; the
automated email functionality will be used to send promotions to members of
the system
as well as provide the managers with low-stock notifications.
The ECS will have numerous constraints on what it can do. The system will not
have
full credit-card processing capabilities. It will not allow managers to be
customers. The
manager will be a hard-coded user and only a single manager will exist. There
will be no
actual book ordering and order completion, however the system will provide
the
customer with a receipt and it will log the transaction details. The system will
not allow
multiple promotions to be added to a single shopping cart nor will it allow a
customer to
add more than one of each item to their cart. The system also will not allow
users to
retrieve passwords or edit their user details.

Overall Description

This section includes details about what is and is not expected of the ECS
system in
addition to which cases are intentionally unsupported and assumptions that will
be used
in the creation of the ECS system.

2.1 Product Perspective

The online shopping application is a web-based system. It can be accessed using Internet Explorer 8.0
and above, Mozilla Firefox 2.0, and Google Chrome.
The two interface types found in the online shopping-cart application are as follows:
1. User Interface:
Users are able to view the home page of the online shopping application, browse the
different categories, browse and add any number of items from any categories in the shopping cart, look
for information about each product, delete the items in the shopping cart, save the cart for later viewing,
check out or continue shopping after adding the item to the cart, and check out the items by completing
the required information in the order form.
2.

Admin Interface:

The administrator is able to view the users information that was entered during checkout in
the database, can update the information, price, shipping costs of the items, add or remove items from
the main display.
Hardware Interface :

Processor : Pentium
32 MB of free hard Disk Space
128 MB Ram
Software Interface :
This section lists the requirements that are needed to run the system efficiently. The operating
system needed for the system to run effectively, the interface to run the application, the driver for
running Java web applications, the integrated development environment to develop the application, and
the third-party tool used for editing purposes are as follows:

1. Operating System: Windows (Vista/Windows 7) or MAC OS

2. Web Brower: Internet Explorer (8.0 and above), Mozilla Firefox (3.0 and above), or Google Chrome
3. Drivers: Java Runtime Environment
4. Integrated Development Environment: Eclipse Juno or Apache Tomcat
5. Third-Party Tool: Microsoft Word

2.2 Product Function

The online shopping application have the following basic functions:
1. Displaying all the categories available for shopping on the systems main page.

2. Displaying all the items linked to each category listed on the main page.
3. Allowing the administrator to add new items to the existing list of available items.
4. Allowing users/administrator to remove items.
5. Allowing the administrator to modify the price of each item.
6. Allowing the administrator to update the description about each item.
7. Allowing the administrator to view and edit information about each user that checkouts the items
from the system.

User 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.3 Use Case Diagram :

2.4 ER Diagram :

3 Specific Requirements
This section contains details about all the software that is required for designers to create a system
to satisfy the users requirements and for testers to test the given requirements. This section contains the
interface description of each GUI for the different system users. These sections also give descriptions
about all the system inputs, all the functions performed by the system, and all the system output
(responses).

3.1 Functional Requirements :

This application is designed using asp .net as front end and sql as back-end. The user

interaction window is created using Asp. Net and the database storing the details of the items
is created using sql.
The purchase has the simple option of adding new items to the inventory and in case that item
already exists then the record for that item is updated.
The selling option has the option to sell the available items. There are many items available
in the inventory all the details are listed in the window.
Once the items are sold then the data are to be updated in the database. When the number of
items available is less than what is required to the buyer then a message is to be displayed by
the user.
All the details of the items are stored in a database and it is accessed using data connectivity.

3.2 NON-FUNCTIONAL REQUIREMENTS

Non functional requhtments includes
Cost Estimation :
An estimate is a prediction based upon probabilistic assessment. It is the responsibility of the project
manager to make accurate estimations of effort and cost.. is particularly true for projects subject to
competitive bidding where a bid too high compared with competitors would result in loosing the contract or
a bid too low could resuh in a loss to the organization. T. does not mean that intemal projects are
unimportant. From a project leaders estimate the management often decide whether to proceed with the
project. hidustry has a need for accurate estimates of effort and sire at a very early stage in a project.
However, when software cost estimates are done early in the software development process the estimate can
be based on wrong or incomplete requirements. A software cost estimate process is the set of techniques and
procedures that organizations use to arrive at an estimate. An important aspect of software projects is to
know the cost. The major contributing factor is effort.
Cost Pricing
Our project is of high range and is highly efficient which can satisfy the payroll calculation for almost all
software companies. The chances of error occurrence is very limited and so our costs around 10,
00,000(app). A team of members is required for completing the task. It takes a time span of 3 weeks to
shape the project. There are no specific environmental constraints.
Network bandwidth
You can have the best online application, unless you have proper bandwidth, the system will not work well.
Depending on how many people access the system at the same time and on functions the program offers, it
can become a burden to the existing network, slowing down processes to a halt.
Flexibility Flexibility is an important nonfunctional requirement of online shopping. As laws
and regulations change, the system must be updated as well.