PROJECT REPORT ON

INTEREST CALCULATION SYSTEM

FOR A RETAIL BANK

Submitted by –
Department Of Information Technology
(2007-11)

Paulami Ghosh (Roll:61)

Bibhas Chandra Debnath (Roll:62)
Aritri Saha (Roll:63)
Nishan Das (Roll:64)
Biswajit Das (Roll:6)
 CERTIFICATE OF ORIGINALITY

This is to certify that the work title:

Development Of Interest Calculation System For A Retail Bank
has been carried out by Paulami Ghosh, Aritri Saha, Bibhas
Chandra Debnath, Nishan Das and Biswajit Das. The work has
been satisfactorily completed by them and I recommend the
work as being worthy of acceptance for partial fulfillment of the
requirement for the Infosys Campus Connect Foundation
Programme Certificate.

Niloy Kumar Nag

SPOC
Infosys Campus Connect

Date :
 ACKNOWLEDGEMENT

We take this opportunity to express our gratitude to all

individuals associated with this project.
We are thankful to Infosys Campus Connect Progaramme for
giving us an opportunity to work and learn here . We
acknowledge our sincere gratitude to the lecturers for their
valuable guidance and helping attitude even in their very busy
schedule.
We are thankful to all the professors, data collectors and
respondents of the questionnaire and all those who have
helped us a lot in pursuing this project work as without their
support we wouldn’t have got into the realities.
 CONTENTS

1. Introduction
1.1 Goals
1.2 Concept of the project
1.3 Features of the project
1.4 Scope of the project

2. Software and System Requirements and Specification

2.1 Software Development Life Cycle (SDLC)

2.2 Feasibility Study
2.3 Software Requirement Specification
2.3.1 Introduction
2.3.2 System Requirement Specification
2.3.2.1 ASP.NET with VB
2.3.2.2 ADO.NET
2.3.2.3 SQL Server
2.3.2.4 Operating System
3. System Design Specification
3.1 System Design
3.1.1 Context Level Diagram
3.1.2 Level 1 of DFD
3.1.3 Database Design for ER Diagram
3.1.4 Entity Relationship Diagram

4. Testing and Maintenance

4.1 Testing
4.2 Maintenance

5. Snapshots

6. Scope for Future Enhancement

7. Conclusion

8. Bibliography
 Chapter-1

INTRODUCTION
1.1 Goals

In real world, to function smoothly & efficiently every

organization must have a proper management facility. As this is
the age of computer this system should be computerized. This
will help organization to function in a more systematic fashion
and to leverage the most of the work force with much less
effort, though the system must be monitor constantly by
expert to pinpoint flaws and implementing all the suggestion as
if, there is a job which cannot be done by machine.

The aim of Interest Calculation System is to automate the

process of interest calculation for a retail bank, which collects
money from customer and in return gives them an interest at a
pre determined rate. This system calculates the interest daily
for each account having balance more than zero.
1.2 Concept of the project

The system developed willautomatically calculate interest on

daily basis for each account having balance more than zero at
the pre determined interest rate. This interest calculated will be
cumulatively stored in a table which will be updated every day.
The balance on which interest is calculated daily will 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 should be set to zero as the customer has benefited for
the period specified. Before interest is credited to customer’s
account, tax should be debited from the interest according to
prevalent government laws.
1.3 Features of the project

1. It automatesdaily interest calculation for each account of a

bank.
2. It automates monthly tax deduction from each customer’s
account.
3. It makes the complex work of updating records in
customer’s database, after each transaction (i.e. deposit or
withdraw money), simple and convenient.
4. It reduces the work load for the process to the minimum.
5. It is cost effective.
6. It is magically time saving.
7. It is easy to handle and maintain.
8. Multiple users can access the webpage at the same time.
9. This is compatible with almost all systems.
1.4 Scope Of the project

Every project is done to achieve a set of goals with some

conditions keeping in mind that it should be feasible, user-
friendly and easy to use. As the goal of our project was to
develop an Interest Calculation system for a retail bank, we
have done it to our best within keeping the conditions started
above in mind. The scope of this project is --
 Username and password for authentication and security
purpose.
 Customers have the facilities to check their balance and
interest till that date after logging into their corresponding
account.
 The amount that have been deposited or withdrawn by a
customer will automatically get updated in the database.
 Administrators have the right to change the rate of
interest and tax rate after logging into their account.
 Chapter-2

SOFTWARE & SYSTEM

REQUIREMENTS
SPECIFICATION
2.1 Software Development Life Cycle
(SDLC)

The System Development Life Cycle (SDLC) is a conceptual

model used project management that describes the stages
involved in information system development project from
investigation of initial requirements through analysis, design,
implementation and maintenance of the completed
application. Once upon a time, software development consisted
of a programmer writing code to solve a problem or automate a
procedure.

To manage this, a number of system development life cycle

(SDLC) models have been created: waterfall, fountain, spiral,
rapid prototyping, incremental models. Mostly, several models
are combined into some sort of hybrid methodology.
Software life cycle model -

The iterative waterfall model is used in this project” (name of

the project)” as it has certain advantages over contemporary
models. It does not impose the rigid phase sequence which
otherwise could create blocking states in the system. If an
engineer works fast and completes design of the parts assigned
to him early, then inspire of writing for others to complete their
designs proceeds to the next phase. Another reason for using
this model is reduced communication gap among the project
engineers. A design defect might go unnoticed till we reach the
coding or testing phase. Once a defect is detected, the engineer
needs to go back to that phase and the subsequent phase
occurred and redo some of the work done during that phase
and the subsequent phases to correct the defect and its effect
on the later phases. In this model feedback paths allow
interactions different phases.
 Feasibility study

Requirement analysis
And specification

Design

Coding and
Unit testing

Integration and
System testing

Maintenance

Fig: Iterative Waterfall Model

2.2 Feasibility Study

The main aim of feasibility study is to determine whether it
would be technically, economically and operationally feasible to
develop the project or product. This activity involves the
analysis of the problem and collection of all relevant
information relating to the product, formulation of different
solution strategies and analysis of alternative solution
strategies to compare their benefits and shortcomings. This
analysis requires making approximately estimates of the
resources required, cost of development, and development
time for each of the option. Once the best solution is identified,
all later phases of development are carried out as per this
solution.

It is both necessary and prudent to evaluate the feasibility and

risk of a project at the earliest possible time. Feasibility and risk
analysis are related in many ways. If project risk is high, the
feasibility of producing quality software is reduced.

The tests of feasibility stated below are equally important:

 Operational Feasibility: Proposed project is
beneficial only if it can be turned into information
system that will meet the organization’s operating
requirements.

 Technical Feasibility: The technical issues raised

during the feasibility stage of investigation include
existence of necessary technology to support the
proposed system, the prospects of ability to expend
the system if developed etc.

 Economic Feasibility: This requires in making approx

estimates of the resources required, cost of
development, development time for each options. A
project is said to be economically feasible if the
project’s goal can be achieved within the resource
limits allocated to it and the benefits obtained from
the new system.
2.3 Software Requirements Specification

2.3.1 Introduction -
The Software Requirement Specification is a documentation in
which all requirements specified by the customer are organized
in a systematic order so that it can be produced at various stage
of the project for precise development of the product. The SRS
is a documentation used by a wide variety of users such as, the
end user, the customers, the software developers, test
engineers, project managers etc. The SRS document can be
viewed as a documentation of a contract between the
developer and the customer as both of them has to agree to
the SRS document before any sort of development begin.
The SRS document contains the following aspects of the
system:
 Functional requirements which discuss the functionalities
required from the system. The SRS document clearly
describes each function which the system would support
along with the corresponding input and output dataset.
  Non-functional requirements that deals with the
characteristic of the system that cannot be expressed as
functions such as portability, usability etc.
 Goals of implementation give general suggestion regarding
the development. This section is concerned with the issues
such as reusability of the system, new device support in
the future etc.

2.3.2 System Requirement Specification-

Hardware Requirements:
 Processor: Intel Duo
 Hard Disk: 40GB
 RAM: 256MB
Software Requirements:
 Operating System: Windows 7/Windows XP
 Other Software Requirement: Visual Studio 2008
 Database: Microsoft Access
Technology Used:
 .Net with VB
2.3.2.1 .NET with VB

What is .NET?
 .NET is a platform that provides a standardized set of
services. It’s just like Windows, except distributed over the
Internet. It exports a common interface so that its
programs can be run on any system that supports .NET.
 A specific software framework which includes a common
runtime.
 Code organized in hierarchical namespace and classes.
Everything is an object in this language.
 Component Oriented-Properties, methods, events and
Design-time functionality are the main component.

Overview of the .NET Framework -

The .NET framework is managed type-safe environment for
application development and execution. The .NET framework
manages all aspects of your program’s execution. It allocate
memory for the storage of data and instruction, grants or
denies the appropriate permission to your application, initiates
and manages application execution, and manages the
reallocation of memory from resources that are no longer
needed. The .NET Framework consists of memory from
resources that are no longer needed. The .NET Framework
consists of two main components: the common language
runtime and the .NET Framework class library.
The Framework is made up of the following parts -
 The Common Language Runtime(CLR)
 The base class library
 Object oriented Internet development with ASP.Net
 Rich client user interface using windows form
 RAD for the Internet using web forms
2.3.2.2 ADO.NET

ADO.NET is set of computer software components that can be

used by programmers to access data and data services. It is a
part of the base class library that is included with the Microsoft.
It is commonly used by programmers to access and modify data
store in relational database system, though it can also be used
to access data in non-relational sources. ADO.NET is sometimes
consider an evolution of ActiveX Data Objects (ADO)
technology, but was changed so extensively that it can be
considered an entirely new product.
ADO.NET base classes enable you to manipulate data from
many data source, such as SQL SERVER, Exchange and Active
Directory. ADO.NET leverages. Net object model exposes very
flexibility components, which in term expose their own
properties and methods, and recognizes events.
ADO.NET as being composed of two major parts:
 .NET data provider- this classes are optimized for fast,
read-only and forward only retrieval of data. The managed
provides like to the database by using a fast data stream.
 Another major part is Data storage.
2.3.2.3 Microsoft Access

Microsoft Office Access, previously known as Microsoft Access,

is a pseudo-relational database management system from
Microsoft that combines the relational Microsoft Jet Database
Engine with a graphical user interface and software-
development tools. It is a member of the Microsoft Office suite
of applications. Access stores data in its own format based on
the Access Jet Database Engine. It can also import or link
directly to data stored in other applications and databases.
Access is supported by Visual Basic for Applications, an object-
oriented programming language that can reference a variety of
objects including DAO (Data Access Objects), ActiveX Data
Objects, and many other ActiveX components. Visual objects
used in forms and reports expose their methods and properties
in the VBA programming environment, and VBA code modules
may declare and call Windows operating-system function.
Microsoft Access is used to create simple, as well as complex,
database solutions. Access tables support a variety of standard
field types, indices, and referential integrity. Access also
includes a query interface, forms to display and enter data, and
reports for printing. Database solutions created entirely in
Microsoft Access are well suited for individual and workgroup
use across a network. The number of simultaneous users that
can be supported depends on the amount of data, the tasks
being performed, level of use, and application design. Microsoft
Access offers parameterized queries. These queries and Access
tables can be referenced from other programs like VB6 and
.NET through DAO or ADO. From Microsoft Access, VBA can
reference parameterized stored procedures via ADO.

2.3.2.4 Operating System

The topic provides an overview of how much Microsoft
Windows work internally and different element that make up
or window program. Also we work at difference between DOS
program and examine how the windows appears more than the
program at run time. Some of the unique aspects executing
Windows program are discussed. Such as processing window
message and using resources to store the program data.
Window build memory management functions are vitalto
window ability to run may applications at the same time. As a
program we will be able to control how different positions of a
program are managed in memory.
 Chapter-3

SYSTEM DESIGN
SPECIFICATION
3.1 System design

There are SIX major steps in the design process. The first
five steps are usually done on paper and pencil and then
final design is implemented.

1. Identify the table

2. Identify data that is needed for each table and
relationship
3. Normalize the data
4. Resolve relationship
5. Verify the design
6. Implement the design
3.1.1. Context Level Diagram
3.1.2. Level 1 DFD
3.1.3. Level 2 DFD
3.1.3. Database Design for ER Diagram

Introduction
Database design is the process of developing database structures
to hold data to cater to user requirements. The final design must
satisfy user needs in terms of completeness, integrity,
performance and other factors. For a large enterprise, the
database design will turn out to be an extremely complex task
leaving a lot to the skill and experience of the designer. A
number of tools and technologies, including computer assisted
techniques, are available to facilitate database design.

The primary input to the database design process is the

organizations’ statement of requirements. Poor definition of
these requirements is a major cause of poor database design,
resulting in database of limited scope and ultimate which are
unable to adopt to change.

The major step in database design is to identify the entities and

relationships that reflect the organization’s data. Naturally, the
objective of this step is to specify conceptual structure of the
data and is often referred to as data modeling.
There are several methodologies to model the data
logically. We adopted ER modeling as our data modeling
technique.ER model is technique for analysis and logical
modeling of systems data requirements. It uses three basic
concepts: entities, attributes and relations.

 Entity –

Entity is a distinguishable object. These entities are

classified in regular entities and weak entities. A weak
entity is an entity that is existence dependent on some
other entity i.e. it does not exist if that other entity does not
exist. A regular entity is that it is not weak .The graphical
notation of entry is shown below.

Regular Entity Weak Entity

 Attribute –

Entities have properties known as attributes. All entities of a

given type have certain kinds of properties in common.
Each property draws its value from the corresponding value
set. Properties can be of various types: simple or composite,
key, single or multi, missing, and base or derived. Attributes
are graphically represented as shown below-

Attribute
 Relation –

Relationship defines an association among entities. The

entities involved in a given relationship are said to be
participants in that relationship.

The number of participants in a given relationship is called

the degree of that relationship. A relationship can be one-
to–one, one-to-many, and many-to-many. Cardinality of a
relationship refers to representing the number of
occurrences of entity in a given relationship. The graphical
representation of relation is as shown below-

Relationship

In our project we have identified entities, attributes

for those entities and relationships between those
entities from data collected at analysis phase.
3.1.4 Entity Relationship Diagram
 Chapter-4

TESTING AND
MAINTENANCE
4.1. Testing
Software testing is the process used to help identify the
correctness, completeness, security, and quality of developed
computer software. Testing is a process of technical
investigation, performed on behalf of stakeholders, that is
intended to reveal quality related information about the
product with respect to the context in which it is intended to
operate. This includes but is not limited to, the process of
executing a program or application with the intent of finding
errors. Quality is not an absolute it is value to some person.
With that in mind, testing can never completely establish the
correctness of arbitrary computer software; testing furnishes a
criticism or comparison that compares the state and behavior
of the product against a specification. An important point is
that software testing should be distinguished from the separate
discipline of software quality assurance, which encompasses all
business process areas, not just testing.

There are many approaches to software testing, but effective

testing of complex products is essentially a process of
investigation, not merely a matter of creating and following
routine procedure. One definition of testing is “the process of
questioning a product in order to evaluate it”, where the
“questions” are operations the tester attempts to execute with
the product, and the answers with its behavior in reacting to
the probing of the tester. Although most of the intellectual
processes of testing are nearly identical to that of review or
inspection, the word testing is connected to mean the dynamic
analysis of the product-putting the product through its paces.
The quality of application can, and normally does, vary widely
from system to system but some of the common quality
attributes include capability, reliability, efficiency, portability,
maintainability, compatibility and usability. A good test is
sometimes described as one which reveals an error; however,
more recent thinking suggest that a good test is one which
reveals information of interest to someone who matters within
the project community.

Testing is performed in three steps:

 Unit Testing
 Integration Testing
 System testing
UNIT TESTING
In computer programming, a unit test is a procedure used to
validate that a particular module of source code is working
properly from each modification to the next. Ideally, each test
case is separate from the others; constructs such as mock
objects can assist in separating unit tests. This type of testing is
mostly done by the developers and not by end-users.
Purpose
 To test the field level validations.
 To test whether the objects in the form like alerts and
prompts are
Working or not.
 To test whether the form conforms to all the standards.
 To test whether all the functions available on the form are
working or not.

INTEGRATION TESTING
Integration testing (sometimes called integration and testing
and abbreviated I&T) is the phase of software testing in which
individual software modules are combined and tested as a
group. It follows unit testing and precedes system testing.
Integration testing takes as input the modules that have been
unit tested, groups them in larger aggregation, applies tests
defined in an Integration test plan to those aggregates, and
delivers as its output the integrated system ready for system
testing.
Purpose
The purpose of Integration testing is to verify functional
performance and reliability requirements placed on major
design items. These “design items”, i.e. assemblages (or groups
of units),are exercised through their interface using Black box
testing success and error cases being simulated via appropriate
parameter and data inputs. Simulated usage of shared data
areas and inter process communication is tested; Individual
subsystems are exercised through their input interface. All test
cases are constructed to test that all components within
assemblages interact correctly, for example, across procedure
calls or process activations and is done after the testing single
module i.e. unit testing.
The overall idea is a “building block” approach, in which verified
assemblages are added to a verified base which is then used to
support the Integration testing of further assemblages. The
different types of integration testing are Big Bang, Top Down,
Bottom Up and Back Bone.

SYSTEM TESTING
System testing is testing conducted on a complete, integrated
system to evaluate the system’s compliance with its specific
requirements. System testing falls within the scope of black box
testing, and as such, should require no knowledge of the inner
design of the code or logic.
Alpha Testing and Beta Testing are sub categories of System
testing.
As a rule, System testing takes, as its input, all of the
“integrated” software components that have successfully
passed Integration testing and also the software system itself
integrated with any applicable hardware systems. The purpose
of integration testing is to detect any inconsistencies between
the software units that are integrated together (called
assemblages) or between any of testing; it seeks to detect
defects both within the “inter-assemblages” and also within the
system as a whole.
4.2 MAINTENANCE

Software Maintenance
Maintenance is the enigma of system development.
Maintenance can be classified as corrective, adaptive and
perfective. Adapting Maintenance means changing the program
function. Perfective maintenance means enhancing the
performance or modifying the program to respond to the user’s
additional or changing needs. Maintenance covers a wide range
of activities, including correcting code and design errors,
updating documentation and test data and upgrading user
supports.
Several MIS organizations have done to attack the ever growing
problem of software maintenance reduction-plan that consists
of three parts
 Maintenance management audit
 Software system audit
 Software modification
Maintenance management audit is done through interviews
and questionnaires that evaluate the quality of maintenance
effort.
Software implementation which consists of program writes
system level update and re-audit of manual system to make
sure that errors have been corrected.
The System that has been developed is easily managed. Codes
for different operations have been placed in different modules
and can be easily changed as per needs. Codes have been
written in classes which facilitate changes at only one place are
reflected through the system.
 Chapter-5

SNAPSHOTS
 Chapter-6

SCOPE FOR FUTURE

ENHANCEMENT

Future scope of the project:

1. We would like to make the project more user-friendly.
2. Administrator part can be modified to facilitate multiple
administrators.
3. The system may be improved graphically with the help
of other applications.
 Chapter-7

CONCLUSION

Every effort has been made on part to make the project viable
and user friendly:-
1. G.U.I based
2. Applicable for any windows operating system
3. Data validation checks at the client side
4. Generates fast & efficient report
5. Updates customer’s record in the database automatically
6. Performs fast operation on data
 Chapter-8

BIBLIOGRAPHY

1. Pressman, R. (1998) Software Engineering: A Practitioner’s

Approach, McGraw-Hill International Edition.
2. Database System Concept by Navathe, McGraw-Hill Higher
Education.
3. Asp.Net 3.5 by Unleashed, Pearson Education.
4. Professional Asp.net 4 C# & VB by Bill Evjen, Scott
Halsmen.
5. Websites:
www.google.com
www.wikipedia.org