'Airline Customer Relationship Management Tool\r'

'* Airline Customer Relationship counsel Tool INDEX 1. Introduction 2. System abbreviation a. Existing System b. proposed System 3. Feasibility radical a. Technical Feasibility b. Operational Feasibility c. efficient Feasibility 4. System Requirement Specification put down a. Overview b. Modules Description c. Process Flow d. SDLC Methodology e. packet Requirements f. Hardw ar Requirements 5. System Design a. DFD b. E-R diagram c. UML d. entropy Dictionary 6. Technology Description 7. Coding 8. testing & Debugging Techniques 9. Output Screens 10. Reports 11. Future Enhancements 2. Conclusion 13. Bibliography * induction The Main Objective of this System is to design a outline to accommodate the needs of guests. This application helps a guest to know somewhat the passage’s information and washbasin reserve seats land up-to-end the globe irrespective of the location. This is a computerized carcass to build up seats reservations, keep ticket bookings and entrance feeibility enlarge up-to-date. This web based administration domiciliates all flight’s information, availability of flights, availability of seats. It contains information about pilots, air hostess and airdrome information.It also provides cartridge holder schedules for different flights and source, destination details. It provides live of tickets and enquiry details. Features of the take to Reduces the complexity present in the manual administration and saves cartridge holder. 1. Users can access the compulsory data easily. 2. It maintains straight information. 3. Provides instantaneous updated information to all substance abusers. 4. Communication is tight and sink and avoids misunderstandings. It is a computerized outline to make board reservations and keep room bookings and availability of details up-to-dateSystem compend Purpose of the System This web based agreement provides all flight’s information, availability of flights, availability of seats. It contains information about pilots, air hostess and airport information. It also provides time schedules for different flights and source, destination details. It provides cost of tickets and enquiry details. Existing System * This administration doesn’t provide register the multiple Flights * This dodge doesn’t provide online help to the public Proposed SystemThe instruction of this fresh establishment contains the spare-time activity activities, which try to develop online application by keeping the entire care for in the view of database integration approach. * This system provide online help to the public * This system provide agents accommodation and book the bulk tickets * This system provide belatedly running flights information before 3 hours * Online view of the tickets must be provided in real time Feasibility Study TECHNICAL FEASIBILITY Evaluating the technological foul feasibility is the trickiest part of a feasibility study.This is because, at this point in time, not too many a(prenominal) detailed design of the system, making it difficult to access issues care performance, costs on (on account of the mannequin of technology to be deployed) etc. A outlet of issues rescue to be considered while doing a technical analysis. i) Understand the different technologies gnarled in the proposed system Before commencing the get a line, we have to be very clear about what are the technologies that are to be required for the development of the raw system. i) Find out whether the fundamental law currently possesses the required technologies * Is the required technology open with the organization? * If so is the capacity sufficient? For vitrine †â€Å"Will the current printer be qualified to handle the new reports and forms required for the new system? ” OPERATIONAL FEASIBILITY Proposed stick outs are beneficial sole(prenominal) if they can be turned into information systems that depart meet the o rganizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed.Are in that location major barriers to Implementation? Here are questions that will help test the operational feasibility of a suggest: * Is there sufficient support for the project from perplexity from users? If the current system is well wish and used to the extent that persons will not be adequate to(p) to see reasons for transfer, there may be resistance. * Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a a lot operational and useful systems. * Have the user been involved in the planning and development of the project? azoic involvement subverts the chances of resistance to the system and in * ordinary and increases the likelihood of successful project. Since the proposed system was to help reduce the hardships encountered. In the existing manual system, t he new system was considered to be operational feasible. ECONOMICAL FEASIBILITY economic feasibility attempts 2 weigh the costs of development and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.A simple economic analysis which gives the actual comparison of costs and benefits are much more(prenominal)(prenominal) meaningful in this case. In addition, this proves to be a useful point of author to compare actual costs as the project circulatees. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, forward motion in intersection quality dampen determination making timeliness of information, expediting activities, improved accuracy of operations, cleanse documentation and record keeping, faster retrieval of information, better employee morale.System Re quirement Specification Modules Description No of Modules The system after careful analysis has been identified to be presented with the following modules: The Modules involved are 1. Admin 2. Flight 3. reserve SDLC METHDOLOGIES This document play a vital single-valued function in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. all changes made to the requirements in the future will have to go through formal change laudation process.SPIRAL MODEL was defined by Barry Boehm in his 1988 article, â€Å"A spiral Model of bundle Development and Enhancement. This puzzle was not the first model to discuss repetitious development, but it was the first model to explain wherefore the iteration models. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thu s far. Analysis and engineering efforts are utilize at each phase of the project, with an eye toward the end goal of the project.The steps for Spiral Model can be generalized as follows: * The new system requirements are defined in as much details as possible. This usually involves interviewing a matter of users representing all the external or internal users and other(prenominal) aspects of the existing system. * A preliminary design is created for the new system. * A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the last product. A second prototype is evolved by a fourfold occasion: 1. Evaluating the first prototype in terms of its strengths, weakness, and risk of exposures. 2. Defining the requirements of the second prototype. 3. Planning an design the second prototype. 4. Constructing and testing the second prototype. * At the customer option, t he entire project can be aborted if the risk is deemed too great. Risk constituents might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product. *The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above. * The preceding steps are iterated until the customer is satisfied that the subtile prototype represents the final product desired. * The final system is constructed, based on the refined prototype. * The final system is thoroughly evaluated and tested. Routine precaution is carried on a continuing basis to stop large scale failures and to minimize down time. The following diagram shows how a spiral model acts like:Fig 1. 0-Spiral Model ADVANTAGES * Estimates(i. e. budget, schedule etc . ) become more relistic as work progresses, because important issues discoved earlier. * It is more able to cope with the changes that are software development loosely entails. * Software engineers can get their hands in and start woring on the core of a project earlier. SOFTWARE REQUIREMENT AND HARDWARE REQUIREMENT Software Requirements Operating System:Windows XP Professional or Above. Languages:C#. NET, ASP. NET Data Base:SQL boniface. Web Server: IIS 5. 0 OR Above. Hardware Requirements Processor:Pentium IV Hard Disk:40GB RAM:512MB or more\r\n'