Air Report

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013
BCA VI
1. INTRODUCTION TO ONLINE AIR TICKET BOOKING
ABSTRACT:
The main aim of the project is to design innovative software, which deals with the place names, flight schedule, check the reservation,, issue the reservation ticket, place of the flight and customer details. The motto of the project is to simplify the Online Air Ticket booking and to render a user-friendly package.
INTRODUCTION
Online Air Ticket Booking system is to provide an option to customers to book the tickets online and to check the confirmation online. This system will help the company to sell the flight tickets online. Unless like in the previous stage people as to walk into travel agency or this company ticket counter to buy the tickets. And also to check the flight timings. This problem is over come introducing this system.
Online Air Ticket Booking is nothing but the details of the Air line system transactions can be built in this website. This is a unique concept; the idea behind this site is to provide the Ticket reservation, list out the flight and customer details on the website and view the customer details, Flight schedule details, place details, Date of journey, Date of reservation and check
G.T Institute Of Advanced Studies
BCA VI
the availability of the ticket of the customer requirement date. Already there are thousands of sites providing the details of the Airline on the online system. But none of these site able to give the information very faster. Because of technical problem or employee problems can be easy to implement in this website. This document fully and formally describes the requirements of the proposed said project system. It sets out the functional and non-functional requirements and includes a description of the user interface and documentation and training requirements.
The main modules of the project are as follows.

1. Place of the Flight 2. Flight Details 3. Flight schedule Details 4. Customer Approval 5. Check Ticket booking 6. Reservation 7. Cancellation 8. Confirmation of the Ticket
BCA VI
9. New User creation or customer sign up 10.View the records
2. SYSTEM ENVIRONMENT
ADVANTAGES
The main purpose of this software is to make ONLINE AIR TICKET BOOKING website. The intension is to reduce effort and time. Searching is customized. Absolutely user friendly software that requires minimum training. Simplified package, which requires minimum interaction. Multi-user package with database loaded in the server. To view the reports stored in the database. This software is validated and easy to port. Contains extensive instant help facility to guide the user. Only the administrator can delete/modify the details in the database.
Existing System
BCA VI
Presently this company has ticket counters in the airport. Where people as to come to book the tickets or to check the flight timings. Also there are many travel agents take the advance booking. In turn these agents will check out with the main ticket counter officials for the ticket confirmation. This is very lengthy and tedious process.
Proposed System
The proposed system will available online. So anybody who are interested in the flight timings and ticket booking they check online only.
THE FEATURES OF PROPOSED SYSTEM

The proposed system is password protected which provides security to the data. Only the authorized user can access the entire data It is user friendly with well defined screens and required inputs. It is interactive and fast in execution. Data entry is optimized using graphical controlled tools. Navigation through forms is easy. Information linking and embedding between the forms is present in the system.
BCA VI
Duplicate information cannot be entered, if done so relating message will be displayed. Maintain detailed information of the customer, supplier, staffs, and items. Large number of bulky registers can be avoided. Reduction in clerical works and better accountability. In general, it reduces time for all the transactions taking place in Inventory management.
SYSTEM ANALSIS AND DESIGN

As the name system analysis and design indicates that it deals with the analysis and designing parts, which are the two important phases of any software system designing The analysis includes steps like Identifying the user details. Identify the tables and its relationships. Writing the ER model and DFD for the better understanding of the problem. Iterate and refine.
The design includes steps like

BCA VI
Design the attributes, structures and codes. Here we have to design the tables, views, indexes and in SQL server, which is backend tool. Forms, reports and menus in Visual Basic 2005, which is the front end tool
3. Hardware and Software requirement Hardware Requirement

Processor RAM Hard disk Monitor Keyboard Mouse : : : : : : Intel Core Duo 2.0 GHz or more 1 GB or More 80GB or more 15 CRT or LCD monitor Normal or Multimedia Compatible mouse
Software Requirement
Front End Back End : : Visual Basic 6.0 MS Access 2007
6
BCA VI
Operation System
Windows XP with server pack 2 Or Windows Vista
4.
SOFTWARE
REQUIREMENT
SPECIFICATION:
An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work. It's a two-way insurance policy that assures that both the client and the organization understand the other's requirements from that perspective at a given point in time. The SRS document itself states in precise and explicit language those functions and capabilities a software system must provide, as well as states any required constraints by which the system must abide. The SRS also
BCA VI
functions as a blueprint for completing a project with as little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it. It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be. A well-designed, well-written SRS accomplishes four major goals:
It provides feedback to the customer. An SRS is the customer's assurance that the development organization understands the issues or problems to be solved and the software behavior necessary to address those problems. Therefore, the SRS should be written in natural language, in an unambiguous manner that may also include charts, tables, data flow diagrams, decision tables, and so on.
It decomposes the problem into component parts. The simple act of writing down software requirements in a well-designed format organizes information, places borders around the problem, solidifies
BCA VI
ideas, and helps break down the problem into its component parts in an orderly fashion.
It serves as an input to the design specification. As mentioned previously, the SRS serves as the parent document to subsequent documents, such as the software design specification and statement of work. Therefore, the SRS must contain sufficient detail in the functional system requirements so that a design solution can be devised.
It serves as a product validation check. The SRS also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.
SRS are typically developed during the first stages of "Requirements Development," which is the initial product development phase in which information is gathered about what requirements are needed--and not. This information-gathering stage can include onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-investment (ROI) analysis or needs analysis of the customer or client's current business environment. The actual specification, then, is written after the requirements have been gathered and analyzed.
BCA VI
The National Bureau of Standards, IEEE (Standard No: 830-1984), and the U.S Department of Defense have all proposed candidate formats for software requirements specifications. The general structure is implemented with the related software application
10
BCA VI
5. SYSTEM ANALYSIS
System Analysis is an activity that feeds information to the specification activity. It is essential that during analysis a complete and consistent set of specifications emerge for the system. For achieving this, the first major problem is to obtain the necessary information. The second problem of analysis is to organize the information obtained so the information can be effectively evaluated for completeness and consistent. The third problem is resolving the contradictions that may exist in the information from different parties. Lastly the fourth problem is avoiding internal design. The proposed system is developed keeping in mind all these steps and is designed in such a manner that it satisfies all the requirements to be called a good system design. The database designed follows 3rd level normalization and the input output forms show a better match with the backend. Thus solving the problem of collecting information and storing it. The collected information is logically related and stored in the database following the database rules that form the data dictionary for the various database operations. This removes all the possible contradictions that may arrive and results in proper functioning of the data repository. Thus having proper functioning of the modules which integrate together to work to their best.
11
BCA VI
6. SOFTWARE ENVIRONMENT
The proposed system is developed using Visual Basic as the front end and MS Access as the back end.
INTRODUCTION TO MICROSOFT VISUAL BASIC 6.0

For database management, we say our Visual Basic application acts as a front-end to the database. This means the Visual Basic application provides the interface between the user and the database. This interface allows the user to tell the database what he or she needs and allows the database to respond to the request displaying the requested information in some manner. Visual Basic and Databases requires some edition of Visual Basic 5 or Visual Basic 6. A Visual Basic application cannot directly interact with a database. There are two controls used by Visual Basic to interact with databases: the DAO (data access object) control and the ADO (ActiveX data object) control. However, that the ADO control is available only with Visual Basic 6 and utilizing ADO we have developed this software.
An observation that illustrates the power of using Visual Basic as a front-end for database management systems: Using Visual Basic, it requires less code to connect to an existing database, view all information within that database, and modify any and all information within that database, than it does to add two numbers together.
12
BCA VI
The following code is necessary to connect to the ORACLE database using ADO DB method using Visual Basic as front - end: Module Public MyCon as ADODB.Connection Dim rs as ADODB.Recordset Function Connect () Set MyCon = New ADODB.Connection MyCon.Open (Provider=MSDASQL.1; Driver={Microsoft ODBC for Oracle}; _ Uid=userid; pwd=password; server=service name) Set rs = New ADODB.Recordset Rs. Open select * from table name, MyCon, adOpenDynaset, adLockOptimistic End Function
Visual Basic is a tool that allows us to develop Windows (Graphic User Interface - GUI) applications. The applications have a user-friendly interface and will have familiar appearance to the user. Visual Basic is event-driven; meaning code remains idle until called upon to respond to some event (button pressing, menu selection, etc.,). An event processor governs Visual Basic. Nothing happens until an event is detected. Once an event is detected, the code corresponding to that event (event procedure) is executed. processor.
Program control is then returned to the event
13
BCA VI
Event
Basic Code
Basic Code
Basic Code
Some Features of Visual Basic

1 Full set of objects - you 'draw' the application. 1 Lots of icons and pictures for your use. 1 Response to mouse and keyboard actions. 1 Clipboard and printer access. 1 Full array of mathematical, string handling, and graphics functions. 1 Can handle fixed and dynamic variable and control arrays. 1 Sequential and random access files support. 1 Useful debugger and error-handling facilities. 1 Powerful database access tools. 1 1 ActiveX support. 11 Package & Deployment Wizard makes distributing your applications simple.
Visual Basic 6.0 versus Other Versions of Visual Basic

14
BCA VI
The original Visual Basic for DOS and Windows were introduced in
1991.
Visual Basic 3.0 was released in 1993. Visual Basic 4.0 released in late 1995 (added 32 bit application support). Visual Basic 5.0 released in late 1996.
New environment, supported
creation of ActiveX controls, deleted 16-bit application support.

And, some identified new features of Visual Basic 6.0: Faster compiler.

New ActiveX data control object. Allows database integration with wide variety of applications. New data report designer. New Package & Deployment Wizard.
Database Design
A database is an organized mechanism that has the
capability of storing information through which a user can retrieve stored information in an effective and efficient manner. The data is the purpose of any database and must be protected. The database design is a two level process. In the first step, user requirements are gathered together and a database is designed which will meet these requirements as clearly as possible. This step is called Information Level Design and it is taken independent of any individual DBMS.
15
BCA VI
In the second step, this Information level design is transferred into a design for the specific DBMS that will be used to implement the system in question. This step is called Physical Level Design, concerned with the characteristics of the specific DBMS that will be used. A database design runs parallel with the system design. The organization of the data in the database is aimed to achieve the following two major objectives. Data Integrity Data independence Normalization is the process of decomposing the attributes in an application, which results in a set of tables with very simple structure. The purpose of normalization is to make tables as simple as possible. Normalization is carried out in this system for the following reasons. To structure the data so that there is no repetition of data , this helps in saving. To permit simple retrieval of data in response to query and report request. To simplify the maintenance of the data through updates, insertions, deletions. To reduce the need to restructure or reorganize data which new application requirements arise.
RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):

16
BCA VI
A relational model represents the database as a collection of relations. Each relation resembles a table of values or file of records. In formal relational model terminology, a row is called a tuple, a column header is called an attribute and the table is called a relation. A relational database consists of a collection of tables, each of which is assigned a unique name. A row in a tale represents a set of related values.
RELATIONS, ATTRIBUTES:
DOMAINS
&
A table is a relation. The rows in a table are called tuples. A tuple is an ordered set of n elements. Columns are referred to as attributes. Relationships have been set between every table in the database. This ensures both Referential and Entity Relationship Integrity. A domain D is a set of atomic values. A common method of specifying a domain is to specify a data type from which the data values forming the domain are drawn. It is also useful to specify a name for the domain to help in interpreting its values. Every value in a relation is atomic, that is not decomposable.
RELATIONSHIPS:
Table relationships are established using Key. The two main keys of prime importance are Primary Key & Foreign Key. Entity Integrity and Referential Integrity Relationships can be established with these keys. Entity Integrity enforces that no Primary Key can
17
BCA VI
have null values. Referential Integrity enforces that no Primary Key can have null values. Referential Integrity for each distinct Foreign Key value, there must exist a matching Primary Key value in the same domain. Other key are Super Key and Candidate Keys.
Relationships have been set between every table in the database. This ensures both Referential and Entity
Relationship Integrity.
NORMALIZATION:
As the name implies, it denoted putting things in the normal form. The application developer via normalization tries to achieve a sensible organization of data into proper tables and columns and where names can be easily correlated to the data by the user. Normalization eliminates repeating groups at data and thereby avoids data redundancy which proves to be a great burden on the computer resources. These includes: Normalize the data. Choose proper names for the tables and columns. Choose the proper name for the data.
First Normal Form:

The First Normal Form states that the domain of an attribute must include only atomic values and that the value of any attribute in a tuple must be a single value from the domain of that attribute. In other words 1NF disallows relations within
18
BCA VI
relations or relations as attribute values within tuples. The only attribute values permitted by 1NF are single atomic or indivisible values. The first step is to put the data into First Normal Form. This can be donor by moving data into separate tables where the data is of similar type in each table. Each table is given a Primary Key or Foreign Key as per requirement of the project. In this we form new relations for each non atomic attribute or nested relation. This eliminated repeating groups of data. A relation is said to be in first normal form if only if it satisfies only. the constraints that contain the primary key
Second Normal Form:

According to Second Normal Form, For relations where primary key contains multiple attributes, no non key attribute should be functionally dependent on a part of the primary key. In this we decompose and setup a new relation for each partial key with its dependent attributes. Make sure to keep a relation with the original primary key and any attributes that are fully functionally dependent on it. This step helps in taking out data that is only dependant on apart of the key.
19
BCA VI
A relation is said to be in second normal form if and only if it satisfies all the first normal form conditions for the primary key and every non-primary key attributes of the relation is fully dependent on its primary key alone.
Third Normal Form:

According to Third Normal Form, Relation should not have a non key attribute functionally determined by another non key attribute or by a set of Non key attributes. That is, there should be no transitive dependency on the primary key. In this we decompose and set up relation that includes the non key attributes that functionally determines other non key attributes. This step is taken to get rid of anything that does not depend entirely on the Primary Key. A relation is said to be in third normal form if only if it is in second normal form and more over the non key attributes of the relation should not be depend on other non key attribute.
MS ACCESS 2003
20
BCA VI
Microsoft Access is a powerful program to create and manage your databases. It has many built in features to assist you in constructing and viewing your information. Access is much more involved and is a more genuine database application than other programs such as Microsoft Works. The keywords involved in the process are: Database File, Table, Record, Field, Data-type. Here is the Hierarchy that Microsoft Access uses in breaking down a database.
Database File:
21
BCA VI
This is your main file that encompasses the entire database and that is saved to your hard-drive or floppy disk. Example: StudentDatabase.mdb
Table: A table is a collection of data about a specific topic. There can be

multiple tables in a database.
Field: Fields are the different categories within a Table. Tables usually
contain multiple fields.
Data types: Data types are the properties of each field. A field only
has 1 data type. Fieldname) Student Last Name Data type) Text
Starting Microsoft Access
Two Ways 1. Double click on the Microsoft Access icon on the desktop.
22
BCA VI
2. Click on Start --> Programs --> Microsoft Access
Creating Databases
New,
and
Opening
Existing
23
BCA VI
The above picture gives you the option to:

Create a New Database from scratch Use the wizard to create a New Database Open an existing database
o
The white box gives you the most recent databases you have used. If you do not see the one you had created, choose the More Files option and hit OK. Otherwise choose the database you had previously used and click OK.
7. SYSTEM DESIGN SYSTEM STUDY

24
BCA VI
Initial study:
This involves the investigation of the existing system which is time consuming with the user and is insufficient depth. This also includes the collection and study of detailed information and literature regarding the complete existing procedure. The detailed initial study properly documented and the falling and problems are noted separately. The System is properly designed and proper outline of the proposed computerized system is prepared. The proposed design is brought against all the known facts and further proposals are made. Various resources including the software, hardware and manpower requirements are decided and are mentioned in the report.
User Requirements Specifications:

Actual user community participation and their requirements analysis is key to success of any new information system. To carry out this work, identification of users who will actually use the system is foremost. Users at every level were even an opportunity to define their goals, objectives and their respective information needs. In addition to this exercise a critical through investigation of present reports and query generated, were carried out to define any other additional requirements that can be useful to the others.
25
BCA VI
The findings of users and other related exercise to access particular user needs are summarized below concisely: The system must provide a graphical user interface. Redundancy must be reduced at the maximum level. Discrepancies should be avoided. Security systems must be provided.
Feasibility Study:
The prime focus of the feasibility study is evaluating the practicality of the proposed system keeping in mind a number of factors. The following factors are taken into account before deciding in favor for the new system:
Economic Feasibility:
The Proposed Resume Tracking System will save lots of paper work and Facilitate magnetic record keeping thereby reducing the costs incurred on above heads. This reduction in cost prompts the company to go for such computer-based system. Technical Feasibility: As the Saying goes, to err is human, Keeping in view the above fact, bow-a-days all organizations are automating the repetitive and monotonous works done by humans. The key process areas of current system are nicely
26
BCA VI
amenable to automation and hence the technical feasibility is proved beyond doubt.
Operational Feasibility: The day to day maintenance of the Resume details is error prone and timeconsuming. The computerization will not only increase the operational
efficiency of the staff.
Time and Resource Feasibility: This system helps the user to find in the best usage of resources keeping in track of all the resume details over a period of time, thereby reducing the decision. SYSTEM DESIGN System design provides the understandings and procedural details necessary for implementing the system recommended in the system study. Emphasis is on the translating the performance requirements into design specifications. The design phase is a transition from a user-oriented
document (System proposal) to a document oriented to the programmers or database personnel. System design goes through two phases of development: Logical Design
27
BCA VI
Physical Design A data flow diagram shows the logical flow of the system. For a system it describes the input (source), output (destination), database (data stores) and procedures (data flows) all in a format that meets the users requirement. When analysis prepares the logical system design, they specify the user needs at a level of detail that virtually determines the information flow into an out of the system and the required data resources. specifies input forms and screen layouts. The activities following logical design are the procedure followed in the physical design e.g., producing programs, software, file and a working system. Design specifications instruct the user about what the system should do. Logical and output Design: The logical design of an information system is analogous to an engineering blue print of an automobile. It shows the major features and how they are related to one another. The detailed specification for the new system was drawn on the bases of users requirement data. The outputs inputs and databases are designed in this phase. Output design is one of the most important features of the information system. When the output is not of good quality the users will be averse to
The logical design also
28
BCA VI
use the newly designed system and may not use the system. There are many types output, all of which can be either highly useful or can be critical to the users, depending on the manner and degree to which they are used. Outputs from computer system are required primarily to communicate the results of processing to user; they are also used to provide a permanent hard copy of these results for later consultation various types of outputs required can be listed as below: External outputs, whose destination is outside the organization Internal outputs, whose destination is with the organization. Operational outputs, whose use is purely within the computer department e.g., program-listing etc. Interactive outputs which involve the user is communicating directly with the computer. It is particularly important to consider human factor when designing computer outputs. End user must find outputs easy to use and useful to their jobs, without quality output, user may find the entire system unnecessary and avoid using it. The term output in any information system may apply to either printer or displayed information. During the deigning the output for this system, it was taken into consideration, whether the information to be presented in the form of query of report or to create documents etc.
29
BCA VI
Other important factors that were taken into consideration are: The End user, who will use the output. The actual usage of the planned information The information that is necessary for presentation When and how often output and their format are needed. While
designing output for project based Attendance Compilation System, the following Aspects of output designing were taken into consideration. The outputs (i.e., well formatted table outputs in the screen itself) designed are simple to read and interpret. Format of each output was another important point taken into consideration. Output media, for each output appropriate media is decided whether it will be displayed on screen or will be taken to printer or both. Other output design related specifications, i.e., how frequently the outputs will be generated, how many pages or sheets approximately it will keep up, what is its planned use and output distribution to user are also taken into account.
30
BCA VI
These were a few major designing issues, which were taken into consideration, while deciding the output specifications for the system. As
direct beneficiary of reports is the user community, they were consulted constantly at every level. Formats and screen design for various reports were identified, taking into account the user requirements. Before finalizing these were given to users for any improvement and suggestions. End users issues taken into consideration were Readability, Relevance and Acceptability.
Once all the output reports to be generated by system were identified they were given to users for their acceptance. For prototyping various outputs, final outputs models were created with dummy data, before they were finalized.
Input Design: The input design is the link that ties the information system into the users world. Input specifications describe the manner in which data enters the system for processing. Input design features can ensure the reliability of the system and produce results from accurate data, or they can result in the production of erroneous information.
31
BCA VI
Input design consist of: The input design is the link that ties the information system into the users world. Input specifications describe the manner in which data enters the system for processing. Input design features can ensure the reliability of the system and produce results from accurate data, or they can result in the production of erroneous information.
Input Design consist of Developing specifications and procedures for data preparation. Steps necessary to put data into a usable form for processing. Data entry, the actively of putting data into the computer processing.
Objectives of input design Five objectives of design input focus on: Controlling the amount of input required Avoid delay Avoiding errors in data Avoiding extra steps Keeping the process simple.
32
BCA VI
Input stages several activities have to carry out as part of the overall input process. They include some or all of the following: Data recording (i.e., collection of data) Data encapsulation (i.e., transfer of data) Data conversion (i.e., controlling the flow of data) Data validation (i.e., checking the input data) Data correction (i.e., correcting the errors) Input designs are aimed at reducing the chances of mistakes of errors. As the human beings are prone to errors there is always a possibility of occurrence of chance of errors. Adequate validation checks are incorporated to ensure error free data storage. Some of the data validation checks applied is as following: Redundancy of data is checked. It means the records of primary key do not occur twice. Primary key field of any table must not be left blank. Whenever items are coded, input code is checked for its, validly with respect to several checks. Utmost care has been taken to incorporate the validation at each stage of the system. E.g. When entering records into employee information table for employee, it is checked that whether the corresponding employee exists in the employee information table etc.
33
BCA VI
Enough messages and dialogue boxes are provided while design screen, which does guide user at the time of any errors, or at time of entry. This feature provides a user-friendly interface to native users. It can be
emphasized that input designs of the system is so designed that it ensures easy and error free data entry mechanism. Once one is sure of input data the output formatting becomes a routine work.
DESIGN OF DFD LEVLE 0:
A d m i n
A i r T i c k e t
LEVEL 1:
34
BCA VI
Type of Coach Online Air Ticket Type of Seat
Reg of new Seat number Reservation
Reg of new Place
Place name
User generated By online Air Ticket Ticket Booking Candidate details Check the Ticket on Date
admin
Flight Schedule
Admin Generated By user Confirmation
Flight name and time Cancellation Cancellation of the ticket on date
user
Confirmation of the ticket for particular place of journey
TABLE DESIGN:
35
BCA VI
ADMIN TABLE
CUSTOMER SIGN UP TABLE
FLIGHT DETAILS
36
BCA VI
FLIGHT SCHEDULE DETAILS
PLACE DETAILS
37
BCA VI
TICKET BOOKING DETAILS
TECHNOLOGY / TOOLS SELECTION: The system should be developed using a web technology and should be developed as such that deployment of the system is east and effortless.
38
BCA VI
Also the technology used should be as such that interactions for the customers are very easy and user friendly. We had plenty of options to select the technology and tools. The selection criteria we set are as detailed below: The technology and upgrading the system very easy and less costly. The technology selected should be platform independent. The language should be easy and robust; making is simpler to learn for the newer members. The application must be browser independent. With all these details in mind, we selected ASP (Active Server Pages) as it stands out on all points mentioned above. Web Design Constraints: The following design constraints were kept in mind while designing the pages for the whole application. The pages should be consistent and easy to operate. It should be designed in such a way that an average user who does not have much idea about ASP and related technology can still be able to access the information needed. The Navigation should be easy and stepwise. A customer may have multiple accounts and should be able to access all the accounts with a single password. The entire bank official should work as administrators and should have access to all the service areas / pages of the application by the transaction areas / pages are accessible to only customers whose accounts are not frozen.
8. SYSTEM TESTING
39
BCA VI
TESTING
The development of software systems involves a series of production activities where opportunities for injections of human fallibilities are enormous. Errors may begin to occur at very inception of the process where the objectives, may be erroneously or imperfectly specified, as well as in later design and development stages. Because of human inability to perform and communicate in perfection, software development is accompanied by quality assurance activity. Software testing is a critical element of software quality assurance and represents the Ultimate review of specification, design and coding. In
general, testing starts with test plan. The test plan identifies all the testing related activities that need to be performed along with the scheduled and guidelines for testing. The plan also specifies the levels of testing that need to be done, by identifying the different testing units. Based on the plan, the testing commences. For each unit specified in the plan, first the test cases and reports are produced. Testing presents an Interesting anomaly for a software engineer.
Testing is basically classified into

Black box Testing White box Testing
40
BCA VI
1.
Black Box Testing
Black box testing focuses in the functional requirements of the software. It enables software engineer to derive sets of inputs conditions that will fully exercise all functional requirements for a program.
Black Box testing attempts to find errors in the following categories

Incorrect or missing function Interface errors Errors in Data Structures or external Database access Performance errors Initialization and termination error Generally Black box testing is applied for high level testing such as system testing, acceptance testing. 2. White Box testing: White Box testing, sometimes called glass box testing is a test case design method which uses the control structure of the procedural design to derive test cases. White Box testing is applied to: Exercise all logical decision on their true and false sides Exercise all loops at their boundaries and within their operational bounds Exercise internal data structures to assure their validity.
41
BCA VI
Testing Strategies Unit testing Integration testing Acceptance testing Unit testing: Unit testing focuses on the verification effort on the smallest unit of software design module. Using the detailed design description as a guide, important control paths are tested to uncover errors within the boundary of the modules. The relative complexity of tests and the errors detected as a result is limited by constraint scope established for unit testing. The unit test is always white box oriented, and the step can be conducted in parallel for multiple modules. Integration testing With unit testing the modules may function properly, but at time they may have inadvertent, adverse affect on another; sub function, when combined, may not produce the desired major function; may present problems. Integration testing is symmetric technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested modules and build a program structure that has been dictated by the design. Individually acceptable imprecision may be magnified to unacceptable level; global data structures
Acceptance Testing:
System under consideration is tested for acceptance by constantly keeping in touch with the prospective system. Series of acceptance test are
42
BCA VI
conducted to enable the user to validate all requirements. Acceptance testing involves planning and execution of Functional Test Performance Test Stress Test Functional test is the exercising of the code with nominal input values for which the expected values for which the expected values are known. Performance test determines the amount of execution time spent in various parts of the unit, program throughput and response time. This test is productive at the subsystem and system level. Stress test is designed to intentionally break the unit and the strength and the limitation of the program are examined.
Sample Coding
Admin Page Imports System.Data.SqlClient Partial Class AdminLoginPage Inherits System.Web.UI.Page
Dim Conn As New SqlConnection() Dim SqlStr As String
43
BCA VI
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr") Conn.Open() Dim Cmd1 As New SqlCommand("select * from AdminUsersTab where uName='" & TextBox1.Text & "' and pWord = '" & TextBox2.Text & "'", Conn) Dim DataReader1 As SqlDataReader = Cmd1.ExecuteReader() if DataReader1.HasRows.ToString = True Then Application("aName") = TextBox1.Text Response.Redirect("AdminMainPage.aspx") Else MsgBox("please enter correct UserName and Password") End If Conn.Close() End Sub End Class
Place Entry Imports System.Data.SqlClient Partial Class AdminPlaceName

44
BCA VI
Inherits System.Web.UI.Page Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
Conn.ConnectionString = Application("ConnStr") Conn.Open() Dim Cmd1 As New SqlCommand("select * from PlaceNameTab where PlaceName='" & TextBox1.Text & "'", Conn) Dim DataReader1 As SqlDataReader = Cmd1.ExecuteReader() If DataReader1.HasRows.ToString = True Then MsgBox("This Place Name is allready present please choose another name", MsgBoxStyle.Information, "UserName") Exit Sub Else
End If Conn.Close()
'insert record to the database

45
BCA VI
Conn.Open() SqlStr = "insert into PlaceNameTab values(" SqlStr = SqlStr & "'" & TextBox1.Text & "'," SqlStr = SqlStr & "'" & TextBox2.Text & "')"
'MsgBox(SqlStr) Dim Cmd2 As New SqlCommand(SqlStr, Conn) Cmd2.ExecuteNonQuery() TextBox1.Text = "" TextBox2.Text = ""
MsgBox("New Place Name is created successfully", MsgBoxStyle.Information, "Record Saved") Conn.Close() End Sub End Class
Air ticket checking page Imports System.Data.SqlClient Partial Class AdminTicketCheckDis Inherits System.Web.UI.Page
46
BCA VI
Dim a As String Dim Conn As New SqlConnection() Dim SqlStr As String
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load HyperLink1.Text = "Ticket Booking Flightwise Date : " &
Format(CDate(Request.QueryString("cDate")), "dd-MMM-yyyy") End Sub End Class
Ticket Selection Page Imports System.Data.SqlClient Partial Class AdminTicketCheckSelection Inherits System.Web.UI.Page
Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
47
BCA VI
Response.Redirect("AdminTicketCheckDis.aspx?fno=" & DropDownList1.Text & "&cDate=" & Calendar1.SelectedDate.Date & "") End Sub End Class
Flight Details Imports System.Data.SqlClient Partial Class AFlightDetails Inherits System.Web.UI.Page Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr") Conn.Open() SqlStr = "insert into FlightDetailsTab values(" SqlStr = SqlStr & "'" & TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "','" & TextBox4.Text & "','" & TextBox5.Text & "')" Dim Cmd1 As New SqlCommand(SqlStr, Conn) Cmd1.ExecuteNonQuery() TextBox1.Text = ""
48
BCA VI
TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" Conn.Close() MsgBox("Record created successfully") End Sub End Class
Flight schedule Imports System.Data.SqlClient Partial Class aFlightSchedule Inherits System.Web.UI.Page
Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr")
Conn.Open()
49
BCA VI
Dim Cmd1 As New SqlCommand("select * from FlightScheduleTab where FlightNo='" & TextBox1.Text & "'", Conn) Dim DataReader1 As SqlDataReader = Cmd1.ExecuteReader() If DataReader1.HasRows.ToString = True Then MsgBox("This Flight No is allready present please choose another name", MsgBoxStyle.Information, "Allready Exist Choose Different One") Exit Sub Else
End If Conn.Close() Conn.Open() SqlStr = "insert into FlightScheduleTab values(" SqlStr = SqlStr & "'" & TextBox1.Text & "','" & DropDownList1.Text & "','" & DropDownList2.Text & "','" & DropDownList3.Text & "'," & Val(TextBox2.Text) & "," & Val(TextBox3.Text) & "," & Val(TextBox4.Text) & "," & Val(TextBox5.Text) & "," & Val(TextBox6.Text) & "," & Val(TextBox7.Text) & ",'" & TextBox8.Text & "','" & TextBox9.Text & "')" Dim Cmd2 As New SqlCommand(SqlStr, Conn) Cmd2.ExecuteNonQuery()
50
BCA VI
TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" TextBox9.Text = "" Conn.Close() MsgBox("Record saved successfully, Please proceed") End Sub End Class
Cancellation Ticket Imports System.Data.SqlClient Partial Class CustCancelTicket Inherits System.Web.UI.Page
Dim Conn As New SqlConnection() Dim SqlStr As String

51
BCA VI
Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button2.Click Conn.ConnectionString = Application("ConnStr") Application("tbVar") = Val(TextBox1.Text) Conn.Open() Dim Cmd1 As New SqlCommand("select * from TicketBookTab where RefNo=" & Val(TextBox1.Text) & " and userName='" & Application("uName") & "'", Conn) Dim DataReader1 As SqlDataReader = Cmd1.ExecuteReader() If DataReader1.HasRows.ToString = True Then DataReader1.Read() HyperLink6.Text = "Flight Date : " & DataReader1("tDate").ToString HyperLink1.Text = "No of Seats : " & DataReader1("tQty").ToString HyperLink2.Text = "Ticket Price : " & DataReader1("tprice").ToString HyperLink5.Text = "Members Names : " & DataReader1("MemDetails").ToString Else HyperLink6.Text = "Ticket RefNo is not valid, Please check" HyperLink1.Text = ""
52
BCA VI
HyperLink2.Text = "" HyperLink5.Text = "" End If Conn.Close() End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr") Conn.Open() SqlStr = "Update TicketBookTab set tConfirm='C' where RefNo=" & Application("tbVar") & "" Dim Cmd1 As New SqlCommand(SqlStr, Conn) Cmd1.ExecuteNonQuery() Conn.Close() Response.Redirect("CustTicketCancelRes.aspx") End Sub End Class
Flight Check Details

Imports System.Data.SqlClient Partial Class CustFlightCheckDis
53
BCA VI
Inherits System.Web.UI.Page Dim a As String Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub GridView1_SelectedIndexChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles GridView1.SelectedIndexChanged Application("fVar") = GridView1.SelectedRow.Cells(1).Text 'a = MsgBox(GridView1.SelectedRow.Cells(1).Text, MsgBoxStyle.Information, "Customer Approval") Response.Redirect("CustTicketBooking.aspx") End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load HyperLink1.Text = "From : " & Request.QueryString("fplace") & " To : " & Request.QueryString("tplace") & " List of Flights Available" End Sub End Class
Flight Check details

Imports System.Data.SqlClient
54
BCA VI
Partial Class CustFlightCheckSel Inherits System.Web.UI.Page
Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Application("tDateVar") = TextBox1.Text Response.Redirect("CustFlightCheckDis.aspx?fplace=" & DropDownList1.Text & "&tplace=" & DropDownList2.Text & "&tdate=" & TextBox1.Text & "") End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load TextBox1.Text = Format(Today(), "dd-MMM-yyyy") End Sub End Class
Login Page
55
BCA VI
Imports System.Data.SqlClient Partial Class CustomerLoginPage Inherits System.Web.UI.Page Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr") Conn.Open() Dim Cmd1 As New SqlCommand("select * from CustomerTab where uName='" & TextBox1.Text & "' and pWord = '" & TextBox2.Text & "'", Conn) Dim DataReader1 As SqlDataReader = Cmd1.ExecuteReader() If DataReader1.HasRows.ToString = True Then Application("uName") = TextBox1.Text Response.Redirect("CustMainPage.aspx") Else MsgBox("please enter correct UserName and Password") End If Conn.Close()
56
BCA VI
End Sub End Class
Customer Sign up
Imports System.Data.SqlClient Partial Class CustomerSignUp Inherits System.Web.UI.Page Dim Conn As New SqlConnection() Dim SqlStr As String Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr") Conn.Open() SqlStr = "insert into CustomerTab(uName,pWord,CName,CAdd,eMail,Mobile,PassPortNo,appro ved) values(" SqlStr = SqlStr & "'" & TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox4.Text & "','" & TextBox5.Text & "','" & TextBox6.Text & "','" & TextBox7.Text & "','" & TextBox8.Text & "','N')" Dim Cmd1 As New SqlCommand(SqlStr, Conn) Cmd1.ExecuteNonQuery()
57
BCA VI
TextBox1.Text = "" TextBox2.Text = "" TextBox3.Text = "" TextBox4.Text = "" Conn.Close() Response.Redirect("customersignupres.aspx") End Sub End Class
CustTicketBooking
Imports System.Data.SqlClient Partial Class CustTicketBooking Inherits System.Web.UI.Page Dim Conn As New SqlConnection() Dim SqlStr As String Dim refVar As Long Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Conn.ConnectionString = Application("ConnStr")
58
BCA VI
Conn.Open() Dim Cmd0 As New SqlCommand("select max(RefNo) from TicketBookTab", Conn) Dim DataReader1 As SqlDataReader = Cmd0.ExecuteReader() If DataReader1.HasRows.ToString = True Then DataReader1.Read() refVar = DataReader1(0) + 1 End If Conn.Close() Conn.Open() Application("tbVar") = refVar SqlStr = "insert into TicketBookTab values(" SqlStr = SqlStr & refVar & ",'" & CDate(TextBox1.Text) & "','" & TextBox2.Text & "'," & Val(Left(DropDownList1.Text, 1)) & "," & Val(TextBox5.Text) & "," & Val(TextBox6.Text) & ",'N','" & TextBox7.Text & "','" & TextBox8.Text & "','" & Application("uName") & "')" Dim Cmd1 As New SqlCommand(SqlStr, Conn) Cmd1.ExecuteNonQuery() TextBox1.Text = "" TextBox2.Text = ""
59
BCA VI
TextBox3.Text = "" TextBox4.Text = "" TextBox5.Text = "" TextBox6.Text = "" TextBox7.Text = "" TextBox8.Text = "" Conn.Close() Response.Redirect("CustTicketBookingRes.aspx") End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load TextBox1.Text = Application("tDateVar") TextBox2.Text = Application("fvar") Conn.ConnectionString = Application("ConnStr") 'MsgBox(Application("fvar"))
Conn.Open() Dim Cmd1 As New SqlCommand("select * from FlightScheduleTab where FlightNo='" & Application("fVar") & "'", Conn) Dim DataReader1 As SqlDataReader = Cmd1.ExecuteReader()
60
BCA VI
If DataReader1.HasRows.ToString = True Then DataReader1.Read()
TextBox3.Text = DataReader1("fromPlace").ToString TextBox4.Text = DataReader1("toPlace").ToString DropDownList1.Items.Add("1 Economy DataReader1("EconomyPrice").ToString) DropDownList1.Items.Add("2 Business DataReader1("BusinessPrice").ToString) DropDownList1.Items.Add("3 Executive DataReader1("ExecutivePrice").ToString) TextBox5.Text = DataReader1("EconomyPrice").ToString Else "& "& "&
End If Conn.Close() End Sub
Protected Sub DropDownList1_SelectedIndexChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles DropDownList1.SelectedIndexChanged

61
BCA VI
TextBox5.Text = Trim(Right(DropDownList1.Text, 5)) End Sub
Protected Sub TextBox6_TextChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles TextBox6.TextChanged Label8.Text = Val(TextBox6.Text) * Val(TextBox5.Text) End Sub
Protected Sub DropDownList1_TextChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles DropDownList1.TextChanged TextBox5.Text = Trim(Right(DropDownList1.Text, 5)) End Sub
62
BCA VI
12. CONCLUSION
We would like to admit that there was a lot of effort involved in developing the software/report ready. The completion time for the report was a long as that of the program.
During the course is not a multi user, but it can backup N number of entries in the database. The main principles of a database are to add, delete and modify a record.
We thank everyone who helped and guided in developing software. We are very much obliged to our parents and blessings of god and our beloved lecturers. End Class
63
BCA VI
BIBILOGRAPHY
Websites Following websites are referring to create this project reports. http://www.google.com http://www.microsoft.com http://www.asp123.com
http://www.wikipedia.org
Books Following books and eBooks are used to complete this project reports. Mastering VWD 2005 (Paperback) SQL Server Bible (Paperback) .NET Black Book (Paperback) Professional VWD 2005, 2nd Edition (Paperback) Professional VWD 2005(Paperback) MCAD/MCSD Self-Paced Training Kit: Developing Web Applications with Microsoft ASP .NET and Microsoft Visual C# .NET, Second Edition MCAD/MCSE/MCDBA Self-Paced Training Kit: Microsoft SQL Server 2005 Database Design and Implementation, Exam 70-229, Second Edition.
64
BCA VI
Admin form
Admin main Page
65
BCA VI
Place Entry form
Flight Details
66
BCA VI
Flight Schedule Entry Form
67
BCA VI
Details of Ticket booking
68
BCA VI
69
BCA VI
CONCLUSION
70
BCA VI
12. CONCLUSION
We would like to admit that there was a lot of effort involved in developing the software/report ready. The completion time for the report was a long as that of the program.
During the course is not a multi user, but it can backup N number of entries in the database. The main principles of a database are to add, delete and modify a record.
We thank everyone who helped and guided in developing software. We are very much obliged to our parents and blessings of god and our beloved lecturers.
BIBILOGRAPHY
Websites
71
BCA VI
Following websites are referring to create this project reports. http://www.google.com http://www.microsoft.com http://www.asp123.com
http://www.wikipedia.org
Books Following books and eBooks are used to complete this project reports. Mastering VWD 2005 (Paperback) SQL Server Bible (Paperback) .NET Black Book (Paperback) Professional VWD 2005, 2nd Edition (Paperback) Professional VWD 2005(Paperback) MCAD/MCSD Self-Paced Training Kit: Developing Web Applications with Microsoft ASP .NET and Microsoft Visual C# .NET, Second Edition MCAD/MCSE/MCDBA Self-Paced Training Kit: Microsoft SQL Server 2005 Database Design and Implementation, Exam 70-229, Second Edition.
72

Air Report

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Air Report

Загружено:

Авторское право:

Доступные форматы

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

1. INTRODUCTION TO ONLINE AIR TICKET BOOKING

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

The main modules of the project are as follows.

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

9. New User creation or customer sign up 10.View the records

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

THE FEATURES OF PROPOSED SYSTEM

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

SYSTEM ANALSIS AND DESIGN

The design includes steps like

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

3. Hardware and Software requirement Hardware Requirement

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

Windows XP with server pack 2 Or Windows Vista

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

INTRODUCTION TO MICROSOFT VISUAL BASIC 6.0

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

Program control is then returned to the event

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

Some Features of Visual Basic

Visual Basic 6.0 versus Other Versions of Visual Basic

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

New environment, supported

creation of ActiveX controls, deleted 16-bit application support.

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS):

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

First Normal Form:

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

Second Normal Form:

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

Third Normal Form:

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

Table: A table is a collection of data about a specific topic. There can be

Starting Microsoft Access

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

2. Click on Start --> Programs --> Microsoft Access

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

The above picture gives you the option to:

7. SYSTEM DESIGN SYSTEM STUDY

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013

User Requirements Specifications:

G.T Institute Of Advanced Studies

ONLINE AIR TICKET BOOKING SEMESTER PROJECT - 2013