Project Report On

Online Sales Order Management System

Submitted By :-
:-
Guided by :-
Patel Chinmay P.(060)
Savan. K.Patel
Gandhi Himil M.(022) BCA –SEM:-VI
MARCH-APRIL 2012

Submitted to :-
ACHARYA MOTIBHAI PATEL INSTITUTE OF COMPUTER STUDIES,
( CONSTITUENT COLLEGE OF GANPAT UNIVERSITY)
GANPAT VIDYA NAGAR,KHERVA-38271
2011-2012
Online Sales Order Management System
For Riwasa Tiles
 PROJECT PROFILE
Project title :- Online Sales Order
Management System
Develop For :- RiwasaTiles Pvt.Ltd
Develop At :- AMPICS
Front-End Visual Basic 2005
Back-End Microsoft Office 2003
Develop By:- Patel Chinmay P.
Gandhi Himil M.
Project Guide :- Patel Ketan P.
Project Coordinator :- Patel Savan K.
 ABOUT COMPANY

NAME OF RIWASA TILES PVT.LTD (ORACLE GRANITO)

COMPANNY
ADDRESS Riwasa tiles pvt.ltd (Oracle granito)
Sabar Dairy-Talod Road,Gadhoda,
Himatnagar-383001.(Gujarat-India)

CONTACT NO Office:- (02772-239931)

DATE OF 6/6/2011
ESTABLISHED
OWNER Patel Harshadbhai. D,
Patel Manilal .P,
Patel Devchandbhai .M
EMPLOYEE 446 Employee in different department
PRODUCT Micro Polish Double Vitrified Tiles
INFORMATION
 EXISTING SYSTEM
 In the existing system the company give information
about product in the newspapers and printed catalog.

 Customer come personaly and select the product and

make payment.

 If product is not available then the customer give order

prior with some advance payment.
 NEED FOR NEW SYSTEM
Future Old New
System System
Get Online Sales Order No Yes

Easy Marketing No Yes

Online Product No Yes

Information
Online Tiles Calculator No Yes

 Generate Report No Yes

 HARDWARE & SOFTWARE
REQUIREMENT
SERVER-SIDE CLIENT-SIDE
 Hardware  Hardware
Pentium IV Processor Celeron or above Processor
1 GB RAM 64 MB RAM

 Software Software
Windows 2003 server
Windows 7
.NET 2.0 Runtime
Crystal Report 10.2.3600 Internet Explorer 5.0 or above
Ms Access 2007
SYSTEM FLOW CHART FOR
ADMIN
ADMIN Start

Username -
Password

No
Login

Yes

Add, Update,
Check Order
Delete View Feedback
Details
Products

Generate
Report

Stop
SYSTEM FLOW CHART FOR
USER
USER Start

View Product
Details

Product
Configuration

Feedback Calculate tiles

Username -
Password
NO
Create
Login
Registration
YES
Give Order

View Status

Stop
DATA FLOW DIAGRAM
 Context level DFD For Online
Sales Order Management
System
0.0
Manage pro. info View pro. info
ONLINE SALES
ADMIN ORDER USER
Order/feedback info MANAGEMET Request/Order of
SYSTEM Product info
FIRST LEVEL DFD
FOR ADMIN
 Request for Login 1.0 Check Id /pass
Admin LOGIN LOGIN_MST
PROCESS Valid /Invalid
Invalid

Login
2.0
Product info Product info
MANAGE
PRODUCT PRODUCT_MST
Update product info Update product info

3.0
USER Registration. info
Registration. info REGISTRATION
DETAIL
_MST

Order info 4.0 Order info

ORDER
Response Feedback DETAIL Response Feedback ORDER_MST

Feedback info 5.0 Feedback info FEEDBACK_MST

FEED-
BACK

6.0
Report info Report
REPORT REPORT
FIRST LEVEL DFD
FOR USER
 1.0
USER Registration info REGI- Registration info REGISTRATION
STRATION _MST

ID/Password 2.0 Id/Password

LOGIN

Product info 3.0 Product info

VIEW PRODUCT_MST
PRODUCT
Response product Response product info
info
Product info

Product Order info 4.0

Order info
ORDER ORDER_MST

Product info

response Feedback info 5.0 Feedback info

FEED- FEEDBACK_MST
BACK
 DATA DICTIONARY

 LOGIN_MST
 USER_MST
 PRODUCT_MST
 ORDER_MST
 FEEDBACK_MST
 USER_FEEDBACK
Table :: Login_MST
Field Data Type Size Description Constrain
User Name Text 12 User Name Primary Key
Password Text 8 Password Not Null
Table :: Registration_MST
Field Data Type Size Description Constrain
User_Id Number 8 User Id Primary Key
Name Text 25 User Name Not Null
Office_Name Text 25 User Office Name Not Null
Address Text 50 User Address Not Null
City Text 15 User City Not Null
Pincode_No Number 6 Pincode No Not Null
Contact_No Number 10 Contact No Not Null
Email_Id Text 25 User Email Id Not Null
Date Date/Time - User Date/Time Not Null
Table :: Product_MST
Field Data Type Size Description Constrain
Product_Id Number 8 Product Id Primary Key
Product_Name Text 25 Product Name Not Null
Series Text 10 Product Series Not Null
Size Text 8 Product Size Not Null
Rate Number 5 Product Rate Not Null
Image Uploaded Text 200 Image Uploaded Not Null
Table :: Order_MST
Field Data Type Size Description Constrain
Order_Id Number 8 Product Id Primary Key
User_Id Number 8 User_Id Not Null
Billing_Address Text 50 Billing Address Not Null
Series Text 20 Series Not Null
Product_Name Text 8 Product Name Not Null
Order_Type Text 12 Order Type Not Null
Quantity Number 6 Product Quantity Not Null
Date Date/Time - Date/Time Not Null
Table :: User_FeedBack
Field Data Type Size Description Constrain
User_FeedBack Number 8 FeedBack Id Primary Key
Name Text 20 Name Not Null
Address Text 40 Address Not Null
FeedBack Text 8 FeedBack Of User Not Null
Date Date/Time - Date/Time Not Null
Table :: FeedBack_MST
Field Data Type Size Description Constrain
FeedBack_Id Number 8 FeedBack Id Primary Key
FeedBack Text 8 FeedBack Of User Not Null
Order_Id Number 10 Order_Id Not Null
Date Date/Time - Date/Time Not Null
ER-DIAGRAM
 M PRODUCT M

ADD VIEW
USER-
ID
USER-
NAME 1
1 M USER-
ADMIN MANAGE USER NAME
PASS-
M
WORD 1 1 1 M 1
EMAIL-
GIVE ID

M
HAVE
FEEDBACK
GIVE

M M 1
ORDER REGIST-
M RATION

MANAGE
Brief Description of
Process
 PROCESS DESCRIPTION

There Are Tow Process Work By System

1.ADMIN
2.USER
 ADMIN PROCESS
 Admin First Login And Has The Right To Handle
The Entire System.
 Admin Can Add, Update And Delete Products.
 Admin Can Check Order Details.
 Admin Can View FeedBack.
 Admin Can Generate Report.
 USER PROCESS
 User View The Product Details.
 User can Get The Products Configuration.
 User Now Give The FeedBack.
 User can Calculate The Tiles.
 User Need To Login.
 If A User Is Not Register Then He Has To First Get
Register.
 If He Is A Already User Provide User Name Password
And Get Login.
 User can now give order.
 User can now see the status of the order given.
PROCESS ALGORITHEM
 ADMIN PROCESS
 Step1: - Admin Login The Application If User
Name And Password Is Correct Then Go to Step 2
Else If Not Then Re enter UserName And Password.
 Step2:-Add, Update and Delete Products,
Check Order Details, View FeedBack.
 Step3:-Create Report Of Order.
 Step4:-Stop
 USER PROCESS
Step1:-User View The Product Details And Get
The Product Configuration.
Step2:- User Can View The FeedBack.
Step3:-User Will Calculate Tiles.
Step4:-To Give Order User need To Login.
Step5:-If A User Is New User Then It Has To Be
Register It Self.
Step6:-Give The UserName And Password To
Login.
Step7:-User Can Give Order.
Step8:-User Can View Order Status .
Step9:-Stop
HOME PAGE
TILES INTERNAL SPACIFATON
ABOUT AS
CONTACT AS
TILES CALCULATE
PRODUCT DETAILS
PRODUCT DETAILS
USER REGISTRATION DETAILS
USER REGISTRATION DETAILS -1
USER REGISTRATION SUCCESSFULLY
USER FEEDBACK
USER LOGIN SUCCESSFULLY
USER HOME PAGE
USER ORDER DETAILS
USER VIEW ORDER STATUS
ADMIN LOGIN
ADMIN LOGIN SUCCESSFULLY
ADMIN HOME
ADD PRODUCT
UPDATE PRODUCT
DELETE PRODUCT
ADMIN VIEW ORDER STATUS
ADMIN VIEW ORDER STATUS-1
ADMIN GIVE ORDER FEEDBACK
ADMIN GIVE ORDER FEEDBACK -1
ADMIN VIEW USER FEEDBACK
ORDER DETAILS REPORT
ORDER DETAILS REPORT -1
ORDER DETAILS REPORT-2
PRODUCT DETAILS REPORT
PRODUCT DETAILS REPORT-1
PRODUCT DETAILS REPORT-2
USER DETAILS REPORT
USER DETAILS REPORT-1
USER DETAILS REPORT-2
 TESTING
We have use following method for testing the system.
Specification Testing:->
- The specification testing is what program does in some various
condition is.
- we check this system to give wrong userneme,password,wrong
data then system display message for input correct data.
Code Testing:->
- The code testing is examining the logic of program.
- we have testing all path of program, path means to specific
combination of condition that handle by program.
- when the any User give order that check correct id,password &
User number etc.
Unit Testing:-
- unit testing is focused on verifying small portion of functionality.
Unit testing is important part where each module and process of
application is to be test by possible input sets and desired output.
- we have check different type of modules like admin module, User
module etc.
 POST IMPLEMENTATION REVIEW

 After the system is implemented and conversation is

complete, a review of system is usually conducted by users,
this is called post implementation.

 the most fundamental concern post implementation review is

determining whether the system has met its objectives; that is
analyst want to know if the performance level of user has
improved and if the system is producing the result intended. If
neither is happening, one may question whether the system can
be considered successful.
 FUTURE ENHANCEMENT
 In future Payment Gateway can be use for the transaction
related to the Order of the Products.

 We will think to make this web application more interactive in

design.

 In future we can try to implement the advertisement also can

be implemented in the web page.
 BIBLIOGRAPHY
>These books acted as our tutor during the system
development

NAME AUTHORE
> ASP. NET UNLEASED Stephan Wither
>Professional ASP.NET WROX Publication
>ASP.NET Black Book Dreamtech Publication

>We had been used the reference of the following websites.

I. http://www.asiangranito.com
II. http://www.w3schools.com