CHAPTER-1 1.

INTRODUCTION
1.1 ORGANIZATION PROFILE
TRAVELLING CHOICE was founded by well experienced persons having 5 years of Service in the public transportation industry and is one of the largest providers of Inter-City bus transportation, serving more than 10 destinations. We aim to be the leading online business to business Platform, offering total travel solutions to our trade partners and meeting the consumer's needs with a guaranteed satisfaction. We offer a comprehensive range of travel services in Southern India.

Travelling choice is the only private operator which provides Hi-Tech coaches to remote destinations such as Muvattupuzha, Thodupuzha, Pala and Erattupetta. Customer Service: Travel has always been a delightful experience with us. Our clients carry home sweet memories of their association with us, and refer several of their friends and relatives to us.

Travelling choice has established over 10 branches with well equipped customer care service centers spread over in three Southern States namely Tamilnadu, Karnataka and Kerala. Web enabled Customer Care Services and authorized Agency arrangements made exclusively to meet the requirements of general public and customers. All passengers wherever on the network are guaranteed the same level of quality and assistance.

1.2 OVERVIEW OF THE PROJECT

This project is aimed at developing an online ticket reservation for bus. It is concept of developing web portal, where a customer can book bus tickets in travels that are made available in the site. E-booking means electronic booking. Its used to reserve tickets in online .This website is mainly aimed for booking ticket for travel around the world. In this website we can easily check the ticket booking details. This ticket reservation is an internet based application that can be accessed over the net. Instant update will be available for destination FARE details. We can easily find out the places for travel around the India. By use of electronic card we can easily pay the ticket fare. The customer can easily postpone & cancel their tickets but it some charges charged for their ticket cancellation and postpone based on their time of cancellation. After ticket booking customer gets mail and message automatically. Only trusted bank card will be accepted in ticket booking process. Customer should be carry the identification card while travel. After complete ticket booking process, customer should carry the soft copy of the ticket conformation details provide by our website.

CHAPTER-2 2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM
Existing system is a tiredness of ticket reservation from ticket counters because customer have to stand in long queue for ticket reservation and customer used their time to go travels and book the tickets. If the customer wanted to do some changes with booked ticket means customer cant easily cancel and postpone tickets. So, peoples need some benefits for book tickets. So we going for new software like ETICKET. Existing system is not a comfortable for the all of the client.

2.1.1 DRAWBACK OF EXISTING SYSTEM:

Peoples got tired in existing system because customer have to stand in long queue for ticket reservation and customer used their time to go travels and book the tickets. Even we are storing data in manually it will take more time to searching and other stubs. With the existing system time is waste for customers. Timing is very important in all the fields so we can save the time, this will give more benefits.

2.2 PROPOSED SYSTEM

The main purpose of our online ticket booking system is to provide an alternate and convenient way for a customer to buy travelling tickets. It is an automatic system. After the data has been fed into the database, the staff does not need to do anything with the order once it is received through the system. Reduced labor cost and human error with automatic asset tracking technology

Advantage of Proposed System:

To provide a anytime anyplace service for the customers. To minimize the number of staff at the booking place. Customers can easily search available tickets. Customers can easily book the tickets through online. By use of electronic card customers can easily pay the ticket fare It will give the financial benefits also like labor cost reducing. To overcome the drawbacks of the existing system, the proposed system E-TICKET is launched. The proposed system uses ASP.NET front end and SQL SERVER as Backend. SQL SERVER has the capacity of sharing the available database to the clients efficiently and it can prevent the logical problem also. ASP.NET is an efficient Front-end tool and it is an object based language, which supports data abstraction and encapsulation. The new proposed system reduces data redundancy and duplication. It is user friendly, so that the end user can easily access it. It has multi-user accessibility and it is also providing timely report to reduce and uncertainly in decision making.

CHAPTER-3
SYSTEM SPECIFICATION

3.1 SOFTWARE SPECIFICATION

PLATFORM FRONT END BACK END TOOLS WINDOWS XP, 7 Microsoft Visual Studio .Net 2008 (ASP.NET) SQL - Server ADO.NET

3.2 HARDWARE SPECIFICATION

PROCESSOR RAM HARD DISK DRIVES MONITOR KEYBOARD MOUSE Intel Pentium IV 2.80 GHz 1 GB DDR2 RAM 80 GB 15 Color Monitor Standard Keyboard Logitech Mouse

CHAPTER-4
4 SOFTWARE DESCRIPTION

4.1 FRONT END: Microsoft .NET is a set of Microsoft software technologies for rapidly building and integrating XML Web services, Microsoft Windows-based applications, and Web solutions. The .NET Framework is a language-neutral platform for writing programs that can easily and securely interoperate. Theres no language barrier with .NET: there are numerous languages available to the developer including Managed C++, C#, Visual Basic and Java Script. The .NET framework provides the foundation for components to interact seamlessly, whether locally or remotely on different platforms. It standardizes common data types and communications protocols so that components created in different languages can easily interoperate. .NET is also the collective name given to various software components built upon the .NET platform. These will be both products (Visual Studio.NET and Windows.NET Server, for instance) and services (like Passport, .NET My Services, and so on).

The .Net Framework The .NET Framework has two main parts: 1. The Common Language Runtime (CLR). 2. A hierarchical set of class libraries. The CLR is described as the execution engine of .NET. It provides the environment within which programs run. The most important features are

Conversion from a low-level assembler-style language, called Intermediate Language (IL), into code native to the platform being executed on.

Memory management, notably including garbage collection. Checking and enforcing security restrictions on the running code. Loading and executing programs, with version control and other such features. The following features of the .NET framework are also worth description:

Managed Code The code that targets .NET, and which contains certain extra Information - metadata - to describe itself. Whilst both managed and unmanaged code can run in the runtime, only managed code contains the information that allows the CLR to guarantee, for instance, safe execution and interoperability.

Managed Data With Managed Code comes Managed Data. CLR provides memory allocation and Deal location facilities, and garbage collection. Some .NET languages use Managed Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not. Targeting CLR can, depending on the language youre using, impose certain constraints on the features available. As with managed and unmanaged code, one can have both managed and unmanaged data in .NET applications - data that doesnt get garbage collected but instead is looked after by unmanaged code.

Common Type System The CLR uses something called the Common Type System (CTS) to strictly enforce type-safety. This ensures that all classes are compatible with each other, by describing types
7

in a common way. CTS define how types work within the runtime, which enables types in one language to interoperate with types in another language, including cross-language exception handling. As well as ensuring that types are only used in appropriate ways, the runtime also ensures that code doesnt attempt to access memory that hasnt been allocated to it.

Common Language Specification The CLR provides built-in support for language interoperability. To ensure that you can develop managed code that can be fully used by developers using any programming language, a set of language features and rules for using them called the Common Language Specification (CLS) has been defined. Components that follow these rules and expose only CLS features are considered CLS-compliant.

The Class Library .NET provides a single-rooted hierarchy of classes, containing over 7000 types. The root of the namespace is called System; this contains basic types like Byte, Double, Boolean, and String, as well as Object. All objects derive from System. Object. As well as objects, there are value types. Value types can be allocated on the stack, which can provide useful flexibility. There are also efficient means of converting value types to object types if and when necessary. The set of classes is pretty comprehensive, providing collections, file, screen, and network I/O, threading, and so on, as well as XML and database connectivity. The class library is subdivided into a number of sets (or namespaces), each providing distinct areas of functionality, with dependencies between the namespaces kept to a minimum.

Languages Supported by .Net The multi-language capability of the .NET Framework and Visual Studio .NET enables developers to use their existing programming skills to build all types of applications and XML Web services. The .NET framework supports new versions of Microsofts old favorites Visual Basic and C++ (as VB.NET and Managed C++), but there are also a number of new additions to the family. Visual Basic .NET has been updated to include many new and improved language features that make it a powerful object-oriented programming language. These features include inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured exception handling, custom attributes and also supports multi-threading. Visual Basic .NET is also CLS compliant, which means that any CLS-compliant language can use the classes, objects, and components you create in Visual Basic .NET. Managed Extensions for C++ and attributed programming are just some of the enhancements made to the C++ language. Managed Extensions simplify the task of migrating existing C++ applications to the new .NET Framework. C# is Microsofts new language. Its a C-style language that is essentially C++ for Rapid Application Development. Unlike other languages, its specification is just the grammar of the language. It has no standard library of its own, and instead has been designed with the intention of using the .NET libraries as its own. Microsoft Visual J# .NET provides the easiest transition for Java-language developers into the world of XML Web Services and dramatically improves the interoperability of Javalanguage programs with existing software written in a variety of other programming languages.

Active State has created Visual Perl and Visual Python, which enable .NET-aware applications to be built in either Perl or Python. Both products can be integrated into the Visual Studio .NET environment. Visual Perl includes support for Active States Perl Dev Kit. Other languages for which .NET compilers are available include FORTRAN COBOL Eiffel

Fig 4.1 .Net Framework ASP.NET XML Web Services Base Class Libraries Common Language Runtime Operating System Windows Forms

C#.NET is also compliant with CLS (Common Language Specification) and supports structured exception handling. CLS is set of rules and constructs that are supported by the CLR (Common Language Runtime). CLR is the runtime environment provided by the .NET Framework; it manages the execution of the code and also makes the development process easier by providing services. C#.NET is a CLS-compliant language. Any objects, classes, or components that created in C#.NET can be used in any other CLS-compliant language. In addition, we can use objects, classes, and components created in other CLS-compliant languages in C#.NET .The

10

use of CLS ensures complete interoperability among applications, regardless of the languages used to create the application.

Constructors And Destructors Constructors are used to initialize objects, whereas destructors are used to destroy them. In other words, destructors are used to release the resources allocated to the object. In C#.NET the sub finalize procedure is available. The sub finalize procedure is used to complete the tasks that must be performed when an object is destroyed. The sub finalize procedure is called automatically when an object is destroyed. In addition, the sub finalize procedure can be called only from the class it belongs to or from derived classes. Garbage Collection Garbage Collection is another new feature in C#.NET. The .NET Framework monitors allocated resources, such as objects and variables. In addition, the .NET Framework automatically releases memory for reuse by destroying objects that are no longer in use. In C#.NET, the garbage collector checks for the objects that are not currently in use by applications. When the garbage collector comes across an object that is marked for garbage collection, it releases the memory occupied by the object. Overloading Overloading is another feature in C#. Overloading enables us to define multiple procedures with the same name, where each procedure has a different set of arguments. Besides using overloading for procedures, we can use it for constructors and properties in a class. Multithreading

11

C#.NET also supports multithreading. An application that supports multithreading can handle multiple tasks simultaneously, we can use multithreading to decrease the time taken by an application to respond to user interaction. Structured Exception Handling C#.NET supports structured handling, which enables us to detect and remove errors at runtime. In C#.NET, we need to use TryCatchFinally statements to create exception handlers. Using TryCatchFinally statements, we can create robust and effective exception handlers to improve the performance of our application. The .Net Framework The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet.

Objectives of. Net Framework 1. To provide a consistent object-oriented programming environment whether object codes is stored and executed locally on Internet-distributed, or executed remotely. 2. To provide a code-execution environment to minimizes software deployment and guarantees safe execution of code. 3. Eliminates the performance problems. There are different types of application, such as Windows-based applications and Web-based applications.

12

4.2 BACK END SQL SERVER

In the business world, everything is about being "better, faster and cheaper" than the competition -- and SQL Server 2005 offers many new features to save energy, time and money. From programming to administrative capabilities, this version of SQL Server tops all others and it enhances many existing SQL Server 2000 features. CLR (Common Language Runtime) The next major enhancement in SQL Server 2005 is the integration of a .NET compliant language such as C#, ASP.NET or VB.NET to build objects (stored procedures, triggers, functions, etc.). This enables you to execute .NET code in the DBMS to take advantage of the .NET functionality. SMTP mail Sending mail directly from SQL Server 2000 is possible, but challenging. With SQL Server 2005, Microsoft incorporates SMTP mail to improve the native mail capabilities. Say "see-ya" to Outlook on SQL Server! Database mirroring It's not expected to be released with SQL Server 2005 at the RTM in November, but I think this feature has great potential. Database mirroring is an extension of the native highavailability capabilities. FEATURES OF SQL SERVER SQL Server is the client/server relational database management system (RDBMS) that uses transact-Sql to send request between a client and SQL server. SQL Server uses transact-Sql as its database query and programming language. SQL Server integrates with Windows NT and hence takes advantage of many of its security features, SMP features, event viewer, performance monitor, cluster server. Applications are written to access SQL Server through a database Application Programming Interface (API). SQL Server validates users at two levels of security-login authentication and
13

permissions validation on database user accounts and roles. Ease of installation, deployment and use. Scalability The same database engine can be used across platforms ranging from laptop computers running Microsoft Windows 95 to large, multiprocessor servers running Microsoft Windows NT. Data Warehousing SQL Server includes tools for extracting and analyzing summary data for online analytical processing. System integration with other server software SQL Server integrates with e-mail, the Internet, and Windows.

14

CHAPTER-5 5 PROJECT DESCRIPTION

5.1 PROBLEM DEFINITION
A system that can able to maintain the problem request and that can resolve with time scheduling. Existing system is a tiredness of ticket reservation from ticket counters because customer have to stand in long queue for ticket reservation and customer used their time to go travels and book the tickets. Using this Application Corporate development represents a major step in the evaluation of the requirements. Display the information and produce the results at a faster rate and cheap operating cost. One of the important steps in planning a project is to determine of appropriateness of a computerized solution. In addition to being cost effective, a computerized system must be socially and politically acceptable. There are possibilities for clerical persons committing errors while correction of papers, so the best available solution is computerization. Hence the concern decided to make the system computerized for cost efficiency and to reduce the manpower, for better service, to better information retrieval and also for the flexibility for the future development.

15

5.2 MODULE DESCRIPTION

MODULE DESCRIPTION: TICKET CHECKING: The ticket checking module is used to check available tickets for travel In this module we can easily check the ticket booking details This module is used to get details of buses. Instant update will be available for destination FARE details. TICKET BOOKING: This ticket booking module is used to reserve the tickets for travel. This module is mainly aimed for booking ticket for travel around the India. This module is used for two type of booking. One is single trip booking another one is tour booking. By use of electronic card we can easily pay the ticket fare. Only trusted bank card will be accepted in ticket booking process Customer should be carry the identification card while travel. After complete ticket booking process , customer should carry the soft copy of the ticket conformation details provide by our website. POSTPONE: The postpone module is used to change or extend travelling date and time Ticket postpone have some time limit to postpone ticket .customer can easily postpone their tickets but it should be before 24 hours of travel time.

16

 For postpone ticket charges charged based upon their ticket price and time of postpone. If there is no ticket customer cant postpone ticket. CANCELLATION: The cancellation module is used to cancel the reserved tickets. The ticket cancellations have some time limit to cancel the ticket. so the customer can easily cancel their tickets but it should be before 24 hours of travel time. For cancelling ticket charges charged based upon their ticket price and time of cancellation. CUSTOMER SUPPORT : The customer support module is used to support the customer. This module maintains ticket refund status, print ticket. REFUND STATUS: The refund status is used to check retransfer status of money. It is used to customer to check their refund status This check refund status contains ticket no, mobile no or E-mail id. PRINT TICKET: The print ticket is used to get the ticket, whenever customer need their booked ticket Customer should carry the soft copy of the ticket conformation details provide by our website. This print ticket contains ticket no, mobile no or E-mail id.

17

5.3 DATA FLOW DESCRIPTION Flow Diagram (DFD) is a modeling tool that allows picturing system as a network of functional process to one another by pipelines of data. They are also widely used for representation of external and top-level design specification. The DFD shows the interface between the system and external terminators. Data Flow Diagram is also called as Bubble Chart. The bubble represents the process, the line represents the data flow and rectangle represents the entity SYMBOLS

Process

Database

Relationship

Modules

Double Direction Flow of Data Single Direction Flow of Data

On page Connector

Display

18

A. DATA FLOW DIAGRAM

Level 0

Level 1

19

Level 2

20

Level 3

21

5.4 DATA BASE DESIGN

A store of integrated data capable of being directly addressed for multiple users is organized so that various files can be accessed through a single reference based on the relationship among the records in the file rather than the physical location. The most important aspect of building an application is the design of the tables or the database scheme. The data stored in the tables must be organized in some manner, which is meaningful. The overall objective in the process of table design has been to treat data as an organizational of data in the database aims to achieve three major objectives viz., Data Integration Data Integrity Data Independence In any database environment, several programs use the available data. Instead of each program managing its own data, authorized users share data across applications with database software managing the data as an entity. The primary objective of database design includes fast response time to enquire, more information at low cost, control of redundancy, clarity and ease of use, data and program independence, accuracy and integrity of the system, fast recovery and availability of a powerful end user language. The database components are File manager DDL compiler Database manager The theme behind a database is to handle information as an integrated whole thus making access to information easy, quick, inexpensive and flexible for users. Each table has been designed with a perfect vision

22

5.4.1 OBJECTIVE OF DATA BASE DESIGN Reduced redundancy Enforcing standards Sharing of data Maintaining integrity Data consistency Applying security restrictions

23

ENTITY RELATIONSHIP DIAGRAM

24

5.5 INPUT DESIGN

Input design is the process of converting user-originated inputs to computer- based format. Input data are collected and organized into groups of similar data. Validations are made for each and every data entered in the screen for data accuracy. The inputs of the system have been designed effectively in such a way that the manual forms and inputs are coordinated where data elements are common to the source document and to the input. A source document has been prepared for the input of the data in order to make the data entry accurate and fast and then select the media used to enter them into the computer. The input screens are very user friendly.

OBJECTIVES OF INPUT DESIGN The quality of the system input determines the quality of the system output. Input specifications describe the manner in which data enter the system 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. The input design also determines whether the user can interact efficiently with the system. Five objectives guiding the design of the input focus on Effectiveness Accuracy Easy to use Consistency

Attractiveness

25

5.6 OUTPUT DESIGN

Computer output is the most important and direct source of information to the user. Efficient, Intelligible output design should improve the systems relationships with the user and help in decision making. A major form of output is a hard copy from the printer printouts should be designed around the output requirements of the user. The output devices to be considered depend on factors such as compatibility of the device with the system response time requirements, expected print quality and number of copies needed. In addition to deciding on the output device, the system analyst must consider the print format and the editing for the final printout. Editing ranges from suppressing unwanted zeroes to merging selected records to produce new figures. In either case the task of output preparation is critical, requiring skill and ability to align user requirements with the capabilities of the system in operation. The standards for printed output suggest the following Give each output a specific name or title Provide a sample of the output layout, including areas where printing may appear and location of each field. State whether each output field is to include significant zero spaces between fields and alphabetic or any other data.

The layout sheet for displayed output is similar to the layout chart used for designing input. Outputs are the direct source of information to the user. Users generally merit the system analyst work closely with the user through an interactive process, until the result is considered to be satisfactory.

26

DATABASE DESIGN

A.TABLE DESIGN
TABLE NAME: TICKET DETAILS Primary Key: TICKET NO

Fields Ticket no Name Age Gender From To Date & time

Type Integer Varchar Integer Varchar Varchar Varchar Date & time

Width 7 30 3 10 20 20

Constraint Primary Key -

Ticket details table contains ticket no, name, age, gender, from, to, date and time. here ticket no is primary key.

TABLE NAME: TICKET CHECKING

Fields From To Date & time Bus types

Type Varchar Varchar Date & time Varchar

Width 20 20

Constraint -

20

27

B_places Amount

Varchar Integer

20 5

Ticket checking table contains from, to, date and time, bus types, boarding place, amount.

TABLE NAME: SINGLE TRIP BOOKING PRIMARY KEY: MOBILE NO

Fields Name Age Gender From To Date Mobile no E-mail Select bank Card on no Card on name Expiry date Cvv

Type Varchar Integer Varchar Varchar Varchar Date Integer Varchar Varchar Integer Varchar Date Integer 3

Width 30 3 10 20 20

Constraint -

10 30 30 16 30

Primary key -

28

Ticket booking table contains name, age, gender, from, to, date, mobile no, email id, bank details, card on no, card on name, expiry date, Cvv.

TABLE NAME: TOUR BOOKING PRIMARY KEY: MOBILE NO

Fields Package Name Mobile No

Type Varchar Varchar Integer

Width 30 45 10

Constraint -

Tour booking table contains tour packages, name, and mobile no.

TABLE NAME: CANCELLATION AND POSTPONE FOREIGN KEY: TICKET NO&MOBILE NO

Fields Ticket no Mobile no

Type Integer Integer

Width 7 30

Constraint Foreign key Foreign key

Ticket cancellation and postpone tables contains ticket no, mobile no.

29

TABLE NAME: CHECK REFUND STATUS AND PRINT TICKET FOREIGN KEY: TICKET NO & MOBILE NO

Fields Ticket no Mobile no

Type Integer Integer

Width 7 30

Constraint Foreign key Foreign key

Check refund status and print ticket table contains ticket no and mobile no.

30

CHAPTER-6
6 SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.

6.1 Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail. Why Testing Testing is the analysis of source/executable code and the controlled execution of executable code to reveal defects that compromise a Java program's executable integrity. Defects often lead to erratic behavior or the premature termination of an executing program. The Software testing process commences once the program is created and the documentation and related data structures are designed. Software testing essential for correcting errors. Otherwise the program or the project is said to be not complete. Software testing is a process of checking whether the developed system is working according to the original objectives and requirements. The system should be tested experimentally with test data so as to ensure that the system works according to the required specification. Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. After the coding phase, computer programs are available that can be executed for testing purposes. This implies that testing not only has to uncover errors introduced during coding, but also errors introduced during the previous phases. Testing objectives The testing objectives are summarized in the following three steps Testing is a process of executing a program with the intent of finding an error.

31

 A good test case is one that has high probability of finding an as-yet undiscovered error. A successful test is one that uncovers an as yet undiscovered error. Testing principles All the tests should be traceable to customer requirement. Tests should be planned long before testing begins that is the test planning can bring as soon as the requirement model is complete.

The following are the attributes of the good test: A good test has high probability of finding an error. A good test is not redundant. A good test should be best of breed. A good test should be neither too simple nor too complex Integration Testing Software integration testing is the incremental integration testing of two or more integrated software components on step up software applications at the company level interact without error. Test Results: All the test cases mentioned above a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or one passed successfully. No defects encountered.

32

6.2 TEST CASE Unit testing Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.

Integration testing

Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components.

Functional testing Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals.

33

Functional testing is centered on the following items: Valid Input Invalid Input Functions Output : identified classes of valid input must be accepted. : identified classes of invalid input must be rejected. : identified functions must be exercised. : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked. Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current tests is determined.

System Testing System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.

White Box Testing White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.

34

Black Box Testing Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot see into it. The test provides inputs and responds to outputs without considering how the software works. Acceptance Testing User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements. Test Results: All the test cases mentioned above passed successfully. No defects encountered.

35

CHAPTER-7
7. SYSTEM IMPLEMENTATION

DESCRIPTION METHODOLOGY
System Implementation is the important stage of the project when the theoretical design is turned into practical system. Implementation simply means converting a new system design into operation. A critical factor in conversion is not disturbing the functioning of the organization. Following conversion, it is desirable to review the performance of the system and to extent that changes in the users environment. PLANNING Planning plays an important role in the implementation. The planning should face any practical problems for controlling various activities of people, out their own data processing. This can be achieved easily with the cooperation of the members of the concern TRAINING Successful implementation needs trained computer staff. End users are trained so that they are capable of working efficiently within the successful of the system. MAINTENANCE Maintenance involves recovery on crash such as the backups and the end user should be given only executable format of the system

36

SPECIFICATION OF MODEL
There are several methods for handling the implementation and the consequent conversion from the old to the new computerized system. The most secure method for conversion from the old system to the new system is to run the old system and new system in parallel. In this approach, a person may operate in the manual older processing system as well as start operating the new computerized system. This method offers high security, because even if there is a flaw in the computerized system, we can depend upon the manual system. However, the cost of maintaining two systems in parallel is very high. This outweighs its benefits. Another commonly method is to direct cut over from the existing manual system to the computerized system. There are no parallel activities. However there is no remedy in case of a problem. This strategy requires careful planning. A working version of the system can also be implemented in one part of the organization and the personnel will be piloting the system and changes can be made as and when required. But this method is less preferable due to the loss of consistency of the system.

37

One such approach/process used in Software Development is "The Waterfall Model". Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate process phases. The phases in Waterfall model are: Requirement Specifications phase, Software Design, Implementation and Testing & Maintenance. All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall Model". All the methods and processes undertaken in Waterfall Model are more visible.

Requirements gathering and analysis

The goal of systems analysis is to determine where the problem is in an attempt to fix the system. This step involves breaking down the system in different pieces and drawing diagrams to analyze the situation, analyzing project goals, breaking down what needs to be created and attempting to engage users so that definite requirements can be defined. Requirements Gathering sometimes requires individuals/teams from client as well as service provider sides to get detailed and accurate requirements.

Design
In systems design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems. The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo code, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input.

38

Build or coding
Modular and subsystem programming code will be accomplished during this stage. Unit testing and module testing are done in this stage by the developers. This stage is intermingled with the next in that individual modules will need testing before integration to the main project.

Testing
The code is tested at various levels in software testing. Unit, system and user acceptance testings often performed. This is a grey area as many different opinions exist as to what the stages of testing are and how much if any iteration occurs. Iteration is not generally part of the waterfall model, but usually some occur at this stage.

39

CHAPTER-8 8. CONCLUSION AND FURTHER ENHANCEMENT

8.1 CONCLUSION
This project entitled E-TICKET is implemented for a balanced growth and efficient running of the enterprise. It helps to replace the manual system effectively. This project is a real time based management system. This can be practically implemented The software developed has been designed and run to satisfy the requirements and needs of the organization as well as the end users. The system reduces the manual work of maintenance of the records and customers can easily search their tickets and book tickets for travel. The customer has the choice of choosing the seat as their comfort ability. Also the pricing could be made dynamic in order to enhance the system. Customer can easily understand the procedure of booking tickets. Customers can easily postpone and cancel their tickets. The most effective one for upcoming days because saving our time while we booking a ticket in a travels, customers can save their time by booking in online.

40

8.2 SCOPE FOR FURTHER ENHANCEMENT

This online ticket booking for TRAVELLING CHOICE website almost covered all the requirements. The design of this package can be extended to any extent in the case of inclusion or number of facilities with the system. Further requirements and improvements can easily be done. Since the coding is mainly structured are modular in nature. Improvements can be appended by changing the existing modules or adding new modules. However there are certain assumptions and certain limitations that could be overcome and various new applications could be added like: In future the project can be used online updating and live news Mode of payment can be modernized and increased. Tour booking method can be change. Price can be made dynamic

41

9. Appendix 9.1SCREEN SHOTS

HOME PAGE

42

TICKET BOOKING

43

CANCELLATION

44

POSTPONE

45

PRINT TICKET

46

9.2 SAMPLE CODING

using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; using System.Net.Mail; public partial class Default8 : System.Web.UI.Page { public SqlConnection con; public SqlCommand cmd; int r, c; public void dbcon() { con = new SqlConnection(System.Configuration.ConfigurationManager.ConnectionStr ings["mydb"].ToString()); con.Open(); } protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { Label2.Text = Session["busfr"].ToString(); Label3.Text = Session["busto"].ToString(); Label4.Text = Session["busdt"].ToString(); } }

protected void Button1_Click(object sender, EventArgs e) { Session["bank"] = DropDownList1.SelectedValue; dbcon(); string dt=Session["date"].ToString(); DateTime bdt = Convert.ToDateTime(dt); string tcno = Session["bid"].ToString() + Session["sel"].ToString(); Session["ttcno"] = tcno; Session["tname"] = TextBox1.Text; Session["tage"] = TextBox2.Text;

47

Session["tgen"] = TextBox3.Text; string sql = "insert into booking values('" + TextBox1.Text + "','"+bdt+"','"+Session["busfr"].ToString()+"','"+Session["busto"].To String()+"','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','"+DropDownList1.SelectedValue+"','"+tcno+"')"; cmd = new SqlCommand(sql,con); cmd.ExecuteNonQuery(); if ((radio1.SelectedValue == "Credit Card")||(radio1.SelectedValue=="Debit Card")) Response.Redirect("creditcard.aspx"); else if(radio1.SelectedValue=="Net banking") Response.Redirect("net banking.aspx");

} protected void Button2_Click(object sender, EventArgs e) { } protected void GridView1_SelectedIndexChanged(object sender, EventArgs e) { } protected void Button2_Click1(object sender, EventArgs e) { dbcon(); string sql = "insert into pass values('"+TextBox1.Text+"','"+TextBox2.Text+"','"+TextBox3.Text+"','" +TextBox4.Text+"')"; cmd = new SqlCommand(sql,con); cmd.ExecuteNonQuery(); con.Close(); TextBox1.Text = " "; TextBox2.Text = " "; TextBox3.Text = ""; TextBox4.Text = " "; TextBox5.Text = " "; } }

using using using using using using using

System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security;

48

using using using using using using

System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Data.SqlClient;

public partial class Default4 : System.Web.UI.Page { public SqlConnection con; public SqlCommand cmd; public string sql; public void connection() { con = new SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings[" mydb"].ToString()); con.Open(); } protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { connection(); sql = "select * from booking where mobile='" + TextBox2.Text + "'"; cmd = new SqlCommand(sql, con); SqlDataReader datareader = cmd.ExecuteReader(); if (datareader.HasRows) { while (datareader.Read()) { SqlCommand cd = new SqlCommand("delete from booking where mobile='" + TextBox2.Text + "' and ticketno='" + TextBox1.Text + "'", con); cd.ExecuteNonQuery(); Response.Write("<script>alert('Your Ticket Cancelled')</script>"); } } else { Response.Write("<script>alert('Your MObile No. or Ticket No. is Wrong')</script>"); } SqlCommand cd = new SqlCommand("delete from booking where mobile='" + TextBox2.Text + "' and ticketno='" + TextBox1.Text + "'", con); cd.ExecuteNonQuery(); Response.Write("<script>alert('Your Ticket Cancelled')</script>"); con.Close(); } }

49

using using using using using using using using using using using using using using

System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Net.Mail; System.Data.SqlClient;

public partial class Default5 : System.Web.UI.Page { public SqlConnection con; public SqlCommand cmd; public string sql; public string nm, dt, sr, des, age, gen, mob, em, bnk, tcno; public void connection() { con = new SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings[" mydb"].ToString()); con.Open(); } protected void Page_Load(object sender, EventArgs e) { Class1 ob = new Class1(); ob.initi(); } protected void Button1_Click(object sender, EventArgs e) { connection(); sql = "select * from booking where mobile='"+TextBox2.Text+"' and ticketno='"+TextBox1.Text+"'"; cmd = new SqlCommand(sql,con); SqlDataReader dr = cmd.ExecuteReader(); if (dr.HasRows) { while (dr.Read()) { nm = dr.GetString(0); //dt = dr.GetDateTime(1); sr = dr.GetString(2); des = dr.GetString(3); age = dr.GetString(4); gen = dr.GetString(5); mob = dr.GetString(6); em = dr.GetString(7); bnk = dr.GetString(8); tcno = dr.GetString(9); } } else

50

{ Response.Write("<script>alert('Your MObile No. or Ticket No. is Wrong')</script>"); } con.Close(); connection(); sql = "delete from booking where mobile='"+TextBox2.Text+"' and ticketno='"+TextBox1.Text+"'"; cmd = new SqlCommand(sql,con); cmd.ExecuteNonQuery(); if(tcno!=" ") { connection(); sql = "insert into postpone values('"+nm+"','"+Calendar1.SelectedDate+"','"+sr+"','"+des+"','"+age+"',' "+gen+"','"+mob+"','"+em+"','"+bnk+"','"+tcno+"')"; cmd = new SqlCommand(sql,con); cmd.ExecuteNonQuery(); con.Close(); string msg = " Name:" + nm + "Postpone Date: " + Calendar1.SelectedDate + " FROM: " + sr + " To: " + des; MailMessage mail = new MailMessage(); mail.To.Add(em); mail.Body = msg; mail.From = new MailAddress("natarajbca60@gmail.com"); mail.Subject = "Ticket Details"; mail.IsBodyHtml = true; SmtpClient smtp = new SmtpClient(); smtp.Host = "smtp.gmail.com"; smtp.Port = 587; smtp.Credentials = new System.Net.NetworkCredential("natarajbca60@gmail.com", "9789634516"); smtp.EnableSsl = true; smtp.Send(mail); Response.Write("<script>alert('Your Tickets Booked,Your ticket is mailed')</script>"); } } protected void Calendar1_SelectionChanged(object sender, EventArgs e) { TextBox3.Text = Calendar1.SelectedDate.ToString(); } }

using using using using using using using using

System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI;

51

using using using using using using

System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Net.Mail; System.Data.SqlClient;

public partial class Default3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { Class1 ob = new Class1(); ob.initi(); Label1.Text="Ticket Number: "+Session["ttcno"].ToString(); Label2.Text="Name: "+Session["tname"].ToString(); Label3.Text="Age: "+Session["tage"].ToString(); Label4.Text="Gender: "+Session["tgen"].ToString(); Label5.Text="From: "+Session["busfr"].ToString()+" To: "+Session["busto"].ToString()+" Date: "+Session["date"].ToString(); } public SqlConnection con; public SqlCommand cmd; public SqlDataReader dr; public void dbcon() { con = new SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings[" mydb"].ToString()); con.Open(); } protected void Button1_Click(object sender, EventArgs e) { string mailid=" "; dbcon(); string sql = "select * from booking where name='"+Session["tname"].ToString()+"'"; cmd = new SqlCommand(sql,con); dr = cmd.ExecuteReader(); if (dr.HasRows) { while (dr.Read()) { mailid = dr.GetString(7); } } else { Response.Write("<script>alert('Invalid Emailid')</script>"); } string msg=Label1.Text+Label2.Text+Label3.Text+Label4.Text+Label5.Text; MailMessage mail = new MailMessage(); mail.To.Add(mailid); mail.Body = msg; mail.From=new MailAddress("natarajbca60@gmail.com"); mail.Subject="Ticket Details";

52

mail.IsBodyHtml = true; SmtpClient smtp = new SmtpClient(); smtp.Host = "smtp.gmail.com"; smtp.Port = 587; smtp.Credentials = new System.Net.NetworkCredential("natarajbca60@gmail.com","9789634516"); smtp.EnableSsl = true; smtp.Send(mail); Response.Write("<script>alert('Your Tickets Booked,Your ticket is mailed')</script>"); } }

53

CHAPTER-10 10. BIBLIOGRAPHY

Book References Apress.Beginning.CSS.Web.Development.From.Novice.to. Professional.Aug.2006 Creating Cool HTML 4 Web Pages Database System Concepts Inside ASP.NET Volume 3 Edition 3.5 Management Information System SQL Server for Window Web Design Workshop Web Design for Dummies -DAVE TAYLOR -SUDARSHAN -SCOTT WORLEY -W S JAWADEKAR -ALAN SIMPSON -ROBIN WILLIAMS' -LISA LOPUCK

- SIMON COLLISON

Wrox_-_Professional_SQL_Server_2005_Programming_2006-12- ROBERT VIEIRA

Online References www.google.com www.w3schools.com www.asp_dotnet2005_sql.com www.dukedotnet.org http://www.w3schools.com/aspnet/default.asp http://forums.asp.net/t/1191703.aspx/1 http://krishnasaralanet.blogspot.in/p/sending-sms-from-aspnet-application.html www.managementhelp.org/hr_mgmnt/hr_mgmnt.html www.csharpcorner.com

http://www.pagetutor.com/html_tutor/index.html http://webdesign.about.com/od/beginningtutorials/qt/web-page-html.htm

54