Created by:- Sunil Thakur

Economical Feasibility:Economical Feasibility:

The cost of acquiring the proposed system is not too high. The agency already has the suitable hardware with them. Even the software is already available with them. So it creates no extra burden on agency. System is developed in Visual Basic and in MS Access which are both advances in feature.

Operational feasibility:Operational feasibility:

The main objective here is to determine whether the system will work after it is developed and installed. A proper investigation was done in this regard and as a result, the following conclusions were derived:

* There was sufficient support from the management and the personnel involved.* As it automates the automobile agency system completely, so the system becomes more efficient.* The persons involved in the current working of the system were met and discussions were held with them to evolve a system with which they had good support and participation.* The repetitive work of the currently manual system is eliminated.

Technical feasibility:Technical feasibility:

The necessary technologies that are required to implement the proposed system are available easily in the software market. The main hardware equipments such as computers, printers, etc. are easily available. The software of VB is easily available in the market. VB is a tool that allows us to develop Windows based applications. So user feels very comfortable with it. Microsoft Access is a powerful program to create and manage our databases. It has many built in features to assist us in constructing and viewing our information. Access is much more involved and is a more genuine database application than other programs such as Microsoft Works.

Since visual basic is an event driven programming we used this tool to optimize our project.

We used the toolbox containing the object and controls, which we will add to the form to create the user interface for your project. Controls like command buttons, text boxes, radio buttons, check boxes, Adodc controls, data combo, data grid, frames, labels, image control, drive list box are present on the toolbox, also known as OCX files. He Form Designer window contains the form on which the controls and objects are going to be placed. Your application can have more than one form.

We used Access as backend to build our simple Payroll System. All tables are designed in Access for our project.

The database needs to be designed in an appropriate manner. This includes

The use of "Primary Keys" in each table Making sure that you use "Auto Numbers" where appropriate and normal numbers where you what to enter the information

manually Using the correct field type.

Zero level DFDZero level DFD

Level 1 DFDLevel 1 DFD

1.LOGIN DATABASE

2. TICKET CANCEL

3. FLIGHT INFORMATION

4. PNR NO.DETAILS

5. RESERVATION

6.SEATS AVAILIBLITY

1. LOGIN FORM

2. WELCOME FORM

3. MAIN FORM

4. DISPLAY INFORMATION FORM

5.FLIGHT INFORMATION FORM

6. TICKET STATUS FORM

7.RESEVATION SLIP FORM

8. REFUND SLIP

9.TICKET INFORMATION FORM

10. NEW RESERVATION FORM

11.DELETE ACCOUNT FORM

1. FLIGHT INFORMATION

4.RESERVATION REPORT

TESTING

The testing of various modules is done at various stages of development process. The golden rule to be kept in mind while testing is that the testing should be done with a view to identifying the ways to in which system is likely to fail.

NEED FOR TESTING

Testing is vital to the success of the system. Testing has the logical assumption that all the part of the system is correct and the goal is successfully achieved.

LEVELS OF TESTING

1. Unit Testing2. Integration testing3. System testing4. System acceptances

USERS NEEDSACCEPTANCE TESTING

REQUIREMENT SYSTEM

DESIGNINTEGRATION TESTING

CODE UNIT

These different levels of testing attempt to detect types of faults. The relation of faults introduced in different phases and different levels of testing are shown here.

1. UNIT TESTING

For my project I performed this testing by running each form separately and encountered many errors. Most of which were type mismatch, data source not found, linking errors, end of file encountered, problem with loops etc.

2. INTEGRATION TESTING

The second level of testing is often called integration testing. In this, many testing modes are combined into sub system, which are tested .The goes here is to see if the modules can be integrated properly, the emphasis being on the testing interface between modules. During this also I encountered a number of problem ranging from the similar type of problems as above to new kind of problems mainly updating.

3. SYSTEM TESTING

The next level of testing is the system testing. Here the entire software system is tested. The reference and the goal are to see if the software meets its requirement. This is essentially a validation exercise.

This level of testing is performed with realistic data to demonstrate that software is working satisfactory. Testing is on external behavior of the system. The internal logic is not emphasized.

4.ACCEPTANCE TESTING