Online Movie Ticket Booking System 1
Transcription
Online Movie Ticket Booking System 1
A PROJECT PRESENTATION ON ONLINE MOVIE TICKET BOOKING SYSTEM Submitted To : Department Of Computer Science Developed By : Chirag Modi - 13084231061 Paresh Patel - 13084231165 M.Sc.(CA & IT) - III Sem. Group No. - 03 Internal Guide By : Mrs.Krupa Bhavsar PROJECT PROFILE Project Title Online Movie Ticket Booking System Objective Booking Tickets for movies in various Theaters by the Users. Platform Web base Application Front End ASP.NET with C# (.NET Framework 3.5) Back End Microsoft SQL Server 2005 Other Tools Microsoft Office 2007, Adobe Photoshop 6.0 Developed By Modi Chirag A. Patel Paresh N. Time Duration 90 Days Submitted To Department Of Computer Science 13084231061 13084231165 EXISTING SYSTEM Manual Time consuming Dependent on employee Insecurity NEED FOR NEW SYSTEM Computerized Time saving Independent of employee Security FUNCTION SPECIFICATION ADMIN : In this module The Administrator is maintain the user Details, Movie details, Theater details and Check the number of seats available. BOOKING TICKETS : In this module The Users will search for the movie and then go for theater then booking the tickets online. MEMBER : In this modules The user can first Registration in enter the Personal details and User login and If you also want to update personal details. The user collect all information like upcoming Movies details, in advance ticket booking and Theater details. BOOKING : If you are book ticket by tell so you collect ticket before start show 30 minute otherwise cancel your booking HARDWARE & SOFTWARE REQUIREMENT Minimum Server Side Requirements : Software Operating System : Window7 or compatible Web Server : IE 6.0 + Hardware Processor : 1.5 MHz or above Ram : 1 GB Hard disk : 5 GB of free space on hard disk Minimum Client Side Requirements : Software Operating System : Window XP or compatible Web Server : IE 6.0 + Hardware Processor : 1.5MHz Ram : 512 MB Hard disk : 2 GB (only if downloading is needed) A flow chart is a pictorial representation of any dataflow. It uses different types of Symbols. BASIC SYMBOL OF FLOWCHART : Terminal Input/Output Processing Flow lines Decision Connectors SYSTEM FLOW CHART TIME LINE CHART Task Time Duration (In Days) 15 30 45 60 Total Days 75 90 Requirement Gathering & Analysis 15 Designing 15 Coding 35 Testing 15 Deployment & Implementation 10 Documentation 90 E-R Diagram Username ADMIN Password 1 Screen_No View info Gold Platinum Silver M USER M Ticket_no Seat_no A/c_no M Seat Movie_name User Film BOOOKING M Book films M M MOVIE INFO 1 ADMIN Screen_No UML Diagram Use Case Diagram Activity Diagram Class Diagram SEQUENCE DIAGRAM Admin SEQUENCE DIAGRAM Member COLLABORATION DIAGRAM Admin COLLABORATION DIAGRAM Member D ATA D I C T I O N A RY Table Name :- login_info Description :- To store login information. Primary Key :Foreign Key :Index Column Name Data Type Size Constraints Description 1 UserName Varchar (50) Not Null Used to store Username 2 Password Varchar (50) Not Null Used to store Password Table Name :- Movie Description: - To store movie information. Primary Key: - MovieId Foreign Key: Index Column Name Data Type Size Constraints Description 1 MovieId Int --- Primary key Used to store Movie Id. 2 MovieName Varchar (50) Not Null Used to store Movie Name. 3 ImagePath Varchar (100) Not Null Used to store Image Path. 4 Director Varchar (100) Not Null Used to store Director. 5 Producer Varchar (50) Not Null Used to store Producer 6 Cast Varchar (200) Not Null Used to store Cast 7 Duration Int --- Not Null Used to store Duration 8 Story Varchar (8000) Allow Null Used to store Story 9 Type Varchar (50) Not Null Used to store Type (running or upcoming) Table Name :- CustomerPoints Description :- To store customer points Primary Key :Foreign Key :- CustomerId Index Column Name Data Type Size Constraints Description 1 CustomerId Int --- Foreign Key Used to store (Forign Key of Customer's column CustomerId) 2 UserName Varchar (50) Not Null Used to store Username 3 CPoints Bigint --- Not Null Used to store Customer Points Table Name :- temp Description :- To store the temp data of seats Index Column Name Data Type Size Constraints Description 1 Name Varchar (50) Not Null Used to store name. 2 c1 Int --- Not Null Used to store c1. 3 i1 Varchar (50) Not Null Used to store i1. 4 c2 Int --- Not Null Used to store c2. 5 i2 Varchar (50) Not Null Used to store i2. 6 c3 Int --- Not Null Used to store c3. 7 i3 Varchar (50) Not Null Used to store i3. 8 c4 Int --- Not Null Used to store c4. 9 i4 Varchar (50) Not Null Used to store i4. 10 c5 Int --- Not Null Used to store c5. 11 i5 Varchar (50) Not Null Used to store i5. 12 c6 Int --- Not Null Used to store c6. 13 i6 Varchar (50) Not Null Used to store i6. 14 c7 Int --- Not Null Used to store c7. 15 i7 Varchar (50) Not Null Used to store i7. 16 c8 Int --- Not Null Used to store c8. 17 i8 Varchar (50) Not Null Used to store i8. 18 c9 Int --- Not Null Used to store c9. 19 i9 Varchar (50) Not Null Used to store i9. 20 c10 Int --- Not Null Used to store c10. (Continue…) 21 i10 Varchar (50) Not Null Used to store i10. 22 c11 Int --- Not Null Used to store c11. 23 i11 Varchar (50) Not Null Used to store i11. 24 c12 Int --- Not Null Used to store c12. 25 i12 Varchar (50) Not Null Used to store i12. 26 c13 Int --- Not Null Used to store c13. 27 i13 Varchar (50) Not Null Used to store i13. 28 c14 Int --- Not Null Used to store c14. 29 i14 Varchar (50) Not Null Used to store i14. 30 c15 Int --- Not Null Used to store c15. 31 i15 Varchar (50) Not Null Used to store i15. 32 c16 Int --- Not Null Used to store c16. 33 i16 Varchar (50) Not Null Used to store i16. 34 c17 Int --- Not Null Used to store c17. 35 i17 Varchar (50) Not Null Used to store i17. 36 c18 Int --- Not Null Used to store c18. 37 i18 Varchar (50) Not Null Used to store i18. 38 c19 Int --- Not Null Used to store c19. 39 i19 Varchar (50) Not Null Used to store i19. 40 c20 Int --- Not Null Used to store c20. 41 i20 Varchar (50) Not Null Used to store i20. Table Name :- Book Description :- To store booking information Primary Key :- StatusId Foreign Key :- SeatId , ShowId Index Column Name Data Type Size Constraints Description 1 StatusId Int --- Primary key Used to store StatusId 2 SeatId Int --- Foreign Key Used to store (Forign key of Seats's column SeatId) 3 SeatName Int --- Allow Null Used to store Seat Name 4 ShowId Int --- Foreign Key Used to store (Forign key of Show's column ShowId) 5 Status Bit --- Not Null Used to store the status Table Name :- City Description :- To store city information Primary Key :- CityId Foreign Key :- Index Column Name Data Type Size Constraints Description 1 CityId Int --- Primary key Used to store city id 2 CityName Varchar (50) Not Null Used to store city name 3 State Varchar (50) Not Null Used to store state Table Name :- Customer Description :- To store customer information Primary Key:- CstomerId Foreign Key:Index Column Name Data Type Size Constraints Description 1 CustomerId Int --- Primary key Used to store customer id 2 UserName Varchar (50) Not Null Used to store Username 3 Pass Varchar (50) Not Null Used to store Password 4 Fname Varchar (50) Not Null Used to store First Name 5 Mname Varchar (50) Allow Null Used to store Last Name 6 Lname Varchar (50) Not Null Used to store Last Name 7 Gender Varchar (50) Not Null Used to store Gender (Male or Female) 8 Address Varchar (500) Not Null Used to store Address 9 City Varchar (50) Not Null Used to store City 10 Pincode Int --- Not Null Used to store Pincode of city 11 State Varchar (50) Not Null Used to store State 12 Email Varchar (50) Not Null Used to store Email of customer 13 Mobile Bigint --- Not Null Used to store Mobile number of customer Table Name :- Screen Description :- To store screen information Primary Key : - ScreenId Foreign Key :-TheatreId Index Column Name Data Type Size Constraints Description 1 ScreenId Int --- Primary key Used to store Screen Id 2 ScreenNo Int --- Not Null Used to store Screen number 3 TheatreId Int --- Not Null Used to store (Forign key of Theatre's column TheatreId) Table Name :- Seats Description :- To store Seat information Primary Key :- SeatId Foreign Key :- Index Column Name Data Type Size Constraints Description 1 SeatId Int --- Primary key Used to store Seat Id 2 ScreenId Int --- Not Null Used to store Screen Id 3 RowName Varchar (10) Allow Null Used to store row number 4 SeatName Int --- Not Null Used to store Seat name 5 ImageUrl Varchar (50) Not Null Used to store Image path Table Name :- Show Description :- To store show timing of the movie Primary Key :- ShowId Foreign Key :- MovieId , TheatreId Index Column Name Data Type Size Constraints Description 1 ShowId Int --- Primary key Used to store Show Id 2 MovieId Int --- Foreign Key Used to store (Forign key of Movie's column MovieId) 3 TheatreId Int --- Foreign Key Used to store (Forign key of Theatre's column TheatreId) 4 ScreenId Int --- Foreign Key Used to store (Forign Key of Screen’s column ScreenID) 5 StartTime Varchar (50) Not Null Used to store Start time of movie 6 EndTime Varchar (50) Not Null Used to store End time of movie 7 Date Varchar (50) Not Null Used to store Date of movie 8 PRate Int --- Allow Null Used to store Platinum seat rate 9 GRate Int --- Allow Null Used to store Gold seat rate 10 SRate Int --- Allow Null Used to store Silver seat rate Table Name :- Theatre Description :- To store Theater information Primary Key :- TheatreId Foreign Key :- CityId Index Column Name Data Type Size Constraints Description 1 TheatreId Int --- Primary key Used to store Theatre Id 2 TheatreName Varchar (50) Not Null Used to store Theatre name 3 CityId Int --- Not Null Used to store (Forign key of City's column CityId) 4 Address Varchar (500) Not Null Used to store address of theatre 5 Pincode Int --- Not Null Used to store pincode 6 Nos Int --- Not Null Used to store no of screen Table Name :- Prints Description :- To store prints details of the movie ticket to customer Primary Key :Foreign Key :- Index Column Name Data Type Size Constraints Description 1 PrintId Int --- Not Null Used to store print id 2 TicketId Int --- Not Null Used to store ticket id 3 Movie Varchar (50) Not Null Used to store movie name 4 Theatre Varchar (50) Not Null Used to store theatre name 5 City Varchar (50) Not Null Used to store city 6 Screen Int --- Not Null Used to store screen number 7 StartTime Varchar (50) Not Null Used to store start time of movie 8 EndTime Varchar (50) Not Null Used to store end time of movie 9 Date Varchar (50) Not Null Used to store date of movie 10 Seats Varchar (50) Not Null Used to store number of seats 11 SeatType Varchar (50) Not Null Used to store seat type 12 Amount Int --- Not Null Used to store amount of ticket 13 IsPaid Varchar (50) Not Null Used to store paid amount to customer Table Name :- Ticket Description :- To store ticket information Primary Key :- TicketId Foreign Key :- ShowId Index Column Name Data Type Size Constraints Description 1 TicketId Bigint --- Primary key Used to store Ticket Id 2 ShowId Int --- Foreign Key Used to store (Forign key of Show's column ShowId) 3 Seats Varchar (50) Not Null Used to store seats 4 SeatType Varchar (50) Not Null Used to store Seat type 5 NoSeats Int --- Not Null Used to store No. of seats 6 Amount Int --- Not Null Used to store amount of ticket 7 IsPaid Varchar (50) Not Null Used to store paid to customer 8 Mobile Bigint --- Not Null Used to store mobile no of customer 9 Email Varchar (50) Allow Null Used to store email id of customer Table Name :- Feedback Description :- To feedback of customer Primary Key :- FeedBackId Foreign Key:- Index Column Name Data Type Size Constraints Description 1 FeedBackId Int --- Primary key Used to store feedback id 2 UserName Varchar (50) Not Null Used to store username 3 EmailId Varchar (50) Not Null Used to store email id 4 Feedback Varchar (500) Not Null Used to store feedback Input Design HOME SELECT CITY SELECT MOVIE MOVIE REVIEW MOVIE DEATAILS ADMIN LOGIN ADMIN HOME ADD MOVIE ADD MOVIE DEATAIL THEATRE DEATAILS THEATRE DEATAILS UPDATE THEATRE ADD THEATRE ADD THEATRE SEATS MOVIE SHOWS ADD NEW MOVIE SHOW ADD CITY ADD CITY DEATAILS USER LOGIN USER REGISTER DEATAILS SELECT CITY SELECT MOVIE SELECT SHOW SELECT SHOW DEATAIL SELECT SEATS TICKET SUMMARY FEEDBACK TESTING CHARACTERISTICS OF TESTING: Testing begins at the module level and works outward towards the integration of the entire computer based system. Different testing techniques are appropriate at different level of time. Testing & debugging are different activities, but debugging must be accommodated in any testing strategy. There are different model of testing. On the basis of testing methods. There are two types of testing. Black-box testing. White-box testing BLACK-BOX TESTING: Black-box tests are used to demonstrate that software function are operational, that input is properly accepted and output is correctly produced, and that integrity of external information is maintained. WHITE-BOX TESTING: White-box tests are used to examine the procedural details. It checks the logical paths by test case. It can also checks the conditions, loops used in the software coding. It checks that loops are working correctly on defined boundary value. UNIT TESTING FOR COMPONENT: In system calendar use for the book the ticket. In system also provide the facility for the movie information, theater information and upcoming movie information. In system each and every field have unique validation. CUSTOMER SIDE Login page No Test Condition Expected Result Actual Output Status 1 Click On login Button without Username, Password. System does not allow user to login. System will display message. Pass 2 Click on login button with Invalid username, Password. Message “Wrong Username or password” As Expected. Pass 3 Click on Login Button with valid username, password. System allow user to login. System allow user to access application. Pass 4 Click on Register button System allow to go on register page System will display register page Pass Registration page No Test Condition Expected Result Actual Output Status 1 Click On submit button and not enter Username. Message ”Required” As Expected Pass 2 Click On submit button and not enter Password Message ”Required” As Expected Pass 3 Click On submit button and not enter Confirm Password Message ”Required” As Expected Pass 4 Click On submit button and not enter First Name Message ”Required” As Expected Pass 5 Click On Submit button and not enter Last Name Message ”Required” As Expected Pass 6 Click On Submit button and not Address Message “ Select city” As Expected Pass 7 Click On submit button and not enter City Message ”Enter ten digit no” As Expected Pass 8 Click On submit button and not enter Pincode. Message ”Required” As Expected Pass 9 Click On submit button and not enter State Message ”Required” As Expected Pass 10 Click On submit button and not enter Email Message ”Required” As Expected Pass 11 Click On submit button and not enter Mobile Message ”Required” As Expected Pass Select A Show No Test Condition Expected Result Actual Output Status 1 Click On Proceed button and not enter Date Message ”Required” As Expected Pass 2 Click On Proceed button and not enter Theatre Message ”Required” As Expected Pass 3 Click On Proceed button and not enter Seat Type Message ”Required” As Expected Pass 4 Click On Proceed button and not enter no of seat Message ”Required” As Expected Pass Select A Seat No Test Condition Expected Result Actual Output Status 1 Click On Proceed button and not select seat Message ”Required” As Expected Pass Feedback No Test Condition Expected Result Actual Output Status 1 Click On submit button and not enter username Message ”Required” As Expected Pass 2 Click On submit button and not enter email Message ”Required” As Expected Pass 3 Click On submit button and not enter feedback Message ”Required” As Expected Pass ADMIN SIDE Login page No Test Condition Expected Result Actual Output Status 1 Click On login Button without Username, Password. System does not allow user to login. System will display message. Pass 2 Click on login button with Invalid username, Password. Message “Wrong Username or password” As Expected. Pass 3 Click on Login Button with valid username, password. System allow user to login. System allow user to access application. Pass Add Movie No Test Condition Expected Result Actual Output Status 1 Click On Upload button and no file chosen Message ”Required” As Expected Pass 2 Click On Upload button and movie image select Message ”Required” As Expected Pass 3 Click On Add button and not enter Director Message ”Required” As Expected Pass 4 Click On Add button and not enter Producer Message ”Required” As Expected Pass 5 Click On Add button and not enter Cast Message ”Required” As Expected Pass 6 Click On Add button and not enter Duration Message “ Select city” As Expected Pass 7 Click On Add button and not enter Story Message ”Enter ten digit no” As Expected Pass 8 Click On Add button and movie added. Message ”Required” As Expected Pass Select Update Movie No Test Condition Expected Result Actual Output Status 1 Click On movie image and file chosen Message ”Required” As Expected Pass 2 Click On Upload button and no file chosen Message ”Required” As Expected Pass 3 Click On Upload button and movie image upload Message ”Required” As Expected Pass 4 Click On Add button and not enter Director Message ”Required” As Expected Pass 5 Click On Add button and not enter Producer Message ”Required” As Expected Pass 6 Click On Add button and not enter Cast Message “ Select city” As Expected Pass 7 Click On Add button and not enter Duration Message ”Enter ten digit no” As Expected Pass 8 Click On Add button and movie Story Message ”Required” As Expected Pass 9 Click On Add button and movie added. Message ”Required” As Expected Pass Delete Movie No Test Condition Expected Result Actual Output Status 1 Click On Movie image and show movie detail Message ”Required” As Expected Pass 2 Click On Delete button and movie delete Message ”Required” As Expected Pass Add Show No Test Condition Expected Result Actual Output Status 1 Click On Add button and not select movie name. Message ”Required” As Expected Pass 2 Click On Add button and not select city Message ”Required” As Expected Pass 3 Click On Add button and not select theatre name Message ”Required” As Expected Pass 4 Click On Add button and not enter Screen No Message ”Required” As Expected Pass 5 Click On Add button and not enter Start time Message ”Required” As Expected Pass 6 Click On Add button and not enter End time Message “ Select city” As Expected Pass 7 Click On Add button and not enter Date Message ”Enter ten digit no” As Expected Pass 8 Click On Add button and not enter Platinum Rate Message ”Required” As Expected Pass 9 Click On Add button and not enter Gold Rate Message ”Required” As Expected Pass 10 Click On Add button and not enter Silver Rate Message ”Required” As Expected Pass 11 Click On Add button and Show added Message ”Required” As Expected Pass Update Show No Test Condition Expected Result Actual Output Status 1 Click On Update button and not select movie name. Message ”Required” As Expected Pass 2 Click On Update button and not select city Message ”Required” As Expected Pass 3 Click On Update button and not select theatre Message ”Required” As Expected Pass 4 Click On Update button and not enter Screen No Message ”Required” As Expected Pass 5 Click On Add button and not enter Date Message ”Enter ten digit no” As Expected Pass 6 Click On Update button and not enter Start Time Message ”Required” As Expected Pass 7 Click On Update button and Show updated Message ”Required” As Expected Pass Add City No Test Condition Expected Result Actual Output Status 1 Click On Add Button and not enter City name. Message ”Required” As Expected Pass 2 Click on Add button and not enter State. Message ”Required” As Expected. Pass 3 Click on Add Button and City added Message ”Required” As Expected. Pass Visitor Side No Test Condition Expected Result Actual Output Status 1 Click On Movie image Show the movie information As Expected Pass 2 Click on Review button Show the movie information As Expected. Pass POST IMPLEMENTATION REVIEW Post Implementation Review is done after the completion of coding and testing part, to know the review of the people who have used this project. After the system is implemented and conversion is completed, a review of system is usually conducted by users and analyst. This is called post implementation review. The most fundamental concern post implementation review is determining whether the system has met its objective; that is analysts want to know if the performance level of users 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 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 than you find it to be complete but we want to make it still mature and fully automatic. Some of the expansions which we have thought of are: We want to improve our home page , as it is the main things which attracts all users. Payment facility for bank to user. BIBLIOGRAPHY List of Books Referred : Software engineering By:: Roger S. Pressman By ASP.NET List of Website Visited: www.google.com www.redcarpet.com