Anda di halaman 1dari 60

1.

INTRODUCTION
1.1 PROJECT OVERVIEW
The project entitled as Banking System(Saving, Employee) mainly deals with
Banking for the System concept of customer and employee .This project has been
developed using VB.NET as front end tool and MS-Access as back end.
The modules included in this project are:
Login
Accounts
1.New Account
2.Deposit/Withdraw
3.View/Delete Account
Fixed Deposit
Recurring Deposit
Transaction
Services
1.Staff
2.Staff Member
Reports

ACCOUNTS

This module deals with customer details in the concern and the deposit of
the customer. This helps the concern to fetch the customer details easily.
The create accounts of the personal profile information as well as work
information is record here

FIXED DEPOSIT

This module deals with the Fixed Deposit Details though the customer
which they are provide from the deposit which instant to the customer for
valid Duration for a year which accomplished from the bank.

RECURRING DEPOSIT

This module deals with the Recurring Deposit Details though the customer
which they are provide from the deposit which instant to the customer for
valid Duration for a month which accomplished from the bank.

TRANSACTION

This module deals with the money transaction. From one account to another
account for the transaction

SERVICES

This module deals with for the services provider of a staff s and staff
member

REPORTS
This module deals with the report to retrieve information easily for the
user,user can view details according to them.
2

2.SYSTEM ANALYSIS
System Analysis by definition is a process of systematic investigation for
the purpose of gathering data, interpreting the facts, diagnosing the problem
and using this information to either build a completely new system or to
recommend the improvements to the existing system.
A satisfactory system analysis involves the process of examining a business
situation with the intent of improving it through better methods and procedures. In
its core sense, the analysis phase defines the requirements of the system and the
problems which user is trying to solve irrespective of how the requirements would
be accomplished.
There are 2 methods to perform System Requirement Analysis:
(i) Structured Analysis
Structured Analysis is an analysis method that provides a basis for developing a
model of software to be developed. The objective of structured analysis is to
identify the customer requirements and establish a basis to create a software
model

The components of a Structured Analysis are


Data Dictionary
Entity Relationship Diagram
Data Flow Diagram
Process Specification
Control Specification

(ii) Object Oriented Analysis


It refers to a detailed study of the various objects involved in a system and the relationship
of these objects with each other. While performing an object oriented analysis, the focus of
the system analyst is on the availability of the objects that are relevant to software
development.

Identification of Need
In current competitive scenario every business establishment needs

quality

processes to increase their efficiency as well as improve their productivity. It is of


vital importance that manual, time consuming & monotonous operations be
automated so as to streamline the working of an organization. In the current
4

business environment, there were lot of person who are searching for jobs. But
the main thing is the proper match for a job opportunity. So the main objective of
this project is to provide right type of job to right person. Since, the existing
system (manual work) takes more time and manpower for processing. Our
system will deal with all the aspects of jobsites starting from jobseeker
registration, providing him right type of jobs. Employer will send its requirement
and consultant search proper match for the job as per the employer requirement
and inform both the jobseeker and employer. So the main objective is to provide
right job to right person.
Preliminary Investigation
The basic purpose behind Preliminary Investigation is to first clarify,
understand and evaluate the Project Request.
Preliminary Investigation basically refers to the collection of
information that guides the management of an organization to evaluate the
merits and demerits of the project request and make an informed judgment
about the feasibility of the proposed system. This sort of investigation provides
us with a through picture of the kind of software and hardware requirements
which are most feasible for the system, plus the environment in which the
entire project has to be installed and made operational.

1) Reviewing the Documents provided by the Organization


They were quite effective in guiding us towards visualizing the
features that were needed to be put together in the system and the

required output which had to be generated once the system


became functional.
These specifications provided to us by the organization showed how the
new system should look like; it helped us in understanding the basic structure
of the application which we were supposed to develop.

2) On site Observation:
Another technique utilized by us to gain information about the project was
to visit the client site where the system had to be installed. Here a detailed
system study was carried out, checking the existing system to replicate it
with our system. We also observed the activities of the system directly.
During the on-site observation, we saw the office environment, work load of
the system and users, method of work, and the facilities provided by the
organization. This information helped us to understand how the system
should operate. But after interviewing the persons, who is affected by the
system, we got more details that further explain the project and shown
whether assistance is merited economically, operationally and technically.
Conducting Interviews:
This method of investigation conducted by us involved questioning
the concerned personnel to get the users (client) view about the
system and the features they desired it to have. Some of the Questions
put forward by our team were:
a) The amount of data needed to be stored.
b) The number of customers using the system and number of
which the application needed to be installed.
6

c) The issue of our application with existing system was widely


discussed.
d) The level of access given to the customer would depend on his
department.

2.1 EXISTING SYSTEM

Existing System refers to the system that is being followed till now. The
Existing System requires more computational time, more manual
calculations,
and the complexity involved in selection of features is high. After collecting
attendance from staff manually, the calculation
of average for each student was
also done manually. Then reports
were stored in papers and submitted to the
authorities.

Disadvantages of the existing system are :o


o
o
o
o

Manual work load.


A lot of time consumed.
Needs of lot of manpower.
Frequent occurrence of error.
Calculations are difficult

2.2 PROPOSED SYSTEM


The drawbacks, which are faced with the existing system configuration, can
be eradicated by using the proposed system. The main objective of the existing
system is to provide a userfriendly
interface. The system, which is
proposed, will be able to computerize all the details and will be able to provide
better readability.
FEATURES:
1.
2.
3.
4.
5.
6.

System become more user friendly


Equipped with better and powerful GUI
provide uniformity
Generates neat formatted report
Minimizes time and effort
Provide ease of access

NEED OF PROPOSED SYSTEM:

Large volumes of data can be performed with ease


Maintenance of file is flexible
Record stored and updated occasionally
Stored data can be edited as per needed

2.3 Feasibility Study


Feasibility study is the process of determination of whether or not a project is
worth doing. Feasibility studies are undertaken within tight time constraints and
normally culminate in a written and oral feasibility report. The contents and
recommendations of this feasibility study helped us as a sound basis for deciding
how to precede the project. It helped in taking decisions such as which software to
use, hardware combinations, etc.
The following is the process diagram for feasibility analysis. In the diagram, the
feasibility analysis starts with the user set of requirements. With this, the existing
system is also observed. The next step is to check for the deficiencies in the
existing system. By evaluating the above points a fresh idea is conceived to define
and quantify the required goals. The user consent is very important for the new
plan. Along with, for implementing the new system, the ability of the organization
is also checked. Besides that, a set of alternatives and their feasibility is also
considered in case of any failure in the proposed system. Thus, feasibility study is
an important part in software development.

WORKING CURRENT SYSTEM

USERS CONSESUS

DEFICIENCES IN
CURRENT SYSTEM

USER
STATED
REQUIREM ENTS

ANALYZE TO FIND
DEFICIENCES

DEFINE AND
QUANTIFY GOALS

REVISION BASED ON FEASIBILITY

CONSTRAINTS ON RESOURCES

EVALUATE
FEASIBILITY OF
ALTERNATES
PROPOSED FEASIBILITY
ALTERNATIVES

FIND BROAD
ALTERNATIVE
SOLUTION
ALTERNATIVES

(PROCESS DIAGRAM FOR FEASIBILITY ANALYSIS)


In the SDLC (Systems Development Life Cycle) of our project we maintained a
number of feasibility checkpoints between the two phases of the SDLC.
These checkpoints indicate that the management decision to be made after a
phase is complete.
The feasibility checkpoints in our project were as follows:
(i)

Survey phase checkpoint

(ii)

Study phase checkpoint

(iii)

Selection phase checkpoint

(iv)

Acquisition phase checkpoint

(v)

Design phase checkpoint

We conducted three tests for Project feasibility namely, Technical, Economical,


and Operational feasibilities
10

Technical Feasibility
Technical feasibility determines whether the work for the project can be done with
the existing equipment, software technology and available personnel. Technical
feasibility is concerned with specifying equipment and software that will satisfy
the user requirement.
This project is feasible on technical remarks also, as the proposed system is more
beneficiary in terms of having a sound proof system with new technical
components installed on the system. The proposed system can run on any machines
supporting Windows and Internet services and works on the best software and
hardware that had been used while designing the system so it would be feasible in
all technical terms of feasibility.
Technical Feasibility addresses three major issues:
Is the proposed Technology or Solution Practical?
The technologies used are matured enough so that they can be applied
to our problems. The practicality of the solution we have developed is proved
with the use of the technologies we have chosen. The technologies such as
ASP, IIS, VBscript and the compatible H/Ws are so familiar with the todays
knowledge based industry that anyone can easily be compatible to the
proposed environment.
Do we currently posses the necessary technology?
We first make sure that whether the required technologies are
available to us or nor. If they are available then we must ask if we have the
capacity. For instance, Will our current Printer be able to handle the new
reports and forms required of a new system?
11

Do we possess the necessary Technical Expertise and is the schedule


reasonable?
This consideration of technical feasibility is often forgotten during
feasibility analysis. We may have the technology, but that doesnt mean we
have the skills required to properly apply that technology.
As far as our project is concerned we have the necessary expertise so
that the proposed solution can be made feasible.
Some projects are initiated with specific deadlines. In our case first we
have given three months time but due to some problems regarding time and
the constraints of expertise it has been extended to six months. Now there are
some organizational constraints that have not yet given us the opportunity to
install the system.
Economical Feasibility
Economical feasibility determines whether there are sufficient benefits in
sufficient benefits in creating to make the cost acceptable, or is the cost of the
system too high. As this signifies cost-benefit analysis and savings. On the behalf
of the cost-benefit analysis, the proposed system is feasible and is economical
regarding its pre-assumed cost for making a system.
Economical feasibility has great importance as it can outweigh other
feasibilities because costs affect organization decisions. The concept of Economic
Feasibility deals with the fact that a system that can be developed and will be used
on installation must be profitable for the Organization. The cost to conduct a full

12

system investigation, the cost of hardware and software, the benefits in the form of
reduced expenditure are all discussed during the economic feasibility.
During the economical feasibility test we maintained the balance between the
Operational and Economical feasibilities, as the two were the conflicting. For
example the solution that provides the best operational impact for the end-users
may also be the most expensive and, therefore, the least economically feasible.
We classified the costs of ONLINE AUCTION according to the phase in
which they occur. As we know that the system development costs are usually onetime costs that will not recur after the project has been completed. For calculating
the Development costs we evaluated certain cost categories viz.
(i)

Personnel costs

(ii)

Computer usage

(iii)

Training

(iv)

Supply and equipments costs

(v)

Cost of any new computer equipments and software.

In order to test whether the Proposed System is cost-effective or not we


evaluated it through three techniques viz.
Payback analysis
Return on Investment:
Net Present value

Operational Feasibility
Operation feasibility is a measure of how people feel about the
system. Operational Feasibility criteria measure the urgency of the
problem or the acceptability of a solution. Operational Feasibility is
13

dependent upon determining human resources for the project. It


refers to projecting whether the system will operate and be used once
it is installed. If the ultimate users are comfortable with the present
system and they see no problem with its continuance, then resistance
to its operation will be zero.
Behaviorally also the proposed system is feasible. A particular application
may be technically and but may fail to produce the forecasted benefits, because the
company is not able to get it to work. For the system, it is not necessary that the
user must be a computer expert, but any computer operator given a little bit of
knowledge and training can easily operate.
Our Project is operationally feasible since there is no need for special
training of staff member and whatever little instructing on this system is required
can be done so quite easily and quickly as it is essentially This project is being
developed keeping in mind the general

people

who one have

very little

knowledge of computer operation, but can easily access their required database
and other related information. The redundancies can be decreased to a large extent
as the system will be fully automated.

14

2.4 HARDWARE SPECIFICATION


Processor

Intel Pentium i5

Speed

1.9GHz

Memory

2 GB RAM

Hard Disk Drive

500 GB

Keyboard Keys

107 Keys include 12 functions

2.5 SOFTWARE SPECIFICATION


Development Platform

Windows 7

Front-End Tool

VB .NET

Back-End Tool

Microsoft Access 2010

Documentation

Microsoft Word 2010

15

1. SYSTEM DESIGN
3.1 INPUT DESIGN
Input design is a part of overall design, which requires careful attribute.
Inaccurate input data are the most common cause of errors in data processing.
Errors entered by data entry operators can be controlled by input design. Input
design is the process of converting user-originated inputs to a computer- based
format. This input to the system is provided through VB.Net. The goal of
designing input data is to make data entry as easy, logical and free from errors.
In the system design phase input data are collected and organized in to groups of
similar data. The expanded data flow diagram logical data flows, data sources,
data stores and destination. Input design input data and source documents.
Source data are captured initially. A source document should be logical and easy
to understand. It should be clearly identified and should specify for the user
what to write and where to write it. Source data are input into the system using
input media and devices.
The input forms are

Registration
Home
New Account
Deposit/Withdraw
View/Delete Account
Fixed Deposit
Recurring Deposit
Transaction
Services

3.2 OUTPUT DESIGN

16

Computer output is the most important and direct source of information to


the user. Efficient, Intelligible output design improves the systems relationship
with the user and helps in decision-making. The output should be in such a way
that the user can see it from the screen and can take a hard copy from the printer.
To make a user- friendly output and for better communication the programmer
can use the features of a window. Efficient, Intelligence output design improves
the systems relationship with the user and help in decision-making. A major
form of the output is a hard copy from the printer. Printouts should be designed
around the output requirements of the user.
When designing the output, system analyst must accomplish the following:
Determine the information to present.
Decide whether to display, print, speak the information and select the
output medium.
Arrange the information in acceptable format.
Decide how to distribute the output to intended receipt
In this project the main important output screens are:
View the module details
Report

3.3DATABASE DESIGN
17

The next considration of the designer after designing the input and
output is file design or how data should be organized around user requirements.
How data are organized depends on the data and response requirements that
determine hardware configurations. An integrated approach to file design is the
database. The general theme behind a database is to handle information as an
integrated whole.
The overall objective in the development of database technology has been
to treat data as an organizational resource and as an integrated whole. Database
Management System allows data to be protected and organized separately from
other resources. Database is an integrated collection of data. This is the
difference between logical and physical data.
Database is a collection of inter-related data store together data with
controlled redundancy to serve one or more application. In a database
environment common data are available to the users. A program now requests
the data through database management system (DBMS), which determines the
data sharing. General objectives are to make information access easy, quick,
efficient, inexperience and flexible for the user. Several specific objectives are
ease of learning, data independence, integrity and recovery from failure, privacy
and security, performance.
In a database environment, Database Management System (DBMS) is the
software that provides the interface between the data file on disk and the
program that requires processing. Although all DBMSs have a common
approach to data management, they differ in the way they structure data. The
18

three types of data structure are hierarchical, network and relational. Here we
use relational structuring in which all data and relationships are represented in a
flat, two-dimensional table called a relation. A relation is equivalent to a file,
where each line represents a record. Each particular DBMS has unique
characteristics and general techniques for database design.
Data structuring is refined through a process called normalization. Data
are grouped in the simplest way possible so that later changes can be made with
a minimum of impact on the data structure.
NORMALIZATION
The process of normalization is concerned with the transformation of the
conceptual schema to a computer represent able form. Normalization reduces
the redundancies and anomalies.
The First Normal Form
First normal form does not allow multivalued and composite valued
attributes. It states that the domain of an attribute must include only atomic
values and that value of any attribute in a tuple must be single value from the
domain of that attribute.
The Second Normal Form
In second normal form, for relation where primary key contains multiple
attributes, non-key attribute should not be functionally dependent on a part of
the primary key.

19

The Third Normal Form


In third normal form, relation should not have a non-key attribute
functionally determined by another nonkey attribute. That is there should be no
transitive dependency of a non-key attribute on the primary key.

3.4 CODE DESIGN


Principles of code design

The main purpose of code design is to simplify the coding and achieve
better performance. Coding is done in such a way that it could be maintained
and easily modified.
The statements used in the coding are selected in such a way that they
perform the task specified and also reducing the memory space thereby
increasing the speed of the system.
Coding is done in a simple way that non-programmers can easily
understand by providing internal documents now and there in a program.
Characteristics of good code
Uniqueness
Meaningfulness
Stability
Uniform size and format
Simplicity
Efficiency

Conciseness

20

4. SYSTEM TESTING
Testing is an activity to verify that a correct system is being built and is being
build and is performed with the intent of finding faults in the system. Testing is an
activity, however not restricted to being performed after the development phase is
complete. Testing results, once gathered and evaluated, provide a qualitative
induction of software quality and serve as basis for design modification if required
a project is set to be incomplete without proper testing.
System testing is a process of checking whether the development system
is working according to the original objectives and requirements. Software
testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding.
TESTING OBJECTIVES
All testing objectives are summarized in the following three steps:
Testing is the process of executing a program with the intent of finding
error.
A good test case is one that as high probability of finding on as yet
undiscovered.
A successful test is one that uncovers an as yet undiscovered error.

21

TESTING PRINIPLES
All tests are traceable to customer requirements. Test should be planned
long before testing begins, that is, the planning can begin as soon as the
requirements model is complete. Testing should begin in the small and
progress towards testing in the large. The focus testing will shift progressively
from programs, to integer modules and finally to the entire project. Exhaustive
testing is not possible. To be are effective, testing should be one, which has
highest probability of finding errors.

THE FOLLOWING ARE THE ATTRIBUTES OF GOOD TEST


A good test has a high of finding an error.
A good is not redundant.
A good test should be best of breed.
A good should be neither too simple nor too complex.

WHITE-BOX TESTING
White-box testing is a test case design method that uses the control
structure of the procedural design to derive test cases. White-box testing of

22

software is predicted on close examination of procedural detail. The White-box


testing is successfully conducted in BANKING SYSTEM.

BLACK-BOX TESTING
The black-box testing focuses on the functional requirements of the software. It
helps to find out errors in incorrect or missing functions, interface errors, errors
in data structures, performance errors and initialization and termination errors.
The black-box testing is applied during the later stages for the functional
requirement evaluation. The Black-box testing is successfully conducted in
BANKING SYSTEM.
UNIT TESTING
Unit testing is carried out verify and uncover error within the boundary of
the smallest unit or a module. In this testing step, each module was found to be
working satisfactory as per the expected output of the module.
In the packages development, each module is tested separately after it has
been completed and checked with valid data; Unit testing exercise specific path
in the modules control structure to ensure complete coverage and maximum
error detection. The unit testing successfully conducted in BANKING
SYSTEM.
INTEGRATION TESTING
Integration testing address the issues associated with the dual problems of
verification and program construction. After the software has been integrated a
23

set of high-order test are conducted. The main objective in that testing process is
to take unit tested modules and build a program structure that has been dictated
by design. The integration testing is successfully conducted in BANKING
SYSTEM.

24

5. SYSTEM IMPLEMENTATION & MAINTENANCE


System implementation is the stage of the project where the theoretical
design is turned in to a working system. If the implementation stage is not
properly planned and controlled it can chaos. It can be considered to be most
crucial stage in achieving a new successful system and giving the users
confident that the new system will work and be effective and accurate. It is less
creative than system design.
Implementation primarily concerned with user training and documentation.
Depending on the nature of the system extensive users training may be required.
Conversion usually takes place about the same time the user is being trained or
later. Implementation simply means converting a new system design into
operation. An important aspect of system analysts job is to make sure that the
new design is implemented to establish standards. Implementation means the
process of converting a new revised system design into an operational one.
At the beginning of the development phase, a preliminary implementation
plan is created to schedule and manage the many different activities that must be
integrated into plan. The implementation plan updated throughout the
development phase, culminating in a changeover for the operation phase. The
major elements of the implementation plan are test plan, training plan,
equipment installation plan and a conversion plan.
Implementation of a new computer system to replace an
existing one.

25

Implementation of modified application to replace an


existing one.
Implementation of a computer system to replace a
manual.

A software application in general is implemented after navigating the


complete life cycle method of a project. Various life cycle processes such as
requirement analysis, design phase, verification, testing and finally followed by
the implementation phase results in a successful project management. The
software application has been successfully implemented after passing various
life cycle processes mentioned above.

26

6. SCOPE FOR FURTHER ENHANCEMENT


The BANKING SYSTEM(SAVING,EMPLOYEE) Software has
been developed in such way that it accepted modification and further
changes.The Software is very friendly any changes be done easily.
The software restructuring is carried out. Software restructuring
modifies source code in an effort to make it amenable to future changes In
general, restructuring does not modify the overall program architecture. It tends
to focus on design details of individual modules and on local data structure
defined within modules

27

7. CONCLUSION

This project was completed within time span allotted. I am very satisfied to
get this opportunity to do this project. All the knowledge I gained is full applied
in the design of the mentioned system and application packages is developer. All
the suggestions forwarded in the software proposal have been completed. This
system is developed in such a way that the modules developed in future can be
linked easily to the system, without affecting the existing system, since it
provides a hierarchical structure.
Top down programming approach has been adopted while developing the
project; each task is divided into separate modules. Hence, modification and
enhancement can be easily made without affecting any other part of the
program. This system has been developed to satisfy the needs of the customer.
The entire system is user-friendly and interactive. The performance of the
system is provided efficiently.
28

Some advantages of the system are: The system keeps up-to-date information of all transactions.
If the operator makes any mistakes the system will prompt that through
the error messages.
This project gives all types of reports according to the user.
To conclude this, I thank all people who helped me to complete this project
work successfully.

8. BIBILOGRAPHY
BOOKS:
Elias M.Awad, System Analysis and design,
- Galgotia Publications, 1997.
Roger.S.Pressman, Software Engineering,
-Tata McGraw-Hill, 1999.
Sandeep Canda and Damien Foggon, Beginning ASP.NET Databases
- 3rd Edition
ONLINE REFERENCE:
www.visual.com
www.w3schools.com
29

www.wikipedia.com

30

9. APPENDIX
A DATA FLOW DIAGRAM
Data flow diagram (DFD) is used to define the flow of the system and its
resources such as information. Data flow diagram are a way of expressing system
requirement in a graphical manner.DFD represent one of the most ingenious tools
used for structured analysis. A DFD is also known as a bubble chart.it has the
purpose of clarifying system requirement and identifying major transformations
that will become program in system design.
In the normal convention, logical DFD can be completed using only 5 notations
:Represents

source or destination of

data
:Represent data flow

incoming

:A process that transforms


data Outgoing flow

:Data Store

:Reports
Level-0
Login Form
Checking
User Type

31

Verifying User name


& Password

User name

Users

Password
Valid
Users

Invalid Users

Main Form

LEVEL- 0
REGISTRATION
SBI LOGIN

REGISTER MEMBER

DATA BASE

32

Level-1
Main Form
Accounts
Valid Users
Main Form

Recurring Deposit
Fixed Deposit
Transaction

Staff Details

Level-2
NEW ACCOUNT

NEW ACCOUNT

ADD CUSTOMER

FIND CUSTOMER
UPDATE
CUSTOMER

INSERT RECORDS

SELECT RECORDS

UPDATE TABLE SET


ID=

DATABASE

REPORT
33

Level-3
RECCURING DEPOSIT

VIEW RECURRING
DEPOSIT

RECCURING DEPOSIT

UPDATE RECURRING
DEPOSIT

UPCOMING
DETAILS

UPDATE TABLE
SET NAME

SELECT DATE FROM


TABLE

INSERT RECORDS

DATABASE

REPORT

34

Level-4
FIXED DEPOSIT

VIEW FIXED
DEPOSIT

FIXED DEPOSIT

UPDATE FIXED
DEPOSIT
UPCOMING
DETAILS
UPDATE TABLE
SET NAME

SELECT DATE FROM


TABLE

INSERT RECORDS

DATABASE

REPORT

35

Level-5
TRANSACTION DETAILS

TRANSACTION DETAILS

VIEW TRANSACTION
DETAILS

ADD TRANSACTION

SELECT * FROM
TABLE
INSERT RECORDS

VIEW ALL
TRANSACTION

SELECT * FROM
TABLE

DATABASE

REPORT

36

Level-6
STAFF DETAILS
VIEW STAFF
DETAILS

STAFF DETAILS

UPDATE STAFF
DETAILS
UPDATE TABLE
SET NAME

SELECT DATE FROM


TABLE

INSERT RECORDS

DATABASE

REPORT

37

B. ER DIAGRAM
An E R diagram is a model that identifies the concept or entities that exist in a
system and the relationships between those entities. An ERD is often used as a way
to visualize a relational database: each entity represents a database table and the
relationship lines represents the key in one table that point to specific records in
related tables.
Advantages of ER diagram
Professional and faster Development.
Productivity Improvement.
Fewer Faults in Development.

Maintenance becomes easy.

38

39

ER-(BANKING SYSTEM)

Address

Name

SBI Registration

Mobile No

Username
Password

Members

Deposit Number

Account
Number

Gender

Name

Address

Address
Customer

Deposit

New Account

TranscationAmou
nt

Interest
Account Type
Deposit
Term

Transaction

Contact
Number

Balance Amount

Balance Amount
Fixed Deposit

Deposit
Amount
Address

Deposit
Term

Deposit Number

Name

Fixed Deposit
Net Salary

Employee
Id

Interest
HRA
Staff
Staff Details
PF

Destignation

Name

Location
Salary

40

Deposit
Term

Balance Amount

C.TABLE DESIGN

41

42

43

D.FORM DESIGN

44

45

46

47

48

OUTPUT DESIGN:-

49

50

51

52

53

54

55

REPORT:-

56

57

Sample code:-

Imports System.Data
Public Class Form5
Dim dt As DataTable
Dim dr As DataRow
Dim bm As BindingManagerBase
Dim flag As Integer
Public Function MarqueeLeft(ByVal Text As String)
Dim Str1 As String = Text.Remove(0, 1)
Dim Str2 As String = Text(0)
Return Str1 & Str2
End Function
Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Timer1.Tick
Label22.Text = MarqueeLeft(Label22.Text)
Label23.Text = MarqueeLeft(Label23.Text)
Label24.Text = MarqueeLeft(Label24.Text)
End Sub
Private Sub Form5_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles MyBase.Load
Me.OleDbConnection1.Open()
Me.OleDbDataAdapter1.Fill(Me.DataSet161, "Table1")
Me.Label20.Text = System.DateTime.Now.ToString("dd-MM-yyyy")
Me.Label21.Text = Hour(Now) & ":" & Minute(Now) & ":" & Second(Now)
bm = BindingContext(Me.DataSet161, "Table1")
End Sub
Private Sub Button9_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button9.Click
bm.Position = 0
End Sub
Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button8.Click
bm.Position -= 1
End Sub
Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button6.Click
bm.Position += 1
End Sub
Private Sub Button7_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button7.Click
bm.Position = bm.Count - 1
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button1.Click
Try
Me.OleDbInsertCommand1.Parameters(0).Value = TextBox3.Text
Me.OleDbInsertCommand1.Parameters(1).Value = TextBox4.Text
Me.OleDbInsertCommand1.Parameters(2).Value = ComboBox1.Text
Me.OleDbInsertCommand1.Parameters(3).Value = DateTimePicker1.Text
Me.OleDbInsertCommand1.Parameters(4).Value = TextBox5.Text
Me.OleDbInsertCommand1.Parameters(5).Value = TextBox6.Text

58

Me.OleDbInsertCommand1.Parameters(6).Value = TextBox7.Text
Me.OleDbInsertCommand1.Parameters(7).Value = TextBox8.Text
Me.OleDbInsertCommand1.Parameters(8).Value = ComboBox2.Text
Me.OleDbInsertCommand1.Parameters(9).Value = DateTimePicker2.Text
Me.OleDbInsertCommand1.Parameters(10).Value = DateTimePicker3.Text
Me.OleDbInsertCommand1.Parameters(11).Value = TextBox9.Text
Me.OleDbInsertCommand1.Parameters(12).Value = TextBox1.Text
Me.OleDbInsertCommand1.ExecuteNonQuery()
Me.OleDbDataAdapter1.Fill(Me.DataSet161, "Table1")
MsgBox("Record Saved")
Catch ex As Exception
Windows.Forms.MessageBox.Show(ex.Message)
End Try
End Sub
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button3.Click
dt = Me.DataSet161.Tables("Table1")
dr = dt.Rows.Find(TextBox3.Text)
dr.Delete()
Me.OleDbDataAdapter1.Update(Me.DataSet161, "Table1")
Me.OleDbDataAdapter1.Fill(Me.DataSet161, "Table1")
MsgBox("Record Deleted")
End Sub
Private Sub PictureBox3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles PictureBox3.Click
Form1.Show()
Me.Hide()
End Sub
Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button4.Click
Try
Me.OleDbUpdateCommand1.Parameters(0).Value = TextBox4.Text
Me.OleDbUpdateCommand1.Parameters(1).Value = ComboBox1.Text
Me.OleDbUpdateCommand1.Parameters(2).Value = DateTimePicker1.Text
Me.OleDbUpdateCommand1.Parameters(3).Value = TextBox5.Text
Me.OleDbUpdateCommand1.Parameters(4).Value = TextBox6.Text
Me.OleDbUpdateCommand1.Parameters(5).Value = TextBox7.Text
Me.OleDbUpdateCommand1.Parameters(6).Value = TextBox8.Text
Me.OleDbUpdateCommand1.Parameters(7).Value = ComboBox2.Text
Me.OleDbUpdateCommand1.Parameters(8).Value = DateTimePicker2.Text
Me.OleDbUpdateCommand1.Parameters(9).Value = DateTimePicker3.Text
Me.OleDbUpdateCommand1.Parameters(10).Value = TextBox9.Text
Me.OleDbUpdateCommand1.Parameters(11).Value = TextBox1.Text
Me.OleDbUpdateCommand1.Parameters(12).Value = TextBox3.Text
Me.OleDbUpdateCommand1.ExecuteNonQuery()
Me.OleDbDataAdapter1.Update(Me.DataSet161, "Table1")
Me.OleDbDataAdapter1.Fill(Me.DataSet161, "Table1")
MsgBox("Record UPDATED")
Catch ex As Exception
Windows.Forms.MessageBox.Show(ex.Message)
End Try
End Sub

59

Private Sub StaffToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As


System.EventArgs) Handles StaffToolStripMenuItem.Click
Form7.Show()
Me.Hide()
End Sub
Private Sub NewAccountToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles NewAccountToolStripMenuItem.Click
Form2.Show()
Me.Hide()
End Sub
Private Sub DepositWithdrawToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles DepositWithdrawToolStripMenuItem.Click
End Sub
Private Sub ViewDeleteAccountToolStripMenuItem_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles ViewDeleteAccountToolStripMenuItem.Click
Form9.Show()
Me.Hide()
End Sub
Private Sub FixedDepositToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles FixedDepositToolStripMenuItem.Click
Form4.Show()
Me.Hide()
End Sub
Private Sub RecurringDepositToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles RecurringDepositToolStripMenuItem.Click
End Sub
Private Sub TransactionToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles TransactionToolStripMenuItem.Click
Form3.Show()
Me.Hide()
End Sub
Private Sub StaffMemberToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles StaffMemberToolStripMenuItem.Click
Form8.Show()
Me.Hide()
End Sub
Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button5.Click
TextBox1.Text = Val(Me.TextBox2.Text) + Val(TextBox1.Text)
End Sub

60