You are on page 1of 87

Sl.No 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22.

Contents Introduction and Objective Purpose and Scope Language Outlook About Oracle 10g System Specification Requirement Analysis System Analysis Feasibility study System Design DFDs (Data Flow Diagram) Normalization E-R Diagram (Entity Relationship Diagrams Database Design Screen Layout Code Generation Software Testing & Implementation Security Majors Taken GANT Chart PERT Chart Future Scope of the Project Conclusion Bibliography

Page No 2 3 4 8 12 13 15 17 19 23 31 32 36 45 52 73 81 83 84 85 86 87

MOVE ON CLICK

Page: 1/87

MOVE ON CLICK
Introduction: . www.moveonclick.com is a move on click web application which has been introduced to Move on click, Bhubaneswar. It enables customer needing a cab for their various purposes and to book in a convenient date and time for their journey. It also provides various type of vehicle of both Ac and Non-Ac as per the requirement of the customer. This particular project contains 2 different parts depending on its authorization of use as 1.Customer Interface and 2.Admin Interface. The customer interface provides the customer to choose vehicle and to request for a booking for his/her tour. Its the interface through which a customer will enable to see the detail price list for different vehicles so that he /she can plan his tour in a convenient manner before booking any vehicle. In the other hand the admin interface of this project is for the owner of this project and protected with a personal username and changeable password. Here the owner or admin person can confirm a booking request, will able to maintain his accounts, can see various reports, etc which will minimize his time as well as his workload.

Objective: The main aim of Move on click is providing fastest booking support for the customers who are visiting to our state and getting support for any vehicle. We provide these facilities to those customers from outside our state. They can book online from their state and get the facility.

MOVE ON CLICK

Page: 2/87

Purpose and Scope


Purpose Here the Move on click is to replace the existing manual system with a software solution. It helps to provide effective communication between different customer and vehicle availability and provides better services for the people at various places also. The menu may contain items such asHome: - Its a hyperlink to the Home page. About: - Its a hyperlink to the About page which contain company profile. Fares: - Its a hyperlink to the Fares page which contains rate chat for different

vehicles. Feedback: - Its a hyperlink to the Feedback page where the customers can give their

feedback. Lost Property: - Its a hyperlink to the Lost Property page where customer can

enquiry for their lost property during their journey. Contact: - Its a hyperlink to the Contact page which contains contact information of

the company. Enquiry Now: - Its a hyperlink to the Enquiry Now page where customers can

easily find their current cab booking status. For Taxi Owner: - This link is only for the admin access.

Scope The scope of this website is global i.e. it should be able to be accessed from anywhere through internet

MOVE ON CLICK

Page: 3/87

LANGUAGE OUTLOOK Internet Terminology: Java and Internet: The Internet helped catapult Java to the forefront of programming and Java in turn has had a profound effect on the Internet. The reason is simple: Java expands the universe of objects that can move about freely in cyberspace. In a network, there are two broad categories of objects transmitted between the Server and your Personal Computer: passive information and dynamic, active programs like an object that can be transmitted to your computer, which is a dynamic, self-executing program. Such a program would be an active agent ton the client computer, yet the server would initiate it. As desirable as dynamic, networked programs are, they also present serious problems in the areas of security and portability. Prior to Java cyberspace was effectively closed to half the entities that now live there. Java addresses these concerns and doing so, has opened the door to an exiting a new form of program. The rise of server-side Java applications is one of the latest and most exciting trends in Java programming. It was first hyped as a language for developing elaborate client-side web content in the form of applets. Now, Java is coming into its own as a language ideally suited for server-side development. Businesses in particular have been quick to recognize Javas potential on the server-Java is inherently suited for large client/server applications. The cross platform nature of Java is extremely useful for organizations that have a heterogeneous collection of servers running various flavors of the Unix of Windows operating systems. Javas modern, object-oriented, memory-protected design allows developers to cut development cycles and increase reliability. In addition, Javas built-in support for networking and enterprise API provides access to legacy data, easing the transition from older client/server systems. Java Servlets are a key component of server-side java development. A Servlets is a small, plug gable extension to a server that enhances the servers functionality. Servlets allow developers to extend and customize and Java enabled server a web server, a mail server, an application server, or any custom server with a hitherto unknown degree of portability, flexibility and ease. Java Server Page (Jsp): Java Server Pages is a simple, yet powerful technology for creating and maintaining dynamic-content web pages. Based on the Java programming language, Java Server Pages offers proven portability, open standards, and a mature re-usable component model. Portability:

MOVE ON CLICK

Page: 4/87

Java Server Pages files can be run on any web server or web-enabled application server that provides support for them. Dubbed the JSP engine, this support involves recognition, translation and management of the Java Server Pages lifecycle and its interaction with associated components. The JSP engine for a particular server might be built-in or might be provided through a 3rd party add-on. As long as the server on which you plan to execute the Java Server Pages supports the same specification level as that to which the file was written, no change should be necessary as you move your files from server to server. Note, however, that instructions for the setup and configuration of the files may differ between files. Composition: It was mentioned earlier that the Java Server Pages architecture could include reusable Java components. The architecture also allows for the embedding of a scripting language directly into the Java Server Pages file. The components current supported include Java Beans and Serves. As the default scripting language, Java Server Pages use the Java Programming language. This means that scripting on the server side can take advantage of the full set of capabilities that the Java programming language offers. Processing: A Java Server Pages file is essentially an HTML document with JSP scripting or tags. It may have associated components in the form of class, .jar, or .ser files- -or it may not. The use of components is not required. The Java Server Pages file has a .jsp extension to identify it to the server as a Java Server Pages file. Before the page is served, the Java Server Pages syntax is parsed and processed into a servlet on the server side. The servlet that is generated, outputs real content in straight HTML for responding to the customer. Because it is standard HTML, the dynamically generated response looks no different to the customer browser than a static response. Access Models: A Java Server Pages file may be accessed in at least two different ways: A client request comes directly into a Java Server Page. Bean

Request

Browser

JSP

Response

MOVE ON CLICK

Page: 5/87

In this scenario, suppose the page accessed reusable Java Bean components that perform particular well-defined computations like accessing a database. The result of the Beans computations, called result sets is stored within the Bean as properties. The page uses such Beans to generate dynamic content and present it back to the client. A request comes through a servlet. SERVLET
JDBC

Bean
Browser
Request

Result Bean

Database

Response

JSP The servlet generates the dynamic content. To handle the response to the client, the servlet creates a Bean and stores the dynamic content (sometimes called the result set) in the Bean. The servlet then invokes a Java Server Page that will present the content along with the Bean containing the generated from the servlet. There are two APIs to support this model of request processing using Java Server Pages. One API facilitates passing context between the invoking servlet and the Java Server Page. The other API lets the invoking servlet specify which Java Server Page to use. In both of the above cases, the page could also contain any valid Java code. The Java Server Pages architecture separation of content from presentation- -it does not mandate it. JDBC requires that the SQL statements be passed as Strings to Java methods. For example, our application might present a menu of database tasks from which to choose. After a task is selected, the application presents prompts and blanks for filling information needed to carry out the selected task. With the requested input typed in, the application then automatically invokes the necessary commands. In this project we have implemented three-tier model, commands are sent to a middle tier of services, which then send SQL statements to the database. The database

MOVE ON CLICK

Page: 6/87

process the SQL statements and sends the results back to the middle tier, which then sends them to the user. JDBC is important to allow database access from a Java middle tier. What Is JDBCTM? JDBCTM is a JavaTM API for executing SQL statements. (As a point of interest, JDBC is a trademarked name and is not an acronym; nevertheless, JDBC is often thought of as standing for "Java Database Connectivity".) It consists of a set of classes and interfaces written in the Java programming language. JDBC provides a standard API for tool/database developers and makes it possible to write database applications using a pure Java API. Using JDBC, it is easy to send SQL statements to virtually any relational database. In other words, with the JDBC API, it isn't necessary to write one program to access a Sybase database, another program to access an Oracle database, another program to access an Informix database, and so on. One can write a single program using the JDBC API, and the program will be able to send SQL statements to the appropriate database. And, with an application written in the Java programming language, one also doesn't have to worry about writing different applications to run on different platforms. The combination of Java and JDBC lets a programmer write it once and run it anywhere. Java being robust, secure, easy to use, easy to understand, and automatically downloadable on a network, is an excellent language basis for database applications. What is needed is a way for Java applications to talk to a variety of different databases. JDBC is the mechanism for doing this. JDBC extends what can be done in Java. For example, with Java and the JDBC API, it is possible to publish a web page containing an applet that uses information obtained from a remote database. Or an enterprise can use JDBC to connect all its employees (even if they are using a conglomeration of Windows, Macintosh, and UNIX machines) to one or more internal databases via an intranet. With more and more programmers using the Java programming language, the need for easy database access from Java is continuing to grow. MIS managers like the combination of Java and JDBC because it makes disseminating information easy and economical. Businesses can continue to use their installed databases and access information easily even if it is stored on different database management systems. Development time for new applications is short. Installation and version control are greatly simplified. A programmer can write an application or an update once, put it on the server, and everybody has access to the latest version. And for businesses selling information services, Java and JDBC offer a better way of getting out information updates to external customers. Connection: MOVE ON CLICK
Page: 7/87

A connection object represents a connection with a database. A connection session includes the SQL statements that are executed and the results that are returned over the connection. A single application can have one or more connections with a single database, or it can have connections with many different databases. Opening A Connection: The standard way to establish a connection with a database is to call the method DriverManager.getConnection. This method takes a string containing a URL. The Driver Manager class, referred to a the JDBC management layer, attempts to locate a driver than can connect to the database represented Driver classes, and when the method get Connection is called, it checks with each driver in the list until it finds one that can connect uses this URL to actually establish the connection. <Sub protocol>-usually the driver or the database connectivity mechanism, which may be supported by one or more drivers. A prominent example of a sub protocol name is oracle, which has been reserved for URLs that specify thin-style data source names. <Sub name>- a way to identify the database. The sub names can vary, depending on the sub protocol, and it can have a sub name with any internal syntax the driver writer chooses. The point of a sub name is to give enough information to locate the database. Sending Statement: Once a connection is established, it is used to pass SQL statements to its underlying database. JDBC does not put any restrictions on the kinds of SQL statements that can be sent; this provides a great deal of flexibility, allowing the use of database-specific statements or even non-SQL statements. It requires, however, that the user be responsible for making sure that the underlying database can process the SQL statements being sent and suffer the consequences if it cannot. Driver Manager: The Driver Manager class is the management layer of JDBC, working between the user and the drivers. It keeps track of the drivers that are available and handles establishing a connection between a database and the appropriate driver. It addition, the driver manager class attends to things like driver login time limits and the printing of log and tracing messages. The only method in this class that a general programmer needs to use directly is DriverManager.getConnection. As its name implies, this method establishes a connection to a database.

MOVE ON CLICK

Page: 8/87

ORACLE 10g
Introduction to Oracle: Any programming environment used to create containers, to manage human data, in the conceptualization as a Data Management System. Traditionally, the block of human data being managed is called a Database. Hence, in very simple terms, these programming environments can the conceptualized as Database Management Systems, in short DBM systems. All Databases Management Systems (that is, Oracle is DBMS) allow users to create containers for data stories and management. These containers are called cells. The minimum information that has to be given to Oracle for a suitable container to be constructed, which can hold free from human data, is, 1. 2. conceptualized as follows. Basic Database Concepts: A database is a corporate collection of data with some inherent meaning, designed, built and populated with data for a specific purpose. A database stores data that is useful to us. This data is only a part of the entire data available in the world around us. To be able to successfully design and maintain databases we have to do the following: Identify which part of the worlds data is of interest to us. Identify what specific objects in that part of the worlds data are of interest to us. Identify a relationship between the objects. Hence the objects, their attributes and the relationship between them that are of interest to us are still owed in the database that is designed, built and populated with data for a specific purpose. Characteristics of a Database Management System: 1. It represents a complex relationship between data. 2. Keeps a tight control of debtor redundancy. 3. Enforces user-defined rules to ensure integrity of table data. 4. Has a centralized data dictionary for the storage of information pertaining to data and its manipulation. 5. Ensures that data can be shared across applications. 6. Enforces data access authorization has automatic, intelligent backup and recovery procedures for data. The cell name The cell length

Another name that programming environments use for a Cell is Field. These can the

MOVE ON CLICK

Page: 9/87

7. Have different interfaces via which users can manipulate data. Relational Database Management: A relational database management system uses only its relational capabilities to manage the information stored in its databases. Information representation: All information stored in a relational database is represented only by data item values, which are stored in the tables that make up the database. Associations between data items are not logically represented in any other way, such as the use of pointers from one table to the other. Logical Accessibility: Every data item value stored in relational database is accessible by stating the nature of the table it is stored in, the name of the column under which it is stored and the value of the primary key that defines the row in which it is stored.

Representation of Null Values: The database management system has a consistent method for representing null values. For example, null values for numeric data must be distinct from zero or any other numeric and for the character data it must be different from a string of blanks or any other character value. Catalogue Facilities: The logical description of the relation database is represented in the same manner as ordinary data. This is done so that the facilities of the relation database management system itself can be used to maintain database description. Data Language: The relational database management system may support many types of languages for describing data and accessing the database. However, there must be at least one language that uses ordinary character strings to support the definition of data, the definition of views, the manipulation of data, constraints on data integrity, information concerning authorization and the boundaries for recovery of units. View Updatability: Any view that can be defined using combination of basic tables, that are theoretically updateable, these capital of being updated by the relational database management system. Insert Update and Delete:

MOVE ON CLICK

Page: 10/87 10/87

Any operand that describes the results of a single retrieval operation is capable of being applied to an insert update or delete operation as well. Physical Data Independence: Changes made to physical storage representation or access methods do not require changes to be made to application programmers. Logical Data Independence: Changes made to tables, that do not modify any data stored in that table, do not require changes to be made to application programmers. Integrity Constraints: Constraints that apply to entity integrity and referential integrity are specifiable by the data language implemented by the database management system and not by the statements coded into the application program. Database Distribution: The data language implemented by the relation database management system supports the ability to distribute the database without requiring changes to be made to application programmers. This facility must be provided in the data language, whether or not the database management system itself supports distributed databases. Non- Subversion: If the relational database management system supports facilities that allow application programmers to operate on the tables a row at a time, an application programmer using this type access is prevented from by passing entity integrity or referential integrity constraints that are defined for the database.

MOVE ON CLICK

Page: 11/87 11/87

SYSTEM SPECIFICATION Hardware and Software requirements The system must be user friendly. The system must be able to handle large volume of data. Processing speed of the system should be huge.

Hardware Specification The software has been developed on computers with the following specifications. The Client Machines Processor Speed RAM Hard Disk Key Board (104 keys) Printer Software Requirements : Intel Pentium IV : 3.2GHz : 512 MB : 160 GB : Standard : Laser Printer

Operating System Database

: WinXP ,Windows 7(32bit) : Oracle 10g XE

Database Connectivity: JDBC Application Tools Server Application Web Server : Dreamweaver 8.0 : JSP / Servlets, JDK 1.6 : Apache Tomcat 6.0.20

MOVE ON CLICK

Page: 12/87 12/87

REQUIREMENT ANALYSIS

Some of the features expected in the site were: 1. Rich presentation, smoother site navigation, wider browser compatibility with w3c validation. 2. Gives the idea about different holiday packages. 3. Classification of vehicles to offer to book with their own rate plans. 4. Set community to apply on different states. 5. Online configuration of members for connecting from various areas to the community. 6. Admin users with different access level. Some of the features were expected as Site Administrator 1. Content management of each webpage with great flexibility to control the webpage content. 2. Tracking of member status and sending the message to each member individually. 3. Administrative privileges based on different rights to access the administrative area

Our Solution We developed entire solution based on requirements. This system has the full control on the type of content like single columnar content or dual columnar content menu with flexibility of ordering of menu and submenu under it. Page heading images for each different page, banners and on each page with dynamic CSS can change the look of color and presentation of each page. The option of changing the content on any part of the webpage is like middle portion and right potion of the webpage. The component of the content is to be reused to get displayed on more than one webpage. Our work has turned out an outstanding result at the end. Customer can get the idea of the using the web-sites based on the configuration they apply or the community they choose. Full project was commenced starting from requirement analysis till the site went live and back office functionality was developed offshore at our premises in India.

MOVE ON CLICK

Page: 13/87 13/87

OVERALL EXPLANATION Goals of proposed system 1. Planned approach towards working: - The working in the organization will be well planned and organized. The data will be stored properly in data stores, which will help in retrieval of information as well as its storage. 2. Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be done correctly and it ensures that whatever information is coming from the centre is accurate. 3. Reliability: - The reliability of the proposed system will be high due to the above stated reasons. The reason for the increased reliability of the system is that now there would be proper storage of information. 4. No Redundancy: - In the proposed system utmost care would be that no information is repeated anywhere, in storage or otherwise. This would assure economic use of storage space and consistency in the data stored. 5. Immediate retrieval of information: - The main objective of proposed system is to provide for a quick and efficient retrieval of information. Any type of information would be available whenever the user requires. 6. Immediate storage of information: - In manual system there are many problems to store the largest amount of information. 7. Easy to Operate: - The system should be easy to operate and should be such that it can be developed within a short period of time and fit in the limited budget of the user.

MOVE ON CLICK

Page: 14/87 14/87

SYSTEM ANALYSIS System analysis is a process of gathering and interpreting facts, diagnosing problems and using the information to recommend improvements to the system. In this step the requirements gathered by various processes and analyzed. The requirements are gathered from the customer in the following manner. 1. By interacting with the customers, end users. 2. By interviewing customers or end users. 3. By studying existing documents of the reservation system. 4. To collect all possible information regarding the system. Then the analysis of the gathered information is done and the anomalies present in the system are identified and the required actions are taken to remove that. Then the functional and non-functional requirements are identified and the SRS document is prepared. Analysis is the focus of system developing and is the stage when system designers have to work at two levels of definition regarding the study of situational issues and possible solutions in terms of what to do and how to do. System Study Definition of the System:A system is an orderly grouping of independent components linked together according to a plan to achieve a specific objective. Its main characteristics are organization, interaction, independent, integration and central objective a system does not necessarily mean to a computer system. It may be a manual system or any other names.

System Analysis System Analysis is a process by which the attribute process or goals to a human activity, determine how well those purpose are being achieved and specify the requirements of the various tools and techniques that are to be used within the system if the system performances are to be achieved. Preliminary Investigation:The initial investigation has the objective of determining the validity of the users request for a candidate system and whether a feasibility study should be conducted. The objectives of the MOVE ON CLICK
Page: 15/87 15/87

problem posed by the user must be understood within the framework of the organizations MIS plan. I had investigated from the concerned authority about the project Information Gathering:A key part of feasibility analysis is gathering information about the present system. The analyst must know what information to gather, where to find it, how to collect it, and what to make of it. The proper use of tools for gathering information is the key to successful analysis. The tools are the traditional interview, questionnaires, and on-site observation. Identification of Need Business Impacts It will reduce the amount of time spent by the employees of the company and also provides a convenient and efficient means of reaching to persons using cutting-edge- technologies. The main goal is targeting towards smooth internal communication and functioning for the customers along with other useful information. Searching Capability For users convenience, they should able to search for desired information using different criteria thus allowing them to find what they are looking for in the shortest possible time. This saves the users time and makes search convenient.

MOVE ON CLICK

Page: 16/87 16/87

FEASIBILITY STUDY Depending on the results of the initial investigation the survey is now expanded to a more detailed feasibility study. FEASIBILITY STUDY is a test of system proposal according to its workability, impact of the organization, ability to meet needs and effective use of the resources. It focuses on these major questions: 1. What are the users demonstrable needs and how does a candidate system meet them? 2. What resources are available for given candidate system? 3. What are the likely impacts of the candidate system on the organization? 4. Whether it is worth to solve the problem? During feasibility analysis for this project, following primary areas of interest are to be considered. Investigation and generating ideas about a new system does this. Steps in feasibility analysis Eight steps involved in the feasibility analysis are: Form a project team and appoint a project leader. 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.

Technical feasibility A study of resource availability that may affect the ability to achieve an acceptable system. This evaluation determines whether the technology needed for the proposed system is available or not. Can the work for the project be done with current equipment existing software technology & available personal? Can the system be upgraded if developed? If new technology is needed then what can be developed?

MOVE ON CLICK

Page: 17/87 17/87

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. The financial and the economic questions during the preliminary investigation are verified to estimate the following: 1. The cost to conduct a full system investigation. 2. The cost of hardware and software for the class of application being considered. 3. The benefits in the form of reduced cost. 4. The proposed system will give the minute information, as a result the 5. Performance is improved which in turn may be expected to provide increased profits. Operational Feasibility It is mainly related to human organizations and political aspects. The points to be considered are: 1. What changes will be brought with the system? 2. What organization structures are disturbed?

MOVE ON CLICK

Page: 18/87 18/87

SYSTEM DESIGN Design Specification: Design of software involves conceiving planning out and specifying the externally observable characteristics of the software product. We have data design, architectural design and user interface design in the design process. These are explained in the following section. The goals of design process it to provide a blue print for implementation, testing, and maintenance activities. Database Design: Databases are normally implemented by using a package called a Data Base Management System (DBMS). Each particular DBMS has somewhat unique characteristics, and so such, general techniques for the design of database are limited. One of the most useful methods of analyzing the data required by the system for the data dictionary has developed from research into relational database, particularly the work of E.F.Codd. This method of analyzing data is called Normalization. Unorganized data are converted into normalized data by three stages. Each stage has a procedure to follow. This activity deals with certain design issues, which are to be finalized in consultation with the user. The two most important design issues of the relevance to the user are the automation boundary and the human-machine interface, the output of this proposed system. This model in addition to the essential model defines the following for the proposed system. Project Scheduling Software Requirements Specification (SRS) A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains Non-functional requirements. A functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system uses the

MOVE ON CLICK

Page: 19/87 19/87

functional requirements are captured in use cases. Functional requirements are supported by non-functional requirements (also known as quality requirements), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). How a system implements functional requirements is detailed in the system design. A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions In general, functional requirements define what a system is supposed to do whereas nonfunctional requirements define how a system is supposed to be. Non-functional requirements are often called qualities of a system. Other terms for non-functional requirements are "constraints", "quality attributes", "quality goals" and "quality of service requirements," and "non-behavioral requirements." Qualities, that is, non-functional requirements, can be divided into two main categories: 1. Execution qualities, such as security and usability, which are observable at run time. 2. Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the software system. 6) Purpose and Scope Purpose The main aim of Move on click is providing fastest booking support for the customers who are visiting to our state and getting support for any vehicle. We provide these facilities to those customers from outside our state. They can book online from their state and get the facility System should be completely web-based application. System should be user friendly. It should be capable of handling multi-users simultaneously. System should be fast. Maintaining database of various visitor. System should maintain database for various travel agencies. Scope The scope of this website is global i.e. it should be able to be accessed from anywhere through internet. MOVE ON CLICK
Page: 20/87 20/87

7)

Requirement Specification Following are the requirement for this website .Some example requirements are entered

in to it. It helps in validating the system during testing S.NO 1 Requirement Information -------Input -----Process Output Information about the web-site (Home 2 3 Contact Enquiry about booking Enter the booking no. page). Contact details about the website Search for the given Result will display input according to the input

Vehicle details

Enter the categories Search for the given Result of the search of vehicle required is either economy or luxurious. input. as per cars type and availability with the agency. Search for the Enter your required package Package according to the availability within the agency. Submission of complain Fare details of the package

Packages available

Lost Property

Enter your complain

Forums/Feedback

Feedback from registered users

Submission of feedback

8.

Software Engineering Paradigm Applied

MOVE ON CLICK

Page: 21/87 21/87

Iterative and Incremental development is a cyclic software development process developed in response to the weaknesses of the waterfall model. It starts with an initial planning and ends with deployment with the cyclic interaction in between. The iterative and incremental development is an essential part of the Rational Unified Process, the Dynamic Systems Development Method, Extreme Programming and generally the agile software development frameworks.

MOVE ON CLICK

Page: 22/87 22/87

DATA FLOW DIAGRAM


Data Flow Diagram is a diagrammatic representation of data movement through a system manual or automated - from inputs to outputs through processing. The data flow diagrams help in the analysis of the flow of data through a system and thus help in identifying the system requirements. These are of two types Logical Data Flow Diagrams and Physical Data Flow Diagrams. The Data Flow Diagram (DFD) clarifies system requirements and identifies major transformations that will become programs in system design. It is the starting point of system design that decomposes the requirements specifications down to the lowest level of detail. The following table lists the important elements of DFDs. Symbol Data process Data flow Data store Actor Data process A data process transforms data values. Stands For Data processing Data flow or the exchange of data between processes Data storage Object producing and consuming data

You can make a distinction between the following types of processes: Process Type High-level Low-level Leaf or atomic processes Indicates Process containing non-functional components such as data stores or external objects that cause side effects Pure function without side effects, such as the sum of two numbers Process that is not further decomposed

The name of a process is usually a description of the transformation it performs.

MOVE ON CLICK

Page: 23/87 23/87

There are three sorts of transformation: 1. Transformation of the structure, for example, reformatting. 2. Transformation of information contained in data 3. Generation of new information Data store A data store stores data passively for later access. A data store responds to requests to store and access data. It does not generate any operations. A data store allows values to be accessed

Actor An actor produces and consumes data, driving the DFD. Actors lie on the boundary of the diagram; they terminate the flow of data as sources and sinks of data. They are also known as terminators. The system interacts with people through the actor.

Anchor A DFD anchor provides a start or end point. In decomposition diagrams, anchors represent the nodes connected to the decomposed process in the higher level diagram.

Data flow A data flow moves data between processes or between processes and data stores. As such, it represents a data value at some point within a computation and an intermediate value within a computation if the flow is internal to the diagram. This value is not changed.

Result flow

MOVE ON CLICK

Page: 24/87 24/87

A result flow is a data flow that generates an object used as the target of another operation. The value of the flow is subsequently treated as an object, usually a data store.

Control flow A control flow is a signal that carries out a command or indicates that something has occurred. A control flow occurs at a discrete point in time. The arrow indicates the direction of the control flow. The name of the event is written beside the arrow. Control flows can correspond to messages in CCDs or events in STDs; however, because they duplicate information in the DFD, use them sparingly.

Update flow Update (or bidirectional) flows are used to indicate an update of a data store, that is, a read, change, and store operation on a data flow.

A System Context Diagram (SCD) in software engineering and systems engineering are diagrams that represent the actors outside a system that could interact with that system. This diagram is the highest level view of a system, similar to Block diagram, showing a, possibly software-based, system as a whole and its inputs and outputs from/to external factors. System Context Diagram is diagrams used in systems design to represent the more important external actors that interact with the system at hand. This type of diagram according to Kossiakoff (2003) usually "pictures the system at the center, with no details of its interior structure, surrounded by all its interacting systems, environment and activities. The objective of a system context diagram is to focus attention on external factors and events that should be considered in developing a complete set of system requirements and constraints". System context diagrams are related to Data Flow Diagram, and show the interactions between a system and other actors with which the system is designed to interface. System context diagrams can be helpful in understanding the context which the system will be part of. Context Diagram

MOVE ON CLICK

Page: 25/87 25/87

1st level Data Flow Diagram User process

MOVE ON CLICK

Page: 26/87 26/87

Admin process

MOVE ON CLICK

Page: 27/87 27/87

2nd level Data Flow Diagram Entry process

MOVE ON CLICK

Page: 28/87 28/87

Billing process

MOVE ON CLICK

Page: 29/87 29/87

NORMALIZATION

MOVE ON CLICK

Page: 30/87 30/87

Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table and ensuring data dependencies make sense. Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored. First Normal Form (1NF) First normal form (1NF) sets the very basic rules for an organized database: 1. Eliminate duplicative columns from the same table. 2. Create separate tables for each group of related data and identify each row with unique column or set of columns (the primary key). Second Normal Form (2NF) Second normal form (2NF) further addresses the concept of removing duplicative data: 1. Meet all the requirements of the first normal form. 2. Remove subsets of data that apply to multiple rows of a table and place them in separate tables. 3. Create relationships between these new tables and their predecessors through the use of foreign keys. Third Normal Form (3NF) Third normal form (3NF) goes one large step further: 1. Meet all the requirements of the second normal form. 2. Remove columns that are not dependent upon the primary key.

ENTITY-RELATIONSHIP

MOVE ON CLICK

Page: 31/87 31/87

An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes. It shows the different relationships exist between different tables present in the database. The different types of symbols user are as follows:

Entity set

Attribute

relationship set m

Specialization 1

Attribute

Primary key 1 m 1

Many to one relationship m n

One to many relationship Primary key

Many to many relationship

An Entity may be defined as a thing which is recognized as being capable of an independent existence and which can be uniquely identified. An entity is an abstraction from the complexities of some domain. When we speak of an entity we normally speak of some aspect of the real world which can be distinguished from other aspects of the real world. An Entity may be a physical object such as a house or a car, an event such as a house sale or a car service, or a concept such as a customer transaction or order. Although the MOVE ON CLICK
Page: 32/87 32/87

IS A

term entity is the one most commonly used, following Chen we should really distinguish between an entity and an entity-type. An entity-type is a category. An entity, strictly speaking, is an instance of a given entity-type. There are usually many instances of an entity-type. Because the term entity-type is somewhat cumbersome, most people tend to use the term entity as a synonym for this term. Entities can be thought of as nouns. Examples: a computer, an employee, a song, a mathematical theorem. Entities are represented as rectangles. The model's linguistic aspect described above is utilized in the declarative database query language which mimics natural language constructs. Entities and relationships can both have attributes. Examples: an employee entity might have a Social Security Number (SSN) attribute; the proved relationship may have a date attribute. Attributes are represented as ellipses connected to their owning entity sets by a line. Every entity (unless it is a weak entity) must have a minimal set of uniquely identifying attributes, which is called the entity's primary key. Entity-relationship diagrams don't show single entities or single instances of relations. Rather, they show entity sets and relationship sets. Example: a particular song is an entity. The collection of all songs in a database is an entity set. The eaten relationship between a child and her lunch is a single relationship. The set of all such child-lunch relationships in a database is a relationship set. Certain cardinality constraints on relationship sets may be indicated as well.

MOVE ON CLICK

Page: 33/87 33/87

MOVE ON CLICK

Page: 34/87 34/87

The Attributes of the System Design are as Follows Input Design The most common cause of data processing errors is inaccurate input data. Errors entered by the data entry operators can be controlled by input design. Input design is the process of converting user oriented inputs and computer based formats. The goal of input design is to make data entry easy, logical and free from errors possible. For convenience of the conversion of the user oriented inputs, we have design the codes for the data entry for the members to signify their categorization. Interface Design The users interface of a windows base application is its first impression regardless of the value of its contents the sophistication of its processing capabilities and services and services and the overall benefit of the application itself. A poorly designed interface will disappoint the potential user and may infect cause the user to elsewhere because of the sheer volume of competing other application in virtually every subject area. As we use language JAVA/MySQL to develop this software so first of all we design good graphical user interface using graphics. Here we design the screen, horizontal menu and vertical menu. When we press enter or click the mouse pointer on a particular selected item it links to that location. Output Design Computers are the most important source to the users inputs is fed into the computers to acquire the necessary outputs. The computer can provide the well enough output in the form of information regarding various items to the user. The major form of output is a hard copy from the printer.

MOVE ON CLICK

Page: 35/87 35/87

DATABASE DESIGN 11. Database Design Database design is the process of producing a detailed data model of a database. This logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a Data Definition Language, which can then be used to create a database. A fully attributed data model contains detailed attributes for each entity. The term database design can used to describe many different parts of the design of an overall database system. Principally, and most correctly, it can be thought of as the logical design of the base data structures used to store the data. In the relational model these are the tables and views. In an object database the entities and relationships map directly to object classes and named relationships. However, the term database design could also be used to apply to the overall process of designing, not just the base data structures, but also the forms and queries used as part of the overall database application within the database management system (DBMS). LOGIN TABLE
CREATE TABLE LOGIN" ( "LOGINID" VARCHAR2 (20) NOT NULL ENABLE, "USERNAME" VARCHAR2 (25) NOT NULL ENABLE, "PASSWORD" VARCHAR2 (25) NOT NULL ENABLE, PRIMARY KEY ("LOGINID") ENABLE )

BOOKING TABLE
CREATE TABLE BOOKING" ( "BOOKINGNO" VARCHAR2 (15) NOT NULL ENABLE, "CNAME" VARCHAR2 (30) NOT NULL ENABLE, "CMOB" VARCHAR2 (15) NOT NULL ENABLE, "EMAIL" VARCHAR2 (30) NOT NULL ENABLE, "PDATE" DATE NOT NULL ENABLE, "PTIME" VARCHAR2 (15) NOT NULL ENABLE, "DDATE" DATE NOT NULL ENABLE, "DTIME" VARCHAR2 (15) NOT NULL ENABLE, "PCITY" VARCHAR2 (20) NOT NULL ENABLE, "PDIST" VARCHAR2 (20) NOT NULL ENABLE, "PDETAILS" VARCHAR2 (50) NOT NULL ENABLE,

MOVE ON CLICK

Page: 36/87 36/87

"DCITY" VARCHAR2 (20) NOT NULL ENABLE, "DDIST" VARCHAR2 (20) NOT NULL ENABLE, "DDETAILS" VARCHAR2 (50) NOT NULL ENABLE, "TCITY" VARCHAR2 (20) NOT NULL ENABLE, "TDIST" VARCHAR2 (20) NOT NULL ENABLE, "TDETAILS" VARCHAR2 (50) NOT NULL ENABLE, "NOPERSON" NUMBER (5, 0) NOT NULL ENABLE, "VTYPE" VARCHAR2 (15) NOT NULL ENABLE, "VCAT" VARCHAR2 (10) NOT NULL ENABLE, "CURDT" DATE NOT NULL ENABLE, PRIMARY KEY ("BOOKINGNO") ENABLE )

FEEDBACK TABLE
CREATE TABLE "FEEDBACK" ( "CNAME" VARCHAR2 (30) NOT NULL ENABLE, "CMOB" VARCHAR2 (15) NOT NULL ENABLE, "JDATE" DATE NOT NULL ENABLE, "VNO" VARCHAR2 (20) NOT NULL ENABLE, "FEEDBACK" VARCHAR2 (300) NOT NULL ENABLE )

LOSTPROPERTY TABLE
CREATE TABLE "LOSTPROPERTY" ( "NAME" VARCHAR2 (30) NOT NULL ENABLE, "MOBNO" NUMBER (12, 0) NOT NULL ENABLE, "ADDRESS" VARCHAR2 (50) NOT NULL ENABLE, "PADD" VARCHAR2 (30) NOT NULL ENABLE, "PDATE" DATE NOT NULL ENABLE, "PTIME" VARCHAR2 (10) NOT NULL ENABLE, "DADD" VARCHAR2 (12) NOT NULL ENABLE, "DDATE" DATE NOT NULL ENABLE, "DTIME" VARCHAR2 (12) NOT NULL ENABLE, "VNO" VARCHAR2 (12) NOT NULL ENABLE, "VTYPE" VARCHAR2 (15) NOT NULL ENABLE, "VCAT" VARCHAR2 (5) NOT NULL ENABLE, "COPMLN" VARCHAR2 (200) NOT NULL ENABLE ) /

MOVE ON CLICK

Page: 37/87 37/87

VEHICLEMASER TABLE
CREATE TABLE "VEHICLEMASTER" ( "VNO" VARCHAR2 (15) NOT NULL ENABLE, "VTYPE" VARCHAR2 (15) NOT NULL ENABLE, "VCAT" VARCHAR2 (10) NOT NULL ENABLE, "VPKM" NUMBER (8, 2) NOT NULL ENABLE, "VPEXTKM" NUMBER (8, 2) NOT NULL ENABLE, "HUNDRED" NUMBER (8, 2) NOT NULL ENABLE, "TWOFIFTY" NUMBER (8, 2) NOT NULL ENABLE, "VCAP" NUMBER (5, 0) NOT NULL ENABLE, "STATUS" CHAR (1) NOT NULL ENABLE, "HULTING" NUMBER (8, 2) NOT NULL ENABLE, PRIMARY KEY ("VNO") ENABLE )

VBOOKINGMASTER TABLE
CREATE TABLE "VBOOKINGMASTER" ( "VNO" VARCHAR2 (15) NOT NULL ENABLE, "BOOKINGNO" VARCHAR2 (15) NOT NULL ENABLE, "VBDATE" DATE NOT NULL ENABLE, "BOOKDT" VARCHAR2 (20) NOT NULL ENABLE, "PHOUR" VARCHAR2 (20) NOT NULL ENABLE, "PKPLACE" VARCHAR2 (200) NOT NULL ENABLE, "TRTYP" VARCHAR2 (10) NOT NULL ENABLE, "CNAME" VARCHAR2 (50) NOT NULL ENABLE, "DMOBILENO" VARCHAR2 (12) NOT NULL ENABLE, CONSTRAINT "VBOOKINGMASTER_IBFK_1" FOREIGN KEY ("BOOKINGNO") REFERENCES "BOOKING" ("BOOKINGNO") ENABLE, CONSTRAINT "VBOOKINGMASTER_IBFK_2" FOREIGN KEY ("VNO") REFERENCES ) "VEHICLEMASTER" ("VNO") ENABLE

VEHICLERETURN MASTER TABLE


CREATE TABLE "VEHICLERETURNMASTER" ( "VNO" VARCHAR2 (15) NOT NULL ENABLE, "BOOKINGNO" VARCHAR2 (15) NOT NULL ENABLE, "VBDATE" DATE NOT NULL ENABLE, "VRDATE" DATE NOT NULL ENABLE, "PPLACE" VARCHAR2 (60) NOT NULL ENABLE,

MOVE ON CLICK

Page: 38/87 38/87

"DRPLACE" VARCHAR2 (60) NOT NULL ENABLE, "CNAME" VARCHAR2 (30) NOT NULL ENABLE, "DMOBILENO" NUMBER (15, 0) NOT NULL ENABLE, CONSTRAINT "VEHICLERETURNMASTER_IBFK_1" FOREIGN KEY ("BOOKINGNO") REFERENCES "BOOKING" ("BOOKINGNO") ENABLE, CONSTRAINT "VEHICLERETURNMASTER_IBFK_2" FOREIGN KEY ("VNO") REFERENCES "VEHICLEMASTER" ("VNO") ENABLE )

VOUCHER TABLE
CREATE TABLE "VOUCHER" ( "BOOKINGNO" VARCHAR2 (15) NOT NULL ENABLE, "BILLNO" VARCHAR2 (10), "CNAME" VARCHAR2 (30) NOT NULL ENABLE, "CMOB" NUMBER (15, 0) NOT NULL ENABLE, "CADD" VARCHAR2 (100) NOT NULL ENABLE, "VNO" VARCHAR2 (20) NOT NULL ENABLE, "VTYPE" VARCHAR2 (20) NOT NULL ENABLE, "VCAT" VARCHAR2 (10) NOT NULL ENABLE, "PPLACE" VARCHAR2 (50) NOT NULL ENABLE, "PDATE" DATE NOT NULL ENABLE, "PTIME" VARCHAR2 (10) NOT NULL ENABLE, "DPLACE" VARCHAR2 (50) NOT NULL ENABLE, "DDATE" VARCHAR2 (15) NOT NULL ENABLE, "DTIME" VARCHAR2 (10) NOT NULL ENABLE, "TOTKM" NUMBER (10, 0) NOT NULL ENABLE, "KMCHRG" NUMBER (8, 2) NOT NULL ENABLE, "HOLDCHRG" NUMBER (8, 2) NOT NULL ENABLE, "EXTCHRG" NUMBER (8, 2) NOT NULL ENABLE, "TOTAMT" NUMBER (8, 2) NOT NULL ENABLE, "ADVPAYMENT" NUMBER (8, 2) NOT NULL ENABLE, "NETAMT" NUMBER (8, 2) NOT NULL ENABLE, "STATUS" CHAR (1) NOT NULL ENABLE, PRIMARY KEY ("BILLNO") ENABLE )

BILL TABLE
CREATE TABLE "BILL" ( "BOOKINGNO" VARCHAR2 (15) NOT NULL ENABLE, "BILLNO" VARCHAR2 (10), "CNAME" VARCHAR2 (30) NOT NULL ENABLE, "VNO" VARCHAR2 (20) NOT NULL ENABLE,

MOVE ON CLICK

Page: 39/87 39/87

"NETAMT" NUMBER (8, 2) NOT NULL ENABLE, "advpayment NUMBER (8, 2) NOT NULL ENABLE, "totamount" NUMBER (8, 2) NOT NULL ENABLE, "amountpaid" NUMBER (8, 2) NOT NULL ENABLE, "balance" NUMBER (8, 2) NOT NULL ENABLE, "status" CHAR (1) )

TABLE STRUCTURE: 1: LOGIN TABLE

2: BILL TABLE

MOVE ON CLICK

Page: 40/87 40/87

3: BOOKING TABLE

4: FEEDBACK TABLE

MOVE ON CLICK

Page: 41/87 41/87

5: LOSTPROPERTY TABLE

6: VBOOKINGMASTER TABLE

MOVE ON CLICK

Page: 42/87 42/87

7: VEHICLEMASTER TABLE

8: VEHICLE RETURNMASTER TABLE

MOVE ON CLICK

Page: 43/87 43/87

9: VOUCHER TABLE

MOVE ON CLICK

Page: 44/87 44/87

SCREEN LAYOUT
Home page:

About Us:

MOVE ON CLICK

Page: 45/87 45/87

Contact

Feedback

MOVE ON CLICK

Page: 46/87 46/87

Lost property

Enquiry Now

MOVE ON CLICK

Page: 47/87 47/87

Fares

Admin login

MOVE ON CLICK

Page: 48/87 48/87

Admin password change

Vechicle entry

MOVE ON CLICK

Page: 49/87 49/87

Booking entry

MOVE ON CLICK

Page: 50/87 50/87

Billing page

MOVE ON CLICK

Page: 51/87 51/87

CODE GENERTION
Code for home page <%@ pagecontent Type="text/html; charset=iso-8859-1" language="java" import="java.sql.*" session="true" errorPage="" %> <%@ page import="java.sql.*,java.util.*,java.text.*,java.text.SimpleDateFormat" %> <%@ include file="library/database.jsp" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Book Taxi Online | Book Taxi Online in Odisha | Book Taxi Online in Bhubaneswar</title> <script src="js/calendar_us.js"></script> <link href="css/calendar.css" rel="stylesheet" type="text/css" /> <link href="css/default.css" rel="stylesheet" type="text/css" /> <link href="css/style.css" rel="stylesheet" type="text/css" /> <script language="javascript" type="text/javascript" src="js/valdation1.js"></script> <script type="text/javascript"> <!-function MM_jumpMenu(targ,selObj,restore){ //v3.0 eval (targ+".location='"+selObj.options[selObj.selectedIndex].value+"'"); if (restore) selObj.selectedIndex=0; } function clearText(field) { if (field.defaultValue == field.value) field.value = ''; else if (field.value == '') field.value = field.defaultValue; } //--> </script> </head> <body> <div class="wraper">

MOVE ON CLICK

Page: 52/87 52/87

<div

class="header"><div

class="header_l"><a

href="#"><img

src="image/logo_move_on_click.gif"/></a></div> <div class="header_r"> <ul><li><a href="index.jsp" style="font-size: 12px ;">HOME</a></li> <li><a href="about.html" style="font-size:12px;">ABOUT</a></li> <li><a href="user/fare.jsp" style="font-size:12px;">FARES</a></li> <li><a href="index.jsp" style="font-size:12px;">BOOK</a></li> <li><a href="user/feedback.jsp" style="font-size:12px;">FEEDBACK</a></li> <li><a href="user/lostprop.jsp" style="font-size:12px;">LOST PROPERTY</a></li> <li style="background:none;"><a href="contactus.html"style="font size:12px;">CONTACT</a></li> </ul></div></div> <div class="content"> <div class="content_l"><div class="about"> <div <div class="about_1"><h1>Welcome class="about_2"><a href="#"><img to <font color="#fffd5e">Move /></a><a on Click</font></h1></div> src="image/f.gif" href="#"><img src="image/t.gif" /></a><a href="#"><img src="image/y.gif" /></a></div> </div><div class="about_p"> <p>At Orissa Taxi Services we only operate with the latest models that are maintained at the highest standards. Orissa Taxi Services know what their client expect and deserve, so all customers are treated with royalty.</p> </div><div class="about_tag"><table width="382" height="34" border="0" cellpadding="0" cellspacing="0"> <tr><td <td width="125"><a width="155"><a href="user/enquiry.jsp"><img href="user/admin.jsp"><img src="image/enquiry_now.jpg" src="image/for_taxi_owner.jpg" width="118" height="34" border="0" /></a></td> width="147" height="34" border="0" /></a></td> <td width="102"><a href="user/fare.jsp"><img src="image/fare.jpg" width="99" height="34" border="0" /></a></td> </tr></table></div><div class="about_call">CALL US : <font color="#fffd5e"><b>0674 6546542</b></font></div></div><div class="content_r"><div class="table"> <table width="658" border="0" cellspacing="1" cellpadding="1" class="border_table" align="center"> <tr><td width="644"> <form name="frm" action="user/action.jsp" method="post" onsubmit="return book(this)" >

MOVE ON CLICK

Page: 53/87 53/87

<table <tr><td

width="610" colspan="5"

border="0"

cellspacing="3"

cellpadding="1"

align="center" A <font

bgcolor="#FFFFFF"> id="heading" bgcolor="#FFCC66">BOOK color="#990000">TAXI</font> IN LESS THEN 60 SECONDS !</td></tr> <tr><td width="97" height="27">&nbsp;</td> <td width="249">&nbsp;</td><td width="223">&nbsp;</td><td width="18" colspan="2">&nbsp;</td></tr><tr><td class="subheading">WHO ?</td> <td colspan="4"><input type="text" name="txtWho" name="txtMno" value="Contact No." size="12" value="Your Name" size="20" <input type="text" onfocus="foc(2)" onblur="los(2)" onblur="los(1)" onfocus="foc(1)" style="color:#666;" /> style="color:#666;" />&nbsp;

<input type="text" name="txtEmail" value="E-mail Address"

size="20" onblur="los(3)" onfocus="foc(3)" style="color:#666;" /></td> </tr><tr><td rowspan="4" class="subheading">WHEN ?</td> <td colspan="4" class="subheading">PICK UP DATE AND TIME.</td> </tr><tr><td><select name="Pday"><option selected="selected">--Day--</option> <option>1</option><option>2</option><option>3</option><option>4</option> <option>5</option><option>6</option><option>7</option><option>8</option> <option>9</option><option>10</option><option>11</option><option>12</option> <option>13</option><option>14</option><option>15</option><option>16</option> <option>17</option><option>18</option><option>19</option><option>20</option> <option>21</option><option>22</option><option>23</option><option>24</option> <option>25</option><option>26</option><option>27</option><option>28</option> <option>29</option><option>30</option><option>31</option></select> <select name="Pmonth"><option selected="selected">--Month--</option> <option>Jan</option><option>Feb</option><option>Mar</option><option>Apr</option> <option>May</option><option>Jun</option><option>Jul</option><option>Aug</option> <option>Sep</option><option>Oct</option><option>Nov</option><option>Dec</option> </select><input type="text" name="Pyear" size="5" value="Year" /></td> <td colspan="3"><select name="selpkhour" style="color:#666;"> <option selected="selected"> Hr</option><option>01</option><option>02</option> <option>03</option><option>04</option><option>05</option><option>06</option> <option>07</option><option>08</option><option>09</option><option>10</option> <option>11</option><option>12</option></select><select name="selpkmin" style="color:#666;"><option selected="selected"> Min</option><option>00</option> <option>05 </option><option>10 </option><option>15</option><option>20</option> MOVE ON CLICK
Page: 54/87 54/87

<option>20</option><option>30</option><option>35</option><option>40</option> <option>45</option><option>50</option><option>55</option></select><select name="selampm" style="color:#666;"><option selected="selected"> Am/Pm</option> <option>Am</option><option>Pm</option></select></td></tr> <tr> <td colspan="4" class="subheading">DROPING DATE AND TIME.</td></tr> <tr><td><select name="Dday"><option selected="selected">--Day--</option> <option>1</option><option>2</option><option>3</option><option>4</option> <option>5</option><option>6</option><option>7</option><option>8</option> <option>9</option><option>10</option><option>11</option><option>12</option> <option>13</option><option>14</option><option>15</option><option>16</option> <option>17</option><option>18</option><option>19</option><option>20</option> <option>21</option><option>22</option><option>23</option><option>24</option> <option>25</option><option>26</option><option>27</option><option>28</option> <option>29</option><option>30</option><option>31</option></select> <select name="Dmonth"><option selected="selected">--Month--</option> <option>Jan</option><option>Feb</option><option>Mar</option><option>Apr</option> <option>May</option><option>Jun</option><option>Jul</option><option>Aug</option> <option>Sep</option><option>Oct</option><option>Nov</option><option>Dec</option> </select><input type="text" name="Dyear" size="5" value="Year" /></td><td colspan="3"> <select name="seldhour" style="color:#666;"><option selected="selected"> Hr</option> <option>01</option><option>02</option><option>03</option><option>04</option> <option>05</option><option>06</option><option>07</option><option>08</option> <option>09</option><option>10</option><option>11</option><option>12</option> </select><select name="seldmin" style="color:#666;"><option selected="selected"> </option> Min</option><option>00</option><option>05 </option><option>10

<option>15</option><option>20</option><option>20</option><option>30</option> <option>35</option><option>40</option><option>45</option><option>50</option> <option>55</option></select><select name="seldampm" style="color:#666;"> <option selected="selected"> Am/Pm</option><option>Am</option><option>Pm</option> </select></td></tr><tr><td rowspan="3" class="subheading">PICK UP ?</td> <td colspan="2"><select name="selectCity" style="color:#666;"> <option <option>Uttar selected="selected">Select Pradesh</option><option>Madhya State</option><option>Orissa</option> Pradesh</option><option>Andhra <option>Delhi</option><option>Maharastra</option><option>Rajasthan</option> Pradesh</option><option>Bihar</option><option>Jharkhand</option> MOVE ON CLICK
Page: 55/87 55/87

<option>Utarakhand</option><option>Himachal

Pradesh</option></select><input

type="text" name="txtpkDist" value="District" size="20" onblur="los(6)" onfocus="foc(6)" style="color:#666;" /></td><td colspan="2">&nbsp;</td></tr><tr><td colspan="4"> <textarea name="textarea" cols="45" rows="5" onblur="los(9)" onfocus="foc(9)" style="color:#666;" >Full Details+Landmark</textarea> </td></tr><tr><td colspan="4"> <input type="checkbox" name="checkbox" id="checkbox" onclick="check()" /> Same copy to Drop. </td></tr><tr><td rowspan="2" class="subheading">DROP ?</td> <td colspan="2"><select name="seldrcity" style="color:#666;"> <option selected="selected">Select State</option> <option>Orissa</option><option>Delhi</option><option>Maharastra</option> <option>Rajasthan</option><option>Uttar Pradesh</option><option>Andhra Pradesh</option></select> </select><input type="text" name="txtdrdist" value="District" size="20" onblur="los(7)" onfocus="foc(7)" style="color:#666;" /></td><td colspan="2">&nbsp;</td></tr> <tr><td colspan="4"><textarea name="textarea2" onfocus="foc(10)" cols="45" rows="5" onblur="los(10)" style="color:#666;">Full Details+Landmark</textarea></td></tr><tr> selected="selected">Select State</option> Pradesh</option><option>Madhya Pradesh</option><option>Bihar</option>

<option>Jharkhand</option><option>Utarakhand</option><option>Himachal

<td rowspan="2" class="subheading">TOUR ?</td><td colspan="2"><select name="seltrcity" style="color:#666;"><option <option>Orissa</option><option>Delhi</option><option>Maharastra</option> <option>Rajasthan</option><option>Uttar Pradesh</option><option>Andhra Pradesh</option></select></select><input <td Pradesh</option><option>Madhya Pradesh</option><option>Bihar</option> type="text" name="tourdist" value="District" name="feedback"

<option>Jharkhand</option><option>Utarakhand</option><option>Himachal size="20" onblur="los(8)" onfocus="foc(8)" style="color:#666;" /></td> colspan="2">&nbsp;</td></tr><tr><td rows="5" onblur="los(11)" colspan="4"><textarea cols="45" onfocus="foc(11)" style="color:#666;">Full

Details+Landmark</textarea></td></tr><tr><td class="subheading">TYPE ?</td> <td colspan="4"><select name="selnoperson" style="color:#666;"> <option selected="selected">Number of Person</option><option >01</option> <option>02</option><option>03</option><option>04</option><option>05</option> <option>06</option><option>07</option><option>08</option><option>09</option> <option>10</option><option>11</option><option>12</option><option>13</option> <option>14</option><option>15</option></select> MOVE ON CLICK
Page: 56/87 56/87

</select><select name="seltyvichel" style="color:#666;"> <option selected="selected">Type of vehicle</option> <%String sql,vtype; sql="select vtype from vehiclemaster";try{rs=stmt.executeQuery(sql); while(rs.next()){vtype=rs.getString("vtype");%> <option><%=vtype %></option><%}}catch(Exception e){} %> </select><select name="seltyacnac" style="color:#666;"><option selected="selected">Catagory</option><option>Ac</option><option>Non-Ac</option> </select></td></tr><tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td> <td <td colspan="2">&nbsp;</td></tr><tr><td>&nbsp;</td><td><input colspan="2">&nbsp;</td></tr><tr><td>&nbsp;</td><td colspan="2" type="submit" align="center" name="btnsub" value="BOOK" class="subheading"/></td><td>&nbsp;</td> >&nbsp;</td><td colspan="2">&nbsp;</td></tr><tr><td>&nbsp;</td><td>&nbsp;</td> <td>&nbsp;</td><td colspan="2">&nbsp;</td></tr></table></form></tr></table><br /> <br /><br /><br /><div id="footer_index_1" ><p><font color="#FFFFFF">Copyright &copy; 2007-2011 Saipro Solutions Pvt. Ltd. All rights reserved.&nbsp;&nbsp;</font></p> <!--<ul><li><a href="moveonclick.html" style="font-size:12px;">HOME</a></li> <li><a href="about.html" style="font-size:12px;">ABOUT</a></li> <li><a href="fare.php" style="font-size:12px;">FARES</a></li> <li><a href="moveonclick.html" style="font-size:12px;">BOOK</a></li> <li><a href="feedback.php" style="font-size:12px;">FEEDBACK</a></li> <li><a href="lostproperty.php" style="font-size:12px;">LOST PROPERTY</a></li> <li style="background:none;"><a href="contactus.html"style="font size:12px;">CONTACT</a></li></ul></div></font> --></div></body></html> Code for admin page <%@ page contentType="text/html; charset=iso-8859-1" language="java" import="java.sql.*" session="true" errorPage="" %><%@ %><%@ page include import="java.sql.*,java.util.*,java.text.*,java.text.SimpleDateFormat"

file="../library/database.jsp" %><%String path = request.getContextPath(); String basePath = request.getScheme()+"://"+request.getServerName()+":"+request.getServerPort() +path+"/user/";//out.print( basePath);%><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><base href="<%=basePath %>" /><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /><title>Moveonclick : An Online Taxi Booking</title><meta http-equiv="pragma" content="no-cache"><meta httpequiv="cache-control" content="no-cache"><meta http-equiv="expires" content="0"> MOVE ON CLICK
Page: 57/87 57/87

<meta

http-equiv="keywords" equiv="description" rel="stylesheet"

content="keyword1,keyword2,keyword3"><meta content="This is my

http page"><link

href="../css/styleeadmin.css"rel="stylesheet" type="text/css" /><link href="../css/style.css" type="text/css"/><script language="javascript" class="wraper"><div src="../images/car_bg.png" alt="." type="text/javascript"></script></head><body><div alt="." /></div> <div class="header_l_bot"><img <div class="header_r"><div

class="header_l"><div class="header_l_top"><img src="../images/logo_move_on_click.gif" /></div></div> href="../index.jsp" class="header_r_top"><ul><li><a href="../about.html" style="fontstyle="fontstyle="fonthref="fare.jsp" href="../index.jsp" href="feedback.jsp"

style="font-size:12px;">HOME</a></li><li><a

style="font-size:12px;">ABOUT</a></li><li><a size:12px;">FARES</a></li><li><a size:12px;">BOOK</a></li><li><a

size:12px;">FEEDBACK</a></li><li><a href="lostprop.jsp" style="font-size:12px;">LOST PROPERTY</a></li><li style="background:none;"><a href="../contactus.html"style="fontsize:12px;">CONTACT</a></li></ul></div> ><table width="300" border="0" <div cellspacing="0" class="header_r_bot"><div cellpadding="0"><%String MyError=""; class="login"><form action="admin.jsp" method="post" name="frm" onsubmit="check(this)" UserID=null,Password=null,

//out.println(request.getMethod().equals("POST"));if((request.getMethod().equals("POST"))) {UserID = request.getParameter("txtUname");Password = request.getParameter("txtPass"); if(( UserID.length()!=0) && (Password.length()!=0)){try{stmt = con.createStatement(); String Query { = "select * from login where = USERNAME = '"+UserID+"' and PASSWORD='"+Password+"'";rs stmt.executeQuery(Query);if(rs.next())

session=request.getSession(true);session.setAttribute("user",UserID);

session.setAttribute("pass",Password);response.sendRedirect("../admin/adminframe.jsp");} else{MyError = "<center><font color='brown' size='3'>User name or Password is incorrect ! </font></center>";}//stmt.close();//con.close();}catch(Exception e) {out.println("Error:"+e.getMessage());}}else{MyError align="left" valign="top">&nbsp;</td><td = "<center><font height="78" color='brown' align="left" align="left" align="left" align="left" valign="middle" valign="top" size='3'>All fields are required !</font></center>";}}%><tr><td width="30" height="78" width="92" valign="top">&nbsp;</td><td valign="top">&nbsp;</td><td valign="top">&nbsp;</td></tr><tr><td valign="top">&nbsp;</td><td class="user_name">User MOVE ON CLICK Login width="10" width="168" width="30" height="28" height="28" </td><td height="78" height="78" height="28" align="left" align="left"
Page: 58/87 58/87

>&nbsp;</td><td

height="40"

align="left" height="28"

valign="middle"><input align="left" height="28"

type="text"

name="txtUname" size="15" /></td></tr><tr><td width="30" height="28" align="left" valign="top">&nbsp;</td><td valign="middle" align="left" <input align="left" align="left" class="user_name">Password</td><td

valign="middle">&nbsp;</td><td height="40" align="left" valign="middle"> align="left" valign="top">&nbsp;</td><td %> height="20" height="20" align="left" colspan="3" height="20"

type="password" name="txtPass" size="15" /></td></tr><tr><td width="30" rowspan="2" valign="top"><%=MyError valign="top">&nbsp;</td><td </td></tr><tr><td

valign="top">&nbsp;</td><td

height="20" align="right" valign="middle"><input style="margin-right:20px;" type="submit" name="Submit" value="Submit" /></td></tr></table></form> </div></div> </div></div><div class="foot"><div class="footer_1"> <p><a>Customer support </a> <a>FAQs</a> &nbsp;&nbsp; <a>Why book a from Move on click?</a> <a>Terms & conditions</a> &nbsp;&nbsp; <a>Careers</a>&nbsp;&nbsp; with us</a> </p> </div></div></body></html> Code for Booking Entry <%@ page contentType="text/html; charset=iso-8859-1" language="java" import="java.sql.*" session="true" errorPage="" %> <%@ page import="java.sql.*,java.util.*,java.text.*,java.text.SimpleDateFormat" %> <%@ include file="../library/database.jsp" %><%StringUserID=(String)session.getAttribute ("user");%> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>booking <script entry frame</title><link href="../css/menu.css" rel="stylesheet" type="text/css" /><link rel="stylesheet" type="text/css" href="../css/chromestyle.css" /> type="text/javascript" src="../js/chrome.js"></script><link href="../css/style.css" rel="stylesheet" type="text/css" /><script type="text/javascript" language="javascript"> function action1(){document.frmvbooking.action="bookingentryframe.jsp";} function action2(){document.frmvbooking.action="vehiclebooking_action.jsp";}</script> </head><body><div </div></div><div align="center" id="header_adminframe_1"><div cellspacing="0" id="header_adminframe_1logo"> width="750" width="744" border="0" height="30" class="header_adminframe_menu"><table ><tr><td &nbsp;&nbsp; &nbsp;&nbsp; <a> Advertise

cellpadding="0"

align="left" valign="middle" ><div class="chromestyle" id="chromemenu"><ul><li><a MOVE ON CLICK


Page: 59/87 59/87

href="adminframe.jsp"

rel="dropmenu5">ADMIN</a></li><li><a

href="#"

rel="dropmenu1">ENTRIES</a></li><li><a href="#" rel="dropmenu2">BILL</a></li> <li><a href="#" rel="dropmenu3">REPORTS</a></li><li><ahref="Logout.jsp">LOGOUT </a></li>Welcome to <li style="text-align:right; font-weight:bold; color:#FFCC00;"> < %=UserID %></li></ul></div><!--1st drop down menu --><div id="dropmenu1" Entry</a> class="dropmenudiv"><a href="vehiclemasterentry.jsp">Vehicle

<ahref="bookingentryframe.jsp"> Booking Entry</a><a href="returnentryframe.jsp">Return Entry</a><a href="#"></a></div><!--2nd drop down menu --><div id="dropmenu5" class="dropmenudiv"><a href="changepassword.jsp">Change Password</a></div> <div <a id="dropmenu2" class="dropmenudiv" drop down style="width: menu --><div 150px;"><ahref= id="dropmenu3" "Billgeneration.jsp">Receipt</a><a href="bill_final.jsp">Payment</a> href="#"></a></div><!--3rd class="dropmenudiv" style="width: 150px;"><a href="Bill.jsp">Bill Details</a> <a href="voucher.jsp">Voucher Details</a><a href="vehicle.jsp">Vehicle Details</a> <a href="vehiclebooking.jsp">Voucher Booking</a><a href="vehiclereturn.jsp">Vehicle href="lost_property.jsp">Lost type="text/javascript"> <td Return</a><a href="feedback.jsp">Feedback</a><a

Property</a></div></td><script cssdropdown.startchrome("chromemenu")

</script></tr></table></td></tr><tr><td align="center" valign="middle"></td></tr><tr> height="74" align="left" valign="middle" /><table background="images/footbg.jpg" width="750" border="0" &nbsp;</td></tr></table><br

lass="txt">

cellspacing="0"

cellpadding="0" align="center"><tr><td height="25" align="center"bgcolor="#CCCCCC"> <font color="#990000" size="+2">Confirm Booking Entry</font></td></tr></table><p> <!--<div id="body_adminframe">--><form name="frmvbooking" action="" method="post"> <table width="750" height="430" border="0" cellpadding="0" cellspacing="0" align="center"><tr><td width="156" class="sub_heading">Booking Number :</td> <td width="156">&nbsp;<input type="text" name="txtBookingno" size="20" /></td> <td colspan="2">&nbsp;<input type="submit" name="btnsub" value="Show"onclick= "action1()"/></td><td>&nbsp;<font color="#990000">Enter Valid Booking No.</font></td> </tr><%String cna="",mob="",addr="",paddr="",pdt="";String ptime="",tdetails="",sql="", sql1="",bno="",vbno="";bno=request.getParameter("txtBookingno"); SimpleDateFormat sdf = new SimpleDateFormat("dd-MMM-yyyy"); sql="select * from booking where bookingno='"+bno+"'" ; try{rs=stmt.executeQuery(sql); while(rs.next()){ vbno=rs.getString("BOOKINGNO");cna=rs.getString("CNAME"); mob=rs.getString("CMOB");addr=rs.getString("PCITY")+", "+rs.getString("PDIST"); MOVE ON CLICK
Page: 60/87 60/87

paddr=rs.getString("PCITY")+", pdt=sdf.format(rs.getDate("PDATE"));ptime=rs.getString("PTIME"); tdetails=rs.getString("TDETAILS");}}catch(Exception e) { //out.println(e.getMessage()); } %>

"+rs.getString("PDIST");

<tr><td height="25" colspan="5" align="center"></td></tr><tr><td height="25" colspan="5" bgcolor="#CCCCCC">&nbsp;</td></tr><tr><td colspan="5"> <fieldset><legend ><font color="#990000" face="Arial, Helvetica, sans-serif">Customer Details </font></legend><table width="100%" height="50" border="0" cellspacing="0" cellpadding="0"><tr><td width="146" height="30" class="sub_heading">&nbsp;Customer Name :</td><td width="216" class="sub_heading1"><input type="text" name="txtCname" value="<%=cna %>" size="20" readonly="readonly" No. /></td><td width="98" width="178" class="sub_heading">Contact %>" size="20" :</td><td

class="sub_heading1">&nbsp;<input type="text" name="txtCcontactno" value="<%=mob readonly="readonly" Number :</td><td /></td></tr><tr><tdclass="sub_heading"> class="sub_heading1"><input type="text" colspan="5" &nbsp;Booking

name="txtBookingno2"size="20"value="<%=vbno %>" readonly="readonly"/></td> <td>&nbsp;</td><td>&nbsp;</td></tr></table></fieldset></td></tr><tr><td bgcolor="#CCCCCC">&nbsp;</td></tr><tr><td width="100%" width="157" height="76" border="0" colspan="5"><fieldset><legend><font cellspacing="0" Up Date cellpadding="0"><tr><td :</td><td width="206"

color="#990000" face="Arial, Helvetica, sans-serif">Pick Up Details</font></legend><table class="sub_heading">Pick

class="sub_heading1">&nbsp;<input type="text" name="txtpickupdate" value="<%=pdt %>" size="20" readonly="readonly" /></td><td width="56" class="sub_heading">Time :</td><td width="220" class="sub_heading1"><input type="text" name="txtpickuptime" value="< %=ptime %>" size="20" Up readonly="readonly" Address:</td><td /></td></tr><tr><td height="52" class="sub_heading">Pick </td><td class="sub_heading1">&nbsp;<textarea type="text" name="txttourtype"

rows="3" cols="30" readonly="readonly" name="txtpickupplace"><%=paddr%> </textarea> class="sub_heading">Tour %>" bgcolor="#CCCCCC" :</td><td><input value="<%=tdetails colspan="5" serif">Vehicle size="20" /></td></tr></table></fieldset></td></tr><tr><td class="sub_heading">&nbsp;</td></tr><tr><td color="#990000" face="Arial, Helvetica, sans

colspan="5"><fieldset><legend><font

Details</font></legend><table width="100%" height="50" border="0"


Page: 61/87 61/87

MOVE ON CLICK

cellspacing="0"

cellpadding="0"><tr><td

width="44">&nbsp;</td><td

width="127"

class="sub_heading">Vehicle Number</td><td width="182" class="sub_heading">Vehicle Catagory</td><td width="139" class="sub_heading">Vehicle Type</td><td width="143" class="sub_heading">Vehicle rs1=stmt1.executeQuery(sql1); Capacity</td></tr><%!String vno="",vtype="",vcat="", sql="";float vcap=0; %><%try{sql1="select * from vehiclemaster where status='0'"; while(rs1.next()){vno=rs1.getString("vno"); value=" < width="139" e){ vtype=rs1.getString("vtype");vcat=rs1.getString("vcat");vcap=rs1.getFloat("vcap"); %><tr><td class="sub_heading1">&nbsp;<input type="radio" name="rdckh" %=vno %>" /></td><td width="127" class="sub_heading1"><%=vno %></td> <td width="182" class="sub_heading1"><%=vcat %></td><td class="sub_heading1"><%=vtype %></td><td width="143"class="sub_heading1"><%=vcap %></td></tr><%}rs1.close();stmt1.close();} catch(Exception //out.println(e.getMessage());}//response.sendRedirect("vehiclemasterentry.jsp");%> </table></fieldset></td></tr><tr><td colspan="2" bgcolor="#CCCCCC">&nbsp;</td> <td width="195" bgcolor="#CCCCCC">&nbsp;</td><td width="46" bgcolor="#CCCCCC" > &nbsp;</td><td width="197" bgcolor="#CCCCCC"> <input type="submit" name="btnsub2" value="Book" onclick="action2()" /> <a href="adminframe.jsp" style="text-decoration:none"><input type="button" name="btnrst" value="Close" /></a> </td></tr> <tr> <td colspan="5">&nbsp;</td> </tr> </table> </form> <!--</div>--> <!--</div>--> <div </body> </html> Code for Vehicle Master Entry <%@ page contentType="text/html; charset=iso-8859-1" language="java" import="java.sql.*" session="true" errorPage="" %> <%@ page import="java.sql.*,java.util.*,java.text.*,java.text.SimpleDateFormat" %> MOVE ON CLICK
Page: 62/87 62/87

id="footer_adminframe"

align="center"><font

color="#FFFFFF">&nbsp;&nbsp;</font></div>

<%@ include file="../library/database.jsp" %> <% String UserID=(String)session.getAttribute("user");%> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>adminframe</title> <link href="../css/style.css" rel="stylesheet" type="text/css" /> <script src="../js/calander_adminframe.js"></script> <link href="../css/calendar.css" rel="stylesheet" type="text/css" /> <link href="../css/menu.css" rel="stylesheet" type="text/css" /> <link rel="stylesheet" type="text/css" href="../css/chromestyle.css" /> <script type="text/javascript" src="../js/chrome.js"></script> <style> .text{color:#666; font-family:"Times New Roman", Times, serif; font-size:14px; fontweight:bold;} .text1{color:#000; font-family:"Times New Roman", Times, serif; font-size:14px;} .text2 {color:#666; font-family:"Times New Roman", Times, serif; font-size:14px; fontweight:bold;} body,td,th { font-size: 12px; } .font { font-family: Arial, Helvetica, sans-serif; } </style> <script src="../js/vehicleentry.js"></script> <script> function del() { ok=confirm("Are you sure to delete record ?"); if(ok) { alert("Record successfully deleted..."); MOVE ON CLICK
Page: 63/87 63/87

return true; } else { alert("Record not deleted..."); return false; } } </script> </head> <body> <% String vno="",sql=""; vno=request.getParameter("del"); try { int chk=Integer.parseInt(request.getParameter("idd")); if(chk==1) { sql="delete from vehiclemaster where vno='"+vno+"'"; stmt.executeUpdate(sql); //out.println("Record Deleted...."); } } catch(Exception e) { //out.println("Error :"+e.getMessage()); } %> <div id="header_adminframe_1"> <div id="header_adminframe_1logo"></div> <!--<div id="header_car_image"></div> --></div> <div class="header_adminframe_menu"> <table width="747" border="0" align="center" cellpadding="0" cellspacing="0" class=""> MOVE ON CLICK
Page: 64/87 64/87

<tr> <td width="744" height="30" align="left" valign="middle" ><div class="chromestyle" id="chromemenu"> <ul> <li><a href="adminframe.jsp" rel="dropmenu5">ADMIN</a></li> <li><a href="#" rel="dropmenu1">ENTRIES</a></li> <li><a href="#" rel="dropmenu2">BILL</a></li> <li><a href="#" rel="dropmenu3">REPORTS</a></li> <li><a href="Logout.jsp">LOGOUT</a></li> Welcome to <li style="text-align:right; font-weight:bold; color:#FFCC00;"><%=UserID %></li> </ul> </div> <!--1st drop down menu --> <div id="dropmenu1" class="dropmenudiv"> <a href="vehiclemasterentry.jsp">Vehicle Entry</a> <a href="bookingentryframe.jsp">Booking Entry</a> <a href="returnentryframe.jsp">Return Entry</a> <a href="#"></a></div> <!--2nd drop down menu --> <div id="dropmenu5" class="dropmenudiv"> <a href="changepassword.jsp">Change Password</a> </div> <div id="dropmenu2" class="dropmenudiv" style="width: 150px;"> <a href="Billgeneration.jsp">Receipt </a> <a href="bill_final.jsp">Payment</a> <a href="#"></a></div> <!--3rd drop down menu --> <div id="dropmenu3" class="dropmenudiv" style="width: 150px;"> <a href="Bill.jsp">Bill Details</a> <a href="voucher.jsp">Voucher Details</a> <a href="vehicle.jsp">Vehicle Details</a></div> <a href="vehiclebooking.jsp">Voucher Booking</a> <a href="vehiclereturn.jsp">Vehicle Return</a> <a href="feedback.jsp">Feedback</a> MOVE ON CLICK
Page: 65/87 65/87

<a href="lost_property.jsp">Lost Property</a> </td> <script type="text/javascript"> cssdropdown.startchrome("chromemenu") </script> <td width="1" height="2"></td> </tr> </table></td> </tr> <tr> <td align="center" valign="middle"> </td> </tr> </table> </div> <br /> <table width="750" border="0" cellspacing="0" cellpadding="0" align="center"> <tr> <td height="25" align="center" bgcolor="#CCCCCC"><font color="#990000" size="+2">Vehicle Master Entry</font></td> </tr> </table> <p> <form name="frmventry" action="vehiclemaster_action.jsp" method="post"> <table width="900" border="0" cellspacing="0" cellpadding="0" align="center"> <tr> <td width="219" align="right">&nbsp;</td> <td width="168" height="25" align="right" class="font"><div align="left"><strong>Vehicle Number&nbsp;</strong></div></td> <td width="513"><input type="text" name="txtVNo" id="txtVNo" size="20" /></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong>Vehicle Type&nbsp; </strong></div></td> MOVE ON CLICK
Page: 66/87 66/87

<td><input name="txttype" type="text" id="txttype" size="20" /></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong>Vehicle Catagory&nbsp; </strong></div></td> <td> <select name="txtcategory" id="txtcategory" style="color:#666;"> <option selected="selected">--Catagory--</option> <option >Ac</option> <option >Non-Ac</option> </select></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong><span class="all_form_title">Price Per K.M&nbsp;</span></strong></div></td> <td><input type="text" name="txtVpperkm" id="txtVpperkm" size="20" /></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong><span class="all_form_title">Price Per Haulting&nbsp;</span></strong></div></td> <td><input type="text" name="txtVperhold" id="txtVperhold" size="20" /></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong><span class="all_form_title">Price per Extra K.M&nbsp;</span></strong></div></td> <td><input type="text" name="txtVextkm" id="txtVextkm" size="20" /></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong><span class="all_form_title">Per 100 K.M&nbsp;</span></strong></div></td> MOVE ON CLICK
Page: 67/87 67/87

<td><input type="text" name="txt100km" id="txt100km" size="20" /></td> </tr> <tr> <td align="right">&nbsp;</td> <td height="25" align="right" class="font"><div align="left"><strong>Per 250 K.M&nbsp; </strong></div></td> <td><input type="text" name="txt250km" id="txt250km" size="20" /></td> </tr> <tr> <td align="right"></td> <td height="25" align="right" class="font"><div align="left"><strong><span class="all_form_title">Vehicle Capacity</span></strong></div></td> <td><input type="text" name="txtVcapjrny" id="txtVcap" size="20" /></td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td><input name="submit" type="submit" id="submit" value="Insert" /> <input name="cancel" type="reset" id="cancel" value="Cancel" /></td> </tr> </table> </form> &nbsp;&nbsp;&nbsp; <form action="vehiclemasterentry.jsp" name="frmEmp" method="post" onsubmit="call(this)"> <table width="514" border="1" cellspacing="0" cellpadding="3" align="center"> <tr> <th colspan="8" scope="col" size:18px">Vehicle Action Form</th> </tr> <tr> <th colspan="8" scope="col" align="right"> <font color="#FF9900">(Search by Vehicle [ No./ Type / Cat. ]) </font>&nbsp;&nbsp;<input type="text" name="Search" size="30" color:#FFFFCC; color:#3399FF; font-weight:bold" /> MOVE ON CLICK
Page: 68/87 68/87

style="background:#999999; color:#CC0000; font-

style="background-

&nbsp; <input type="image" name="search" src="../images/icon/search.gif" value="Search" title="Search records" /> </tr> <tr bgcolor="#CCCC00" style="background:#999999; color:#FFCC00; font-size:16px; fontweight:bold"> <td width="74">&nbsp;Vehicle No.</td> <td /></a><br /> <a href="vehiclemasterentry.jsp?idd=20"><img src="../images/icon/darrow.gif" width="15" height="15" title="Sort Asc Order" border="0" /></a></td> <td width="172">&nbsp;Vehicle Type</td> <td width="120">&nbsp;Vehicle Category</td> <td </tr> <%! String vno1="",vtype1="",vcat1="",sql1=null,se=""; %> <% se=request.getParameter("Search"); try { sql1="Select * from vehiclemaster where vno='"+se+"' or vtype ='"+se+"' or vcat ='"+se+"' order by vno"; rs=stmt.executeQuery(sql1); if(!se.equals("")) { while(rs.next()) { vno1=rs.getString("vno"); vtype1=rs.getString("vtype"); vcat1=rs.getString("vcat"); %> <tr bordercolor="#FF9900" style="font-weight:bolder; color:#FF0000"> MOVE ON CLICK
Page: 69/87 69/87

</th>

width="17"><a

href="vehiclemasterentry.jsp?idd=10"><img

src="../images/icon/uarrow.gif" width="15" height="15" title="Sort Desc Order" border="0"

colspan="3"

style="

background:#FFCCCC;

color:#006699"><center><b>Action</b></center></td>

<td colspan="2">&nbsp;<%=vno1 %></td> <td>&nbsp;<%=vtype1 %></td> <td><%=vcat1 %></td> <td width="19" align="center"><a href="vehiclemasterview.jsp?idd=1&amp;id=<%=vno1 %>"><img src="../images/icon/view.gif" title="View" border="0" /></a></td> <td width="24" align="center"><a href="vehiclemasteredit.jsp?id=<%=vno1 %>"><img src="../images/icon/edit.gif" title="Edit" border="0" /></a></td> <td width="30" align="center"><a href="vehiclemasterentry.jsp?idd=1&amp;del=<%=vno1 %>" onclick="return del()"> <img src="../images/icon/delete.gif" title="Delete" border="0" /></a></td> <% }//While closed %> </tr> <tr bgcolor="#990000"> <td colspan="8"></td> </tr> <% }//if closed else { %> <script> function call(frm) { if(frm.Search.value=="") { alert("Field should not be left blank...try again"); } } </script> <% } } MOVE ON CLICK
Page: 70/87 70/87

catch(Exception e) { //out.println("Error:"+e.getMessage()); } finally { rs.close(); } %> <%! String vno="",vtype="",vcat="",sql=null; %> <% int id=0; try { id=Integer.parseInt(request.getParameter("idd")); } catch(Exception e) { //out.println("Error:"+e.getMessage()); } //out.println("Value :"+id); try { if(id==10) sql="Select * from vehiclemaster order by vno"; else if(id==20) sql="Select * from vehiclemaster order by vno desc"; else sql="Select * from vehiclemaster order by vno"; rs=stmt.executeQuery(sql); while(rs.next()) { vno=rs.getString("vno"); MOVE ON CLICK
Page: 71/87 71/87

vtype=rs.getString("vtype"); vcat=rs.getString("vcat"); %> <tr bgcolor="#FFFFCC"> <td colspan="2">&nbsp;<%=vno %></td> <td>&nbsp;<%=vtype %></td> <td><%=vcat %></td> <td align="center"><a href="vehiclemasterview.jsp?idd=1&amp;id=<%=vno %>"><img src="../images/icon/view.gif" title="View" border="0" /></a></td> <td width="24" align="center"><a href="vehiclemasteredit.jsp?id=<%=vno %>"><img src="../images/icon/edit.gif" title="Edit" border="0" /></a></td> <td width="30" align="center"><a href="vehiclemasterentry.jsp?idd=1&amp;del=<%=vno %>" onclick="return del()"><img src="../images/icon/delete.gif" title="Delete" border="0" /></a></td> </tr> <% }//while closed } catch(Exception e) { out.println(e.getMessage()); } %> </table> </form> <div </body> </html> id="footer_adminframe" align="center"><font color="#FFFFFF">&nbsp;&nbsp;</font></div>

MOVE ON CLICK

Page: 72/87 72/87

SYSTEM TESTING & IMPLEMENTATION Software Testing Techniques: Software testing is a critical element of software quality assurance and represents the ultimate review of specification, designing and coding. Testing Objectives: 1. 2. 3. Testing is process of executing a program with the intent of finding an error. A good test case design is one that has a probability of finding an as yet A successful test is one that uncovers an as yet undiscovered error.

undiscovered error. These above objectives imply a dramatic change in view port. Testing cannot show the absence of defects, it can only show that software errors are present. Test Case Design: Any engineering product can be tested in one of two ways: White Box Testing: This testing is also called as glass box testing. In this testing, by knowing the specified function that a product has been designed to perform test can be conducted that demonstrates each function is fully operation at the same time searching for errors in each function. It is a test case design method that uses the control structure of the procedural design to derive test cases. Basis path testing is a white box testing. Basis Path Testing: i. ii. iii. iv. i. ii. iii. Flow graph notation Cyclomatic Complexity Deriving test cases Graph matrices Condition testing Data flow testing Loop testing

Control Structure Testing:

Black Box Testing: In this testing by knowing the internal operation of a product, tests can be conducted to ensure that all gears mesh, that is the internal operation performs according to specification and all internal components have been adequately exercised. It fundamentally focuses on the functional requirements of the software. The steps involved in black box test case design are: i. Graph based testing methods

MOVE ON CLICK

Page: 73/87 73/87

ii. iii. iv. Software Testing Strategies:

Equivalence partitioning Boundary value analysis Comparison testing

A software testing strategy provides a road map for the software developer. Testing is a set of activities that can be planned in advance and conducted systematically. For this reason a template for software testing a set of steps into which we can place specific test case design methods should be defined for software engineering process. Any software testing strategy should have the following characteristics: 1. Testing begins at the module level and works outward toward the integration of the entire computer based system. 2. Different testing techniques are appropriate at different points in time. 3. The developer of the software and an independent test group conducts testing. 4. Testing and Debugging are different activities but debugging must be accommodated in any testing strategy. Unit Testing: Unit testing focuses verification efforts in smallest unit of software design (module). 1. Unit test considerations 2. Unit test procedures Integration Testing: Integration testing is a systematic technique for constructing the program structure while conducting tests to uncover errors associated with interfacing. There are two types of integration testing: 1. Top-Down Integration: Top down integration is an incremental approach to construction of program structures. Modules are integrated by moving down wards throw the control hierarchy beginning with the main control module. 2. Bottom-Up Integration: Bottom up integration as its name implies, begins construction and testing with automatic modules. 3. Regression Testing: In this contest of an integration test strategy, regression testing is the re execution of some subset of test that have already been conducted to ensure that changes have not propagate unintended side effects. Validation Testing:

MOVE ON CLICK

Page: 74/87 74/87

At the culmination of integration testing, software is completely assembled as a package; interfacing errors have been uncovered and corrected, and a final series of software tests validation testing may begin. Validation can be fined in many ways, but a simple definition is that validation succeeds when software functions in a manner that can be reasonably expected by the customer. Reasonable expectation is defined in the software requirement specification a document that describes all user-visible attributes of the software. The specification contains a section titled Validation Criteria. Information contained in that section forms the basis for a validation testing approach.

Validation Test Criteria: Software validation is achieved through a series of black-box tests that demonstrate conformity with requirement. A test plan outlines the classes of tests to be conducted, and a test procedure defines specific test cases that will be used in an attempt to uncover errors in conformity with requirements. Both the plan and procedure are designed to ensure that all functional requirements are satisfied; all performance requirements are achieved; documentation is correct and human-engineered; and other requirements are met. After each validation test case has been conducted, one of two possible conditions exist: (1) The function or performance characteristics conform to specification and are accepted, or (2) a deviation from specification is uncovered and a deficiency list is created. Deviation or error discovered at this stage in a project can rarely be corrected prior to scheduled completion. It is often necessary to negotiate with the customer to establish a method for resolving deficiencies. Configuration Review: An important element of the validation process is a configuration review. The intent of the review is to ensure that all elements of the software configuration have been properly developed, are catalogued, and have the necessary detail to support the maintenance phase of the software life cycle. The configuration review sometimes called an audit. Alpha And Beta Testing: It is virtually impossible for a software developer to foresee how the customer will really use a program. Instructions for use may be misinterpreted; strange combination of data may be regularly used; and output that seemed clear to the tester may be unintelligible to a user in the field. MOVE ON CLICK
Page: 75/87 75/87

When custom software is built for one customer, a series of acceptance tests are conducted to enable the customer to validate all requirements. Conducted by the end user rather than the system developer, an acceptance test can range from an informal test drive to a planned and systematically executed series of tests. In fact, acceptance testing can be conducted over a period of weeks or months, thereby uncovering cumulative errors that might degrade the system over time. If software is developed as a product to be used by many customers, it is impractical to perform formal acceptance tests with each one. Most software product builders use a process called alpha and beta testing to uncover errors that only the end user seems able to find. A customer conducts the alpha test at the developers site. The software is used in a natural setting with the developer looking over the shoulder of the user and recording errors and usage problems. Alpha tests are conducted in controlled environment. The beta test is conducted at one or more customer sites by the end user of the software. Unlike alpha testing, the developer is generally not present. Therefore, the beta test is a live application of the software in an environment that cannot be controlled by the developer. The customer records all problems that are encountered during beta testing and reports these to the developer at regular intervals. As a result of problems reported during bets test, the software developer makes modification and then prepares for release of the software product to the entire customer base. Implementation: Implementation is the process of having systems personnel check out and put new equipment into use, train users, install the new application depending on the size of the organization that will be involved in using the application and the risk associated with its use, systems developers may choose to test the operation in only one area of the firm, say in one department or with only one or two persons. Sometimes they will run the old and new systems together to compare the results. In still other situation, developers will stop using the old system one-day and begin using the new one the next. As we will see, each implementation strategy has its merits, depending on the business situation in which it is considered. Regardless of the implementation strategy used, developers strive to ensure that the systems initial use in trouble-free. Once installed, applications are often used for many years. However, both the organization and the users will change, and the environment will be different over weeks and months. Therefore, the application will undoubtedly have to be maintained; modifications and changes will be made to the software, files, or procedures to meet emerging user requirements. Since organization systems and the business environment undergo continual change, the information MOVE ON CLICK
Page: 76/87 76/87

systems should keep pace. In this sense, implementation is ongoing process. Evaluation of the system is performed to identify its strengths and weakness. The actual evaluation can occur along any of the following dimensions. Operational Evaluation: assessment of the manner in which the system functions, including ease of use, response time, suitability of information formats, overall reliability, and level of utilization. Organization Impact: Identification and measurement of benefits to the organization in such areas as financial concerns operational efficiency, and competitive impact. Includes impact on internal and external information flows. User Manager Assessment: Evaluation of the attitudes of senior and user mangers within the organization, as well as end-users. Development Performance: Evaluation of the development process in accordance with such yardsticks as overall development time and effort, conformance to budgets and standards, and other project management criteria. Includes assessment of development methods and tools. Unfortunately system evaluation does not always receive the attention it merits. Where properly managed however, it provides a great deal of information that can improve the effectiveness of subsequent application efforts.

MOVE ON CLICK

Page: 77/87 77/87

REPORT GENERATION Report generation is an integral part of enterprise application development. Choosing the right kind of report generation strategy decides the success of the application in terms of cost and performance. The whitepaper discusses some of the key factors that need to be considered when architecting reporting systems. Picking the right kind of reporting tools also plays a significant role in deciding the scalability and cost of the system. We will discuss some of the reporting tools which are widely used in the existing reporting systems. Selecting the best out of these tools is a crucial decision. ORACLE reporting service is one of the hot reporting tools; the white paper gives an introduction to the tool. Comparing reporting tools in terms of performance and cost is a really difficult job; and these measures will vary from architecture to architecture. But comparing the JAVA features available in these tools is very interesting for a JAVA chap. Excel reporting is an integral part of many financial applications. Many retail applications require Excel reports with fairly large amount of data and good format. The simple approach which comes into our mind will be to uses Excel component. But Microsoft doesn't recommend this approach. One of the best alternatives is explained in the Excel Reporting section. Securing the data exposed by reports is also a critical decision. Report Generation Tools: Let's discuss some of the reporting tools which are widely used in the existing reporting systems. Selecting the best out of these tools is a crucial decision. Three main reporting tools available in the JAVA code space are: JAVA Reports. Comparative Study. Active Reports. SQL Reporting Service.

MOVE ON CLICK

Page: 78/87 78/87

IMPLEMENTATION Implementation includes all those activities that take place to convert from the old system to the new. The old system consists of manual operations, which is operated in a very different manner from the proposed new system. A proper implementation is essential to provide a reliable system to meet the requirements of the organizations. An improper installation may affect the success of the computerized system. Implementation Methods: 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 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 for maintaining two systems in parallel is very high. This outweighs its benefits. Another commonly method is a direct cut over from the existing manual system to the computerized system. The change may be within a week or within a day. 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 entirety of the system.

Implementation Plan: The implementation plan includes a description of all the activities that must occur to implement the new system and to put it into operation. It identifies the personnel responsible for the activities and prepares a time chart for implementing the system. The implementation plan consists of the following steps.

1. List all files required for implementation. 2. Identify all data required to build new files during the implementation. 3. List all new documents and procedures that go into the new system.

MOVE ON CLICK

Page: 79/87 79/87

The implementation plan should anticipate possible problems and must be able to deal with them. The usual problems may be missing documents; mixed data formats between current and files, errors in data translation, missing data etc.

MOVE ON CLICK

Page: 80/87 80/87

SECURITY MEASURES TAKEN With security threats proliferating globally in just minutes, a top priority for customers is securing their information assets and minimizing the impact of unauthorized intrusions and viruses. This strongly needs the implementation of a pro-active pervasive security approach. It is a solution that protects the network and the data that traverse it, ensures the availability of the network and its resources and reduces expenses. This feature structures the authentication methods and access controls making sure that only authorized users access the organizations information resources and only those resources which they are trusted to access for their role in the organization . This also incorporates browserlevel encryption which protects all of our business information before it travels over the web. For every system, security is the main concern after when the software is installed. The security needs from all the section of the computer. The security from external factor, internal factor or the exceptional conditions of software engineering. For any system to be long lasting, the system to be secured at every level. Though it is not possible to keep safe at all level but at every level there needs a maximize security. For a system which is only one level or two level secured have the maximum chance of failure because they concentrate only upon few areas and rest is bared. Sometimes this creates the lethal situation for the system. So only the multilevel security is the best for the reason of higher system sufficiency. Now we discuss about the parts and aspects of the multilevel security: Application level security Database level security Operating System level Security In this level of security we discuss about the systems application after installation. When the system starts working then there are certain boundaries about the use of software or programs. This may be a minimum criterion for to be run such as minimum primary limit, minimum storage space, the way of using software/ programs, the supporting software versions etc. So in other sense we can say that not only the designed program/software the desired work can be done but it really needs the support of coordinating software / hardwires. Database Level Security: Every software has its data storage and it is obvious to keep it safe and secure from unauthorized user. The database level security can be achieved by using RDBMS. It means there needs a lot of hard work to keep this level secure. How data are related, is there any MOVE ON CLICK
Page: 81/87 81/87

Application Level Security:

violation of rule among data entry, is correct data is passing, can data be retrieved, can there is rule violation in boundary conditions? So there are lots of query among the database level security. The more it is secured the more significant will be the program. This also concerns about the logical concerns of the program. Operating System Level Security: An operating system level security means that how much system is preserved from external/internal haphazard. The happening may be from viruses, operating system failure, and unauthorized user etc. so there needs an advance care of operating system to do this. The system administrators do this. The work of administrator (system) is to carry all the technical aspects of the software related to the software/program. The security in the Application is implemented by two ways: 1. Login Page: It is a kind of security, in which only the authenticated user or the administrator himself can enter in to the site and will be able to use the privileges of Vehicle Section after logging into the Page. So, it is must to login into the Vehicle section before using any features of the Vehicle Section. 2. Web.xml: This is a form of security in which we can give authentication and authorization.

MOVE ON CLICK

Page: 82/87 82/87

PROJECT PLANNING 12. GANTT CHART Gantt charts are mainly used to allocate resources to activities. The resources allocated to activities include staff, hardware and software. Gantt charts are useful for resource planning. A gantt chart is a special type of bar chart where each bar represents an activity. The bars are shown along a timeline. The length of each bar is proportional to the duration of time plan for corresponding activity. Gantt charts used in software project management are actually enhanced versions of the standard gantt charts. In the Gantt chart s used for software project management each bar consists of a white part and a shaded part. The shaded part of the bar shows the length of time each task is estimated to take. The white chart shows the slake time , i.e . the later time by which the task must be finished. Sl No. 1 2 3 4 5 6 7 8 9 10 Task Name Requirements Collection Requirement Analysis Data Analysis Screen Design Report Design Datsbase Design Code Generation Unit Testing Integration & System Testing Installation DURATION 4days 15days 5days 23days 8days 15days 45days 43days 6days 1days

MOVE ON CLICK

Page: 83/87 83/87

13.

PERT CHART The Program (or Project) Evaluation and Review Technique, commonly

abbreviated PERT, is a model for project management designed to analyze and represent the tasks involved in completing a given project. PERT is a method to analyze the involved tasks in completing a given project, especially the time needed to complete each task, and identifying the minimum time needed to complete the total project. PERT was developed primarily to simplify the planning and scheduling of large and complex projects. It was developed by Bill Pocock of Booz Allen Hamilton and Gordon Person of the U.S. Navy Special Projects Office in 1957 to support the U.S. Navy's Polaris nuclear submarine project. It was able to incorporate uncertainty by making it possible to schedule a project while not knowing precisely the details and durations of all the activities. It is more of an event-oriented technique rather than start- and completion-oriented, and is used more in projects where time, rather than cost, is the major factor. It is applied to very largescale, one-time, complex, non-routine infrastructure and Research and Development projects.

Report Design Requirement analysis 1 2 14 3 5 Data analysis Screen Design 5 4 Database Design 23 8 6 15

Coding

Testing 43

2 Requirement Collection

9 43

8 Unit testing 10 Execution

MOVE ON CLICK

Page: 84/87 84/87

14.

Future Scope of the Project Aligning technical decision with business requirements is important to project success.

Failure to clearly identify functional requirements that align with the business often results in a design that does not meet with business needs even after development. Often these failures become the part of future review leading to time updating in existing system. These are carried out at three level in relation to this project. I. At implementation level it was found some section of code takes time to execute and it was discussed with organization to implement AJAX in that code section to fully speedup. For that cose consideration is under consideration.
II.

In future we want to merge all the travel agencies with in Orissa to provide better facility to our customers.

MOVE ON CLICK

Page: 85/87 85/87

Conclusion
This project is beneficial to all those users who are looking for booking their tours online by searching different places and different travel agencies around their desired place. This site gives them a better way to search and book their journey. This project has been developed by us as we thought that this type of project is worth making because this can be used to give information and fulfill a necessary requirement of this internet era. Our project also provides a beautiful interface to work as well as having a good database to keep track all the user records. User friendly screens are provided. It has been thoroughly tested and implemented.

MOVE ON CLICK

Page: 86/87 86/87

Bibliography
The following books and manuals provided a lot of help to us in making this project a reality.
JAVA COMPLETE REFERENCE PATRICK NAUGHTON, HERBERT SCHILDT JAVA HOW TO PROGRAM DEITERL & DEITEL JAVA UNLEASHED JDBC DATABASE ACCESS WITH JAVA GRAHAM AMELTON, RICK CATTEL, SERVLET PROGRAMMING ORELLY SOFTWARE ENGINEERING R. E. FAIRELY SOFTWARE ENGINEERING PRESSMAN AN INTEGRATED APPROACH TO SOFTWARE ENGINNERING PANKAJ JALOTE NAROSA PUBLISING HOUSE FUNDAMENTALS OF DATABASE SYSTEMS ELMASRI & NAVATHE ADDISON WESLY SQL, PL/SQL IVAN BAYROSS BPB PUBLICATIONS
SYSTEM ANALYSIS AND DESIGN

ELIAS M AWAD GALGOTIA


J2EE 2
ND

EDITION WROX PRESS

MOVE ON CLICK

Page: 87/87 87/87