"Banking Management System": Project On

AMTRON COMPUTER CENTRE
KOKRAJHAR
Project on
“Banking Management
System”
Submitted by-
Name :
Course :
Reg no :
BIODATA
1. Name :-
2. Father’s Name :-
3. Mother’s Name :-
4. Permanent Address :-
5. Mobile No. :-
6. E-mail :-
7. Date of Birth :-
8. (i) Nationality :- INDIAN
(ii) Religion :-
9. Caste :-
10. Language known :-
11. Educational Qualification:-
Slno. Examination Board Year of Subjects Division Percentag
Passed /Council Passing e
/University
(%)
1.
H.S.L.C
2. H.S.
3. B.A.
12. Other Certificate :-
CERTIFICATION
I, the Undersigned certify that to the best of knowledge and belief, the resume correctly
describes my qualification and Myself.
Date:Poonam
Place: Kokrajhar, Assam
1
SURAJIT SARKAR
CAREER OBJECTIVE
 To work with an Organization where I can use my skills and knowledge acquired during
my work with different organization at the same time can serve organization at my best.
 Meet Organizational, Professional and Personal goals in terms of Profitability, revenues
and relational ships through continuous efforts and Endeavour.
CAPABILITIES
 Multi-tasking, Prioritizing and Planning Tasks

 Utmost Focus on Solutions
 Ability to adopt different situations
 Ability to respond rather than react
 Team Player, Motivational and Leadership Skills
PERSONAL IMFORMATION
NAME – SURAJIT SARKAR
FATHERS NAME- SRI SUBODH KR. SARKAR
PRESENT ADDRESS – C/O NRIPENDRA KR. DAS
MAA SARADA LANE, SUBHASPALLY WORD NO -3
KOKRAJHAR ,ASSAM -783370
CONTACT NO – 09706474841
EMAIL –[email protected]
MARTIAL STATUS – MARRIED
DATRE OF BIRTH -5TH SEPT 1975
LANGUAGE KNOWN- ENGLISH, HINDI, BENGALI, ASSAMESE
EDUCATIONAL QUALIFICATION
 10TH from D.N.N.H School, Kokrajhar -1990

 10 +2 in Science Stream from Kokrajhar College Under Guwahati University -1990-1992
 BSc with Bio-Chemistry from Guwahati University-1992-1995
PROFESSIONAL QUALIFICATION
3 YEARS GNIIT DIPLOMA FROM NIIT SALTLAKE CENTER 1996-1998
2
PROFESSIONAL EXERCISE
Industry/Period Job Profile and Responsibility

1. NIIT SILCHAR Role 1. Working as a Computer Faculty for
Period – 1998 -2001 teaching UNIX,C , C++ and Visual Basic 6.0
Role 2. Working as a System administrator for

UNIX installation, SYBABSE, WINDOWSNT4.0
and complete maintenance for Unix and NT
Networking Center.
2. Allied Computer and Electronics Role 1. Joining as Sr. System Administrator for
Period 2001- 2005. SILCHAR giving Client Support for Zenith PC with my
Tech. Team which include Client –Server
maintenance, Security System.
3. Sigma Consortium Pvt. Ltd. 2005- Role 1. Joining as Sr. Coordinator under
2010 NIIT@School Program for giving technical
support
Support with my team to different private schools
of Assam. There used to maintain team of 40
faculties with two coordinators.
4. Epitome Computer Center ,Kokrajhar Working a Sr.Faculty to teach C , C++ ,MS SQL
Period 2011 to 2015 SERVER, Java,c#.net,VB.net.ASP.Net. Also
helping students to prepare these above mentioned
Environments.
5. Don Bosco Mission Working a Sr.Faculty to teach C , C++ ,MS SQL

Institute(AMTRON) ,Kokrajhar SERVER, Java,c#.net,VB.net.ASP.Net. Also
Period 2016 to current helping students to prepare these above mentioned
Environments.
Also developed Online Examination System for

center which purely based on C#.net and MSSQL
2008 as Back hand. Apart from Current working
on Online Admission System. Make a Web sites
on behalf of center www.dbmikoj.in under PHP
and MYSQL environment.
CERTIFICATION
I , the Undersigned certify that to the best of knowledge and belief, the resume correctly describes
my qualification and Myself.
Date : 14th Dec 2017. SurajitSarkar
Place: Kokrajhar,Assam
3
CONTENT
SL.NO DESCRIPITON PAGE NO
1 ACKNOWLEDGEMENT 5
2 INTRODUCTION AND OBJECTIVE 6
3 FEASIBILITY ANALYSIS 8
4 FEASIBILITY STUDY 9
INTRODUCTION TO FRONT END APPLICATION

5 OVERVIEW OF C#.NET 10
INTRODUCTION TO BACK END APPLICATION

6 13
OVERVIEW OF MS ACCESS
5 18
SYSTEM REQUIREMENTS
6 19
SOFTWARE DEVELOPMENT LIFE CYCLE
7 DATA FLOW DIAGRAM 20
8 E-R DIAGRAM 21
9 DATA STRUCTURES AND DATABASE SPECIFICATION 24
10 DESIGN 31
11 CODDING 34
12 TESTING AND DEBUGGING 45
13 SCOPE OF THE PROJECT 48
BIBILOGRAPHY 49
ACKNOWLEDGEMENT
4
I have taken efforts in this project. However, it would not have been possible
without the kind support and help of many individual. I would like to extend my
sincere thanks to all of them.
I am highly indebted to my Head of the Institute Mr. Jacob M.O who gave me
the golden opportunity to do this wonderful project (Bank Management
System)and his guidance and constant supervision as well as for providing
necessary information regarding the project & also for his support in completing
the project.
I owe my deep gratitude to our project guide Mr. SurajitSarkar, who

took keen interest on our project work and guided us all along, till the
completion of our project work by providing all the necessary
information for developing a good system.
My thanks and appreciations also go to my colleague in developing the project

and people who have willingly helped me out with their abilities.
I also thank all my friends who have more or less contributed to the preparationof
this project report. I will be always indebted to them. The study has indeed
helped me to explore more knowledgeable avenues related tomy topic and I am
sure it will help me in my future
Date: 09 /04/2019 Poonam Basumatary
5
INTRODUCTION
During the past several decades’ personnel function has been transformed from
a relatively obscure record keeping staff to central and top level management
function. There are many factors that have influenced this transformation like
technological advances, professionalism, and general recognition of human
beings as most important resources.
A computer based management system is designed to handle all the primary
information required to calculate monthly statements of customer account
which include monthly statement of any month. Separate database is maintained
to handle all the details required for the correct statement calculation and
generation.
This project intends to introduce more user friendliness in the various activities
such as record updation, maintenance, and searching. The searching of record
has been made quite simple as all the details of the customer can be obtained by
simply keying in the identification or account number of that customer.
Similarly, record maintenance and updation can also be accomplished by using
the account number with all the details being automatically generated. These
details are also being promptly automatically updated in the master file thus
keeping the record absolutely up-to-date.
The entire information has maintained in the database or Files and whoever
wants to retrieve can’t retrieve, only authorization user can retrieve the
necessary information which can be easily be accessible from the file.
6
Project on Bank Management System
OBJECTIVE OF THE PROJECT
A computer based management system is designed to handle all the primary

information required to calculate monthly statements of customer account which
include monthly statement of any month. Separate database is maintained to
handle all the details required for the correct statement calculation and
generation.
This project intends to introduce more user friendliness in the various activities
such as record updating, maintenance, and searching. The searching of record has
been made quite simple as all the details of the customer can be obtained by simply
keying in the identification or account number of that customer. Similarly, record
maintenance and updating can also be accomplished by using the account number
with all the details being automatically generated. These details are also being
promptly automatically updated in the master file thus keeping the record
absolutely up-to-date.
The main objective of our project is providing the different typed of customers
facility, the main objective of this system is to find out the actual customer service.
Etc.
 It should fulfill almost all the process requirements of any Bank.

 It should increase the productivity of bank by utilizing the working hours
more and more, with minimum manpower.
This project includes the entire upgraded feature required for the computerization
banking system. This system is very easy to use, so that any user can use without
getting pre-knowledge about this. Its very much user friendly and meet almost all
daily working process requirements. This system is completely GUI based and
can be use by mouse and as well as keyboard. This system is melded in such a way
that has got all features to upgrade without making much change in existing
components.
AMTRON AUTHORIZED COMPUTER CENTRE, KOKRAJHAR Page | 7

FEASIBILITY ANALYSIS
Depending on the results of the initial investigation, the survey is expanded

to a more detailed feasibility study. A feasibility study is a test of a system
proposal. According to its workability, impact on the organization, ability to
meet user’s needs and effective use of the resources its main task done during
the feasibility study are: -
Evaluation of existing system and procedures. Our group went to various

Banking Professionals to gather information about the software system.
They are using and evaluating those systems and the procedures invoked in
it during the period of feasibility study.
Analysis of alternative candidate systems after studying the various systems

we derived various alternatives through which we develop our project and
evaluated the alternative. The most appropriate is selected.

FEASIBILITY STUDY
The only tangible benefit provided by the proposed system is that the paper
work is reduced to the minimum and hence the reduction in cost incurred on
Stationary and its storage. The system provides many benefits that can’t be
measured in terms of Money for e.g. user’s friendliness, more user response
being more efficient.
 TECHNICALFEASIBILITY
The proposed system is technically feasible as it can be developed easily with the
help of available technology. The proposed system requires MS VISUAL Studio
2010 using c#.Net as an Interface for Programming & back-end as MS ACCESS
2007 for storing/maintaining database.
 OPERATIONAL FEASIBILITY
Automation makes our life easy. The proposed system is highly user friendly and
is much easily able to interact with the system. Therefore, the users will readily
accept the system as data entry and making queries can be easily done.

INTRODUCTION TO FRONT END TOOL
 Visual programming aims at providing the user with an interface that is intuitive and easy
to use. In developing such an interface, the programmer employs user-friendly features
such as windows, menus, buttons and list boxes.
 Its Environment provides all features that are required to develop a graphical user
interface as ready -to- use components. The programmer does not have to write code to
create and display commonly required user-friendly features each time around.
 When the programmer needs a specific user interface feature such as button, he selects the
appropriate ready-to-use component provided by the visual programming environment.
These components can be moved, resized and renamed as required.
 For Example: -
If the programmer needs to have a button, then the visual programming environment
provides him with one. All that, the programmer does this select the button and place
it on screen at the required position.
 Typically, the mouse is used to select and place the necessary components. Thus, the
visual programming environment is also called a point and click environment.
 A visual programming environment automates the process of creating a user

interface. The interface provided by the visual programming environment to the
programmer designs the user interface visually instead of writing code.
Overview ofC#.net

C# is pronounced as "C-Sharp". It is an object-oriented programming language

provided by Microsoft that runs on .Net Framework.
By the help of C# programming language, we can develop different types of

secured and robust applications:
 Window applications
 Web applications
 Distributed applications
 Web service applications
 Database applications etc.
C# is approved as a standard by ECMA and ISO. C# is designed for CLI

(Common Language Infrastructure). CLI is a specification that describes
executable code and runtime environment.
C# programming language is influenced by C++, Java, Eiffel, Modula-3, Pascal

etc. languages.
.NET Framework Platform Architecture

C# programs run on the .NET Framework, an integral component of Windows that
includes a virtual execution system called the common language runtime (CLR) and a
unified set of class libraries. The CLR is the commercial implementation by Microsoft
of the common language infrastructure (CLI), an international standard that is the
basis for creating execution and development environments in which languages and
libraries work together seamlessly.
Source code written in C# is compiled into an intermediate language (IL) that

conforms to the CLI specification. The IL code and resources, such as bitmaps and
strings, are stored on disk in an executable file called an assembly, typically with an
extension of .exe or .dll. An assembly contains a manifest that provides information
about the assembly's types, version, culture, and security requirements.
When the C# program is executed, the assembly is loaded into the CLR, which might
take various actions based on the information in the manifest. Then, if the security
requirements are met, the CLR performs just in time (JIT) compilation to convert the
IL code to native machine instructions. The CLR also provides other services related
to automatic garbage collection, exception handling, and resource management. Code
that is executed by the CLR is sometimes referred to as "managed code," in contrast
to "unmanaged code" which is compiled into native machine language that targets a
specific system. The following diagram illustrates the compile-time and run-time
relationships of C# source code files, the .NET Framework class libraries, assemblies,
and the CLR.
Language interoperability is a key feature of the .NET Framework. Because the IL

code produced by the C# compiler conforms to the Common Type Specification
(CTS), IL code generated from C# can interact with code that was generated from
the .NET versions of Visual Basic, Visual C++, or any of more than 20 other CTS-
compliant languages. A single assembly may contain multiple modules written in
different .NET languages, and the types can reference each other just as if they were
written in the same language.
In addition to the run time services, the .NET Framework also includes an extensive
library of over 4000 classes organized into namespaces that provide a wide variety of
useful functionality for everything from file input and output to string manipulation
to XML parsing, to Windows Forms controls. The typical C# application uses the
.NET Framework class library extensively to handle common "plumbing" chores.

INTRODUCTION TO BACK END TOOL

Overview of MS Access
Database
A Database is a collection of related data organized in a way that data can be easily
accessed, managed and updated. Database can be software based or hardware based,
with one sole purpose, storing data.
During early computer days, data was collected and stored on tapes, which were mostly
write-only, which means once data is stored on it, it can never be read again. They were
slow and bulky, and soon computer scientists realised that they needed a better solution
to this problem.
Larry Ellison, the co-founder of Oracle was amongst the first few, who realised the
need for a software based Database Management System.
DBMS
A DBMS is a software that allows creation, definition and manipulation of database,
allowing users to store, process and analyse data easily. DBMS provides us with an
interface or a tool, to perform various operations like creating database, storing data in
it, updating data, creating tables in the database and a lot more.
DBMS also provides protection and security to the databases. It also maintains data
consistency in case of multiple users.
Here are some examples of popular DBMS used these days:
 MySql
 Oracle
 SQL Server
 IBM DB2
 PostgreSQL
 Amazon SimpleDB (cloud based) etc.
MSACCESS
Ms Access is a database management tool that enables one to have good command of
data collected. The programme enables one to retrieve, sort, summarize and report
results speedily and effectively. It can combine data from various files through creating
relationships and can make data entry more efficient and accurate. Microsoft Access (MS
Access) enables one to manage all important information from a single database file.
Within the file, one can use:
 Tables to store your data.

 Queries to find and retrieve specific data of interest.

 Forms to view, add, and update data in tables.
 Reports to analyze or print data in a specific layout.
 Data access pages to view or update, the data.
In MS Access, data is stored once in one table, but can be viewed from multiple locations.
When the data is updated in a Table, Query or Form, it is automatically updated

everywhere it appears
Establishment of Ms Access database
All Ms Access databases files are saved with extension .mdb
A database should have a separate table for every major subject, such as student records,
Production data or Treatment information. Data should not be duplicated in multiple
tables.
Microsoft Access provides three methods to create a database
 Database Wizard (though easy, the wizard offers limited options to customize the
database)
 Using a template (This method works best if one can find and use a template that
closely matches the specific requirements)
 Creating a database directly (This is the most flexible method, but it requires one
to define each database element separately).
Create Access 2007 Database

The first step in creating an Access 2007 database, is to create a blank database file. This
is done from the Getting Started Screen when you launch Access. The file is saved onto
one of your PCs folders (which you specify). The procedure for doing this is outlined
below.
1. Launch Access
To begin, launch Access by clicking on the desktop icon, or choose Access from the start
menu. This brings up the GETTING STARTED WITH MICROSOFT OFFICE ACCESS
screen.
2. Select Blank Database Template

Towards the top left of the screen you will see a "Blank Database" icon. Click this
icon to bring up the Blank Database side bar on the right hand side of the screen.
This is where you will enter details about the database file that you are about to
create.
3. Enter filename for your Access 2007 database
Begin by entering the name that you want to call the database in the filename
textbox.
4. Browse and select folder
Next click the folder icon and browse for a folder to put your database. Once
selected you should see the file path below the textbox.
5. Click Create
All you need to do now is click the "Create" command button below, and your
database file saves to the location that you specified, and opens for you to work
on.
You are now ready to work on your newly created database file.
The next step is to create an Access table
Create Access Table
1. Open database file
If you created a blank Access database in the previous tutorial lesson, you are now
ready to create a new table. Begin by opening your existing database file if it is not
already open. Do this by clicking on the Access desktop icon to bring up the getting
started screen again. You should see the file name that you just created towards
the top of the right hand side bar (If you cant see it, click the folder icon to browse
for the file). Click on the file name to bring up your blank database.

If, at this stage, you get a security warning underneath the ribbon, click where it
says options, select the "enable this content" radio button (in the pop-up
window), and then click ok.
Our blank database file should now be fully open.
2. Create Access Table
Select the CREATE tab on the Access ribbon. Next select the TABLE DESIGN icon
from the TABLES group. This creates a new table.
3. Create fields in DESIGN VIEW
This brings up the TABLE DESIGN GRID where you enter each field name and its
data type. The first field we are going to create is the ID field which is going to
contain a unique reference number for each record. Enter the name "ID" into the
first column of the first row in the grid. Because we want Access to automatically
generate a unique reference number, select AUTONUMBER from the drop down
list in the data type column. You can also enter a description for each field, but
this is not essential.

On the next row the field is going to be called FIRSTNAME and the data type is
going to be TEXT. On the third row the field name is SURNAME with the data type
again being TEXT. And finally, the last field name is AGE and the data type here is
going to be NUMBER.
Before you save the table you will need to choose the Primary Key, which in this
case is ID. To do this, select the ID row by clicking on it, and then simply click the
primary key symbol on the Ribbon.
The table design grid should now look like this:
We can now save the table by clicking the save icon on the top left of the screen
above the Access Ribbon. To view your table select DATASHEET VIEW from the
VIEWS group under the DESIGN TAB. This brings up the datasheet view of the
table that you have just created. You should see your field headings running across
the top of the table.

SYSTEM REQUIREMENTS
Hardware specifications
Hardware is a set of physical components, which performs the functions of applying

appropriate, predefined instructions. In other words, one can say that electronic and
mechanical parts of computer constitute hardware.
This package is designed on a powerful programming language Visual Basic. It is a
powerful Graphical User Interface. The backend is ACCESS, which is used to
maintain database. It can run on almost all the popular microcomputers. The following
are the minimum hardware specifications to run this package: -
Personal Computer: -
It minimum contains P-III
Processor with 128 MB RAM
Software Requirements:
The software is a set of procedures of coded information or a program which

when fed into the computer hardware, enables the computer to perform the
various tasks. Software is like a current inside the wire, which cannot be seen
but its effect can be felt.
 Operating System: - Windows NT / 2000 / XP

 Application Software: - Application software uses front end visual basic
2010 and database access etc. Editor: - Visual basic 2010.

SOFTWARE DEVELOPMENT LIFE CYCLE
A system development life cycle is a logical process by which system analysts, software
engineers, programmers, and end users build information systems and computer
applications to solve business problems and needs.
The major phases involved in the MIS development process are referred to as system
development life cycle. Each phase of the development process must have well defined
objectives, and at the end of each phase ,progress towards meeting the objectives must be
evaluated.
The development process should not continue until the objectives of all prior phases have
been met.
System development life cycle is a phased approach to analysis and design to ensure that
systems are best developed.
The system development life cycle can be divided into seven phases as shown in fig

DATA FLOW DIAGRAM
 DATA FLOW DIAGRAM: -The data flow diagram is also known as “bubble
chart” has the purpose of clarifying system requirements and identifying major
transformations that will become programs in system design so it is the starting
point of specification down to the lowest level of detail. A DFDs consists of a series
if bubbles joined by lines. The bubbles represent data transformation and the
lines represent the data flow in the system.
 DFD SYMBOLS:
 A system defined a source or destination of data.

 An arrow identifies data flow, data in motion.
 A circle represents the process that transforms incoming data flow to outgoing
data flow.
 An open rectangular is data store-data at rest or a temporary repository of
data.
SYSTEM DATA FLOW DIAGRAM
BANKING ACCOUNT HOLDERS

TRANSACTION
S
DATABASE

E-R DIAGRAM
ER-modeling is a data modeling technique used in software engineering to produce a

conceptual data model of a information system. Diagrams created using this ER-
modeling technique are called Entity-Relationship Diagrams, or ER diagrams or ERDs.
So you can say that Entity Relationship Diagrams illustrate the logical structure of
databases.
Dr. Peter Chen is the originator of the Entity-Relationship Model. His original paper
about ER-modeling is one of the most cited papers in the computer software field.
Currently the ER model serves as the foundation of many system analysis and design

methodologies, computer-aided software engineering (CASE) tools, and repository

systems.
The original notation for ER-Diagrams uses rectangles to represent entities, and
diamonds to represent relationships.
There are three basic elements in ER-Diagrams:
 Entities are the "things" for which we want to store information. An

entity is a person, place, thing or event.
 Attributes are the data we want to collect for an entity.
 Relationships describe the relations between the entities.
ERDs show entities in a database and relationships between tables within that database.
It is essential to have ER-Diagrams if you want to create a good database design. The
diagrams help focus on how the database actually works.
Entity (Instance)
Aninstance ofaphysical object in the real world.
Entity Class
: Group of objects of the same type.
E.g. Entity Class “Student”, Entities “John”, “Trish” etc
Attributes
Properties of Entities that describetheir characteristics.

Types of Attributes:
Simple Composite Multiple
Attribute that is not Attribute composed of several Attribute with a set of

divisible, e.g. age. simple attributes, possible values for the
same entity,
e.g. address (house number,
street, district) e.g. Phone (home, mobile
etc.) or email
Key
Uniquely Ids the Entity e.g. PPSN, Chassis No.Each simple attribute associated with a
VS that may be assigned to that attribute for each individual entity, e.g. age = integer

DATA STRUCTURES AND DATABASE SPECIFICATIONS
“ACCOUNT_HOLDERS” Table: -
Field Name Type Constraints
AccountHolderID AutoNumber Primary Key
AccountID Number
Surname Short Text
OtherNames Short Text
MaidenName Short Text
TitleID Number
Gender Number
DateOfBirth Date/Time
PlaceAndCountryOfBirth Short Text
Nationality Short Text
Occupation Short Text
Employer Short Text
OfficePhone Short Text
HomePhone Short Text
MobilePhone Short Text
POBox Short Text
EMail Short Text
HolderType Number
DigitalSign Short Text

Picture Short Text
IdentificationDetailsID Number
“ACCOUNTh_TYPES” Table: -
AccountTypeID AutoNumber Primary Key
AccountType Short Text
MinimumBalance Short Text
Rate Short Text
Description Short Text
CanHaveChequeBook Number 1->Can Have Cheque Book, 0 -> Can

Not have cheque book
BANK_BRANCHES” Table: -
BranchID AutoNumber Primary Key
BankID Number
BranchNo Short Text
BranchName Short Text
Address Short Text
WebSite Short Text
EMail Short Text

PhoneNo1 Short Text
PhoneNo2 Short Text
Fax Short Text
POBox Short Text
City Short Text
Country Short Text
Location Short Text
“tb_USERS” Table: -
Field Name Data type Constraints
UserID Number Primary Key
UserName Short Text
Password Short Text
FullName Short Text
Status Number
Deleted Number
Active Number
Admin Number
LastPasswordChangeDate Date/Time
LastLoginDate Date/Time
LastLoginWorkStation Short Text

Picture Short Text
“tb_BANKS” Table: -
Field Name Data type Description
BankID Number Primary Key
BankName Short Text
Field Name Data type Description
Motto Short Text
Slogan Short Text
Logo Short Text
“tb_TRNSACTIONS” Table: -
TransactionID Number Primary Key
TransactionDate Date/Time
TransactionTypeID Number
TransactionMode Short Text

FromAccountID Number
FromAccountNo Short Text
ToAccountID Number
ToAccountNo Short Text
ChequeNo Number
ChequeNumber Short Text
Amount Short Text
Status Number
DepositedBy Short Text
“tb_ACCOUNTS” Table: -
AccountID Number Primary Key
AccountNumber Short Text
AccountName Short Text
AccountType Number
CurrencyType Number
InitialDeposit Short Text
Balance Short Text
DateOpened Date/Time
“tb_IDENTIFICATION_DETAILS” Table: -

IdentificationDetailID AutoNumber Primary Key
IdentificationTypeID Number
IdentificationNo Short Text
DateIssued Date/Time
IssuedAt Short Text
IssuedBy Short Text
ResidencePermitNo Short Text

DESIGN
Login Screen
Change Password

Cash Deposit
Transfer

Bank Statement
Customer Report

C#.Net Codding
using System;
usingSystem.Windows.Forms;
usingSystem.Diagnostics;
using BMS.CLASSES;
usingFireball.Docking;
namespace BMS.FORMS
{
publicpartialclassfrm_MAIN : Form
{
cls_USERScls_USERS_OBJ = newcls_USERS();
publicstaticfrm_MAINfrm_MAIN_obj;
publicfrm_MAIN()
{
InitializeComponent();
}
privatevoidfrm_MAIN_Load(object sender, EventArgs e)

{
frm_MAIN_obj = this;
frm_SPLASH_SCREENfrm_SPLASH_SCREEN_obj = newfrm_SPLASH_SCREEN();
frm_SPLASH_SCREEN_obj.ShowDialog();
//frm_LOGINfrm_LOGIN_OBJ = new frm_LOGIN();
//frm_LOGIN_OBJ.ShowDialog();
}
privatevoidusersToolStripMenuItem_Click(object sender, EventArgs e)

{
Users();
}
privatevoid Users()
{
foreach (Formfrminthis.MdiChildren)
{
if (frmisfrm_USERS) { frm.Focus(); return; }
}
frm_USERSfrm_USERS_obj = newfrm_USERS();
frm_USERS_obj.Show(dockContainer, DockState.Document);
}
privatevoidbankProfileToolStripMenuItem_Click(object sender, EventArgs e)

{
bankProfile();
}
privatevoidbankProfile()
{
frm_BANK_PROFILEfrm_BANK_PROFILE_obj = newfrm_BANK_PROFILE();
frm_BANK_PROFILE_obj.ShowDialog();
}

privatevoidaccountsToolStripMenuItem_Click(object sender, EventArgs e)

{
accounts();
}
privatevoid accounts()
{
{
if (frmisfrm_BANK_ACCOUNTS) { frm.Focus(); return; }
}
frm_BANK_ACCOUNTSfrm_BANK_ACCOUNTS_obj = newfrm_BANK_ACCOUNTS();
//frm_BANK_ACCOUNTS_obj.MdiParent = this;
frm_BANK_ACCOUNTS_obj.Show(dockContainer, DockState.Document);
}
privatevoidaccountTypesToolStripMenuItem_Click(object sender, EventArgs e)

{
accountTypes();
}
privatevoidaccountTypes()
{
frm_ACCOUNT_TYPESfrm_ACCOUNT_TYPES_obj = newfrm_ACCOUNT_TYPES();
frm_ACCOUNT_TYPES_obj.ShowDialog();
}
privatevoidcurrencyTypesToolStripMenuItem_Click(object sender, EventArgs e)

{
currencyTypes();
}
privatevoidcurrencyTypes()
{
frm_CURRENCY_TYPESfrm_CURRENCY_TYPES_obj = newfrm_CURRENCY_TYPES();
frm_CURRENCY_TYPES_obj.ShowDialog();
}
privatevoidcustomerTypesToolStripMenuItem_Click(object sender, EventArgs e)

{
customerTypes();
}
privatevoidcustomerTypes()
{
frm_CUSTOMER_TYPESfrm_CUSTOMER_TYPES_obj = newfrm_CUSTOMER_TYPES();
frm_CUSTOMER_TYPES_obj.ShowDialog();
}
privatevoididentificationTypesToolStripMenuItem_Click(object sender, EventArgs e)

{
identificationTypes();
}
privatevoididentificationTypes()
{
frm_IDENTIFICATION_TYPESfrm_IDENTIFICATION_TYPES_obj = newfrm_IDENTIFICATION_TYPES();
frm_IDENTIFICATION_TYPES_obj.ShowDialog();
}
privatevoidtitleTypesToolStripMenuItem_Click(object sender, EventArgs e)

{
titleTypes();

privatevoidtitleTypes()
{
frm_TITLE_TYPESfrm_TITLE_TYPES_obj = newfrm_TITLE_TYPES();
frm_TITLE_TYPES_obj.ShowDialog();
}
privatevoidcustomerQueriesToolStripMenuItem_Click(object sender, EventArgs e)

{
customerQueries();
}
privatevoidchequeBook()
{
{
if (frmisfrm_CHEQUE_BOOK) { frm.Focus(); return; }
}
frm_CHEQUE_BOOKfrm_CHEQUE_BOOK_obj = newfrm_CHEQUE_BOOK();
frm_CHEQUE_BOOK_obj.Show(dockContainer, DockState.Document);
}
privatevoid Transfer()
{
{
if (frmisfrm_TRANSFER) { frm.Focus(); return; }
}
frm_TRANSFERfrm_TRANSFER_obj = newfrm_TRANSFER();
frm_TRANSFER_obj.Show(dockContainer, DockState.Document);
}
privatevoidcustomerQueries()
{
{
if (frmisfrm_CUSTOMER_QUERIES) { frm.Focus(); return; }
}
frm_CUSTOMER_QUERIESfrm_CUSTOMER_QUERIESS_obj = newfrm_CUSTOMER_QUERIES();
frm_CUSTOMER_QUERIESS_obj.Show(dockContainer, DockState.Document);
}
privatevoidtransactionTypesToolStripMenuItem_Click(object sender, EventArgs e)

{
transactionTypes();
}
privatevoidtransactionTypes()
{
frm_TRANSACTION_TYPESfrm_TRANSACTION_TYPES_obj = newfrm_TRANSACTION_TYPES();
frm_TRANSACTION_TYPES_obj.ShowDialog();
}
privatevoid cashDepositToolStripMenuItem1_Click(object sender, EventArgs e)

{
cashDeposit();
}
privatevoidcashDeposit()
{
{
if (frmisfrm_CASH_DEPOSIT) { frm.Focus(); return; }

}
frm_CASH_DEPOSITfrm_CASH_DEPOSIT_obj = newfrm_CASH_DEPOSIT();
frm_CASH_DEPOSIT_obj.Show(dockContainer, DockState.Document);
}
privatevoidchequeDepositToolStripMenuItem_Click(object sender, EventArgs e)

{
chequeDeposit();
}
privatevoidchequeDeposit()
{
{
if (frmisfrm_CHEQUE_DEPOSIT) { frm.Focus(); return; }
}
frm_CHEQUE_DEPOSITfrm_CHEQUE_DEPOSIT_obj = newfrm_CHEQUE_DEPOSIT();
frm_CHEQUE_DEPOSIT_obj.Show(dockContainer, DockState.Document);
}
privatevoidwithdrawalToolStripMenuItem_Click(object sender, EventArgs e)

{
withdrawal();
}
privatevoid withdrawal()
{
{
if (frmisfrm_WITHDRAWAL) { frm.Focus(); return; }
}
frm_WITHDRAWALfrm_WITHDRAWAL_obj = newfrm_WITHDRAWAL();
frm_WITHDRAWAL_obj.Show(dockContainer, DockState.Document);
}
privatevoidcalculatorToolStripMenuItem_Click(object sender, EventArgs e)

{
calculator();
}
privatevoid calculator()
{
try { Process.Start("calc.exe"); }
catch (Exception ex) { cls_UTILITY.displayMessage(ex.Message, MessageBoxIcon.Error); }
}
privatevoidcalendarToolStripMenuItem_Click(object sender, EventArgs e)

{
notepad();
}
privatevoid notepad()
{
try { Process.Start("Notepad.exe"); }
}
privatevoidnotepadToolStripMenuItem_Click(object sender, EventArgs e)

{
wordpad();
}
privatevoidwordpad()
{

try { Process.Start("Write.exe"); }
}
privatevoidmToolStripMenuItem_Click(object sender, EventArgs e)

{
paint();
}
privatevoid paint()
{
try { Process.Start("MSPaint.exe"); }
}
privatevoidbankBranchesToolStripMenuItem_Click(object sender, EventArgs e)

{
bankBranches();
}
privatevoidbankBranches()
{
{
if (frmisfrm_BANK_BRANCHES) { frm.Focus(); return; }
}
frm_BANK_BRANCHESfrm_BANK_BRANCHES_obj = newfrm_BANK_BRANCHES();
frm_BANK_BRANCHES_obj.Show(dockContainer,DockState.Document );
}
privatevoidoptionsToolStripMenuItem_Click(object sender, EventArgs e)

{
options();
}
privatevoid options()
{
frm_OPTIONSfrm_OPTIONS_obj = newfrm_OPTIONS();
frm_OPTIONS_obj.ShowDialog();
}
privatevoidlogOffToolStripMenuItem_Click(object sender, EventArgs e)

{
logOff();
}
privatevoidlogOff()
{
if (cls_UTILITY.displayMessage("Are you sure you want to log off ?") == true)
{
saveUserAccessLogOut(cls_GLOBAL_VARIABLES.intUserID);
frm_LOGINfrm_LOGIN_obj = newfrm_LOGIN();
frm_LOGIN_obj.ShowDialog();
}
}
privatevoidquitApplicationToolStripMenuItem_Click(object sender, EventArgs e)

{
quitApplication();
}
privatevoidquitApplication()
{
if (cls_UTILITY.displayMessage("Are you sure you want to exit ?") == true)

{
Application.Exit();
}
}
privatevoidchangePasswordToolStripMenuItem_Click(object sender, EventArgs e)

{
changePassword();
}
privatevoidchangePassword()
{
frm_CHANGE_PASSWORDfrm_CHANGE_PASSWORD_obj = newfrm_CHANGE_PASSWORD();
frm_CHANGE_PASSWORD_obj.ShowDialog();
}
privatevoidaccountSearchToolStripMenuItem_Click(object sender, EventArgs e)

{
accountReport();
}
privatevoidaccountReport()
{
{
if (frmisfrm_BANK_ACCOUNT_SEARCH) { frm.Focus(); return; }
}
frm_BANK_ACCOUNT_SEARCHfrm_BANK_ACCOUNT_SEARCH_obj = newfrm_BANK_ACCOUNT_SEARCH();
frm_BANK_ACCOUNT_SEARCH_obj.Show(dockContainer, DockState.Document);
}
privatevoidcustomerReportToolStripMenuItem_Click(object sender, EventArgs e)

{
customerReport();
}
privatevoidcustomerReport()
{
{
if (frmisfrm_CUSTOMER_SEARCH) { frm.Focus(); return; }
}
frm_CUSTOMER_SEARCHfrm_CUSTOMER_SEARCH_obj = newfrm_CUSTOMER_SEARCH();
frm_CUSTOMER_SEARCH_obj.Show(dockContainer, DockState.Document);
}
privatevoid transactionsToolStripMenuItem1_Click(object sender, EventArgs e)

{
transactions();
}
privatevoid transactions()
{
{
if (frmisfrm_TRANSACTIONS) { frm.Focus(); return; }
}
frm_TRANSACTIONSfrm_TRANSACTIONS_obj = newfrm_TRANSACTIONS();
frm_TRANSACTIONS_obj.Show(dockContainer, DockState.Document);
}
privatevoidaccountStatement()
{

{
if (frmisfrm_BANK_STATEMENTS ) { frm.Focus(); return; }
}
frm_BANK_STATEMENTSfrm_BANK_STATEMENTS_obj = newfrm_BANK_STATEMENTS();
frm_BANK_STATEMENTS_obj.Show(dockContainer, DockState.Document);
}
privatevoidlockApplicationToolStripMenuItem_Click(object sender, EventArgs e)

{
lockApplication();
}
privatevoidlockApplication()
{
if (cls_UTILITY.displayMessage("Are you sure you want to lock application ?") == true)
{
frm_LOGINfrm_LOGIN_obj = newfrm_LOGIN();
frm_LOGIN_obj.ShowDialog();
}
}
privatevoidsaveUserAccessLogOut(intintUserID)
{
cls_USERS_OBJ.StrWorkStationName = cls_UTILITY.getComputerName();
cls_USERS_OBJ.saveUserAccessLogOut(intUserID);
cls_USERS_OBJ.updateUserLogOutDetails(intUserID);
}
privatevoidfrm_MAIN_FormClosed(object sender, FormClosedEventArgs e)

{
if (cls_GLOBAL_VARIABLES.blLoginStatus == true)
{
}
Application.Exit();
}
privatevoidpicChangePassword_Click(object sender, EventArgs e)

{
if (mnuChangePassword.Enabled == true){changePassword();}
}
privatevoidpicLogOff_Click(object sender, EventArgs e){logOff();}
privatevoidpicLockApplication_Click(object sender, EventArgs e){lockApplication();}
privatevoidpicExitApplication_Click(object sender, EventArgs e){quitApplication();}
privatevoidpicCashDeposit_Click(object sender, EventArgs e)

{
if (mnuCashDeposit.Enabled == true){cashDeposit();}
}
privatevoidpicChequeDeposit_Click(object sender, EventArgs e)

{
if (mnuChequeDeposit.Enabled == true){chequeDeposit();}
}
privatevoidpicWithdrawal_Click(object sender, EventArgs e)

{
if (mnuWithdrawal.Enabled == true){withdrawal();}

privatevoidpicBankProfile_Click(object sender, EventArgs e)

{
if (mnuBankProfile.Enabled == true){bankProfile();}
}
privatevoidpicBankBranches_Click(object sender, EventArgs e)

{
if (mnuBankBranches.Enabled == true){bankBranches();}
}
privatevoidpicBankAccounts_Click(object sender, EventArgs e)

{
if (mnuBankAccounts.Enabled == true) { accounts(); }
}
privatevoidpicCustomerQueries_Click(object sender, EventArgs e)
{
if (mnuCustomerQueries.Enabled == true) { customerQueries(); }
}
privatevoidpicUsers_Click(object sender, EventArgs e)

{
if (mnuUsers.Enabled == true) { Users(); }
}
privatevoidpicAccountReport_Click(object sender, EventArgs e)

{
if (mnuAccountReport.Enabled == true) { accountReport(); }
}
privatevoidpicCustomerReport_Click(object sender, EventArgs e)

{
if (mnuCustomerReport.Enabled == true) { customerReport(); }
}
privatevoidpicAllTransactions_Click(object sender, EventArgs e)

{
if (mnuAllTransactions.Enabled == true) { transactions(); }
}
privatevoidpicCalculator_Click(object sender, EventArgs e)

{
if (mnuCalc.Enabled == true) { calculator(); }
}
privatevoidpicNotepad_Click(object sender, EventArgs e)

{
if (mnuNotepad.Enabled == true) { notepad(); }
}
privatevoidpicWordpad_Click(object sender, EventArgs e)

{
if (mnuWordPad.Enabled == true) { wordpad(); }
}
privatevoidpicPaint_Click(object sender, EventArgs e)

{
if (mnuPaint.Enabled == true) { paint(); }
}
privatevoidpicOptions_Click(object sender, EventArgs e)

{
if (mnuProgramSettings.Enabled == true) { options(); }

privatevoidpicAccountTypes_Click(object sender, EventArgs e)

{
if (mnuAccountTypes.Enabled == true) { accountTypes(); }
}
privatevoidpicCurrencyTypes_Click(object sender, EventArgs e)

{
if (mnuCurrencyTypes.Enabled == true) { currencyTypes(); }
}
privatevoidpicCustomerTypes_Click(object sender, EventArgs e)

{
if (mnuCustomerTypes.Enabled == true) { customerTypes(); }
}
privatevoidpicIdentificationTypes_Click(object sender, EventArgs e)

{
if (mnuIdentificationTypes.Enabled == true) { identificationTypes(); }
}
privatevoidpicTitleTypes_Click(object sender, EventArgs e)

{
if (mnuTitleTypes.Enabled == true) { titleTypes(); }
}
privatevoidpicTransactionTypes_Click(object sender, EventArgs e)

{
if (mnuTransactionTypes.Enabled == true) { transactionTypes(); }
}
privatevoidpicChequeBook_Click(object sender, EventArgs e)

{
if (mnuChequeBooks.Enabled == true) { chequeBook(); }
}
privatevoid toolStripMenuItem54_Click(object sender, EventArgs e)

{
paint();
}
privatevoidmnuChequeBooks_Click(object sender, EventArgs e)

{
chequeBook();
}
privatevoiddisableFeatures()
{
foreach (ToolStripItem item inmenuStrip.Items)
{
if (item isToolStripMenuItem)
{
foreach (ToolStripItemnewItemin ((ToolStripMenuItem)item).DropDownItems)
{
if (newItemisToolStripMenuItem)
{
newItem.Enabled = false;
}
}
}
}
mnuLogOff.Enabled = true;

mnuLockApplication.Enabled = true;
mnuQuitApplication.Enabled = true;
mnuContents.Enabled = true;
}
publicvoidloadFeatures(intintUserID)
{
disableFeatures();
cls_FEATURES.loadFeatures(intUserID);
foreach (int x incls_GLOBAL_VARIABLES.arrayList)
{
switch (x)
{
case 1:
mnuChangePassword.Enabled = true;
break;
case 2:
mnuCashDeposit.Enabled = true;
break;
case 3:
mnuChequeDeposit.Enabled = true;
break;
case 4:
mnuTransfer.Enabled = true;
break;
case 5:
mnuWithdrawal.Enabled =true;
break;
case 6:
mnuAccountReport.Enabled = true;
break;
case 7:
mnuCustomerReport.Enabled = true;
break;
case 8:
mnuAllTransactions.Enabled = true;
break;
case 9:
mnuBankProfile.Enabled = true;
break;
case 10:
mnuBankBranches.Enabled = true;
break;
case 11:
mnuBankAccounts.Enabled = true;
break;
case 12:
mnuCustomerQueries.Enabled = true;
break;
case 13:
mnuUsers.Enabled = true;
break;

case 14:
mnuProgramSettings.Enabled = true;
break;
case 15:
mnuAccountTypes.Enabled = true;
break;
case 16:
mnuCurrencyTypes.Enabled = true;
break;
case 17:
mnuCustomerTypes.Enabled = true;
break;
case 18:
mnuIdentificationTypes.Enabled = true;
break;
case 19:
mnuTitleTypes.Enabled = true;
break;
case 20:
mnuTransactionTypes.Enabled = true;
break;
case 21:
mnuCalc.Enabled = true;
break;
case 22:
mnuNotepad.Enabled = true;
break;
case 23:
mnuWordPad.Enabled = true;
break;
case 24:
mnuPaint.Enabled = true;
break;
case 25:
mnuChequeBooks.Enabled = true;
break;
case 26:
mnuAccountStatement.Enabled = true;
break;
}
}
}
privatevoidmnuTransfer_Click(object sender, EventArgs e){Transfer();}
privatevoidpicTransfer_Click(object sender, EventArgs e)

{
if (mnuTransfer.Enabled == true) { Transfer(); }
}
privatevoidmnuAccountStatement_Click(object sender, EventArgs e)

{
if (mnuAccountStatement.Enabled == true) { accountStatement(); }
}
privatevoidpicAccountStatement_Click(object sender, EventArgs e)

{
if (mnuAccountStatement.Enabled == true) { accountStatement(); }
}
privatevoidcontentsToolStripMenuItem_Click(object sender, EventArgs e)

{
System.Diagnostics.Process.Start(Application.StartupPath + @"\BMS PRESENTATION.ppt");
}
TESTING AND DEBUGGING
INTRODUCTION:-
The implementation phase of software development is concerned with translating design

specification into source code. The preliminary goal of implementation is to write source code
and internal documentation so that conformance of the code to its specifications can be easily

verified, and so that debugging, testing and modifications are eased. This goal can be achieved
by making the source code as clear and straightforword as possible. Simplicity, clarity and
elegance are the hallmark of good programs, obscurity, cleverness, and complexity are
indications of inadequate design and misdirected thinking.
Source code clarity is enhanced by structured coding techniques, by good coding style, by,
appropriate supporting documents, by good internal comments, and by feature provided in
modern programming languages.
The implementation team should be provided with a well-defined set of software requirement,
an architectural design specification, and a detailed design description. Each team member
must understand the objectives of implementation.
TERMS IN TESTING FUNDAMENTAL
1. Error
The term error is used in two ways. It refers to the difference between the actual output of
software and the correct output, in this interpretation, error is essential a measure of the
difference between actual and ideal. Error is also to used to refer to human action that result in
software containing a defect or fault.
2. Fault
Fault is a condition that causes to fail in performing its required function. A fault is a basic
reason for software malfunction and is synonymous with the commonly used term Bug.
3. Failure
Failure is the inability of a system or component to perform a required function according to
its specifications. A software failure occurs if the behavior of the software is the different
from the specified behavior. Failure may be caused due to functional or performance reasons.
a. Unit Testing
The term unit testing comprises the sets of tests performed by an individual programmer prior
to integration of the unit into a larger system.
A program unit is usually small enough that the programmer who developed it can test it in
great detail, and certainly in greater detail than will be possible when the unit is integrated into
an evolving software product. In the unit testing the programs are tested separately,
independent of each other. Since the check is done at the program level, it is also called
program teasing.
b. Module Testing
A module and encapsulates related component. So can be tested without other system module.
c. Subsystem Testing
Subsystem testing may be independently design and implemented common problems are sub-
system interface mistake in this checking we concentrate on it.
There are four categories of tests that a programmer will typically perform on a program unit.
1) Functional test
2) Performance test
3) Stress test
4) Structure test
1) Functional Test
Functional test cases involve exercising the code with Nominal input values for which
expected results are known; as well as boundary values (minimum values, maximum values
and values on and just outside the functional boundaries) and special values.
2) Performance Test
Performance testing determines the amount of execution time spent in various parts of the
unit, program throughput, response time, and device utilization by the program unit. A certain
amount of avoid expending too much effort on fine-tuning of a program unit that contributes
little to the over all performance of the entire system. Performance testing is most productive
at the subsystem and system levels.
3) Stress Test
Stress test are those designed to intentionally break the unit. A great deal can be learned about
the strengths and limitations of a program by examining the manner in which a program unit
breaks.
4)Structure Test
Structure tests are concerned with exercising the internal logic of a program and traversing
particular execution paths. Some authors refer collectively to functional performance and
stress testing as “black box” testing. While structure testing is referred to as “white box” or
“glass box” testing. The major activities in structural testing are deciding which path to
exercise, deriving test date to exercise those paths, determining the test coverage criterion to
be used, executing the test, and measuring the test coverage achieved when the test cases are
exercised.
DEBUGGING
Defect testing is intended to find areas where the program does not confirm to its
specifications. Tests are designed to reveal the presence of defect in the system.When defect
have been found in the program. There must be discovered and removed. This is called
“Debugging”.
FUTURE SCOPE OF THE PROJECT
This project can be handled in future by doing various modifications like: -
 We can go further for Online Banking.

 We can establish and start various Branches and available help centers
for Account Holder’s Queries.
 We can also deal through internet by creating web pages and a banking
website for internet dealing.
 To attract Account Holder’s we can offer various offers during festivals

months.
 We can also deal in various types of Banking Transactions.
 To have more and more customer satisfaction we will emphasize more

and more on our dealings.
BIBLIOGRAPHY
BOOKS:
1. The Book of Visual Basic 2005: .NET Insight for Classic C# Developers 1st
Edition by Matthew MacDonald
2. Microsoft Office Access 2007: The Complete Reference (Complete Reference
Series) Paperback – Audiobook, Import by Virginia Andersen

3. Accelerated VB 2005 (Expert's Voice in .NET) Paperback – Import, 23 Mar 2007

by Trey Nash
WEBSITE:
1. https://www.google.com
2. https://www.wikihow.com

"Banking Management System": Project On

Uploaded by

Copyright:

Available Formats

"Banking Management System": Project On

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

"Banking Management System": Project On

Uploaded by

Copyright:

Available Formats

AMTRON COMPUTER CENTRE

12. Other Certificate :-

Place: Kokrajhar, Assam

 Multi-tasking, Prioritizing and Planning Tasks

NAME – SURAJIT SARKAR

FATHERS NAME- SRI SUBODH KR. SARKAR

PRESENT ADDRESS – C/O NRIPENDRA KR. DAS

MAA SARADA LANE, SUBHASPALLY WORD NO -3

KOKRAJHAR ,ASSAM -783370

MARTIAL STATUS – MARRIED

DATRE OF BIRTH -5TH SEPT 1975

LANGUAGE KNOWN- ENGLISH, HINDI, BENGALI, ASSAMESE

 10TH from D.N.N.H School, Kokrajhar -1990

Industry/Period Job Profile and Responsibility

Role 2. Working as a System administrator for

5. Don Bosco Mission Working a Sr.Faculty to teach C , C++ ,MS SQL

Also developed Online Examination System for

Date : 14th Dec 2017. SurajitSarkar

SL.NO DESCRIPITON PAGE NO

2 INTRODUCTION AND OBJECTIVE 6

INTRODUCTION TO FRONT END APPLICATION

INTRODUCTION TO BACK END APPLICATION

9 DATA STRUCTURES AND DATABASE SPECIFICATION 24

12 TESTING AND DEBUGGING 45

13 SCOPE OF THE PROJECT 48

I owe my deep gratitude to our project guide Mr. SurajitSarkar, who

My thanks and appreciations also go to my colleague in developing the project

Date: 09 /04/2019 Poonam Basumatary

OBJECTIVE OF THE PROJECT

A computer based management system is designed to handle all the primary

 It should fulfill almost all the process requirements of any Bank.

AMTRON AUTHORIZED COMPUTER CENTRE, KOKRAJHAR Page | 7

Depending on the results of the initial investigation, the survey is expanded

Evaluation of existing system and procedures. Our group went to various

Analysis of alternative candidate systems after studying the various systems

AMTRON AUTHORIZED COMPUTER CENTRE, KOKRAJHAR Page | 8

AMTRON AUTHORIZED COMPUTER CENTRE, KOKRAJHAR Page | 9

INTRODUCTION TO FRONT END TOOL

 A visual programming environment automates the process of creating a user

AMTRON AUTHORIZED COMPUTER CENTRE, KOKRAJHAR Page | 10

C# is pronounced as "C-Sharp". It is an object-oriented programming language

By the help of C# programming language, we can develop different types of

C# is approved as a standard by ECMA and ISO. C# is designed for CLI

C# programming language is influenced by C++, Java, Eiffel, Modula-3, Pascal

.NET Framework Platform Architecture

Source code written in C# is compiled into an intermediate language (IL) that

Language interoperability is a key feature of the .NET Framework. Because the IL

AMTRON AUTHORIZED COMPUTER CENTRE, KOKRAJHAR Page | 12

INTRODUCTION TO BACK END TOOL

 Amazon SimpleDB (cloud based) etc.

Within the file, one can use:

 Tables to store your data.

 Queries to find and retrieve specific data of interest.

When the data is updated in a Table, Query or Form, it is automatically updated

Establishment of Ms Access database

All Ms Access databases files are saved with extension .mdb

Microsoft Access provides three methods to create a database

Create Access 2007 Database