Get documents about "INTRODUCTION TO BANK RESERVATION SYSTEM
Document Sample
INTRODUCTION TO BANK RESERVATION SYSTEM
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.
Every month the cumulative interest calculated will be credited to the
customer. After this point of time the cumulative interest stored
1
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.
2
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.
3
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
4
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
do without describing how it will be done. This document is known as
software requirement specification (SRS) document.
5
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:
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.
6
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.
7
CHAPTER-1
SYSTEM ANALYSIS
1.1 Problem Definition
1.2 Required Analysis
1.3 H/W, S/W analysis
1.4 Feasibility Study
1.4.1 Operational Feasibility
1.4.2 Economical Feasibility
1.4.3 Technical Feasibility
8
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.
9
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.
10
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
11
1.3 HARDWARE , SOFTWARE ANALYSIS
SOFTWARE REQUIREMENTS:
The operating system : Windows 2009 professional/XP
Framework : .NET FRAMEWORK 2.0
Front-end tool : ASP.NET with C#.NET
Editing tool : VISUAL STUDIO 2005
Interface : HTML , Stylesheet
Back-end tool : SQL Server 2005.
HARDWARE REQUIREMENTS:
Processor/above : INTEL PENTIUM-1V , 2.4 GHz
Memory : 256 MB,DDR RAM
Modem : 56 KBPS voice Fax Data
Network Adapter : Ethernet Adapter
Secondary Storage : HARD DISK 512 MB
12
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.
13
1.4.2 ECONOMICAL FEASIBILITY
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.
14
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.
15
CHAPTER-2
SYSTEM DESIGN
2.1 ER-Diagram
2.2 DFD
2.3 Database Design
2.4 User Interface Design
16
2.1 ER DIAGRAM
Admin_ad Admin_id Admin_tel_no
dress
Admin_first Admin_city
_name Administrator
Can see
manages details
customer
Employee controls
Cust_id
Cust_dob
Emp_tel_no
Emp_id
Cust_first
Emp_passwo
_name
rd
Emp_first
_name
issue
loan
Laon_date
Loan_id
Loan_amt
17
2.2 DATA FLOW DIAGRAM (DFD)
0 LEVEL DFD
ADMINISTRATOR
EMPLOYEE
*VIEW INFO
*CHANGE PASSWORD
*CHANFE PASS OF
*LOAN BANKING CUST/EMP
*VIEW INFO *DELETE CUST/EMP
*CHEQUE BOOK REQUEST *LOAN INFO
*CHANGE PASSWORD
CUSTOMER
*CHANGE PASSWORD
* LOAN
*VIEW INFO
*CHEQUE BOOK
18
1 LEVEL DFD
CHEQUE
BOOK
LOGIN CUSTOMER LOAN
CUST A/C MGNT
VIEW INFO
EMPLOYEE
ADMINISTRATOR VIEW INFO
MANAGE
CUST/EMP
CHANGE PASSWORD
ADMIN CUST EMP
A/C MANAGEMENT
19
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.
20
1) ADMINISTRATOR TABLE
Administrator Table
Attribute Data Type Size Description Constraints
First_name Varchar2 30 Name of administrator
Last_name Varchar2 30 Last name
Address Varchar2 60 Address
Dob Varchar2 20 Date of birth
City Varchar2 25 City
User_id1 Varchar2 20 User id Primary Key
Password Varchar2 30 Password
Re-password Varchar2 30 Re-password
Email_id Varchar2 25 E-mail id
Tel_no Varchar2 Number Telephone number
Phn_no Varchar2 Number Phone number
21
2) CUSTOMER TABLE
Customer Table
Attribute Data Type Size Description Constraints
First_name Varchar2 30 Name of administrator
Last_name Varchar2 30 Last name
Address Varchar2 60 Address
Dob Varchar2 20 Date of birth
City Varchar2 25 City
User_id1 Varchar2 20 User id Primary Key
Password Varchar2 30 Password
Re-password Varchar2 30 Re-password
Email_id Varchar2 25 E-mail id
Tel_no Varchar2 Number Telephone number
22
3) CUSTOMER CHEQUE BOOK TABLE
Customer Cheque Book Table
Attribute Data Type Size Description Constraints
Acct_type Varchar2 30 Name of administrator
Acct_id Varchar2 30 Last name
Branch_name Varchar2 60 Address
Name Number 30 Date of birth
No_page Number 40 City
23
4) EMPLOYEE TABLE
Employee Table
Attribute Data Type Size Description Constraints
First_name Varchar2 30 Name of administrator
Last_name Varchar2 30 Last name
Address Varchar2 60 Address
Dob Varchar2 20 Date of birth
City Varchar2 25 City
User_id1 Varchar2 20 User id Primary Key
Password Varchar2 30 Password
Re-password Varchar2 30 Re-password
Email_id Varchar2 25 E-mail id
Tel_no Varchar2 Number Telephone number
Phn_no Varchar2 Number Phone number
24
5) EMPLOYEE CHEQUE BOOK TABLE
Employee Cheque Book Table
Attribute Data Type Size Description Constraints
Acct_type Varchar2 30 Name of administrator
Acct_id Varchar2 30 Last name
Branch_name Varchar2 60 Address
Name Number 30 Date of birth
No_page Number 40 City
Contact_no Number 20 Contact number
address Varchar2 40 Address
25
6) LOAN TABLE
Loan Table
Attribute Data Type Size Description Constraints
First_name Varchar2 30 Name of administrator
Last_name Varchar2 30 Last name
Address Varchar2 60 Address
Dob Varchar2 20 Date of birth
City Varchar2 25 City
User_id1 Varchar2 20 User id
Loan_amt Varchar2 30 Password
No_install Varchar2 30 Re-password
Downpay Varchar2 25 E-mail id
Tel_no Varchar2 Number Telephone number
income Varchar2 Number Phone number
26
2.4 USER INTERFACE
Home page
THIS IS HOME PAGE WHICH CONTAINS ALL THE LINKS TO FURTHER
PAGES.WE CAN LOGIN TO IT BY FILLING THE LOGIN PANNEL.
27
ADMIN CREATE EMPLOYEE ACCOUNT
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).
28
ADMIN CREATE USER ACCOUNT
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).
29
LOGIN BY CUSTOMER
THIS IS LOGIN PAGE BY CUSTOMER. AFTER LOGIN CUSTOMER CAN SEE
VARIOUS TERMS AND CONDITIONS OF BANK AND ALSO THE LOAN
INFORMATION.
30
LOGIN BY EMPLOYEE
THIS IS EMPLOYEE LOGIN PAGE. AFTER LOGIN AN EMPLOYEE CAN ACCESS
INFORMATION REGARDING THE TERMS AND CONDITIONS OF BANK.
31
LOGIN BY ADMINISTRATOR
THIS IS ADMINISTRATOR LOGIN PAGE.AFTER LOGIN ADMINISTRATOR CAN
MAKE ANY MODIFICATIONS WHERE EVER AND WHENEVER REQUIRED.
CRITERIA FOR CHANGING PASSWORD
32
THIS PAGE IS FOR CHANGING THE PASSWORD OF ACCOUNT.ONE CAN
EASILY CHANGE HIS/HER PASSWORD BY FILLING THIS FORM WITH PROPER
DETAILS.
33
CUSTOMER CHEQUE BOOK REQUEST
THIS IS THE PAGE FOR CUSTOMER CHEQUE BOOK REQUEST .IT CONTAINS
COLUMNS LIKE ACCOUNT TYPE, USER ID ,BRANCH NAME, NAME.
34
CREATE EMPLOYEE ACCOUNT
THIS IS THE PAGE FOR THE CREATION OF EMPLOYEE
ACCOUNT CONTAINING COLUMNS LIKE :FIRST NAME, LAST NAME,
CITY, DOB ETC.
35
CHAPTER 3
CODING
36
ADMIN ACCOUNT INFORMATION
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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;
37
}
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;
}
}
38
EMPLOYEE CHANGE PASSWORD
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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;
}
39
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)
40
{
GridView5.Visible = true;
}
}
ADMIN CHANGE PASSWORD OF CUSTOMER
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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;
}
41
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)
42
{
GridView4.Visible = true;
}
protected void Button7_Click(object sender, EventArgs
e)
{
GridView5.Visible = true;
}
}
ADMIN CHANGE PASSWORD OF EMPLOYEE
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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");
}
43
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)
{
44
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 System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class Admin_Mod_Acc_Info :
System.Web.UI.Page
{
45
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)
{
Response.Redirect("~/admin/Mod_User_Acc.aspx");
}
protected void Page_Load(object sender, EventArgs e)
46
{
}
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 System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
47
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;
}
48
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 HOMEPAGE
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
49
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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)
{
50
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 ACCOUNT
using System;
51
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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)
52
{
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;
}
}
53
ADMIN MODIFY USER ACCONT
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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)
{
54
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)
{
GridView5.Visible = true;
}
55
}
CUSTOMER HOMEPAGE
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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;
56
}
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;
}
57
protected void Button7_Click(object sender, EventArgs
e)
{
GridView5.Visible = true;
}
}
EMPLOYEE CHANGE PASSWORD
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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"
);
58
}
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)
{
59
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 CHEQUEBOOK REQUEST
using System;
60
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
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)
61
{
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;
}
}
62
EMPLOYEE HOMEPAGE
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using 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("<center><b><u>Employee</center></
b></u>");
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");
63
DataView objview = new
DataView(objset.Tables["employee"]);
// objview.RowFilter = "std_id <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
64
EMPLOYEE LOAN PAGE
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using 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("<center><b><u>Employee</center></
b></u>");
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");
65
DataView objview = new
DataView(objset.Tables["employee"]);
// objview.RowFilter = "std_id <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
EMPLOYEE REGISTRATION
using System;
using System.Data;
using System.Configuration;
using System.Collections;
66
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using 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("<center><b><u>Employee</center></
b></u>");
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 <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
67
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
HOMEPAGE
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
68
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("<center><b><u>Employee</center></
b></u>");
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 <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
69
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
USER CHANGE PASSWORD
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using 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("<center><b><u>Employee</center></
b></u>");
70
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 <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
71
USER CHEQUE BOOK REQUEST
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using 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("<center><b><u>Employee</center></
b></u>");
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");
72
DataView objview = new
DataView(objset.Tables["employee"]);
// objview.RowFilter = "std_id <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
USING SYSTEM
using System;
using System.Data;
using System.Configuration;
using System.Collections;
73
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using 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("<center><b><u>Employee</center></
b></u>");
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 <18";
// objview.Sort = " std_name" ;
// GridView1.DataSource = objset;
74
GridView1.DataSource = objview;
GridView1.DataBind();
}
protected void LinkButton1_Click(object sender,
EventArgs e)
{
}
protected void
GridView1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
75
CHAPTER-4
TESTING
76
Testing Approach
INTRODUCTION
Testing a program consists of providing the program with a set of test
inputs (or test cases) and observing if the program behaves as
expected. If the program fails to behave as expected, then the
conditions under which a failure occurs are noted for debugging and
correction.
Normally, while developing the code a software developer also
carries out some testing. This is known as Debugging. This
unearthing the defects that must be removed from the program.
Testing and debugging are two different processes. Testing is meant
for finding the existence of defects while debugging stands for
locating the place of errors and correcting the errors during the
process of testing .
TESTING GUIDELINES
The following are some guidelines were followed for testing:
* Test the modules thoroughly, cover all the access paths
* Generate enough data to create all the access paths arising from
conditions.
*Test the modules by deliberately processing/entering wrong data.
77
TESTING OBJECTIVES
The objective while testing our project are:
* To verify the interaction between objects.
* To verify the proper integration of all components of the software.
To verify that all requirements have been correctly implemented.
* To identify and ensure defects are addressed prior to the
deployment of the software.
The following are some guidelines were followed for testing:
* Test the modules thoroughly, cover all the access paths
* Generate enough data to create all the access paths arising from
conditions.
*Test the modules by deliberately processing/entering wrong data.
* Specifically create data for conditional statements.
* Test for locking by invoking multiple concurrent processes.
78
TESTING APPROACHES
Unit Testing
In unit testing analyst tests the program making up the system. For
this reason unit testing is sometimes called the program testing. Unit
testing give stress on modules independent of others, to find errors.
This helps the tester in detecting the error in coding and logic that are
contained within the module alone. The errors resulting from the
interaction between modules are initially avoided. Unit testing can be
performed from bottom up, starting with the smallest and lowest-level
modules and proceeding one at a time.
In this project each module is independently coded i.e. front end
pages and back-end logic are coded separately and testing (a low
level) is performed by the respective developers by themselves. All
the modules which are coded are independent with each other and
once it has been all completed them are linked together and further
integrated and functional testing is performed.
79
Integration Testing
It involves testing a set of functionally related software modules to
ensure integration of functionality and is derived from the design of
the software. The objective of integration testing is to ensure that
components link and work together, and the focus is on the
effectiveness of functional interactions and compatibility at the
interfaces of the components. Integration testing is carried out based
on the control flow of units, and their dependency. Large complex
products can go through many build-and-test cycles before they are
fully integrated.
Function Testing & System Testing
Unit and integration testing are more technical in nature and is
performed by technical specialists, who are close to the details of the
system while Functional & System Testing focuses on the
functionality of the system. Unit and integration testing is performed
earlier and on subsystems that may be much smaller than the entire
system, while Functional & System Testing tests the entire system
against the requirements and verifies all User Documentation is
correct. The results are analysed and Bug reports are generated for
discrepancies found during testing. The Project Manager, in
coordination with the Test Leader, analyses all Bug reports and
determines which ones must be recycled to the software developer
before re-testing. Conceptually, Functional & System Testing
requirements are based upon the Use Case models, Business
models, SRS.
80
Before a system can be released for general use or even beta
testing, it must pass a series of tests. These tests are specifically
designed to discover errors or bugs, which may have been over
looked in the design or implementation stages. They are also
essential tool for determining whether the system meets the Software
Requirements Specifications. Potential testing strategies techniques
used are :
the black box testing
the white box testing
Black box testing
Takes an external perspective of the test object to derive test cases.
These tests can be functional or non-functional, though usually
functional. The test designer selects valid and invalid input and
determines the correct output. There is no knowledge of the test
object's internal structure.
This method of test design is applicable to all levels of software
testing: unit, integration, functional testing, system and acceptance.
The higher the level, and hence the bigger and more complex the
box, the more one is forced to use black box testing to simplify. While
this method can uncover unimplemented parts of the specification,
one cannot be sure that all existent paths are tested.
It has the following feature
1. Exercise all logical decisions on their true and false sides.
2. Execute all loops at their boundaries and within their operational
Bounds, and
3. Exercise internal data structures to ensure their validity.
White box testing is a test case design method that uses the
control structure of the procedural design to derive test cases. Test
81
cases can be derived that.
1. Exercise all logical decisions on their true and false sides.
2. Execute all loops at their boundaries and within their operational
bounds,and
3. Exercise internal data structures to ensure their validity.
With respect to our project testing of independent modules is
performed with all possible inputs. Various test cases of all the
modules used were developed to test for all possible errors and bugs.
On integrated various modules it is tested that links on all the pages
are properly open. Sessions are maintained on client login while
traversing from one page to another.
82
GENERIC ERROR PAGE
83
NO ACCESS
84
UPDATE ERROR
85
CONCLUSION
86
CONCLUSION
Software can use the latest technology which will arise in future
because it has been made after considering the change management
on projects and can modified very easily.
Software scope describes the data and control to be processed,
function performance, constraints, interfaces and reliability. Function
describes in the statement of scope are evaluated and in some case
refined to provide more detail prior to the beginning of the estimation.
Because both cost and schedule estimates are functionally oriented,
some degree of decomposition is often useful.
Software has been made using advance tools & technologies and
used advance feature so it easily changeable according to
requirement because
Data is not dependent to front end.
The basic idea behind this project to manage the relationship
between customer, suppliers and organization and their integration
on product processing.
We can implement easily this application. We can update it next
version. We can add new features as and when we require. There is
flexibility in all the modules. Scope of this document is to put down
the requirements, clearly identifying the information needed by the
user, the source of the information and outputs expected from the
system.
87
FUTURE SCOPE
AND
LIMITATIONS
88
FUTURE SCOPE
The name of the software is “BANKING RESERVATION SYSTEM”.
This software provides options for viewing different Facilities available
with different schemes and provides customers with the facility to
create an account, modify or update a particular account but it does
not provide the customers with details of cost of the account and it
does not allow the customer to modify a particular part of his account
and he/she can modify all his details.
89
LIMITATIONS
There are numerous examples of how the limited capabilities of the
current banking reservation systems affect the ability of bank to
realize full potential of revenue management. The issue on hand is
the availability , quality and stability of the problem data in electronic
form. The magnitude of this challenge changes from one account to
another depending on the sophistication of the banking reservation
system. Here are some limitations:
*Most reservations systems store only data on accepted created
account and do not store historical information about rejected
request.
*Some reservations do not carry point of issue account data with a
demanding request. This weakens the effectiveness of managing
revenue by distribution channel.
*Most reservations systems do not carry fare data with request.
* Some banking systems cannot control round request. All data is
one-way based. This makes it difficult to differentiate between one-
way and round demand of customer
90
BIBLIOGRAPY
91
9.1 ONLINE REFERENCES
Various references are used in developing the project.
* WORLD WIDE WEB
* PROFESSIONAL ASP.NET WITH C# WROX PUBLICATION.
* SQL SERVER 2005 (WROX).
* SOFTWARE ENGINEERING
* ADVANCE DATABASE MANAGEMENT SYSTEM
9.2 BOOK REFERENCES
* Jamie jaworsky “visual basic 6.0” techmedia
* Stefen denninger “visual basic 6.0” author‟s press
* Lan Somerville “software engineering”
* Rajiv mall “software engineering”
* Elmasri navathe “fundamentals of database system”
92
