banking system repoet

RAA Bank 2012

UNIVERSITY OF MYSORE

B.C.A University of Mysore Online Banking System

RAA Bank 2012

ABSTRACT

This 'Online Banking' 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. E-banking 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 software has been developed using the most powerful and secure backend MS SQL Server 2008 and the most widely accepted web oriented as well as application oriented .Net Platform 2010 which is being deployed using MS Windows Server 2008.


RAA Bank 2012

INTRODUCTION

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.> Erroneous records may lead to misleading information, which is more likely in manual system.> 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.


RAA Bank 2012

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

Proposed System

In order to overcome the drawbacks in the existing system database is created which is:

> Integrated> Accessibility> Reliable> Consistent> Flexible> Secure

The present database

> Helps in speedy information retrieval

> Extract information from tables using menus

> Offers options of the online updating and in main ting up to date information.


RAA Bank 2012

The proposed system is

> Menu driven and user friendly

> It assists in quick deletion of errors by issuing appropriate error message.> Validity of input data is automatically checked and error will be immediately signaled> Efficient utilization of resources.

Feasibility Study

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

Forms based authentication is used here, the data will be more secured.

Economic Feasibility

The application can be used on existing computers itself so that user doesn’t require

higher configuration. Since the user already has all software’s required the application can

be used on existing software, preventing the user to buy additional software which is

economically feasible to the user.


RAA Bank 2012

Operational Feasibility

Here the proposed system is checked for its operational feasibility. The ease of using

proposed system contributes to the benefits of the system. The new system will be user

friendlier.


RAA Bank 2012

ANALYSIS

Introduction:

System analysis is the process of gathering and interpreting facts, diagnosing and using

this information to recommended improvements to the system. Analysis specifies what

the system should do. The bottom line in analysis is to know what is happening in the

system.

The purpose of analysis is to state and understand the problem and application domain,

using fact-finding techniques so that a current design can be constructed. A good analysis

captures the essential features of the problem without introducing the implementation

details.

The key features of analysis are:

Statement of the problem.

Current System.

Proposed System.

Software Requirement Specification.

System Requirement Specification.


RAA Bank 2012

Software Requirement Specification:

Online Banking system application is a web-based application. After studying the

limitations of the existing system and considering the feedbacks obtained from

customers, bankers and administration the requirement of the proposed system were

encompassed as follows.

Requirement Specification

These specific requirements for the application as identified by the various users.

Performance

For web-based responses on the Internet, the application will return the requested

web-page to the user within few seconds.

External Interface Requirements

User interfaces

The application will have a web interface available to all customers and bankers. Each

type of user will have an interface specific to that user’s needs. The application will use

the e-mail system when necessary to notify users.


RAA Bank 2012

Security:

Security is a very wide-reaching term. During every step of the application-building

process, you must, without a doubt, be aware of how mischievous end users might

attempt to bypass your lockout measures. You must take steps to ensure that no one can

take over the application or gain access to its resources. Whether it involves working with

basic server controls or accessing databases, you should be thinking through the level of

security you want to employ to protect yourself.

Authentication and Authorization

Authentication is the process that determines the identity of a user. After a user has been

authenticated, a developer can determine if the identified user has authorization to

proceed. It is impossible to give an entity authorization if no authentication process has

been applied.

Authorization is the process of determining whether an authenticated user is permitted

access to any part of an application, access to specific points of an application, or access

only to specified datasets that the application provides. Authenticating and authorizing

users and groups enable you to customize a site based on user types or preferences.

Applying Authentication Measures


RAA Bank 2012

ASP.NET provides many different types of authentication measures to use within your

applications, including basic authentication, digest authentication, forms authentication,

Passport, and Integrated Windows authentication. You also can develop your own

authentication methods. You should never authorize access to resources you mean to be

secure if you haven’t applied an authentication process to the requests for the resources.

The different authentication modes are established through settings that can be applied

to the application’s web.config file or in conjunction with the application server’s Internet

Information Services (IIS) instance.

ASP.NET is configured through a series of .config files on the application server. These are

XML-based files that enable you to easily change how ASP.NET behaves. This is an ideal

way to work with the configuration settings you require. ASP.NET configuration files are

applied in a hierarchal manner. The .NET Framework provides a server-level configuration

file called the machine.config file, which can be found at

C:\Windows\Microsoft.NET\Framework\v2.0xxxxx\CONFIG.

The folder contains machine.config and machine.config.comments files. These files

provide ASP.NET application settings at a server-level, meaning that the settings are

applied to each and every ASP.NET application that resides on the particular server.

Aweb.config file is another XML-based configuration file that resides in the root of the

Web application. The settings applied in the web.config file override the same settings

applied in the higher-level machine.config file.

You can even nest the web.config files so that the main application web.config file is

located in the root directory of your application, but additional web.config files reside in


RAA Bank 2012

some of the application’s subdirectories. The web.config files contained in any of the

subdirectories supersede the root directory’s web.config file. Therefore, any settings

applied through a subdirectory’s web.config file change whatever was set in the

application’s main web.config file.

Forms-Based Authentication

Forms-based authentication is a popular mode of authenticating users to access an entire

application or specific resources within an application. Using it enables you to put the

login form directly in the application so that the end user simply enters his username and

password into an HTML form contained within the browser itself. One negative aspect of

forms-based authentication is that the usernames and passwords are sent as clear text

unless you are using SSL. It’s easy and relatively straightforward to implement forms-

based authentication in your Web application.

If the requestor is not authenticated, what is defined in the <authentication> element is

put into action. The value of the mode attribute is set to Forms to employ forms-based

authentication for your Web application.

The next attribute specified is loginUrl, which points to the page that contains the

application’s login form. In this example, Login.aspx is specified as a value. If the end user

trying to access the application is not authenticated, his request is redirected to

Login.aspx so that the user can be authenticated and authorized to proceed. After valid

credentials have been provided, the user is returned to the location in the application

where he originally made the request. The final attribute used here is path. It simply


RAA Bank 2012

specifies the location in which to save the cookie used to persist the authorized user’s

access token. In most cases, you want to leave the value as /.

Functional Requirements:

The functional requirements for online banking system are described below according to

the take holders.

Customer

Customer can apply online to create account with the web site.

Customer can view transactions details.

Customer can carry out money transfer.

Apply for loan.

View loan status.

Can view balance.

Banker / Admin

Banker can view loan application.

Banker can approve loan requests.

Banker can reject loan requests.

Banker can delete loan requests.

Banker can view account details.


RAA Bank 2012

System Requirement Specification

Infrastructure requirements for any project are to be judged before it even starts and

that was something that has been taken care of properly.

Hardware Requirements

1) Operating System: Windows XP.

2) Minimum Hardware Requirements:

a) 1.0 MHz Intel Pentium-4 or AMD Athalon processor.

b) 256 MB RAM.

c) 20 GB of free space on the Hard Disk.

Software Requirements

1) .NET Framework 4.0 (Visual Studio 2010).

2) Internet-enabled Web Application using ASP.NET

3) Developed using programming language: c#.

4) Database: SQL Server 2008.

5) ADO.Net for database middleware.

6) Style Sheets: CSS.

7) IIS should be installed on Windows Xp.


RAA Bank 2012

Structure Chart


RAA Bank 2012

The various sub modules in the above modules are

Customer

This is an important module in the project. This module is mainly for assisting the second

category of users (customer). This module provides various functionalities to customers

like

Create account- This sub module provides customer can apply online to create

account with the web site.

Transaction details - Customer can view transactions details.

Money transfer - Customer can carry out money transfer to any account in

seconds.

Loan – customer can apply loan within its limit and he can view loan status.

Administration/Banker

This is an important module in the project this module includes sub modules like.

Accounts - Banker can view every one account details.

Loan - Banker can approve loan or reject loan request.

Close A/c - Banker can close any one A/c.


RAA Bank 2012

Data flow diagrams for the proposed system

A data flow diagram shows the flow of data through a system. The system may be an

organization, a manual procedure, a software system, a mechanical system, a hardware

system, or any combination of these. A DFD shows the movement of data through the

different transformations or processes in the system. A DFD is very useful in

understanding a system and can be effectively used for partitioning during analysis.

The DFD consists of data flows, processes, sources, destinations and stores. These are all

described through the use of the conventional symbols like the arrow for the data flow,

rectangle for source and sink, open rectangle for the data store and the circle for the

process. It also describes how the data gets stored, retrieved, updated during its flow.

The DFD support the top-down approach to system analysis where by we begin by

developing a general understanding of the system and gradually explore the components

in greater detail. As details are gathered information about control can also be included,

although upper level general diagrams are drawn without showing specific control issues

to ensure focuses on data and processes.


RAA Bank 2012

System Hierarchy


RAA Bank 2012

The various sub modules of the above hierarchy are as follows.

Customer Hierarchy:


RAA Bank 2012

Admin Hierarchy


RAA Bank 2012

Context Level diagram:


RAA Bank 2012

DFD for the Proposed System:


RAA Bank 2012

DFD for ADMIN:


RAA Bank 2012

DFD for Customer Module:


RAA Bank 2012

ER-Diagram:


RAA Bank 2012

DESIGN

System design

Design is a multi step process in which representations of data structure, program

structure and interface characteristics and procedural detail are synthesized from

information requirements the objective is to provide a systematic approach for the

deviation of the design- the blueprint from which software is constructed. In the software

engineering, design focuses on following three major areas of concern:

1) Data design

2) Architectural design

3) Procedural design

Data Design

Data Design describes how the data of the program is going to be stored. The data model

for the application is as follows.

Data Model

A data model describes how data is represented and accessed.

A data model theory, i.e. a formal description of how data may be structured.

A data model instance, i.e. a data model theory to create a practical data model

instance for some particular application.


RAA Bank 2012

Architectural Design

Design Considerations

To support wide variety of platforms, functionally was developed in Java. This is a web-

based application. All the clients or users will be accessing the application over Internet

with http protocol. Custom components will be developed in Java and Struts. The system

will be implemented on an n-tier architecture model, with the ability to combine or spilt

out application components onto different host servers as needed.

Authentication and Authorization

Authentication and Authorization framework

User authentication is to be done in SQL Server only. All the registered users’ details will

be stored in the database along with their status. Once the user enters the name and

password, depending upon the credentials supplied user will be authenticated.

User Name Syntax

User names are alphanumeric character.


RAA Bank 2012

Password Syntax

Password should be of minimum 7 character length and it should include one

alphanumeric character.

Procedural Design

Customer: create new A/c, login, transactions and transfer, apply loan and view loan

status.

Baker: A/c details, Loan details, Close A/c.

IMPLEMENTATION

THE GOALS OF ASP.NET 4.0

ASP.NET 4.0 is a major release of the product and is an integral part of the .NET

Framework 4.0. This release of the Framework was code-named Whidbey internally at

Microsoft. ASP.NET 4.0 heralds a new wave of development that should eliminate any of

the remaining barriers to adopting this new way of coding Web applications.

When the ASP.NET team started working on ASP.NET 4.0, it had specific goals to achieve.

These goals focused around developer productivity, administration and management, as

well as performance and scalability. These goals are achieved with this milestone product

release.


RAA Bank 2012

Performance and Scalability

One of the goals for ASP.NET 4.0 set by the Microsoft team was to provide the world’s

fastest Web application server.

One of the most exciting performance enhancements is the new caching capability aimed

at exploiting Microsoft’s SQL Server.

ASP.NET 4.0 now includes a feature called SQL cache invalidation. Before ASP.NET 4.0, it

was possible to cache the results that came from SQL Server and to update the cache

based on a time interval—for example, every 15 seconds or so. This meant that the end

user might see stale data if the result set changed sometime during that 15-second

period.

In some cases, this time interval result set is unacceptable. In an ideal situation, the result

set stored in the cache is destroyed if any underlying change occurs in the source from

which the result set is retrieved—in this case, SQL Server. With ASP.NET 4.0, you can

make this happen with the use of SQL cache invalidation. This means that when the result

set from SQL Server changes, the output cache is triggered to change, and the end user

always sees the latest result set. The data presented is never stale.

Additional New Features of ASP.NET 4.0

You just learned some of the main goals of the ASP.NET team that built ASP.NET 4.0. To

achieve these goals, the team built a mountain of new features into ASP.NET. A few of

them are described in the following sections. B.C.A University of Mysore Online Banking System

RAA Bank 2012

New Developer Infrastructures

An exciting advancement in ASP.NET 4.0 is that new infrastructures are in place for you to

use in your applications. The ASP.NET team selected some of the most common

programming operations performed with ASP.NET 2.0 to be built directly into ASP.NET.

This saves you considerable time and coding.

Membership and Role Management

In earlier versions, if you were developing a portal that required users to log in to the

application to gain privileged access, invariably you had to create it yourself. It can be

tricky to create applications with areas that are accessible only to select individuals.

Personalization

One advanced feature that portals love to offer their membership base is the capability to

personalize their offerings so that end users can make the site look and function however

they want. The capability to personalize an application and store the personalization

settings is now completely built into the ASP.NET framework.

Because personalization usually revolves around a user and possibly a role that this user

participates in, the personalization architecture can be closely tied to the membership

and role infrastructures. B.C.A University of Mysore Online Banking System

RAA Bank 2012

LITERATURE SURVEY

.NET FRAMEWORK

OVERVIEW OF .NET FRAMEWORK:

The .NET Framework is a new computing platform that

simplifies application development in the highly distributed

environment of the Internet. The .Net Framework is a collection of

functions for many programming tasks. The framework contains all

the functionalities of the operating system and makes it available to

an application. These functions are also aimed at bridging the gap in

the interoperability between applications. The .Net framework

integrates various programming languages and services. It improves

code reuse, code specialization, resource management, multi

language development, security, deployment and administration.

Note that all .net languages like visual basic.net, C# and Visual C++


RAA Bank 2012

use extensible markup language (XML) for describing and

exchanging data between applications.

The .NET Framework is designed to fulfill the following objectives

To provide a consistent object-oriented programming

environment whether object code is stored and executed locally,

executed locally but Internet-distributed, or executed remotely.

To provide a code- execution environment that minimizes

software deployment and versioning conflicts.

To provide a code-execution environment that guarantees

safe execution of code, including code created by an unknown or

semi-trusted third party.

To provide a code-execution environment that eliminates

the performance problems of scripted or interpreted environments.

To make the developer experience consistent across

widely varying types of applications, such as Window-based

applications and Web-based applications.

To build all communication on industry standards to

ensure that code based on .NET Framework can integrate with any

other code.


RAA Bank 2012

The .NET Framework has two main components: The Common

Language Runtime and The .NET Framework Class Library. The

Common Language Runtime is the foundation of the .NET

Framework. The .NET Framework can be hosted by unmanaged

components that load the Common Language Runtime into their

processes and initiate the execution of managed code, thereby

creating a software environment that can exploit both managed and

unmanaged features. The .NET Framework not only provides several

runtime hosts, but also supports the development of third-party

runtime hosts.

COMPONENT OF .NET FRAMEWORK:

The components of the .Net framework consist of a collection of services and classes.

These components exist as a layer between .Net applications and the underlying

operating system. Below fig shows the components of the .Net Framework.

The Components of the .NET Framework.

The .Net Framework consists of:


ASP .Net Windows Forms

Console Application Services

.Net Base Classes

Common Language Runtime

RAA Bank 2012

ASP .NET

Windows Forms

Console Application Services

.Net framework base classes

Common language runtime

The first three components pertain to the presentation layer of an

application. The .net framework base classes consist of a class library that

works with any .NET language such as VB.NET and C#. This class l ibrary can

be used across many languages. The same set of classes can be used to

perform a certain task in VB.NET as well as Visual C++. This class l ibrary

comprises of namespaces, which are contained within assemblies.

COMMON LANGUAGE RUNTIME:

The Common Language Runtime manages: memory, thread execution,

code execution, code safety verification, compilation, and other system

services. These features are intrinsic to the managed code that runs on the

Common Language Runtime.

With regards to security, managed components are awarded varying

degrees of trust, depending on a number of factors that include their origin.

This means that a managed component might or might not be able to


RAA Bank 2012

perform file-access operations, registry-access operations, or other sensitive

functions, even if it is being used in the same active application.

The Runtime enforces code access security. The security features of the

runtime thus enable legitimate Internet-deployed software to be

exceptionally feature rich.

The Runtime also enforces code robustness by implementing a strict type

and code verification infrastructure called the common type system (CTS).

The CTS ensures that all managed code is self-describing. The various

Microsoft and third-party language compilers generate managed code that

conforms to the CTS.

The Runtime also accelerates developer productivity. Language compilers

that target the .NET Framework make the features of the .NET Framework

available to existing code written in that language, greatly easing the

migration process for existing applications.

The runtime is designed to enhance performance. Although the Common

Language Runtime provides many standard runtime services, managed code

is never interpreted.

A feature called just-in-time (JIT) compiling enables all managed code to

run in the native machine language of the system on which it is executing.


RAA Bank 2012

Meanwhile, the memory manager removes the possibilities of fragmented

memory and increases memory locality-of-reference to further increase

performance.

The Runtime can be hosted by high-performance, server-side applications,

such as Microsoft, SQL Server and Internet Information Services (IIS).

The CLR or the runtime provides the following functionality: exception handling,

security, debugging and versioning support to any of languages that targets it. The CLR is

designed so that it can execute programs written in any language. The languages that the

CLR executes are Visual Basic .net, C# and C++ with managed extensions. The compiler of

any of these languages compiles the code to avail the services offered by the CLR.

The garbage collection feature is an inbuilt feature of the .Net. This

feature automatically manages the allocation and de-allocation of memory.

The CLR allocates memory for each and every object created. If the CLR does

not find enough memory space, it invokes the garbage collection process,

which identifies objects that are no longer used by the application and

terminates them.


RAA Bank 2012

Compiling and Execution Steps in .NET Framework:

The process of compiling and executing managed code is given below:

Step 1:When a program written in any language compatible with CLR is

compiled, the compiler translates the program into MSIL (Microsoft

Intermediate Language).

Step 2:Any compiler, compatible with .Net framework while compiling

programs, produces metadata about the program during the process of

compilation. Metadata contains details l ike, description of the program

including classes and interfaces, dependencies, and the versions of the

programs used in the program.

Step 3:The Intermediate Language and the metadata are linked in an assembly.

Step 4:The compiler creates the .EXE or .DLL file. When the .EXE or .DLL file is executed,

the code and all the other relevant information from the base class library are sent to the

class loader.

The class Loader loads the EXE/DLL code and the class libraries into the memory. The just-

in-time (JIT) compiler translates this code into managed native code. During the process


RAA Bank 2012

of compilation, the JIT compiler compiles only the code that is required for executes the

code. While executing the code, a security check is performed to ensure that the code has

the appropriate permissions for accessing the available resources

The following diagram depicts the process of compilation and execution of

a .NET application

Fig Process of compilation and execution of .NET application

.NET FRAMEWORK CLASS LIBRARY:

The .NET Framework class library is a collection of reusable types that

tightly integrate with the Common Language Runtime. The class library is


EXE/DLL Class Libraries

Class Loader

JIT compiler

Execution

RAA Bank 2012

object oriented, providing types from which your own managed code can

derive functionality.

The .NET Framework types enable you to accomplish a range of common

programming tasks, including tasks such as string management, data

collection, database connectivity, and file access.

.NET FEATURES:

The .NET Framework provides a number of basic features that make it

easier to deploy a variety of applications. These features include:

No-impact applications.

This feature provides application isolation and eliminates DLL

conflicts. By default, components do not affect other applications.

Private components by default.

By default, components are deployed to the application directory

and are visible only to the containing application.

Controlled code sharing.

Code sharing requires you to explicitly make code available for

sharing rather than being the default behavior.

Side-by-Side versioning.

Multiple versions of a component or application can coexist, you

can choose which versions to use, and the common language

runtime enforces versioning policy.

XCOPY deployment and replication.


RAA Bank 2012

Self-described and self-contained components and applications can

be deployed without registry entries or dependencies.

On-the-fly updates.

Administrators can use hosts, such as ASP.NET, to update program

DLLs, even on remote computers.

Enterprise deployment.

This feature provides easy software distribution, including using Active

Directory.

Downloading and caching.

Incremental downloads keep downloads smaller, and components

can be isolated for use only by the application for zero-impact

deployment.

Partially trusted code.

Identity is based on the code rater than the user, the administrator

sets policy, and no certificate dialog boxes appear.

MASTER PAGES

Visual inheritance is a great new enhancement to your Web pages provided by new

additions to ASP.NET 2.0. In effect, you can create a single template page that can be used

as a foundation for any number of ASP.NET content pages in your application. These

templates, called master pages, increase your productivity by making your applications

easier to build and easier to manage after they are built. Visual Studio 2005 includes full


RAA Bank 2012

designer support for master pages, making the developer experience richer than ever

before.

The Basics of Master Pages

Master pages are an easy way to provide a template that can be used by any number of

ASP.NET pages in your application. In working with master pages, you create a master file

that is the template referenced by a subpage or content page. Master pages use a .master

file extension, whereas content pages use the .aspx file extension you’re used to; but

content pages are declared as such within the file’s Page directive.

Working with Master Pages

Put anything you want to share within the template in the .master file. This can include

the header, navigation, and footer sections used across the Web application. The content

page then contains all the page content except for the master page’s elements. At

runtime, the ASP.NET engine combines these elements into a single page for the end

user. Figure 8-2 shows a diagram of how this process works.

One of the nice things about working with master pages is that you can visually see the

template in the IDE when you are creating the content pages. Because you can see the

entire page while you are working on it, it is much easier to develop content pages that

use a template. While you are working on the content page, all the templated items are

shaded gray and are not editable. The only items that are alterable are clearly shown in


RAA Bank 2012

the template. These workable areas, called content areas, originally are defined in the

master page itself. Within the master page, you specify the areas of the page that the

content pages can use. You can have more than one content area in your master page if

you want.

With the release of ASP.NET 4.0, master pages are possible because the .NET Framework

2.0 now supports partial classes. This is the capability to take two classes and merge them

into a single class at runtime.

Using this new capability, the ASP.NET engine takes two page classes and brings them

together into a single page class at runtime..

Master pages are added to your projects in the same way as regular .aspx pages—choose

the Master Page option when you want.

ASP. NET CONTROLS

ASP.NET controls provide the dynamic and interactive portions of the user interface web

application. The controls render the content that the user of the web sites actually see

and interact with it.

ASP.NET controls co-exist peacefully with HTML content. Typically static areas of web

pages are created with normal HTML content and dynamic and interactive portions are

created with ASP.NET controls.

Web controls used in the project:


RAA Bank 2012

Web controls are more rationalized version of the standard HTML tags. Web

controls do not directly correspond to standard HTML tags, so we can’t create a web page

by simple sticking the run at=”server” attribute at the end of the standard HTML tag. The

web controls do not look like standard HTML tag. When we add web controls to page we

should always explicitly close the tag. There are more web controls than there are HTML

controls. Several of the web controls do not correspond to existing HTML tags at all.

The web controls can be divided into five different groups:-

Basic web controls

Validation web controls

Data web controls

Rich web controls

The first group consists of the web control correspond to the existing HTML tag. The web

control in this group includes the Textbox. Dropdown list and List box controls. The web

control is as fallows.

Button

Image button

Link button

Checkbox

Checked list box

Dropdown list

Label


RAA Bank 2012

List box

Radio button

Textbox

The second group of web controls contains controls used for form validation. The controls

in this group do not correspond to any existing HTML tag.

The following list contains all the validation web controls:

Compare Validator.

Custom Validator.

Range Validator.

Regular Expression Validator.

Required Field Validator.

Validation Summary.

The third group of controls displays data. The following is a list of the Data

Related Web Controls:

Data Grid

Data List

SiteMap Data Provider

A whole new series of data providers in the form of DataSource controls have been added

to ASP.NET 2.0. One of these new DataSource controls now at your disposal, which you


RAA Bank 2012

looked at earlier in the chapter, is the SiteMapDataSource control. This new DataSource

control was developed to work with site maps and the controls that can bind to them.

Some controls don’t need a SiteMapDataSource control in order to bind to the

application’s site map (which is typically stored in the Web.sitemap file). Earlier in the

chapter, you saw this in action when using the SiteMapPath control. This control was able

to work with the Web.sitemap file directly—without the need for this new data provider.

Certain navigation controls, however, such as the TreeView control and the DropDownList

control, require an intermediary SiteMapDataSource control to retrieve the site

navigation information.

Validation Server Controls

Validation server controls are a series of controls that enable you to work with the

information your end users input into the form elements of the applications you build.

These controls work to ensure the validity of the data being placed in the for

SQL SERVER 2008

SQL Server is Microsoft’s main Relational database Management System

(RDBMS). The word SQL denotes that SQL is language used to access the data

present into the SQL Server database or SQL is a standard language for the

development and implementation of relational databases. The word Server

denotes that this database can support multiple and concurrent users, large

database sizes, and scalable. SQL Server has another language component

called Transact SQL that is used to create stored procedures and triggers.


RAA Bank 2012

Transaction SQL supports many data manipulation functions and flow-control

statements.

SQL Server 2008 is a client/server relational database management system

that runs on windows 2000 professional, server and advanced server,

Windows NT, windows 9x/millennium, or windows CE. SQL Server is included

as the Microsoft BackOffice Suite. SQL Server bests suites in the client/Server

environment. Microsoft’s SQL Server is a client/Server database engine. SQL

Server is the server part of the equation.

Client/Server can be defined as an application that is spit up into at least

two parts; one part runs on the server, and the other part runs on the client

computers, or workstation. The server side of the application provides

security, fault tolerance, performance, concurrency, and reliable backups.

The client side provides the user interface and may contain reports, forms,

and queries.

In non-client server based database systems the work is not being

shared between the server and the workstation machines. Suppose a

database is of about 10MB in the network server. When a client opens the

Database and runs a query, all 10MB is downloaded the client and the query

is processed at the client computer.

In contrast, when a query is run on a Client/Server system, the server

searches for the database and then sends back to the client only those rows


RAA Bank 2012

that match the search conditions. This saves the bandwidth on the network

and it often faster than workstations do all the work.

STRUCTURED QUERY LANGUAGE:

During the 1970’s IBM invented a computer language for database queried

called SEQUEL (Structured English Query Language). Overtime, this language

has been expanded so that it is not just a language for queries but can also

be used to build databases and manage security of the database engine.

Currently, there are various versions of SQL in use. Microsoft SQL Server

uses a version called T-SQL (Transact SQL).

T- SQL is divided into two categories of commands:

Database schema commands, also known as Data Definition Language

(DDL) are use to define the database, tables, and other objects that are

used for managing the structure if the database.

Database Management commands, also known as Data-Manipulation

Language (DML), are used much like SQL commands to manipulate, add to

or delete in the database.


RAA Bank 2012

FEATURES OF SQL SERVER 2008

Internet Integration

The SQL Server 2005 database engine includes integrated XML support. It

also has the scalability, availability, and security features required to

operate as the data storage component of the largest Web sites. The SQL

Server 2005 programming model is integrated with the windows DNA

architecture for developing Web applications, and SQL Server 2000 supports

features such as English Query and the Microsoft Search Service to

incorporate user-friendly queries and powerful search capabilities in web

application.

Scalability and Availability

The same database engine can be used across platforms ranging from laptop

computers running Microsoft windows 98 through large, multiprocessor

servers running Microsoft windows 2005 Data Center Edition. SQL Server

2005 Enterprise Edition supports features such as federated servers, indexed

views, and large memory support that allow it to scale to the performance

levels required by the largest Web sites.


RAA Bank 2012

Enterprise-Level Database Features

The SQL Server 2008 relational database engine supports the features

required to support demanding data processing environments. The database

engine protects data integrity while minimizing the overhead of managing

thousands of users concurrently modifying the database. SQL Server 2008

distributed queries allow you to reference data from multiple sources as if it

were a part of a SQL Server 2008 database, while at the same time, the

distributed transaction support protects the integrity of any updates of the

distributed data. Replication allow you to also maintain multiple copies of

data, while ensuring that the separate copies remain synchronized, you can

replicate a set of data to multiple, mobile, disconnected users, have them

work autonomously, and then merge their modifications back to the

publisher.

Ease of installation, deployment, and use

SQL Server 2008 includes a set of administrative and development tools that

improve upon the process of installing, deploying, managing, and using SQL

Server across several sites. SQL Server 2008 also supports a standards-based

programming model integrated with the windows DNA, making the use of


RAA Bank 2012

SQL Server databases and data warehouses a seamless part of building

powerful and scalable systems. These features allow you to rapidly deliver

SQL Server applications that customers can implement with a minimum of

installation and administrative overhead.

Data warehousing

SQL Server 2008 includes tools for extracting and analyzing summary data

for online analytical processing. SQL Server also includes tools for visually

designing databases and analyzing data using English-based questions.

SQL Server Tools

SQL Server Service Manager

This tool enables us to start and stop SQL Server. To start SQL Server, select Start –

Programs – Microsoft SQL Server –Service Manager, which opens a window where we

start and stop SQL Server.

Enterprise Manger

The enterprise Manager is a visual tool that enables us to view and edit all the objects of

SQL server. There are several objects in SQL Server. Some of the objects we use

commonly are:

a. Database

b. Data Transformation Services


RAA Bank 2012

c. Management

d. Replication

e. Security

f. Support Services

g. Meta Data Services

We use the Enterprise Manager to access these objects and work with them. Each of the

objects plays an important role in an application. However, some of the objects are for

advanced users and some objects are necessary for all applications.

We can create new databases, edit tables, and create stored procedures using

Enterprise Manager.

Databases

The databases object is represented in the Enterprise Manager as a folder. When we click

on the databases folder we are presented with all the databases already created. When

we click on each database we are presented with different objects for this database.

Some of these objects are explained below:

1. Diagrams

A diagram is a picture of the database’s structure. We can change the structure of the

database from within this window. This shows how the various tables relate to each

other. We can add new relationships, set their properties, add constraints for the various

fields, enforce referential integrity, and so on.


RAA Bank 2012

2. Tables

A table is a set of data elements (values) that is organized using a model of rows

and columns. The columns are identified by name, and the rows are identified by the

values appearing in a particular column subset. Table is another term for relations;

although there is the difference in that a table is usually a multi-set of rows whereas a

relation is a set and does not allow duplicates.

3. Views

A view is a virtual or logical table composed of the result set of a query. Unlike ordinary

tables (base tables) in a relational database, a view is not part of the physical schema. SQL

Server’s views are generated from SQL statements, and the data generated from a

standard view is not uniquely stored in the database.

4. Stored Procedures

Stored procedures are written in T- SQL and are executed on the database server. Stored

procedures are groups of SQL statements submitted for execution as a single executable

unit. In the stored procedures folder, we see the list of stored procedures attached to the

database and their definitions. We can create new ones as well as edit and debug existing

stored procedures.


RAA Bank 2012

The Query Analyzer

The Query Analyzer is the option where we can execute SQL statements, batches,

and stored procedures against a database. To start the Query Analyzer, select Start-

programs- Microsoft SQL Server- Query Analyzer.

STORED PROCEDURES

A stored procedure is a routine written in T- SQL by using the DML, which acts on rows of

a table in a database. SQL does not support IF statements and functions which manipulate

strings, formatting functions, whereas T- SQL supports all of them.

Stored procedures are stored in SQL Server databases. We can use stored

procedures to build business rules into the database. After stored

procedures have been stored to the database, users and applications can call

them as if they were another SQL statement or a built-in T- SQL function.

ADVANTAGES OF STORED PROCEDURES:

1. Security:

Stored procedures can help enforce data security.


RAA Bank 2012

E.g. you can grant users access to a procedure that can query a table, but not grant

them access to the table itself.

2. Performance:

It improves database performance in the following ways:

Amount of information sent over a network is less.

No compilation step is required to execute the code.

i. As stored procedure is present in the shared pool of SGA retrieval from disk is

not required.

3. Memory Allocation:

Reduction in memory as stored procedures have shared memory capabilities so only one

copy of procedure needs to be loaded for execution by multiple users.

4. Productivity:

Increased development productivity, by writing a single stored procedure we

can avoid redundant coding and increase productivity

5. Integrity:

Improves integrity, a stored procedure needs to be tested only once to guarantee that it

returns an accurate result. Hence coding errors can be reduced.


RAA Bank 2012

ADO.NET

A large number of computer applications—both desktop and web applications—are data-

driven. These applications are largely concerned with retrieving, displaying, and

modifying data. Retrieving and processing data seems like a fairly straightforward task,

but over the past decade the way applications use data has changed repeatedly.

Developers have moved from simple client applications that use local databases to

distributed systems that rely on centralized databases on dedicated servers. At the same

time, data access technologies have evolved. The .NET Framework includes its own data

access technology, ADO.NET. ADO. NET consists of managed classes that allow .NET

applications to connect to data sources (usually relational databases), execute

commands, and manage disconnected data. The small miracle of ADO.NET is that it allows

you to write more or less the same data access code in web applications that you write

for client-server desktop applications, or even single-user applications that connect to a

local database.

THE ADO.NET ARCHITECTURE

ADO.NET uses a multilayered architecture that revolves around a few key concepts, such

as Connection, Command, and Dataset objects. However, the ADO.NET architecture is

quite a bit different from classic ADO.


RAA Bank 2012

One of the key differences between ADO and ADO.NET is how they deal with the

challenge of different data sources. In ADO, programmers always use a generic set, if you

want to retrieve a record from an Oracle database; you use the same Connection class

you would use to tackle the same task with SQL Server. This isn’t the case in ADO.NET,

which uses a data provider model.

ADO.NET Data Providers

A data provider is a set of ADO.NET classes that allows you to access a specific database,

execute SQL commands, and retrieve data. Essentially, a data provider is a bridge

between your application and a data source.

The classes that make up a data provider include the following:

• Connection: You use this object to establish a connection to a data source.

• Command: You use this object to execute SQL commands and stored procedures.

• Data Reader: This object provides fast read-only, forward-only access to the data

retrieved from a query.

• Data Adapter: This object performs two tasks. First, you can use it to fill a Dataset (a

disconnected collection of tables and relationships) with information extracted from a

data source.

Second, you can use it to apply changes to a data source, according to the modifications

you’ve made in a Dataset.


RAA Bank 2012

ADO.NET doesn’t include generic data provider objects. Instead, it includes different data

providers specifically designed for different types of data sources. Each data provider has

a specific implementation of the Connection, Command, DataReader, and DataAdapter

classes that optimized for a specific RBDMS (relational database management system).

For example, if you need to create a connection to a SQL Server database, you’ll use a

connection class named Sql_Connection.

One of the key underlying ideas of the ADO.NET provider model is that it’s extensible. In

other words, developers can create their own providers for proprietary data sources. In

fact, numerous proof-of-concepts examples are available that show how you can easily

create custom ADO.NET providers to wrap non_relational data stores, such as the file

system or a directory service. Some third-party vendors also sell custom providers

for .NET.

The .NET Framework is bundled with a small set of four providers:

• SQL Server provider: Provides optimized access to a SQL Server database (version 7.0

or later).

• OLE DB provider: Provides access to any data source that has an OLE DB driver. This

includes SQL Server databases prior to version 7.0.

• Oracle provider: Provides optimized access to an Oracle database (version 8i or

later).

• ODBC provider: Provides access to any data source that has an ODBC driver.


RAA Bank 2012

Description of the Modules:

Home Page

Screen Description

Users get access to this page via links from any external resources or by clicking on the

home link available on other pages in this site.


RAA Bank 2012

New user can login by clicking on Login link. This is the Home Page.

.

Login Form

SCREEN DESCRIPTION

The admin/customer can gain access thro’ this page by clicking the login link in home

Page. Customer/admin has to enter the customer name and password to enter as a new

user.

Customer/admin name and password should be entered correctly.


RAA Bank 2012

ADMIN HOME

After we login as admin we get the login sub modules that is

1) Loan Details

2) Account Details


RAA Bank 2012

3) Close Account

Where the admin or user can edit, add or change this sub module.

Loan Details

Screen Description

Loan status can be edited, Approve or reject loan by the Admin/Banker.


RAA Bank 2012

Edit Loan Status

Screen Description


RAA Bank 2012

The Loan Status is updated by the Admin

Account Details

Screen Description

When the admin wants to know Account details by click A/c Details.


RAA Bank 2012

When the admin enter to A/c Details he can check all account he can take decision

whether account should be there or closed.

Close Account:

Screen Description


RAA Bank 2012

Admin entered to the Close Account he can Close any one Accounts if the user wants to

close or in the case of insufficient balance.

Home Page When click Create A/c:


RAA Bank 2012

Screen Description:

By clicking Create A/c the new user can create his own Account thro online.

Create New Account:


RAA Bank 2012

Screen Description:

To Create New Account enter all the required fields with correct document and click

on Submit button if user wants to quit the select the Cancel Button.

Account Number Generation:

Screen Description:


RAA Bank 2012

The New customer Account Number has been generated. Customer should save the A/c

Number for next use. In first time he can access directly by clicking “click here to

transaction”.

Login Form:


RAA Bank 2012

Screen Description:

The new Customer can gain this page by clicking on homepage. Customers who

have already registered should be login through login page.

Customer Home Page:


RAA Bank 2012

Screen Description:

The Customer can came back to home page in any stage The Customer can view Balance

and his Details.

Transfer:


RAA Bank 2012

Screen Description:

In this form the A/c numbers shown in dropdown list, the Customer can easily select any

A/c number which the customer intend to transfer money.

Enter Amount:

Screen Description:

Customer can enter amount to transfer receiver A/c.


RAA Bank 2012

Successful amount Transfer:


RAA Bank 2012

Screen Description:

Amount has been successfully transferred to receivers A/c. The amount has been

deducted from senders A/c.

7.8.8.2 Action

Transactions:

Screen Description:


RAA Bank 2012

The customer can view his Transaction details.

Apply Loan:

Screen Description:

The Customers can Apply Loan through online for salaried loan only.


RAA Bank 2012

Customer should enter Gross Salary.

7.8.8.6 Enter Loan Amount:

Screen Description

The available amount of loan has been calculated and displayed


RAA Bank 2012

.

Successful apply

Screen description:


RAA Bank 2012

Loan has been Applied Successfully. The loan request has been sent to Admin for further actions.

Loan status:

Screen Description


RAA Bank 2012

The customer can check applied loan status.


RAA Bank 2012

TESTING

Introduction:

Software testing is the process used to measure the quality of developed computer

software. Testing is a process of technical investigation, performed on behalf of

stakeholders, that is intended to reveal quality-related information about the product

with respect to the context in which it is intended to operate. This includes, but is not

limited to, the process of executing a program or application with the intent of finding

errors. Quality is not an absolute; it is value to some person. With that in mind, testing

can never completely establish the correctness of arbitrary computer software; testing

furnishes a criticism or comparison that compares the state and behavior of the product

against a specification. An important point is that software testing should be distinguished

from the separate discipline of Software Quality Assurance (SQA), which encompasses all

business process areas, not just testing.

Today, software has grown in complexity and size. The software product developed

by a developer is according to the System Requirement Specification.

Therefore, when an organization invests large sums in making a software product, it must

ensure that the software product must be acceptable to the end users or its target

audience. This is where Software Testing comes into play. Software testing is not merely

finding defects or bugs in the software, it is the completely dedicated discipline of

evaluating the quality of the software.


RAA Bank 2012

One definition of testing is "the process of questioning a product in order to evaluate it",

where the "questions" are operations the tester attempts to execute with the product,

and the product answers with its behavior in reaction to the probing of the tester.

7.2 Testing methods

Software testing methods are traditionally divided into black box testing and

white box testing. These two approaches are used to describe the point of

view that a test engineer takes when designing test cases.

7.2.1 Black box testing

Black box testing treats the software as a black-box without any understanding of internal

behavior. It aims to test the functionality according to the requirements.[14] Thus, the

tester inputs data and only sees the output from the test object. This level of testing

usually requires thorough test cases to be provided to the tester who then can simply

verify that for a given input, the output value (or behavior), is the same as the expected

value specified in the test case. Black box testing methods include: equivalence

partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing,

traceability matrix etc.

7.2.2 White box testing

White box testing, however, is when the tester has access to the internal data structures, code, and

algorithms.

Types of white box testing

The following types of white box testing exist:


RAA Bank 2012

Code coverage - creating tests to satisfy some criteria of code coverage. For example, the test

designer can create tests to cause all statements in the program to be executed at least once.

mutation testing methods.

fault injection methods.

static testing

Code completeness evaluation

White box testing methods can also be used to evaluate the completeness of a test suite that was

created with black box testing methods. This allows the software team to examine parts of a

system that are rarely tested and ensures that the most important function points have been tested.

Two common forms of code coverage are:

Function coverage, which reports on functions executed and

Statement coverage, which reports on the number of lines executed to complete the test.

They both return a coverage metric, measured as a percentage.

7.2.3 Grey Box TestingIn recent years the term grey box testing has come into common usage. This involves having

access to internal data structures and algorithms for purposes of designing the test cases, but

testing at the user, or black-box level.

Manipulating input data and formatting output do not qualify as grey-box because the input and

output are clearly outside of the black-box we are calling the software under test. This is

particularly important when conducting integration testing between two modules of code written

by two different developers, where only the interfaces are exposed for test. Grey box testing may

also include reverse engineering to determine, for instance, boundary values.


RAA Bank 2012

7.3 Verification & Validation

Software testing is used in association with verification and validation (V&V). Verification is the

checking of or testing of items, including software, for conformance and consistency with an

associated specification. Software testing is just one kind of verification, which also uses

techniques such as reviews, inspections, and walkthroughs. Validation is the process of checking

what has been specified is what the user actually wanted.

Verification: Have we built the software right? (i.e. does it match the specification).

Validation: Have we built the right software? (i.e. Is this what the customer wants?)

7.4 Levels Of Testing:

7.4.1 Unit Testing tests the minimal software component, or module. Each unit (basic

component) of the software is tested to verify that the detailed design for the unit has been

correctly implemented. In an Object-oriented environment, this is usually at the class level, and

the minimal unit tests include the constructors and destructors.

7.4.2 Integration testing exposes defects in the interfaces and interaction between integrated

components (modules). Progressively larger groups of tested software components corresponding

to elements of the architectural design are integrated and tested until the software works as a

system.

7.4.3 Functional testing tests at any level (class, module, interface, or system) for proper

functionality as defined in the specification.

7.4.4 System testing tests a completely integrated system to verify that it meets its requirements.


RAA Bank 2012

7.4.5 Alpha testing is simulated or actual operational testing by potential users/customers or an

independent test team at the developers' site. Alpha testing is often employed for off-the-shelf

software as a form of internal acceptance testing, before the software goes to beta testing.

7.4.6 Beta testing comes after alpha testing. Versions of the software, known as beta versions,

are released to a limited audience outside of the programming team. The software is released to

groups of people so that further testing can ensure the product has few faults or bugs. Sometimes,

beta versions are made available to the open public to increase the feedback field to a maximal

number of future users.

7.4.7 Acceptance testing can be conducted by the end-user, customer, or client to validate

whether or not to accept the product. Acceptance testing may be performed as part of the hand-off

process between any two phases of development.

8 Conclusion

The main aim of developing software is to provide all information that is required by the customer. User friendliness is a must that is the customer must be able to carry out his work without complicated searching procedures. Other important requirements of software are data security, extensibility and maintainability. All these features are included in this web application.


RAA Bank 2012

The project greatly helped in understanding the various phases in website development and exposure to a new developer platform MS Visual Studio .Net and database MS SQL Server.

Future Enhancements:

USER can deploy this project in a website.

We can give this web site to an institution and to a company.

In institution that is if this web site is used in college, it contains static pages

Which contains detail about college, so that it promotes different activities of

College. Using this website in a company , the employee of different companies that is the HR can search resume based on criteria.

Based on criteria they get a call for an interview through mail

9 Web Bibliography

ASP.NET:

http://asp.net

http://www.w3schools.com

http://Quickstarts.asp.net/quickstartv20/aspnet/


http://Quickstarts.asp.net/quickstartv20/aspnet/

http://www.w3schools.com/

http://asp.net/

RAA Bank 2012

http://aspalliance.com/articles/learnASP.aspx

http://www.aspin.com

c#: http://www.csharp-station.com/tutorial.aspx

http://www.programmersheaven.com/

http://www.csharp-station.com/ SQL SERVER:

http://www.functionx.com/sqlserver/

http://www.quackit.com/sql_server/tutorial/

Book Bibliography

Professional ASP.NET 2.0 [WROX publications]

Professional C# 2005 [WROX publications]

Professional SQL Server 2005 programming[WROX publications]

Pro ASP.NET 2.0 in C# 2005 for developers

By Bryan syverson and Joel murach


http://www.functionx.com/sqlserver/

http://www.programmersheaven.com/

http://www.csharp-station.com/tutorial.aspx

http://aspalliance.com/articles/learnASP.aspx

banking system repoet

Documents

standard html

internal data

existing html

standard html

data model

white box

largest web

stop sql server