ABSTRACT

The project entitled “E-Deal Management System” is developed

on behalf of Elysium Group Of Companies.

A system for generating, in a retail store, a printable discount coupon

image solely in response to a customer's action concerning the purchase of
an item.
The system includes at least one customer checkout terminal, a store
controller, a file for storing the terms of at least one coupon deal .
The triggering product in the customer order, associates it with the coupon
deal, and automatically generates data defining at least one discount
coupon for a product........
 2

ACKNOWLEDGEMENT

First and foremost I concede the surviving presence and the

flourishing refinement of ALMIGHTY GOD for his concealed hand yet
substantial all through the project.

My sincere thanks to Dr.M.Sachithanantham B.E., M.Tech.,

Ph.D., Principal, K.L.N. College of Information Technology, for
providing facilities to successfully carry the project work.

My sincere thanks to Mr.N.Ayyanathan

MCA.,P.G.D.C.A.,P.G.M.M.., (Ph.D.,)
Director of Department of Computer Applications, K.L.N. College of
Information Technology, for his encouragement throughout the project
work.

I sincerely thank Mrs.B.Sarojini MCA, M.Phil(COMP.SC.),(PH.D), for

her valuable guidance and constant encouragement that helped me to
complete the project. I also thank my Guide Ms.M.Seethalakshmi
M.C.A., M.Phil, Lecturer, Department of M.C.A for her constant
encouragement, kind co-operation, valuable suggestions and support
rendered in making my project a success.

I offer my whole hearted thanks to Mr.K.Rajasekar M.C.A External

Guide, AMAIN INFOTECH for her kind cooperation in office development lab
& culminating in the successful completion of project work.

I also thank all the other Staff Members of the department of

Computer Applications who gave me many suggestions from time-time
that made my project work better and well furnished.
 3

I take this beautiful opportunity to thank my Parents and my

Friends for giving me so much confidence and strength to work on our
project.

Saravan
an.S.S.
TABLE OF CONTENTS

CHAPTER NO TITLE PAGE NO

Abstract i
List of Tables viii
List of Figures ix

1 INTRODUCTION 9
1.1. Introduction
1.2. Corporate profile
1.3. Problem Definition
2 SYSTEM ANALYSIS & DESIGN 13
2.1. Problem Analysis
2.2. System requirements
2.3. H/W & S/W Specification
2.4. System Design
2.5. Modular Design
2.5.1. Context Flow Diagrams
2.5.2. Data Flow Diagrams
2.6. Algorithms
2.7. Coding implementation
3 TESTING & IMPLEMENTATION 32
3.1. Testing
 4

3.1.1. Unit Testing

3.1.2. Integration Testing
3.1.3. User Acceptance Testing
3.2. Implementation & Maintenance
3.3. Enhancements & Future work
3.4. Conclusion

4 APPENDICES 39
A Screen Shots
B Overall Table Design
C References
 5

LIST OF TABLES

TABLE NO TABLE NAME PAGE NO

1
2
3
4
5
6
 6

LIST OF FIGURES

FIGURE NO FIGURE NAME PAGE NO

1 usecase diagram 28
2 Context flow diagram 29
3 Sequence Diagram 30
4 Data flow diagram 31

CHAPTER 1

1. INTRODUCTION
 7

The vast majority of computer and communication systems use

passwords in order to identify users. Unfortunately, in ubiquitous alpha-
numeric password schemes, users tend to choose passwords with
predictable characteristics, related to how easy they are to remember. To
overcome the vulnerabilities of textual passwords, a lot of alternative
techniques have been proposed such as visual or graphical login, biometric
systems and fingerprint verification. In this paper we focus on graphical
password techniques

1.1. ORGANIZATION PROFILE

Elysium Group Of Companies

Introduction:

To illuminate the world we started Elysium Technologies to

serve humanity utmost to their satisfaction. Our propensity to

service induce us to expand our horizons as we plunge into eleventh

year and our growth stands as landmarks in the field of excellence.

Elysium knows knowledge is unbound and realizes the margin fades

forever and ever as it moves.

But within its boundaries, the disseminated knowledge

embodies the spirit of enquiry, research and quality. Our search is

incessant, our service is ceaseless and our perseverance untiring.

Distribution of right knowledge, dispersal of wisdom and creation of

individuals of distinction is our pursuit.

 8

Elysium has grown and matured with every successful project

delivered. The challenges and hurdles we have faced over the years

have helped us to streamline and build strong processes. Elysium

has emerged as a strong and stable organization that our clients can

entrust on without any risk. In fact, our client list has grown, and

most importantly we have retained each and every client that we

have served so far. These achievements have given Elysium the

strength to surge ahead into a promising future.

About Us

Elysium group of companies have grown to its current position as the

largest global solutions firm in Asia on the basis of its outstanding service
record, collaborative partnerships, innovative and corporate responsibility.
We are proud of our heritage, which is founded in 1999.

Our mission reflects the Elysium Group's longstanding commitment

to provide excellence to help customers to achieve their business
objectives and by providing innovative ideas, best in solutions and
services. Our vision is to be one of the top 10 global service providers by
the year 2010. Our values: Leading change, Integrity, Respect for the
individual, Excellence, Learning and sharing. Our ability is to deliver high-
quality services and solutions.
 9

Elysium Technologies, leading digitization solutions provider

catering to the needs of enterprises in Tamil Nadu Founded in 1999

by a band of offspring's from some of the leading software

companies in Madurai. Engineers at Elysium Technologies gained

their expertise by executing projects varying from Website roll out to

e-commerce portal development. We have experts in Web

development and design, Multimedia CD presentation for Corporatist.

Vision And Mission

Elysium is a social utility that helps people to excel in their

profession and communicate more efficiently with their friends,

family and coworkers. The company develops technologies that

facilitate the sharing of information through this site.

Mission Statement

"Elysium will actively promote and preserve the highest

standards of quality and ethical values in customer care, education,

training and research and will pursue excellence in all these areas

while consciously meeting the expectations of the people it serves

without prejudice and in all fairness stay socially meaningful in its

propagation of support and strength to humanity at large".

 10

Our mission reflects the Elysium Group's longstanding

commitment to provide excellence to help customers to achieve their

business objectives and by providing innovative ideas, best in

solutions and services. Our vision is to be one of the top 10 global

service providers by the year 2010. Our values: Leading change,

Integrity, Respect for the individual, Excellence, Learning and

sharing. Our ability is to deliver high-quality services and solutions.

1.2. PROBLEM DEFINITION.

we investigated the security of the Pass-Points graphical password scheme

and the suitability of the underlying images, by providing a model that
predicts the
users' click points and their saliency value. From this we predicted the
entropy of a click point in a graphical pass-word.

We tested our model experimentally on two images. We analyzed the

password security of those underlying images by computing the entropy of
a click point, and we compared
the predictions produced by our model with data consisting of roughly 100
actual passwords selected by users
. Inthese (very small) images our model was able to predict 70-80% of the
user click positions (Table 2). The results show that our model can be used
 11

to evaluate the suitability of an underlying image for the PassPoints

system.

Our model could be improved by extending the FoA mapso that, in addition
to centroids of regions, it includes midand end points of edges in the
image, as well as corner points
or tips of pointy regions. Moreover, in image segmentation,texture
information may be included to get better results in natural images. A
more di±cult, but very important
improvement of the model would be to include \high-level" factors of
attraction (i.e., based on image \content").

we only considered individual click points. In order to predict entire

passwords we must consider the correlations between click points in a
graphical password. Finally, for
a better experimental test of our model we would need to collect
thousands of graphical password data for types of images
 12

CHAPTER 2

2. SYSTEM ANALYSIS & DESIGN

2.1 PROBLEM ANALYSIS

EXITSING SYSTEM

1.3.2. PROPOSED SYSEM

In the online shopping, internet marketing and every e-commerce
site is launching new features and offering something new to attract more
and more customers.
The latest talks about online discount coupons. That means one get rebate
in a particular outlet on various products.
High discounts are given on the products to gain more satisfied
customers.
 13

FEASIBILITY STUDY

In the system survey we conduct the feasibility study. The key

considerations involved in the feasibility are:

• Economic feasibility
• Technical feasibility
• Behavioral feasibility
• Operational feasibility

The proposed system must be evaluated from a technical view point first,
and if technical feasibility their impact on the organization must be
assessed. If compatible, behavioral system can be devised. Then they
must be tested for economical feasibility.

TECHNICAL FEASIBILITY

The assessment of technical feasibility must be based on an outline

design of system requirements in terms of input, output, fields, programs,
and procedures. This can be qualified in terms of volumes of data, trends,
frequency of updating, cycles of activity etc, in order to give an
introduction of technical system.

BEHAVIORAL FEASIBILITY

People are inherently resisted to change and computers have been

known to facilitate change. Since the new proposed system is nothing to
do with the ordinary customers and worker resistance to the system is very
 14

much less. On the other hand the user of the system are accessing this
system through Internet and they are computer literate, so resistance from
that side is also very less.

ECONOMICAL FEASIBILITY

Justification of any capital outlay is that it will reduce expenditure or

improve the quality of service or goods, which in turn may be expected to
provide increased profits.
The technique of cost benefit analysis is often used a basis for assessing
economic feasibility

OPERATIONAL FEASIBILITY
Operational feasibility can be determined by visualizing if the
resources that are required to implement or install are already available in
the organization. The fact that the organization basically being involved in
software development clearly states that the personals are in need of no
exposure to computer. Hence the system, its development and
implementation is very much desired. The management also being
convinced about the system, the project can be termed as operationally
feasible.

PROJECT FEASIBILITY STUDY

Our project is feasible in all ways in satisfying the requirements
needed by the clients due to the above reasons.
 15

2.2 SYSTEM REQUIREMENTS

.NET FRAME WORK

The .NET Frame work is many things, but it is worth while listing its
most important aspects. In short the .NET Frame work is :

A Platform designed form the start for writing. Internet-aware and

Internet -enabled applications that embrace and adopt open standards
such as XML, HTTP, and SOAP.

A platform that provides a number of very rich and powerful

application development technologies, such as Windows Forms, used to
build the classic GUI applications, and of course ASP.NET,used to build web
applications.

A Platform with an extensive class library that provides extensive

support for date access (relational and XML), a director services, message
queuing, and much more.

A Platform that has a base class library that contains hundreds of

classes for performing common tasks such as file manipulation, registry
access, security, threading, and searching of text using regular
expressions.
 16

A Platform that doesn’t forget it origins, and has great

interoperability support for existing components that you or third parties
have written , sing COM or standard DLLs.

A Platform with an independent code execution and management

environment called the Common Language Runtime(CLR), which ensures
code is safe to run, and provides an abstract layer on top of the operating
system, meaning that elements of the .NET framework can run on many
operating systems and devices.

ASP.NET

ASP.NET is part of the whole. NET framework, built on the top of the
Common Language Runtime (also known as the CLR) a rich and flexible
architecture, designed not just to cater for the needs of developers today,
but to allow for the long future we have ahead of us. What you might not
realize is that, unlike previous updates of ASP, ASP.NET is very much more
than just an upgrade of existing technology- it is the gateway to a whole
new era of web development.

ASP.NET is a feature at the following web server releases

Microsoft IIS 5.0 on WINDOWS 2000 SERVER

Microsoft IIS 5.1 on WINDOWS XP
 17

ASP.NET has been designed to try and maintain syntax and run-time
compatibility with existing ASP pages where ever possible. The motivation
behind this is to allow ASP Pages to be initially migrated ASP.NET by simply
renaming the file to have an extension of .aspx. For the most part this goal
has been achieved although there are typically some basic code changes
that have to be made, since VBScript is no longer supported, and the VB
language is it has changed.

Some of the key goals of ASP.NET were to

● Reduce the amount of code required to develop web applications.

● Make ASP.NET well factored, allowing customers to add in their own
custom functionality, and extend/replace built-in ASP.NET functionality.
● Make ASP.NET a logical evolution of ASP, where existing ASP investment
and therefore code can be reused with little, if any, change.
● Realize that bugs are a fact of life, as ASP.NET should be as fault
tolerant as possible.

BENEFITS OF ASP.NET

The .NET Frame work includes a new data access technology named
ADO.NET, an evolutionary improvement to ADO. Though the new data
access technology is evolutionary, the classes that make up ADO.NET bear
little resemblance to the ADO objects with which you might be familiar.
Some fairly significant changes must be made to existing ADO applications
to convert them to ADO.NET. The changes don’t have to be made
immediately to existing ADO applications to run under ASP.NET, however.
 18

ADO will function under ASP.NET. However, the work necessary to

convert ADO applications to ADO.NET is worthwhile. For disconnected
applications, ADO.NET should offer performance advantages over ADO
disconnected record sets. ADO requires that transmitting and receiving
components be COM objects.ADO.NET transmits data in a standard XML-
format file so that COM marshaling or data type conversions are not
required.

ASP.NET has several advantages over ASP

The following are some of the benefits of ASP.NET:

● Make code cleaner
● Improve deployment, scalability, and reliability.
● Provide better support for different browsers and devices.
● Enable a new breed of web applications.

C#

C# is a general purpose programming object oriented language

invented around 1999 or 2000 by Anders Hejlsberg at Microsoft. It is very
similar to Java in its syntax with a major difference being that all variable
types are descended from a common ancestor class.

The purpose of C# is to precisely define a series of operations that a

computer can perform to accomplish a task. Most of these operations
 19

involve manipulating numbers and text, but anything that the computer
can physically do can be programmed in C#. Computers have no
intelligence- they have to be told exactly what to do and this is defined by
the programming language you use. Once programmed they can repeat
the steps as many times as you wish at very high speed. Modern PCs are
so fast they can count to a billion in a second or two.

ADO.NET

ADO.NET provides consistent access to data sources such as

Microsoft SQL Server, as well as data sources exposed via OLE DB and
XML. Data-sharing consumer applications can use ADO.NET to connect to
these data sources and retrieve, manipulate, and update data.

ADO.NET cleanly factors data access from data manipulation into

discrete components that can be used separately or in tandem. ADO.NET
includes .NET data providers for connecting to a database, executing
commands, and retrieving results. Those results are either processed
directly or placed in an ADO.NET Dataset object in order to be exposed to
the user in an ad-hoc manner, combined with data from multiple sources,
or remote between tiers. The ADO.NET Dataset object can also be used
independently of a .NET data provider to manage data local to the
application or sourced from XML.
As application development has evolved, new applications have
become loosely coupled based on the Web application model. More and
more of today’s applications use XML to encode data to be passed over
network connections. Web applications use HTTP as the fabric for
communication between tiers and therefore must explicitly handle
maintaining state between requests. This new module is very different
 20

from the connected, tightly coupled style of programming that

characterized the client/server era, where a connection was held open for
the duration of the programs lifetime ad no special handling of state was
required.

In designing tools and technologies to meet the needs of today’s

developer, Microsoft recognized that an entirely new programming model
for data access was needed, one that is built upon the .NET Framework.
Building on the .NET Framework ensured that the data access technology
would be uniform-components would share a common type system, design
patterns and naming conventions.

ADO.NET was designed to meet the needs of this new programming

model: disconnected data architecture, tight integration with XML,
common data representation with the ability to combine data from multiple
and varied data sources, and optimized facilities for interacting with a
database, all native to the .NET Framework.

XML SUPPORT

XML and data access are intimately tied-XML is all about encoding
data, and data access is increasingly becoming all about XML. The .NET
Framework does not just support Web standards-it is built entirely on the
top of them.
 21

2.3.1 Hardare Requirement

: Processor : Pentium IV (Compatible).

RAM : 512 MB.

Hard disk : 80 GB.

2.3.2 Software Requirement

Server : IIS (Internet Information Service) 6.0.
Operating System: Windows 2000 & Above.

Database : SQL Server 2005.

Web technology : ASP.Net v 2.0# .Net

Scripting Tool : HTML

 22

2.4 SYSTEM DESIGN

Modules Description

The project contains following modules:

LIST OF MODULES:

 Administration
 Customer
 Vendor

MODULE DESCRIPTION:

Administration:-
Sub Modules:-

Login
Manage The Customer And Vendor Details
Update The Coupon Details
Send The Offer Details Via Sms/E-Mail
Manage The Payment System
Validate The Coupon Details
 23

Login:-

In login there are two types of login is specified one type of login
is for administrator and another type of login is user login in
admin only admin can login and in the user all the user those
who will have the id can able to login in our portal .

Manage The Customer And Vendor Details:-

In this module the customer and vendor will be managed here if

once customer registered he may not be getting the
authenticated rights only if the admin allow then the customer
is allowed to interact with the system, that means he can get
into the portal in our portal the both vendor as well as the
customer will be having account and their account should be
effectively maintained by the admin.

Update The Coupon Details:-

The coupon should be updated properly and it should be

updated periodically so the coupon displayed here should be
updated and the work should be updated correctly

Send The OfferDetails Via Sms/E-Mail:-

 24

Offers should be properly intimated to the customer in such a

way through his mobile or E-Mail...........

Manage The Payment System:-

Here all(Customer and Vendor) the transaction are managed

by adminstrator..
And It Manage Properly....

Validate The Coupon Details:-

Here Coupons are validated by administrator. Whether coupon
is validate means offers are intimated to that appropriate
customer. Otherwise coupon will be considered as expired one.

Customer

Sub-Modules:-

Registration
Product Choosen

Vendor

Sub-Modules
 25

Registration
Validation
Type of Offers

USECASE DIAGRAM

Query
Database

Authentication

Authenticatio Authenticatio
n by n by
username, graphical
pwd image
 26

Context flow diagram:

User name password Bank

User(admin) Finger print
process
a

verify

Data base
I image check
 27

Data flow diagram

 28

user

Image Separation

Data
Withdraw base Deposit

Transaction

MiniStatement

Report
 29

Sequence Diagram:

Withdraw/
User Image Authendication MiniStmt Deposit

Click choosen
image

ImageDisplay

Click correct
clickpoints Provide password
authendication

Applying for
mini report

Receiving mini
report

Apply to
withdraw/
Depositamount

Recive
Withdraw amount
 30

3.1Testing

TESTING OBJECTIVES

Testing objectives include

• Testing is a process of executing a program with the intent of

finding an error
• A good test case is one that has a high probability of finding an
as yet undiscovered error
• A successful test is one that uncovers an as yet undiscovered
error.

Testing should systematically uncover different classes of errors in a

minimum amount of time and with a minimum amount of effort. A
secondary benefit of testing is that it demonstrates that the software
appears to be working as stated in the specifications. The data collected
through testing can also provide an indication of the software’s reliability
and quality. But, testing cannot show the absence of defect, it can only
show that software defects are present.

TESTING STRATEGIES

The purpose of the testing strategy is to define the overall context for all
entire testing process. A good test strategy is:
 31

● Specific
● Practical
● Justified

The testing Strategy provides the overall guidelines from which all future
testing decisions are made. A well-crafted Testing Strategy allows the rest
of the testing process to be defined more effectively.

The test strategy is formal description of how a software product will

be tested. A test strategy is developed for all levels of testing, as required.
The test team analyses the requirements, writes the test strategy and
review a plan with the project team. The test plan may include test cases,
conditions, and the environment, a list of related tasks, pass/fail criteria
and risk assessment. Inputs for this process:

A description of the required hardware and software components,

including test tools. This information’s comes from the test environment,
including test tool data.
A description of roles and responsibilities of the resources required for
the test and schedule constraints. This information comes from man-hours
and schedules.
Functional and technical requirements of the application. This
information comes form requirements, change request and technical and
functional design documents.
Requirements that the system cannot provide, e.g. system limitations
Output for this process:
An approved and signed off test strategy documents, test plan,
including test cases.
Testing issues requiring resolution. Usually this requires additional
negotiation at the project management level.
 32

3.1.1. UNIT TEST

The first test in the development process is the unit test. The source
code is normally divided into modules, which in turn are divided into
smaller unites called units. These units have specific behavior. The test
done on these units of code is called unit test.

Unit test depends upon the language on which path of the project
performs accurately to the documented specifications and contains clearly
defined inputs and expected results.

3.1.2 INTEGRATION TESTING

Integration testing is the logical extension of Unit Testing. In simpler
form, two units that have already been tested are combined into a
component and the system is tested.
Here, after integrating each module with the system, testing is done.
After Integration, the system is working properly.

3.1.3 USER ACCEPTANCE TESTING

An Acceptance testing is an important testing which is an exercise of
the completed system by a group of end users to determine whether the
system is ready for deployment. Here we can know how well we
understood the requirements of the project. If the requirements are not
understood properly, then there will be more errors in this level of testing.
Here the system is tested and it is accepted by the user.

3.2 IMPLEMENTATION
 33

Implementation means converting a new system design into

effective operation. This involves creating compatible files, training the
operating staff before the system is up and running. The major factor is not
disturbing function organization OBJECTIVE.

• In this phase, the system modifications are installed and

made operational in a production environment.
• The phase is initiated after the system has been tested
and accepted by the user and project manager.
• Activities in this phase include notification of
implementation to end users, execution of the previously
defined training plan, data entry or conversion, and post
implementation review.

NOTIFY USERS OF NEW IMPLEMENTATION

The implementation notice should be sent to all users and

organizations affected by the implementation. Additionally, it is good policy
to make internal organizations not directly affected by the implementation
aware of the schedule so that allowances can be made for a disruption in
the normal activities of that section.

The schedule of the implementation:

• A brief synopsis of the benefits of the system;

• The difference between the old and new system;
 34

• Responsibilities of end user affected by the

implementation during this phase;
• The process to obtain system support, including contact
names and phone numbers.

TRAINING PLAN

It is always a good business practice to provide training before the

end user uses the new system. Because there has been a previously
designed training plan established, complete with the system user manual,
the execution of the plan should be relatively simple.

PERFORM DATA ENTRY CONVERSION

With the implementation of any system, typically there is old data

which is to be included in the new system. This data can be in a manual or
an automated form. Regardless of the format of the data, the task in this
section is two fold, data input and data verification. When replacing a
manual system, hard copy data will need to be entered into the automated
system. Some sort of verification that the data is being entered correctly
should be conducted throughout this process.

This is also the case in data transfer, where data fields in the old
system may have been entered inconsistently and there affect the
integrity of the new database. Verification of the old data becomes
imperative to useful computer system. One of the ways verification of both
system operation and integrity can be accomplished is through parallel
operations.
 35

Parallel operations consist of funning the old process or system and

the new system simultaneously until the new system is certified. In this
way if the new system fails in any way, the operations can proceed on the
old system while the bugs are worked out.

CONDUCT POST IMPLIMENTATION REVIEW

After the system has been fielded a post-implementation review is

conducted to determine the success of the project through its
implementation phase. The purpose of this review is to document
implementation experiences to recommend system enhancements and
provide guidance for feature projects.

MAINTAIN SYSTEM/SOFTWARE

Daily operations of the system/ software may necessitate that

maintenance personnel identify potential medications needed to ensure
that the system continues to operate as intended and produces quality
data.
Daily maintenance activities for the system, takes place to ensure
that any previously undetected errors are fixed. Maintenance personnel
may determine that modifications to the system and database are needed
to resolve errors or performance problems.
Also modifications may be needed to provide new capabilities or to
take advantage of hardware upgrades or new
 36

New capabilities may take the form of routine maintenance or may

constitute enhancements to the system or database as a response to user
requests for new/improves capabilities. Revise previous documentation.
At this phase of the SDLC all security has been completed
An update must be made to the system security plan; an update
and test of the contingency plan should be completed. The project
manager must be sure that security operating procedures are kept
updated accordingly.

3.3 Enhancement & Future Works

A project can be solving some particular problems but at the same time,
project is continuous process to maintain and upgrade in all times. In this
project may enhance the modules and from that modules we can provide
more details about customer and can give more services. In future there
are lot of new technology may come, regarding that technologies we
should upgrade it.

All software products aim at lesser degree of maintenance. This is quite

natural, but enhancements also pour in, in due course of time, which is
unavoidable Better technologies developers aiming for sophistication and
increasing need of customers are all part and parcel of the software.
 37

3.4 Conclusion

In this project we found that there were few significant

differences among several images of everyday scenes. Using
guidance from psychology as well as intuition one may be able
to choose images that are sufficiently good password images
and avoid at least the worst images that interfere with
memorability. However, further work on password images is
needed to determine to what extent images have “hot spots”
that attract many users to choose password points in the same
small areas. If hot spots occur frequently, then they reduce
entropy of the system.
This phenomenon has been shown in face recognition
graphical passwords but the danger may be less in our system
with good choice of images to avoid hot spots. We plan to begin
studying hot spots by collecting a large number of password
points on multiple images.
 38

APPENDICS A

Screen shot

Registration:
39
 40

Login Form:

Admin Login:
41
 42

Deposit:
 43

WithDraw:
 44

Transaction:
 45

Report:
 46

APPENDICES B

Table Design
DatabaseDesign:

1.[dbo].[BankAccount]

Fieldname Datatype
Acc_id Int
userid Int
Acc_name Varchar
Acc_No Varchar
Branch_Id Int
Img_id Int
Createddate Varchar
 47

2.[dbo].[Bank_Details]

Fieldname Datatype
Branch_id Int
Branch_name varchar
Address1 Varchar
Address2userid Varchar
Acc_name Int
Acc_No Int
Pincode Varchar
Phone Varchar
Description Varchar
City_id int
Createddate datetime

3. deposit
Fieldname Datatype

Doposit id int
Acc no varchar
Dept_name varchar
amount numeric
Process id int
date datetime
 48

4. Image date
Fieldname Datatype

Img_id int
image image

5.transaction
Fieldname Datatype

Trans id int
Acc_no varchar
amount numeric

6.users
Fieldname Datatype

User id int
User name nvarchar
email nvarchar
Creation date varchar
First name nvarchar
Last name nvarchar
gender char
Address 1 nvarchar
Address 2 nvarchar
city nvarchar
zip nvarchar
phone nvarchar
state nvarchar
country nvarchar
Img_id int
 49

APPENDICES C

REFERENCES

Books References:

 Asp.Net Data Web Controls - by Scott Mitchell

 Asp.Net - by Stephen Walther

 Asp.Net for Web Designers -by Peter Ladka
 Asp.Net Developer's Jumpstart - by Paul D Sheriff, Ken Getz

 C#: The Complete Reference. By Schildt, Herbert.

 NET and Microsoft Visual C# Step by Step" by Robin A.

Reynolds-Haertle
 Asp.Net Solutions - 23 Case Studies: Best Practices for

Developers - by Rick Leinecker

 Asp.net 2.0 Cookbook -by Geoffrey T Leblond, Michael A

Kittel
 Inside Asp.Net - by Scott Worley

 SQL: The Complete Reference, Second Edition. by James

R Groff & Paul N. Weinberg

 Transact-SQL Language Reference Guide. Published By:

www.DyessConsulting.Com
I.
50