Project Report On Online Sales Order Management System

Transcription

1 Project Report On Online Sales Order Management System Submitted By :- Patel Chinmay P.(060) Gandhi Himil M.(022) BCA SEM:-VI MARCH-APRIL 2012 Guided by :- Savan. K.Patel Submitted to :- ACHARYA MOTIBHAI PATEL INSTITUTE OF COMPUTER STUDIES, ( CONSTITUENT COLLEGE OF GANPAT UNIVERSITY) GANPAT VIDYA NAGAR,KHERVA

2 Online Sales Order Management System For Riwasa Tiles

3 PROJECT PROFILE Project title :- Develop For :- Develop At :- Online Sales Order Management System RiwasaTiles Pvt.Ltd 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.

4 ABOUT COMPANY NAME OF COMPANNY ADDRESS RIWASA TILES PVT.LTD (ORACLE GRANITO) Riwasa tiles pvt.ltd (Oracle granito) Sabar Dairy-Talod Road,Gadhoda, Himatnagar (Gujarat-India) CONTACT NO DATE OF ESTABLISHED Office:- ( ) 6/6/2011 OWNER Patel Harshadbhai. D, EMPLOYEE PRODUCT INFORMATION Patel Manilal.P, Patel Devchandbhai.M 446 Employee in different department Micro Polish Double Vitrified Tiles

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

6 NEED FOR NEW SYSTEM Future Old System New System Get Online Sales Order No Yes Easy Marketing No Yes Online Product Information No Yes Online Tiles Calculator No Yes Generate Report No Yes

7 HARDWARE & SOFTWARE REQUIREMENT Hardware SERVER-SIDE Pentium IV Processor 1 GB RAM CLIENT-SIDE Hardware Celeron or above Processor 64 MB RAM Software Windows 2003 server.net 2.0 Runtime Crystal Report Ms Access 2007 Software Windows 7 Internet Explorer 5.0 or above

8 SYSTEM FLOW CHART FOR ADMIN

9 ADMIN Start Username - Password Login No Yes Add, Update, Delete Products Check Order Details View Feedback Generate Report Stop

10 SYSTEM FLOW CHART FOR USER

11 USER Start View Product Details Product Configuration Feedback Calculate tiles Username - Password Login YES Give Order NO Create Registration View Status Stop

12 DATA FLOW DIAGRAM

13 Context level DFD For Online Sales Order Management System ADMIN Manage pro. info Order/feedback info 0.0 ONLINE SALES ORDER MANAGEMET SYSTEM View pro. info Request/Order of Product info USER

14 FIRST LEVEL DFD FOR ADMIN

15 Admin Request for Login Invalid 1.0 LOGIN PROCESS Check Id /pass Valid /Invalid LOGIN_MST Product info Update product info Login 2.0 Product info MANAGE PRODUCT Update product info PRODUCT_MST Registration. info 3.0 USER DETAIL Registration. info REGISTRATION _MST Order info Response Feedback 4.0 ORDER DETAIL Order info Response Feedback ORDER_MST Feedback info 5.0 FEED- BACK Feedback info FEEDBACK_MST Report info 6.0 REPORT Report REPORT

16 FIRST LEVEL DFD FOR USER

17 USER Registration info 1.0 REGI- STRATION Registration info REGISTRATION _MST ID/Password 2.0 Id/Password LOGIN Product info Response product info 3.0 VIEW PRODUCT Product info Response product info Product info PRODUCT_MST Product Order info 4.0 ORDER Order info ORDER_MST Product info response Feedback info 5.0 FEED- BACK Feedback info FEEDBACK_MST

18 DATA DICTIONARY LOGIN_MST USER_MST PRODUCT_MST ORDER_MST FEEDBACK_MST USER_FEEDBACK

19 Table :: Login_MST Field Data Type Size Description Constrain User Name Text 12 User Name Primary Key Password Text 8 Password Not Null

20 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 _Id Text 25 User Id Not Null Date Date/Time - User Date/Time Not Null

21 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

22 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

23 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

24 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

25 ER-DIAGRAM

26 M PRODUCT M ADD VIEW USER- NAME PASS- WORD 1 ADMIN M MANAGE M GIVE M USER M 1 USER- ID USER- NAME - ID FEEDBACK GIVE HAVE M ORDER M M 1 REGIST- RATION MANAGE

27 Brief Description of Process

28 PROCESS DESCRIPTION There Are Tow Process Work By System 1.ADMIN 2.USER

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

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

31 PROCESS ALGORITHEM

32 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 ADMIN PROCESS

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

34 Step7:-User Can Give Order. Step8:-User Can View Order Status. Step9:-Stop

35

36 HOME PAGE

37 TILES INTERNAL SPACIFATON

38 ABOUT AS

39 CONTACT AS

40 TILES CALCULATE

41 PRODUCT DETAILS

42 PRODUCT DETAILS

43 USER REGISTRATION DETAILS

44 USER REGISTRATION DETAILS -1

45 USER REGISTRATION SUCCESSFULLY

46 USER FEEDBACK

47 USER LOGIN SUCCESSFULLY

48 USER HOME PAGE

49 USER ORDER DETAILS

50 USER VIEW ORDER STATUS

51 ADMIN LOGIN

52 ADMIN LOGIN SUCCESSFULLY

53 ADMIN HOME

54 ADD PRODUCT

55 UPDATE PRODUCT

56 DELETE PRODUCT

57 ADMIN VIEW ORDER STATUS

58 ADMIN VIEW ORDER STATUS-1

59 ADMIN GIVE ORDER FEEDBACK

60 ADMIN GIVE ORDER FEEDBACK -1

61 ADMIN VIEW USER FEEDBACK

62

63 ORDER DETAILS REPORT

64 ORDER DETAILS REPORT -1

65 ORDER DETAILS REPORT-2

66 PRODUCT DETAILS REPORT

67 PRODUCT DETAILS REPORT-1

68 PRODUCT DETAILS REPORT-2

69 USER DETAILS REPORT

70 USER DETAILS REPORT-1

71 USER DETAILS REPORT-2

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

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

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

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

76 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. II.

77