A Ticket Booking System For Theatre

A tag end Booking dust For battlefieldThe purpose of the online ticket booking system is to provide a nonher expression for purchasing movie tickets in advance. It is an automatic system. This paper presents a formal use of the Object Oriented analytic thinking and Design, we go forth illustrate our system by providing Use display case diagrams with Specifications, application Diagrams, Class Diagrams, Sequence Diagrams, State Machines and Communication Diagrams on the functionalities of the system, also we willing provide some cover description and selective information dictionary.The goals of our system be remember makeance detailsRecord client detailsRecord tickets sold f both guy ticketsPrint address labels for teleph unrivaled bookingTask 1 Functional ModellingIdentification of Actors Use contingencysAnalyzing the existing system we figured out that, there are two main scopes to be covered in the system. The scopes are exercise Planning and fine Booking. We u sed the below table to identify the Actors and the Use brasss for the system.UserRoleUse CaseTheatre autobusPerformance planningDefine the grapheme of the performance and name it.Performance schedulingDefine date and time of the performance.Artist bookingBook an mechanic for the performance. tatter pricingDetermine a cost for the ticket.Clerk watch over schedule interrupt the performance schedule for a particular fork up on a date. follow seat availabilityChecks for available seatsCapture customer informationRecord 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.Use Case DiagramFollowing plat shows the overall view of the Ticket Booking System for Theatre.Figure 1 Use Case Diagram (Performance Planning Ticket Booking)Use Case Specification flurry 1 Use Case of Performance Planning exitUC01Req. mendelevium refereeN amePerformance PlanningStatusActorsTheatre ManagerPre-requisitesUser should be logged in the system.GoalDefining the performance type and naming it.Use Case RelationshipsExtendUC02, UC03Include connectedness generality definition tycoonActor cause1User enters the name of the performance.2User enters the type of the performance.3System checks for all inevitable entropy entry.4System connects to the database.5System writes data into the database.6System shows a confirmation message after sure-fire database writes.AlternativesIndexActor EventA 3.1Enter required information.A 4.1Check network connectivityA 4.2Check database connectivityA 4.3Check database user office staffA 5.1Theatre manager gets apprisal of unsuccessful operation.Table 2 Use Case of Performance computer programmingNumberUC02Req. Doc RefNamePerformance SchedulingStatusActorsTheatre ManagerPre-requisitesUser should be logged in the system.Performance planning (UC01) should be inserted into the system.GoalDefine da te and time of the performance.Use Case RelationshipsExtendInclude tie beamGeneralizationDescriptionIndexActor 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.1Enter required information.A 5.1Check network connectivityA 5.2Check database connectivityA 5.3Check database user roleA 6.1Theatre manager gets nonification of unsuccessful operation.Table 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 RelationshipsExtendInclude friendshipGeneralizationDescriptionIndexActor Event1Us er 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 record CheckingNumberUC04Req. Doc RefName muniment 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 UC01IncludeAssociationGeneralizationDescriptionIndexActor Event1User selects a desired performance and a date.2System shows a confirmation message for the availability of the performance.3Syste m allows the user to perform the next concomitant (UC06).AlternativesIndexActor EventA 1.1System notifies the user that the performance is unavailable on the desired date.Table 6 Use Case of Check fag end 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 customer InformationNumberUC06Req. Doc RefNameCapture Customer InformationStatusActorsClerkPre-requisitesUser should be logged in the system.Seat checking (UC06) shoul d 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 PriceNumberUC07Req. Doc RefNameCheck Ticket PriceStatusActorsClerkPre-requisitesUser should be logged in the system.Ticket pricing information (UC04) should be entered into the system.GoalCheck for ticket price for particular showUse Case RelationshipsExtend UC01IncludeAssociationGeneralizationDescriptionIndexActor Event1User selects a desired performance for m the system.2System shows the defined pricing for the ticket.AlternativesIndexActor EventA 2.1Price 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 Ca se 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 bring out command for the sold ticket.AlternativesIndexActor EventA 1.1 printer not found notification will be break downn to the user.Table 11 Use Case of Checking Ticket Booking TypeNumberUC10Req. 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 type to identify whether the ticket was booked over phone.AlternativesIndexActor EventTable 12 Use Case of Printing Address LabelNumberUC11Req. Doc RefNamePrint Addr ess LabelStatusActorsClerkPre-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 act 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.Figure 2 Activity Diagram (Performance Planning Ticket Booking)Task 2 Structural ModellingClass Diagram (attributes operations)The following diagram depicts the relationships amongst the classes for Ticket Booking System along with the attributes and the operations.Figure 3 Class Diagram (Performance Planning Ticket Booking)Task 3 Behavioural ModellingSequence DiagramThe following diagra m is a sequence diagram for acquire ticket. There are few 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, separates sequence will not be shown.Figure 4 Sequence Diagram (Performance Planning Ticket Booking)State Machine DiagramBelow diagram is used 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 different 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 relationship s between objects, rather than focusing on the order of messages between objects, as the software executes.Figure 6 Communication Diagram (Performance Planning Ticket Booking)Task 4 Data Protection LawIntroductionIn Bangladesh Cyber Acts are in a process to be follow uped. The Government of Bangladesh has formed National Council for Science and Technology (NCST). The Executive Committee for NCST has also been formed to implement policies formulated by the Council. Currently NCST is working with the general boundaries 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 better(p) PracticesThe Data Protection Act gives individuals the right to know what information is held about them. It provides a framework to ensure that individualized information is handled properly. The Act works in two ways. Firstly, it states that anyone who processes ain information must comply with ei ght principles, which make sure that personal information isFairly and lawfully processedProcessed for contain purposesAdequate, relevant and not excessiveAccurate and up to datenot kept for longer than is necessaryProcessed in line with your rightsSecureNot transferred to other countries without adequate protectionThe second 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 maintain the below options at a minimum-How to access informationThis allows one to find out what information is held about him/her on a computer and within some manual records, such as medical records, files held by human beings bodies and financial information held by credit reference agencies.Correcting informationThis allows one to apply to a court to order a data controller to correct, block, arrive at or destroy personal details if they are inaccurate or contain expressions of opinion based on inaccurate information.Preventing processing of informationThis style 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 make 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 focus on ensuring that organizations meet the obligations of the act.To promote best 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 real benefits for data controllers.The committee should adopt, wherever possible, a participative approach including working closely with the data controller to agree the time and scope of the audit.Comply with Data Protection LawA short checklist can help 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 t he personnels involved with the system. And we need to make sure that we know what we are going 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 prevent 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 prevent 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 set them in to practice.RecommendationsBeing a strategic regulator means that, in so far 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 return in terms of a sustained reduction 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 tending on situations where there is a real 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 intervene 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 authorise to have legitimate expectations of those who are in a position to influence data protection risk. Our effectiveness depends on them look toing and welcoming our reasonable interventions. moreover 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 regulatory practice. It does not mean that we seek to remove all data protection risk. We do what we can to moderate the most serious risks and protect those who are most unsafe to improper use of their information. But we will not try to take away freedom of choice and will remember that individuals themselves ought to be best move 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 informing 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 representative bodies and other stakeholders, to ensure privacy friendly outcomes.We will also see k to influence the legal framework that governs our own work to ensure that data protection requirements are simple, 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 perpetration is at the heart of how we approach our job as data protection regulator and will inform all our data protection tasks including complaints handling and the preparation of advice.Task 5 Ticket PrintingProduce 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 tagged with random numbers with 10 digits, which will serve as copy protection.Figure 7 Sample barcode to print on ticketsSeat AllocationTickets 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. ironware for printing ticketsThere are numerous tickets available in the market but I found D-Link printers suitable for our system. Below are the details of the hardware-Description With the DSA-3100 and the DSA-3100P Ticket pressman, 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 mobile 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/Private Gateway to generate and print access usernames and passwords for the hot spot customers. Patented for easy 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 inborn database and support up to 50 logged-in users at any time.FeaturesPrinting Method Thermal Dot Line PrintingPrint Speed 80 mm/SecondConnectivity RS-232 SerialCompatibility D-Link DSA-3100 Public/Private GatewaySpecificationManufacturerD-LinkManufacturer Part DSA-3100PDevice TypeThermal Line Label PrinterMedia HandlingMedia TypeReceipt PaperMax Media Size2.2Max Printing Width1.9Roll Maximum Outer Diameter3.3Total expertness1 RollConnectivityInterfaces1 x RS-232 SerialIncluded Cables1 x Serial CablePower RequirementsPower SupplyExternal, 3.5 V D CDimensions(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 spacePrimary KeyRef. TableArtistIDwhole numberYesArtistNameVarchar100Table PerformanceAttributeData TypeLengthPrimary KeyRef. TablePerformanceIDIntegerYesPerformanceNameVarchar100TicketPriceIDIntegerTicketPriceArtistIDIntegerArtistTable TicketPriceAttributeData TypeLengthPrimary KeyRef. TableTicketPriceIDIntegerYesPerformanceIDIntegerPerformanceTicketPriceNumeric(18,2)Table PerformanceScheduleAttributeData TypeLengthPrimary KeyRef. TableScheduleIDIntegerYesPerformanceIDIntegerPerformancePerformanceDateDateTable CustomerAttributeData TypeLengthPrimary KeyRef. TableCustomerIDIntegerYesNameVarchar100AddressVarchar250TelephoneVarchar20Table gross revenueAttributeData TypeLengthPrimary KeyRef. TableSalesIDIntegerYesPerformanceIDIntegerPe rformanceScheduleIDIntegerPerformanceScheduleTicketPriceIDIntegerTicketPriceCustomerIDIntegerCustomerBookingTypeBooleanTable SeatAllocationAttributeData TypeLengthPrimary KeyRef. TableSeatIDIntegerYesSalesIDIntegerSalesSeatNoFromIntegerSeatNoToIntegerTask 7 Object-Orient Approaches vs. Standard ApproachesStandard ApproachesStandard approach includes many variations based on techniques used to develop information system with structured and modular programming. Standard analytic thinking and design techniques are a software engineering methodology for describing systems as a hierarchy of functions. Below are the characteristics of Standard 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 systems undersurface be used to show logical and physicalIs a quantum lea p forward to other techniques at the time, I.e. monolithic descriptions with globs of text.Context Diagram