INTRODUCTION TO BANK RESERVATION SYSTEM
1
This system provides the basic services to manage bank accounts at a bank called ABC Bank. ABC Bank has many branches, each of which has an address and branch number. A client opens accounts at a branch. Each account is uniquely identified by an account number; it has a balance and a credit or overdraft limit. There are many types of accounts, including: A mortgage account (which has a property as collateral), a chequing account, and a credit card account (which has an expiry date and can have secondary cards attached to it). It is possible to have a joint account (e.g. for a husband and wife). Each type of account has a particular interest rate, a monthly fee and a specific set of privileges (e.g. ability to write cheques, insurance for purchases etc. ABC Bank is divided into divisions and subdivisions (such as Planning, Investments and Consumer), the branches are considered subdivisions of the Consumer Division. Each division has a manager and a set of other employees. Each customer is assigned a particular employee as his or her ‘personal banker’.a This is a project on the banking management system .It includes the forms, the interfaces and all the work included in the efficient tasks to be performed in a bank, This is not as secure to be included in the actual implementation in a bank but would contain all the basic features, it is built on the work as included with an example from the prestigious UCO bank. The major parts of this project include the login forms, transaction details, crystal reports etc. The system developed should calculate interest for each account having balance more than zero at the correct interest rate. This interest calculated will be stored in a table which can be updated. The balance on which interest is calculated can change because the customer may deposit or withdraw money.
2
Every month the cumulative interest calculated will be credited to the customer. After this point of time the cumulative interest stored should be set to zero because the customer has benefited for the period specified. 3 different accounts viz. the savings ,fixed deposit or loan account will be created. Sanction for cheques, drafts, pay orders etc also to be included.
OBJECTIVES OF BANK RESERVATION SYSTEM
1) All the transaction details. 2) Loan details included for different types of loans. 3) Different special services like sale of forms like MBA entrance exams can be included. 4) Features for the insurance, loan against fixed deposit etc. can be included. 5) A website restore can also be made for the bank’s special requests using asp.net with c#.net or asp.net with vb.net.
3
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
To solve actual problems in a software project setting, a software engineer or a team of engineers must incorporate a development strategy that includes methods, tools and procedures. this strategy is referred to as a process model or a software development life cycle. There are several such cycles available. Which SDLC is more suitable depends on lot of factors such as: 1. Nature of the project 2. Type of applications 3. Tools proposed to be used 4. Kind of controls and documentation required Code And Fix Life Cycle Model As the name suggests, this model uses an ad hoc approach for the software designing. A very casual study is followed by coding. The issues regarding specification or design are never addressed. Instead, the developers simply build a product that is re-build again and again until the customer is satisfied. Limitations of code-and-fix cycle model This approach may work well for small systems but is very unsatisfactory for larger systems. As the code size increases, the understandability and maintainability of the system decreases.
4
Methodology adopted
The Waterfall Model/Linear Sequential Life Cycle Model We have used classic life cycle methodology, which is best known as waterfall model to develop my project. We performed the phase in the order possibly with some over lap, and with little or no iteration.
Feasibility Study
Hardware Evaluation & Acquisition
Analysis
Design
Development
Implementation
Maintenance
5
The simplest, oldest and most widely used process model for software designing is the waterfall model. It was proposed by Royce in 1970. The essence of this software paradigm is that the process of software designing consists of linear set of distinct phases. These phases are:
Stage1: Feasibility Study
The goal of feasibility study is to evaluate alternative systems and to purpose the most feasible and desirable system for designing. Five types of feasibility are addressed in this study. TECHNICAL FEASIBILITY ECONOMIC FEASIBILITY MOTIVATIONAL FEASIBILITY SCHEDULE FEASIBILITY OPERATIONAL FEASIBILTY
Stage2: Requirement Analysis and Specification
The goal of this phase is to understand the exact requirements of the customers and to document them properly. This activity is usually executed together with the customers, as the goal is to document all functions, performance and interfacing requirements for the software designing and management. The requirements describe “what” of a system. This phase produces a large document containing a description of what the system will
6
do without describing how it will be done. This document is known as software requirement specification (SRS) document.
Stage3: Design
The goal of this phase is to transform the requirement specification produced in the requirement analysis phase into a structure that is suitable for implementation in some programming language, Here, overall software architecture is defined, and the product design and detailed design work is performed. This work is documented and is known as software design description (SDD document).
Stage4: Coding and Unit Testing
The information contained in SDD is sufficient to begin the coding Phase. The coding Phase of software designing involves translation of design specification into a machine readable form. If design is performed in a detailed manner, code generation can be accomplished easily. This phase is also known as the implementation phase. Here, each component of the design is implemented as a program module, and each of these program modules is unit tested. The purpose of unit testing is to determine the correct working of individual modules.
Stage5: Integration and System Testing:
7
During this phase the different program modules are integrated in a planned way and then tested as a completed system to ensure that the designed system functions according to its requirements as specified in the SRS document. After testing, the software is delivered to the customer.
Stage6: Software Maintenance
This is the last phase of software designing which includes a broad set of activities such as error correction, enhancement of capabilities, deletion of ob Advantages 1. Simple and easy to use 2. The phase of the model are processed and completed one at a time. 3. Works very well for smaller software projects. Disadvantages 1.It is often difficult for the customer to state all the requirements. 2. The customer must have patience, as the product is delivered very late in this software process. 3. The model is not suitable for long time software projects.
8
CHAPTER-1 SYSTEM ANALYSIS
1.1 1.2 1.3 1.4 1.4.1 1.4.2
1.4.3
Problem Definition Required Analysis H/W, S/W analysis Feasibility Study Operational Feasibility Economical Feasibility Technical Feasibility
9
1.1 Problem Definition
In this project we have analysed all the aspect of a reservation system between a customer and banking reservation and I have analyzed all the problem faced by customer because I thought on behalf of a customer or thought as a customer what types of doubt & problem faced by customer when he needs to reserve an account so I have tried to solve that doubt and creating transparency between bank processing by a customer and I tried to give the facility to save time and efforts to reserve ticket which is single click away from the reach of customer using advance tools & technology. It is quite enough to start a idea in which I can develop the proposed solution and that problem has to be solved using latest advance tools and technologies. The problem definition describe only the preliminary requirement but as we start system to develop many requirements arises.
10
1.2 Required analysis (SRS)
SOFTWARE REQUIREMENT SPECIFICATION
The software requirement specification (SRS) is very important part of the software building process, which describes the actual user level requirement from technical point of view. I.e. what the user exactly wants? The objective of preparing the software requirement specification is to represent the requirements of the software in such a manner that ultimately leads to successful software implementation. It is the result of the analysis process of the software development. It should contain all the data the software is going to process, the function it will provide, and the behavior it will exhibit.
11
This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE Recommended Practice for Software Requirements Specifications The SRS provides the following functionality:The SRS provides the following functionality:Introduction of the software: - It specifies the goals and objectives of the software. Information description: - It provides the detailed description of the problem that the software must solve. SRS for the ongoing project Problems faced by the passengers 1. Insufficient time 2. reservation problem 3. cost of amount realization 4. Not aware to all the information about different loan terms
12
1.3 HARDWARE , SOFTWARE ANALYSIS
SOFTWARE REQUIREMENTS:
The operating system Framework Front-end tool Editing tool Interface Back-end tool
: Windows 2009 professional/XP : .NET FRAMEWORK 2.0 : ASP.NET with C#.NET : VISUAL STUDIO 2005 : HTML , Stylesheet : SQL Server 2005.
HARDWARE REQUIREMENTS:
Processor/above Memory Modem Network Adapter Secondary Storage
: INTEL PENTIUM-1V , 2.4 GHz : 256 MB,DDR RAM : 56 KBPS voice Fax Data : Ethernet Adapter : HARD DISK 512 MB
13
1.4 FEASIBILITY STUDY
1.4.1 OPERATIONAL FEASIBILITY
It is mainly related to human organizational and political aspects the points to be considered are: *what changes will be brought with the system? *what organizational structures are distributed? *what new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? Generally project will not be rejected simply because of operational infeasibility but such considerations are likely to critically affect the natural and scope of the eventual recommendations. For operational feasibility study we appointed a small group of people who are familier with information system techniques, who understands the parts of the business that are relevant to the project and are skilled in system analysis and design process.
1.4.2 ECONOMICAL FEASIBILITY
14
A financial benefit must exceed the cost of developing that system. i.e. a new system being developed should be a good investment for the organization. Economic feasibility considers the following:The cost if nothing changes (i.e. The proposed system is developed). The proposed “WEB BASED COURSE REGISTRATION ” is economically feasible because :
*The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and man power spent in running the system. *The system requires very less time factors. *The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and man power spent in running the system. *The system will have GUI interface and very less user-training is required to learn it. *The system requires very less time factors. *The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and man power spent in running the system. *The system will have GUI interface and very less user-training is required to learn it.
15
1.4.3 TECHNICAL FEASIBILTY
Technical feasibility centers around the existing computer system (hardware and software) whether it can support the addition of proposed system, if not to what extend it can support the organization’s capacity to acquire required additional components.
Proposed system is technically feasible because of the following reasons:. * Expandability will be maintained in the new system. New modules can be added later on the application, if required in the future. * The application will have User-friendly Forms and Screens, all validation checks. So the new system guarantees accuracy, reliability, ease of access and data security.
16
CHAPTER-2 SYSTEM DESIGN
2.1 ER-Diagram 2.2 DFD 2.3 Database Design 2.4 User Interface Design
17
2.1
Admin_ addres s
ER DIAGRAM
Admin_tel_ no
Admin_id
Admin_fi rst_nam e
Administrat or
Admin_city
manag es
Can see details
Employee
control s Emp_tel_n o Emp_pass word
custome r Cust_i d Cust_do b Cust_fir st_nam e
Emp_i d
Emp_fir st_nam e
issu e loan Laon_dat e Loan_id Loan_amt
18
2.2
DATA FLOW DIAGRAM (DFD)
0 LEVEL DFD
EMPLOYEE
*CHANGE PASSWORD *LOAN *VIEW INFO *CHEQUE BOOK REQUEST
ADMINISTRATOR *VIEW INFO
BANKING
*CHANFE PASS OF CUST/EMP *DELETE CUST/EMP *LOAN INFO *CHANGE PASSWORD
CUSTOMER *CHANGE PASSWORD * LOAN *VIEW INFO *CHEQUE BOOK
19
1 LEVEL DFD
CHEQUE BOOK LOAN
LOGIN
CUSTOMER
CUST A/C MGNT EMPLOYEE VIEW INFO
ADMINISTRATOR
VIEW INFO
MANAGE CUST/EMP
CHANGE PASSWORD
ADMIN
CUST
EMP
A/C MANAGEMENT
20
2.3 DATABASE DESIGN
Introduction: The design is the process of designing exactly how the specifications are to be implemented. It defines specifically how the software is to be written including an object model with properties and method for each object, the client/server technology, the number of tiers needed for the package architecture and a detailed database design. Analysis and design are very important in the whole development cycle. Any glitch in the design could be very expensive to solve in the later stage of the software development.
Basic Modules:
In Our Project with the help of ‘Divide and Conquer theory’ we can divide overall program in 6 modules.
21
1) ADMINISTRATOR TABLE Administrator Table
Attribute First_name Last_name Address Dob City User_id1 Password Re-password Email_id Tel_no Phn_no
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2
Size 30 30 60 20 25 20 30 30 25 Numbe r Numbe r
Description Name of administrator Last name Address Date of birth City User id Password Re-password E-mail id Telephone number Phone number
Constraints
Primary Key
22
2) CUSTOMER TABLE Customer Table
Attribute First_name Last_name Address Dob City User_id1 Password Re-password Email_id Tel_no
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2
Size 30 30 60 20 25 20 30 30 25 Numbe r
Description Name of administrator Last name Address Date of birth City User id Password Re-password E-mail id Telephone number
Constraints
Primary Key
3) CUSTOMER CHEQUE BOOK TABLE
23
Customer Cheque Book Table
Attribute Acct_type Acct_id Branch_name Name No_page
Data Type Varchar2 Varchar2 Varchar2 Number Number
Size 30 30 60 30 40
Description Name of administrator Last name Address Date of birth City
Constraints
4) EMPLOYEE TABLE
24
Employee Table
Attribute First_name Last_name Attribute Address Acct_type Dob Acct_id City Branch_name User_id1 Name Password No_page Re-password Contact_no Email_id address Tel_no Phn_no
Data Type Varchar2
Employee Cheque Book Table
30 Name of administrator Last name Description Address Name of administrator Date of birth Last name City Address User id Date of birth Password City Re-password Contact number E-mail id Address Telephone number Phone number 30 Size 60 30 20 30 25 60 20 30 30 40 30 20 25 40 Numbe r Numbe r
Size
Description
Constraints
Varchar2 Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Varchar2 Number Varchar2 Number Varchar2 Varchar2 Varchar2 Varchar2
Constraints
Primary Key
5) EMPLOYEE CHEQUE BOOK TABLE
25
6) LOAN TABLE
Loan Table
Attribute First_name Last_name Address Dob City User_id1 Loan_amt No_install Downpay
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2
Size 30 30 60 20 25 20 30 30 25
Description Name of administrator Last name Address Date of birth City User id Password Re-password E-mail id
Constraints
26
Tel_no income
Varchar2 Varchar2
Numbe r Numbe r
Telephone number Phone number
USER INTERFACE
Home page
27
THIS IS HOME PAGE WHICH CONTAINS ALL THE LINKS TO FURTHER PAGES.WE CAN LOGIN TO IT BY FILLING THE LOGIN PANNEL.
ADMIN CREATE EMPLOYEE ACCOUNT
28
THIS IS THE PAGE FOR THE CREATION OF EMPLOYEE ACCOUNT BY ADMIN. IT CONTAINS COLUMN LIKE PERSONAL INFORMATION (FIRST NAME, LAST NAME, ADDRESS, CITY ETC).
ADMIN CREATE USER ACCOUNT
29
THIS IS THE PAGE FOR THE CREATION OF USER ACCOUNT BY ADMINISTRATOR .IT CONTAINS COLUMN LIKE PERSONAL INFORMATION (FIRST NAME, LAST NAME, DOB , CITY ETC).
LOGIN BY CUSTOMER
30
THIS IS LOGIN PAGE BY CUSTOMER. AFTER LOGIN CUSTOMER CAN SEE VARIOUS TERMS AND CONDITIONS OF BANK AND ALSO THE LOAN INFORMATION.
LOGIN BY EMPLOYEE
31
THIS IS EMPLOYEE LOGIN PAGE. AFTER LOGIN AN EMPLOYEE CAN ACCESS INFORMATION REGARDING THE TERMS AND CONDITIONS OF BANK.
LOGIN BY ADMINISTRATOR
32
THIS IS ADMINISTRATOR LOGIN PAGE.AFTER LOGIN ADMINISTRATOR CAN MAKE ANY MODIFICATIONS WHERE EVER AND WHENEVER REQUIRED.
CRITERIA FOR CHANGING PASSWORD
33
THIS PAGE IS FOR CHANGING THE PASSWORD OF ACCOUNT.ONE CAN EASILY CHANGE HIS/HER PASSWORD BY FILLING THIS FORM WITH PROPER DETAILS.
34
CUSTOMER CHEQUE BOOK REQUEST
THIS IS THE PAGE FOR CUSTOMER CHEQUE BOOK REQUEST .IT CONTAINS COLUMNS LIKE ACCOUNT TYPE, USER ID ,BRANCH NAME, NAME.
35
CREATE EMPLOYEE ACCOUNT
THIS IS THE PAGE FOR THE CREATION OF EMPLOYEE ACCOUNT CONTAINING COLUMNS LIKE :FIRST NAME, LAST NAME, CITY, DOB ETC.
36
CHAPTER 3 CODING
37
ADMIN ACCOUNT INFORMATION
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true;
38
} protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
39
EMPLOYEE CHANGE PASSWORD
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; }
40
protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e)
41
{ GridView5.Visible = true; } }
ADMIN CHANGE PASSWORD OF CUSTOMER
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; }
42
protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e)
43
{ GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN CHANGE PASSWORD OF EMPLOYEE
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); }
44
protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) {
45
GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN CREATE CUSTOMER
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e)
46
{ Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) {
47
} protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN CREATE USER
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
48
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) {
49
Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN HOMEPAGE
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;
50
using System.Data.SqlClient; public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; }
51
protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN MODIFY ACCOUNT
using System; using System.Data; using System.Configuration;
52
using using using using using using using using
System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx");
53
} protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN MODIFY USER ACCONT
54
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true;
55
} protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
56
CUSTOMER HOMEPAGE
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; }
57
protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e)
58
{ GridView5.Visible = true; } }
EMPLOYEE CHANGE PASSWORD
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info. aspx"); }
59
protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info. aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc. aspx"); }
60
protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
EMPLOYEE CHEQUEBOOK REQUEST
using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security;
61
using using using using using
System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e)
62
{ GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
EMPLOYEE HOMEPAGE
using System; using System.Data;
63
using using using using using using using using using
System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Home_Sign_page : System.Web.UI.Page { SqlConnection con; protected void Page_Load(object sender, EventArgs e) { Literal1.Text = Session["Emp_id"].ToString() ; //Response.Write("
1
This system provides the basic services to manage bank accounts at a bank called ABC Bank. ABC Bank has many branches, each of which has an address and branch number. A client opens accounts at a branch. Each account is uniquely identified by an account number; it has a balance and a credit or overdraft limit. There are many types of accounts, including: A mortgage account (which has a property as collateral), a chequing account, and a credit card account (which has an expiry date and can have secondary cards attached to it). It is possible to have a joint account (e.g. for a husband and wife). Each type of account has a particular interest rate, a monthly fee and a specific set of privileges (e.g. ability to write cheques, insurance for purchases etc. ABC Bank is divided into divisions and subdivisions (such as Planning, Investments and Consumer), the branches are considered subdivisions of the Consumer Division. Each division has a manager and a set of other employees. Each customer is assigned a particular employee as his or her ‘personal banker’.a This is a project on the banking management system .It includes the forms, the interfaces and all the work included in the efficient tasks to be performed in a bank, This is not as secure to be included in the actual implementation in a bank but would contain all the basic features, it is built on the work as included with an example from the prestigious UCO bank. The major parts of this project include the login forms, transaction details, crystal reports etc. The system developed should calculate interest for each account having balance more than zero at the correct interest rate. This interest calculated will be stored in a table which can be updated. The balance on which interest is calculated can change because the customer may deposit or withdraw money.
2
Every month the cumulative interest calculated will be credited to the customer. After this point of time the cumulative interest stored should be set to zero because the customer has benefited for the period specified. 3 different accounts viz. the savings ,fixed deposit or loan account will be created. Sanction for cheques, drafts, pay orders etc also to be included.
OBJECTIVES OF BANK RESERVATION SYSTEM
1) All the transaction details. 2) Loan details included for different types of loans. 3) Different special services like sale of forms like MBA entrance exams can be included. 4) Features for the insurance, loan against fixed deposit etc. can be included. 5) A website restore can also be made for the bank’s special requests using asp.net with c#.net or asp.net with vb.net.
3
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)
To solve actual problems in a software project setting, a software engineer or a team of engineers must incorporate a development strategy that includes methods, tools and procedures. this strategy is referred to as a process model or a software development life cycle. There are several such cycles available. Which SDLC is more suitable depends on lot of factors such as: 1. Nature of the project 2. Type of applications 3. Tools proposed to be used 4. Kind of controls and documentation required Code And Fix Life Cycle Model As the name suggests, this model uses an ad hoc approach for the software designing. A very casual study is followed by coding. The issues regarding specification or design are never addressed. Instead, the developers simply build a product that is re-build again and again until the customer is satisfied. Limitations of code-and-fix cycle model This approach may work well for small systems but is very unsatisfactory for larger systems. As the code size increases, the understandability and maintainability of the system decreases.
4
Methodology adopted
The Waterfall Model/Linear Sequential Life Cycle Model We have used classic life cycle methodology, which is best known as waterfall model to develop my project. We performed the phase in the order possibly with some over lap, and with little or no iteration.
Feasibility Study
Hardware Evaluation & Acquisition
Analysis
Design
Development
Implementation
Maintenance
5
The simplest, oldest and most widely used process model for software designing is the waterfall model. It was proposed by Royce in 1970. The essence of this software paradigm is that the process of software designing consists of linear set of distinct phases. These phases are:
Stage1: Feasibility Study
The goal of feasibility study is to evaluate alternative systems and to purpose the most feasible and desirable system for designing. Five types of feasibility are addressed in this study. TECHNICAL FEASIBILITY ECONOMIC FEASIBILITY MOTIVATIONAL FEASIBILITY SCHEDULE FEASIBILITY OPERATIONAL FEASIBILTY
Stage2: Requirement Analysis and Specification
The goal of this phase is to understand the exact requirements of the customers and to document them properly. This activity is usually executed together with the customers, as the goal is to document all functions, performance and interfacing requirements for the software designing and management. The requirements describe “what” of a system. This phase produces a large document containing a description of what the system will
6
do without describing how it will be done. This document is known as software requirement specification (SRS) document.
Stage3: Design
The goal of this phase is to transform the requirement specification produced in the requirement analysis phase into a structure that is suitable for implementation in some programming language, Here, overall software architecture is defined, and the product design and detailed design work is performed. This work is documented and is known as software design description (SDD document).
Stage4: Coding and Unit Testing
The information contained in SDD is sufficient to begin the coding Phase. The coding Phase of software designing involves translation of design specification into a machine readable form. If design is performed in a detailed manner, code generation can be accomplished easily. This phase is also known as the implementation phase. Here, each component of the design is implemented as a program module, and each of these program modules is unit tested. The purpose of unit testing is to determine the correct working of individual modules.
Stage5: Integration and System Testing:
7
During this phase the different program modules are integrated in a planned way and then tested as a completed system to ensure that the designed system functions according to its requirements as specified in the SRS document. After testing, the software is delivered to the customer.
Stage6: Software Maintenance
This is the last phase of software designing which includes a broad set of activities such as error correction, enhancement of capabilities, deletion of ob Advantages 1. Simple and easy to use 2. The phase of the model are processed and completed one at a time. 3. Works very well for smaller software projects. Disadvantages 1.It is often difficult for the customer to state all the requirements. 2. The customer must have patience, as the product is delivered very late in this software process. 3. The model is not suitable for long time software projects.
8
CHAPTER-1 SYSTEM ANALYSIS
1.1 1.2 1.3 1.4 1.4.1 1.4.2
1.4.3
Problem Definition Required Analysis H/W, S/W analysis Feasibility Study Operational Feasibility Economical Feasibility Technical Feasibility
9
1.1 Problem Definition
In this project we have analysed all the aspect of a reservation system between a customer and banking reservation and I have analyzed all the problem faced by customer because I thought on behalf of a customer or thought as a customer what types of doubt & problem faced by customer when he needs to reserve an account so I have tried to solve that doubt and creating transparency between bank processing by a customer and I tried to give the facility to save time and efforts to reserve ticket which is single click away from the reach of customer using advance tools & technology. It is quite enough to start a idea in which I can develop the proposed solution and that problem has to be solved using latest advance tools and technologies. The problem definition describe only the preliminary requirement but as we start system to develop many requirements arises.
10
1.2 Required analysis (SRS)
SOFTWARE REQUIREMENT SPECIFICATION
The software requirement specification (SRS) is very important part of the software building process, which describes the actual user level requirement from technical point of view. I.e. what the user exactly wants? The objective of preparing the software requirement specification is to represent the requirements of the software in such a manner that ultimately leads to successful software implementation. It is the result of the analysis process of the software development. It should contain all the data the software is going to process, the function it will provide, and the behavior it will exhibit.
11
This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE Recommended Practice for Software Requirements Specifications The SRS provides the following functionality:The SRS provides the following functionality:Introduction of the software: - It specifies the goals and objectives of the software. Information description: - It provides the detailed description of the problem that the software must solve. SRS for the ongoing project Problems faced by the passengers 1. Insufficient time 2. reservation problem 3. cost of amount realization 4. Not aware to all the information about different loan terms
12
1.3 HARDWARE , SOFTWARE ANALYSIS
SOFTWARE REQUIREMENTS:
The operating system Framework Front-end tool Editing tool Interface Back-end tool
: Windows 2009 professional/XP : .NET FRAMEWORK 2.0 : ASP.NET with C#.NET : VISUAL STUDIO 2005 : HTML , Stylesheet : SQL Server 2005.
HARDWARE REQUIREMENTS:
Processor/above Memory Modem Network Adapter Secondary Storage
: INTEL PENTIUM-1V , 2.4 GHz : 256 MB,DDR RAM : 56 KBPS voice Fax Data : Ethernet Adapter : HARD DISK 512 MB
13
1.4 FEASIBILITY STUDY
1.4.1 OPERATIONAL FEASIBILITY
It is mainly related to human organizational and political aspects the points to be considered are: *what changes will be brought with the system? *what organizational structures are distributed? *what new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? Generally project will not be rejected simply because of operational infeasibility but such considerations are likely to critically affect the natural and scope of the eventual recommendations. For operational feasibility study we appointed a small group of people who are familier with information system techniques, who understands the parts of the business that are relevant to the project and are skilled in system analysis and design process.
1.4.2 ECONOMICAL FEASIBILITY
14
A financial benefit must exceed the cost of developing that system. i.e. a new system being developed should be a good investment for the organization. Economic feasibility considers the following:The cost if nothing changes (i.e. The proposed system is developed). The proposed “WEB BASED COURSE REGISTRATION ” is economically feasible because :
*The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and man power spent in running the system. *The system requires very less time factors. *The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and man power spent in running the system. *The system will have GUI interface and very less user-training is required to learn it. *The system requires very less time factors. *The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and man power spent in running the system. *The system will have GUI interface and very less user-training is required to learn it.
15
1.4.3 TECHNICAL FEASIBILTY
Technical feasibility centers around the existing computer system (hardware and software) whether it can support the addition of proposed system, if not to what extend it can support the organization’s capacity to acquire required additional components.
Proposed system is technically feasible because of the following reasons:. * Expandability will be maintained in the new system. New modules can be added later on the application, if required in the future. * The application will have User-friendly Forms and Screens, all validation checks. So the new system guarantees accuracy, reliability, ease of access and data security.
16
CHAPTER-2 SYSTEM DESIGN
2.1 ER-Diagram 2.2 DFD 2.3 Database Design 2.4 User Interface Design
17
2.1
Admin_ addres s
ER DIAGRAM
Admin_tel_ no
Admin_id
Admin_fi rst_nam e
Administrat or
Admin_city
manag es
Can see details
Employee
control s Emp_tel_n o Emp_pass word
custome r Cust_i d Cust_do b Cust_fir st_nam e
Emp_i d
Emp_fir st_nam e
issu e loan Laon_dat e Loan_id Loan_amt
18
2.2
DATA FLOW DIAGRAM (DFD)
0 LEVEL DFD
EMPLOYEE
*CHANGE PASSWORD *LOAN *VIEW INFO *CHEQUE BOOK REQUEST
ADMINISTRATOR *VIEW INFO
BANKING
*CHANFE PASS OF CUST/EMP *DELETE CUST/EMP *LOAN INFO *CHANGE PASSWORD
CUSTOMER *CHANGE PASSWORD * LOAN *VIEW INFO *CHEQUE BOOK
19
1 LEVEL DFD
CHEQUE BOOK LOAN
LOGIN
CUSTOMER
CUST A/C MGNT EMPLOYEE VIEW INFO
ADMINISTRATOR
VIEW INFO
MANAGE CUST/EMP
CHANGE PASSWORD
ADMIN
CUST
EMP
A/C MANAGEMENT
20
2.3 DATABASE DESIGN
Introduction: The design is the process of designing exactly how the specifications are to be implemented. It defines specifically how the software is to be written including an object model with properties and method for each object, the client/server technology, the number of tiers needed for the package architecture and a detailed database design. Analysis and design are very important in the whole development cycle. Any glitch in the design could be very expensive to solve in the later stage of the software development.
Basic Modules:
In Our Project with the help of ‘Divide and Conquer theory’ we can divide overall program in 6 modules.
21
1) ADMINISTRATOR TABLE Administrator Table
Attribute First_name Last_name Address Dob City User_id1 Password Re-password Email_id Tel_no Phn_no
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2
Size 30 30 60 20 25 20 30 30 25 Numbe r Numbe r
Description Name of administrator Last name Address Date of birth City User id Password Re-password E-mail id Telephone number Phone number
Constraints
Primary Key
22
2) CUSTOMER TABLE Customer Table
Attribute First_name Last_name Address Dob City User_id1 Password Re-password Email_id Tel_no
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2
Size 30 30 60 20 25 20 30 30 25 Numbe r
Description Name of administrator Last name Address Date of birth City User id Password Re-password E-mail id Telephone number
Constraints
Primary Key
3) CUSTOMER CHEQUE BOOK TABLE
23
Customer Cheque Book Table
Attribute Acct_type Acct_id Branch_name Name No_page
Data Type Varchar2 Varchar2 Varchar2 Number Number
Size 30 30 60 30 40
Description Name of administrator Last name Address Date of birth City
Constraints
4) EMPLOYEE TABLE
24
Employee Table
Attribute First_name Last_name Attribute Address Acct_type Dob Acct_id City Branch_name User_id1 Name Password No_page Re-password Contact_no Email_id address Tel_no Phn_no
Data Type Varchar2
Employee Cheque Book Table
30 Name of administrator Last name Description Address Name of administrator Date of birth Last name City Address User id Date of birth Password City Re-password Contact number E-mail id Address Telephone number Phone number 30 Size 60 30 20 30 25 60 20 30 30 40 30 20 25 40 Numbe r Numbe r
Size
Description
Constraints
Varchar2 Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Varchar2 Number Varchar2 Number Varchar2 Varchar2 Varchar2 Varchar2
Constraints
Primary Key
5) EMPLOYEE CHEQUE BOOK TABLE
25
6) LOAN TABLE
Loan Table
Attribute First_name Last_name Address Dob City User_id1 Loan_amt No_install Downpay
Data Type Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2
Size 30 30 60 20 25 20 30 30 25
Description Name of administrator Last name Address Date of birth City User id Password Re-password E-mail id
Constraints
26
Tel_no income
Varchar2 Varchar2
Numbe r Numbe r
Telephone number Phone number
USER INTERFACE
Home page
27
THIS IS HOME PAGE WHICH CONTAINS ALL THE LINKS TO FURTHER PAGES.WE CAN LOGIN TO IT BY FILLING THE LOGIN PANNEL.
ADMIN CREATE EMPLOYEE ACCOUNT
28
THIS IS THE PAGE FOR THE CREATION OF EMPLOYEE ACCOUNT BY ADMIN. IT CONTAINS COLUMN LIKE PERSONAL INFORMATION (FIRST NAME, LAST NAME, ADDRESS, CITY ETC).
ADMIN CREATE USER ACCOUNT
29
THIS IS THE PAGE FOR THE CREATION OF USER ACCOUNT BY ADMINISTRATOR .IT CONTAINS COLUMN LIKE PERSONAL INFORMATION (FIRST NAME, LAST NAME, DOB , CITY ETC).
LOGIN BY CUSTOMER
30
THIS IS LOGIN PAGE BY CUSTOMER. AFTER LOGIN CUSTOMER CAN SEE VARIOUS TERMS AND CONDITIONS OF BANK AND ALSO THE LOAN INFORMATION.
LOGIN BY EMPLOYEE
31
THIS IS EMPLOYEE LOGIN PAGE. AFTER LOGIN AN EMPLOYEE CAN ACCESS INFORMATION REGARDING THE TERMS AND CONDITIONS OF BANK.
LOGIN BY ADMINISTRATOR
32
THIS IS ADMINISTRATOR LOGIN PAGE.AFTER LOGIN ADMINISTRATOR CAN MAKE ANY MODIFICATIONS WHERE EVER AND WHENEVER REQUIRED.
CRITERIA FOR CHANGING PASSWORD
33
THIS PAGE IS FOR CHANGING THE PASSWORD OF ACCOUNT.ONE CAN EASILY CHANGE HIS/HER PASSWORD BY FILLING THIS FORM WITH PROPER DETAILS.
34
CUSTOMER CHEQUE BOOK REQUEST
THIS IS THE PAGE FOR CUSTOMER CHEQUE BOOK REQUEST .IT CONTAINS COLUMNS LIKE ACCOUNT TYPE, USER ID ,BRANCH NAME, NAME.
35
CREATE EMPLOYEE ACCOUNT
THIS IS THE PAGE FOR THE CREATION OF EMPLOYEE ACCOUNT CONTAINING COLUMNS LIKE :FIRST NAME, LAST NAME, CITY, DOB ETC.
36
CHAPTER 3 CODING
37
ADMIN ACCOUNT INFORMATION
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true;
38
} protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
39
EMPLOYEE CHANGE PASSWORD
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; }
40
protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e)
41
{ GridView5.Visible = true; } }
ADMIN CHANGE PASSWORD OF CUSTOMER
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; }
42
protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e)
43
{ GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN CHANGE PASSWORD OF EMPLOYEE
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); }
44
protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) {
45
GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN CREATE CUSTOMER
using using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e)
46
{ Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) {
47
} protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN CREATE USER
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
48
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) {
49
Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN HOMEPAGE
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;
50
using System.Data.SqlClient; public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; }
51
protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN MODIFY ACCOUNT
using System; using System.Data; using System.Configuration;
52
using using using using using using using using
System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx");
53
} protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
ADMIN MODIFY USER ACCONT
54
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true;
55
} protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
56
CUSTOMER HOMEPAGE
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; }
57
protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e)
58
{ GridView5.Visible = true; } }
EMPLOYEE CHANGE PASSWORD
using using using using using using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info. aspx"); }
59
protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info. aspx"); } protected void Button1_Click1(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc. aspx"); }
60
protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
EMPLOYEE CHEQUEBOOK REQUEST
using using using using using using
System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security;
61
using using using using using
System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info : System.Web.UI.Page { protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button2_Click(object sender, EventArgs e) { GridView1.Visible = true; } protected void Button3_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button5_Click(object sender, EventArgs e) { GridView2.Visible = true; } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_Acc_Info.aspx"); } protected void Button1_Click1(object sender, EventArgs e)
62
{ GridView1.Visible = true; } protected void Button2_Click1(object sender, EventArgs e) { Response.Redirect("~/admin/Mod_User_Acc.aspx"); } protected void Page_Load(object sender, EventArgs e) { } protected void Button3_Click1(object sender, EventArgs e) { GridView3.Visible = true; } protected void Button4_Click(object sender, EventArgs e) { GridView4.Visible = true; } protected void Button7_Click(object sender, EventArgs e) { GridView5.Visible = true; } }
EMPLOYEE HOMEPAGE
using System; using System.Data;
63
using using using using using using using using using
System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;
public partial class Home_Sign_page : System.Web.UI.Page { SqlConnection con; protected void Page_Load(object sender, EventArgs e) { Literal1.Text = Session["Emp_id"].ToString() ; //Response.Write("
Employee"); con = new SqlConnection("server=localhost;Integrated Security=true ;database=delhi"); SqlDataAdapter objadapter = new SqlDataAdapter("select first_name ,last_name,address,city,dob ,user_id1,email_id from Employee Where user_id1='"+Literal1.Text+"' ", con); DataSet objset = new DataSet(); objadapter.Fill(objset, "employee"); DataView objview = new DataView(objset.Tables["employee"]); // objview.RowFilter = "std_id