Download - Srs Online shopping cart

7/28/2019 Srs Online shopping cart

1/28

Online Shopping Portal 2013

1

Shri Vaishnav Institute of Technology and Science, Indore

Department of Information Technology2013-2014

Online Shopping Portal

Lab Submission Report For Software Engineering and Project Management

Lab

Guided By: Submitted by:

Akash Ralotiya(0802IT101006)Mr.Jigyasu Dubey Divyendu Yadav (0802IT101019)Mr.Chetan Verma Hitesh Aleriya(0802IT101024)

Rakesh Tejra(0802IT101049)


2/28


2


CERTIFICATE This is to Certify that Mr. Divyendy Yadav (0802IT101019), Hitesh

Aleriya(0802IT101024), Rakesh Tejra(0802IT101049) and AkashRalotiya(0802IT101006) working in group have satisfactorily completed the

project titled Online Shopping Portal towards the partial fulfillment of thedegree of Bachelor of Engineering (Information technology). Awarded byRajiv Gandhi Technical University, Bhopal for the academic year 2013.

Project Guide Head of DepartmentMr Jigyasu DubeyMr. Chetan Verma Dr. Ashish Bansal

Internal External


3/28


3


ACKNOWLEDGEMENT

We follow your foot-steps, we move on the path shown by you, weacknowledge you, and we are proud to have guides like you.

We feel it our proud privilege to express our deep sense of gratitude andIndebtedness to Dr. Ashish Bansal (Head of Department), Mr. Jigyasu

Dubey and Mr. Chetan Verma (Project Guide) for providing their painstaking and untiring supervision. We own our deep sense of gratitude andthanks for their constructive criticism, valuable suggestions and constantencouragement at all stages of development of this project.

We wish to express our sincere thanks to all the faculty of Computer Science Department, for providing a conductive environment for proper development of project and the necessary facilities for completion of project.

We also express our sincere thanks and gratitude to Dr. Ing. V.P. Singh(Principal) for their support and guidance and constant encouragement for completion of project.

Akash Ralotiya(0802IT101006)Divyendu Yadav (0802IT101019)

Hitesh Aleriya(0802IT101024)Rakesh Tejra(0802IT101049)


4/28


4

Table of Contents

1. Introduction1.1 Problem Statement.. 5 1.2 Purpos e .... 51.3 Scope ....... 6 1.4 Definitions, Acronyms and Abbreviations 61.5 Tools Used 71.6 References 8 1.7 Technologies to be used 8

1.8 Overview 92. Overall Description2.1 Use-Case Model Survey 10 2.2 Assumptions and Dependencies . 14

3. Specific Requirements3.1 Use-Case Reports ... 143.2 Activity Diagram 223.2 Seque nce Diagram. 26 3.4 Class Diagram . . 273.5 Supplementary Requirements .. .. 28


5/28


6/28


6

1.3 ScopeThe system accepts the General selling and purchasing of items , gives the

proper information about the place where items are may be found . The

different areas where we can use this application are :

This can be used at everywhere because it is very easy to use and operate as

it is very user friendly.

This software reduces the human effort and time saving.

Anyone can make use of it for providing information about items and their

prices.

Modifications can be easily done according to requirements.

1.4 Definitions, Acronyms and Abbreviations:

OSP (Online Shopping Portal) : It is a web application that provides onlineshopping facility for consumers.

AdminAdministrator: He/she has the authority to add/delete users, grant permissionto employees and maintain the content of application.

JSPJava Server PagesIt is used to create dynamic web content.

J2EEJava 2 Enterprise Edition


7/28


7

A programming platform which is a part of java platform for developing andrunning distributed java.

UML

Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct anddocument

HTTPHypertext Transfer Protocol Its a service protocol.

1.5 Tools UsedApplication architecture JAVA, J2EE

JAVAJava is an object-oriented programming language developed by SunMicrosystems a company best known for its high end UNIX workstations.

Java language was designed to be small, simple, and portable across platforms, operating systems, both at the source and at the binary level, whichmeans that Java programs (applet and application) can run on any machinethat has the Java virtual machine (JVM) installed.

Development tool RAD

IBM Rational Application Developer for Web Sphere Software (RAD) is anintegrated development environment (IDE), made by IBM's Rational Softwaredivision, for visually designing, constructing, testing, and deploying Webservices, portals, and Java (J2EE) applications.

Database platform MY SQL


8/28


8

MYSQL Database is the database management system that delivers a flexibleand cost effective database platform to build robust on demand business

applications and supports the J2EE and web services standards.

E-DRAW

Edraw Max is a 2D business technical diagramming software with richexamples and symbols, which make it easy to create flowcharts,organizational charts, ER diagram, Activity diagram, Use case diagram andother software engineering diagrams.

1.6 References Object Oriented Modeling and Design with UML-Michael Blaha, James

Rambaugh. Software Engineering, Seventh Edition, Ian Sommerville. IBM Red Books.

IBM www.ibm.in/developerworks. Java - www.sun.com Wikipedia - www.wikipedia.com Database Management Systems - Navathe. Complete Reference - J2EE - Keogh.

1.7 Technologies to be used

EDRAW- for UML Diagrams Rational Software Modeler.


9/28


9

SQL: Relational Database Management System. ADOBE DREAMWEAVER: Designing Software.

1.8 Overview

Existing System: Registration for users. Registration for Courier Managers

Online Cart

Drawbacks: There is no maintenance of back up so availability will get affected. Limited to HTTP/HTTPS. Real-life credit card validation and Banking system is not implemented. No multilingual support.

10/28


10

2. Overall Description

2.1 Use Case Model Survey

Main Use case:

Web Customer

Administrator

Identity Provider

PayPal

View Item

MakePurchase

CheckOut

ClientRegister

< 

>

< >


11/28

12/28


12

2.2.2 Use Case for User (Registered)

Customer

Log In

BrowseCatalog

Add/Removeitems from

Shopping Cart

CheckOutPayment

GiveFeedback

View AccountDetails

View currentorder status

< >

< >

< >

< >

Figure 2: Use Case Diagram for User


13/28


13

2.1.3 Use Case for Admin

Administrator

LogIn

Managecustomerdatabase

ManageEmployeebatabase

Add/Remove/Update categories

or items

Figure 3: Use case diagram for Administrator


14/28


15/28


16/28


16

MAIN FLOW:

STEP ACTOR DESCRIPTION CONDITION LOCATION

1. WebCustomer

Searches for theitem byentering theitem name

2. WebCustomer

Can view onlyitems.

If not aregisteredcustomer

S-1

3. WebCustomer

Will enter theusername and

password andsystem willverify

If entries dontmatch

S-2

4. WebCustomer

View item andmake a

purchase

If a registeredcustomer

S-3

5. Administrator Keep the itemslist updated

6. Administrator Checks clientregistration

If a new user want to signup

S-4

7. Administrator ProvidesCustomer Authentication

If the webcustomer goesfor purchase

8. Administrator MaintainsCheckout

If customer finally wantsto purchasethe item

S-5

9. Identity

Provider

Maintains

unique item list10. IdentityProvider

Check outCustomer authentication

11. PayPal Provide aninterface for

payment


17/28


17

Precondition:Administrator should be registered as authorized user .

PostconditionAdministrator should log out after the transaction.

Sub Flows:

(S-1)

STEP ACTOR DESCRIPTION CONDITION LOCATION1. Web Customer If want to

purchase anitem anERROR message isgenerated

2. Web Customer System requestthe user toregister him/her

(S-2)

STEP ACTOR DESCRIPTION CONDITION LOCATION1. Web Customer If username or

password dontmatch anERROR message isgenerated

2. Web Customer If it matcheshe/she is

provided withadditionalfunctionalities


18/28


19/28


19

(S-4)

STEP ACTOR DESCRIPTION CONDITION LOCATION1. Administrator System ask the

user to enter theUsername and

password2. Administrator User enters the

Username and password

Incorrectusername/password

ALT-1

3. Administrator System ask theuser to create anew account

4. Administrator User enters therequired details

Entries alreadyin use

ALT-2

(ALT-1)


1. Administrator If the

Username/passwordentered by the User isIncorrect/Incompleteor not in thedatabase an error message isgenerated

2. Administrator System request theuser to Re-Enter theUsername/password


20/28


20

(ALT-2)


1. Administrator If some of thedetails alreadyused by someoneor already in thedatabase an error message isgenerated

2. Administrator System request the

user to Re-Enter the details

(S-5)

STEP ACTOR DESCRIPTION CONDITION LOCATION1. Administrator System ask the

user to enter theItems in cart

2. Administrator User enters theItem no. of the

purchasing item

Incorrect Itemno.

ALT-1

3. Administrator System ask theuser to enter thequantity of itemto be purchased

4. Administrator User enters the

quantity details

Exceed max.

limit

ALT-2


21/28


21

(ALT-1)


1. Administrator If the Item no.entered by the User isIncorrect/Incompleteor not in thedatabase an error message isgenerated

2. Administrator System request theuser to Re-Enter theItem no.

(ALT-2)


1. Administrator If the quantity

exceeds themaximum limit anerror message isgenerated

2. Administrator System request theuser to Re-Enter the quantity


22/28


22

3.2 Activity Diagram

3.2.1 User Login Activity


23/28


23

3.2 .2 User Registration Activity


24/28


24

3.2.3 Place Order Activity


25/28


25

3.2.4 Make Payment Activity


26/28


26

3.3 Sequence Diagram


27/28


27

3.4 Class Diagram :

Admin

-Id:Integer#name:CharViewProducts()AddProductse()DeleteProducts()ModifyProducts()ConfrmDelivery()

Customer

-Id:Integer#name:Char#Address:Char#PhNo:IntegerBuyProducts()ViewProducts()MakePayment()AddToCart()DeleteFromCart()

Payment

#CustomerId::CharName:CharCardType:CharCardNo:Char

Products

-Id:Integer#name:Char#Group:Char#SubGroup

Cart

-Id:Integer#NoOfProducts:

Integer#Product1:Char#Product2:Char#Price:Float#Total:Float

M a n a g e

Buy

M a k e s

Has

+1..*

+1

+1..*

+ 0 . . *

+1

+1

+1

+1

+ 0 . . *


28/28


3.5 Supplementary Requirement:

Th is Supplementary Specification applies to the Online Shopping PortalSystem, which will be developed by our group. This specification defines the non-functional requirements of the system;

such as reliability, usability, performance, and supportability, as well asfunctional requirements that are common across a number of use cases. (Thefunctional requirements are defined in the Use Case Specifications.)Functionality:

User should have an account for online transaction. System authorities are not responsible for any transaction failure. The main objective of this software is to reduce the work load of general

users and professionals. More efficient and time saving.