You are on page 1of 11

SOFTWARE REQUIREMENT SYSTEM

1. INTRODUCTION
1.1 PURPOSE;

The Online Shopping Mall (OSM) web application is intended to provide complete
solutions for vendors as well as customers through a single get way using the internet as
the sole medium. It will enable vendors to setup online shops, customer to browse through
the shop and purchase them online without having to visit the shop physically. The
administration module will enable a system administrator to approve and reject requests for
new shops and maintain various lists of shop category
This document is meant to delineate the features of OSM, so as to serve as a guide to the
developers on one hand and a software validation document for the prospective client on the other.
Some highlighted purposes of shopping mall management system are:

a) Communication between the customer


,analysist,system developer, maintainer
b) Contract between the purchaser & supplier
c) Firm foundation for the design phase
d) Support system testing activities
e) Support project, management & control
f) Controlling the evolution of the system

1.2 SCOPE;

Initial functional requirements will be: -

1.Secure registration and profile management facilities for Customers

Browsing through the e-Mall to see the items that are there in each category of products
like Apparel, Kitchen accessories, Bath accessories, Food items etc.

Adequate searching mechanisms for easy and quick access to particular products and
services.

Creating a Shopping cart so that customers can shop n no. of items and checkout finally
with the entire shopping carts.

Regular updates to registered customers of the OSM about new arrivals.

Uploading Most Purchased Items in each category of products in the Shop like Apparel,
Kitchen accessories, Bath accessories, Food items etc.

Strategic data and graphs for Administrators and Shop owners about the items that are
popular in each category and age group.

Maintaining database of regular customers of different needs.

Shop employees are responsible for internal affairs like processing orders, assure home
delivery, getting customer's delivery-time feedback, updating order's status and answering
client's queries online.

Feedback mechanism, so that customers can give feedback for the product or service which
they have purchased. Also facility rating of individual products by relevant customers.
Also feedback can be given on the performance of particular vendors and the entire mall as
well.

Adequate payment mechanism and gateway for all popular credit cards, cheques and other
relevant
payment
options,
as
available
from
time
to
time.

Initial non functional requirements will be: -

Secure access of confidential data (users details). SSL can be used.

24 X 7 availability

Better component design to get better performance at peak time

Advertisement space where it will effectively catch the customers attention and as a
source of revenue.

In addition to the above mentioned points, due to the highly evolving nature of the
project, the following are planned to be delivered if deemed necessary:

Warehousing within the very ambits of the project

More payment gateways.

Dynamic price model by which prices can be changed based on demand and supply

Dynamic Storefront: Each customer will have a web page personalized based on his or her
recent purchases. This is the equivalent of having a unique storefront for each customer in
hopes of drawing in as many return customers as possible.

This list is by no means, a final one. The final list will be dictated by implementation
constraints, market forces and most importantly, by end user demands for whom this is
being built.

1.3 DEFINITIONS,ACRONYMS &


ABBREVIATIONS:

1.SLA: Service Level Agreement or SLA is a formal written agreement made between two
parties, the service provider & the service recipient. It defines the term of engagement - the
fundamental rules that will govern the relationship.

EJB: Enterprise Java Beans.

JAVA EE: Java Enterprise Edition 5 is a programming platform part of the Java
Platform-for developing and running distributed multi-tier architecture Java applications,
based largely on modular software components running on an application server.

HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between


a web browser & a Web Server.

HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication


protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two
main ones being TCP and IP.

OSM: Online Shopping Management.

1.4 REFERENCES:

The references are:

E-Store Structural Model


E-Store Behavioral Model
E-Store NFR Model
Vision Draft 5

1.5 overview
The rest of this SRS is organized as follows: Section 2 gives an overall description of the
software. It gives what level of proficiency is expected of the user, some general
constraints while making the software and some assumptions and dependencies that are
assumed. Section 3 gives specific requirements which the software is expected to deliver.
Functional requirements are given by various use cases. Some performance requirements
and design constraints are also given.

2. OVERALL DESCRIPTION
The customer/user may use any of the web browsers and enter the web address,
from which they want to shop. Looking through the list of items provided along
with the rate, the customer can select any of it. Next the customer is requested to
enter the quantity of items he wishes to buy. Depending on this, the total amount
is displayed and also provides discount if any and finally the net amount is
displayed.Next is the payment procedure. The customer can pay cash on
delivery or through his credit card.The system also asksfor the address to where
the goods have to be delivered. As soon as he provides his credit card number,

its details are checked. If the details are correct, then the sales procedure is
authorized.
The Online Shopping System normally doesnt have items in their
warehouse. They order it from a distributor and the items are dispatched to the
customer. A bill will be sent to the customer by the credit card company and
vendors account will be credited.Admin provides a unique username and
password for each employee through which he can login.Admin alsohas the
authority to add details of the items to be sold.

2.1 PRODUCT PERSPECTIVE


OSM is aimed towards the vendors who want to reach out to the maximum cross-section
of customer and common people who can be potential customer. This project envisages
bridging the gap between the seller, the retailer and the customer. OSM should be userfriendly, quick to learn and reliable software for the above purpose. OSM is intended to
be a stand-alone product and should not depend on the availability of other software. It
should run on both UNIX and Windows based platform.

a)
b)

SYSTEM INTERFACES
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.

c)

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.

Processor: Intel dual core or above

Processor Speed:1.0GHZ or above

RAM: 1 GB RAM or above

Hard Disk: 20 GB hard disk or above


Protocol : shall be HTTP.

Port number: will be 80.

logical address of the system in IPv4 format.

d)

SOFTWARE INTERFACES
Language: PHP,HTML,JAVASCRIPT,CSS
Database:MySQL

1. The Shopping mall system shall communicate with the Configurator to identify all
the available components to configure the product.
2. The Shopping mall shall communicate with the content manager to get the product
specifications, offerings and promotions.
3. The Shopping mall system shall communicate with billPay system to identify
available payment methods , validate the payments and process payment.
4. The Shopping mall system shall communicate to credit management system for
handling financing options.
5. The Shopping mall system shall communicate with CRM system to provide support.
6. The Shopping mall system shall communicate with Sales system for order
management.
7. The Shopping mall system shall communicate with shipping system for tracking
orders and updating of shipping methods.
8. The Shopping mall system shall communicate with external Tax system to calculate
tax.
9. The Shopping mall system shall communicate with export regulation system to
validate export regulations.
10. The Shopping mall 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.

e)

COMMUNICATIONS
INTERFACES

The Shopping Mall Management System shall use the HTTP protocol for communication
over the internet and for the intranet communication will be through TCP/IP protocol
suite.

f)
g)
h)

MEMORY
OPERATIONS
SITE ADAPTATION
REQUIREMENT

2.2 PRODUCT FUNCTIONS

Maintenance of details of various items, vendors and stores online.


Online generation of purchase order
Easy comparison of actual receipt of order with the Purchase order.
Status of all purchase order is available

User: Mall Administrator


Functions: The Mall Administrator is the super user and has complete control over all the
activities that can be performed. The application notifies the administrator of all shop
creation requests, and the administrator can then approve or reject them. The administrator
also manages the list of available product categories. The administrator can also view and
delete entries in the guestbook.

User: Shop Owner


Functions: Any user can submit a shop creation request through the application. When the
request is approved by the Mall Administrator, the requester is notified, and from there on
is given the role of Shop Owner. The Shop Owner is responsible for setting up the shop
and maintaining it. The job involves managing the sub-categories of the items in the shop.
Also, the shop owner can add or remove items from his shop. The Shop Owner can view
different reports that give details of the sales and orders specific to his shop. The Shop
Owner can also decide to close shop and remove it from the mall.

User: Mall Customer/Guests


Functions: A Mall Customer can browse through the shops and choose products to place in
a virtual shopping cart. The shopping cart details can be viewed and items can be removed
from the cart. To proceed with the purchase, the customer is prompted to login. Also, the
customer can modify personal profile information (such as phone number and shipping
address) stored by the application. The customer can also view the status of any previous
orders, and cancel any order that has not been shipped yet.

User: Employees
Functions: Purchase department under a Purchase manager to overlook purchasing
activities if warehousing needs arise.
Functions: Sales department under a Sales manager who will look after the sale of products
and services, the most important activity.
Functions: Accounts department under an Accounts manager to look after the accounting
activities of the enterprise

2.3 USER CHARACTERISTICS

The user should be familiar with the Shopping Mall related terminology like Shopping
cart/Checking out/Transaction etc.

The user should be familiar with the Internet.

Owner
President
Buyer
Store Manager
Office Manager
All The above users have similar rights. They have total access the BPMS system.

They have the rights to generate new users in the system .They will have the total access to all the
information in the system being a people from the management team of the organization.

District Manager
District manager may have more than 1 store under him. He logs in he sees only stores under him
i.e. a list of his stores and toggle between them. He should have managerial type access only for
those stores that are under him.
Assistant Store Manager
The Store Manager and Assistant Store Manager have limited access in the BPMS. They will be able
to see the details restricted to their Store only.
Following are their rights

Creation of PO
Cost of items bought will not be disclosed
The comparison with other vendor items will not shown
Sales Deposit
Enter the details of Sales for his store registers
Data Maintenance
The Usage of the system will be restricted only to add cash registers and Changing
his password
Limited Internet Access
The Stores will have limited Internet access that is the usage of BPMS system online
rest of the Internet will not be accessible.

2.4 CONSTRAINTS
a)
Regulatory policies
b)
Hardware limitations
c)
Interfaces to other
applications
d)
Parallel operations
e)
Audit Functions
f)
Control Functions
g)
Higher-order language
requirement
h)
Signal handshake
protocols
i)
Reliability requirement

j)
k)

Criticality of the
application
Safety and security
considerations

2.5 ASSUMPTIONS & DEPENDENCIES

The details related to the product, customer, payment and service transaction provided
manually.

Administrator is created in the system already.

Roles and tasks are predefined.

2.6 APPORTIONING OF REQUIREMENT


3

SPECIFIC REQUIREMENT
3.2 EXTERNAL INTERFACES
3.3 FUNCTIONS
These requirements are organized by the features discussed in the vision document.
Features from vision documents are then refined into use case diagrams and to
sequence diagram to best capture the functional requirements of the system. All these
functional requirements can be traced using tractability matrix.

3.4 PERFORMANCE REQUIREMENT


3.5 LOGICAL DATABASE REQUIREMENT
3.6 DESIGN CONSTRAINTS

3.6.1 STANDARD COMPLIANCE


3.7 SOFTWARE SYSTEM ATTRIBUTES
3.7.1 RELIABILITY
3.7.2 AVAILABILITY
3.7.3 SECURITY
3.7.4 MAINTAINABILITY
3.7.5 PORTABILITY
3.8 ORGANIZING THE SPECIFIC
REQUIREMENT
3.8.1 SYESTEM MODE
3.8.2 USER CLASS
3.8.3 OBJECTS
3.8.4 FEATURE
3.8.5 STIMULUS
3.8.6 RESPONSE
3.8.7 FUNCTIONAL HIERARCHY
3.9 ADDITIONAL COMMENTS
4 SUPPORTING INFORMATION
4.2 TABLE OF CONTENTS & INDEX
4.3 APPENDIXES