Online Bus Booking System

Transcription

1 A Project Presentation On Online Bus Booking System Submitted By Barot Alok T Dayani Yash K M.Sc. (CA & IT) Semester-III Internal Guided By Amit B. Suthar Submitted to Department of Computer Science, Ganpat University, Ganpat Vidyanagar Group no:-07 1

2 INDEX Sr. No Title 1 Project Profile 2 Existing System 3 Need for New System 4 Function Specification 5 Hardware &Software Requirements 7 System Flowchart 8 Timeline Chart 9 E-R- Diagram 10 Use case Diagram 11 Activity Diagram 12 Class Diagram 13 Sequence Diagram 14 Collaboration Diagram 15 Data Dictionary

3 Sr. No Title 16 Input design 17 Out put design 18 Testing 19 Post implementation review 20 Future enhancement 21 Bibliography

4 Project-Profile Project title:- Online Bus Booking System Objectives:- Front End Tool:- Customer can easy book their Tickets And Cancel Choice and provide Information about Bus. Asp.net with c# Framework3.5 Back End Tool:- Sql Server 2005 Type Of Application:- Internal Guide : Time Duration:- Web Application Mr. Amit B. Suthar 90 days Group no:- 07

5 The work is done manually. Existing System Those who are interested in inquiring about the Bus Type, its Tickets Price, available seats, facility of the bus etc. has to walk to the Booking office. This creates a huge Relief for the Customer of the Office on weekends to save their time.

6 Need For New System A new system is helpful to both employees as well as the customers. New system provides help to the customer as they can inquire about the Bus model, its Ticket price, available Seats, facility of the bus etc. and they don t need to walk to the office. There is login and password service for employee and Regular customers to use this system.

7 User FUNCTIONAL SPECIFICATION This Project basically provides a Bus information and regarding bus information. First of all, in our website any user or visitor are view our system and also search the bus and how many seats are available in our buses. user can also registered its own seats in bus this website. User can post a comment on different Bus Services. But user can compulsory registered first in the system. Search Bus category wise.

8 Admin In this system admin can maintain all the Bus information and also maintain Bus category, comments etc. In this system admin can maintain the registered users, manage news,and also admin can generates a reports and manage the whole system.

9 MODULE SPECIFICATION Login: Login Module includes various utilities like User Authentication, Change Password and Forgot Password. Registration: In this website provide a some facility user can Registered in this website. user can use this facility so user can make a registration. Book the Ticket: In this module admin can add new bus category using this module. Bus Category contains like Volvo, Slipper coach, Ac Coach etc.

10 Update Bus Information: In this module admin can add or Update Bus using this module. It contains the information about the Bus type, photo, description, Location of tour, Available Seats in Bus etc. Cancel the Booking Ticket: In this Module User can Cancel the booking Ticket. Comments: In this Module User can Post the Comment on a particular Bus. Report Generation: This module is used to generate a reports. 10

11 Hardware Requirement(Minimum) Minimum Server Requirement : Processor RAM Disk Space 1 GHZ 2 GB 10 GB Of Free Space Minimum Client Requirement : Processor RAM Disk Space 2 GHZ 1 GB 20 GB Of Free Space

12 Software Requirement(Minimum) Server Software Requirement : Operating System Windows server 2003 Web Server Front End Back End IIS 6.0 ASP.NET with c# SQL Server 2005 Client Software Requirement : Operating System Web browser Windows Xp or Any equivalent OS Internet Explorer 6.0 or Any compatible Browser

13 System Flow Chart

14 System Flow Chart START View Website VISITOR If Register? no Registration Yes Login no Valid UserId & Password Yes Is Admin? no ADMIN Yes User A B C

15 A B C Update Bus Information View Bus information View Booking details Book the Ticket Receive Payment Information Manage comment Cancel the Booking Ticket Post comment Generate Reports Log out STOP

16 Timeline Chart A C TI VI T Y 12 Preliminary Investigation 15 Req. Gathering & System Analysis 18 System Designing 25 Coding 11 Testing 9 Implement & Deployment Days

17 ER Diagram 1 View 1 Admin 1 1 Book_id M View Manage Booking_Master F_id Reg_id City M Mobileno M M Feedback M Manage Bus_id Bus_Master M price Select Bus Can 1 M User 1 View Can Reg_id 1 Username

18 Use-case Diagram for Admin

19 Use-case Diagram for User

20

21 Activity Diagram for User

22 Class Diagram

23 Sequence Diagram for Admin

24 Sequence Diagram for User

25 Collaboration Diagram for Admin

26 Collaboration Diagram for User

27 TABLE NAME :- Reg_MASTER Data Dictionary Primary Key : Reg_id Foreign Key : - Description: The information about Registration of costumer No Field Name Data type Constraint Description 1 Reg_id Int Primary Key It store Registration id. 2 First_Name Nvarchar(30) Not Null It store Customer First Name. 3 Last_Name Nvarchar(30) Not Null It store Customer Last name. 4 _id Nvarchar(20) Not Null It store the _id. 5 Address Nvarchar(20) Not Null It store customer Address. 6 City Nvarchar(20) Not Null It store customer city. 7 Pincode Nvarchar(6) Not Null It store customer Pincode. 8 ContactNo Numeric(10) Not Null It store customer Contactno

28 TABLE NAME :- LOG_MASTER Primary Key : U_id Foreign Key : --- Description: The information about Login. No Field Name Data type Constraint Description 1 u_id Int Primary Key It is store User ID 2 Username Nvarchar(30 ) Not Null It store Username. 3 Password Nvarchar(20) Not Null It store Password. 4 Type Nvarchar(10) Not Null It store Type of admin or user.

29 TABLE NAME :- Booking_MASTER Primary Key : Book_id Foreign Key : Reg_id, Bus_Id Description: The information about Booking Ticket detail No Field Name Data type Constraint Description 1 Book_id Int Primary Key It store Booking id 2 Reg_id Int Foreign Key Give references to Reg_master 3 Bus_id Int Foreign Key Give references to Bus_master 3 Fname Nvarchar(20) Not null It store First Name. 4 Lname Nvarchar(20) Not null It store Last Name 5 Nvarchar(20) Not Null It store id. 6 Contactno Numeric(10) Not Null It store Mobile no. 7 Address Nvarchar(20) Not Null It store customer Address. 8 City Nvarchar(20) Not Null It store City. 9 SeatNO Nvarchar(20) Not Null It store Bus seat no. 10 Date Nvarchar(20) Not Null It store Travelling date.

30 TABLE NAME :- Bus_MASTER Primary Key : Bus_id Foreign Key : - Description: The information about Bus Ticket price. No Field Name Data type Constraint Description 1 Bus_id Int Primary key It store Bus id. 2 BusNumber Nvarchar(20 ) Not null It store Bus Number. 3 BusType Nvarchar(20) Not Null It store Bus Type. 4 TotalSeat int Not Null It store Total Seat of Bus.

31 TABLE NAME :- Feedback Primary Key : -F_id Foreign Key : Reg_id Description: The information about Feedback. No Field Name Data type Constraint Description 1 F_id Int Primary Key It is store Feedback ID 2 Username Nvarchar(30) Not Null It is store Username 3 Feedback Nvarchar(30 ) Not Null It store Feedback. 4 Date Nvarchar(20) Not Null It store Date of given Feedback

32 Input output design

33 Home page Description:- This is the Home page of user,admin and Visitor.

34 Visitor search page Description:- in this page visitor serch the bus details

35 Login page Description:- This is the login page for user and Admin

36 Login page Description:- when user enter wrong password then the error occur.

37 Registration page Description:- This is the the Registration page.

38 Reset Password page Description:- User & Admin Forget Password Then Reset Password.

39 Admin side

40 Login page Description:- This is the login page for Admin side and user side

41 Admin home page Description:- This is the home page for Admin

42 Bus schedule Description:- This is the Admin can Add bus schedule.

43 Add Bus Description:- This is the Admin can Add Bus.

44 Pickup stand Description:- This is the Admin can Add the pickup stand.

45 News update Description:- This is the page news update by Admin.

46 Change password Description:- Admin can change the password.

47 View user details Description:- Admin can manage User details.

48 View feedback Description:- Admin can manage feedback

49 View report Description:- Admin can view report

50 User side

51 Home page for user Description:- This is the Home page of user.

52 Change password page Description:- Use can change the password.

53 Search bus page Description:- user can search the bus and see time schedule.

54 Reservation page Description:- user can select the seat and pickup stand.

55 Reservation confirm page Description:- Reservation confirm page.

56 PayPal page Description:- user conform ticket when user pay a payment via PayPal.

57 Ticket print Description:- User can print the ticket

58 Feed back page Description:- user can give feedback

59 Out put Design

60 Update password Description :- Admin can update password

61 View report Description :- Admin can view Bookreport

62 View report Description - Admin can view registration report

63 Unit Testing:- TESTING This is the testing process which we can do manually because in this testing program is a tested individually using dummy record to see whether that program produce satisfied output as the company and validation also. Validation Testing:- In this requirements established as part of software requirements analysisare validated against the software that has been constructed. Validation testing provides finalnassurance that software meets all functional, behavioural and performance requirements. Validation can be define in many ways but a simple definition is that validation succeeds when software Function in a manner that can be reasonably by the customer. 1. Validation test criteria 2. Configuration review 3. Alpha and Beta testing(conducted by end user)

64 System Testing:- System testing is actually a series different test whose primary purpose is to full exercise the computer base system.where the software and other system elements are tested as whole.to test computer software,we spiral out along streamlines that broadens the scope of testing with each turn. The last higher-order testing step falls outside the boundry of software Engineering and in to the broader context of computer system engineering.software,once validated,must be combining with order system Elements(e.g.hardware,people,databases).System testing verifies that all the elements Mesh properly and that overall system function/performance is achieved. 1.Recovery Testing 2.Security Testing 3.Stress Testing

65 TEST CASES: Admin Cases: Case ID Test case Expected Output Actual Output Pass/Fail Remarks 01 Login Test Login with proper details and role. Successfully Pass Good 02 Managing details Manage information properly stored successfully Pass Good 03 Add &update Bus information Add &update Bus info properly successfully pass Good 04 Exception Handling Proper error message should display. Not Successfully Fail Poor 05 View tickets booking information View booking info properly Successfully pass Good 06 View Payment information View payment request properly successfully pass Good

66 Register Customer Test Cases: Case ID Test case Expected Output Actual Output Pass/Fail Remarks 01 Login Test Login with proper details Successfully Pass Good 02 Register Information Proper Register with exception handling Successfully Pass Good 03 View bus Information Proper Bus Information Successfully Pass Good 04 search information Search information Properly Successfully Pass Good 05 Book Ticket Information Book bus tickets Properly Successfully Pass Good

67 Post Implementation Review After the system is implemented and conversion is completed a review of system is usually conducted by user and analyst. This is called post implementation review. The most fundamental concern post implementation review to determining whether the system has met its objective; that is analysts want to know if the performance the performance level of improved and if the system is producing the result intended.if neither is happening,one may question whether the system can be considered successful The new system needs less manpower, provide facility for Book Tickets and Latest News for bus information.

68 Future Enhancement We think that not a single project is ever considered as complete forever.because our mind is always thinking something new and our necessities also are growing day by day.we always want something more than what we have.our application also, If you see at the first glance then you find it to be complete but we want to make it still mature and fully automatically. The future perspective of our project can linking our booking system with other centralized bus services so that user has an ease of booking and travelling. Other then this for long route journeys food facility and its variety can be added. With the use of GPS every traveler can get advance map of route to be followed during journey. Making a mobile app for the user is also a first step development.

69 Bibliography During the development of our system, we have taken the reference from Books and journals, which we would like to mention in this section. These books acted as our tutors during the system development.. ASP.NET UNLEASHED ASP.NET WITH C# Stephen Walther Shyam N. Chawda Besides these we were referring the online manuals from the sites