Om Shanti Diploma Engg College

Prepared by: -

guided by:-

VORA.BHARAT

BHATT.KISHAN TANNA .SEJAL

Omshanti diploma Engg College INSTITUTE OF ENGG

Certificate
This is to certify that Mr : DESANI.ABHISHEK.R having Enrolment No : 096720307017 has completed Part-I IDP Project work Having title : BANKING SYSTEM. He has undergone the process of shodh yatra, literature survey and problem definition. He is supposed to carry out the residue IDP Part-II work on same problem during Semester-VI for the final fulfilment of the IDP work which is prerequisite to complete Diploma Engineering.

Guide IDP Head of Department

Omshanti diploma Engg College INSTITUTE OF ENGG

Certificate
This is to certify that Mr : VORA.BHARAT.R having Enrolment No : 096720307010 has completed Part-I IDP Project work Having title : BANKING SYSTEM. He has undergone the process of shodh yatra, literature survey and problem definition. He is supposed to carry out the residue IDP Part-II work on same problem during Semester-VI for the final fulfilment of the IDP work which is prerequisite to complete Diploma Engineering.

Guide IDP Head of Department

3

ACKNOWLEDGEMENT

We owe our professor thanks to all who co-operated and assisted us for the successful accomplishment of this project work. We express our gratitude to our college for providing us an opportunity to achieve our vision. We are also indebted to our course co-coordinator MR kishan sir for his valuable guidance and also to our external for evaluating our project by giving valuable suggestions.

Sir_ no

Contents

Page no

Introduction

5-10

Project Management

11-13

System Requirements study

14-17

System Analysis

18-31

System Design

32-37

Implementation Planning

38-47

Limitation and Future Enhancement

48-49

Bibliography

50

Project summery
6

 purpose

Scope

PROJECT SUMMARY

THE LIST OF FEATURES IN THIS PROJECT

1. 5. 6. 7. 9.

CREATION OF ACCOUNT AND NEW ACCOUNT DEBIT CREDIT LOAN SYSTEM TRANSACTION

10. BALANCE CHECK

7

7. EMI CALCULATOR

CREATION OF ACCOUNT AND NEW ACCOUNT

In creation account form customer can create it account. But in creation of customer id is must be unique and referred account user name must be valid otherwise customer cant make an account. Customer can create an account if it deposited more than RS: 1000. DEBIT
We put the constraints of user and administrator in login form through which user cant update and delete its records. In debit form user can withdraw its amount from bank and used it for its purpose.

CREDIT
In Credit account form customer can credit it account if it deposit amount more than RS: 1000.

TRANSACTION

Most of banking system provides transaction system in which customer can transfer amount of its account balance to another. its chosen account no to implement this feature we use transfer balance account form to transfer balance from one account to another one.

BALANCE CHECK
In balance check form customer can view its balance and its customer id, name, age, gender and mobile no.

LOAN
In loan module user can get loan from bank but it must be user of that bank.

Purpose of banking system

The main purpose that banks have been serving since their inception is keeping our money safe for us. While keeping our money safe, they also let us earn a certain amount of interest on the money deposited with them. Traditional banks have been doing this, and banks continue the same function. The only difference is in the way the transactions are made. We all know about banking and most of us use it quite often as well, but few of us actually understand about the history of banking and how it all came out. Knowing the history of internet banking can be incredibly useful, especially since it will allow us to have more respect for the little things that we take for granted. Computers themselves have really come an enormous way since their initial establishment, as the earliest electronic computers were so large that they would take up the entire area of a room, while today some are so small that they can hardly be seen at all.

 Scope of banking system

A healthy banking system is essential for any economy striving to achieve good growth and yet remain stable in an increasingly global business environment. The Indian banking system, with one of the largest banking networks in the world, has witnessed a series of reforms over the past few years like the deregulation of interest rates, dilution of the government stake in public sector banks (PSBs), and the increased participation of private sector banks. The growth of the retail financial services sector has been a key development on the market front. Indian banks (both public and private) have not only been keen to tap the domestic market but also to compete in the global market place. Studying the increasing business scope of the bank. Market segmentation to find the potential customers for the bank. Customers perception on the various products of the bank. The corporate sector has stepped up its demand for credit to fund its expansion plans; there has also been a growth in retail banking. The report seeks to present a comprehensive picture of the various types of bank.

10

 project planning and scheduling

Schedule for Milestone Activities:

WEEK 1:
Introduction to Institute.

11

WEEK 2:

create a database for banking system

WEEK 3:

Create a login and create customer form.

WEEK 4:
Create a debit, credit, transaction, loan form.

WEEK 5:

Create project report on banking system.

WEEK 6:

Create use case and data flow diagram

Layout of project creation schedule

12

1st Week Months 1st Month Introduction to Institute.

2nd Week

3rd Week 4th Week Get overview about various Functions of banking System.

Introduction to Banking system..

2nd Month

Requirement gathering Study of Existing system which Parallel work of of the software to be works manually. developed were studied. Started analysis of the System. . Study of c#

language. Finish the analysis and decide modules. of Final layout of system design view.

3rd Month

Start: -

Decide about the Designing Logical design of the various modules. diagrams.

UML the

Designing Architecture.

of

system

4th Month

Development Phase.

Testing module.

of

our Standard integrationof variousModul es.

Final documentation the project.

13

 user characteristics hardware and software requirement

User characteristics

14

User of banking system

1. Administrator: He is the super user responsible for managing system users,

taking system backup, generating reports, maintaining organization details, Starting Sessions and ending Sessions and also manages various requests from different Types of users. Providing Username, Password and other information required for the users to start an account. Starting Sessions: The Administrator creates the system users and will be assigned with the different roles. He is also responsible to start the session when a particular user wants to use the system every time (It is automatically managed setup). Managing Data Backup: The Administrator is responsible for managing entire details by taking the backup periodically. He also takes the Backup of the database in order to prevent loss of data on system crashes or in order to prevent malfunctioning. He can take a backup of entire database or a particular section. Crash Recovery: The Administrator manages the crash recovery at the time of system crash or failure occurs. Ending session: The administrator is responsible for ending the session when the particular user logged out of the system (It is automatically managed setup).

1. Customer (Normal/others): Ordinary customers have a user name & password

with which they can login into their account. They can perform all the transactions such as funds transfer, balance enquiry, etc by sitting at their home on internet.

15

Login: User can login to the system by providing appropriate username and password provided by the administrator. Selecting the Account: After logging in the user is provided with a screen showing the details of accounts and he selects one of the accounts in order to perform the transaction. Balance Enquiry: He can view the balance left in his account, if once he has entered into his account. Funds Transfer: Upon the request the user can transfer funds from his account to other accounts. Mini statements: He also can take a mini statement print out upon his requirement.

Hardware and software requirement

1. Hardware Requirements.
16

 Any processor above 2.4 GHz.

Minimum 384 MB RAM (1024 MB Recommended).

Minimum 5400 rpm HDD (Recommended 7200 rpm). 1280*1024 display resolution capable monitor.

2.

Software Requirements.
Operating system: Windows XP Front End: Visual studio 2008 Jasper Reporting Tool Microsoft office 2007.

Back End: Database ms access 2003

17

 Requirement of new system feasibility of study requirements validation function of system activity/process in new system

18

Requirement of new system

In existing system transaction are done only manually but in proposed system we have to computerized all the banking transaction using the banking system software

PROBLEMS WITH EXISTING SYSTEM

1.

Lack of security of data.

2. 3.

More man power. Time consuming.

4. 5.

Consumes large volume of pare work. Needs manual calculations.

6. 7.

No direct role for the higher officials. Damage of machines due to lack of attention.

To avoid all these limitations and make the working more accurately the system need to be computerized.

PROPOSED SYSTEM

The aim of proposed system is to develop a system of improved facilities. The proposed system can overcome all the limitations of the existing system. The system provides proper security and reduces the manual work.

19

ADVANTAGES OF THE PROPOSED SYSTEM

the system is very simple in design and to implement. The system requires very low system resources and the system will work in all most all configurations. It has got following features

1.

Security of data.
2. 3.

Ensure data accuracy's. Proper control of the higher officials.

4. 5.

Reduce the damages of the machines. Minimize manual data entry.

6. 7.

Minimum time needed for the various processing. Greater efficiency.

8. 9.

Better service. User friendliness and interactive.

10.

Minimum time required.

Advantages of current system

Any information can be easily searched. All records of A/c`s and customer are stored in separate files. Which are maintained constantly update by system. Particular A/c information can be modified A particular customer record can be modified for one or more Fields customer name, address by providing A/c number. A customer record can be easily deleted by providing A/c number. The proposed system provides faster data access, data entry and Retrieval. The proposed system is more efficient, fast, reliable, user friendly. Over and above the proposed system does not have any possibility of data loss during processing

FEASIBILITY STUDY
20

 Feasibility Consideration
There were three key consideration involved in this feasibility analysis each consideration has reviewed to depict how it relates to the system effort. They are as follows:1. Economic feasibility 2. Technical feasibility 3. Behavioural feasibility

ECONOMIC FEASIBILITY
Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More Commonly known s cost/benefit. Analysis in this procedure we determine the benefits and saving that are expected in this procedure we determine the benefits and saving that are expected from the proposed system and compare the cost; we take a decision and implement the new proposed system. The manual efforts involved in maintaining the A/c and customer information, the withdrawal, the deposit and balance calculation, is tremendous. This is so because the volume of information to be handled is tremendous. Maintaining the records of these many customers is not easy and the manpower involved is great. With the help of computers it is very easy to maintain the detail of book and library and to keep track of available books. In case of computerization, the cost involvement is not very high. As it is used to be about 5-7 years back. All banking management needs initially is a desktop computer, a printer and a UPS to maintain continuous supply of electricity. A single operator can handle many queries. On an average, it should not take more 10-15 minutes to enter the information of a customer. As part of the feasibility study, an estimate is made whether the identified user needs may be satisfied using the current software and hardware. This study decides that whether or not the proposed system will be cost effective from a business point of view. In this case, user has one head clerk who does all the work. So the one clerk has maintain records regarding new A/c and deletion of A/c addition and deletion of customer, balance amount etc.Since he volume of information to be handled by a single person is tremendous. An analysis of the various alternatives suggested by the software development team follows in subsequent page

Technical Feasibility
21

This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include: a. The facility to produce outputs in a given time B C Response time under certain conditions. Ability to process a certain volume of transaction at a particular speed.

D Facility to communicate data to distant location. After examining technical feasibility, we give more importance to the configuration of the system than the actual make of hardware.

BEHAVIORAL FEASIBILITY

this includes the following questions:

1.

Is there sufficient support for the users?

2.

Will the proposed system cause harm?

The project would be beneficial because it satisfies the objectives when developed and installed. All behavioral aspects are cons idered carefully and conclude that the project is behaviorally feasible.

USECASE DIAGRAM:-

22

Customer AN System AN MANAGE REGIS SIGN OPERATE OPEN MANAGE

ACCOUNTS TER IN TRANSACTIONS CUSTOMERS ACCOUNT

Banking system

23

24

 E-R DIAGRAM:-

PASSWORD ADDRESS

ADMIN ID

Password

CUSTOMER ID PHONE NO Manages

Administr ator

Custome r

Main

CREATE ACCOUNT CHECK BALANCE TRANSF ER EMI CALCULAT ION DEBIT

CREDIT

CREDIT AMOUNT

INSERT DATA

CALCULATE EMI Perform transactions

WITHDRAW AMOUNT

DISPLAY
25

 CLASS DIAGRAM:-

Banking

System

Login
Username integer password

Loan
Customerid integer name integer interesttype integer loanamount

Transferbala nce Customerid

integer name integer amount

Createid
Customarid integer name integer age integer gender integer civil status integer mobileno integer referred integer postalcode integer mobileno integer openbalance integer birthday integer currentdate

View status
Customerid integer name integer age integer gender integer balance integer mobileno integer

Sequence diagram:26

 banking system

Custome r

Main

Varification of Valid Customer

Choise bank services

Create account

Creadit amount

Debit account

Get loan

Transaction process

Login customer

27

customer
Login System Services

enter user id and pass Verify of valid user

Allow access to service

Login fail

Relogin login fail ac

ACTIVITY DIAGRAM:28

Start

ENTER USERID AND PASSWORD

VALID USER

No Yes

BALANCE ENQUIRY

CREATE ACCOUNT

TRANSFER BALANCE

LOAN AMOUNT

DEBIT BALANCE

CREDIT BALANCE

YOUR ACCOUNT BALANCE IS:-

TRANSFER AMOUNT:LOAN AMOUNT:-

ENTER CUSTOMERID ENTER CUSTOMERID

COMMIT TRANSACTION CLOSE

Stop

Data Flow Diagrams:-

29

 DFD FOR BANKING SYSTEM

ADMIN

USERNAME PASSWORD

LOGIN CUSTOMER

CREATE ACCOUNT

CUSTOMER DATABASE

ADD

BALANCE REDUCE BALANCE

CREADIT AND DEBIT ACCOUNT

PASS NOT VALIDATE USER HAS IN DATABASE ORELOAN IN BANK

PROVIDE BANK SERVICE

TRANSACTION AND VIEW BALANNCE VALIDATION TRANSACTION & BALANCE

LOGIN PROCESS OF CUSTOMER

30

Custome r

Admin

Verifies user_id & password

Process customer request

Display Banking Services

Admin

Customer

REGISTRATION PROCESS OF CUSTOMER

31

32

 System Application Design Database Design/Data Structure Design

SYSTEM DESIGN
In the system and software design phase, the system specifications are translated into a software representation. The software engineer at this stage is concerned with:

DATA STRUCTURE Things taken into the consideration:

33

 Table Names Field Names Field Type Field Length Field Size Constraints Consistency

SOFTWARE ARCHITECTURE Things taken into the consideration: Separation of User Interface & Data Access Adaptability Interpretability

INTERFACE REPRESENTATION Things taken into the consideration: User Friendly Minimum Data Entry Appropriate Use of Dialogue Box

34

 Extensive use of Validations Consistency

ALGORITHM Things taken into the consideration: Reusability Readability Performance Maintainability

Database design/data structure design:

Database Tables Names and Description

Table name

table description

AUTHENTICATION

This table stores the username and passwords of administrators.

35

BANK LOAN

THIS Table stores all customer information related to it bank account. THIS table store the customer information which get lone from bank

Data dictionary:Features:The volume of data in most information system application is substantial-more than a single analyst can easily keep track of when teams of analyst work on a system the task of co-ordination data definition becomes more complex. Individuals depend on the definitions others establish and assumption they make about data specifications. Yet, unless they meet almost daily, it is virtually impossible to have accepted table data co-ordination. Data dictionaries are an integral component of structured analysis, since data flow diagrams by themselves do not fully describe the subject of the investigation. The data dictionary provides additional information about the system.

Data dictionary table:The data dictionary of this software can be given by following table: BANK table

Column Name customerid

Date Type integer

Constraint Primary Key

Description User name

Full name

integer

Not null

Full name of employee

36

Age Gender Civil status referred

integer integer integer integer

Not null Not null Not null Not null

age gender Married or not. Reference of customer name in banking system

postal code mobileno open balance birthdates current date occupation annual income

integer integer Date Integer integer integer integer

null null Not null Not null Not null Not null Not null

Current city code. Contact information Amount of opening account. Birth day date. Date when account is created. occupation Total monthly income of

customer. emailid address integer integer Not null Not null email address Full address

Authentication
Column Name User_id Password Data Type integer integer Constraint Not null Not null Description Unique user name for login password

Loan

Column Name customerid Full name interest type

Date Type integer integer integer

Constraint Foreign key Not null Not null

Description User name Full name of employee Give status interest

monthly or yearly
37

loan amount MODE OF DISBURSEMEN T

integer integer

Not null Not null

Cash amount of loan. MODE OF DISBURSEMENT

38

 Implementation environment

Program modules specification

Security features

Implementation environment The C# Language

C# (pronounced C-Sharp) is no doubt the language of choice in the .Net environment. It is a whole new language Free of the backward compatibility curse with a whole bunch of new, exciting and promising features. It is an Object Oriented Programming language and has at its core, many similarities to Java, C++ and VB. In fact, C# combines the power and efficiency of C++, the simple and clean OO design of Java and the language Simplification of Visual Basic. Like Java, C# also does not allow multiple inheritance or the use of pointers (in safe/managed code), but does Provide garbage memory collection at runtime, type and memory access checking. However, contrary to JAVA, C# maintains the unique useful operations of C++ like operator overloading, enumerations, pre-processor Directives, pointers (in unmanaged/un-safe code), function pointers (in the form of delegates) and promises to have Template support in the next versions. Like VB, it also supports the concepts of properties (context sensitive fields). In addition to this, C# comes up with some new and exciting features such as reflections, attributes, marshalling, Removing, threads, streams, data access with ADO.Net and more The .Net Architecture and .Net Framework In the .Net Architecture and the .Net Framework there are different important terms and concepts which we will Discuss one by one:The Common Language Runtime (CLR)

39

The most important concept of the .Net Framework is the existence and functionality of the .Net Common Language Runtime (CLR) also called .Net Runtime for short. It is a framework layer that resides above the OS and Handles the execution of all the .Net applications. Our programs don't directly communicate with the OS but go Through the CLR. Our .Net Applications Common Language Runtime (CLR) Windows OS MSIL (Microsoft Intermediate Language) Code When we compile our .Net Program using any .Net compliant language (such as C#, VB.Net or C++.Net) our Source code does not get converted into the executable binary code, but to an intermediate code known as MSIL Which is interpreted by the Common Language Runtime? MSIL is operating system and hardware independent Code. Upon program execution, this MSIL (intermediate code) is converted to binary executable code (native Code). Cross language relationships are possible as the MSIL code is similar for each .Net language. Language Just In Time Code in any .Net MSIL Executable Compiler Compiler Language Code Native Code Compile time run time 18 Programmers Heaven: C# School Just In Time Compilers (Jitters) When our IL compiled code needs to be executed, the CLR invokes the JIT compiler, which compile the IL code to Native executable code (.exe or .dll) that is designed for the specific machine and OS. JITers in many ways are different from traditional compilers as they compile the IL to native code only when desired; e.g., when a function is called, the IL of the function's body is converted to native code just in time. So, the part of code that is not used by that particular run is never converted to native code. If some IL code is converted to native code, then the next time it's needed, the CLR reuses the same (already compiled) copy without re-compiling. So, if a program runs for some time (assuming that all or most of the functions get called), then it won't have any just-in-time performance penalty. As JITers are aware of the specific processor and OS at runtime, they can optimize the code extremely efficiently resulting in very robust applications. Also, since a JIT compiler knows the exact current state of executable code, they can also optimize the code by in-lining small function calls (like replacing body of small function when its called in a loop, saving the function call time). Although Microsoft stated that C# and .Net are not competing with languages like C++ in efficiency and speed of execution, JITers can make your code even faster than C++ code in some cases when the program is run over an extended period of time (like web-servers).

40

The Framework Class Library (FCL) The .Net Framework provides a huge Framework (or Base) Class Library (FCL) for common, usual tasks. FCL contains thousands of classes to provide access to Windows API and common functions like String Manipulation, Common Data Structures, IO, Streams, Threads, Security, Network Programming, Windows Programming, Webm Programming, Data Access, etc. It is simply the largest standard library ever shipped with any development environment or programming language. The best part of this library is they follow extremely efficient OO design (design patterns) making their access and use very simple and predictable. You can use the classes in FCL in your program just as you would use any other class. You can even apply inheritance and polymorphism to these classes. The Common Language Specification (CLS) Earlier, we used the term '.Net Compliant Language' and stated that all the .Net compliant languages can make use of CLR and FCL. But what makes a language a '.Net compliant' language? The answer is the Common Language Specification (CLS). Microsoft has released a small set of specifications that each language should meet to qualify as a .Net Compliant Language. As IL is a very rich language, it is not necessary for a language to implement all the IL functionality; rather, it merely needs to meet a small subset of CLS to qualify as a .Net compliant language. This is the reason why so many languages (procedural and OO) are now running under the .Net umbrella. CLS basically addresses language design issues and lays down certain standards. For instance, there shouldn't be any global function declarations, no pointers, no multiple inheritance and things like that. The important point to note here is that if you keep your code within the CLS boundary, your code is guaranteed to be usable in any other .Net language. The Common Type System (CTS) .Net also defines a Common Type System (CTS). Like CLS, CTS is also a set of standards. CTS defines the basic data types that IL understands. Each .Net compliant language should map its data types to these standard data types. This makes it possible for the 2 languages to communicate with each other by passing/receiving parameters to and from each other. For example, CTS defines a type, Int32, an integral data type of 32 bits (4 bytes) which is mapped by C# through int and VB.Net through its Integer data type.

Garbage Collection (GC) CLR also contains the Garbage Collector (GC), which runs in a low-priority thread and checks for un-referenced, dynamically allocated memory space. If it finds some data that is no longer referenced by any variable/reference, it re-claims it and returns it to the OS. The presence of a standard Garbage Collector frees the programmer from keeping track of dangling data. Ask any C++ programmer how big a relief it is! The .Net Framework

41

The .Net Framework is the combination of layers of CLR, FCL, Data and XML Classes and our Windows, Web applications and Web Services. A diagram of the .Net Framework is presented below for better understanding. Our .Net Applications (Win Forms, Web Applications, Web Services) Data (ADO.Net) and XML Library Framework Class Library (FCL) (IO, Streams, Sockets, Security, Reflection, UI) Common Language Runtime (CLR) (Debugger, Type Checking, JIT, exceptions, GC) Windows Os

Security features
Security is an important aspect of software development nowadays, and C# in its very architecture has this feature, present in various forms. There are some holy-water droplets to drink before eating the topic to self-satisfaction. And those include

1.

- Permissions
2.

- Type-safety
3.

- Security Policy
4.

- Principal
5.

- Authentication
6.

- Authorization

42

The .NET Framework offers code access security and role-based security to help address security concerns about mobile code and to provide support that enables components to make decisions about what users are authorized to do. These security mechanisms are designed to have a simple, consistent model so that developers familiar with code access security can easily use role-based security, and vice-versa.

Program module specification:-

1 ) LOGIN FORM:-

43

2) MAIN FORM:-3) CREATE ACCOUNT:-

4) Credit:-

5) Debit:-

6) Emi calculation:44

7) Loan:8) TRANSFER BALANCE: -

9) Bank account:-

45

 Limitation

Enhancements

LIMITATIONS AND FUTURE ENHANCEMENTS

LIMITATIONS:

There are some limitations of this project which are as listed below:
1. It requires the c sharp plug-in, which isn't available by default on all computers.

2. In this project if user want to make an account then user must know refereed of that Banking system .otherwise user cant make an account.

3. User must deposit more than RS: 1000 for creating an account.

46

FUTURE ENHANCEMENTS:

We would like to add some functionality in this banking system;

1. Admin user can modify update and delete accounts through admin password and other

user can only view profile credit and debit and done some transaction but cant done any updating and deletion in its particular account.

2. We would like to add student loan in this banking system for special student user which users studied in various fields.

47

I.

II.

III.

IV.

V.

http://www.google.com http://www.wikipedia.com http://www.pdf4me.org http://www.scribd.com http://www.findadoc.com

48