PUNJAB TECHNICAL UNIVERSITY (MCA 6-LE) JALANDHAR

PROJECT REPORT

On

ROYAL INDIAN TOUR

MASTER OF COMPUTER APPLICATIONS (Batch 2012-2013)

Submitted to: Mr. -----------------(HOD-MCA)

1

Submitted by: Name: jaswinder kaur Semester: MCA 6th (LE) Roll No: 12205810112

MAJOR PROJECT REPORT On

ROYAL INDIAN TOUR

At K Y COMPUTERS, RAJPURA

Submitted in partial fulfillment for the award of the degree of

MASTER OF COMPUTER APPLICATIONS (Batch 2012-2013)

Submitted to: Mr. -----------------(HOD-MCA)

Submitted by: Name: JASWINDER KAUR Semester: MCA 6th (LE) Roll No: 12205810112

ACKNOWLEDGEMENT

Apart from the efforts of me, the success of my project depends largely on the encouragement and guidelines of many others. I take this opportunity to express my gratitude to the people who have been instrumental in the successful completion of this project. I would like to show my greatest appreciation to my project in-charge, MR. KRISHAN TULI . I cant say thank you enough for the tremendous support and help. I feel motivated and encouraged every time I attend his meeting. Without his encouragement and guidance this project work would not have materialized. Im highly grateful to MR. KRISHAN TULI, for his thorough guidance right from day 1 till the end of training. He actually laid the ground for conceptual understanding of technologies used in project. The guidance and support I received from my internal guide- MR. KRISHAN TULI, was equally vital for the success of the project. Im grateful for his con stant support and help.

JASWINDER KAUR

DECLARATION

I, JASWINDER KAUR hereby declare that the report of the project entitled Royal Indian Tour has not presented as a part of any other academic work to get my degree or certificate except (PUNJAB TECHNICAL UNIVERSITY, JALANDHAR) for the fulfillment of the requirements for the degree of Master of Computer Application.

jaswinder kaur (Roll No: 12205810112) (Session : 2012-2013)

Table of Contents
Objective of the Project 1. Project Profile:1.1 Introduction 1.2Purpose of Documents 1.3Project Scope 1.4Definitions, Acronyms and Abbreviations

2. General Description:2.1 RIT Function 2.2 User Characteristics 2.3 Principal Actor 2.4 Operating Environment 2.5 User Documentations 2.6 Assumptions and Dependencies

3. System Requirements:3.1Software Tools: 3.1.1 About ASP.NET 3.1.2 About JAVA SCRIPT 3.1.3 About HTML 3.1.4 About MY-SQL 3.2 Hardware Platform

4. System Analysis
4.1 Existing System 4.2 Need of a new system 4.3 Proposed System 4.4 Feasibility Study

5. System Requirement Specification

5.1 Introduction to SRS 5.2 Software Engineering Paradigm

6. System Design and Development:

6.1 Introduction 6.2 Steps of Design Process 6.3 Data Flow Diagrams 6.4 E-R Diagrams 6.5 Data Base Design 6.5.1 Database Table: 6.5.1.1 CLIENT Table 6.5.1.2 USERINFO Table 6.5.1.3REGISTER USER Table 6.5.1.4 HOTEL FACILITIES Table 6.5.1.5 LOCATION Table 6.5.1.6 HOTEL Table 6.5.1.7 ADD TO CART Table 6.5.1.8 CONTACT US Table 6

6.5.1.9 RID Table 6.5.1.10 TID Table

7. Module Description 7.1 Modules of Project & Descriptiom 8. System Testing 9. System Implementation and Maintenance 10. Future Extension and Conclusion 11. Bibliography.

OBJECTIVES OF THE PROJECT:Before Starting the project we should fully know about the meaning of project. There are seven letters in the word PROJECT each character has its own technical meaning.

Planning
This deal with the idea at thinking and which are required for the project.

Resource
The money problem will be solved and resources from which collected.

Operating
The procedure from which the getting job is prepared in a systematic way is known as operation.

Joint effort
This is directly proper to a operation output is made of several person working sincerely is known as JOINT EFFORT.

Engineering
A well-educated engineer can do this work in a better way to find out better result. Hence the project is as engineering function.

Co-operation
8

To make the project successfully, it is necessary for its success and completion of project.

Technique
It must as it gives a better shape. It is not possible to complete the project without technique.

The project is a system that gives the systematic way of planning and working.

1)Project Profile:1.1Introduction

Project:-ROYAL INDIAN TOUR We have tried to design the Website in such a way that user may not have any difficulty in using this package & further expansion is possible without much effort. Even though we cannot claim that this work to be entirely exhaustive, the main purpose of our exercise is to gather information about places for vacations. We are confident that this website package can be readily used by non-programming personal avoiding human handled chance of error. This project is used by following types of users-

Administrator can maintain daily updates . Administrator is must be an authorized user. He can further change the password. There is the facility for password recovery, logout etc. Unauthorised users can only acess the information about the locations.

Some basic requirements of the Web-App:-

1.2 Purpose of Documents: Provide information about the famous locations and hotels in these areas We also provide the offerprice thats suits to the tourist budget Facility of booking and payment tranasaction Registration facilities.and contact us to be in touch with us
The Software includes:1. Information about locations and hotel 2. Providing add to cart facilities 3. Pay now and registration facilities 10

4.

Member Identification whether authorized or not

Technical Requirements There are some technical requirements which should be assured by every type of sites:1. Range of work volumes 2. Range of time. 3. Database size and compatible softwares. 4. Security requirements.

1.3 Project Scope:

The Software Requirements Specification captures all the requirements in a single document. It can be used in any tour and travel organization for maintaining member details and their existence.

1.4 Definitions, Acronyms and Abbreviations

In Order to make any trip to any famous Locations And Hotels Royal Indian Tour is the best travel consultant in India..It makes your travel experience a memorable with our years of experience and trust of thousands of clients. Some Basic Functions Of Web App

Project is related to Royal Indian Tour

The project maintains two levels of users: Administrator Level-login , logout Unauthorized user:to acees only information about the locations Main facilities available in this project are: Maintaining records of user like transaction id,email,phone no etc Providing different facilities to members. Hotel room type facilities Facilities in hotels purchasing facilities online transaction facilities 11

If guard user forgets his/her password then a message of unauthorized user will be displayed. In this project collection of data is from different residential areas. Members information will be automatically updated in the database. User or Administrator can search a members record by his/her transaction id. Member Id is also given to each member.

2)GENERAL DESCRIPTION:-

2.RIT Function

RIT is web-app formed by groups of people from a specific geographic community who come together to gather information about tourists attraction locations. It provide facilities like:-

Registeration Contact us On Line payment Add to cart Booking facility

Various operational works that are done in our project are: Recording information about the users that come. Generating on line bills. Maintenance of the list of user information.

Keeping records of transaction id that is provided to each user who is authorized. 12

Keeping information of member database.

2.2 User Characteristics The project maintains two levels of users: Administrator Level-Honours Unauthorized User Level- Permission of onlyData access

Every user should be: Comfortable of working with computer. He must have knowledge in IT field. He must also have basic knowledge of English too.

2.3 Principal Actor

The main Principal Actor of this project Royal Indian Tour is a Dynamic web that are used to On-line Searching of famous locations & hotels in India as well as Fulfill the Needs of tourists and any one.

2.4 Operating Environment

Giving best in order to make tourists vacation fabulous. The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform.

2.5 User Documentation

Eight steps involved in the user documentation are:

Form a project team and appoint a project leader. 13

Prepare system flowcharts. Enumerate potential proposed system. Define and identify characteristics of proposed system. Determine and evaluate performance and cost effective of each proposed system. Weight system performance and cost data. Select the best-proposed system. Prepare and report final project directive to management.

2.6 Assumptions and Dependencies

The users have sufficient knowledge of computers. Users should have Internet connection and Internet server capabilities. The users know the English language, as the user interface will be provided in English.

14

3) System Requirements:3.1 Software Tools>> 3.1.1 Introduction to ASP.NET:.NET Framework The .NET Framework (pronounced dot net) is a software framework developed by Microsoft that runs primarily on Microsoft Windows. It includes a large library and provides language interoperability (each language can use code written in other languages) across several programming languages. Programs written for the .NET Framework execute in a software environment (as contrasted to hardware environment), known as the Common Language Runtime (CLR), an application virtual machine that provides important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework. The .NET Framework's Base Class Library provides user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. Programmers produce software by combining their own source code with the .NET Framework and other libraries. The .NET Framework is intended to be used by most new applications created for the Windows platform. Microsoft also produces a popular integrated development environment largely for .NET software called Visual Studio. Contents 1 History 2 Design features 3 Architecture 3.1 Common Language Infrastructure (CLI) 3.2 Security 3.3 Class library 3.4 Memory management 15

4 Standardization and licensing 5 Criticism 6 Alternative implementations 7 References 8 External links History

A more complete listing of the releases of the .NET Framework may be found on the List of .NET Framework versions. Design features

Interoperability Because computer systems commonly require interaction between newer and older applications, the .NET Framework provides means to access functionality implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework; access to other functionality is provided using the P/Invoke feature. Common Language Runtime Engine The Common Language Runtime (CLR) is the execution engine of the .NET Framework. All .NET programs execute under the supervision of the CLR, guaranteeing certain properties and behaviors in the areas of memory management, security, and exception handling.

Language Independence The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible datatypes and programming constructs supported by the CLR and how they may or may not interact with each other conforming to the Common Language Infrastructure (CLI) 16

specification. Because of this feature, the .NET Framework supports the exchange of types and object instances between libraries and applications written using any conforming .NET language. Base Class Library The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes that encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction, XML document manipulation, and so on. Simplified Deployment The .NET Framework includes design features and tools which help manage the installation of computer software to ensure it does not interfere with previously installed software, and it conforms to security requirements. Security The design is meant to address some of the vulnerabilities, such as buffer overflows, which have been exploited by malicious software. Additionally, .NET provides a common security model for all applications. Portability While Microsoft has never implemented the full framework on any system except Microsoft Windows, the framework is engineered to be platform agnostic,[6] and cross-platform implementations are available for other operating systems (see Silverlight and the Alternative implementations section below). Microsoft submitted the specifications for the Common Language Infrastructure (which includes the core class libraries, Common Type System, and the Common Intermediate Language),[7][8][9] the C# language,[10] and the C++/CLI language[11] to both ECMA and the ISO, making them available as official standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms. [edit]Architecture

17

Visual overview of the Common Language Infrastructure (CLI) Common Language Infrastructure (CLI) Main article: Common Language Infrastructure The purpose of the Common Language Infrastructure (CL) is to provide a language-neutral platform for application development and execution, including functions for Exception handling, Garbage Collection, security, and interoperability. By implementing the core aspects of the .NET Framework within the scope of the CL, this functionality will not be tied to a single language but will be available across the many languages supported by the framework. Microsoft's implementation of the CLI is called the Common Language Runtime, or CL.

Main article: .NET assembly The CIL code is housed in .NET assemblies. As mandated by specification, assemblies are stored in the Portable Executable (PE) format, common on the Windows platform for all DLL and EXE files. The assembly consists of one or more files, one of which must contain the manifest, which has the metadata for the assembly. The complete name of an assembly (not to be confused with the filename on disk) contains its simple text name, version number, culture, and public key token. Assemblies are considered equivalent if they share the same complete name, excluding the revision of the version number. A private key can also be used by the creator of the assembly for strong naming. The public key token identifies which public key an assembly is signed with. Only the creator of the keypair (typically the .NET developer signing the assembly) can sign assemblies that have the same strong name as a previous version assembly, since he is in possession of the private key. Strong naming is required to add assemblies to the Global Assembly Cache. Security .NET has its own security mechanism with two general features: Code Access Security (CA), and validation and verification. Code Access Security is based on evidence that is associated with a specific assembly. Typically the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the intranet or Internet). Code Access Security 18

uses evidence to determine the permissions granted to the code. Other code can demand that calling code is granted a specified permission. The demand causes the CL to perform a call stack walk: every assembly of each method in the call stack is checked for the required permission; if any assembly is not granted the permission a security exception is thrown. Class library The .NET Framework includes a set of standard class libraries. The class library is organized in a hierarchy of namespaces. Most of the built-in APIs are part of either System.* or Microsoft.* namespaces. These class libraries implement a large number of common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation, among others. The .NET class libraries are available to all CLI compliant languages. The .NET Framework class library is divided into two parts: the Base Class Library and the Framework Class Library The Base Class Library (BC) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime.[12] The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL. The BCL classes are available in both .NET Framework as well as its alternative implementations including .NET Compact Framework, Microsoft Silverlight and Mono. The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework. It includes an expanded set of libraries, including Windows Forms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others. The FCL is much larger in scope than standard libraries for languages like C++, and comparable in scope to the standard libraries of Java. Memory management The .NET Framework CL frees the developer from the burden of managing memory (allocating and freeing up when done); it handles memory management itself by detecting when memory can be safely freed. Memory is allocated to instantiations of .NET types (objects) from the managed heap, a pool of memory managed by the CL. As long as there exists a reference to an object, which might be either a direct reference to an object or via a graph of objects, the object is 19

considered to be in use. When there is no reference to an object, and it cannot be reached or used, it becomes garbage, eligible for collection. NET Framework includes a garbage collector which runs periodically, on a separate thread from the application's thread, that enumerates all the unusable objects and reclaims the memory allocated to them. The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep garbage collector. The GC runs only when a certain amount of memory has been used or there is enough pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim memory are reached, the GC runs are non-deterministic. Each .NET application has a set of roots, which are pointers to objects on the managed heap (managed objects). These include references to static objects and objects defined as local variables or method parameters currently in scope, as well as objects referred to by CPU registers.[13] When the GC runs, it pauses the application, and for each object referred to in the root, it recursively enumerates all the objects reachable from the root objects and marks them as reachable. It uses .NET metadata and reflection to discover the objects encapsulated by an object, and then recursively walk them. It then enumerates all the objects on the heap (which were initially allocated contiguously) using reflection. All objects not marked as reachable are garbage.[13] This is the mark phase.[14] Since the memory held by garbage is not of any consequence, it is considered free space. However, this leaves chunks of free space between objects which were initially contiguous. The objects are then compacted together to make used memory contiguous again.[13][14] Any reference to an object invalidated by moving the object is updated by the GC to reflect the new location.[14] The application is resumed after the garbage collection is over. The GC used by .NET Framework is actually generational.[15] Objects are assigned a generation; newly created objects belong to Generation 0. The objects that survive a garbage collection are tagged as Generation 1, and the Generation 1 objects that survive another collection are Generation 2 objects. The .NET Framework uses up to Generation 2 objects.[15] Higher generation objects are garbage collected less frequently than lower generation objects. This helps increase the efficiency of garbage collection, as older objects tend to have a larger lifetime than newer objects.[15] Thus, by removing older (and thus more likely to survive a collection) objects from the scope of a collection run, fewer objects need to be checked and compacted.[15] 20

3.1.2About Java Script JavaScript is a programming language that is used to make web pages interactive. It runs on your visitors computer and so does not require constant downloads from your web site. JavaScript supports all the structured programming syntax in C (e.g., if statements, while loops, switch statements, etc.). One partial exception is scoping: C-style block-level scoping is not supported. JavaScript 1.7, however, supports block-level scoping with the let keyword. Like C, JavaScript makes a distinction between expressions and statements.

3.1.3About HTML HTML is a computer language devised to allow website creation. These websites can then be viewed by anyone else connected to the Internet. It is relatively easy to learn, with the basics being accessible to most people in one sitting; and quite powerful in what it allows you to create. It is constantly undergoing revision and evolution to meet the demands and requirements of the growing Internet audience under the direction of the W3C, the organization charged with designing and maintaining the language.

The definition of HTML is Hypertext Markup Language.

Hypertext is the method by which you move around on the web by clicking on special text called hyperlinks which bring you to the next page. The fact that it is hyper just means it is not linear i.e. you can go to any place on the Internet whenever you want by clicking on links there is no set order to do things in.

Markup is what HTML tags do to the text inside them. They mark it as a certain type of text (italicized text, for example).

HTML is a Language, as it has code-words and syntax like any other language. 21

How HTML Works HTML consists of a series of short codes typed into a text-file by the site author these are the tags. The text is then saved as a html file, and viewed through a browser, like Internet Explorer or Netscape Navigator. This browser reads the file and translates the text into a visible form, hopefully rendering the page as the author had intended. Writing your own HTML entails using tags correctly to create your vision. You can use anything from a rudimentary text-editor to a powerful graphical editor to create HTML.

3.1.4My-SQL MySQL is a relational database management system (RDBMS) that runs as a server providing multiuser access to a number of databases. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL is owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Sun Microsystems, a subsidiary of Oracle Corporation.
SQL ( sometimes referred to as Structured Query Language) is a programming language designed for managing data in relational database management systems (RDBMS). Originally based upon relational algebra and tuple relational calculus, its scope includes data insert, query, update and delete, schema creation and modification, and data access control.

3.2Hardware Required>>
1. Intel Pentium IV 2. 512 MB RAM 3. 80 GB Hard Disk

22

4) SYSTEM ANALYSIS:4.1 Existing System: The existing system does not use any computer based system. All the jobs are done manually. The job such as maintaining the information about the various authorized users like name,phone no,e mail id,date of arrival,credit cart information,DOB & many more. Informing the authorized member manually which is very time consuming process. Information about the various famous locations in India that has to be searched manually that takes time and consume many resources. The existing system had following Drawbacks: It was very time consuming Recording Information generated manually. The Activities are often prone to errors. The speed of processing of data is very slow. The information required was not readily available. Lots of paper work was there.

4.2Need for System:At present, all the operations are carried out manually. Sometimes, information is duplicated, filled incorrectly or missed. A new computerized system is needed to handle all these data integrity and consistency problems that arise when system is handled manually. (a) (b) I To improve quality of work and accuracy To improve work speed and accuracy To provide the easy and user friendly environment

23

(d) (e)

Get instant and detail information at single terminal The project would help in effective and systematic record keeping that is storing and retrieving of useful data.

4.3 Proposed System: The proposed system objectives are drawn to avoid the drawbacks of the Manual Gathering Of Information .The proposed system replaces inefficient process and timeconsuming task of the current system to be a simple, accurate and effective proposed system. The objective of this project is To make your travel experience a memorable with our years of experience and trust of thousand of clients..

24

Figure : Context data flow diagram for the proposed system

Modules of the project : Administrator This module is prepared for the administrator who is the only user having the authority to add, delete and modify the database. The administrator can avail these facilities only after proper login mechanism built in the system. 25

Registration This module is developed for new user can open an account with the web site to become a registered user. Through this module, personal information of users is gathered to allow them signing into the system. Once their username and password is created they can login into the system through login module.

Login This module is developed to allow the visitors and administrators to login into the system. Through the I/O/Update facility one can easily maintain the records in the

file. Moreover, the user will be able to get variety of reports, which is the most important part of this system like any other. A lot of effort and care has been taken in designing format. Most of the time, it is not possible to computerize the manual system completely and some things have to be left out. The system deals right from entering the records in the database to generation of the reports. The major advantage is the increase in the speed and efficiency of the work. Much of the tedious jobs in the old system are reduced. 4.4 Feasibility Study:A Feasibility Study is a test of system proposal regarding to its workability; impact on the organization; an effective use of resources. 4.4.1 Technical Feasibility: This application is technically feasible. Hardware Requirements: Processor Pentium IV 512 MB RAM 80 GB HDD LAN card Modem Internet Connection Monitor 26

 Keyboard and Mouse Software Requirements: For Development Purpose: MICROSOFT VISUAL STUDIO 2008(ASP.NET) MS-ACCESS For Work Station: Internet Explorer. Internet Connection Mail Server Windows Operating System

4.4.2 Economical feasibility:

Economic justification is generally the Bottom Line consideration for most systems. Economic justification includes a broad range of concerns that includes cost benefit analysis. In this we weight the cost and the benefits associated with the candidate system and if it suits the basic purpose of the organization i.e. profit making, the project is making to the analysis and design phase.

4.4.3 Operational Feasibility:

It is mainly related to human organizations and political aspects. The points to be considered are: What changes will be brought with the system? What organization structures are disturbed? What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform. 27

5) System Requirement Specification:5.1 Introduction to SRS:The Software Requirements Specifications presents the overall information about the interface, flow of data and constraints for the products. An SRS is a document that completely describes what the proposed software should do without describing how the software will do it. Therefore it describes the complete external behavior of proposed software. An SRS is used to define needs and expectations of the users. It serves as a contract document between customer and developer. It is produced at the culmination of analysis task. The function and performance allocated to software as part of Software Engineering is refunded by: Establishing a complete introduction General description Information description A detailed functional description, and Other information pertinent to requirement. This document, that is, software requirements specifications describes the overall requirement that will be satisfied by the final product development. It serves as the foundation for subsequent software engineering activities. It describes the function of computer-based system and the constraints that will govern the development.

28

5.2 Software Engineering Paradigm Applied: Project Planning The key to a successful project is in the planning. Creating a project plan is the first thing you should do when undertaking any kind of project. Often project planning is ignored in favor of getting on with the work. However, many people fail to realize the value of a project plan in saving time, money and many problems. Project Planning Objective: Coordinate the various interrelated processes of the project. Ensure project includes all the work required, and only the work required, to complete the project successfully. Ensure that the project is completed on time and within budget. Ensure that the project will satisfy the needs for which it was undertaken. Ensure the most effective use of the people involved with the project. Promote effective communication between the projects team members and key members. Ensure that project risks are identified, analyzed, and responded.

Need and Importance: Quality delivery Customer satisfaction Structured Managing the manpower

29

6) System Design & development:6.1Introduction: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: 1) 2) Logical Design 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. The logical design also 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. 6.2Logical 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.

30

Output design is one of the most important features of the information system. When the outputs is not of good quality the users will be averse to use the newly designed system and may not use the system. There are many types of 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 users, 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., programlisting 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 designing 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. 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 is needed. While designing output for project based Attendance Compilation System, the following aspects of outputs designing were taken into consideration. The outputs (i.e., well formatted table outputs in the screen itself) designed are simple to read and interpret. 31

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 users are also taken into account. 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 ACS 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. Output Sources: Output contents originate from these sources: Retrieval from a data source. Transmission from a process or system activity. Directly from an input source.

The information produced in an output can be presented as Tabular contents Graphic format Using Icons

32

 Output Definition: The output should be defined in terms of: Types of outputs Content-headings, numeric, alphanumeric, etc., Format-hardcopy, screen, microfilm, etc., Location-local, remote, transmitted, etc., Frequency-daily, weekly, hourly, etc., Response-immediate with in a period, etc.,

Data items The name given to each data item should be recorded and its characteristics described clearly in a standard form: Whether alphanumeric or numeric Legitimate and specific range of characteristics Number of characters Positions of decimal point, arithmetic design, etc.,

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. Input Design consists of developing specifications and procedures for data preparation Steps necessary to put data into a usable form for processing. Data entry, the activity of putting data into the computer processing. 33

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. Input stages several activities have to be carried out as part of te 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 transmission(i.e., transporting the data) Data validation(i.e., checking the input data) Data correction(i.e.,correcting the errors) Input Performa were designed, after a careful discussion with users. It was attempted to cover all user requirements. Designed Performa were given to user for any suggestion and final approval. Various data items were identified and wherever necessary were recorded. 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 are 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. 34

Wherever 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., 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 deigns of CRM is so designed that it ensures easy and error free data entry mechanism. Once one is sure of input data the output formatting becomes an routine work.

SOFTWARE DESIGN The purpose of this phase is to plan a solution for the problem specified by the requirement document. This is first step in moving from the problem domain to solution domain. Designing activity is divided into two parts. a) System Design It aims to identify the modules that should be in the system, the specification of these modules and how they interact with each other to produce the desired result. b) Detailed Design The internal goal of each of the modules specified in the system design is decided

DATABASE DESIGN A database is a collection of inter-related data stored with a minimum of redundancy to serve many applications. It minimizes the artificiality embedded in using separate files. The primary objectives are fast response time to enquires, more information at low cost, control of redundancy, clarity and ease of use, accuracy and fast recovery. The organization of data in a database aims to achieve three major objectives, they are data integration, data integrity and data independence. 35

During the design of the database at most care has been taken to keep up the objectives of the database design. CODE DESIGN The process of code is to facilitate the identification and retrieve of items of information. The code should be simple and easy to understandable. The codes were designed in such a way that the features such as optimum human oriented use and machine efficiency are unaffected. For the code to be designed effectively, the following characteristics were also considered while designing the code. Uniqueness Versatility Stability Simplicity Consciousness

The code should be adequate for present and anticipated data processing for machine and human use. Care was taken to minimize the clerical effort and computer time required to continue operation.

PROCESS DESIGN The process can be conceptualized in such a way to keep the methodology of main module process along with some auxiliary task, which will run concurrently with the main program. The top-down approach is maintained so as to keep track of the process, which satisfies the maintenance reliability testing requirements. The concurrency of the data is checked during data entry, by means of validation check for data in each field.

36

6.3DATA FLOW DIAGRAM:-

Data Flow Diagramming is a means of representing a system at any level of detail with a graphic network of symbols showing data flows, data stores, data processes, and data sources/destination.

DFD OF PROJECT

DFD: Level 0

37

DFD: Level 1

38

DFD: Level 2

39

6.4Entity Relationship Diagram:-

40

6.5 Database Design:The most important aspect of the system is data design . The data must be organized according to the system requirements. The database approach is used to store and organize the data in developing the system . The database is an integrated collection of data stored in different types of tables. Some general objectives in establishing a database are as follows: Integrating all data Incorporate updations easily Provide data security unauthorized users

6.5.1 Database Tables:6.5.1.1 CLIENT TABLE>>

TID

TEXT

CLID

AUTONO.

CNAME

TEXT

CADD.

TEXT

CPHONENO.

TEXT

CCREDIT

TEXT

41

CEXPIRY

TEXT

CEMAIL

TEXT

DATEOFTRAVEL

TEXT

6.5.1.2 USER INFO TABLE>> UNAME UPASS TEXT TEXT

6.5.1.3 REGISTER USER TABLE>>

ID UNAME UPASS RNAME REMAIL RADD. RMOBNO. RAPPROVED

TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT

42

6.5.1.4 HOTEL FACILITIES TABLE>> HOTELID FACILITIESID FACILITIESTYPE CHARGES TEXT TEXT TEXT CURRENCY

6.5.1.5 LOCATION TABLE>> LID MAININFO MAINPIC CITY STATE PIC1 PIC2 PIC3 PIC4 INFO1 INFO2 INFO3 INFO4 PRICE OFFERPRICE TEXT MEMO TEXT TEXT TEXT TEXT TEXT TEXT TEXT MEMO MEMO MEMO MEMO CURRENCY CURRENCY

43

6.5.1.6 HOTEL TABLE>> HOTELID LID HOTELNAME HOTELADD. MAINPICHOTEL PIC1 PIC2 PIC3 PIC4 HOTELMAININFO. TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXT MEMO

6.5.1.7 ADD TO CART TABLE>> TID PRODUCTNAME PRODUCTTYPE PRODUCTID PRODUCTPRICE PAID TEXT TEXT TEXT TEXT TEXT TEXT

44

6.5.1.8 CONTACT US TABLE>>

CID NAME MESSAGE TE PHONENO.

AUTONO. TEXT TET TEXT TEXT

6.5.1.9 RID TABLE>>

RID

TEXT

6.5.1.10 TID TABLE>> TID TEXT

45

7) Module Description:Graphical User Interface

MVC Model This section gives an overview of the MVC Model to assist the Employees / HR Admin to better understand the working on HRMS. HRMS is designed on the Eclipse. MVC Environment Model-view-controller(MVC) is an architectural pattern used in software engineering. Successful use of the pattern isolates business logic from user interface considerations, resulting in an application where it is easier to modify either the visual appearance of the application or the underlying business rules without affecting the other. In MVC, the model represents the information (the data) of the applications; the view corresponds to elements of the user interface such as text, checkbox items, and so forth; and the controller manages the communication of data and the business rules used to manipulate the data to and from the model.

46

7.1Modules of Project and Description:-

HomePage>>

Menu Descriptions:-

Home Page This is a home page specifying the details of famous locations in india with search facilities provided and checking of authorized users.

47

 View points In this page all the information about locations are available and information about the hotels to stay.. Register In this page user can register by giving their details. Add To cart In this page ,the information about the type of product that has been purchased by the user with our offerprice and total bill will be shown. Contact Us In this Page Honour shows the Address and contact no. to .ontact with us. About Us In this page the information about Our Royal Indian Tour is mentioned

48

LOCATION INFO >> In this page information about the locations that has been provided by us will be shown:

49

50

LOCATION INFO WITH OFFER PRICE>>

51

HOTEL INFO>>

52

FIND HOTEL & ADD LOCATION TO ADD TO CART>>

53

ADD HOTEL TO ADD TO CART>>

54

About us>>

55

ADD TO CART>>

56

PAY NOW>>

57

BOOKING>>

58

CONTACT US>>

59

REGISTER>>

60

WELCOME & THANKS AFTER REGISTERATION>>

61

MAIN ADMIN>>

Description:This is the home Page of Admin panel .when the admin login he/she will enter in the Home page of Admin side. Admin can navigate through this Home page.

62

Welcome to the Administrator Section of www.abktour.com

The Admin Panel has Some Menus: Login Logout Add location Update location Add hotel Update hotel Hotel facilities Paid Check mails

63

Add location:-

Description: This page is used to add information about location like information about particular location & various view points to visit within that location.

64

UPDATE LOCATION:-

Description: This page is used to update information about location like information about particular location & various view points to visit within that location.

65

ADD HOTEL:-

Description: This page is used to add information about hotel like information about particular hotel & various facilities.

66

UPDATE HOTEL:-

Description :This page is used to update information about hotel like information about particular hotel & various facilities.

67

HOTEL FACILITIES:-

Description :This page provides all the facilities available in hotel.

68

CHECK MAILS:-

Description :This page is used to check the mail sent by user .

69

PAID:-

Description :This page is used to check whether the payment has been done or not.

8) System Testing:1) Introduction: System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

70

As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limiting type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole. 2) Testing Objective:Testing is the process of executing a program with the intent of finding an error. A good test case is the one that has a high probability of finding an as-yet-undiscovered error. A successful test is one that uncovers an as-yet-undiscovered error. The objective of testing are: Software quality improvement. Verification and Validation. Software Reliability Estimation. These objectives imply dramatic change in viewpoint. They move counter to the commonly held view that a successful test is one in which no errors are found. Our objective is to design tests that systematically uncover different classes of errors and to do so with minimum amount of time and effort. If testing is conducted successfully (according to the objective stated previously), it will uncover errors in the software. As a secondary benefit, testing demonstrates that software functions appear to be the working according to the specification, that behavioral and performance requirements appear to have been met. In addition, data collected as testing conducted provide a good indication of software reliability and some indication of software quality as a whole but testing cannot show the absence of errors and defects, it can show only that software errors and defects are present. It is important to keep this (rather gloomy) statement in mind as testing is being conducted.

71

3)Types of Testing: They are various types of testing as follows: Black box testing - Internal system design is not considered in this type of testing. Tests are based on requirements and functionality. White box testing - This testing is based on knowledge of the internal logic of an applications code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions. Unit testing - Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses. Incremental integration testing - Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers. Integration testing - Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems. Functional testing - This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application. System testing - Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system. End-to-end testing - Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. Sanity testing - Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.

72

Regression testing - Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types. Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application. Load testing - Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the systems response time degrades or fails. Stress testing - System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load. Performance testing - Term often used interchangeably with stress and load testing. To check whether system meets performance requirements. Used different performance and load tools to do this. Usability testing - User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing. Install/uninstall testing - Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment. Recovery testing - Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. Security testing - Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access. Checked if system, database is safe from external attacks. Compatibility testing - Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

73

Comparison testing - Comparison of product strengths and weaknesses with previous versions or other similar products. Alpha testing - In house virtual user environment can be created for this type of testing. Testing is done at the end of development. Still minor design changes may be made as a result of such testing. Beta testing - Testing typically done by end-users or others. Final testing before releasing application for commercial purpose. Software Testing Life Cycle Software testing life cycle identifies what test activities to carry out and when (what is the best time) to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle. Software Testing Life Cycle consists of six (generic) phases:

Test Planning, Test Analysis, Test Design, Construction and verification, Testing Cycles, Final Testing and Implementation and Post Implementation.

Software testing has its own life cycle that intersects with every stage of the SDLC. The basic requirements in software testing life cycle is to control/deal with software testing Manual, Automated and Performance. Test Planning This is the phase where Project Manager has to decide what things need to be tested, do I have the appropriate budget etc. Naturally proper planning at this stage would greatly reduce the risk of low quality software. This planning will be an ongoing process with no end point. 74

The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.). Almost all of the activities done during this stage are included in this software test plan and revolve around a test plan. Test Analysis Once test plan is made and decided upon, next step is to delve little more into the project and decide what types of testing should be carried out at different stages of SDLC, do we need or plan to automate, if yes then when the appropriate time to automate is, what type of specific documentation I need for testing. Proper and regular meetings should be held between testing teams, project managers, development teams, Business Analysts to check the progress of things which will give a fair idea of the movement of the project and ensure the completeness of the test plan created in the planning phase, which will further help in enhancing the right testing strategy created earlier. We will start creating test case formats and test cases itself. In this stage we need to identify which test cases to automate, begin review of documentation, i.e. Functional Design, Business Requirements, Product Specifications, Product Externals etc. We also have to define areas for Stress and Performance testing. Test Design Test plans and cases which were developed in the analysis phase are revised. Functional validation matrix is also revised and finalized. In this stage risk assessment criteria is developed. If you have thought of automation then you have to select which test cases to automate and begin writing scripts for them. Test data is prepared. Standards for unit testing and pass / fail criteria are defined here. Schedule for testing is revised (if necessary) & finalized and test environment is prepared. Construction and verification In this phase we have to complete all the test plans, test cases, complete the scripting of the automated test cases, Stress and Performance testing plans needs to be completed. We have to support the

75

development team in their unit testing phase. And obviously bug reporting would be done as when the bugs are found. Integration tests are performed and errors (if any) are reported. Testing Cycles In this phase we have to complete testing cycles until test cases are executed without errors or a predefined condition is reached. Run test cases --> Report Bugs --> revise test cases (if needed) --> add new test cases (if needed) --> bug fixing --> retesting (test cycle 2, test cycle 3.). Final Testing and Implementation In this we have to execute remaining stress and performance test cases, documentation for testing is completed / updated, provide and complete different matrices for testing. Acceptance, load and recovery testing will also be conducted and the application needs to be verified under production conditions. Post Implementation In this phase, the testing process is evaluated and lessons learnt from that testing process are documented. Line of attack to prevent similar problems in future projects is identified. Create plans to improve the processes. The recording of new errors and enhancements is an ongoing process. Cleaning up of test environment is done and test machines are restored to base lines in this stage. Testing is usually performed for the following purposes: To improve quality. As computers and software are used in critical applications, the outcome of a bug can be severe. Bugs can cause huge losses. Bugs in critical systems have caused airplane crashes, allowed space shuttle missions to go awry, halted trading on the stock market, and worse. In a computerized embedded world, the quality and reliability of software is a matter of life and death..Quality means the conformance to the specified design requirement. Being correct, the minimum requirement of quality, means performing as required under specified circumstances. Debugging, a narrow view of software testing, is performed heavily to find out design defects by the programmer. The imperfection of human nature makes it almost impossible to make a 76

moderately complex program correct the first time. Finding the problems and get them fixed , is the purpose of debugging in programming phase. For Verification & Validation (V&V) Just as topic Verification and Validation indicated, another important purpose of testing is verification and validation (V&V). Testing can serve as metrics. It is heavily used as a tool in the V&V process. Testers can make claims based on interpretations of the testing results, which either the product works under certain situations, or it does not work. We can also compare the quality among different products under the same specification, based on results from the same test. Good testing provides measures for all relevant factors. Any system where human lives are at stake must place extreme emphasis on reliability and integrity. In the typical business system usability and maintainability are the key factors, while for a one-time scientific program neither may be significant. We cannot test quality directly, but we can test related factors to make quality visible. Quality has three sets of factors -- functionality, engineering, and adaptability. A testable design is a design that can be easily validated, falsified and maintained. For reliability estimation Software reliability has important relations with many aspects of software, including the structure, and the amount of testing it has been subjected to. Based on an operational profile (an estimate of the relative frequency of use of various inputs to the program), testing can serve as a statistical sampling method to gain failure data for reliability estimation.

77

9)System Implementation:Introduction System implementation is the stage when the user has thoroughly tested the system and approves all the features provided by the system. The various tests are performed and the system is approved only after all the requirements are met and the user is satisfied. The new system may be totally new, replacing an existing manual or automated system, or it may be a major modification to an existing system. In either case, proper implementation is essential to provide a reliable system to meet organizational requirements. Successful

implementation may not guarantee improvement in the organization using the new system (that is a design question), but improper will prevent it. Implementation is the process of having systems personnel check out and put new equipment into use, train users, install the new application and construct any files of data needed to use it. This phase is less creative than system design. Depending on the size of the organization that will be involved in using the application and the risk involved in its use, systems developers may choose to test the operation in only one area of the firm with only one or two persons. Sometimes, they will run both old and new system in parallel way to com-pare the results. In still other situations, system developers stop using the old system one day and start using the new one the next. The implementation of the web based or LAN based networked project has some extra steps at the time of implementation. We need to configure the system according the requirement of the software.

78

MAINTENANCE:-

Maintenance or enhancement can be classified as: Corrective Adaptive Perfective Corrective maintenance means repairing processing or performance failures or making changes because of previously uncorrected problems or false assumptions. Adaptive maintenance means changing the program function Perfective maintenance means enhancing the performance or modifying the program(s) to respond to the users additional or changing needs. Maintenance is actually the implementation of the post implementation review plan. As important as it is, many programmers and analysts are reluctant to perform or identify themselves with the maintenance effort. There are psychological, personality and professional reasons for this. In any case, a first class effort must be made to ensure that software changes are made properly and in time to keep the system in tune with user specifications

79

10) FUTURE EXTENSION:The project ROYAL INDIAN TOUR is to make your travel experience a memorable with our years of experience & trust of thousands of clients. The software takes care of presenting the best our country has to offer which not only reflects clients needs but also reveal the beauty of the country and culture and is capable to provide easy and effective storage of information related to members that are authorized. It provide members details including their name., Contact no., and about their on line information. .

Conclusion
This project www.abktour.com developed as per the requirement and necessities of tourists... The main feature of this project is providing user-friendly interface for managing the information of members and keep Information about their date of arrival . Each activity is performed in computerized way rather than manually which is time consuming.

80

11) BIBLIOGRAPHY:-

SYSTEM ANALYSIS AND DESIGN SOFTWARE ENGINEERING E-COMMERCE ASP.NET MS-ACCESS WWW.GOOGLE.COM WWW.YAHOO.COM

81

82