OnlineShopping(Synopsis)
-
Upload
praveen-sehgal -
Category
Documents
-
view
13 -
download
1
description
Transcript of OnlineShopping(Synopsis)
Online Shopping
INDEX & TABLES
1. Project Introduction2. Project Description3. Data flow diagram 4. ER-Diagram5. Data Structure6. Tools/Platform/Language
7. Hardware/Software Requirement
8. Further Development 9. References
1. INTRODUCTION
Starting the project we should fully know about the meaning of project. There are seven letters in the word “PROJECT” each character has its own technical meaning.
Planning:-This deal with the idea at thinking and which are required for the project.
Resource:-The money problem will be solved and resources from which collected.
Operating: - The procedure from which the getting job is prepared in a systematic way is known as operation.
Joint effort :- This is directly proper to a operation output is made of several person working sincerely is known as JOINT EFFORT.
Engineering :- A well-educated engineer can do this work in a better way to find out better result. Hence the project is as engineering function.
Co-operation:- To make the project successfully, it is necessary for its success and completion of project.
Technique: - It must as it gives a better shape. It is not possible to complete the project without technique.
The project is a system that gives the systematic way of planning and working.
OR
It represents a temporary task , in a scientific manner carried out by group of engineers to achieve a goal.
Online Shopping
1.1 Overview
The Online Shopping is the part of the sample application that provides customers with online shopping. Through a Web browser, a customer can browse the catalog, place items to purchase into a virtual shopping cart, create and sign in to a user account, and purchase the shopping cart contents by placing an order with a credit card.
Our Online Shopping (shopping websites) will use some sort of shopping cart - this is your virtual trolley into which you can place items, then take them to the checkout when you want to pay. The checkout must be in a secure server in order for your transaction to be secure.
In our Online Shopping (Shopping website) all electronic records will maintained in password protected archives. Our records are maintained so we can send you details of promotions or services, in which you may be interested. However, each time we send you something you have the opportunity to request that no further information be sent to you. Your personal information will then be deleted from our records.
1.2 Scope of investigation
The aim of this project is to design, build and test a Online Shopping. This will be a vastly complex software development project which will take approximately 5 months to complete. The project will be split up into stages and documented thoroughly throughout.
Project management is a key factor of this task to ensure the strict deadlines are adhered to. It is also of paramount importance that tried and tested practices and techniques from the field are adhered to ensure that no common development project mistakes are reproduced.
1.3 Problem
As there is a vast increase in the demand for creating and using website, each sector is busy developing their own websites to make them more and more approachable. This rise in the use of websites and need for making themselves global has raised the need for allocating or purchasing space and domain for hosting their websites. But the task of getting or purchasing space or domain is quite complex and at time not easy for those who have no idea in this field. This problem encouraged us to think in this direction and come up with the idea of developing a site that would ease out the problems of purchasing space and domain.
2. DESCRIPTION OF PROJECT
Modules:
1. ADMIN
2. CUSTOMER
1. VISITOR
2. MEMBER
3. ORDER TRACK
A report on online shopping rankings by Nielsen/NetRatings indicates that online auction house eBay leads in the number of visitors to its site. Not only that, but eBay also leads, by a huge margin, for the amount of time visitors spent on a shopping site.4.VISITOR:
Online Shopping leads for number of unique visitors. Not only leading in unique visitors, Online Shopping also leads in average amount of time users spent on their site with 41 minutes, 58 seconds. This amount represents a huge lead that Online Shopping has over other shopping sites in web site stickiness. This indicates that Online Shopping has a strong hold over the internet shopping industry.Also included in this report were the rankings for most online advertising impressions, or the amount of times an ad was clicked, among consumer goods.
3. 3. DATA FLOW DIAGRAMDATA FLOW DIAGRAM
DFD
The Data flow Diagram shows the flow of data. It is generally made of symbols given below :
(1) A square shows the Entity : -
(2) A Circle shows the Process: -
(3) An open Ended Rectangle shows the data store : --
(4) An arrow shows the data flow :-
The DFD can be up to several levels. The 0 level DFD states the flow of data in the system as seen from the outward in each module.
The first level DFD show more detail, about the single process of the 0 level DFD
The second level DFD can show even more details and so on.
Zero Level DFDZero Level DFD
Context Level DFD:
Add Products to Carts.
Place Orders & Make Payments.
Make Query
Add & update products, category.
Delivery updates & Query Response
Get Queries.
Check Orders & Check Payments.
(ONLINE SHOPING)
ADMIN
CUSTOMER
Browse Products.
Check Order Status Online.
Get Query Response
First Level DFD:
Browse Products.
Create Account
Update Profile
Get Query Response
Get Payment Reports
Get Orders Reports
Get Delivery Reports
Check Order Status Online.
Get Query Response
Make Query
Add & update products, category.
Delivery updates & Query Response Get Queries.
Check Orders & Check Payments.
Add Products to Carts.
Place Orders & Make Payments.
(ONLINE SHOPING)
ADMIN
CUSTOMER
Order Track
MEMBERVISITOR
Second Level DFD (ADMIN):
Check Orders & Order Details Get Member Details
Update Member Payment Receiving
Get Query & Update Query Response
Place Orders to Delivery & Update Delivery Status
Check Orders & Order Details
Enter Username & Password
Add update, delete Product & Product Category
Process Login
I F LOGIN TRUE THEN ENTER TO ADMIN SECTION
ADMIN SECTION
USERLoginADMIN USER
PRODUCT
CATEGORY
ORDER
(External Entity)
ORDER DETAIL
(External Entity)
DELIVERY
QUERY
MEMBER_PAYMENT
(External Entity)
MEMBER
(External Entity)
Second Level DFD (MEMBER):
Browse Products & Add to Cart and Place Cart to Order (Check Out)
Get or Update Profile
Get Payment Details
Make Query & Get Response Get Delivery
Status Check Orders & Order Details
Enter Username & Password
Process Login
I F LOGIN TRUE THEN ENTER TO MEMBER SECTION
MEMBER SECTION
MEMBERLoginMEMBER USER
PRODUCT
(External Entity)
CATEGORY
(External Entity)
ORDER
(Derived Entity)
ORDER DETAIL
(Derived Entity)
DELIVERY
(External Entity)
QUERY
MEMBER_PAYMENT
Second Level DFD (VISITOR):
Browse Products & Add to Cart and Place Cart to Order (Check Out)
ENTER TO VISITOR SECTION
VISITOR SECTION
VISITOR USER
PRODUCT
(External Entity)
CATEGORY
(External Entity)
Second Level DFD (ORDER TRACK):
Make Query & Get Response Get Delivery Status
Check Orders & Order Details
ENTER ORDER_ID
FOR ENTERING TO THIS MODULE
ORDER TRACK SECTION
CUSTOMER (VISITOR OR MEMBER)
ORDER
(Derived Entity)
ORDER DETAIL
(Derived Entity)
DELIVERY
(External Entity)QUERY
4. E-R Diagram 4. E-R Diagram
Definition:
An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.
Entity Relationship (ER) diagram:
This diagramming technique is used to visually present a database schema or data model and was original proposed by Chen in the 1970s. There are many different data modeling notations; some are very similar to UML class diagrams (with the exception of operations). However, the notation the used here is slightly different, as proposed by Elmasri, et al.The database schema for this system is shown in figure. The table object has been left out of the diagram because the table management feature set had been dropped from the requirements before this stage of the design process.
Some important database design decisions are as follows:_ To store the total price of an order with the order rather than calculating it on the fly when looking at past orders. This is because the price of menu items could change at any time, so the total price at the time of ordering must be stored so that the total price is not incorrectly calculated in future.
_ Similar to the previous point, the order receipt is stored as a hard-copy and not regenerated when reviewing past orders because things such as the restaurant name or VAT percentage are subject to change. Receipts stored need to be exactly the same as the customer copy in case of
5.Data Structures1. Category:1. Category:
Field Name Data Type Constraint Description
Catid Number Primary key This is a unique & not null column entire table
Description Varchar2 Description of the product Category
2. Product:
Field Name Data Type Constraint Description
Pid Number Primary key This is a unique & not null column entire table
Catid Number Foreign key It refers to another table. category(catid)
Name Varchar2 Name or title of the product
Description Varchar2 Description of the product
Type Varchar2 Type of the product
PostingDate Date Posting date of the Product
3. Product Details:
Field Name Data Type Constraint Description
Detail_id Number Primary key This is a unique & not null column entire table
P_id Number Foreign key It refers to another table. category(catid)
Color Varchar2 Color of the product
Weight Varchar2 Weight of the product
Size Varchar2 Size of the product
Image Raw Image of the product
NetPrice Number Net Price of the product
SellPrice Number Sell Price of the product
4. Product Update:
Field Name Data Type Constraint Description
Update_id Number Primary key This is a unique & not null column entire table
P_id Number Foreign key It refers to another table. Product(catid)
Name Varchar2 Name or title of the product
Description Varchar2 Description of the product
Type Varchar2 Type of the product
Update_Type Varchar2 Type of operation( delete or update)
UpdateDate Date Date of the updation
5. Product Update Details:
Field Name Data Type Constraint Description
Up_Detail_id Number Primary key This is a unique & not null column entire table
Update_id Number Foreign key It refers to another table ProductUpdate(upda_id)
Color Varchar2 Color of the product
Weight Varchar2 Weight of the product
Size Varchar2 Size of the product
Image Raw Image of the product
NetPrice Number Net Price of the product
SellPrice Number Sell Price of the product
6. Delivery:
Field Name Data Type Constraint Description
Deli_id Number Primary key This is a unique & not null column entire table
Order_id Number Foreign key It refers to another table. Order (order_id)
Status Varchar2 Show the current status of the order delivery.
Deli_Date Date Date of the Order Delivery.
Deli_remark Varchar2 Any comment related to order delivery
7. User:
Field Name Data Type Constraint Description
UserId Varchar2 Primary key This is a unique & not null column entire table
Password Varchar2 Not null It refers to another table. Order (order_id)
Typeoflogin Varchar2 Type of user login (admin or executive )
Module (Customer);
1. Order:
Field Name Data Type Constraint Description
Order_id Number Primary key This is a unique & not null column entire table
Order_type Varchar2 Type of the Order (Member or Visitor )
Date_Time Varchar2 Order date & time
Billing_Add Varchar2 Billing Address
1. OrderDetail:
Data Type Constraint Description
O_Detail_id Number Primary key This is a unique & not null column entire table
Order_id Number Foreign Key It refers to order table (order id) column.
P_Detail_id Number Foreign Key It refers to product Detail table (p_detail id)
Qty Number Product quantity
Module (Visitor);
1. Visitor Order:
Field Name Data Type Constraint Description
V_Order_id Number Primary key This is a unique & not null column entire table
Order_Id Number Foreign Key It refers to order table (order id) column.
Name Varchar2 Name of the visitor
Address Varchar2 Address of the visitor
Phone Number Check Visitor phone number
Mobile Number Visitor Mobile Number
Email Varchar2 Visitor email address
Payment Varchar2 Payment option
Payment_details Varchar2 Payment details
Module (Member);
1. Member Order:
Field Name Data Type Constraint Description
M_Order_id Number Primary key This is a unique & not null column entire table
Order_Id Number Foreign Key It refers to order table (order id) column.
Mem_id Number Foreign Key It refers to member table (mem_id) column.
2. Member:
Field Name Data Type Constraint Description
Mem _id Number Primary key This is a unique & not null column entire table
Name Varchar2 Name of the member
Address Varchar2 Address of the member
Phone Number Check member phone number
Mobile Number member Mobile Number
Email Varchar2 member email address
Balance Number Member account balance
Password Varchar2 Login password
SequrityQuestion Varchar2 Password recovery secured question
SequrityAns Varchar2 Password recovery secured answer
3 Member Payments:
Field Name Data Type Constraint Description
Payment_id Number Primary key This is a unique & not null column entire table
Mem _id Number Foreign key It refers to another table member(memid)
PayOption Varchar2 Payment option( cash deposit, online, credit cards)
PayDetails Varchar2 Details of the payment
Amount Number Amount of payment
Payment_Date Varchar2 Date & time of the payment
Module (Order Track);
1. Query:
Field Name Data Type Constraint Description
Query_id Number Primary key This is a unique & not null column entire table
Order_Id Number Foreign Key It refers to order table (order id) column.
Query Varchar2 Query Question
QueryDateTime Varchar2 Query generation Date & time
Response Varchar2 Query Response
ResDateTime Varchar2 Response generation Date & time
6. TOOLS/PLATFORMS, LANGUAGES
Front End : Html, JavaScript, CSS, JQuery
User friendly GUI Client Side Validation
Middle-Tier : J2ee with MVC Architecture
Model : JavaBeans
View : Servlet, JSP
Controller : Filter
Back End : Oracle10gXE
Security Performance Scalability Reliability Support RDMS concepts
7. HARDWARE & SOFTWARE REQUIREMENTS
Hardware Specification:
Microprocessor : - Pentium-4 class processor, 450 megahertz (MHz)
RAM : - 256 MB of RAM
Hard Disk : - 40 gigabytes (GB) on installation drive
Software requirements:
Windows 98 / XP /7 or any operating system
Oracle10g Database Server
JDK 5 or above
Weblogic8.1 or above/ Apache Tomcat 5.0 or above
Web builder for form designing
8.Further development
The most notable features which were not implemented in the system are table management and a more intuitive order item notes interface.These features were not implemented because of time constraints. The process of removing features from software when time is running out is known as feature cutting. A drawback of removing features at such a late stage in the project is that some time will probably have already been wasted on the design or partial implementation of these features. The future of this project depends on whether the author has enough spare time over the next few months to continue with the development. The author feels that those last few remaining features would round off the system.
If the author was to try to sell this system then more system testing would have to be done, in particular a more comprehensive real-world testing environment would have to be adopted along with some real-world usage. Multiple concurrent users would be common in real-world usage but have been difficult to test for considering there was only one tester involved in this project. This type of system would benefit from being sold via Software as a Service (SaaS). SaaS would allow support would be provided for the hardware in case of a system failure and for the software in case of newly found bugs, in return for a subscription fee.
9. REFERENCES
References
[1] I. Alexander. Stakeholders: Who is your system for? IEEE: Computing and Control Engineering,14(1):22{26, April 2003.
[2] I. Alexander and T. Zink. Introduction to systems engineering with use cases. IEEE: Computing and Control Engineering, 13(6):289{297, December 2002.
[3] Almyta Systems. Point of Sale Systems. http://systems.almyta.com/Point_of_Sale_Software.asp. Accessed on 20th October 2008.
[4] S. W. Ambler. Process Patterns: Building Large Scale Systems Using Object Technology. Cam-bridge University Press, 1998.
[5] M. Andrews and J. A. Whittaker. How to Break Web Software: Functional and Security Testing
[6] Java-2 Complete Reference - by Patrick Haughton[7] Java Servlet Programming - by O'Reilly[8] Pure JavaScript - by Jason Gilliam, R.Allen Wyke [9] HTML complete - BPB publications.[10] Java Server Programming - by Apress publication.