A Ticket Booking System For Theatre

A Ticket Booking System For Theater The motivation behind the online ticket booking framework is to give another approach to buying film tickets ahead of time. It is a programmed framework. This paper presents a proper utilization of the Object Oriented examination and Design, we will show our framework by giving Use Case Diagrams Specifications, Activity Diagrams, Class Diagrams, Sequence Diagrams, State Machines and Communication Diagrams on the functionalities of the framework, additionally we will give some procedure depiction and information word reference. The objectives of our framework are: Record execution subtleties Record client subtleties Record tickets sold Print tickets Print address names for phone booking Assignment 1: Functional Modeling Distinguishing proof of Actors Use Cases Dissecting the current framework we made sense of that, there are two fundamental degrees to be canvassed in the framework. The degrees are Performance Planning and Ticket Booking. We utilized the beneath table to recognize the Actors and the Use Cases for the framework. Client Job Use Case Theater Manager Execution arranging Characterize the kind of the exhibition and name it. Execution booking Characterize date and time of the exhibition. Craftsman booking Book a craftsman for the exhibition. Ticket valuing Decide a cost for the ticket. Assistant Check plan Check the exhibition plan for a specific show out on the town. Check seat accessibility Checks for accessible seats Catch client data Record client subtleties Check ticket cost Check for ticket cost for specific show. Sell ticket Record tickets sold. Print ticket Print ticket for the client. Print address mark Print address mark for phone booking. Use Case Diagram Following graph shows the general perspective on the Ticket Booking System for Theater. Figure 1: Use Case Diagram (Performance Planning Ticket Booking) Use Case Specification Table 1: Use Case of Performance Planning Number: UC01 Req. Doc Ref: Name: Execution Planning Status: Entertainers: Theater Manager Pre-necessities: Client ought to be signed in the framework. Objective: Characterizing the exhibition type and naming it. Use Case Relationships: Extend:UC02, UC03 Include: Affiliation: Speculation: Depiction: File On-screen character Event 1 Client enters the name of the exhibition. 2 Client enters the kind of the presentation. 3 Framework checks for every single required datum section. 4 Framework associates with the database. 5 Framework composes information into the database. 6 Framework shows an affirmation message after fruitful database composes. Options: File Entertainer Event A 3.1 Enter required data. A 4.1 Check arrange network A 4.2 Check database network A 4.3 Check database client job A 5.1 Theater supervisor gets notice of fruitless activity. Table 2: Use Case of Performance Scheduling Number: UC02 Req. Doc Ref: Name: Execution Scheduling Status: Entertainers: Theater Manager Pre-imperatives: Client ought to be signed in the framework. Execution arranging (UC01) ought to be embedded into the framework. Objective: Characterize date and time of the presentation. Use Case Relationships: Expand: Include: Affiliation: Speculation: Portrayal: List On-screen character Event 1 Client chooses the ideal execution from the framework. 2 Client enters the date of the presentation. 3 Client enters the hour of the presentation. 4 Framework checks for every necessary datum section. 5 Framework associates with the database. 6 Framework composes information into the database. 7 Framework shows an affirmation message after fruitful database composes. Choices: Record On-screen character Event A 3.1 Enter required data. A 5.1 Check organize network A 5.2 Check database network A 5.3 Check database client job A 6.1 Theater administrator gets notice of fruitless activity. Table 3: Use Case of Artist Booking Number: UC03 Req. Doc Ref: Name: Craftsman Booking Status: On-screen characters: Theater Manager Pre-requirements: Client ought to be signed in the framework. Execution arranging (UC01) ought to be embedded into the framework. Objective: Book a craftsman for the presentation. Use Case Relationships: Expand: Include: Affiliation: Speculation: Portrayal: List On-screen character Event 1 Client chooses the ideal execution from the framework. 2 Client enters the name of the ideal craftsman. 3 Framework checks for every single required datum passage. 4 Framework associates with the database. 5 Framework composes information into the database. 6 Framework shows an affirmation message after effective database composes. Choices: List Entertainer Event A 3.1 Enter required data. A 4.1 Check organize availability A 4.2 Check database network A 4.3 Check database client job A 5.1 Theater supervisor gets warning of ineffective activity. Table 5: Use Case of Schedule Checking Number: UC04 Req. Doc Ref: Name: Timetable Checking Status: Entertainers: Representative Pre-imperatives: Client ought to be signed in the framework. Execution booking (UC02) ought to be embedded into the framework. Objective: Check the exhibition plan for a specific show out on the town. Use Case Relationships: Expand: UC01 Include: Affiliation: Speculation: Portrayal: Record On-screen character Event 1 Client chooses an ideal presentation and a date. 2 Framework shows an affirmation message for the accessibility of the presentation. 3 Framework permits the client to play out the following occasion (UC06). Choices: Record On-screen character Event A 1.1 Framework advises the client that the presentation is inaccessible on the ideal date. Table 6: Use Case of Check Seat Availability Number: UC05 Req. Doc Ref: Name: Check Seat Availability Status: On-screen characters: Assistant Pre-essentials: Client ought to be signed in the framework. Timetable checking (UC05) ought to be performed by the client. Objective: Checks for accessible seats. Use Case Relationships: Broaden: Include: Affiliation: Speculation: Depiction: File Entertainer Event 1 Client chooses an ideal exhibition and a date. 2 Framework shows an affirmation message for the accessibility of the seat. 3 Framework permits the client to play out the following occasion (UC07). Options: File Entertainer Event A 1.1 Framework tells the client that the seat is inaccessible for the ideal execution. Table 7: Use Case of Capturing Customer Information Number: UC06 Req. Doc Ref: Name: Catch Customer Information Status: Entertainers: Representative Pre-imperatives: Client ought to be signed in the framework. Seat checking (UC06) ought to be performed by the client. Objective: Record client subtleties. Use Case Relationships: Broaden: Include: Affiliation: Speculation: Depiction: File Entertainer Event 1 Client enters the name, address and phone number of the client. 2 Framework checks for every single required datum section. 3 Framework associates with the database. 4 Framework composes information into the database. 5 Framework shows an affirmation message after effective database composes. Choices: List Entertainer Event A 2.1 Enter required data. A 3.1 Check organize network A 3.2 Check database network A 3.3 Check database client job A 4.1 Client gets notice of fruitless activity. Table 8: Use Case of Checking Ticket Price Number: UC07 Req. Doc Ref: Name: Check Ticket Price Status: Entertainers: Representative Pre-imperatives: Client ought to be signed in the framework. Ticket evaluating data (UC04) ought to be gone into the framework. Objective: Check for ticket cost for specific show Use Case Relationships: Broaden: UC01 Include: Affiliation: Speculation: Depiction: File On-screen character Event 1 Client chooses an ideal presentation structure the framework. 2 Framework shows the characterized valuing for the ticket. Options: Record On-screen character Event A 2.1 Cost not discovered is advised to the client. Table 9: Use Case of Selling Ticket Number: UC08 Req. Doc Ref: Name: Selling Ticket Status: On-screen characters: Assistant Pre-requirements: Client ought to be signed in the framework. Check ticket value (UC08) ought to be performed by the client. Objective: Record tickets sold. Use Case Relationships: Expand: Include: Affiliation: Speculation: Portrayal: List Entertainer Event 1 Client chooses the ideal execution from the framework. 2 Client enters ticket selling date and the ticket cost for the ideal execution. 3 Framework checks for every single required datum section. 4 Framework interfaces with the database. 5 Framework composes information into the database. 6 Framework shows an affirmation message after fruitful database composes. Choices: List Entertainer Event A 3.1 Enter required data. A 4.1 Check organize network A 4.2 Check database availability A 4.3 Check database client job A 5.1 Theater director gets notice of fruitless activity. Table 10: Use Case of Printing Ticket Number: UC09 Req. Doc Ref: Name: Printing Ticket Status: On-screen characters: Assistant Pre-requirements: Client ought to be signed in the framework. Check ticket value (UC08) ought to be performed by the client. Objective: Print ticket for the client Use Case Relationships: Broaden: Include: Affiliation: Speculation: Depiction: File Entertainer Event 1 Client triggers the print order for the sold ticket. Options: File Entertainer Event A 1.1 Printer not discovered warning will be given to the client. Table 11: Use Case of Checking Ticket Booking Type Number: UC10 Req. Doc Ref: Name: Check Ticket Booking Type Status: Entertainers: Agent Pre-necessities: Client ought to be signed in the framework. Print ticket (UC10) ought to be performed by the client. Objective: Decide the ticket booking type. Use Case Relationships: Broaden: Include: Affiliation: Speculation: Depiction: File Entertainer Event 1 Client chooses the booking type to distinguish whether the ticket was reserved over telephone. Options: File Entertainer Event Table 12: Use Case of Printing Address Label Number: UC11 Req. Doc Ref: Name: Print Address Label Status: Entertainers: Agent Pre-necessities: Client ought to be signed in the framework. Ticket booking type (UC11) ought to be performed by the client. Objective: Print address