System Analysis Cinema Booking Information Technology Essay

scheme abbreviation Cinema participation Information Technology EssayWaterfall Life Cycle Waterfall life motorcycle is the just about familiar and classic life cycle mock up. It is sometimes referred to as the classic life cycle or the linear sequential prototype. It the simplest type of life cycle and very(prenominal) easy to white plague and understand. In the falls life cycle, each phase needs to be completed before the next phase bank discount start. Each phase is separate and does theres no overlapping. prerequisites Analysis corpse DesignImplementation Unit examinationIntegration System runingOperation MaintenancePhasesRequirement Analysis Requirements be collected from end- exploiter consultations and thus analyzed. A requirement Specification Document is created which guides the next phases of the model.System Design System purport is prompt by studying the requirements specification from the 1st phase. The ironware requirements are specified in this po int in time and a picture of the overall scheme architecture is produced.Implementation Unit Testing In this phase, the work is split up in small units actual coding starts. Testing makes sure that the software product successfully meets the required specification and that every errors are identified.Integration System Testing All units are integrated and tested to ensure that the governing body meets the requirements. At the end of this do, the software is delivered to the guest.Operation Maintenance This is the longest phase in the model. The software is updated in this phase to correct any errors, make the software to a greater extent efficient and to meet the ever-changing needs of the customers.AdvantagesIt is a linear sequential modelVery easy simple to implement thusly well accommodate for small projectsIt is also cheaperMinimal amount of resources are required to implement this modelTesting is done after each phase to ensure the project is on the right alleyEasi ly manageable beca expend model is rigid each phase has certain deliverables a review solve after a phase is over, which makes understanding of the designing procedure simpler.DisadvantagesHigh risk uncertainty.Not suited for long projects where the requirements may variegate.The operative software is only produced late during the life cycle.It is difficult to estimate the price and time for each stage.No back tracking possible if an error occurred in the earlier stages of the cycle, it affectation be corrected for that batch.V-Shaped nonplus The V-Shaped Model is very similar to the Waterfall model life cycle, nonwithstanding interrogatory is done upfront instead of later in the life cycle like in Waterfall model. Like Waterfall model, V-Shaped Model is also a sequential cycle and a bran- refreshing phase is only started after the completion of the previous phase. Each study stage is matched with its respective testing stage Requirements System Testing, upper-level D esign Integration Testing, subordinate Design Unit Testing. V-Shaped model is very reclaimable for dodges which require high reliability.System TestingRequirementsIntegration TestingHigh- train DesignLow-Level DesignUnit TestingImplementationPhasesRequirements Commences the life cycle form test plan is created.High-Level Design Focuses on design system architecture integration tests are created.Low-Level Design software package components are designed unit tests are created.Implementation Coding takes place in this phase.AdvantagesIts easy to use but not as easy as the waterfall model.More chance of success than the waterfall model receivable to the early testings.Project moves promptly to the implementation stage.Useful for small projects considering the requirements are tardily understood get alongn upfront.DisadvantagesBugs in the final examination stage are very personifyly to fix.Total victimisation time of v-shaped model is more than the waterfall model.Does no t contain any risk analysis activities philippic Prototyping model Very useful in situations the users needs and requirements are not clear. The of import objective of this model is to validate or drive the system requirements. This model is experience to reduce the requirement risks. This prototype is developed and accordingly delivered to the user for experiments and then it is discarded, hence throw away prototype and it should not be considered as a final system.AdvantagesRequirement risks are fewerIf delivered model does not meet the users needs, then it piece of ass be discarded and juvenile models tail end be developed.DisadvantagesCan be undocumentedDevelopers may be push to deliver the throw away prototype as the final system, which is not recommended.System induceing may be degraded due to the changes made during the software development process.Evolutionary Prototyping model In evolutionary prototyping, the initial prototype is developed and it is then refined th rough number of stages to final stage. The main objective is to deliver the working system to the user. Verification is not possible because there is no specification.Requirement gathering,RefinementQuick DesignBuilding PrototypeRefine RequirementEnd-User EvaluationEnd harvest-festivalRefinePrototypeAdvantagesSystem development involves the userWorking system is delivered fastA more useful system book notice be deliveredDisdvantagesTime required to complete project is unknown.May deem problems Management, Maintenance and Verification problems.Incremental model The incremental model is similar to the Waterfall life cycle model, but there are multiple development cycles here, which makes it a multi-waterfall cycle. It has an iterative approach (repeating), and each looping passes through each of the phases. A working version of software can be produced during the first iteration, which heart and soul a functioning software is usable early in the cycle.1st IncrementAnalysisTestCod eDesign1st Increment rescue2nd Increment2nd Increment deliveryAnalysisTestCodeDesignnth IncrementTestCodeDesignAnalysisnth Increment deliveryTimeAdvantagesWorking bundle can be developed quickly early during the life cycle.Its less costly to change requirements therefore Flexible.Easier to test and fix errorsEnd-users get to agnize working software early in the software development life cycle.DisadvantagesThe total development cost is higherWell defined project planning is required to distribute the work properly.Spiral Model Also known as Spiral lifecycle model. This model combines the features of the waterfall model and the prototyping model. The Spiral Model is approximately commonly used in large, complicated and expensive projects and constant review is needed to stay on target. The main area in which Spiral model is used is Game development due to the always changing goals size of the large project.Cumulative CostProgress1. Determine Objectives, Alternatives, Constraint s2. Evaluate alternatives.Identify, and resolve risks. analyse3. Development Tests4. Plan next PhasesAdvantagesImportant issues can be discovered earlier, which makes estimation of budget muniment more realistic reliable.Good amount of risk analysisReally good for large projectsSoftware can be conceived early in the life cycle.Flexible allows for multiple iterations.DisadvantagesNot satisfactory for smaller projectsSuccess of the project depends on the risk analysisCostlyRequires knowledgeable lag for risk analysis.2. naming of the Functions and Purpose of a Systems Life Cycle.The systems life cycle is a series of well-defined phases in the development of systems. It is very important that a project should meet the required specification, should be within budget and delivered on time. Large system developments can take a long time to be developed and can be very costly too therefore most organisations use the systems life cycle (stages) to develop systems because it saves t ime isnt as costly.ProgrammingMaintenanceInstallationDesignfeasibleness StudyAnalysis1. Feasibility studyDifferent solutions are examined in this stage. First step of this stage is to discover the funds available and then compare with the benefits of the company, in view of their requirements because sometimes in order to arrive at final decision a trade-off (give and take) has to be accepted e.g. less functionality for less cash. there are iii different options that a company could chooseOptionsBenefitCostPerformanceCompany does not change any intimacyNo interference to the business. Least costSystem remains outdated. Less efficientN/ACompany updates half of the systemLeast efficient parts are redesigned to improve performance patch best parts of the system are not changedModerate, light training for stave40% improveComplete upgradeMore profitableHigh, New equipments, Upgraded Software, learn for staff.80% improved (over the old system)2. investigating and AnalysisInvestigati onFirst step of this stage is to investigate the old system and problem it is causing.There are different ways to find out the problemsQuestionnaires and InterviewsObserving people using the old systemFollowing the knowledge from the point it enters the system till the point of output.Taking the cause of the problemThese locomote should lead toward the true cause of the problemAnalysisThe next part is to analyze how the existing system whole shebang how information is handled and how people interact with it.To Analyze, different methods are used e.g.System diagramsThis shows the dealings mingled with different systems in the company or outside. System diagram shows how they interact and what depends on what and so on.selective information Flow platThis shows the movement through the system, how the system deals with the information, how information flows through the system, how dose it connect and undo and what the outputs are.Process DiagramThis shows how people interact with the system for example an employee makes a claim, first it impart go to manager who go forth counter-sign the claim it will then go to account manager who authorizes payment and so on.3. DesignThis stage defines the system in greater detail and the best way to start this stage is to write down exact flesh out of the bare-ass system e.g.The entropy InputsThe info OutputsScreen LayoutsDocuments that are printed outProcedure of the data that flows through the systemThe structure of any files that store dataHow information is accessedAnd so onThe testing procedure comes after the system has been built. In my opinion it is really useful to build a test procedure before starting to build a system because, if you know how the system will be tested, it will lead you towards a better design.PrototypePrototype is something that allows you to build a program without having to worry about the detail, it is to confirm that design is likely to work. The master document created in this s tage is called System Requirement Document.4. ProgrammingThis stage takes the design forward and put it into practice and this stage take place when the lymph gland has agree on what needs to be done (Requirement Specification) and the Analyst has distinctly described what needs to be done(System Requirement Document).There are several terms involved in this stage so it is reasonable to break down the System Requirement Document into sections that each can develop.At this stage following things may take placeThe software developers write codeThe hardware people develop equipmentThe testing squad develops test plansThe user-testing groups follow the test plans and check the system works as expected5. InstallationNow the system is developed and tested and it is working correctly and doing what client wanted.The key events in this stage are data conversion entropy stored on the old system are now converted into the correct format for the revolutionary system.System Change Over ex change off the old system and turn on the new system, which is not as simple as it sound.AlternativesRun the old and new system in parallel for a time node does not care what your IT system is made up of, they are only concerned about their order. One method is to run the old system along the new one, then in the quiet time the new system store the old system data and is then fully loaded and ready to go.TrainingTraining is the vital part of this stage, staff training must take place.Staff needs to be shown how to use the new systemHow to access help when they run into difficultiesMember of a development team should be available on callA user manual should be available for staff6. MaintenanceThe new system is running smoothly and it will need to be looked after so maintenance stage takes care of the following that can take place chores are cleared as they occurTweaks to the system are applied to improve performanceThe system has to be moved due to office movementData is backed up an d kept safeEquipment are replace as required essentially this stage never ends until the new system becomes old and is then switch with new system.3. Undertake a User Needs Analysis (UNA) for your system. organisation USED CINEMA BOOKING SYSTEMUNA is the first stage in the system development process. UNA in system developing includes task that is demanded by the user for new or different system. Requirements must be actionable, measurable, and testable and must be related to user needs.The best way to undertake UNA in my view is to have a workshop with the users who will use the new system. This will give me one clear idea of what the new system must do. When working on developing the new system under the weather have a better idea of what users wants from the new system, keeping every users requirements in mind.So Ill set up a workshop, in which Ill ask users what they want from the new system. I will document their requirements as I go along. Basically Ill ask different questions from the users and then the users themselves will work out what kind of a new system they want.Questions that Ill ask usersWhat the new system should do?Do you want it to be networked with another(prenominal) computers?How long the information needs to be saved?Should staff login when using the system?Anything needs to be printing?What information needs to be print out? defrayal procedure/ types of cards?Discounts school-age childInputs, process and outputs lucre booking/ serial number only for internet bookingThis is how Ill design the system, keeping in view the users requirements. It will be an advanced system which will be preferably reliable and it will be easy for the users to use this system.System RequirementsInputsSerial number only for Internet bookingName retributionAge/ discountName of the photographic filmDateProcess home NumberDiscount reductionOutputMovie shred for customerInformation saved in the systemThis program is supposed to save the information of the cus tomer and print out a film ticket containing the required information.Print out of the ticketNameAgepaymentDiscountPayment after discountTheater NumberMovies nameDateSystem will show this information on the slate.4. Produce a Systems Context Diagram for your system.User/ StaffNew systemCustomerInfo givenInput filledData saved tatterProcessCalculate discount if applied and check for seats in theatreSaved in waiter for 3 age and is access able by any member of staff controls the shred just the ticket givenCheck movie and timeLoginAdministrator LoginUpdate Movie DataDelete Old DataUpdates the systemThis Diagram explains the program I am building for the Cinema. Circles in the diagram mean the first thing is done by Administrator, User/ Staff and the customer.ExplanationAdministrator must update the system by inserting new movies and deleting old movies.User/ Staff is the person who can access the system by login in and takes the details (info given) of the customer. User/ Staff th en enter the details (input filled) in the system.News System will process the input and process it, calculate discount if applied and check for seats available in theatre. Itll then give two outputs Data Saved and Ticket.Data Saved meaning the data will be saved in a server for three days and is access able by any member for staff but the saved data cannot be changed after the Ticket is printed out.Ticket will be printed out and is going to be checked by the staff. Staff will give the ticket to the customer.5. Produce a Level 1 Current Physical Data Flow Diagram for your system.D1 User/ Staff/ counterEnquiresDeposits and WithdrawalsProcess customer dataTickets recheckData storeSystem moneyCustomerCustomer details/ dataPrintTicketDetails are checkedTicket handed to the customerResource FlowData FlowOutside dataProcessD2In this Physical Data flow diagram customer, who is outside data, goes to the counter to purchase a ticket for the movie. foresee/ staff take his query and process i t, system then stores the data and process a ticket, which is given to the customer.6. Produce a Level 1 Required Logical DFD for your system.AdminUser/ StaffCustomerSystemProcessData StoredTicketUpdates the SystemCustomer details/ dataTicketInput customer detail/ dataCalculates discounts Theatre No.Stores in a serverPrint outTicket details are checked by user/ staffData FlowSource of DataIn this Diagram Admin is updating the data for the system and user is taking the detail/ data of the customer and entering it in the system to process a Ticket for customer.7. Decompose one of the processes to a Level 2 Required Logical Data Flow Diagram for your system.AdminSystemProcessData StoredUpdates the SystemAdding new movie dataDeleting old movie dataStores admin new dataStores customer dataMovie is suitable for customer (age)Theatre availabilityCalculate discountsStore data in serverAuto deletes 3 days old customer dataAccess to old dataIn this Diagram Admin is updating the data for the system and system is processing customer details against admin updated data and it is then stored in a server for three days.8. Construct a Logical Data Structure for the system you are producing.CustomerStaff/ counterTicketEnquiresTicketCustomer will seek staff on counter for any enquiry or to purchase a movie ticket add service to customerStaff will take customer details from customer for a movie ticketTo process a Ticket, staff will have to enter customer details in the system for a movie ticketTicket is handed to the customer after staff checks for any errors9. With the aid of your Logical Data Structure, produce an Entity/Event Matrix for your database system.CustomerPurchasing a ticket for a movieEnquiryStaff/ CounterStaff/ CounterSolve the issueYesNoJob doneAdminEnter customer details in the systemSystem processTicketData storedStaff (checks it)Customer (takes ticket)Server10. Describe the Required Physical Data Model.Customer details/ dataAdminAdmin loginUpdate new movie dat aDelete old movie dataProblem solvingStaffCustomer serviceSystem operatorStaff loginhandle customer detailsTicketCashierCustomerEnquiresTicket purchaserUpdates the SystemInput customer detail/ dataSystemCustomer internet serial no.Customer nameCustomer agePayment methodDiscountAmount paying(a)Name of the movieTheatre numberDateStores admin updated dataAccess to old dataCheck for any errors on the ticketProcessMovie is suitable for the customer (age)Discount reductionTheatre numberDraft ticketPrint outData storedStored in serverAccess ableAuto delete 3 days old dataTicketCustomer nameCustomer agePayment methodDiscountAmount paidMovies nameTheatre numberDateAdmin updates the system and solve problemsStaff handles the customers and input the customers details in the systemSystem processes the data and check for availabilitiesData is stored for 3 daysTicket is issued for customer as a receipt