CAPSTONE PROJECT MID-TERM REPORT (6th March - 2012) INTERNET BANKING SYSTEM

Submitted by: Akhilesh Pathania Registration No:-1050070081 B.tech (CSE) Section-K28E3

Under the Guidance of: Mr. Aman Kamboj Discipline of CSE/IT Lovely School of technology and science Lovely Professional University, Phagwara

Page | 1

CERTIFICATE

This is to certify that Akhilesh Pathania(1050070081) has completed capstone project titled Internet banking system under my guidance and supervision. To the best of my knowledge, the present work is the result of their original investigation and study. No part of the work has ever been submitted for any other degree at any University.

The project is fit for submission and the partial fulfillment of the conditions for the award of degree.

Signature Name of the Research Supervisor Designation School Lovely Professional University Phagwara, Punjab. Date:- 06-03-11

Page | 2

DECLARATION

We, Akhilesh Pathania student of B.tech (CSE) under Department of Lovely School of technology and Science of Lovely professional University, Punjab, hereby declare that all the information furnished in this capstone project report is based on my intensive research and is genuine.

This report does not, to the best of my knowledge, contain part of my work which has been submitted for the award of my degree rather of this university or any other university without proper citation.

Date:-06-03-2012 Akhilesh Pathania 1050070081 Sec: K28E3

Page | 3

TABLE OF CONTENTS
S. no 1 2 3 4 Certificate Declaration List of Tables 1. Introduction 1.1 Overview of the system 1.2 Block Diagram of Website as per client and Administrator 5 6 2. Existing system 3. Proposed System 3.1 Aim 3.2 System Objective 3.3 Scope 7 8 4. Project Modules 5. System Analysis 5.1 System under study 5.2 User Identification and goals 9 6. System Design 6.1 Use Case Diagram 9 10 10 10 10 11 12 12 12 13 13 Topic Page No 2 3 4 7 7 8

Page | 4

6.2 Site diagram 6.3 Database Description 6.3.1 Database Table Structure

14 15

6.4 ER Diagram 6.5 Activity Diagram 6.6 Use Cases 10 7. System Development And Implementation 7.1 About visual Studio 2008 7.2 Coding Standards Used 7.3 Form Designs 7.3.1 Client Modules 7.3.2 Administrative Modules 7.4 Testing And Maintenance 7.4.1 Software Testing 7.4.2 Software Maintenance 19

17

25 30 30 35 35 35 36 36 36 37

Page | 5

LIST OF TABLES

S.NO 1. 2. 3. 4. 5. 6. 7.

TOPIC Client database Branch database Complaint database Bill Database Form Database Administrator login Database Test Case Implemented

Page No 15 15 16 16 17 18 18

Page | 6

1. INTRODUCTION:

1.1 OVERVIEW OF THE SYSTEM: This 'Internet Banking System' Project is a model Internet Banking Site. This site enables the customers to perform the basic banking transactions by sitting at their office or at homes through PC or laptop. The customers can access the banks website for viewing their Account details and perform the transactions on account as per their requirements. With Internet Banking, the brick and mortar structure of the traditional banking gets converted into a click and portal model, thereby giving a concept of virtual banking a real shape. Thus today's banking is no longer confined to branches. Ebanking facilitates banking transactions by customers round the clock globally. The primary aim of this software is to provide an improved design methodology, which envisages the future expansion, and modification, which is necessary for a core sector like banking. This necessitates the design to be expandable and modifiable and so a modular approach is used in developing the software. Anybody who is an Account holder in this bank can become a member of online banking. He has to fill a form with his personal details and Account Number.

All transactions are carried out online by transferring from accounts in the same Bank. The software is meant to overcome the drawbacks of the manual system

The System as described will be operated by two categories of users: client and administrator. The system consists of basic components as shown in the fig2 and fig3 below. This Block diagram is made as per working model of the system from user perspective and the administrator point of view respectively.

Page | 7

AS PER CLIENT:

AS PER ADMINISTRATOR:

Page | 8

2. EXISTING SYSTEM The existing system involves the following activities: > The present system consists of networking environment wherein regular activities are automated. > However activities like Demand Draft issues, Pay Order issues are done manually and corresponding registers updated manually. > Further the status of a pay order whether the same has been honored or not cannot be accessed, in case, if required. > Above all in manual system, only the man responsible for DD/Pay issue is aware of the various records to be updated on each transaction. > Readability of the records, which are maintained manually, is also constrained in the present system. > Since record are kept on a paper registers, again is also a problem. > Further retrieving information from such records for a period is tedious, as the storage place restricts, old records will be kept off the disk. > Also report generation of the various areas is done manually using great amount of manpower and time. > The great limitation to the existing system is that the service to the customers is limited to the bank hours only. The online banking facility provides 24 hours service to the customer. > Erroneous records may lead to misleading information, which is more likely in manual system.

Limitations of the existing system > Leads to tedious manual work. > Enormous amount of time consumption for recording all transactions > Error can occur during the manipulation of several records. >' Economic justification is not obvious. > The technique adopted in this system is more complicated. > Lack of technical background towards the system

Page | 9

3. PROPOSED SYSTEM 3.1 AIM Objective of the system is to develop complete and sustainable website for the countrys largest bank that help in dealing with the customers quickly and provide adequate information to the users. 3.2 SYSTEM OBJECTIVE

Online Banking is the most convenient and powerful way to manage customers
account.

Online Banking is Real Time, giving you up-to-the-second details on customers

account.

It can be accessed anytime, from anywhere, giving you complete control over the
customers finances.

There are no queues to stand in, or turns to wait for. With Online Banking the
customers are in control.

System shall provide complete information of clients with the bank, maintaining
their databases, searching for branches of bank as per their location, downloading of different utility forms and complaint registration and enquiry.

3.3 SCOPE

System will support multi-user environment. System will be a fully automated system. System will provide concrete security features like assigning privileges to users of
the system.

System will maintain a secured database for all the users accessing online services.
Page | 10

 System will be capable of keeping track of all the detailed descriptions of the client
and the whole details of services offered by the client organization.

System will handle extremely large volumes of data (i.e. large database support)
which is accessible round the clock.

It will allow searching of the bank branches as per its location. It will allow downloading of the new account opening form and other account
utility forms.

System will also provide a complaint form to lodge complaints about banks services
online as well as the service to enquire about the complaints

It will also provide information about the various services available online.
4. PROJECT MODULES A. CLIENT INTERACTIVE MODULES: 1. ONLINE CLIENT REGISTRATION:

2. NET BANKING BRANCHES ENQUIRY 3. FORMS----DOWNLOADABLE NEW OPENING ACCOUNT FORM 4. ONLINE COMPLAINT REGISTRATION
B. ADMINISTRATOR INTERACTIVE MODULES:

1. UPDATING DATABASE FOR NEW BRANCHES OF BANKS 2. UPLOADING DIFFERENT UTILITY FORMS. 3. UPDATING COMPLAINT STATUS.
C. STATIC WESITE PAGES 1. ABOUT US:

BOARD OF DIRECTORS EVOLUTION OF THE BANK

2. AFFILIATES:

BANKING SUBSIDIARIES FOREIGN SUBSIDARIES

3. SERVICES OFFERED
Page | 11

4. CONTACT US 5. CUSTOMER CARE

5. SYSTEM ANALYSIS: 5.1 SYSTEM UNDER STUDY

Branch Search: This allows the user to obtain information about the branch of the bank on the basis of the location selected by him/her. Complaint Registration and Enquiry: The user can register complaints about the various products and services of the bank. The system also provides the facility to enquire the status of the complaint whether they are pending or whether they have been dealt. Available Form Download: The user can download various utility forms such as new account opening form, internet banking form, complaint form etc. Bill Payment: The user can pay bills (MTNL, BSES etc.) online. For this the user has been provided with a login ID and password with which he can login and use the internet banking facility. Personal Information Updation: The user can login and update his/her information with the bank online. 5.2 USER IDENTIFICATION AND THEIR GOALS There are two users of the system:

a) Client: These users are the account holders with the bank. They can use their login ID

and password to login and use the Internet Banking facility to pay bills (for e.g. BSES, MTNL etc.) and update their personal information online. They can use various facilities provided by the website online such as searching for branches of bank according to the location of their liking, lodge and enquire complaints, gather knowledge on various other online services etc.

b) Administrator: They are responsible for site maintenance. They can login and update

the site by uploading new forms, keep a check on complaints and update the complaint status etc.

6. SYSTEM DESIGN:

6.1 USE CASE DIAGRAM

Page | 12

A use case in software engineering and systems engineering is a description of a systems behavior as it responds to a request that originates from outside of that system. In other words, a use case describes "who" can do "what" with the system in question. The use case technique is used to capture a system's behavioral requirements by detailing scenario-driven threads through the functional requirements.

There are 2 actors: Administrator and Client There are 10 use cases: Login, Branch Search, Form Download, Bill Payment, Update Personal Information, Complaint Register and Enquiry, Complaint Status Update, Add New Branches and Form Upload

ADMINISTRAT OR

Page | 13

6.2 SITE DIAGRAM

ABOUT US AFFILIATE S SERVICES OFFERED FORM DOWNLOA D SEARCH BRANCH ES COMPLAIN T ACCOUNT OPENING FORM

INTERNET BANKING FORM COMLAINT REGISTRATIO N

HOME

COMPLAINT ENQUIRY PERSONAL INFORMATIO N UPDATION BILL PAYMEN T BSES MTNL

LOGIN/ INTERNE T BANKING

CONTACT US

CUSTOMER CARE

Page | 14

6.3 DATABASE DESCRIPTION 6.3.1 DATABASE TABLE STRUCTURE DATABASE NAME: BANK DATABAS E TABLE 1: CUSTOMER DETAILS table name: client Field name acc_no Fname Lname addr1 addr2 Phn Mobl Email cust_type Username Paswrd Bal mail_stat Field type Number Varchar Varchar Varchar Varchar Number Number Varchar Varchar Varchar Varchar Number Varchar Field size 8 20 20 20 20 08 10 40 2 20 20 15 02 05 Description Account Number First Name Last Name Address Line 1 Address Line 2 Resident Phone No. mobile no. E-mail Address Customer type Username Password Balance Mail Status Branch ID Account Opening Date Constraints Primary key Not null Not null Not null Not null Not null A-account holder N- non account holder Not null Not null Not null U- updated status N- non updated status Foreign Key Not null

b_id Number Acc_opn_date Datetime Table 1: Client Database

DATABASE TABLE 2: BRANCH INFORMATION TABLE NAME: BRANCH Field Name Field Type b_id Number b_loc Varchar b_addr1 Varchar b_addr2 b_phn1 b_phn2 b_mgr b_email b_pin b_fax Varchar Number Number Varchar Varchar Number Number Field Size 05 20 40 40 10 10 20 40 06 10 Description Branch ID Branch Location Branch Address Line 1 Branch Address Line 2 Branch Phone no Branch Phone no Branch Manager Branch E-mail Address Branch Pin Code Branch Fax Number Constraints Primary key Not null Not null Not null Not null Not null

Page | 15

DATABASE TABLE 3: COMPLAINT DETAILS TABLE NAME:COMPLAINT Field Name Field Type Field Size compl_id acc_no prod_name nature Brief compl_stat compl_date Name Addr cust_type Number Number Varchar Varchar Varchar Varchar Datetime Varchar Varchar Varchar 20 40 02 10 40 05 08 20 20 40 2 Description Complaint ID Account no Product name Nature of complaint Brief of complaint Status of complaint Complaint Date Name Address Customer Type Phone no. E-mail U / N- updated status / non updated status Not null Constraints Primary key Foreign key Not null Not null

A / N-account holder/non account holder

Phn Number Email Varchar Table 3: Complaint Database

DATABASE TABLE 4: FORM DETAILS TABLE NAME: FORM Field Name f_id f_name date_of_upld f_path Rmrks Field Type Number Varchar Date Varchar Varchar 40 40 Field Size 05 30 Description Form ID Form name Date of Upload Form Path Remarks Constraints Primary key Not null Not null Not null

Table 4: Form Database

Page | 16

DATABASE TABLE 5: BILL DETAILS TABLE NAME:BILL Field Name Field Type bill_no acc_no Amt Bill_due_date Month Mode chq_no Date_of_pay Kno consumer_no Number Number Number Date Varchar Varchar Number Datetime Varchar Number 10 2 08 12 10 15 Field Size 10 08 15 Description Bill no Account no Amount Due date of bill Bill month Mode of bill B- BSES M- MTNL Not null Not null Constraints Primary key Foreign key Not null Not null

Amt_paid Number Table 5: Bill Database

Cheque number Date of Payment Give KNO while paying for Electricity Bill Give consumer no. while paying for Telephone Bill Amount paid Not null

DATABASE TABLE 6: ADMINISTRATOR DETAILS table name: ADMINLOGIN Field name Username Paswrd Field type Varchar Varchar Field size 20 30 Description Username Password Constraints Not null Not Null

Table 6: Admin Login Database 6.4 ER DIAGRAM An Entity-Relationship Model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion.

Page | 17

Diagrams created using this process are called entity-relationship diagrams, or ER diagrams or ERDs for short.

Acc_opn_da te lname fnam e mo bl bal mail_sta t emai l acc_n o

Cust_ty pe

am t billn o consmer_ no

Amt_pai d mode

mnth Bill_du e_date kn o Chq_n o

ph n

usernam e pwd Addr2

BILL

CLIENT

Date_of_pa y
pay s B_id b_lo c

Addr 1

b_addr 2 b_addr 1

Belongs to
b_ph n2 lodges name cust_typ e b_pi n

BRANCH
B_em ail B_mng r

compl_da tee cmpl_i d

b_ph n1 b_fa x

COMPLAINT

compl_st at Prod_na me

emai l ph n

brief addr

natur e

Page | 18 BRANCH

INFORMATION UPDATION

6.5 ACTIVITY CHARTS UML 2 activity diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the detailed logic of a business rule. Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so that it is simple enough that you dont require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of flow charts and data flow diagrams (DFDs) from structured development. 1) SEARCH BRANCHES USER SYSTEM

Click Net Banking Branches

Display page for Searching Branches

Select Location

Submit

Displays Banks branch information on the basis of selected location Close Webpage

Page | 19

2) FORM DOWNLOAD USER SYSTEM

Click Download Forms on the Home page

Displays Forms available for download

Click on the required Form to be downloaded

[Open]/ [Save]

[Cancel]

Display Form Downloaded message

Close Webpage

Page | 20

BRANCH INFORMATION UPDATION

3a). COMPLAINT REGISTRATION USER SYSTEM

Click Complaint on Home Page

Select Complaint Registration

Display Complaint Form

Enter Details Submit [!e-mail] [incomplete form] Display Blank Fields message

Display Invalid Email Address message

Record User Details Display Recording Failure message Close Webpage [ Recording failure] Complaint [else Registration ] Successful

Complaint ID generated and sent as e-mail

Page | 21

3b). COMPLAINT ENQUIRY

USER

SYSTEM

Click Complaint on Home Page Select Complaint Enquiry Display Complaint Enquiry page

Enter Complaint ID Submit [Incorrect ID] Display Incorrect ID message [else]

Display Complaint Status

Close Webpage

Page | 22

4)PERSONAL INFORMATION UPDATE

USER

SYSTEM
[successful] [login failure] Displays Users Home page

Logs In Re-enter Login Details

Click Profile Update link

Display existing record with updateable fields Update Profile Submit Displays updated information and awaits confirmation [User denies consent] [else] Displays No Updation carried out message [users consent] Updates record [Update failure]

Logs Out

Page | 23

5)BILL PAYMENT USER SYSTEM

[successful] [Login failure] Displays Users Home page

Logs in Re-enter Login Details Click Bill Payment link

Displays Bill Payment page Select Bill Type [BSES] [MTNL ] Enter MTNL Bill Details Enter BSES Bill Details Enter Personal Details Submit [incomplete forms] Display Blank Fields message [else]

Display information and awaits confirmation [User denies consent] Displays No Bill Payment done message

[else]

Updates Bill records

6.6Logs Out USE CASES:

Page | 24

6.6.1 Search Bank Branches Use Case for Searching Branches of Bank Primary Actor: Client Pre-Condition: The home page must be displayed. Post-Condition: The client gets information about the branch of the bank at the location specified Main Success Scenario: 1. User clicks the Net Banking Branches option on the home page. 2. System displays the page for searching branches. 3. User selects the location and submits it. 4. System displays the information of the bank on the basis of location entered asuser. 5. User closes the webpage

6.6.2 Form Download Use Case for Downloading Utility Forms Primary Actor: Client Pre-Condition: The home page must be displayed. Post-Condition: The required form is downloaded. Main Success Scenario: 1. 2. 3. 4. 5. User clicks the Download Forms option. System displays the page where various forms can be downloaded. User selects the form to be downloaded. Form is downloaded. User closes the webpage.

Page | 25

Extensions: 3a. User cancels the download: Handle cancel download.

6.6.3 Complaint Registration and Enquiry Use Case for Complaint Enquiry Primary Actor: Client Pre-Condition: The home page must be displayed. Post-Condition: Complaint is lodged and client gets the Complaint ID Main Success Scenario: 1. User selects the complaint form link on the home page. 2. System displays the complaint page. 3. User then selects Complaint Registration link to lodge complaint. 4. System displays the Complaint Registration page. 5. User enters the details in the required fields and submits the form. 6. System records the details. 7. System displays Complaint Registration Successful message

Page | 26

8. System generates a Complaint ID and sends an e-mail to the client. 9. User closes the webpage. Extensions: 5a. Incomplete Form Submission: Handle incomplete form. 5b. Invalid E-mail Address: Handle invalid e-mail address. 6a. Record details failure: Handle failure to update records.

Use Case for Complaint Enquiry Primary Actor: Client Pre-Condition: The home page must be displayed. Post-Condition: The client gets to know the status of his/her complaint. Main Success Scenario: 1. User selects the complaint form link on the home page. 2. 3. 4. 5. 6. 7. Extension: 5a. Incorrect Complaint ID: Handle incorrect Complaint ID. System displays the complaint page. User then selects Complaint Enquiry link to lodge complaint. System displays the Complaint Enquiry page. User enters the Complaint ID. System displays the Complaint Status. User closes the webpage.

6.6.4 Personal Information Updation

Page | 27

Use Case for Complaint Enquiry Primary Actor: Client Pre-Condition: The client must be registered with the website and the login page must be displayed. Post-Condition: The personal information of the client is updated. Main Success Scenario: 1. User logs in with ID and Password. 2. System displays the Users home page. 3. User clicks the Update Profile link. 4. System displays existing records with updatable fields. 5. User updates the profile and submits it. 6. System displays updated information and awaits confirmation. 7. User confirms the updation. 8. System updates the record. 9. User logs out of the website. Extensions: 1a. Incorrect Login Credentials: Handle Login Failure. 7a. User updates the profile and cancels it 1. System displays the original profile and displays the message that the attempted update has been cancelled. 8a. Record details failure: Handle failure to update records. 6.6.5 Bill Payment

Page | 28

Use Case for Bill Payment Primary Actor: Client Pre-Condition: The client must be registered with the website and login page must be displayed. Post-Condition: The bill payment is made. Main Success Scenario: 1. 2. 3. User logs in with ID and Password. System displays the Users home page. User clicks the Bill Payment link.

4. System displays the Bill Payment page. 5. User selects the bill type i.e. either BSES or MTNL. 6. User enters the bill details. 7. User then enters his/her personal details and submits it. 8. System displays the information and awaits user confirmation. 9. System updates the bill records. 10. User logs out of the website. Extensions: 7a. Incomplete Form Submission: Handle incomplete form. 8a. User after entering the bill and personal details, cancels it 1. System displays the users profile and displays the message that the attempted bill payment has been cancelled. 6.6.6 Handle Login Failure Use Case for Handling Login Failure Primary Actor: Client Pre-Condition: The registered user makes an attempt to login into the system. Post-Condition: System displays appropriate message in case of login failure. Main Success Scenario:
Page | 29

1. System displays a message that either login ID or password is incorrect and asks him to login again. 6.6.7 Handle Incomplete Form

Use Case for Handling Incomplete Form Primary Actor: Client Pre-Condition: The user attempts to fill in the required form. Post-Condition: System gives a message asking the user not to leave any field blank. Main Success Scenario: 1. System detects that the user has left a field blank in the submitted form and displays a message asking the user not to leave any field blank. 6.6.8 Handle Invalid E-mail Address Use Case for Handling Invalid E-mail Address Primary Actor: Client Pre-Condition: The user attempts to fill in the required form. Post-Condition: System gives a message asking the user to enter a valid value corresponding to the field. Main Success Scenario: 1. System detects that the email field has an invalid value in the submitted form. 2. System gives a message asking the user to enter a valid value for the same.

6.6.9 Handle Failure to Record Details Use Case for Handling Failure to Record Details Primary Actor: Client Pre-Condition: The user tries to update the details Post-Condition: System gives a message that the recording of details has failed. Main Success Scenario: 1. System fails to record details.
Page | 30

2. System gives a message that the recording of the details has failed and displays the page again.

6.6.10 Handle Cancel Download

Use Case for Handling Cancel Download Primary Actor: Client Pre-Condition: The user tries to download the utility forms Post-Condition: System gives a message that the download has been cancelled. Main Success Scenario: 1. System gives a message that the download has been cancelled an displays form download page. 6.6.11 Handle Incorrect Complaint ID Submission Use Case for Handling Complaint ID Submission Primary Actor: Client Pre-Condition: The user tries to enquire about the registered complaint Post-Condition: System gives a message that the Complaint Id entered is incorrect Main Success Scenario: 1. System gives a message that the Complaint Id entered is incorrect and reloads the page.

SYSTEM IMPLEMENTATION AND DEVELOPMENT 7.1 ABOUT VISUAL STUDIO Microsoft Visual Studio is an Integrated Development Environment (IDE) from Microsoft. It can be used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silverlight. Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level

Page | 31

debugger. Other built-in tools include a forms designer for building GUI applications, web designer, class designer, and database schema designer. It accepts plug-ins that enhance the functionality at almost every levelincluding adding support for source control systems (like Subversion and Visual SourceSafe) to adding new toolsets like editors and visual designers for domain-specific languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer). Visual Studio supports languages by means of language services, which allow the code editor and debugger to support (to varying degrees) nearly any programming language, provided a language-specific service exists. Built-in languages include C/C++ (via Visual C++), VB.NET (via Visual Basic .NET), and C# (via Visual C#). Support for other languages such as F#, M, Python, and Ruby among others is available via language services installed separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Language-specific versions of Visual Studio also exist which provide more limited language services to the user. These individual packages are called Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++. Microsoft provides "Express" editions of its Visual Studio 2008 components Visual Basic, Visual C#, Visual C++, and Visual Web Developer at no cost. Visual Studio 2008 and 2005 Professional Editions, along with language-specific versions (Visual Basic, C+ +, C#, J#) of Visual Studio 2005 are available for free to students as downloads via Microsoft's DreamSpark program. Visual Studio 2010 is currently in Release Candidate and can be downloaded by the general public at no cost. .NET programming languages The .NET Framework provides a set of tools that help to build code that works with the .NET Framework, Microsoft provides a set of languages that are already .NET compatible. BASIC is one of those languages. ASP.NET environment Active Server Pages were released by Microsoft to enable the creation of dynamic pages based on user input and interaction with a Web site. ASP.NET improves upon the original ASP by providing code-behind. With ASP.NET and codebehind, the code and HTML can be separated. ASP.NET Web services are XML-based services that are exposed can be accessed by other Web services and Web service clients.
ASP.NET'

on the Internet that

ASP.NET is more than the next version of Active Server Pages (ASP); it is a unified Web development platform that provides the services necessary for developers to build enterprise-class Web applications. While ASP.NET is largely syntax compatible with
Page | 32

ASP, it also provides a new programming model and infrastructure for more secure, scalable, and stable applications. ASP.NET is a compiled, .NET-based environment; you can author applications in any .NET compatible language, including VisualBasic.NET, BASIC, and JScript.NET. Additionally, the entire .NET Framework is available to any ASP.NET application. Developers can easily access the benefits of these technologies, which include the managedcommon language runtime -environment, type safety, inheritance, and so on. ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors and other programming tools, including Microsoft Visual Studio .NET. Not only does this make Web development easier, but it also provides all the benefits that these tools have to offer, including a GUI that developers can use to drop server controls onto a Web page and fully integrated debugging support. Developers can choose from the following two features when creating an ' ASP.NET application, Web Forms and Web services, or combine these in any way they see fit.

> Web Forms allows you to build powerful forms-based Web pages. When building these pages, you can use ASP.NET server controls to create common Ul elements, and program them for common tasks. These controls allow you to rapidly build a Web Form out of reusable built-in or custom components, simplifying the code of a page. > An XML Web service provides the means to access server functionality remotely. Features: Intuitive C++ based Language Use a language modeled on C++ syntax, immediately familiar to C++ and Java developers, as well as intuitive new language constructs that greatly simplify development tasks Reliable Interoperability Employ code to call native Windows APIs, use pre-built COM components, and leverage existing ActiveX controls to seamlessly integrate existing applications and components.

Page | 33

Modern, Component-Oriented Language Take advantage of inherent support for properties, indexers, delegates, single and multidimensional arrays, advanced inheritance, attributes, versioning, and XML comments.

Powerful Debugging and Testing Tools ASP .NET includes a powerful remote and multi-language debugger, enabling developers to test applications and build reliable multi-tier solutions that span process boundaries and are written in multiple programming languages

. NET Framework Class Library Gain mature and powerful, built-in functionality, including a rich set of collection classes, networking support, multithreading support, string and regular expression classes, and broad support for XML, XML schemas, XML namespaces, XSLT, XPath, and SOAP.

Robust Web Development Environment Create Web-based solutions in C# using the shared Web Forms Designer and XML Designer. Developers can also use IntelliSense features and tag completion or choose the WYSIWYG editor for drag-and-drop authoring to build interactive Web applications.

. NET Framework Microsoft designed VB from the ground up to take advantage of its new .NET Framework. The .NET Framework is made up of four parts, the Common Language Runtime, a set of class libraries, a set of programming languages, and the ASP.NET environment. The .NET Framework was designed with three goals in mind. First, it was intended to make Windows applications much more reliable, while also providing an application with greater degree of security. Second, it was intended to simplify the development of Web applications and services that not only work in the traditional sense, but on mobile devices as well. Lastly, the framework was designed to provide a single set of libraries that would work with multiple languages. The .NET Framework is the infrastructure for the new Microsoft .NET
Page | 34

Platform. And it is a common environment for building, deploying, and running Web applications and Web Services. The .NET Framework contains a common language runtime and common class libraries - like ADO .NET, ASP .'NET and Windows Forms to provide advanced standard services that can be integrated into a variety of computer systems. The .NET Framework provides a feature-rich application environment, simplified development and easy integration between a number of different development languages. The .NET Framework is language neutral. Currently it supports C++, C#, Visual Basic, and Jscript. Microsoft's Visual Studio.NET is a common development environment for the new .NET Framework

HTML HTML stands for Hyper Text Markup Language. It is a simple text formatting language used to create hypertext documents. It is a platform independent language unlike most other programming language. HTML is neutral and can be used on many platform or desktop. It is this feature of HTML that makes it popular as standard on the WWW. This versatile language allows the creation of hypertext links, also known as hyperlinks. These hyperlinks can be used to connect documents on different machine, on the same network or on a different network, or can even point to point of text in the same document. HTML is used for creating documents where the emphasis is on the appearance of the document. It is also used for DTP. The documents created using HTML can have text with different sizes, weights and colors. It can also contain graphics to make the document more effective. 7.2 CODING STANDARDS USED All the command buttons have their name as button followed by the no when they were added to the page.

Page | 35

All the textboxes and data combos have their name as the caption of their respective label. Connection has been set for every page with the databases to retrieve and submitting data.

7.3 FORM DESIGNS 7.3.1 CLIENT MODULES 1. Branch Search: It lets you search the branches of the bank on the basis of location selected. 2. Form Download: It lets you download the various utility forms provided by the bank as selected from the list. 3. Complaint: It lets you to register and enquire about your complaints regarding customers problems. Non account holders can also lodge complaints 4. Login: It lets you to provide the facility of internet banking. 5. Update Personal Information: Once you have logged in, you update your personal information with the bank. 6. Bill Payment: It lets the customer to pay electricity as well as telephone bills. 7.3.2 ADMINISTRATIVE MODULE
1. Login: It allows the administrator to login. 2. Upload Forms: It allows the administrator to upload new utility forms 3. Add New Branches: Once logged in, the administrator can add new branch

information and store it in the database.

4. Update Complaint Status: The administrator can check complaints that are

pending and update them. 7.4 TESTING AND MAINTENANCE 7.4.1 SOFTWARE TESTING: Software Testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate. Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the

Page | 36

risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. Software Testing can also be stated as the process of validating and verifying that a software program/application/product: 1. meets the business and technical requirements that guided its design and development; 2. works as expected; and 3. can be implemented with the same characteristics. Software Testing, depending on the testing method employed can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. Different software development models will focus the test effort at different points in the development process. In a more traditional model, most of the test effort occurs after the requirements have been defined and the coding process has been completed. Newer development models, such as Agile or XP, often employ test driven development and place an increased portion of the testing up front in the development process, in the hands of the developer. 7.4.2 SOFTWARE MAINTENANCE Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes, or to adapt the product to a modified environment (ISO/IEC 14764). This international standard describes the 6 software maintenance processes as: 1. The implementation processes contains software preparation and transition activities, such as the conception and creation of the maintenance plan, the preparation for handling problems identified during development, and the follow-up on product configuration management. 2. The problem and modification analysis process, which is executed once the application has become the responsibility of the maintenance group. The maintenance programmer must analyze each request, confirm it (by reproducing the situation) and check its
Page | 37

validity, investigate it and propose a solution, document the request and the solution proposal, and, finally, obtain all the required authorizations to apply the modifications. 3. The process considering the implementation of the modification itself. 4. The process acceptance of the modification, by checking it with the individual who submitted the request in order to make sure the modification provided a solution.
5. The migration process (platform migration, for example) is exceptional, and is not part

of daily maintenance tasks. 6.Finally, the last maintenance process, also an event which does not occur on a daily basis, is the retirement of a piece of software

BIBLIOGRAPHY BOOKS Steven Holzner, Visual Basic .Net Programming Black Book Dreamtech Press Publication Second Edition. K.K. Agarwal and Yogesh Singh, Software Engineering New Age International Publication Revised Second Edition

INTERNET http://en.wikipedia.org/wiki/Data_flow_diagram http://www.smartdraw.com/resources/tutorials/Introduction-to-UML http://en.wikipedia.org/wiki/Use_case_diagram http://en.wikipedia.org/wiki/Entity-relationship_model http://www.west-wind.com/weblog/posts/76293.aspx

Page | 38