Online Shopping

Online Shopping System Version < 1.0>

Software Requirements Specification Kgce1

< kgce1 >

Online Shopping System

Software Requirements Specification Version < 1.0>

Team Guide: Mr S.M.Patil

Members:

1) Pallavi Jain 2) Mukeshkumar Choudhary 3) Prasad Borole

College Name: Konkan Gyanpeeth College of Engineering, karjat

Department: Computer Engineering

State: Maharashtra

kgce1/ Konkan Gyanpeeth College of Engineering Page 1

Online Shopping System Version <1.0>

Software Requirements Specification <date> Kgce1

Revision History

Date Version Description Author <date> 1.0 Synopsis Kgce1




Table of Contents

Description Page No.

1.0 Introduction

1.1 Purpose

1.2 Scope

1.3 Definition, Acronyms, and Abbreviations

1.4 References

1.5 Technologies to be used

1.6 Overview

2.0 Overall Description

2.1 Product Perspective

2.2 Software Interface

2.3 Hardware Interface

2.4 Product Function

2.5 User Characteristics

2.6 Constraints

2.7 Architecture Design 2.8 Use Case Model Description




2.9 Class Diagram

Sequence Diagrams

2.10 Database Design

2.11.1 ER Diagram

2.11.2 Schema

2.12 Assumptions and Dependencies

3.0 Specific Requirements

3.1 Use Case Reports

3.2 Supplementary Requirements


Online Shopping System Version 1.0



Software Requirements Specification 1.0 Introduction:

The project is a simple online shopping portal. The system will allow more than one categories to be selected and different brands under the segment. The system will allow the customer to make the payment in local language. The system would be easy to use and hence make the shopping experience pleasant for the users. The system will provide drag and drop features which will allow the users to add a product to shopping cart or remove a product from a shopping cart. The system will allow the customer to view complete specification of the product along with the images.

1.1 Purpose

o To develop an easy to use web based interface where users can search for products, view a complete description of the products and order the products.

o Making the application AJAX enabled gets rid of these unnecessary delays letting the user to perform exhaustive search. The users of this application can easily feel the difference between the Ajax empowered user interfaces vs. traditional user interfaces.

o Provide Interactive interface through which a user can interact with different areas of application easily.

o Provide Drag and Drop feature thereby allowing the user to add products to or remove products from the shopping cart by dragging the products in to or out of the shopping cart.

o A user can view the complete specification of the product along with various images and also view the customer reviews of the product.

kgce1/ Konkan Gyanpeeth College of Engineering Page 5Online Shopping System Version 1.0



1.2 SCOPE:

The Scope of online shopping portal includes:

o The users could subscribe for price alerts which would enable them to receive messages when price for products fall below a particular level.o The current system is confined only to the shopping cart process. It can be extended to have a easy to use check out process.

1.3 Definitions, Acronyms and Abbreviations:

o Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create dynamic web pages.

o HTML (Hyper Text Markup Language): It is used to create static web pages.

o J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications.

o JSP (Java Server Pages): It is used to create dynamic web content

o DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong "on demand" business applications.

o HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server.

o XML (Extensible Markup Language): It is a markup language that was designed to transport and store data.

o Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability, user-centered design and collaboration on the World Wide Web.


Online Shopping System Version 1.0 Online Shopping System Version <1.0>


1.4 References:

o AJAX-COMPLETE REFERENCE.

o J2EE COMPLETE REFERENCE.

1.5 Technologies to be used:

o J2EE : (Servlet, JSP, JAXP, Java Beans) Application architecture.

o DB2 : IBM Database.

o Ajax : Asynchronous Java Script and XML.

o XML : Extension Markup Language.

Web 2.0: RSS Feed 2.0.

1.6 Overview:

The SRS will include two sections, namely:

-I- Overall Description:

Project describes what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed.





-I- Specific Requirements: This system contains the following types of actors:

1. Customer:

o Simplicity.

o Payment possibilities in local language.

o End to end functions.

o Simple interface for terms and condition.

o Printout of the bill.

2. Administrator:

o Track usage of services in language.

o Ensure Simplicity and correctness correspondence of services

purchased.o Find approaches to simplify transactions.

o Ensure original information is perfectly localized to remove any

duplication.

2.0 Overall Description:

2.1 Product Perspective:

Online shopping project 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 and the customer. Online shopping should be user-friendly, ‘quick to learn’ and reliable software for the above purpose. This is intended to be a stand-alone product and should not depend on the availability of other software.





2.2 Software Interface:

Front End Client: Web Browser, AJAX

Web Server: IBM Web Server

Database Server: IBM Database Server

Back End Client: DB2

2.3 Hardware Interface:

Client Side:

Browser Type Processor Disk Space RAMIE, NN, Mozila andFirefox

Pentium II at 500MHz.

1 GB 512 MB

Server Side:

Browser Type Processor Disk Space RAMIE, NN, Mozila andFirefox

Pentium II at 500MHz.

1 GB 512 MB

2.4 Product Functions:

This System includes major functions like:- 1. Creating an account. 2. Login to the system. 3. Search for a Product 4. Selecting Products. 5. Adding in the Cart.




6. Confirming the Cart Items. 7. Payment of the Shopping done. 8. Bill Generation. 9. Suggestion for a product.

NOTE: A user can only do the above operations (expect no. 1&2) after creating an account.

2.5 User Characteristics:

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

The user should be familiar with the Internet.

2.6 Constraints:

Real-life credit card validation and Banking system is not implemented.

No multilingual support

Pre Conditions: An account must be created before searching, selecting and adding the products to the cart

Post Condition: After creation of a user account the user can perform the operations such as searching, selecting and adding the products to the cart and bill payment.

2.7 Architecture Design:




2.8 Use Case Diagram:

(a) Use Case Diagram for the Admin:




(b) Use Case Diagram for the Customer:




2.9 Class Diagram:

2.10 Sequence Diagram:

(a) Sequence Diagram for registering a New User




(b) Sequence Diagram for Logging a User:







(c) Sequence Diagram for Adding a Product to the Cart:




2.10.1 Database Design:

2.11 Assumptions and Dependencies:

Assumptions: 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.

User should know the purpose of website. Registration Steps will be known by the user. User should know how to ask the queries.

Dependencies: User should get registered one to get the full utilization of the website. The registered user only will be getting the updates.

3.0 Specific Requirements:

3.1 Use Case Reports:

The use case diagram of Online Shopping System is very easy to understand. It shows us the direct relationships between the actors Admin and customer.

1. Use Case of Admin:

Admin performs the following functions:

Adding a Segment

Add a Brand

Add a Product

Bill Generation

Product Delivery





2. Use Case of Customer:

Customer performs the following functions:

Registers

Login

Searches the Products

Selects the Brand

Selects the Product

Adds Item to the Cart

Payment

3.2 Supplementary Requirements:

These requirements are yet not there


Online Shopping

Documents

o o o o j2ee

purposeo o o o o

online shopping system

o j2ee java

simple online shopping

shopping cart process

o ajaxcomplete reference

o j2ee complete reference