Airline Customer Relationship Management Tool

* escape cock of stairs path Customer Relationship Management Tool INDEX 1. Introduction 2. body psychoanalysis a. Existing arrangement b. proposed dust 3. Feasibility Report a. technical Feasibility b. Operational Feasibility c. scotchal Feasibility 4. System need Specification Document a. Overview b. Modules Description c. Process Flow d. SDLC Methodology e. computer software Requirements f. Hardware Requirements 5. System Design a. DFD b. E-R diagram c. UML d. entropy Dictionary 6. engine elbow room Description 7. Coding 8. Testing & Debugging Techniques 9. Output Screens 10. Reports 11. Future Enhancements 2. Conclusion 13. Bibliography * institution The Main Objective of this System is to design a clay to throw the needs of guests. This application helpers a customer to know about the flights information and smoke reserve seats throughout the ground irrespective of the location. This is a computerized strategy to make seats reservations, keep tatter bookin gs and availability details up-to-date. This web based system provides correctly flights information, availability of flights, availability of seats. It contains information about pilots, air stewardess and airport information.It as good provides time schedules for diametrical flights and source, destination details. It provides cost of tickets and query details. Features of the jutting Reduces the complexity present in the manual of arms system and saves time. 1. Users can access the take data easily. 2. It maintains accurate information. 3. Provides instantaneous updated information to all users. 4. Communication is fast and clear and avoids misunderstandings. It is a computerized system to make room reservations and keep room bookings and availability of details up-to-dateSystem Analysis Purpose of the System This web based system provides all flights information, availability of flights, availability of seats. It contains information about pilots, air hostess and airpo rt information. It also provides time schedules for different flights and source, destination details. It provides cost of tickets and enquiry details. Existing System * This system doesnt provide register the multiple Flights * This system doesnt provide online help to the public Proposed SystemThe nurture of this fresh system contains the chase activities, which try to develop on-line application by keeping the entire process in the view of database integration approach. * This system provide online help to the public * This system provide agents registration and book the bulk tickets * This system provide late running flights information before 3 hours * Online experimental condition of the tickets must be provided in real time Feasibility sketch TECHNICAL FEASIBILITY Evaluating the technical feasibility is the trickiest part of a feasibility study.This is because, at this point in time, not too many enlarge design of the system, do it difficult to access issues like perfo rmance, costs on (on account of the kind of technology to be deployed) etc. A consequence of issues hold back to be considered while doing a technical psychoanalysis. i) Understand the different technologies convolute in the proposed system Before commencing the assure, we have to be rattling clear about what are the technologies that are to be required for the development of the radically system. i) Find out whether the organization currently possesses the required technologies * Is the required technology avail sufficient with the organization? * If so is the capacity sufficient? For antecedent Will the current printer be able to handle the new reports and forms required for the new system? OPERATIONAL FEASIBILITY Proposed projects are dependable only if they can be turned into information systems that go forth hear the organizations operating requirements. Simply stated, this test of feasibility asks if the system will written report when it is developed and instal led.Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project * Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for salmagundi, there may be resistance. * Are the current phone line methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more(prenominal) operational and multipurpose systems. * Have the user been gnarly in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in * General and increases the likeliness of successful project. Since the proposed system was to help reduce the hardships encountered. In the animated manual system, the new system was considered to be operational feasible. ECONOMICAL FEASIBILITY Economic feasibility attempts 2 weigh the costs of developing a nd implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the outstrip management the economic justification for the new system.A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of quote to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, quicker retrieval of information, better employee morale.System Requirement Specification Modules Description No of Modules The system after careful analysis has been identified to be presented with the sideline modules The Modules involved are 1. Admi n 2. Flight 3. Reservation SDLC METHDOLOGIES This document play a merry role in the development of life cycle (SDLC) as it describes the do it requirement of the system. It means for use by developers and will be the staple during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.SPIRAL MODEL was be by Barry Boehm in his 1988 article, A spiral object lesson of computer software development and Enhancement. This model was not the starting time model to discuss iterative development, scarcely it was the first model to explain why the iteration models. As before 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 thus far. Analysis and engineering efforts are applied at each phase of the project, with an centre toward the end goal of the project.The steps for Spiral Model can be generalized as follows * The n ew system requirements are defined in as much details as possible. This usually involves interviewing a enumerate of users representing all the external or internal users and other 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 utmost product. A second prototype is evolved by a fourfold procedure 1. Evaluating the first prototype in terms of its strengths, weakness, and risks. 2. Defining the requirements of the second prototype. 3. Planning an designing the second prototype. 4. Constructing and testing the second prototype. * At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customers judgment, resu lt in a less-than-satisfactory final product. *The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, some other prototype is developed from it according to the fourfold procedure outlined above. * The previous steps are iterated until the customer is satisfied that the refined 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 maintenance is carried on a act basis to prevent large scale failures and to minimize down time. The following diagram shows how a spiral model acts likeFig 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 generally entails. * software product engineers can get their hands in and start woring on the bone m arrow of a project earlier. SOFTWARE REQUIREMENT AND HARDWARE REQUIREMENT Software Requirements Operating SystemWindows XP Professional or Above. LanguagesC. NET, ASP. NET Data BaseSQL Server. Web Server IIS 5. 0 OR Above. Hardware Requirements processorPentium IV Hard Disk40GB RAM512MB or more