Airline Customer Relationship Management Tool

* Airline Customer Relationship Management Tool INDEX 1. Introduction 2. System Analysis a. Existing System b. proposed System 3. Feasibility Report a. Technical Feasibility b. Operational Feasibility c. Economical Feasibility 4. System Requirement Specification Document a. Overview b. Modules Description c. Process Flow d. SDLC Methodology e. Software Requirements f. Hardware Requirements 5. System Design a. DFD b. E-R diagram c. UML d. Data Dictionary 6. Technology Description 7. Coding 8. Testing & Debugging Techniques 9. Output Screens 10. Reports 11. Future Enhancements 2. Conclusion 13. Bibliography * INTRODUCTION The Main Objective of this System is to design a system to accommodate the needs of customers. This application helps a customer to know about the flight’s information and can reserve seats throughout the globe irrespective of the location. This is a computerized system to make seats reservations, keep ticket bookings and availability details up-to-date. This web based system 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. Features of the project Reduces the complexity present in the manual system and saves time. 1. Users can access the required 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-date

System Analysis Purpose of the System This web based system 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 system doesn’t provide register the multiple Flights * This system doesn’t provide online help to the public Proposed System

The development of this new system contains the following 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 status of the tickets must be provided in real time Feasibility Study 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 detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical analysis. i) Understand the different technologies involved in the proposed system Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system. i) Find out whether the organization currently possesses the required technologies * Is the required technology available with the organization? * If so is the capacity sufficient? For instance – “Will the current printer be able to handle the new reports and forms required for the new system? ” OPERATIONAL FEASIBILITY Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed.

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 change, 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 more operational and useful systems. * Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in * General and increases the likelihood of successful project. Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible. ECONOMICAL FEASIBILITY Economic feasibility attempts 2 weigh the costs of developing 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 meaningful in this case. In addition, this proves to be a useful point of reference 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, faster 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 following modules: The Modules involved are 1. Admin 2. Flight 3. Reservation SDLC METHDOLOGIES This document play a vital role 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. Any changes made to the requirements in the future will have to go through formal change approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why 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 thus far. Analysis and engineering efforts are applied 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 number 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 final 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 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 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 continuing basis to prevent 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 generally 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 Server. Web Server: IIS 5. 0 OR Above. Hardware Requirements Processor:Pentium IV Hard Disk:40GB RAM:512MB or more