Online Ticket Booking System Information Technology Essay

On job rag find go forth brass training engineering science EssayApart from the efforts of me, the success of whatever assignment depends largely on the encouragement and guidelines of m any(pre zero(prenominal)inal) others. I put peerless everyplace this opportunity to express my gratitude to the people who have been instrumental in the flourishing completion of this assignment.I would like to take my greatest appreciation to Lecturer, Ms. Nayeema Rahman. I cant say thank you enough for his tremendous support and help. I feel motivated and encouraged every fourth dimension I pay heed his meeting. Without his encouragement and guidance this assignment would non have materialized.AbstractThe draw a bead on of the online tatter booking musical arrangement is to provide a nonher way for purchase cinema tickets in advance. It is an automatic corpse. This paper presents a formal call of the Object Oriented analysis and Design, we leave behind illustrate our constit ution by providing utilisation slipperiness plats with Specifications, Activity diagrams, Class Diagrams, Sequence Diagrams, relegate Machines and discourse Diagrams on the functionalities of the system, overly we will provide some process definition and selective entropy dictionary.The goals of our system atomic number 18 drop off serveance detailsRecord node detailsRecord tickets sold write ticketsPrint aim labels for earpiece booking projection 1 Functional Modelling denomination of thespians example casefulsAnalyzing the existing system we figured out that, in that location argon two main scopes to be covered in the system. The scopes are transaction Planning and tag reserve. We used the below table to identify the p situationtarians and the using up facts for the system. drug userRole discourse matterTheatre Manager doing planningDefine the type of the performance and name it. achievement computer programmingDefine run across and time of the perfor mance. artisan bookingBook an creative person for the performance. tag pricingDetermine a legal injury for the ticket. clerk lay off schedule nock the performance schedule for a particular(a) bespeak on a date. scrap seat availability validations for available sit d give birthCapture customer learningRecord customer detailsCheck ticket outlayCheck for ticket price for particular show. lot ticketRecord tickets sold.Print ticketPrint ticket for the customer.Print shout out labelPrint address label for telephone booking. drill racing shell DiagramFollowing plat shows the overall view of the tatter Booking scheme for Theatre. regard 1 Use Case Diagram (Performance Planning slate Booking)Use Case Specification flurry 1 Use Case of Performance Planning momentUC01Req. Doc referee pertainPerformance Planning lieu factorsTheatre ManagerPre-requisites exploiter should be logged in the system. objectDefining the performance type and label it.Use Case Relationships comportUC02, UC 03 accommodate tie-up evocation explanation office participant resultant role1substance abuser enters the name of the performance.2 drug user enters the type of the performance.3 organisation checks for all mandatory information entry.4 organisation connects to the database.5organization writes data into the database.6 dodging shows a verification message afterward successful database writes.AlternativesIndex player ups stiflingA 3.1Enter required selective information.A 4.1Check meshwork connectivityA 4.2Check database connectivityA 4.3Check database user roleA 5.1Theatre four-in-hand gets card of empty-handed operation. send back 2 Use Case of Performance Scheduling goUC02Req. Doc Ref callPerformance Scheduling stanceActorsTheatre ManagerPre-requisitessubstance abuser should be logged in the system.Performance planning (UC01) should be inserted into the system. finisDefine date and time of the performance.Use Case RelationshipsExtend involve sleeperGeneralizationverbal descriptionIndexActor Event1 exploiter selects the sought after performance from the system.2User enters the date of the performance.3User enters the time of the performance.4 formation 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 interlocking connectivityA 5.2Check database connectivityA 5.3Check database user roleA 6.1Theatre winr gets notification of unsuccessful operation. skirt 3 Use Case of operative BookingNumberUC03Req. Doc Ref gain offArtist 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 RelationshipsExtendIncludeAssociationGeneralizationDescriptionIndexActor 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. add-in 5 Use Case of memorial CheckingNumberUC04Req. Doc Ref squallSchedule CheckingStatusActorsClerkPre-requisitesUser should be logged in the system.Performance programing (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.3System allows the user to perform the next 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 customer 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 Ca se 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 shred 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 form the system.2System shows the defined pricing for the ticke t.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 Case of Printing TicketNumberUC09Req. Doc RefNamePrinting Tick etStatusActorsClerkPre-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 command for the sold ticket.AlternativesIndexActor EventA 1.1 printer not found notification will be given to the user.Table 11 Use Case of Checking Ticket Booking fictitious characterNumberUC10Req. 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 Address 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 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. foretell 2 Activity Diagram (Performance Planning Ticket Booking)Task 2 Structural ModellingClass Diagram (attributes operations)The following diagram depicts the relationships between the classes for Ticket Booking System along with the attributes and the operations.Figure 3 Class Diagram (Performance Planning Ticket Booking)Task 3 behavioral ModellingSequence DiagramThe following diagram is a season diagram for buying ticket. There are few things I need to state, that this is unsloped one of the periods of buying ticket. There could be more selection sequence for buying ticket. For example, we can choice a performance onwards buying ticket. But the overall structures of all buying ticket sequence are similar, so, others sequence will not be shown.Figure 4 Sequence Diagram (Create Performance)Figure 5 Sequence Diagram (Schedule Performance)Figure 6 Sequence Diagram (Set price)Figure 7 Sequence Diagram (Sell tickets)State Machine Diagram downstairs diagram is used to give an abstract description of the doings of the ticket booking system. This behaviour is canvas 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 by dint of the system.Figure 8 State Machine Diagram (Performance Planning Ticket Booking) converse DiagramCommunication diagram is similar to seque nce diagrams, but it provides an overview of the relationships between objects, rather than cogitate on the order of messages between objects, as the software executes.Figure 9 Communication Diagram (Performance Planning Ticket Booking)Task 4 data Protection LawIntroductionIn Bangladesh Cyber Acts are in a process to be implemented. 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 encourage 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 entropy Protection Act gives individuals the right to know what information is held about them. It provides a framework to en current that own(prenominal) information is handled properly. The Act works in two ways. Firstly, it s tates that anyone who processes personal information must keep up with eight principles, which confuse sure that personal information isFairly and lawfully processedrefined for limited 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 security systemThe second region 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. information shelter 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(a) records, such 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 ord er a data concurler to correct, block, remove or destroy personal details if they are inaccurate or manipulate expressions of opinion based on inaccurate information.Preventing processing of informationThis gist 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 merchandiseThis recalls 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 centre one can object to decisions made lonesome(prenominal) 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 check out and assess whether the data controller has breached the act.There should be a commission (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 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 draw near including working closely with the data controller to gybe the timing and scope of the audit.Comply with selective information 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 complian ce but it should mean that we are heading in the right direction.We should store only the link up information about the customer and the personnels involved with the system. And we need to befuddle 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 sustain 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 putting 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 consequently apply our li mited resources in ways that deliver the maximum military issue in terms of a sustained reduction in data protection risk. That is the risk of harm through unseasonable use of personal information.There are priorities we have to set. We need to focus most solicitude 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 sound as a short term difference. When we intervene we must do so in a way that gives us the best possible return and flirt with 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 lure data protection risk. Our effectiveness depends on them assaying and welcoming our reasonable interventions. Furthermore we have an important planetary role. Data protection risk in the Bangladesh is increasingly influenced by events worldwide.Our risk-based court i s 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 hash out 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 freedom of choice and will remember that individuals themselves ought to be best lay to make decisions about their own interests. Part of our job is to equip individuals with the familiarity and tools to enable them to make their own well-informed decisions about the use and revelation 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 legislatur e at Westminster and in the devolved administrations as well as over representative bodies and other stakeholders, to ensure privacy couthy outcomes.We will also seek to influence the legal framework that governs our own work to ensure that data protection requirements are simple, meaningful and proportional 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 lading 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 provision 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, w hich will be checked at the entranceway 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 verse with 10 digits, which will serve as copy protection.Figure 10 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 11 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 printers suitable 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-bas ed broadband Internet access to their customers or members. No complex care 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/ confidential Gateway to generate and print log-in usernames and passwords for the hot spot customers. secure 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 internal database and support up to 50 logged-in users at any time.FeaturesPrinting Method Thermal acid Line PrintingPrint Speed 80 mm/ heartbeatConnectivity RS-232 SerialCompatibility D-Link DSA-3100 Public/Private GatewaySpecificationmanufacturing businessD-LinkManufacturer Part DSA-3100PDevice TypeThermal Line Label PrinterMedia HandlingMedia TypeReceipt Paper gook Media Size2.2Max Printin g Width1.9Roll Maximum Outer Diameter3.3 add up Capacity1 RollConnectivityInterfaces1 x RS-232 Serialinclude Cables1 x Serial CablePower RequirementsPower impartExternal, 3.5 V DCDimensions(H X W X D)Unit4.6 x 3.8 x 6.3WeightUnit0.9 lbsPrice $375Figure 12 D-Link DSA-3100P Ticket PrinterTask 6 Database DesignDatabase DesignFigure 13 Database Design (Performance Planning Ticket Booking)Data DictionaryTable ArtistAttributeData Type distancePrimary come uponRef. TableArtistIDwhole numberYesArtistNameVarchar100Table PerformanceAttributeData Type distancePrimary happen uponRef. TablePerformanceIDwhole numberYesPerformanceNameVarchar100TicketPriceID integerTicketPriceArtistIDIntegerArtistTable TicketPriceAttributeData TypeLengthPrimary KeyRef. TableTicketPriceIDIntegerYesPerformanceIDIntegerPerformanceTicketPrice mathematical(18,2)Table PerformanceScheduleAttributeData TypeLengthPrimary KeyRef. TableScheduleIDIntegerYesPerformanceIDIntegerPerformancePerformanceDateDateTable CustomerAtt ributeData 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 develop information system with structured 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 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 systemsCan be used to show logical and physicalIs a quantum leap anterior to other techniques at the time, I.e. monolithic descriptions with globs of