PROJECT REPORT ON

ONLINE BANKING
Submitted in the Partial Fulfillment of the Fifth Semester of

BACHELOR OF TECHNOLOGY IN INFORMATION TECHNOLOGY OF COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY BY ALSON BLASTO CYRAIC JUSTIN JOSE JOMA GEORGE SURYA RANI SUNNY SREEJA UNNIKRISHANAN

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING COLLEGE OF ENGINEERING POONJAR POONJAR THEKKEKKARA

KOTTAYAM 686582

COLLEGE OF ENGINEERING POONJAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE

This is certify that the project work entitled

ONLINE BANKING SOFTWARE

SJ & SJ online
Submitted by

JUSTIN JOSE Reg No: 14081817 for the partial fulfillment of completion of the sixth semester of Bachelor of Technology in Information Technology from Cochin University of Science & Technology is a bona-fied record of the work done by them during the period of DECEMBER 2009 to APRIL 2010

Aswathy M.S
Internal Project Guide Lecturer Dept. of Information Technology Technology

Deepak John
Project Coordinator Lecturer Dept. of Information

KOTTAYAM 686582

COLLEGE OF ENGINEERING POONJAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE

This is certify that the project work entitled

ONLINE BANKING SOFTWARE

SJ & SJ online
Submitted by

ALSON BASTO CYRIAC

Reg No: 14081803 for the partial fulfillment of completion of the sixth semester of Bachelor of Technology in Information Technology from Cochin University of Science & Technology is a bona-fied record of the work done by them during the period of DECEMBER 2009 to APRIL 2010

Aswathy M.S
Internal Project Guide Lecturer Dept. of Information Technology Technology

Deepak John
Project Coordinator Lecturer Dept. of Information

KOTTAYAM 686582

COLLEGE OF ENGINEERING POONJAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE

This is certify that the project work entitled

ONLINE BANKING SOFTWARE

SJ & SJ online
Submitted by

JOMA GEORGE
Reg No: 14081843 for the partial fulfillment of completion of the sixth semester of Bachelor of Technology in Information Technology from Cochin University of Science & Technology is a bona-fied record of the work done by them during the period of DECEMBER 2009 to APRIL 2010

Aswathy M.S
Internal Project Guide Lecturer Dept. of Information Technology Technology

Deepak John
Project Coordinator Lecturer Dept. of Information

KOTTAYAM 686582

COLLEGE OF ENGINEERING POONJAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE

This is certify that the project work entitled

ONLINE BANKING SOFTWARE

SJ & SJ online
Submitted by

SREEJA UNNIKRISHANAN Reg

No: 14081856

for the partial fulfillment of completion of the sixth semester of Bachelor of Technology in Information Technology from Cochin University of Science & Technology is a bona-fied record of the work done by them during the period of DECEMBER 2009 to APRIL 2010

Aswathy M.S
Internal Project Guide Lecturer Dept. of Information Technology Technology

Deepak John
Project Coordinator Lecturer Dept. of Information

KOTTAYAM 686582

COLLEGE OF ENGINEERING POONJAR

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CERTIFICATE

This is certify that the project work entitled

ONLINE BANKING SOFTWARE

SJ & SJ online
Submitted by

SURYA RANI SUNNY Reg

No: 14081859

for the partial fulfillment of completion of the sixth semester of Bachelor of Technology in Information Technology from Cochin University of Science & Technology is a bona-fied record of the work done by them during the period of DECEMBER 2009 to APRIL 2010

Aswathy M.S
Internal Project Guide Lecturer Dept. of Information Technology Technology

Deepak John
Project Coordinator Lecturer Dept. of Information

ACKNOWLEDGEMENT

If the words are considered as symbols of Approval and Token of Acknowledgement, then let the words play the heralding role of expressing my gratitude. First and Foremost, I praise the God Almighty for the grace he showered on us during our studies as well as our day to day life activities. I would like to express my gratitude to our principal Prof.Gymmy Joseph Kattoor for providing the facilities and constant encouragement in our achievement. I also express our heartfelt thanks to Mrs. Sindhu L, H.O.D of Computer Science and Engineering Department and project coordinator who helped us to materialize this project. I also sincerely thank the Computer Science and Engineering Faculty for providing us with invaluable help. Our project coordinator, Mr.Deepak John deserves a special mention, whose observation and assistance were very much helpful as well as valuable in sorting up our project work. Last but not the least, I owe to my family and my friends for giving us the help, strength and courage for accomplishing the task.

We would like to express our heartfelt gratitude and reverence to Miss. Aswathy M.S, lecturer in IT for their timely advices and encouragement.

ABSTRACT

The project is meant to develop a software system that is very useful to all users who want to manage their accounts. Using this software we can access all details of account and transaction can also be done very easily. It also provides the users to view details of their accounts, list of transactions and also to edit their details etc. The administrator has overall privilege on the software. The administrator can add new clients, view of the details all accounts, remove accounts and also approve the transactions made by clients.

TABLE OF CONTENTS

ACKNOWLEDGEMENT. 3 ABSTRACT......4 LIST OF FIGURES7 LIST OF ABBREVIATIONS....7

1.

INTRODUCTION..8 PROBLEM DEFINITION9

2.

3. SOFTWARE REQUIREMENT SPECIFICATION.......10 4. SYSTEM REQUIRMENTS......13 (A) (B) 5. (A) (B) (C) HARDWARE REQUIREMENTS SOFTWARE REQUIREMENTS SYSTEM STUDY.......14 EXISTING SYSTEM PROPOSED SYSTEM FEASIBILITY STUDY

6.

SYSTEM

DESIGN.17
(A) (B) 7.

MODULES DATA FLOW DIAGRAMS DATABASE

DESIGN26 (A)
8.

TABLE STRUCTURE INPUT/OUTPUTNDESIGN..30 INPUT DESIGN OUTPUT DESIGN SYSTEM IMPLEMENTATION.32 FAMILIARIZATION OF THE TOOLS TO BE USED IN IMPLEMENTATION

(A) (B)
9.

10. 11. 12. 13.

SOURCE CODE40 SCREEN SCHOTS..44 CONCLUSION..68 REFERNCES.69

LIST OF FIGURES

Fig 1: Data Flow diagram of Login (Context Level) Fig 2: Data Flow diagram of Administrator Module Fig 3: Data Flow diagram of Paid User Fig 4: Data Flow diagram of Free User

LIST OF ABBREVIATIONS

DBMS - DATA BASE MANAGEMENT SYSTEM RDBMS - RELATIONAL DATA BASE MANAGEMENT SYSETM SQL - STRUCTERED QUERRY LANGUAGE PHP-HYPERTEXT PREPROCESSOR HTML-HYPER TEXT MARKUP LANGUAGE

1. INTRODUCTION
Online banking software is time saving software which can be used by all users who want to manage accounts at their convenience. The present existing systems are very tedious and time consuming process as it requires a large number of paperworks and need large documentations. But with this software, the task becomes easy and reduces the workload .This application can be accessed via an internet connection at anytime and anywhere. Online banking is defined as the automated delivery of new and traditional banking products and services directly to customers through electronic, interactive communication channels. Online banking includes the systems that enable financial institution customers, individuals or businesses, to access accounts, transact business, or obtain information on financial products and services through a public or private network, including the Internet. This software includes two user levels namely:1. Administrator 2. Users\Client Users can view the details of the accounts; edit their profiles etc. They can transfer accounts to any beneficiaries whose has accounts in any banks by using their account number. The administrator can add new clients, view of the details all accounts, remove accounts and also approve the transactions made by clients. Online banking software is developed on the database system technology MySQL server, PHP and HTML. PHP as serverside scripting language and JavaScript as client side scripting language. This Software system provides the benefits of streamlining of operations, enhanced administration and control, improved response, time saving.

2. PROBLEM DEFINITION
The objective of this project is to make software for all users who want to manage their accounts at their convenience . This project is mainly for searching details of their accounts and transaction of accounts is also possible. Our software consists of two modules. First administrator manages the overall system. Using Online banking software the administrator can search accounts using account number and username, delete accounts, approve transactions. Secondly the user can edit personal details, view details, made transactions. Manually handling all these data may result in consistency and stability in the data stored here.

3. SOFTWARE REQUIREMENT SPECIFICATION

3.1Introduction
3.1.1. Purpose of this Document This SRS describes the function and the performance allocated to our product. It provides a reference for the validation of the final product. SRS provides an overview of the product including functional and non functional requirements, abbreviations used, product and functions etc. 3.1.2. Scope of the Development Project The project is meant to develop a software system that is very useful to all users who want to manage their accounts. Using this software we can access all details of account and transaction can also be done very easily. It also provides the users to view details of their accounts, list of transactions and also to edit their details etc. One of the best features of this software is that user can view the details of their accounts very easily. 3.2.3. Overview of Document This document provides a description of the requirements of the product. Section 2 of the Software Requirement Specification gives the detailed descriptions of the product including the data requirements. Section 3 provides specific functional requirements of the different components of the product and the performance criteria.

3.2 General Description

3.2.1. User Characteristics

The user may be an administrator, user\clients. The user will manage accounts, transfer accounts, view account information etc. The administrator manages the overall system. Also administrator controls the all transaction made by the users. 3.2.2. Product Perspective This software on been installed can be implemented on any Tier system that is, it can act both as
a)

Web Application System Client-Server System

b)

This facility enables it to be useful in any environment of work. 3.2.3. Overview of Data Requirement There are two users are there in this project. Administrator can search accounts both savings and current accounts, delete accounts, add new clients, create accounts. Also all the administrator can search their suitable accounts by using account number. Secondly user\clients can view account details, transfer accounts to any beneficiary by using their account number but there is limit for transaction. 3.2.4. General Constraints, Assumptions, Dependencies and Guidelines The System on which the process is going on must have Microsoft SQL server installed. It should also have Micro media Dreamweaver 8 installed in order to run PHP, HTML and JAVA script program in that. The language used must be English. The operating system should be one that supports server setting on the server and client setting on the client side. The software has to completely bug-free as the slightest error may cause the total mishap in business.

3.3

Special Requirements

3.3.1. External Interface Requirements

Input from the user will be via keyboard input and mouse point and click. The user will navigate through the software by clicking on icons and links. The icons will give appropriate response to the given input 3.3.2. Detailed Description of Functional Requirements This section provides a requirement overview of the product. The project will be on PHP + HTML and the Xampp is installed so that it acts as a local host for the system. 3.3.3. Functional Requirement
Different login for administrator, users\clients. Users can edit details.

Users can assign password to protect their data.

Administrator can approve transactions. Administrator can create accounts.

Administrator can add clients.

3.3.4. User Input Validation If the user leaves a mandatory field blank, he will prompted to enter valid data in that particular field. 3.3.5. Performance Requirements The performance of our product is at its best if stored locally, as the response time will be much faster. If the product accessed via Internet, the performance is not limited by the connection. .

4. SYSTEM REQUIEMENTS

4.1. Hardware Requirement

CPU Operation Speed RAM HDD Monitor Keyboard Mouse Intel Pentium IV or equivalent 1.60 GHz 256 MB 40 GB 15 105 keys 3 button scroll mouse

4.2. Software Requirement

FOR SERVER Operating System Server Developing Language Database Web Browser WINDOW XP Apache PHP + HTML MySQL Opera

FOR CLIENT Operating System Web Browser Windows XP Opera

5. SYSTEM STUDY
5.1. Existing System
The existing system is a static one. It can generate only static contents. The present existing systems are very tedious and time consuming process as it requires a large number of paperworks and need large documentations 5.1.1 Drawbacks of Existing System The existing system is not user friendly. If any defects/errors occurred its difficult to manage. Drawbacks of the existing system can be summarized as below: It is a static one Updating of data is done only by static methods. Difficult to access the database Updating process is more tedious and more time consuming.

5.2. Proposed System

The proposed system is very much efficient than the existing system in many aspects. In proposed system we make use of on-line processing which is not at all time consuming. Our proposed system is a dynamic one using PHP + HTML. Using this system administrator and user can do their functions very easily.

5.2.1. Advantages of Existing System The contents are dynamic. Can access database It is very user friendly. The updating process is easy. Less time consuming. 5.2.2. Benefits of the Proposed System
1. Online Banking Software System helps in maintain a totally secured database of all

the details of all user information. This information can be available at your figure tips.
2. Online Banking Software System helps in improved retrieving details by providing

the users with better data access, faster data retrieval, higher quality data and more versatility in data display.
3. Online Banking Software System helps in improving efficiency, of getting details of

accounts by avoiding duplications, repetitions, delays, missing records and confusions.

4. Online Banking Software System helps to force orderliness and standardization of the

details of all users

5.3. Feasibility Analysis

A feasibility study is a test of system proposal according to its workability, impact on the organization, ability to meet user needs and effective use of resources. The objective of feasibility study is not to solve the problem, but to acquire a sense of its scope. During the study, the problem definition is crystallized and aspects of problem to be included in the system are determined, consequently costs and benefits are estimated with greater detail at this stage. The result of feasibility study is a system formal proposal. This is simply a form of documenting or detailing the nature and scope of proposed solution. The proposed summarizes what is known and what going to be done. The key considerations involved in the feasibility analysis are technical, economic, and operational.

Technical Feasibility Technical feasibility is the most important of all types of feasibility analysis. Technical feasibility deals with hardware as well as software requirements. An idea from the outline design to system requirements in terms of inputs outputs, files and procedures is drawn and type of hardware, software, and the methods required for running the systems are analyzed. Keeping in mind of the above considerations, the resource availability at his company was observed. It was found that the company has the sufficient resources to develop the current project; hence the system is technically feasible. Economic Feasibility Economic analysis is the most frequently used method for evaluating the effectiveness of the software, more commonly known as the cost/benefit analysis. The procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If the benefits outweigh cost, the decision is made to design and implement the system; otherwise further alternatives have to be made. Here it is seen that no new hardware or software is needed for the development of the system. Hence the project is economically feasible for development in this system. Schedule Feasibility Schedule feasibility is concerned with the completion of the project development within the fixed time span. It is an important factor as it can affect other factors like machine availability, tools, cost development and delay in the development of other systems. Besides these, this project is assigned to the student as an academic exercise to be completed within a fixed period of time. Operational Feasibility The purpose of the operational feasibility study is to determine whether the new system would be used if it is developed and implemented? Will there be resistance from

users that will undermine the possible application benefits? From the outputs of the meeting that was held with the system users, it was found that all of them support the development of new system. The positive response from them encouraged in building such a system.

6. SYSTEM DESIGN
6.1. Different Modules Administrator Module

Add new clients and also create new accounts. Approve transactions made by clients. Search accounts by using both account number and username. Remove unwanted accounts

Add new clients and also create new accounts Administrator can add new clients and also create new accounts. Approve transactions made by clients Administrator can approve transactions of all accounts to any beneficiary by giving their account number but there is limit in amount that transfer. Search accounts. Administrator can search accounts by giving account number of that particular account and also by giving username. Remove unwanted accounts Administrator can remove accounts. User module

View the details of the accounts. Edit personal details Made transactions. View the details of the accounts

User can view account information by logging into the software by using the username and password. Edit personal details User can edit their personal details and also there is also an option for changing password. Made transactions User can transfer accounts to any beneficiaries whose has accounts in any banks by using their account number.

6.2. DATA FLOW DIAGRAM (DFD

The DFD is also known as the bubble chart. It is a simple graphical formalism that can be used to represent a system in terms of data to the system, various processing carried out on these data and the output data generated by the system. The main reason why this DFD technique is so popular because of that DFD is very simple to understand and use. A DFD model uses very limited number of primitives symbols to represent the functions performed by a system and the data flow among these systems. Starting with a set of high level functions that a system performance of DFD model in hierarchically it represent various sub function. The Data Flow Diagramming technique also follows a simple set of intuitive concepts and rules. Data flow diagram (DFD) is used to show how data flows through the system and the processes that transfer the input data into output. Data flow diagrams are a way of

expressing system requirements in a graphical manner. DFD represents one of the most ingenious tools used for structured analysis. In the normal convention, logical DFD can be completed using only four notations. Function Symbols:

A function is represented using a circle. This symbol is called a processes or a bubble. Bubbles are annotated with the names of corresponding functions.

External Entity Symbols:

An external such as a user, project manager etc. is represented by a square. The external entities are essentially those physical entities external to the application system, which interact with the system by inputting data to the system or by consuming the data produced by the system. In addition to the human users the external entity symbol can be used to represent external hardware and software such as application software. Data Flow Symbol:

A directed arc or an arrow is used as a Data Flow Symbol. This represents the data flow occurring between two processes or between an external entity and a process; in direction of the Data Flow Arrow. Data flow symbol are annotated with corresponding data names. Data Store Symbol:

A data store represents a logical file; it is represented using two parallel lines. A logical file can represent either data store symbol, which can represent either data structure or physical file on a disk. Each data store is connected to a process means of data flow symbol. The direction of the data flow arrow shows whether data is being read from or written into a data store. An arrow in or out of a data store implicitly represents the entire area of the data store and hence arrows connecting to a data store need not be annotated with the names of the corresponding data items. Output Symbol: The output symbol is used when a hard copy is produced and the user of the copies cannot be clearly specified or there are several users of the output. The DFD at the simplest level is referred to as the CONTEXT ANALYSIS DIAGRAM. These are expanded by level, each explaining its process in detail. Processes are numbered for easy identification and are normally labeled in block letters. Each data flow is labeled for easy understanding.

6.2.1. Context Diagram

The context diagram is the most abstract data flow representation of a system. It represents the entire system as a single bubble. This bubble is labeled according to the main function of the system. The various external entities are also represented as incoming and outgoing arrows. These data flow arrows should be annotated with the corresponding data names. The name context diagram is well justified because it represents the context in the which the system is to exist, i.e. the external entity who would interact with the system and the specific data items they would be supplying to the system and the data items they would be receiving from the system. The context diagram is also called the Level 0 DFD. To develop the context diagram o the system, we have to analyze the SRS document to identify the difference types of users who would be using the system and the kinds of data they would be inputting to the system and the data they would be receiving from the system. Here, the term users of the system also include the external system, which supply data to receive data from the system. How to develop the DFD of a system ?

The SRS document is examined to determine: Different high-level functions that the system needs to perform. Data input to every high-level function. Data output from every high-level function. Interactions among the identified high level functions. These aspects of high-level functions are then represented in a diagrammatic form. This forms top level DFD.

The high level functions described in the SRS document are examined. If there between three to seven high level requirements, then each of the high-level functions can be represented in the form of a bubble. If there are more than seven bubbles, then some of them have to be combined. If there are less than three bubbles, then some of the need to be split. Each high-level function is documented into constituent sub-functions through the following set of activities: Different sub functions of the high-level functions are identified. Data input to each of these sub functions are identified. Data output from each of the sub functions are identified. Interactions among these sub functions are identified.

LEVEL 0

Administr ator OLB Banks Database

Client

Admini strator

User name passw & ord

r Use e & nam word s pas

LOGIN

LOGIN

Client

ADMINISTRATOR
Account details
Remove account

Approve transaction

Search account

Add account

Transaction details

Add individual

Client details

7. DATA BASE DESIGN

The primary need at the outset of design is the database. An important requirement in the design is the representation of data in different tables. The data items for tables are classified based on their characteristics. The relationships between the data items are identified in each table. Certain data that are unlikely to be changed and those that would facilitate the operation of the other processes are kept in the master tables. Similarly data that form a part of transaction are put into the transaction table. Thus, looking at the different data available, tables are carefully done aiming to achieve its main objective such as:

Table Used in the System

Account transfer Login Client details

 Pending list

ACCOUNT TRANSFER Column Name Account no. Client id User name Account type Branch Balance Date Data type Int(11) Int(11) Varchar(50) Varchar(50) Varchar(50) double Date Allow Nulls No No No No No No No

LOGIN Column Name User id Username Password Datatype Int(11) Varchar(50) Varchar(50) Allow Nulls No No No

Client details

Column Name

Data type

Allow Nulls

Acc no. Username First name Middle name Surname Sex House name Street Town Pin State Country Phone Email Password Passrems Secans Accc type Branch Balance Date Pending List Column Name

Int(11) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Int(50) Varchar(50) Varchar(50) Int(50) Varchar(50) Datatype Int(11) Varchar(50) Varchar(50) Varchar(50) Varchar(50) Int(11)

No No No no No No No No No No No no No No Allow Nulls No No No no No No

Data type

Allow Nulls

Tran id Acc no. Acctype Ben Benacno. Benbranch Amount Date

Int(11) Varchar(50) Int(11) Vachar(50) Int(20) Vachar(50) Int(11) Date

No No No No No No No No

8. INPUT/OUTPUT DESIGN
8.1 Input Design Input Design is a process of converting user-oriented input to computer based format. It also includes determining the record media. Method of input speeds of capture and entry into the system. Input design consist of developing specification and procedures for data procedure for data preparations, those necessary steps into put transaction data into usable form of processing, data entry and activity of putting the data into computer for processing. Five objectives guiding the design are input focus on controlling the amount of input required, avoiding delay, controlling error and keeping the steps simple. The following are the details the system analyst decides while designing: The data to input The details of how data should be arranged or coded The item and transaction needed validation to detect errors.

All input processes have been designed with at most care to avoid entry of any kind of invalid data into the system. The input screens have been validated effectively in order to give the most accurate input details. Points to be noted while designing the input screens are Dont overcrowd the input screen Keep the same style among the screens Ask for confirmation of critical data Validate data as soon as possible on input.

8.2. Output Design Designing computer output should proceed in an organized, well throughout manner; the right output element is designed so that people will find the system whether or executed. When we design an output we must identify the specific output that is needed to meet the system. The usefulness of the new system is evaluated on the basis of their input. Once the output requirements are determined, the system designer can decide what to include in the system and how to structure it so that the require output can be produced. For the proposed software, it is necessary that the output reports be compatible in format with the existing reports. The output must be concerned to the overall performance and the systems working, as it should. It consists of developing specifications and procedures for data preparation, those steps necessary to put the inputs and the desired output, i.e. maximum user friendly. Proper messages and appropriate directions can control errors committed by users.

The output design is the key to the success of any system. Output is the key between the user and the sensor. The output must be concerned to the systems working, as it should. Output design consists of displaying specifications and procedures as data presentation. User never left with the confusion as to what is happening without appropriate error and acknowledges message being received.

9 SYSTEM IMPLEMENTATION
Familiarization with tools used in implementation process
9.1 PHP PHP is a scripting language originally designed for producing dynamic web pages. It has evolved to include a command line interface capability and can be used in standalone graphical applications. While PHP was originally created by Rasmus Lerdorf in 1995, the implementation of PHP is now produced by The PHP Group and serves as the de facto standard for PHP as there is no formal specification. PHP is free software released under the PHP License. In 2008, PHP 5 became the only stable version under development. Late static binding has been missing from PHP and will be added in version 5.3. PHP 6 is under development alongside PHP 5. Major changes include the removal of register_globals, magic quotes, and safe mode. The reason for

the removals was because register_globals had given way to security holes, and magic quotes had an unpredictable nature, and was best avoided. Instead, to escape characters, Magic quotes may be substituted with the addlashes() function, or more appropriately an escape mechanism specific to the database vendor itself likemysql_real_escape_string() for MySQL. PHP is a general-purpose scripting language that is especially suited for web development. PHP generally runs on a web server, taking PHP code as its input and creating web pages as output. It can also be used for command-line scripting and clientside GUI applications. PHP can be deployed on most web servers, many operating systems and platforms, and can be used with many relational database management systems. It is available free of charge, and the PHP group provides the complete source code for users to build, customize and extend for their own use. PHP primarily acts as a filter, taking input from a file or stream containing text and/or PHP instructions and outputs another stream of data; most commonly the output will be HTML. It can automatically detect the language of the user. The LAMP architecture has become popular in the web industry as a way of deploying web applications. PHP is commonly used as the P in this bundle alongside Linux, Apache and MySQL. As of April 2007, over 20 million Internet domains were hosted on servers with PHP installed, and PHP was recorded as the most popular Apache module. Significant websites are written in PHP including the user-facing portion of Facebook, Wikipedia (Media Wiki), Yahoo!, My Yearbook, Digg, Wordpress and Tagged. In addition to server-side scripting, PHP can be used to create stand-alone, compiled applications and libraries, it can be used for shell scripting, and the PHP binaries can be called from the command line.

PHP only parses code within its delimiters. Anything outside its delimiters is sent directly to the output and is not parsed by PHP. The most common delimiters are <? php and ?>, which are open and close delimiters respectively. Basic object-oriented programming functionality was added in PHP 3. Object handling was completely rewritten for PHP 5, expanding the feature set and enhancing performance. In previous versions of PHP, objects were handled like primitive types. The drawback of this method was that the whole object was copied when a variable was assigned or passed as a parameter to method. In the new approach, objects are referenced by handle, and not by value. PHP 5 introduced private and protected member variables and methods, along with abstract classes and final classes as well as abstract methods and final methods. It also introduced a standard way of declaring constructors and destructors, similar to that of other object-oriented languages such C++, and standard exception handling model. PHP includes free and open sources libraries with the core build. PHP is a fundamentally Internet- aware system with modules built in for accessing FTP servers, many database servers, embedded SQL libraries such as embedded PostgreSQL, MySQL and SQLite, LDAP servers, and others. 9.2 MySQL What is a database? Quite simply, it is an organized collection of data. A database management system (DBMS) such as Access, FileMaker Pro, Oracle or SQL Server provides you with the software tools you need to organize that data flexible manner. It includes facilities to add, modify or delete data from the database, ask questions (or queries) about the data stored in the database and produce reports summarizing selected contents. MySQL is multithreaded, multi-user SQL database management system (DBMS). The basic program runs as a server providing multi-user access to a number of databases. Originally financed in similar fashion to the JBoss model, MySQL was owned and sponsored by a single for-profit firm, the Swedish company MySQLAB now a subsidiary of Sun Microsystems, which holds the copyright

to most of the codebase. The projects source code is available under terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL is a database. The data in MySQL is stored in the database objects called tables. A table is a collection of related data entries and it consists of columns and rows. Databases are useful when storing information categorically. 9.3 Macromedia Dreamweaver 8 Is a professional HTML editor for designing, coding, and developing websites, web pages, and web applications? Whether you enjoy the control hand-coding HTML or prefer to work in a visual editing environment, Dreamweaver provides you with helpful to enhance your web creation experience. The visual editing feature in Dreamweaver let you quickly create pages without writing a line of code. You can view all your site elements or assets and drag them from an easy-to-use panel directly into a document. You can streamline your development workflow by creating and editing images in Macromedia Fireworks or another graphics application, then importing them directly into Dreamweaver, or by adding Macromedia Flash objects. Client-side role of forms: Forms support the client side of the client-server relationship. When a visitor enter information into a form displayed in web browser (the client) and clicks the submit button, the information is sent to the server where a serverside script or application processes it. Common server-side technologies used for processing form data include Macromedia ColdFusion, Microsoft Active Server Pages (ASP), and PHP. The server responds by sending requested information back to the user (or client), or performing some action based on the forms contents. 9.4 Apache Web server

Often referred to as simply Apache, a public- domain open source Web server developed by a loosely knit group of programmers. The first of Apache, based on the NCSA httpd Web server, was developed in 1995. Core development of Apache Web server is performed by a group of about 20 volunteer programmers, called the Apache Group. However, because the source code is freely available, anyone can adapt the server for specific needs, and there is a public library of Apache add-ons. In many respects, development of Apache is similar to development of the Linux operating system. The original version of Apache was written for UNIX, but there are now versions that run under OS/2, Windows and other platforms. The name is a tribute to the Native American Apache Indian tribe, a tribe well known for its endurance and skill in warfare. A common misunderstanding is that it was called Apache because it was developed from existing NCSA code plus various patches, hence the name a patchy server, or Apache server.

Apache consistently rates as the worlds most popular Web server according to analyst surveys. Apache has attracted so much interest because it is full-featured, reliable, and free. Originally developed for UNIXTM operating systems, Apache has been updated to run on Windows, OS/2, and other platforms. One aspect of Apache that some site administrators find confusing, especially those unfamiliar with UNIX-style software, is its configuration scheme. Instead of using a point-and-click graphic user interface (GUI) or Windows Registry keys as most other modern software packages, Apache generally relies on simple text files for its configuration settings.

10. Source Code

<?php ob_start(); ?> <!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=iso-8859-1" /> <title>ONLINE BANKING</title> </head>

<body> <?php $a=$_POST["username"]; $b=$_POST["password"];

$con = mysql_connect("localhost","root",""); if (!$con) {

print "not connected"; }

else { mysql_select_db("onlinbanking", $con); $sql="select * from adminlogin where username='$a' and password='$b'"; $rs = mysql_query($sql,$con);

$num=mysql_num_rows($rs); if($num!= 0) { //$msg="<p> Congratulations, you're authorized!</p> "; session_start(); $arr = mysql_fetch_array($rs); $_SESSION['username'] = $arr['userid']; header("Location: acccrt.php"); } else { header("Location: adminlogin.php?message=Wrong username or password try again!"); } }

?> </body> </html>

<?php $con = mysql_connect("localhost","root",""); if (!$con) { die('Could not connect: ' . mysql_error()); echo "unable to connect"; } mysql_select_db("online banking", $con);

$myid = $_SESSION['username']; $sql = "select * from clientdetails where accno = '$myid'"; $rs = mysql_query($sql,$con); $arr = mysql_fetch_array($rs); mysql_close($con); ?>

<div align="left"> <input name="add" type="submit" id="add" value="ADD" /> </div>

<div align="left"> <input name="delete" type="submit" id="delete" value="DELETE" /> </div>

<div align="left"> <input name="modify" type="submit" id="modify" value="MODIFY" /> </div>

screen shots