Online Venu Booking Content Doc.docx

INTRODUCTION INTRODUCTION TO PROJECT PURPOSE OF THE PROJECT EXISTING SYSTEM & ITS DISADVANTAGES PROPOSED SYSTEM & ITS ADVANTAGES

1. SYSTEM ANALYSIS

2.1.

STUDY OF THE SYSTEM

2.2.

PROCESS MODELS USED WITH JUSTIFICATION

2.3.

SYSTEM ARCHITECTURE

2. FEASIBILITY STUDY

3.1.

TECHNICAL FEASIBILITY

3.2.

OPERATIONAL FEASIBILITY

3.3.

ECONOMIC FEASIBILITY

3. REQUIREMENT SPECIFICATIONS

4.1.

FUNCIONAL REQUIREMENTS

4.2.

PERFORMANCE REQUIREMENTS

4.3.

SOFTWARE REQUIREMENTS

4.4.

HARDWARE REQUIREMENTS

4.4.1.

INTRODUCTION TO JAVA

4.4.2.

Servlets/JSP

4.4.3.

JDBC

4.4.4.

Oracle

4.4.5.

HTML

4.4.6.

Java Script

4. SYSTEM DESIGN

5.1 .

INTRODUCTION

5.2

UML DIAGRAMS

5.3

NORMALIZATION

5.4

DATA DICTIONARY

5. OUTPUT SCREENS

6. SYSTEM TESTING

7.1

INTRODUCTION TO TESTING

7.2

TESTING STRATEGIES

7. SYSTEM SECURITY

8.1

INTRODUCTION

8.2

SECURITY IN SOFTWARE

ONLINE VENUE BOOKING

Objective

The objective of the project is to reserve a venue for functions, parties, weddings, meetings etc., user can enter into a single site for reservation which provides vacancies and profile of different venues. Existing system:

In the present world the reservation of venues are done through some agencies, electronic services and venue providers. The user can make arrangements face to face with the agent and can make depending on services provided by the agency. Through venue provider, user can make arrangements and have a direct contact with the provider. Problems

In agencies access may be limited to physical hours of operation Websites are there but only regarding particular venue. If that particular venue is not Available they have to go to other site which is a time consuming process.Last alternative is directly contacting the venue provider. But they can give information only about their own venue and is time consuming as the user checks with multiple services on their own. All this consumes lot of time. Proposed system:

To overcome the above problems we came up with an idea to implement a system called Suburb Possessor ship.The System that is developed will help the users to plan their reservations for functions, parties, weddings, meetings etc., by not getting into troubles through some agencies. They can enter into a single site which provides vacancies and profile of different venues. This provides a solution for smooth running of the schedules of the users. Advantages

1. Users need not go to venues provider for booking venues.

2. Our system also helps venue providers since they can personally reserve venues for users which are also through our system. 3. Our system provides profile of different venues. So users can find different venues at single place.

.

2.1 SYSTEM ANALYSIS

SOFTWARE REQUIREMENT SPECIFICATION What is SRS? Software Requirement Specification (SRS) is the starting point of the software developing activity. As system grew more complex it became evident that the goal of the entire system cannot be easily comprehended. Hence the need for the requirement phase arose. The software project is initiated by the client needs. The SRS is the means of translating the ideas of the minds of clients (the input) into a formal document (the output of the requirement phase.) The SRS phase consists of two basic activities: 1) Problem/Requirement Analysis: The process is order and more nebulous of the two, deals with understand the problem, the goal and constraints. 2) Requirement Specification: Here, the focus is on specifying what has been found giving analysis such as representation, specification languages and tools, and checking the specifications are addressed during this activity.The Requirement phase terminates with the production of the validate SRS document. Producing the SRS document is the basic goal of this phase. ROLE OF SRS The purpose of the Software Requirement Specification is to reduce the communication gap between the clients and the developers. Software Requirement Specification is the medium though which the client and user needs are accurately specified.

It forms the basis of software

development. A good SRS should satisfy all the parties involved in the system.

SCOPE This document is the only one that describes the requirements of the system. It is meant for the use by the developers, and will also be the basis for validating the final delivered system. Any changes made to the requirements in the future will have to go through a formal change approval process. The developer is responsible for asking for clarifications, where necessary, and will not make any alterations without the permission of the client.

2.1 PROCESS MODEL USED WITH JUSTIFICATION There are various software development approaches defined and designed which are used/employed during development process of software, these approaches are also referred as "Software Development Process Models". Each process model follows a particular life cycle in order to ensure success in process of software development.

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

The stages of "The Waterfall Model" are: Requirement Analysis & Definition: All possible requirements of the system to be developed are captured in this phase. Requirements are set of functionalities and constraints that the end-user (who will be using the system) expects from the system. The requirements are gathered from the end-user by consultation, these requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model. System & Software Design: Before a starting for actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model. Implementation & Unit Testing: On receiving system design documents, the works divided in modules/units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality; this is referred to as Unit Testing. Unit testing mainly verifies if the modules/units meet their specifications. Integration & System Testing: As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during Integration phase and tested to check if all modules/units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer. Operations & Maintenance:

This phase of "The Waterfall Model" is virtually never ending phase (Very long). Generally, problems with the system developed (which are not found during the development life cycle) come up after its practical use starts, so the issues related to the system are solved after deployment of the system. Not all the problems come in picture directly but they arise time to time and needs to be solved; hence this process is referred as Maintenance.

Advantages and Disadvantages of Waterfall Model: Advantages: The advantage of waterfall development is that it allows for departmentalization and managerial control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time. Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative steps. Disadvantages: The disadvantage of waterfall development is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. Alternatives to the waterfall model include joint application development (JAD), rapid application development (RAD), synch and stabilize, build and fix, and the spiral model.

2.4 SYSTEM ARCHITECTURE Architecture flow: Below architecture diagram represents mainly flow of requests from users to database through servers. In this scenario overall system is designed in three tires separately using three layers called presentation layer, business logic layer and data link layer. This project was developed using 3-tire architecture.

User

SERVER Request

URL Pattern:

Data Base

Response

Response sent from the servlet

Presentation Layer

URL Request sent through the browser

SERVLETS AT THE SERVER Reply from the database

SIDE

according to the statement

Verifying or updating the database through a statement

DATABASE

URL pattern represents how the requests are flowing through one layer to another layer and how the responses are getting by other layers to presentation layer through server in architecture diagram.

Feasibility Study: The purpose of feasibility study is not to solve the problem, but to determine whether the problem is worth solving.T he feasibility study concentrates on the following area. 

Operational Feasibility



Technical Feasibility



Economic Feasibility Operational Feasibility: Operational feasibility study tests the operational scope of the software to be developed. The proposed software must have high operational feasibility. The usability will be high. Technical Feasibility: Thetechnical feasibility study compares the level of technology available in the software development firm and the level of technology required for the development of the product. Here the level of technology consists of the programming language, the hardware resources, Other software tools etc. Economic Feasibility: The economic feasibility study evaluate the cost of the software

development

against

the

ultimate

income

or

benefits

developed system.There must be scopes for profit after the successful Completion of the project.

gets

from

the

4.1 FUNCTIONAL REQUIREMENTS SPECIFICATION

Modules: The system is proposed to have the following modules: (1)

Admin

(2)

Search

(3)

Venue Provider

(4)

User

Registration The registration module deals with the intake of complete details of the user and venues. The user has to enter the personal details. Registration for venue providers will be done directly by the administrator in order to confirm that the venue they provide is at correct place and all the details are correct. Venue Providers has to give their venue name, address and other contact details. By providing the above details both user and venue provider can create their own accounts. Search The search module allows users to search for venues of their desire. The user has to just specify the place. The profile of all the venues in that place are displayed to the user. The user can select a venue and can check the availability of the venue by specifying a date. If it is available the user can go for reservation otherwise he can check the availability of other venues.

Reservation In this module the user has to tell the venue name, check-in date, check-in and checkout times in-order to reserve a venue. Cancellation The user has the facility to cancel a venue. For cancellation the user should login and provide the details of the venue he already reserved.

Venues Profile Submission This module deals with the venue provider. Venue Provider will provides the details of the venue like venue name, address, capacity, cost, contact numbers etc. When the users search for a venue these details will be displayed.

4.2 PERFORMANCE REQUIREMENTS Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely with the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use. The requirement specification for any system can be broadly stated as given below: The system should be able to interface with the existing system 

The system should be accurate



The system should be better than the existing system The existing system is completely dependent on the user to perform all the duties.

Software Requirements:

Technology

:

J2SE and J2EE



Web-Technologies

:

HTML ,JavaScript ,CSS



Web Server

:

Tomcat 7.0



Java Version

:

JDK1.6



Backend Database

:

Oracle 10G

Processor

:

Pentium IV

RAM Capacity

:

1GB

Hardware Requirements:

Java Technology Java technology is both a programming language and a platform.

The Java Programming Language:

The Java programming language is a high-level language that can be characterized by all of the following buzzwords: 

Simple



Architecture neutral



Object oriented



Portable



Distributed



High performance



Interpreted



Multithreaded



Robust



Dynamic



Secure

With most programming languages, you either compile or interpret a program so that you can run it on your computer. The Java programming language is unusual in that a program is both compiled and interpreted. With the compiler, first you translate a program into an intermediate language called Java byte codes —the platform-independent codes interpreted by the interpreter on the Java platform. The interpreter parses and runs each Java byte code instruction on the computer.

Compilation happens just once; interpretation occurs each time the program is executed. The following figure illustrates how this works.

FIGURE 2- WORKING OF JAVA You can think of Java bytecodes as the machine code instructions for the Java Virtual Machine (Java VM). Every Java interpreter, whether it’s a development tool or a Web browser that can run applets, is an implementation of the JVM. Java bytecodes help make “write once, run anywhere” possible. You can compile your program into bytecodes on any platform that has a Java compiler. The bytecodes can then be run on any implementation of the Java VM. That means that as long as a computer has a Java VM, the same program written in the Java programming language can run on Windows 2000, a Solaris workstation, or on an iMac. The Java Platform A platform is the hardware or software environment in which a program runs. We’ve already mentioned some of the most popular platforms like Windows 2000, Linux, Solaris, and MacOS. Most platforms can be described as a combination of the operating system and hardware. The Java platform differs from most other platforms in that it’s a software-only platform that runs on top of other hardware-based platforms. The Java platform has two components: 

The Java Virtual Machine (Java VM)



The Java Application Programming Interface (Java API)

You’ve already been introduced to the Java VM. It’s the base for the Java platform and is ported onto various hardware-based platforms. The Java API is a large collection of ready-made software components that provide many useful capabilities, such as graphical user interface (GUI) widgets. The Java API is grouped into libraries of related classes and interfaces; these libraries are known as packages. The next section, What Can Java Technology Do?, highlights what functionality some of the packages in the Java API provide. The following figure depicts a program that’s running on the Java platform. As the figure shows, the Java API and the virtual machine insulate the program from the hardware.

FIGURE 3- THE JAVA PLATFORM Native code is code that after you compile it, the compiled code runs on a specific hardware platform. As a platform-independent environment, the Java platform can be a bit slower than native code. However, smart compilers, well-tuned interpreters, and just-in-time bytecode compilers can bring performance close to that of native code without threatening portability. What Can Java Technology Do?

The most common types of programs written in the Java programming language are applets and applications. If you’ve surfed the Web, you’re probably already familiar with applets. An applet is a program that adheres to certain conventions that allow it to run within a Java-enabled browser. However, the Java programming language is not just for writing cute, entertaining applets for the Web. The general-purpose, high-level Java programming language is also a powerful software platform. Using the generous API, you can write many types of programs.

An application is a standalone program that runs directly on the Java platform. A special kind of application known as a server serves and supports clients on a network. Examples of servers are Web servers, proxy servers, mail servers, and print servers. Another specialized program is a servlet. A servlet can almost be thought of as an applet that runs on the server side. Java Servlets are a popular choice for building interactive web applications, replacing the use of CGI scripts. Servlets are similar to applets in that they are runtime extensions of applications. Instead of working in browsers, though, servlets run within Java Web servers, configuring or tailoring the server. How does the API support all these kinds of programs? It does so with packages of software components that provide a wide range of functionality. Every full implementation of the Java platform gives you the following features: 

The essentials: Objects, strings, threads, numbers, input and output, data structures, system

properties, date and time, and so on. 

Applets: The set of conventions used by applets.



Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram

Protocol) sockets, and IP (Internet Protocol) addresses. 

Internationalization: Help for writing programs that can be localized for users worldwide.

Programs can automatically adapt to specific locales and be displayed in the appropriate language. 

Security: Both low level and high level, including electronic signatures, public and private

key management, access control, and certificates. 

Software components: Known as JavaBeansTM, can plug into existing component

architectures. 

Object serialization: Allows lightweight persistence and communication via Remote

Method Invocation (RMI). 

Java Database Connectivity (JDBCTM): Provides uniform access to a wide range of

relational databases.

The Java platform also has APIs for 2D and 3D graphics, accessibility, servers, collaboration, telephony, speech, animation, and more. The following figure depicts what is included in the Java 2 SDK.

FIGURE 4 – JAVA 2 SDK

ODBC Microsoft Open Database Connectivity (ODBC) is a standard programming interface for application developers and database systems providers. Before ODBC became a de facto standard for Windows programs to interface with database systems, programmers had to use proprietary languages for each database they wanted to connect to. Now, ODBC has made the choice of the database system almost irrelevant from a coding perspective, which is as it should be. Application developers have much more important things to worry about than the syntax that is needed to port their program from one database to another when business needs suddenly change. Through the ODBC Administrator in Control Panel, you can specify the particular database that is associated with a data source that an ODBC application program is written to use. Think of an ODBC data source as a door with a name on it. Each door will lead you to a particular database. For example, the data source named Sales Figures might be a SQL Server database, whereas the

Accounts Payable data source could refer to an Access database. The physical database referred to by a data source can reside anywhere on the LAN.

The ODBC system files are not installed on your system by Windows 95. Rather, they are installed when you setup a separate database application, such as SQL Server Client or Visual Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a file called ODBCINST.DLL. It is also possible to administer your ODBC data sources through a standalone program called ODBCADM.EXE. There is a 16-bit and a 32-bit version of this program, and each maintains a separate list of ODBC data sources.

From a programming perspective, the beauty of ODBC is that the application can be written to use the same set of function calls to interface with any data source, regardless of the database vendor. The source code of the application doesn’t change whether it talks to Oracle or SQL Server. We only mention these two as an example. There are ODBC drivers available for several dozen popular database systems. Even Excel spreadsheets and plain text files can be turned into data sources. The operating system uses the Registry information written by ODBC Administrator to determine which low-level ODBC drivers are needed to talk to the data source (such as the interface to Oracle or SQL Server). The loading of the ODBC drivers is transparent to the ODBC application program. In a client/server environment, the ODBC API even handles many of the network issues for the application programmer.

The advantages of this scheme are so numerous that you are probably thinking there must be some catch. The only disadvantage of ODBC is that it isn’t as efficient as talking directly to the native database interface. ODBC has had many detractors make the charge that it is too slow. Microsoft has always claimed that the critical factor in performance is the quality of the driver software that is used. In our humble opinion, this is true. The availability of good ODBC drivers has improved a great deal recently. And anyway, the criticism about performance is somewhat analogous to those who said that compilers would never match the speed of pure assembly

language. Maybe not, but the compiler (or ODBC) gives you the opportunity to write cleaner programs, which means you finish sooner. Meanwhile, computers get faster every year.

JDBC In an effort to set an independent database standard API for Java, Sun Microsystems developed Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access mechanism that provides a consistent interface to a variety of RDBMSs. This consistent interface is achieved through the use of “plug-in” database connectivity modules, or drivers. If a database vendor wishes to have JDBC support, he or she must provide the driver for each platform that the database and Java run on.

To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC. As you discovered earlier in this chapter, ODBC has widespread support on a variety of platforms. Basing JDBC on ODBC will allow vendors to bring JDBC drivers to market much faster than developing a completely new connectivity solution. JDBC was announced in March of 1996. It was released for a 90 day public review that ended June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon after. The remainder of this section will cover enough information about JDBC for you to know what it is about and how to use it effectively. This is by no means a complete overview of JDBC. That would fill an entire book.

JDBC Goals Few software packages are designed without goals in mind. JDBC is one that, because of its many goals, drove the development of the API. These goals, in conjunction with early reviewer feedback, have finalized the JDBC class library into a solid framework for building database applications in Java.

The goals that were set for JDBC are important. They will give you some insight as to why certain classes and functionalities behave the way they do. The eight design goals for JDBC are as follows: 1.

SQL Level API The designers felt that their main goal was to define a SQL interface for Java. Although not

the lowest database interface level possible, it is at a low enough level for higher-level tools and APIs to be created. Conversely, it is at a high enough level for application programmers to use it confidently. Attaining this goal allows for future tool vendors to “generate” JDBC code and to hide many of JDBC’s complexities from the end user.

2.

SQL Conformance SQL syntax varies as you move from database vendor to database vendor. In an effort to

support a wide variety of vendors, JDBC will allow any query statement to be passed through it to the underlying database driver. This allows the connectivity module to handle non-standard functionality in a manner that is suitable for its users.

3.

JDBC

must

be

implemental

on

top

of

common

database

interfaces

The JDBC SQL API must “sit” on top of other common SQL level APIs. This goal allows JDBC to use existing ODBC level drivers by the use of a software interface. This interface would translate JDBC calls to ODBC and vice versa.

4.

Provide a Java interface that is consistent with the rest of the Java system

Because of Java’s acceptance in the user community thus far, the designers feel that they should not stray from the current design of the core Java system.

5. Keep it simple This goal probably appears in all software design goal listings. JDBC is no exception. Sun felt that the design of JDBC should be very simple, allowing for only one method of completing a task per mechanism. Allowing duplicate functionality only serves to confuse the users of the API. 6.

Use strong, static typing wherever possible:

Strong typing allows for more error checking to be done at compile time; also, less errors appear at runtime. 7. Keep the common cases simple Because more often than not, the usual SQL calls used by the programmer are simple SELECT’s, INSERT’s, DELETE’s and UPDATE’s, these queries should be simple to perform with JDBC. However, more complex SQL statements should also be possible.

JDBC Driver Types: JDBC drivers are divided into four types or levels. The different types of jdbc drivers are: Type 1: JDBC-ODBC Bridge driver (Bridge) Type 2: Native-API/partly Java driver (Native) Type 3: AllJava/Net-protocol driver (Middleware) Type 4: All Java/Native-protocol driver (Pure)

Type 1 JDBC Driver JDBC-ODBC Bridge driver The Type 1 driver translates all JDBC calls into ODBC calls and sends them to the ODBC driver. ODBC is a generic API. The JDBC-ODBC Bridge driver is recommended only for experimental use or when no other alternative is available. Advantages:

The JDBC-ODBC Bridge allows access to almost any database, since the database's ODBC drivers are already available. Disadvantages: 1. Since the Bridge driver is not written fully in Java, Type 1 drivers are not portable. 2. A performance issue is seen as a JDBC call goes through the bridge to the ODBC driver, then to the database, and this applies even in the reverse process. They are the slowest of all driver types. 3. The client system requires the ODBC Installation to use the driver. 4. Not good for the Web.

Type 2 JDBC Driver Native-API/partly Java driver The distinctive characteristic of type 2 jdbc drivers are that Type 2 drivers convert JDBC calls into database-specific calls i.e. this driver is specific to a particular database. Some distinctive characteristic of type 2 jdbc drivers are shown below. Example: Oracle will have oracle native api. Advantage: The distinctive characteristic of type 2 jdbc drivers are that they are typically offer better performance than the JDBC-ODBC Bridge as the layers of communication (tiers) are less than that of Type1 and also it uses Native api which is Database specific.

Disadvantage: 1. Native API must be installed in the Client System and hence type 2 drivers cannot be used for the Internet. 2. Like Type 1 drivers, it’s not written in Java Language which forms a portability issue. 3. If we change the Database we have to change the native api as it is specific to a database 4. Mostly obsolete now 5. Usually not thread safe.

Type 3 JDBC Driver All Java/Net-protocol driver Type 3 database requests are passed through the network to the middle-tier server. The middle-tier then translates the request to the database. If the middle-tier server can in turn use Type1, Type 2 or Type 4 drivers. Advantage: 1. This driver is server-based, so there is no need for any vendor database library to be present on client machines. 2. This driver is fully written in Java and hence Portable. It is suitable for the web. 3. There are many opportunities to optimize portability, performance, and scalability. 4. The net protocol can be designed to make the client JDBC driver very small and fast to load. 5. The type 3 driver typically provides support for features such as caching (connections, query results, and so on), load balancing, and advanced system administration such as logging and auditing. 6. This driver is very flexible allows access to multiple databases using one driver. 7. They are the most efficient amongst all driver types.

Disadvantage : It requires another server application to install and maintain. Traversing the recordset may take longer, since the data comes through the backend server.

Type 4 JDBC Driver Native-protocol/all-Java driver The Type 4 uses java networking libraries to communicate directly with the database server. Advantage: 1. The major benefit of using a type 4 jdbc drivers are that they are completely written in Java to achieve platform independence and eliminate deployment administration issues. It is most

suitable for the web. 2. Number of translation layers is very less i.e. type 4 JDBC drivers don't have to translate database requests to ODBC or a native connectivity interface or to pass the request on to another server, performance is typically quite good. 3. You don’t need to install special software on the client or server. Further, these drivers can be downloaded dynamically. Disadvantage:

With type 4 drivers, the user needs a different driver for each database.

Servlets: Servlets are programs that run on a Web or application server and act as a middle layer between a request coming from a Web browser or other HTTP client and databases or applications on the HTTP server. Their job is to perform the following tasks, as illustrated in Figure

Database

Legacy application

Java application (Client /end User)

web service Web server (Servlets/JSP)

Figure: The role of web middleware

…………………….

1. Read the explicit data sent by the client. The end user normally enters this data in an HTML form on a Web page. However, the data could also come from an applet or a custom HTTP client program.

1.

Read the implicit HTTP request data sent by the browser: Figure shows a single arrow going from the client to the Web server (the layer in which servlets and JSP pages execute), but there are really two varieties of data: the explicit data the end user enters in are really two varieties of data: the explicit data the end user enters in a form and the behind-the-scenes HTTP information. Both types of data are critical to effective development. The HTTP information includes cookies, media types and compression schemes the browser understands, and so forth;

3. Generate the results. This process may require talking to a database, executing an RMI or CORBA call, invoking a Web service, or computing the response direcly.

4. Send the explicit data (i.e., the document) to the client. This document can be sent in a variety of formats, including text (HTML or XML), binary (GIF images), Excel, or even a compressed format like gzip that is layered on top of some other underlying format.

5. Send the implicit HTTP response data. The above figure shows a single arrow going from the Web middle layer (the servlet or JSP page) to the client, but there are really two varieties of data sent. In principle, servlets are not restricted to Web or application servers that handle HTTP requests but can be used for other types of servers as well. For example, servlets could be embedded in FTP or mail servers to extend their functionality.

HTML Webpages are written in HTML - a simple scripting language. HTML is short for HyperText Markup Language. 

Hypertext is simply a piece of text that works as a link.



Markup Language is a way of writing layout information within documents.

Basically an HTML document is a plain text file that contains text and nothing else. When a browser opens an HTML file, the browser will look for HTML codes in the text and use them to change the layout, insert images, or create links to other pages.

Since HTML documents are just text files they can be written in even the simplest text editor. A more popular choice is to use a special HTML editor - maybe even one that puts focus on the visual result rather than the codes - a so-called WYSIWYG editor ("What You See Is What You Get"). Some of the most popular HTML editors, such as FrontPage or Dreamweaver will let you create pages more or less as you write documents in Word or whatever text editor you're using. However, there are some very good reasons to create your own pages - or parts of them - by hand... It is possible to create webpages without knowing anything about the HTML source behind the page. There are excellent editors on the market that will take care of the HTML parts. All you need to do is layout the page.

HTML Tags What are HTML tags? 

HTML tags are used to mark-up HTML elements



HTML tags are surrounded by the two characters < and >



The surrounding characters are called angle brackets



HTML tags normally come in pairs like and



The first tag in a pair is the start tag, the second tag is the end tag



The text between the start and end tags is the element content



HTML tags are not case sensitive, means the same as

JAVA SCRIPT: Javascript is a scripting language that will allow you to add real programming to your webpages.

You can create small application type processes with javascript, like a calculator or a primitive game of some sort. However, there are more serious uses for javascript: 

Browser Detection Detecting the browser used by a visitor at your page. Depending on the browser, another page specifically designed for that browser can then be loaded.



Cookies Storing information on the visitor's computer, then retrieving this information automatically next time the user visits your page. This technique is called "cookies".



Control Browsers Opening pages in customized windows, where you specify if the browser's buttons, menu line, status line or whatever should be present.



Validate Forms Validating inputs to fields before submitting a form. An example would be validating the entered email address to see if it has an @ in it, since if not, it's not a valid address.



5.1 INTRODUCTION Systems design Introduction: Systems design is the process or art of defining the architecture, components, modules, interfaces, and data for a system to satisfy specified requirements. One could see it as the application of systems theory to product development. There is some overlap and synergy with the disciplines of systems analysis, systems architecture and systems engineering.

5.2 UML DIAGRAMS Unified Modeling Language:

The Unified Modeling Language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows. 

User Model View i. This view represents the system from the users perspective. ii. The analysis representation describes a usage scenario from the end-users perspective.



Structural model view i. In this model the data and functionality are arrived from inside the system. ii. This model view models the static structures.



Behavioral Model View

It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.



Implementation Model View In this the structural and behavioral as parts of the system are represented as they are to be built.



Environmental Model View

In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented.

UML is specifically constructed through two different domains they are:  UML Analysis modeling, this focuses on the user model and structural model views of the system.  UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a user’s point of view. Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view.

Actors are external entities that interact with the system. Examples of actors include users like administrator, bank customer …etc., or another system like central database.

CLASS DIAGRAM:-

Class Diagram:

UseCaseDiagram

Lname

PresentAddress

Fname extends

extends

extends

PermenentAddress extends

extends Registration PhNum extends extends User

EmailId

include

include Login

UserName

include Role

Logout PassWord Role

ViewVenueStatus(Provider):

VenueProvider

Registration

Login

Venue

Database

Enters Reg Information

Enters Login Info

Add Venue Info Stores Processing View Venue Info view Req Processing Update Venue Info update Req Processing Delete Venue Info delete Req Processing

2: Enters Login Info VenueProvider

Login

1: Enters Reg Information

3: Add Venue Info 6: View Venue Info 9: Update Venue Info 12: Delete Venue Info

Registration

5: Processing 8: Processing 11: Processing 14: Processing 4: Stores 7: view Req 10: update Req 13: delete Req

Venue

Visitor Sequence Diagram:

Database

Visitor

Registration

Login

Venue

Database

Enters Reg Information

Enters Login Info

Search venue Details

Search Req Processing

View Venue Info view Req Processing Online Reservation Reserve Req Processing Cancelletion Cancel Req Processing

2: Enters Login Info

Login

Visitor 1: Enters Reg Information

3: Search venue Details 6: View Venue Info 9: Online Reservation 12: Cancelletion

Registration

5: Processing 8: Processing 11: Processing 14: Processing 4: Search Req 7: view Req 10: Reserve Req 13: Cancel Req

Venue

Database

User Activity Diagram:

Venue Provider Acivity Diagram:

7.1 INTRODUCTION TO TESTING

7.1 INTRODUCTION TO TESTING Introduction to Testing: Testing is a process, which reveals errors in the program. It is the major quality measure employed during software development. During software development. During testing, the program is executed with a set of test cases and the output of the program for the test cases is evaluated to determine if the program is performing as it is expected to perform.

7.2 TESTING IN STRATEGIES In order to make sure that the system does not have errors, the different levels of testing strategies that are applied at differing phases of software development are :

Unit Testing: Unit Testing is done on individual modules as they are completed and become executable. It is confined only to the designer's requirements.

Each module can be tested using the following two Strategies: Black Box Testing: In this strategy some test cases are generated as input conditions that fully execute all functional requirements for the program. This testing has been uses to find errors in the following categories: Incorrect or missing functions Interface errors Errors in data structure or external database access Performance errors Initialization and termination errors. In this testing only the output is checked for correctness. The logical flow of the data is not checked

White Box testing : In this the test cases are generated on the logic of each module by drawing flow graphs of that module and logical decisions are tested on all the cases. It has been uses to generate the test cases in the following cases:  Guarantee that all independent paths have been Executed.  Execute all logical decisions on their true and false Sides.  Execute all loops at their boundaries and within their operational bounds



Execute internal data structures to ensure their validity.

Integrating Testing : Integration testing ensures that software and subsystems work together a whole. It tests the interface of all the modules to make sure that the modules behave properly when integrated together.

System Testing: Involves in-house testing of the entire system before delivery to the user. It's aim is to satisfy the user the system meets all requirements of the client's specifications.

Acceptance Testing : It is a pre-delivery testing in which entire system is tested at client's site on real world data to find errors. Test Approach :

Testing can be done in two ways: Bottom up approach Top down approach

Bottom up Approach: Testing can be performed starting from smallest and lowest level modules and proceeding one at a time. For each module in bottom up testing a short program executes the module

and provides the needed data so that the module is asked to perform the way it will when embedded with in the larger system. When bottom level modules are tested attention turns to those on the next level that use the lower level ones they are tested individually and then linked with the previously examined lower level modules.

Top down approach: This type of testing starts from upper level modules. Since the detailed activities usually performed in the lower level routines are not provided stubs are written. A stub is a module shell called by upper level module and that when reached properly will return a message to the calling module indicating that proper interaction occurred. No attempt is made to verify the correctness of the lower level module.

Validation: The system has been tested and implemented successfully and thus ensured that all the requirements as listed in the software requirements specification are completely fulfilled. In case of erroneous input corresponding error messages are displayed

8.1 INTRODUCTION System Security: Setting Up Authentication for Web Applications: Introduction: To configure authentication for a Web Application, use the element of the web.xml deployment descriptor. In this element you define the security realm containing the user credentials, the method of authentication, and the location of resources for authentication.

8.2 SECURITY IN SOFTWARE To set up authentication for Web Applications: 1. Open the web.xml deployment descriptor in a text editor or use the Administration Console. Specify the authentication method using

element. The

available options are:

BASIC Basic authentication uses the Web Browser to display a username/password dialog box. This username and password is authenticated against the realm.

FORM Form-based authentication requires that you return an HTML form containing the username and password. The fields returned from the form elements must be: j_username and j_password, and the action attribute must be j_security_check. Here is an example of the HTML coding for using FORM authentication:

The resource used to generate the HTML form may

be an HTML page, a JSP, or a servlet. You define this resource with the element. The HTTP session object is created when the login page is served. Therefore, the session.isNew () method returns FALSE when called from pages served after successful authentication.

9. BIBLIOGRAPHY

References for the Project Development Were Taken From the following Books and Web Sites . JAVA Technologies JAVA Complete Reference Java Script Programming by Yehuda Shiran Mastering JAVA Security JAVA2 Networking by Pistoria

JAVA Security by Scotl oaks Head First EJB Sierra Bates J2EE Professional by Shadab siddiqui JAVA server pages by Larne Pekowsley JAVA Server pages by Nick Todd HTML HTML Black Book by Holzner JDBC Java Database Programming with JDBC by Patel moss. Software Engineering by Roger Pressman