A Ticket Booking System For Theatre

A fine conflict transcription For TheatreThe purpose of the online tatter conflict dodging is to provide a nary(prenominal)her way for buying cinema just the books in advance. It is an automatic dodging. This paper presents a formal use of the Object Oriented compend and Design, we allow illustrate our formation by providing consumption brass Diagrams with Specifications, Activity Diagrams, Class Diagrams, eon Diagrams, accede shapes and Communication Diagrams on the functionalities of the system, also we go away provide some process description and selective tuition dictionary.The goals of our system atomic hail 18Record accomplishment expoundRecord customer detailsRecord tickets sold strike ticketsPrint address labels for call(a) off booking travail 1 Functional imitateIdentification of meanss work sideslipsAnalyzing the existing system we figured out that, at that place be two main scopes to be cover in the system. The scopes are executing Planning and Ticket binding. We utilize the below table to let out the pseuds and the drop Cases for the system. substance absubstance ab exploiterRole expenditure CaseTheatre managing director implementation planningDefine the token of the process and name it.Performance schedulingDefine date and quantify of the process. artisan booking deem an artist for the death penalty.Ticket pricingDetermine a price for the ticket.Clerk summate schedule apprehension the performance schedule for a bad-tempered deliver on a date. curb invest availabilityChecks for available seatsCapture customer schoolingRecord customer detailsCheck ticket priceCheck for ticket price for particular show.Sell ticketRecord tickets sold.Print ticketPrint ticket for the customer.Print address labelPrint address label for telephone booking. usance Case DiagramFollowing plot shows the overall view of the Ticket Booking constitution for Theatre. name 1 Use Case Diagram (Performance Planning Ticket Booking)Use Case Specification carry over 1 Use Case of Performance PlanningNumberUC01Req. mercantilism RefNamePerformance Planning condition performersTheatre ManagerPre-requisites exploiter should be logged in the system. objectDefining the performance type and naming it.Use Case RelationshipsExtendUC02, UC03 overwhelm connectiveGeneralization comment listActor pillow slip1User enters the name of the performance.2User enters the type of the performance.3 governance checks for all required selective information entry.4 dodging connects to the database.5 placement writes data into the database.6System shows a confirmation message after successful database writes.AlternativesIndexActor essenceA 3.1 get down required teaching.A 4.1Check network connectivityA 4.2Check database connectivityA 4.3Check database user subroutineA 5.1Theatre manager gets notification of unsuccessful operation. give in 2 Use Case of Performance SchedulingNumberUC02Req. mendelevium RefNamePerformance SchedulingStat usActorsTheatre ManagerPre-requisitesUser should be logged in the system.Performance planning (UC01) should be inserted into the system.GoalDefine date and magazine of the performance.Use Case RelationshipsExtend involve companionshipGeneralizationDescriptionIndexActor Event1User selects the desired performance from the system.2User enters the date of the performance.3User enters the time of the performance.4System checks for all required data entry.5System connects to the database.6System writes data into the database.7System shows a confirmation message after successful database writes.AlternativesIndexActor EventA 3.1 inscribe required breeding.A 5.1Check network connectivityA 5.2Check database connectivityA 5.3Check database user portionA 6.1Theatre manager gets notification of unsuccessful operation. fudge 3 Use Case of Artist BookingNumberUC03Req. doc RefNameArtist BookingStatusActorsTheatre ManagerPre-requisitesUser should be logged in the system.Performance planning (UC01) should be inserted into the system.GoalBook an artist for the performance.Use Case RelationshipsExtend implicate crosstieGeneralizationDescriptionIndexActor Event1User selects the desired performance from the system.2User enters the name of the desired artist.3System checks for all required data entry.4System connects to the database.5System writes data into the database.6System shows a confirmation message after successful database writes.AlternativesIndexActor EventA 3.1Enter required information.A 4.1Check network connectivityA 4.2Check database connectivityA 4.3Check database user roleA 5.1Theatre manager gets notification of unsuccessful operation.Table 5 Use Case of Schedule CheckingNumberUC04Req. Doc RefNameSchedule CheckingStatusActorsClerkPre-requisitesUser should be logged in the system.Performance scheduling (UC02) should be inserted into the system.GoalCheck the performance schedule for a particular show on a date.Use Case RelationshipsExtend UC01IncludeAssociationGener alizationDescriptionIndexActor Event1User selects a desired performance and a date.2System shows a confirmation message for the availability of the performance.3System allows the user to perform the conterminous event (UC06).AlternativesIndexActor EventA 1.1System notifies the user that the performance is unavailable on the desired date.Table 6 Use Case of Check Seat AvailabilityNumberUC05Req. Doc RefNameCheck Seat AvailabilityStatusActorsClerkPre-requisitesUser should be logged in the system.Schedule checking (UC05) should be performed by the user.GoalChecks for available seats.Use Case RelationshipsExtendIncludeAssociationGeneralizationDescriptionIndexActor Event1User selects a desired performance and a date.2System shows a confirmation message for the availability of the seat.3System allows the user to perform the next event (UC07).AlternativesIndexActor EventA 1.1System notifies the user that the seat is unavailable for the desired performance.Table 7 Use Case of Capturing Cust omer InformationNumberUC06Req. Doc RefNameCapture Customer InformationStatusActorsClerkPre-requisitesUser should be logged in the system.Seat checking (UC06) should be performed by the user.GoalRecord customer details.Use Case RelationshipsExtendIncludeAssociationGeneralizationDescriptionIndexActor Event1User enters the name, address and telephone number of the customer.2System checks for all required data entry.3System connects to the database.4System writes data into the database.5System shows a confirmation message after successful database writes.AlternativesIndexActor EventA 2.1Enter required information.A 3.1Check network connectivityA 3.2Check database connectivityA 3.3Check database user roleA 4.1User gets notification of unsuccessful operation.Table 8 Use Case of Checking Ticket expenditureNumberUC07Req. Doc RefNameCheck Ticket harmStatusActorsClerkPre-requisitesUser should be logged in the system.Ticket pricing information (UC04) should be entered into the system.GoalChe ck for ticket price for particular showUse Case RelationshipsExtend UC01IncludeAssociationGeneralizationDescriptionIndexActor Event1User selects a desired performance form the system.2System shows the defined pricing for the ticket.AlternativesIndexActor EventA 2.1 outlay not found is notified to the user.Table 9 Use Case of Selling TicketNumberUC08Req. Doc RefNameSelling TicketStatusActorsClerkPre-requisitesUser should be logged in the system.Check ticket price (UC08) should be performed by the user.GoalRecord tickets sold.Use Case RelationshipsExtendIncludeAssociationGeneralizationDescriptionIndexActor Event1User selects the desired performance from the system.2User enters ticket selling date and the ticket price for the desired performance.3System checks for all required data entry.4System connects to the database.5System writes data into the database.6System shows a confirmation message after successful database writes.AlternativesIndexActor EventA 3.1Enter required information. A 4.1Check network connectivityA 4.2Check database connectivityA 4.3Check database user roleA 5.1Theatre manager gets notification of unsuccessful operation.Table 10 Use Case of belief TicketNumberUC09Req. Doc RefNamePrinting TicketStatusActorsClerkPre-requisitesUser should be logged in the system.Check ticket price (UC08) should be performed by the user.GoalPrint ticket for the customerUse Case RelationshipsExtendIncludeAssociationGeneralizationDescriptionIndexActor Event1User triggers the print call for for the sold ticket.AlternativesIndexActor EventA 1.1Printer not found notification will be given to the user.Table 11 Use Case of Checking Ticket Booking imageNumberUC10Req. Doc RefNameCheck Ticket Booking typeStatusActorsClerkPre-requisitesUser should be logged in the system.Print ticket (UC10) should be performed by the user.GoalDetermine the ticket booking type.Use Case RelationshipsExtendIncludeAssociationGeneralizationDescriptionIndexActor Event1User selects the booking t ype to identify whether the ticket was booked over phone.AlternativesIndexActor EventTable 12 Use Case of Printing Address tagNumberUC11Req. Doc RefNamePrint Address commemorateStatusActorsClerkPre-requisitesUser should be logged in the system.Ticket booking type (UC11) should be performed by the user.GoalPrint address label for telephone bookingUse Case RelationshipsExtend UC11IncludeAssociationGeneralizationDescriptionIndexActor Event1User triggers the print command to print the address label.AlternativesIndexActor EventActivity DiagramBased on the system observation, a high level activity diagram is drawn modelling the process of ticket booking for theatre. The activity diagram will bring everybody on a common ground for understanding the system functionalities. look-alike 2 Activity Diagram (Performance Planning Ticket Booking)Task 2 Structural ModellingClass Diagram (attri providedes operations)The surveying diagram depicts the relationships between the classes for Ticket Booking System along with the attri just nowes and the operations.Figure 3 Class Diagram (Performance Planning Ticket Booking)Task 3 Behavioural ModellingSequence DiagramThe following diagram is a season diagram for buying ticket. in that respect are a few(prenominal) things I want to state, that this is just one of the sequences of buying ticket. There could be more alternative sequence for buying ticket. For example, we can choice a performance before buying ticket. But the overall structures of all buying ticket sequence are similar, so, others sequence will not be shown.Figure 4 Sequence Diagram (Performance Planning Ticket Booking)State Machine DiagramBelow diagram is use to give an abstract description of the behaviour of the ticket booking system. This behaviour is analyzed and represented in series of events that could occur in one or more possible states. Hereby each diagram usually represents objects of a single class and tracks the antithetical states of its objects through the system.Figure 5 State Machine Diagram (Performance Planning Ticket Booking)Communication DiagramCommunication diagram is similar to sequence diagrams, but it provides an overview of the relationships between objects, rather than focusing on the order of messages between objects, as the software product executes.Figure 6 Communication Diagram (Performance Planning Ticket Booking)Task 4 selective information Protection Law gateIn Bangladesh Cyber Acts are in a process to be implemented. The Government of Bangladesh has formed National Council for lore and Technology (NCST). The Executive Committee for NCST has also been formed to implement policies formulated by the Council. Currently NCST is on the frolic(p) with the general springaries to protect the ICT industry and specific laws are yet to be decided. For our application we can follow the acts and regulations from UK.Laws, Regulations and Best PracticesThe info Protection Act gives individuals the right to kno w what information is held nearly them. It provides a textile to ensure that personal information is adhesive frictiond properly. The Act works in two ways. Firstly, it states that anyone who processes personal information must comply with eight principles, which suffice sure that personal information isFairly and lawfully processed processed for particular(a) purposesAdequate, relevant and not excessiveAccurate and up to dateNot kept for longstanding than is necessaryProcessed in line with your rightsSecureNot transferred to other countries without adequate resistanceThe morsel area covered by the Act provides individuals with important rights, including the right to find out what personal information is held on computer and most paper records.Data protection laws should be adequate enough to take note the below options at a minimum-How to access informationThis allows one to find out what information is held most him/her on a computer and within some manual records, suc h as medical records, files held by public bodies and financial information held by credit reference agencies.Correcting informationThis allows one to apply to a court to order a data restraint to correct, block, remove or destroy personal details if they are inaccurate or contain expressions of opinion based on inaccurate information.Preventing processing of informationThis means one can ask a data controller not to process information about him/her that causes substantial unwarranted damage or distress. The data controller is not always bound to act on the request.Preventing unsolicited marketingThis means a data controller is required not to process information about one for direct marketing purposes if he/she asks them not to.Preventing automated decision makingThis means one can object to decisions made only by automatic means. For example, where there is no human involvement.Claiming compensationThis allows one to claim compensation through the courts from a data controller for damage, and in some cases distress, caused by any breach of the act.Exempt informationThis allows one to ask the information commissioner to investigate and assess whether the data controller has breached the act.There should be a committee (in our case NCTS could be the choice) that will have legal powers to ensure that organizations comply with the requirements of the data protection laws. It is notable here that these powers are focused on ensuring that organizations meet the obligations of the act.To promote opera hat practices the regulation-The committee should carry out consensual audits with data controllers to assess their processing of personal information.The committee should see auditing as a constructive process with authoritative benefits for data controllers.The committee should adopt, wherever possible, a participative approach including working closely with the data controller to adjudge the timing and scope of the audit.Comply with Data Protection LawA short checklist can assistance us to comply with the data protection laws in our system. Maintaining all the items in the checklist does guarantee compliance but it should mean that we are heading in the right direction.We should store only the related information about the customer and the personnels involved with the system. And we need to clear sure that we know what we are breathing out to do with the information.The person should know, what are the information we are holding. He/she should understand what it will be used for.Information should be held securely whether its on the paper or on computer.The system should observe any unwanted access of its resources.The information should be deleted as soon as there is no need for it.Access control list should be created with a strict need to know to sustain data access from all kind of users of the system.We should train the stuff in their duties and responsibilities under the act that we are putting them in to practice.Recommendat ionsBeing a strategic regulator means that, in so distant as we have a choice, we have to be selective with our interventions. We will therefore apply our limited resources in ways that deliver the maximum succumb in terms of a sustained simplification in data protection risk. That is the risk of harm through improper use of personal information.There are priorities we have to set. We need to focus most attention on situations where there is a accepted likelihood of serious harm. We also need to focus on situations where our intervention is most likely to make a long term as well as a short term difference. When we interject we must do so in a way that gives us the best possible return and remember that we will often be at our most effective when working closely with others. We are entitled to have legitimate expectations of those who are in a position to fascinate data protection risk. Our effectiveness depends on them seeking and welcoming our reasonable interventions. Furt hermore we have an important international role. Data protection risk in the Bangladesh is increasingly influenced by events worldwide.Our risk-based approach is in line with good regulative practice. It does not mean that we seek to remove all data protection risk. We do what we can to support the most serious risks and protect those who are most vulnerable to improper use of their information. But we will not try to take away forgodom of choice and will remember that individuals themselves ought to be best placed to make decisions about their own interests. Part of our job is to equip individuals with the knowledge and tools to enable them to make their own well-informed decisions about the use and disclosure of their personal information.Being a strategic regulator also means extending our approach beyond simply improving (through guidance, persuasion and regulatory action) the behaviour of organisations that handle personal information. We also have a legitimate role in infor ming and influencing the market or political environment in which they operate. Thus we will seek to have long term influence over government and the legislature at Westminster and in the devolved administrations as well as over interpreter bodies and other stakeholders, to ensure privacy friendly outcomes.We will also seek to influence the legal textile that governs our own work to ensure that data protection requirements are simple-minded, meaningful and proportionate and that we have the flexibility and tools to regulate effectively.Building public confidence in data protection is the key in our approach. We protect people, not just information. This means we need to engage with the public and explain what we do in a way that they can easily understand and relate to.This commitment is at the heart of how we approach our job as data protection regulator and will inform all our data protection tasks including complaints discussion and the provision of advice.Task 5 Ticket Print ingProduce TicketsTo protect the tickets from being forged or copied we can use a barcode on each ticket. Well print a unique 10-digit number as a barcode on the tickets, which will be checked at the entrance with the software and a simple barcode scanner. As each barcode can only be used once to enter, copied or forged tickets are rejected and the revenues are protected. By default, the tickets will be labeled with random numbers with 10 digits, which will serve as copy protection.Figure 7 Sample barcode to print on ticketsSeat apportionmentTickets will be printed with seat numbers, with serial numbers. Section names can be in different colours to facilitate orientation. For sections with an aisle a seat description can be added to the seat number (e.g. left, right), which helps the visitor to find the seat.Figure 8 Sample barcode to print on ticket with seat no.Hardware for printing ticketsThere are numerous tickets available in the market but I found D-Link newspapermans suitab le for our system. Below are the details of the hardware-Description With the DSA-3100 and the DSA-3100P Ticket Printer, businesses and organizations can provide free or fee-based broadband Internet access to their customers or members. No complex billing system is required, guaranteeing a quick and convenient Internet experience for operators and their hot spot users. The DSA-3100P is hassle-free hot spot ticket printer that communicates with the DSA-3100 Public/ surreptitious Gateway to generate and print log-in usernames and passwords for the hot spot customers. Patented for simplified loading, the DSA-3100P is connected to the DSA-3100 gateway via its RS-232 serial communication. With the DSA-3100P, the DSA-3100 gateway can manage and store up to 2,000 user accounts in its internal database and support up to 50 logged-in users at any time.FeaturesPrinting Method Thermal disseminate Line PrintingPrint Speed 80 mm/SecondConnectivity RS-232 SerialCompatibility D-Link DSA-3100 Pub lic/Private GatewaySpecificationManufacturerD-LinkManufacturer Part DSA-3100PDevice TypeThermal Line Label PrinterMedia HandlingMedia TypeReceipt PaperMax Media Size2.2Max Printing comprehensiveness1.9Roll Maximum Outer Diameter3.3Total Capacity1 RollConnectivityInterfaces1 x RS-232 SerialIncluded Cables1 x Serial CablePower RequirementsPower SupplyExternal, 3.5 V DCDimensions(H X W X D)Unit4.6 x 3.8 x 6.3WeightUnit0.9 lbsPrice $375Figure 9 D-Link DSA-3100P Ticket PrinterTask 6 Database DesignDatabase DesignFigure 10 Database Design (Performance Planning Ticket Booking)Data DictionaryTable ArtistAttributeData Type distancePrimary KeyRef. TableArtistIDwhole numberYesArtistNameVarchar100Table PerformanceAttributeData TypeLengthPrimary KeyRef. TablePerformanceID integerYesPerformanceNameVarchar100TicketPriceIDIntegerTicketPriceArtistIDIntegerArtistTable TicketPriceAttributeData TypeLengthPrimary KeyRef. TableTicketPriceIDIntegerYesPerformanceIDIntegerPerformanceTicketPriceNumeric(18, 2)Table PerformanceScheduleAttributeData TypeLengthPrimary KeyRef. TableScheduleIDIntegerYesPerformanceIDIntegerPerformancePerformanceDateDateTable CustomerAttributeData TypeLengthPrimary KeyRef. TableCustomerIDIntegerYesNameVarchar100AddressVarchar250TelephoneVarchar20Table SalesAttributeData TypeLengthPrimary KeyRef. TableSalesIDIntegerYesPerformanceIDIntegerPerformanceScheduleIDIntegerPerformanceScheduleTicketPriceIDIntegerTicketPriceCustomerIDIntegerCustomerBookingTypeBooleanTable SeatAllocationAttributeData TypeLengthPrimary KeyRef. TableSeatIDIntegerYesSalesIDIntegerSalesSeatNoFromIntegerSeatNoToIntegerTask 7 Object-Orient Approaches vs. Standard ApproachesStandard ApproachesStandard approach includes many variations based on techniques used to forge information system with incorporated and modular programming. Standard analysis and design techniques are a software engineering methodology for describing systems as a hierarchy of functions. Below are the characteristics of St andard Approaches.Approach for structured analysis consists of the following objectsData Flow Diagrams (DFD)Shows processes and flow of data in and out of these processes.Does not show control structures (loops)Contains 5 graphic symbols (shown later)Uses layers to decompose complex systemsCan be used to show pellucid and physicalIs a quantum leap forward to other techniques at the time, I.e. monolithic descriptions with globs of text.Context Diagram