ATM SYSTEM

By p.prasath p.prabhu ranjith Of

P.A.COLLEGE OF ENGINEERING AND TECHNOLOGY A PROJECT REPORT

Submitted to the

FACULTY OF COMPUTER SCIENCE AND ENGINEERING

In partial fulfillment of the requirements For the award of the degree Of

BACHELOR OF ENGINEERING IN COMPUTER SCIENCE AND ENGINEERING JULY, 2011

CERTIFICATE

BONAFIDE CERTIFICATE

Certified that this project report titled ATM SYSTEM is the bonafide work of p.prasath,p.prabhu,ranjith who carried out the research under my supervision. Certified further, that to best of our knowledge the work reported herein does not form part of any other project report or dissertation on the basis of which a degree or award was conferred on an earlier occasion on this or any other batch.

______________________ Signature N.Suba Rani M.E ., Head of the Department, P.A .College of Engineering and Technology, Pollachi . Submitted for the viva voce examination held at P.A .College of Engineering and Technology on ____________

_______________________ INTERNAL EXAMINER

______________________ EXTERNAL EXAMINER

ABSTRACT

ABSTRACT
ATM System allows customers to conduct financial transactions on a secure website operated by their retail or virtual bank, credit union or building society.Online banking solutions have many features and capabilities in common, but traditionally also have some that are application specific.The common features fall broadly into several categories such as Transactional (e.g., performing a financial transaction such as an account to account transfer, paying a bill, wire transfer... and applications... apply for a loan, new account, etc.), Non-transactional (e.g., online statements, check links, cobrowsing, chat), Bank statements, Financial Institution Administration , Support of multiple users having varying levels of authority, Transaction approval process, Wire transfer. Features commonly unique to Internet banking which include Personal financial management support, such as importing data into personal accounting software. Some online banking platforms support account aggregation to allow the customers to monitor all of their accounts in one place whether they are with their main bank or with other institutions.

ACKNOWLEDGEMENT

ACKNOWLEDGEMENT
First we thank the management for providing the necessary lab facilities.thanks to our Chairman P.Appukutty M.E.,FIV, P.A Institution, and Principal Dr.R.K.Suresh, for providing the facilities to complete the project efficiently and quickly.

We also thank Mrs.N.Suba Rani M.E., Head, Department of Computer Science and Engineering for her constant support and encouragement throughout the project.

We would like to express our thanks to the project coordinator Mrs.N.Suba Rani M.E., for her valuable guidance suggestions given during various times to complete the project.

Lastly, we would like to express our thanks to all the lab technicians for their providing all equipments and software to work efficiently in their tight schedule.

TABLE OF CONTENTS

TABLE OF CONTENTS

Abstract List of Tables List of Figures Chapters 1.Introduction 1.1 Objective 1.2 Organisation 2.UML diagram description 2.1 Use case diagram 2.2 Class diagram 2.3 Sequence diagram 2.4 Collaboration diagram 2.5 State chart diagram 2.6 Activity diagram 2.7 Component diagram 2.8 Deployment diagram 3.UML diagram for banking system 3.1Use case diagram 3.2 Activity diagram 3.3 Sequence diagram 3.4 Collaboration diagram 3.5Class diagram 3.6 State chart diagram 4.Implementation and coding 4.1 Requirements : 4.2 Software requirement speciation document:(srs)

4.3Coding 4.3.1 Depositmoney 4.3.2 New account 4.3.3 Find account 4.3.4 Withdrawl 4.3.5 View customer 4.3.6 Main class 5.Result screen shots : 5.1 Opening Atm window 5.2 Creating a new account 5.3 Depositing the money 5.4 Withdrawing the money 5.5 Deleting the account holder 5.6 Searching customer one by one 5.7 View account one by one 5.8 View all accounts 6. Conclusion References

LIST OF TABLES

LIST OF TABLES

TABLE NO.

TITLE

PAGE NO.

2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8

Use case graphical notation Class graphical notation Sequence graphical notation Collaboration graphical notation State chart graphical notation Activity graphical notation Component graphical notation Deployment graphical notation

LIST OF FIGURES
LIST OF FIGURES

FIGURE NO.
3.1 3.2 3.3 3.4 3.5 3.6

TITLE
Use case diagram Activity diagram Sequence diagram Collaboration diagram Class diagram State chart diagram

PAGE NO.

CHAPTER 1

INTRODUCTION
CHAPTER 1

INTRODUCTION
An Automated Teller Machine (ATM) allows customers to perform banking transactions anywhere and at anytime without the need of human teller. By using a debit or ATM card at an ATM, individuals can withdraw cash from checking or savings accounts, make a deposit or transfer money from one account to another or perform other functions. You can also get cash advances using a credit card at an ATM. Individuals should be aware that many banks charge transaction fees generally ranging from Rs 50-150 per transaction - for using another banks ATM.

The ATM is online with the bank, that is, each transaction will be authorised by the bank ondemand and directly debited from the account's owner. The ATM works as follows. First, the client will insert his/her client card in the ATM and then the ATM will ask for a Personal Identification Number (PIN) , if the number is entered incorrectly several times in a row, most ATMs will retain the card as a security precaution to prevent an unauthorised user from working out the PIN by pure guesswork. Once the correct PIN is given, the

ATM will ask for the amount of money to be withdrawn. If the amount is available and if the client has enough money on his credit then the said amount of money will be paid. Whether the amount of money is payable or not, i.e. the ATM has enough cash but could be the case the ATM has no change for that amount, will be also checked. Once the money is offered to the client a countdown is started, i.e. the client has a determined amount of time to pick up the money. If this timeout is over, the money will be collected by the ATM and the transaction will be rolled back.

The class Card_input has the methods for reading the code of the client's card and for ejecting the card from the ATM. The class Card_input will interact through the Controller with the class Terminal, where the methods Req_PIN and Req_amount are defined, in order to get the PIN of the user and to verify if the given PIN is correct or not. The class Card will have the information of the cardholder, that is, the Card_number, PIN, and Account_number. The Controller will interact with Bank using the information of the cardholder in order to get the authorization to pay (or not) the requested amount. The bank_interface will send the request to the Accounting class, which belongs to the Bank package, in order to call the Debit method of the accounting class3. The Accounting class has the methods Rollback, Authorization and Debit which directly

interact with the Accounts class. Rollback is for roll back a transaction (for the case anything is wrong) and should leave the account and the teller machine in the original state; Authorization will authorize or not an operation and Debit will extract the requested amount of money from the account in

the case the operation is authorized. ATMs are generally reliable, but if they do go wrong customers will be left without cash until the following morning or whenever they can get to the bank during opening hours. Of course not all errors are to the detriment of customers; there have been cases of machines giving out money without debiting the account or giving out a higher denomination of note by mistake. There are also many "phantom withdrawals" from ATMs, which banks often claim are the result of fraud by customers. Phantom withdrawals are considered to be a problem generated by dishonest insiders by most other observers.

HISTORY OF ATM
As is often the case with inventions, many inventors contribute to the history of an invention. In the case of the ATM, Don Wetzel invented the first successful and modern ATM in the USA, however he was not first inventor to create an ATM. In 1939, Luther George Simjian started patenting an earlier and not-so-successful version of an ATM. An automatic teller machine or ATM allows a bank customer to conduct their banking transactions from almost every other ATM machine in the world. Don Wetzel was the co-patentee and chief conceptualist of the automated teller machine, an idea he said he thought of while waiting in line at a Dallas bank.

At the time (1968) Wetzel was the Vice President of Product Planning at Docutel, the company that developed automated baggage-handling equipment. The other two inventors listed on the patent were Tom Barnes, the chief mechanical engineer and George Chastain, the electrical engineer. It took five million dollars to develop the ATM. The concept of the modern ATM first began in 1968, a working prototype came about in 1969 and Docutel was issued a patent in 1973. The world's first ATM was installed in Enfield Town in the London Borough of Enfield, London on June 27 1967. The first working ATM was installed in a New York based Chemical Bank. The first ATMs were off-line machines, meaning money was not automatically withdrawn from an account. The bank accounts were not (at that time) connected by a computer network to the ATM. Therefore, banks were at first very exclusive about who they gave ATM privileges to. Giving them only to credit card holders (credit cards were used before ATM cards) with good banking records. Wetzel, Barnes and Chastain developed the first real ATM cards, cards with a magnetic strip and a personal ID number to get cash. ATM cards had to be different from credit cards (then without magnetic strips) so account information could be included.

CHAPTER 2

UML DIAGRAM DESCRIPTION

CHAPTER 2 UML DIAGRAM DESCRIPTION
2.1 USE CASE DIAGRAM

OBJECTIVE
To draw the use-case diagrams using Rational Rose. DESCRIPTION Use-case diagrams identify the functionality provided by the system (use-cases), the users who interact with the system (actors), and the association between the users and the functionality. Use-cases are used in the Analysis phase of software development to

articulate the high level requirements of the system. A use-case diagram may depict all or some of the use- cases of a system. Use-case diagrams can be used during analysis to capture the system requirements and to understand how the system should work. Use-cases extend beyond pictorial diagrams. In fact, text-based use-case descriptions are often used to supplement diagrams, and explore use-case functionality in detail. The uses relationship is very much like a function call or a subroutine. The usecase being used in this fashion is called an abstract use-case because it cannot exist on its own but must be used by other use-cases. The other interesting relationship is the extends relationship. This represents a change to the use-case that could be addressed in other use-cases. Use-cases are powerful tools for analysts to use when partitioning the functionality of a system. Use-case relationships and the corresponding diagrams help analysts to structure use-cases such that their textual descriptions contain a minimum of redundant information. ALGORITHM 1. Define the actors. 2. Determine the events that are necessary for developing a system. 3. Represent the communication relationship of an actor in the system by connecting the actor symbol to the use-case symbol with a solid path. 4. Represent the Uses and Extends relationship if required. 5. Use the necessary tools for developing the Library Management System.

Graphical Notation The basic components of Use-case diagrams are the Actor, the Use-case and the Association.

Actor

An Actor is a user of the system, and is depicted using a stick figure. The role of the user is written beneath the icon. Actors are not limited to users. If a system communicates with another application and expects input or delivers output then that application can also be considered an actor. A Use-case is functionality provided by the system, typically described as verb + object (eg: Register Car, Delete User). Use-cases are depicted with an ellipse. The name of the usecase is written within the ellipse. Associations are used to link Actors with Usecases, and indicate that an Actor participates in the Use-case in some form. A line connecting the Actor and Use-case depicts associations.

Actor Role Name

Use-case

Us e c as e N am e

Association

2.2 CLASS DIAGRAM

OBJECTIVE To draw the class diagram and to describe the relationships that exists between the classes using Rational Rose. DESCRIPTION Class diagrams identify the class structure of a system, including the properties and methods of each class. It specifies the various relationships that can exist between classes, such as an inheritance. The Class diagram is one of the most widely used diagrams from the UML specification. Part of the popularity of Class diagrams is the fact that many CASE tools, such as Rational Rose, will provide clarity of the designing process. We can create one or more class diagrams to depict the classes at the top level of the current model; such class diagrams are themselves contained by the top level of the current model. We can also create one or more class diagrams to depict classes contained by each package in the model; such class diagrams are themselves contained by the package enclosing the classes they depict; the icons representing logical packages and classes in class diagrams. We can change properties or relationships by editing the specification or modifying the icon on the diagram. Cardinality is the representation of how many instances of one class may relate to an instance of an associated class. Classes are typically modeled as rectangles with three sections: the top section for the name of the class, the middle section for the attributes of the class, and the bottom section for the methods of the class ALGORITHM 1. Identify the various classes that behave as main to perform various functions in the system 2. Define all its attributes and what operation they perform. 3. Identify various relationships among the classes. 4. The relationship between a class and its subclass is represented by generalization.

Graphical Notation The basic components on a Class diagram are classes and the relationships between them. Classes are the building blocks in objectoriented programming. A class is depicted using a rectangle divided into 3 sections. The top section is the name of the class. The middle section defines the properties of the class. The bottom section lists the methods of the class. Object diagrams can contain associations as well. Often, the constraints, relationship details and multiplicity rules found in the Class diagram are left out to concentrate the diagram on the objects and their properties. Associations between objects specified using a line joining the two objects. When a class uses another class, perhaps as a member variable or a parameter, and so depends on that class, a Dependency relationship is formed. The Dotted arrow indicates a Dependency relationship. Aggregations indicate a whole-part relationship Aggregation and are known as has-a relationships. A line with a hollow diamond indicates an Aggregation relationship. The Generalization relationship is the equivalent of an inheritance relationship in Generalization object-oriented terms. (is-a relationship). An arrow indicates a Generalization relationship with a hollow arrowhead pointing to the base or parent class.

SiteConfig SqlDSN : string add()

Class

Association

Dependency

2.3 SEQUENCE DIAGRAM OBJECTIVE To draw the sequence diagram using Rational Rose. DESCRIPTION A sequence diagram is a graphical view of a scenario that shows object interaction in a time-based sequence what happens first, what happens next. Sequence diagrams demonstrate the behavior of objects in a use-case by describing the objects and the messages they pass. Sequence diagrams are normally associated with use-cases. Sequence diagrams are closely related to collaboration diagrams and both are alternate representations of an interaction. The main differences between sequence and collaboration diagrams: sequence diagrams show time-based object interaction while collaboration diagrams show how objects associate with each other. Sequence diagram model the flow of logic within our system in a visual manner, enabling to document and validate the logic, and are commonly used for both analysis and design purposes. Sequence diagrams are the most popular for dynamic modeling, which focuses on identifying the behavior within a system. The main purpose of a sequence diagram is to define event sequences that result in some desired outcome. The focus is less on messages themselves and more on the order in which messages occur; nevertheless, most sequence diagrams will communicate what messages are sent between a system's objects as well as the order in which they occur.

ALGORITHM
1. Identify the objects in the diagram according to the system to be drawn. 2. Identify the sequence of message transfer between the objects. 3. Determine how the message is passed between two objects and how other objects respond. 4. Create the sequence diagram based on the information from 1 and 2 with the tools provided. 5. At the end of object lifeline include the destruction object.

Graphical Notation In a Sequence diagram, objects and actors are listed as columns with vertical lifelines indicating the lifetime of the object over time. Objects are instances of classes, and are arranged horizontally. The pictorial representation for an object is a class (a rectangle) with the name prefixed by the object name (optional) and a semi-colon. Actors can also communicate with objects, so they too can be listed as a column. An Actor is modeled using the ubiquitous symbol, the stick figure.
A r R le N m cto o a e

: Object1

Object

Actor

Lifeline

The Lifeline identifies the existence of the object over time. The notation for a Lifeline is a vertical dotted line extending from an object.

Activation

Activations, modeled as rectangular boxes on the lifeline, indicate when the object is performing an action.

Message

Messages, modeled as horizontal arrows between Activations, indicate the communications between objects.

Start

2.4 COLLABORATION DIAGRAM

OBJECTIVE To draw the collaboration diagram using Rational Rose. DESCRIPTION A collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior of individual objects as well as the overall operation of the system in real time. Collaboration diagrams show a spatial organization of components and interactions rather than concentrating on the sequence of the interactions. A collaboration diagram shows an interaction organized around the objects in the interaction and their links to each other. Unlike a Sequence diagram, a collaboration diagram shows the relationships among the objects. On the other hand, a collaboration diagram does not show time as a separate dimension, so sequence numbers determine the sequence of messages and the concurrent threads. Objects are shown as rectangles with naming labels inside. These labels are preceded by colons and may be underlined. The relationships between the objects are shown as lines connecting the rectangles. An Object Specification enables us to display and modify the properties and relationships of an object. The information in a specification is presented textually. We can change properties or relationships by editing the specification or modifying the icon on the diagram. An actor in a collaboration diagram represents the person, software, hardware, or other agent external to the system that is interacting with the system. The messages between objects are shown as arrows connecting the relevant rectangles along with labels that define the message sequencing. ALGORITHM 1. 2. 3. 4. 5. Identify the main entities or objects in the system. Link all the objects using the object link. Identify the messages transferred between the objects. Represent this message by numbers, based on the activities done by each objects. Design the collaboration diagram using the information obtained from the above with the tools provided. 2.5 STATE CHART DIAGRAM

OBJECTIVE To draw the state chart diagram using Rational Rose. DESCRIPTION State chart diagrams model the dynamic behavior of individual classes or any other kind of object. They show the sequences of states that an object goes through, the events that cause a transition from one state to another and the actions that result from a state change. State chart diagrams are closely related to activity diagrams. A state chart diagram is typically used to model the discrete stages of an objects lifetime, whereas an activity diagram is better suited to model the sequence of activities in a process.Each state represents a named condition during the life of an object during which it satisfies some condition or waits for some event. A state chart diagram typically contains one start state and multiple end states. The details of a state are shown as a set of lines of the form: condition/operation in which the conditions entry , exit , and do are, by convention, used to represent processing an entry to a state, processing whilst in a state, and processing on exit from a state. Transitions connect the various states on the diagram. A transition is a progression from one state to another and will be triggered by an event that is either internal or external to the entity being modeled. A transition may be to a superstate, in which case the flow of control begins at the initial state symbol nested within the superstate. A superstate may contain more than one set of nested states and transitions, each set separated from all other sets, and each set having its own initial state and final state symbols. These sets are considered to run concurrently. ALGORITHM 1. Identify the states in the state chart diagram. 2. The changes form one state to another state is depicted. 3. The association link is drawn between the states and the messages. 4. Terminate the process after completion. Graphical Notation

State

The State notation marks a mode of the entity, and is indicated using a rectangle with rounded corners, and the state name written inside. A Transition marks the changing of the object state, caused by an event. The notation for a Transition is an arrow, with the event name written above or below or alongside the arrow.

Start

Transition

Transition

Initial state

The Initial state is the state of an object before any transition. For objects, this could be the state when instantiated. The Initial state is marked using a solid circle. Only one initial state is allowed on a diagram. End states mark the destruction of the object whose state we are modeling. These states are drawn using a solid circle with a surrounding hollow circle.

Final state

2.6 ACTIVITY DIAGRAM

OBJECTIVE

To draw the activity diagram using Rational Rose. DESCRIPTION Activity diagram provide a way to model the workflow of a business process. Activity diagrams are very similar to a flowchart because we can model a workflow from activity to activity. An activity diagram is basically a special case of a state machine in which most of the states are activities and most of the transitions are implicitly triggered by completion of the actions in the source activities. In fact, the Activity diagram is a variation of the state diagram where the states represent operations, and the transitions represent the activities that happen when the operation is complete. The general purpose of Activity diagrams is to focus on flows driven by internal processing vs. external events. Each activity represents the performance of a group of actions in a workflow. Once the activity is complete, the flow of control moves to the next activity or state through a transition. If an outgoing transition is not clearly triggered by an event, then it is triggered by the completion of the contained actions inside the activity. A unique activity diagram feature is a swimlane that defines who or what is responsible for carrying out the activity or state. It is also possible to place objects on activity diagrams. The workflow stops when a transition reaches an end state. ALGORITHM 1. Identify the operations and transformations that are triggered by the completion of an operation, which is referred as activities. 2. Represent those activities by a rounded rectangle. 3. Link the activities by automatic transactions, represented by arrows and write the name of the transition. 4. If needed a decision which is represented by a diamond with many transitions

Graphical Notation

Activity states

Activity states mark an action by an object When an Activity state is completed, processing moves to another Activity state. Transitions are used to mark this movement. Swimlane divide activities according to objects by arranging objects in column format. The Initial State marks the entry point and the initial activity state. Final States mark the end of the modeled workflow.

Activity States

Transition

Transition

Swimlane

Initial State

Final State

Synchronization Bar

Activities often can be done in parallel. To split processing fork has been used. When multiple activities have been completed join has been used.

2.7 COMPONENT DIAGRAM

OBJECTIVE To draw the component diagram using Rational Rose. DESCRIPTION

Component diagrams fall under the category of an implementation diagram. These diagrams provide a physical view of the current model. Component diagrams illustrate the physical structure of the code, mapping the logical view of the project classes to the actual code where the logic is implemented. A component diagram shows the organizations and dependencies among software components, including source code components, binary code components, and executable components. It also shows the externally visible behavior of the components by displaying the interfaces of the components. Calling dependencies among components are shown as dependency relationships between components and interfaces on other components. Component diagram contains Component packages, Header file, Interfaces, Database, Task Specification, Package specification, Package body and Dependency relationships. Packages are useful for collecting related classes so they can be referenced more concisely in top level view drawings of the project architecture. A Component diagram in particular, is used to describe the dependencies between various software components such as the dependency between executable files and source files. There are several advantages to components that promote agility. First, components are reusable building blocks from which we can build software, increasing our productivity as a developer. Second, components can improve our testing productivity. Even though components are autonomous units they still may depend on the services provided by other components. Because of this, documenting a component's required interfaces is useful. ALGORITHM 1. Identify the software entities used in the system 2. The dependency relationship is drawn according to the system set up. 3. The link is drawn between the components. 4. Terminate the process after completion. Graphical Notation

Component

A component represents a software entity in a system. Examples include source code files, programs, documents and resource files. A component is represented using a rectangular box, with two rectangles from the left side. The notation for a dependency relationship is a dotted arrow, pointing from a component to the dependent component.

Component

Dependency

2.8 DEPLOYMENT DIAGRAM OBJECTIVE To draw the deployment diagram using Rational Rose. DESCRIPTION

Deployment diagram models the hardware used in implementing a system and the association between those hardware components. Deployment diagrams used in the design phase to document the physical architecture of a system. It is a static view of the run-time configuration of processing nodes and the components that run on those nodes. A deployment diagram shows processors, devices, and connections. Each model contains a single deployment diagram, which shows the connections between its processors and devices, and the allocation of its processes to processors. We can change properties or relationships by editing the specification or modifying the icon on the diagram. The deployment diagram specifications are automatically updated. A Deployment diagram shows how and where the system will be deployed. Physical machines and processors are reflected as nodes, and embedding nodes or artifacts can depict the internal construction. As artifacts are allocated to nodes to model the system's deployment, the allocation is guided by the use of deployment specifications. Deployment diagrams are an important element of system documentation that can assist in planning complex projects with artifacts, such as executable files, data files, XML documents, and configuration files, which will ultimately reside on separate hardware platforms. Clear and detailed deployment diagrams also allow larger teams to better understand the entire project architecture. ALGORITHM 1. Identify the processors and devices used in the deployment diagram. 2. The processors are connected according to the office set up. 3. The association link is drawn with the messages. 4. Connect the Terminals with the appropriate Server.

Graphical Notation The elements used in Deployment diagrams are Components, as we have seen in Component diagrams, Nodes that represent the physical processing resources in the system and Associations. A node represents a piece of hardware in the system. A three-dimensional cube represents this entity. An association, drawn as a solid line between two nodes, indicates a line of communication between the hardware elements

Node

Node

Association

CHAPTER 3

UML DIAGRAM FOR BANKING SYSTEM

CHAPTER 3
UML DIAGRAM FOR BANKING SYSTEM 3.1USE CASE DIAGRAM

Banker Deposit

Customer

Print Details

Delete

WithDraw Search

Diagram description : This use case diagram consists of two actors such as Banker and Customer. It consists of various use case such as Create Account, Deposit, Print Details, Withdraw, Search, Delete.

These various use cases can be accessed by both the actors.

3.2 ACTIVITY DIAGRAM

A cc ount No

A ccount Nam e

D ate O f C re a t io n

In it a l A m o u n t

A ccount No A m o u n t T ra n s a c ti o n s

S e a rc h P rin t D e t a ils A ccount No

W it h D ra w D e le t e D e p o s it Y es D e le t e A c c ount Y es Reduc e A m ount In c r e a s e A m ount

P rin t A c c o u n t D e t a ils

Diagram description : In this we can create a new customer, delete the old or current customer, print the details of each customer details.

3.3 SEQUENCE DIAGRAM

: Banker

: Bank Boundary 1: interaction

: Bank Control

: Bank Entity

: Customer

2: Request to create account 3: Account No 4: Acc Name 5: Date Of Creation 6: Store Acc No 7: Display Account details 8: Create Account

9: View Details 10: Display 11: With Draw 12: Reduce Amount And Display 13: Deposit 14: Increase amount and Display 15: Search 16: Display to Bank

Diagram description : This diagram shows the sequential flow of the datas between the customer and the banker.

3.4 COLLABORATION DIAGRAM

1 5 : S e a rc h

1 6 : D is p la y t o B a n k : B ank er

: B a n k C o n tro l

1 : in t e ra c t i o n

1 0 : D is p la y 1 2 : R e d u c e A m o u n t A n d D is p l a y 1 4 : In c r e a s e a m o u n t a n d D is p la y 2 : R e q u e s t to c re a te a c c o u n 9 : V ie w D e 6 a: i ls t o r e A c c N o t S

: B a n k B o u n d a ry

7 : D is p l a y A c c o u n t d e t a il s 1 1 : W i th D ra w 1 3 : D e p o s it 4: A cc N am e 5 : D a t e O f C r e a t io n : C u s to m e r

: B a n k E n tity

Diagram description : After the creation of the sequential diagram while pressing the F5 key we get the required collaboration diagram for our project.

3.5CLASS DIAGRAM

Create Account Customer Name Date Of Creation Account No 1 initial Amount 1 Create Acc() 1 1 1

Deposit Acc No Customer Name Date Of Deposit Amount Insert Amount() Search Acc Acc No Search Customer()

* W ithDraw Account No Customer Name Date Of W ithDraw Amount Draw Money()

View Details Acc No Fetch Details()

1 Delete Account Account No Del Acc()

Diagram description : The class diagram shows the various class that are to be created for our project. It also gives us the various methods that are being to be included in our project.

3.6 STATE CHART DIAGRAM

S ea rc h W it h D ra w C re at e ac c oun t D e p o s it

V iew D e t ails

D e le t e

Diagram description : This state diagram consists of the start and the stop state. In this it shows the entire operations that are to be performed in our project.

CHAPTER 4

IMPLEMENTATION AND CODING

CHAPTER 4 IMPLEMENTATION AND CODING

4.1 Requirements : The system implemented using the following hardware and software configuration. Hardware Configuration: Processor: Intel Core 2 Duo 2.67 Ghz Ram: 2 GB Hard disc: 250 GB Software Configuration: Front End: JAVA Back End: File Systems 4.2 Software Requirement Speciation Document:(SRS) A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements, which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).

4.3 CODING
MAIN PAGE
Public Class Frm_MainMenu Dim id As Integer Private Sub btnExit_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnExit.Click Frm_PinCode.txt_code.Clear() Frm_PinCode.Enabled = True Frm_PinCode.Show() Me.Close() End Sub Private Sub btnBalanceInquiry_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnBalanceInquiry.Click Me.GroupBox1.Show() End Sub Private Sub Frm_MainMenu_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load Frm_PinCode.Enabled = False GroupBox1.Visible = False End Sub Private Sub btnSettings_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnSettings.Click GroupBox1.Visible = False Frm_PinCode.values() Frm_Settings.Show() GroupBox1.Visible = False End Sub Private Sub btnDepositCash_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnDepositCash.Click Frm_Deposit_Cash.Show() GroupBox1.Visible = False End Sub Private Sub btnGetCash_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnGetCash.Click Frm_Withdraw_Cash.Show() GroupBox1.Visible = False End Sub Private Sub btnTransfer_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnTransfer.Click Frm_Transfer_Cash.Show() GroupBox1.Visible = False End Sub

Private Sub btnTransaction_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnTransaction.Click Frm_Transaction_History.Show() GroupBox1.Visible = False End Sub End Class

4.3.2 PIN CODE VERIFICATION

Global.Microsoft.VisualBasic.CompilerServices.DesignerGenerated()> _ Partial Class Frm_PinCode Inherits System.Windows.Forms.Form 'Form overrides dispose to clean up the component list. <System.Diagnostics.DebuggerNonUserCode()> _ Protected Overrides Sub Dispose(ByVal disposing As Boolean) Try If disposing AndAlso components IsNot Nothing Then components.Dispose() End If Finally MyBase.Dispose(disposing) End Try End Sub 'Required by the Windows Form Designer Private components As System.ComponentModel.IContainer 'NOTE: The following procedure is required by the Windows Form Designer 'It can be modified using the Windows Form Designer. 'Do not modify it using the code editor. <System.Diagnostics.DebuggerStepThrough()> _ Private Sub InitializeComponent() Me.components = New System.ComponentModel.Container Me.CloudLabel1 = New CloudToolkitN6.CloudLabel Me.CloudLabel2 = New CloudToolkitN6.CloudLabel Me.btnOK = New CloudToolkitN6.CloudDesktopButton Me.btnClear = New CloudToolkitN6.CloudDesktopButton Me.txt_code = New CloudToolkitN6.CloudTextBox Me.btnExit = New CloudToolkitN6.CloudDesktopButton Me.ErrorProvider1 = New System.Windows.Forms.ErrorProvider(Me.components) Me.CloudDigitalClock1 = New CloudToolkitN6.CloudDigitalClock Me.btnAdmin = New CloudToolkitN6.CloudDesktopButton Me.btnAbout = New CloudToolkitN6.CloudDesktopButton CType(Me.ErrorProvider1, System.ComponentModel.ISupportInitialize).BeginInit() Me.SuspendLayout() ' 'CloudLabel1 ' Me.CloudLabel1.Anchor = CType((System.Windows.Forms.AnchorStyles.Top Or

System.Windows.Forms.AnchorStyles.Bottom), System.Windows.Forms.AnchorStyles) Me.CloudLabel1.AutoSize = True Me.CloudLabel1.BackColor = System.Drawing.Color.Transparent Me.CloudLabel1.Font = New System.Drawing.Font("Calibri", 20.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.CloudLabel1.ForeColor = System.Drawing.Color.White Me.CloudLabel1.Location = New System.Drawing.Point(193, 18) Me.CloudLabel1.Name = "CloudLabel1" Me.CloudLabel1.Size = New System.Drawing.Size(315, 33) Me.CloudLabel1.TabIndex = 0 Me.CloudLabel1.Text = "Welcome To ATM Pakistan" ' 'CloudLabel2 ' Me.CloudLabel2.Anchor = System.Windows.Forms.AnchorStyles.None Me.CloudLabel2.AutoSize = True Me.CloudLabel2.BackColor = System.Drawing.Color.Transparent Me.CloudLabel2.Font = New System.Drawing.Font("Calibri", 18.0!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.CloudLabel2.ForeColor = System.Drawing.Color.White Me.CloudLabel2.Location = New System.Drawing.Point(103, 152) Me.CloudLabel2.Name = "CloudLabel2" Me.CloudLabel2.Size = New System.Drawing.Size(156, 29) Me.CloudLabel2.TabIndex = 1 Me.CloudLabel2.Text = "Enter Your Pin" ' 'btnOK ' Me.btnOK.Anchor = System.Windows.Forms.AnchorStyles.None Me.btnOK.AnimationSpeed = 5 Me.btnOK.BackColor = System.Drawing.Color.Transparent Me.btnOK.BackgroundOpacity = 100 Me.btnOK.BackgroundOpacity_MouseDown = 170 Me.btnOK.BorderColor = System.Drawing.Color.White Me.btnOK.BorderOpacity = 170 Me.btnOK.BorderWidth = 1 Me.btnOK.ControlText = "Ok" Me.btnOK.CornerRadius = 12 Me.btnOK.Cursor = System.Windows.Forms.Cursors.Hand Me.btnOK.DrawBlackTextBackground = True Me.btnOK.FillColor = System.Drawing.Color.FromArgb(CType(CType(192, Byte), Integer), CType(CType(255, Byte), Integer), CType(CType(255, Byte), Integer)) Me.btnOK.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.btnOK.ForeColor = System.Drawing.Color.White Me.btnOK.Icon = Global.ATM.My.Resources.Resources._492 Me.btnOK.Location = New System.Drawing.Point(247, 284) Me.btnOK.Margin = New System.Windows.Forms.Padding(4, 4, 4, 4) Me.btnOK.Name = "btnOK" Me.btnOK.Size = New System.Drawing.Size(120, 87) Me.btnOK.TabIndex = 2 '

'btnClear ' Me.btnClear.Anchor = System.Windows.Forms.AnchorStyles.None Me.btnClear.AnimationSpeed = 5 Me.btnClear.BackColor = System.Drawing.Color.Transparent Me.btnClear.BackgroundOpacity = 100 Me.btnClear.BackgroundOpacity_MouseDown = 170 Me.btnClear.BorderColor = System.Drawing.Color.White Me.btnClear.BorderOpacity = 170 Me.btnClear.BorderWidth = 1 Me.btnClear.ControlText = "Clear" Me.btnClear.CornerRadius = 12 Me.btnClear.Cursor = System.Windows.Forms.Cursors.Hand Me.btnClear.DrawBlackTextBackground = True Me.btnClear.FillColor = System.Drawing.Color.FromArgb(CType(CType(192, Byte), Integer), CType(CType(255, Byte), Integer), CType(CType(255, Byte), Integer)) Me.btnClear.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.btnClear.ForeColor = System.Drawing.Color.White Me.btnClear.Icon = Global.ATM.My.Resources.Resources.looknfeel Me.btnClear.Location = New System.Drawing.Point(375, 284) Me.btnClear.Margin = New System.Windows.Forms.Padding(4, 4, 4, 4) Me.btnClear.Name = "btnClear" Me.btnClear.Size = New System.Drawing.Size(120, 87) Me.btnClear.TabIndex = 3 ' 'txt_code ' Me.txt_code.Anchor = System.Windows.Forms.AnchorStyles.None Me.txt_code.Font = New System.Drawing.Font("Microsoft Sans Serif", 14.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.txt_code.Location = New System.Drawing.Point(297, 152) Me.txt_code.MaxLength = 4 Me.txt_code.Name = "txt_code" Me.txt_code.PasswordChar = Global.Microsoft.VisualBasic.ChrW(42) Me.txt_code.Size = New System.Drawing.Size(184, 29) Me.txt_code.TabIndex = 1 Me.txt_code.TextRenderingMode = System.Drawing.Text.TextRenderingHint.AntiAlias ' 'btnExit ' Me.btnExit.Anchor = CType((System.Windows.Forms.AnchorStyles.Bottom Or System.Windows.Forms.AnchorStyles.Right), System.Windows.Forms.AnchorStyles) Me.btnExit.AnimationSpeed = 5 Me.btnExit.BackColor = System.Drawing.Color.Transparent Me.btnExit.BackgroundOpacity = 100 Me.btnExit.BackgroundOpacity_MouseDown = 170 Me.btnExit.BorderColor = System.Drawing.Color.White Me.btnExit.BorderOpacity = 170 Me.btnExit.BorderWidth = 1

Me.btnExit.ControlText = "Exit" Me.btnExit.CornerRadius = 12 Me.btnExit.Cursor = System.Windows.Forms.Cursors.Hand Me.btnExit.DrawBlackTextBackground = True Me.btnExit.FillColor = System.Drawing.Color.FromArgb(CType(CType(192, Byte), Integer), CType(CType(255, Byte), Integer), CType(CType(255, Byte), Integer)) Me.btnExit.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.btnExit.ForeColor = System.Drawing.Color.White Me.btnExit.Icon = Global.ATM.My.Resources.Resources.DeleteRed2 Me.btnExit.Location = New System.Drawing.Point(609, 377) Me.btnExit.Margin = New System.Windows.Forms.Padding(4, 4, 4, 4) Me.btnExit.Name = "btnExit" Me.btnExit.Size = New System.Drawing.Size(120, 87) Me.btnExit.TabIndex = 5 ' 'ErrorProvider1 ' Me.ErrorProvider1.ContainerControl = Me ' 'CloudDigitalClock1 ' Me.CloudDigitalClock1.Anchor = CType((System.Windows.Forms.AnchorStyles.Top Or System.Windows.Forms.AnchorStyles.Right), System.Windows.Forms.AnchorStyles) Me.CloudDigitalClock1.BackColor = System.Drawing.Color.Transparent Me.CloudDigitalClock1.ColorLower_1 = System.Drawing.Color.Transparent Me.CloudDigitalClock1.ColorLower_2 = System.Drawing.Color.Transparent Me.CloudDigitalClock1.ColorUpper_1 = System.Drawing.Color.Transparent Me.CloudDigitalClock1.ColorUpper_2 = System.Drawing.Color.Transparent Me.CloudDigitalClock1.Cursor = System.Windows.Forms.Cursors.Hand Me.CloudDigitalClock1.DateColor = System.Drawing.Color.White Me.CloudDigitalClock1.DateFont = New System.Drawing.Font("Segoe UI", 14.0!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Pixel) Me.CloudDigitalClock1.DrawDate = True Me.CloudDigitalClock1.Location = New System.Drawing.Point(458, 2) Me.CloudDigitalClock1.Name = "CloudDigitalClock1" Me.CloudDigitalClock1.NumberColor = System.Drawing.Color.White Me.CloudDigitalClock1.NumberFont = New System.Drawing.Font("Segoe UI", 50.0!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Pixel) Me.CloudDigitalClock1.Size = New System.Drawing.Size(271, 99) Me.CloudDigitalClock1.TabIndex = 6 ' 'btnAdmin '

Me.btnAdmin.Anchor = CType((System.Windows.Forms.AnchorStyles.Bottom Or System.Windows.Forms.AnchorStyles.Left), System.Windows.Forms.AnchorStyles) Me.btnAdmin.AnimationSpeed = 5 Me.btnAdmin.BackColor = System.Drawing.Color.Transparent Me.btnAdmin.BackgroundOpacity = 100 Me.btnAdmin.BackgroundOpacity_MouseDown = 170 Me.btnAdmin.BorderColor = System.Drawing.Color.White Me.btnAdmin.BorderOpacity = 170 Me.btnAdmin.BorderWidth = 1 Me.btnAdmin.ControlText = "Admin" Me.btnAdmin.CornerRadius = 12 Me.btnAdmin.Cursor = System.Windows.Forms.Cursors.Hand Me.btnAdmin.DrawBlackTextBackground = True Me.btnAdmin.FillColor = System.Drawing.Color.FromArgb(CType(CType(192, Byte), Integer), CType(CType(255, Byte), Integer), CType(CType(255, Byte), Integer)) Me.btnAdmin.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.btnAdmin.ForeColor = System.Drawing.Color.White Me.btnAdmin.Icon = Global.ATM.My.Resources.Resources.linuxconf Me.btnAdmin.Location = New System.Drawing.Point(0, 377) Me.btnAdmin.Margin = New System.Windows.Forms.Padding(4, 4, 4, 4) Me.btnAdmin.Name = "btnAdmin" Me.btnAdmin.Size = New System.Drawing.Size(120, 87) Me.btnAdmin.TabIndex = 7 ' 'btnAbout ' Me.btnAbout.AnimationSpeed = 5 Me.btnAbout.BackColor = System.Drawing.Color.Transparent Me.btnAbout.BackgroundOpacity = 100 Me.btnAbout.BackgroundOpacity_MouseDown = 170 Me.btnAbout.BorderColor = System.Drawing.Color.White Me.btnAbout.BorderOpacity = 170 Me.btnAbout.BorderWidth = 1 Me.btnAbout.ControlText = "About" Me.btnAbout.CornerRadius = 12 Me.btnAbout.Cursor = System.Windows.Forms.Cursors.Hand Me.btnAbout.DrawBlackTextBackground = True Me.btnAbout.FillColor = System.Drawing.Color.FromArgb(CType(CType(192, Byte), Integer), CType(CType(255, Byte), Integer), CType(CType(255, Byte), Integer)) Me.btnAbout.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.btnAbout.ForeColor = System.Drawing.Color.White Me.btnAbout.Icon = Global.ATM.My.Resources.Resources.messenger Me.btnAbout.Location = New System.Drawing.Point(0, 2) Me.btnAbout.Margin = New System.Windows.Forms.Padding(4, 4, 4, 4) Me.btnAbout.Name = "btnAbout" Me.btnAbout.Size = New System.Drawing.Size(120, 87) Me.btnAbout.TabIndex = 8

' 'Frm_PinCode ' Me.AutoScaleDimensions = New System.Drawing.SizeF(6.0!, 13.0!) Me.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font Me.BackgroundImage = Global.ATM.My.Resources.Resources.darkaurora Me.BackgroundImageLayout = System.Windows.Forms.ImageLayout.Stretch Me.ClientSize = New System.Drawing.Size(727, 462) Me.Controls.Add(Me.btnAbout) Me.Controls.Add(Me.btnAdmin) Me.Controls.Add(Me.CloudDigitalClock1) Me.Controls.Add(Me.btnExit) Me.Controls.Add(Me.txt_code) Me.Controls.Add(Me.btnClear) Me.Controls.Add(Me.btnOK) Me.Controls.Add(Me.CloudLabel2) Me.Controls.Add(Me.CloudLabel1) Me.name = "Frm_PinCode" Me.Text = "Frm_PinCode" Me.WindowState = System.Windows.Forms.FormWindowState.Maximized CType(Me.ErrorProvider1, System.ComponentModel.ISupportInitialize).EndInit() Me.ResumeLayout(False) Me.PerformLayout() End Sub Friend WithEvents CloudLabel1 As CloudToolkitN6.CloudLabel Friend WithEvents CloudLabel2 As CloudToolkitN6.CloudLabel Friend WithEvents btnOK As CloudToolkitN6.CloudDesktopButton Friend WithEvents btnClear As CloudToolkitN6.CloudDesktopButton Friend WithEvents txt_code As CloudToolkitN6.CloudTextBox Friend WithEvents btnExit As CloudToolkitN6.CloudDesktopButton Friend WithEvents ErrorProvider1 As System.Windows.Forms.ErrorProvider Friend WithEvents CloudDigitalClock1 As CloudToolkitN6.CloudDigitalClock Friend WithEvents btnAdmin As CloudToolkitN6.CloudDesktopButton Friend WithEvents btnAbout As CloudToolkitN6.CloudDesktopButton End Class

4.3.4 CASH WITH DRAWAL

<Global.Microsoft.VisualBasic.CompilerServices.DesignerGenerated()> _ Partial Class Frm_Transfer_Cash Inherits System.Windows.Forms.Form 'Form overrides dispose to clean up the component list. <System.Diagnostics.DebuggerNonUserCode()> _ Protected Overrides Sub Dispose(ByVal disposing As Boolean) Try If disposing AndAlso components IsNot Nothing Then components.Dispose() End If Finally

MyBase.Dispose(disposing) End Try End Sub 'Required by the Windows Form Designer Private components As System.ComponentModel.IContainer 'NOTE: The following procedure is required by the Windows Form Designer 'It can be modified using the Windows Form Designer. 'Do not modify it using the code editor. <System.Diagnostics.DebuggerStepThrough()> _ Private Sub InitializeComponent() Me.CloudLabel4 = New CloudToolkitN6.CloudLabel Me.CloudLabel1 = New CloudToolkitN6.CloudLabel Me.CloudLabel2 = New CloudToolkitN6.CloudLabel Me.txt_AccountNo = New CloudToolkitN6.CloudTextBox Me.txt_TransferCash = New CloudToolkitN6.CloudTextBox Me.btnExit = New CloudToolkitN6.Windows.Vista.CloudStartMenuButton Me.btnTransfer = New CloudToolkitN6.Windows.Vista.CloudStartMenuButton Me.SuspendLayout() ' 'CloudLabel4 ' Me.CloudLabel4.AutoSize = True Me.CloudLabel4.BackColor = System.Drawing.Color.Transparent Me.CloudLabel4.Font = New System.Drawing.Font("Calibri", 20.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.CloudLabel4.ForeColor = System.Drawing.Color.White Me.CloudLabel4.Location = New System.Drawing.Point(12, 25) Me.CloudLabel4.Name = "CloudLabel4" Me.CloudLabel4.Size = New System.Drawing.Size(167, 33) Me.CloudLabel4.TabIndex = 17 Me.CloudLabel4.Text = "Transfer Cash" ' 'CloudLabel1 ' Me.CloudLabel1.AutoSize = True Me.CloudLabel1.BackColor = System.Drawing.Color.Transparent Me.CloudLabel1.Font = New System.Drawing.Font("Calibri", 14.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.CloudLabel1.ForeColor = System.Drawing.Color.White Me.CloudLabel1.Location = New System.Drawing.Point(45, 201) Me.CloudLabel1.Name = "CloudLabel1" Me.CloudLabel1.Size = New System.Drawing.Size(180, 23) Me.CloudLabel1.TabIndex = 18 Me.CloudLabel1.Text = "Enter Amount In (Rs.)" ' 'CloudLabel2 ' Me.CloudLabel2.AutoSize = True Me.CloudLabel2.BackColor = System.Drawing.Color.Transparent

Me.CloudLabel2.Font = New System.Drawing.Font("Calibri", 14.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.CloudLabel2.ForeColor = System.Drawing.Color.White Me.CloudLabel2.Location = New System.Drawing.Point(45, 144) Me.CloudLabel2.Name = "CloudLabel2" Me.CloudLabel2.Size = New System.Drawing.Size(154, 23) Me.CloudLabel2.TabIndex = 19 Me.CloudLabel2.Text = "Enter Account No." ' 'txt_AccountNo ' Me.txt_AccountNo.Font = New System.Drawing.Font("Calibri", 11.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.txt_AccountNo.Location = New System.Drawing.Point(244, 141) Me.txt_AccountNo.MaxLength = 10 Me.txt_AccountNo.Name = "txt_AccountNo" Me.txt_AccountNo.Size = New System.Drawing.Size(153, 26) Me.txt_AccountNo.TabIndex = 27 Me.txt_AccountNo.TextRenderingMode = System.Drawing.Text.TextRenderingHint.AntiAlias ' 'txt_TransferCash ' Me.txt_TransferCash.Font = New System.Drawing.Font("Calibri", 11.25!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.txt_TransferCash.Location = New System.Drawing.Point(244, 198) Me.txt_TransferCash.MaxLength = 5 Me.txt_TransferCash.Name = "txt_TransferCash" Me.txt_TransferCash.Size = New System.Drawing.Size(153, 26) Me.txt_TransferCash.TabIndex = 28 Me.txt_TransferCash.TextRenderingMode = System.Drawing.Text.TextRenderingHint.AntiAlias ' 'btnExit ' Me.btnExit.Anchor = System.Windows.Forms.AnchorStyles.None Me.btnExit.AnimationOpacityChange = 0.1 Me.btnExit.BackColor = System.Drawing.Color.Transparent Me.btnExit.ButtonText = "Exit" Me.btnExit.ClickedColors_1 = System.Drawing.Color.FromArgb(CType(CType(70, Byte), Integer), CType(CType(70, Byte), Integer), CType(CType(70, Byte), Integer)) Me.btnExit.ClickedColors_2 = System.Drawing.Color.FromArgb(CType(CType(49, Byte), Integer), CType(CType(49, Byte), Integer), CType(CType(49, Byte), Integer)) Me.btnExit.ClickedColors_3 = System.Drawing.Color.FromArgb(CType(CType(12, Byte), Integer), CType(CType(12, Byte), Integer), CType(CType(12, Byte), Integer)) Me.btnExit.ClickedColors_4 = System.Drawing.Color.FromArgb(CType(CType(10, Byte), Integer), CType(CType(10, Byte), Integer), CType(CType(10, Byte), Integer)) Me.btnExit.ControlOpacity = 255 Me.btnExit.CornerRadius = 8

Me.btnExit.Cursor = System.Windows.Forms.Cursors.Hand Me.btnExit.DrawHoverOverIcon = False Me.btnExit.Font = New System.Drawing.Font("Segoe UI", 13.0!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Pixel) Me.btnExit.ForeColor = System.Drawing.Color.Black Me.btnExit.GlowColor = System.Drawing.Color.FromArgb(CType(CType(79, Byte), Integer), CType(CType(215, Byte), Integer), CType(CType(226, Byte), Integer)) Me.btnExit.Icon = Nothing Me.btnExit.IsAnimated = True Me.btnExit.Location = New System.Drawing.Point(256, 333) Me.btnExit.MaximumGlowOpacity = 0.8 Me.btnExit.Name = "btnExit" Me.btnExit.NormalColors_1 = System.Drawing.Color.PowderBlue Me.btnExit.NormalColors_2 = System.Drawing.Color.PowderBlue Me.btnExit.NormalColors_3 = System.Drawing.Color.PowderBlue Me.btnExit.NormalColors_4 = System.Drawing.Color.PowderBlue Me.btnExit.Size = New System.Drawing.Size(114, 39) Me.btnExit.StartMenuIndex = 0 Me.btnExit.TabIndex = 31 Me.btnExit.TextCentered = True Me.btnExit.TextDistanceFromBorder = 5 Me.btnExit.TextIconRelation = CloudToolkitN6.Windows.Vista.CloudStartMenuButton.TextIconRelation_Enum .TextOverIcon ' 'btnTransfer ' Me.btnTransfer.Anchor = System.Windows.Forms.AnchorStyles.None Me.btnTransfer.AnimationOpacityChange = 0.1 Me.btnTransfer.BackColor = System.Drawing.Color.Transparent Me.btnTransfer.ButtonText = "Transfer" Me.btnTransfer.ClickedColors_1 = System.Drawing.Color.FromArgb(CType(CType(70, Byte), Integer), CType(CType(70, Byte), Integer), CType(CType(70, Byte), Integer)) Me.btnTransfer.ClickedColors_2 = System.Drawing.Color.FromArgb(CType(CType(49, Byte), Integer), CType(CType(49, Byte), Integer), CType(CType(49, Byte), Integer)) Me.btnTransfer.ClickedColors_3 = System.Drawing.Color.FromArgb(CType(CType(12, Byte), Integer), CType(CType(12, Byte), Integer), CType(CType(12, Byte), Integer)) Me.btnTransfer.ClickedColors_4 = System.Drawing.Color.FromArgb(CType(CType(10, Byte), Integer), CType(CType(10, Byte), Integer), CType(CType(10, Byte), Integer)) Me.btnTransfer.ControlOpacity = 255 Me.btnTransfer.CornerRadius = 8 Me.btnTransfer.Cursor = System.Windows.Forms.Cursors.Hand Me.btnTransfer.DrawHoverOverIcon = False Me.btnTransfer.Font = New System.Drawing.Font("Segoe UI", 13.0!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Pixel) Me.btnTransfer.ForeColor = System.Drawing.Color.Black Me.btnTransfer.GlowColor = System.Drawing.Color.FromArgb(CType(CType(79, Byte), Integer), CType(CType(215, Byte), Integer), CType(CType(226, Byte), Integer)) Me.btnTransfer.Icon = Nothing Me.btnTransfer.IsAnimated = True

Me.btnTransfer.Location = New System.Drawing.Point(136, 333) Me.btnTransfer.MaximumGlowOpacity = 0.8 Me.btnTransfer.Name = "btnTransfer" Me.btnTransfer.NormalColors_1 = System.Drawing.Color.PowderBlue Me.btnTransfer.NormalColors_2 = System.Drawing.Color.PowderBlue Me.btnTransfer.NormalColors_3 = System.Drawing.Color.PowderBlue Me.btnTransfer.NormalColors_4 = System.Drawing.Color.PowderBlue Me.btnTransfer.Size = New System.Drawing.Size(114, 39) Me.btnTransfer.StartMenuIndex = 0 Me.btnTransfer.TabIndex = 30 Me.btnTransfer.TextCentered = True Me.btnTransfer.TextDistanceFromBorder = 5 Me.btnTransfer.TextIconRelation = CloudToolkitN6.Windows.Vista.CloudStartMenuButton.TextIconRelation_Enum .TextOverIcon ' 'Frm_Transfer_Cash ' Me.AutoScaleDimensions = New System.Drawing.SizeF(6.0!, 13.0!) Me.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font Me.BackgroundImage = Global.ATM.My.Resources.Resources.darkaurora Me.BackgroundImageLayout = System.Windows.Forms.ImageLayout.Center Me.ClientSize = New System.Drawing.Size(509, 426) Me.ControlBox = False Me.Controls.Add(Me.btnExit) Me.Controls.Add(Me.btnTransfer) Me.Controls.Add(Me.txt_TransferCash) Me.Controls.Add(Me.txt_AccountNo) Me.Controls.Add(Me.CloudLabel2) Me.Controls.Add(Me.CloudLabel1) Me.Controls.Add(Me.CloudLabel4) Me.Location = New System.Drawing.Point(278, 220) Me.Name = "Frm_Transfer_Cash" Me.Text = "Frm_Transfer_Cash" Me.ResumeLayout(False) Me.PerformLayout() End Sub Friend WithEvents CloudLabel4 As CloudToolkitN6.CloudLabel Friend WithEvents CloudLabel1 As CloudToolkitN6.CloudLabel Friend WithEvents CloudLabel2 As CloudToolkitN6.CloudLabel Friend WithEvents txt_AccountNo As CloudToolkitN6.CloudTextBox Friend WithEvents txt_TransferCash As CloudToolkitN6.CloudTextBox Friend WithEvents btnExit As CloudToolkitN6.Windows.Vista.CloudStartMenuButton Friend WithEvents btnTransfer As CloudToolkitN6.Windows.Vista.CloudStartMenuButton End Class

CHAPTER 5

RESULT SCREEN SHOTS

CHAPTER 5 RESULT SCREEN SHOTS :

5.1 OPENING BANK WINDOW

5.2 ADMIN LOGIN PAGE

5.3ADDING NEW USER TO BANK

5.4ADDED DETAILS OF CUSTOMER

5.5DELETING THE USER DETAILS

5.6LOGIN OF CUSTOMER

5.7TRANSACTION

5.8 ENTER AMOUUT TO WITH DRAWAL

5.9EXIT WINDOW

CHAPTER 6

CONCLUSION

CHAPTER 6

CONCLUSION
Based studies on the ATM we hereby conclude that ATM is the easiest way of depositing and withdrawing money. Transaction is possible any time, thats why in India some people call ATM as all time money. If ATM machines are connected to internet then its possible to do transaction from any where, 24 hours a days and 365 days a year. With the security of ATM improving it has now become a safe mode of transaction. Hence it can be concluded that ATM is safe, fast, reliable, convenient, excisable and any time money machine. In future the facilities that can be added to ATM machines are: Filling of bills. Daily news headline. Check matches score or sensex ups and downs.

BIBLIOGRAPHY
1. 2. 3. ROBERT LAFORE: TURBO C++, Galgotia Publications Pvt Ltd, New Delhi YASHAVANT KANETKAR: LET Us C, BPB Publications, New Delhi YASHAVANT KANETKAR: GRAPHICS IN C, BPB Publications, New Delhi