“Software of order. 2.1.12 Allow Online Product reviews

 

“Software Requirements Specification (SRS) for E-Commerce (myntra)

 

Submitted as an Assignment
purpose

by

 

Shaikh Shadab Ishrat

                                                                        to

 

           

 

Contents

Table of Contents

1. Introduction

                1.1 SRS

                1.2 Scope

                1.3 Definitions, Acronyms
and Abbreviations

 

2.
Overall Description

            2.1 Specific
Requirements

                        2.1.1    Product
details

2.1.2    Search Facilities

2.1.3    Maintain customer profile.

2.1.4    Provide personalized profile

2.1.5   
Provide Customer Support.

2.1.6    Email confirmation.

2.1.7    Detailed invoice for customer

2.1.8    Provide shopping cart facility

2.1.9    Online tracking of shipments

2.1.10  Allow multiple payment methods.

2.1.11  Allow online change or cancellation of order.

2.1.12  Allow Online Product reviews and ratings

2.1.13  Offer online promotions and rewards.

2.1.14  Online Purchase of products.

 

3.
Requirement analysis

                        3.1       platform requirement

                                    3.1.1    Supportive
operating system

                        3.2       Software Requirements

                        3.3       Hardware Requirements

                        3.4       Feasibility Study

                                    3.4.1    Technical Feasibility

                                    3.4.2    Economic Feasibility

                                    3.4.3    Legal Feasibility

 

 

 

 

 

 

 

 

1. Introduction

 

1.1 SRS:–

 

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 Software.

This Software Requirements Specification aims
to describe the Functionality, External

Interfaces, Attributes and Design Constraints
imposed on Implementation of the software Software described throughout the
rest of the document.

Defining
and describing the functions and specifications of Software  is the primary goal of this Software
Requirements Specification (SRS). This Software Requirements Specification
illustrates, in clear terms, the Software’s primary uses and required
functionality as specified by our customer

 

 

1.2 Scope

The
software Software being produced is called E-Commerce Software. It is being
produced for a customer interested in selling goods via Internet.

This
Software is cross-platform and is available to anyone using the Computer &
smartphones.

This
E-Commerce Software 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 Software will allow customers to
browse, search, select, and add goods to a shopping cart. Check out goods in shopping
cart and decrement the stock that the inventory the Software maintains.

It
will also allow, on an inventory wide basis, customers and sellers to interact
with a promotion Software that handles percentage-off promotions that can be
applied to member’s orders.

 

1.3 Definitions, Acronyms, and
Abbreviations

 

FAQ

Frequently Asked Questions

Shopping cart

An object that lists a Customer’s selected Items, their applied
promotions and gives them an option to check out

SRS

Software Requirements Specification

Item

An individual entity in the inventory which has several descriptive
attributes:
Barcode, Price, Reorder Threshold, Stock

Pin number

The unique id given to
either customer or merchant who
access the data in the site

Data mining

The process of collecting, searching through, and analyzing a large
amount of data in a database, as to discover patterns or relationships.

Tracking

A line of travel or motion, a course or route followed.
 

 

 

2.
Overall Description

Introduction

The term “Electronic commerce” (or e-Commerce) refers
to the use of an electronic medium to carry out commercial transactions. Most
of the time, it refers to the sale of products via Internet, but the term
ecommerce also covers purchasing mechanisms via Internet

Mainly all the current ecommerce websites are showing the
similar amount of things The main purpose of all the e commerce is to maximize
the the business of the organization. This proposed Software will also perform
almost the similar amount of things but with some of the additional data, we
have maked this Software hassel free , we can do payment in many types of way,
the uniqueness in this project is that people will able to buy this product in
various other way, like anybody can do the payment if the customer isnot having
sufficient balance

 

 

 

2.1
Specific Requirements

·        
The Software must display all the products that can
be configured.

·        
The Software must allow user to select the product
to add cart

·        
The Software must display all the availAble
components of the product to configure

·        
The Software must enable user to add one or more component
to the configuration..

·        
The Software must allow user to update the
configuration to resolve conflict in the current configuration.

·        
The Software must allow user to confirm the
completion of current configuration

 

2.1.1 Product
details.

·       
The Software must display detailed
information of the selected products.

·        
The Software must provide browsing options to see
product details.

 

·        
The Software must
display detailed product categorization to the user.

 

2.1.2 Search facility.

 

·        
The Software must
enable user to enter the search text on the screen.

 

·        
The Software must
enable user to select multiple options on the screen to search.

 

·        
The Software must
display all the matching products based on the search

 

·        
The Software must
display only 100 matching result on the current screen.

 

·        
The Software must
enable user to navigate between the search results.

 

·        
The Software must
notify the user when no matching product is found on the search.

 

 

2.1.3  Maintain customer profile.

 

·        
The Software must
allow user to create profile and set his credential.

 

·        
The Software must
authenticate user credentials to view the profile.

 

·        
The Software must
allow user to update the profile information.

 

2.1.4        Provide personalized profile

 

·        
The Software must
display both the active and completed order history in the customer profile.

 

·        
The Software must
allow user to select the order from the order history.

 

·        
The Software must
display the detailed information about the selected order.

 

·        
The Software must
display the most frequently searched items by the user in the profile.

 

·        
The Software must
allow user to register for newsletters and surveys in the profile.

 

2.1.5  Provide Customer Support.

 

·        
The Software must
provide online help, FAQ’s customer support, and sitemap options for customer
support.

 

·        
The Software must
allow user to enter the customer and product information for the support.

 

·        
The Software must
display the customer support contact numbers on the screen.

 

·        
The Software must
allow user to enter the contact number for support personnel to call.

 

·        
The Software must
display the online help upon request.

 

·        
The Software must
display the FAQ’s upon request.

 

2.1.6  Email confirmation.

 

·        
The Software must
maintain customer email information as a required part of customer profile.

 

·        
The Software must
send an order confirmation to the user through email.

 

2.1.7          Detailed
invoice for customer.

 

·        
The Software must
display detailed invoice for current order once it is confirmed.

 

·        
The Software must
optionally allow user to print the invoice.

 

2.1.8          Provide
shopping cart facility.

 

·        
The Software must
provide shopping cart during online purchase.

 

·        
The Software must
allow user to add/remove products in the shopping cart.

 

2.1.9          Online
tracking of shipments

 

The Software must allow user to enter
the order information for tracking.

 

The Software must display the current
tracking information about the order.

 

2.1.10     Allow multiple payment methods.

 

·        
The Software must
display available payment methods for payment.

 

·        
The Software must
allow user to select the payment method for order.

 

2.1.11     Allow online change or cancellation of order.

 

·        
The Software must
display the orders that are eligible to change.

 

·        
The Software must
allow user to select the order to be changed.

 

·        
The Software must
allow user to cancel the order

 

·        
The Software must
allow user to change shipping, payment method.

 

·        
The Software must
notify the user about any changes made to the order.

 

 

2.1.12     Allow Online Product reviews and ratings

 

·        
The Software must
display the reviews and ratings of each product, when it is selected.

 

·        
The Software must
enable the user to enter their reviews and ratings.

 

 

 

2.1.13         Offer online promotions and rewards.

 

·        
The Software must
display all the available promotions to the user.

 

·        
The Software must
allow user to select available promotion.

 

 

2.1.14     Online Purchase of products

 

The Software must allow user to
confirm the purchase.

 

The Software must enable user to enter
the payment information.

 

 

Chapter 3.

Requirement Analysis

3.1   
Platform Requirement:

 

Our
proposed Software comprises of a web
application for E-commerce,

& a mobile application for customer / users.

 

Each of their requirements are as stated
below.

 

 

•  
Web Application for E-commerce

•  
Mobile Application for end users

•  
Back end Management Software

 

 

3.1.1   Supportive Operating
Software :

 

MOBILE OPERATING SOFTWARE

 

Mobile OS is the platform on top of which other programs, called application
programs, can run on mobile
devices such as mobile
phones, Smart phone, and hand held computers. The most common
operating Software’s (OS) used in smart phones
are:

 

Android from Google Inc. (open source,
Apache)

Android was developed by a small startup company
that was purchased by Google Inc., and Google continues to update the software.

 

Android is an open source, Linux-derived OS backed by Google, along with major hardware and software developers (such as Intel, HTC, ARM, Samsung, Motorola and eBay, to name a few), that form the Open Handset Alliance. Released on November 5th 2007, the OS has a following
among programmers.

 

 

There have been many releases of Android .All are nicknamed
after a dessert item like Cupcake (1.5) or Frozen
Yogurt (2.2). Most major
mobile service providers carry an Android
device.

 

 

3.2      
Software Requirement :

The Software Requirements in this project
include:

·      
Operating Software: Windows
XP, Windows 7 or Windows8

 

·        
IDE: Eclipse with STS Plugin,
android studio

 

·        
Application Server: Apache Tomcat 7.0.67

 

·        
Front End: HTML5, JavaScript, j Query, AJAX and CSS,

 

·        
Database: MySQL

 

·        
Browser: Chrome or Firefox
or Internet Explorer

 

 

3.3      
Hardware Requirement:

 

•  
Processor: Intel Core i3 or Higher / android minimum
lollipop

 

•  
RAM: minimum 2GB/4GB
for computer

 

•  
RAM: minimum 512MB
for android

 

 

3.4       Feasibility Study

 

A feasibility study aims to objectively and rationally uncover the strengths and weaknesses of an existing
business or proposed venture, opportunities and threats present in the environment
& the resources

 

3.4.1     
Technical feasibility

 

The project member was very much familiar
with the basic website building, so with the help of that, we have
converted it into the android
members of the project also have ideas about the android , which help us to build a proper application

the mainly
used skills was HTML,CSS
JavaScript there were required
experts were present for possible solution for our problems

 

 

3.4.2      Economic Feasibility

 

This project
requires a computer
Software to develop the software
and a server Software
to host the application. Rest everything is software
requirement. by economic
also it is feasible like parking demand in future,
and also financial
analysis is also feasible

 

 

3.4.3      Legal Feasibility

 

This
project is developed with a premium template which is legally
purchased from the developers
and are authorized to use it for personal purpose.
Also the major idea behind the project is our own idea and does not conflict with other existing Software’s idea. Hence legally project
is feasible to be developed

 

 

Chapter 3

 

Software Design

 

 

3.1    System basic Flow
Architecture

Given below figure describe the figure of the
flow of  the entire architecture

Whenever the end user will enter the website with
the help of computer or android application, the entire website must be
displayed to the user within 15 sec , it’s our responsibility to make the
website responsive , & it should be user friendly simultaneously

Since as per the survey done, maximum number f
the people mostly prefer mobile phone over the laptop, so it may allow the user
to login, register or search the product as a guest, after that user will
search for the respected product & proceed to checkout after doing payment
it will give notification to the seller to dispatch the order from warehouse. Warehouse
is the place where entire items is to be kept, successfully confirmation by the
warehouse will let the item go for quality & services for packaging process,
After the completion of the entire packaging, product isready to get dispatched
to the customer

 

 

                                                                             Figure
3.1 Architecture of the project

 

 

3.2    Use case Diagram

 

The purpose
of use case diagram is to capture the dynamic aspect of a Software.
Use case diagrams
are used to gather
the requirements of a Software
including internal and external
influences. These requirements are mostly
design requirements. So when Software
is analyzed to gather its functionalities use cases are prepared and actors are identified.

 

 

 

 

Use case diagrams are used to gather the requirements of Software including
internal and external influences. These requirements are mostly design requirements. So when Software is analyzed to gather its functionalities use cases are prepared and actors are identified.

 

 

 

3.2      
Activity Diagram

 

Activity diagram is another important diagram
in UML to describe
dynamic aspects of the Software. Activity diagram is basically
a flow chart to represent
the flow form one activity to another activity.
The activity can be described as an operation of the Software. So the control
flow is drawn from one operation
to another. This flow can be sequential, branched or concurrent. Activity diagrams
deals with all type of flow control by using different elements
like fork, join etc.

 

Activity is a particular operation
of the Software. Activity
diagrams are not only used for visualizing dynamic nature of a Software
but they are also used to construct
the executable Software by using forward
and reverse engineering technique