Dashen Bank Automation

July 1, 2010
DASHEN BANK AUTOMATION SYSTEM
Acknowledgement
First and foremost, the team would like to thank almighty God. Then the team would like to thank to the project coordinator, Mr. Kasahun for the valuable guidance and advice. He inspired us greatly to work in this project. His willingness to motivate us contributed tremendously to the project. Besides, the team would like to thank the authority of ArbaMinch University (AMU) for providing us with a good environment and facilities to complete the project. Also, the team would like to take this opportunity to thank to the department of computer Science for offering this subject, developing this final year project. It gave us an opportunity to participate and learn about the operation of bank system. Finally, an honorable mention goes to Mr. Mehari the project main advisor, Mr. Nebiyat and Miss. Tigist our project co advisor they help us in developing this project by giving advice and comment how to precede and the team want to thank the manager of the bank Mr. Daniel who helps us by giving detail information of the bank operation. Without helps of the particular persons that mentioned above, we would face many difficulties while doing this project.
Abstract
Currently the bank is performing its task manually, so considering the problem of manual operation of the bank this project will try to solve the problem by automating the manual operation of the
Final year project Page 1
July 1, 2010
bank system. The proposed project will solve operation problems that can be occur in the existing system like depositing, Withdrwing, loaning, transferring money from one account to another account. The manual operation requires long time and much human power to complete a task .So the proposed project is going to avoid such problems.
CHAPTER ONE
Introduction
Now a day it is better if every activity is done using new technology in order to fulfill the need of human being, Organization, Enterprise etc . As todays world is present at the computations time so, in order to be the winner from those computation you must have use the technology. For example by this time there are many
July 1, 2010
organizations and each organizations needs to be preferable, computable, work on faster way on faster way in order to satisfy users interest etc they should have facilitate their activities in computerized way. In Arba Minch there is a Dashen Bank branch which is using manual operation to give services to the customer . 1.1. Background of the company The new economic policy introduced in November, 1991 caused the culmination of the command economic heralding the establishment of a market oriented one. This policy change created an opportunity and a conducive environment for the emergence of private financial institutions aimed at the bringing a meaningful economic role in the development efforts of the country. Dashen Bank was established as per the intent of the new policy and the Ethiopian investment code. It came into existence on September 20, 1995 according to the commercial code of Ethiopia, 1960, and the licensing and supervision of banking business proclamation No. 84/1994. The first founding members were 11 businessmen and professional that agreed to combine their financial resources and expertise to form this new private bank.
The rationale behind its name, "Dashen Bank"
"Ras Dashen" is the highest mountain of Ethiopia. It is also the habitat of rare wild animals; the Walia Ibex, the Gelada Baboon, and the Lammergeyer - the beautiful bone breaker eagle. These unique characteristics of the mountain coincided with the interest of the founders of the Bank and prompted them to adopt this great name and epitomize their aspiration. Rightly, reaching the top of banking business in dynamic and competitive business environment symbolized the highest peak, while the unique and efficient services the bank caters for the public through state -of-the-art computer technology and carefully selected and trained man-power equated with the rare wild animals. Today, indeed, reliability, efficiency and modernity are the hallmark and the bank's distinguishing features which make them synonymous with Dashen Bank as much as the rare animals are synonymous with Ras-Dashen Mountain. The bank gives the following services to the customers
July 1, 2010
Saving money Depositing money Withdraw of the deposit money Loaning and Repayment of money Money transfer (internal and external) Some special services depending on conditions
Vision of the bank
1.1.1

1.1.2
To become a world class bank. To satisfy customers by giving a very fast service
Mission of the bank
The mission of the bank is to play a major role in the financial service cost-effectively for all sectors of the economy and thereby support the long term development of the country.
1.2

Streangth and weakness of the existing system

The workers give service for the customers in a smooth manner. Eventhough they are using manual system they will try to complete the customers
1.2.1 Streangth of the existing system
need in a short time.
1.2.2
weakness of the existing system

All the necessary records of the above management activities are kept manually on papers
and stored in a file cabinet which are exposed for different physical hazards like fire, flood and the access time of the data is slow Frequent error generation which leads to unnecessary rework
1.3 BACKGROUND OF THE PROJECT

Background of the project is directed on the Arbaminch branch Dashen Bank of Ethiopia that
facilitates and provides different service to foreigners as well as local peoples by providing different activities related to the banks operation like money deposit ,loan and money transfer
1.3.1 Team composition

Role
Final year project
Description Assigned To
Page 4
July 1, 2010
Project Manager
Oversees the project and ensures that it meets its objective in time, function, and cost according to the project plan Writing a code and design the system Design the information system and ensure the system conforms to information systems standards and analyze the system requirement Design the project structure and interface
Girum Bekele
Programming/Coding
Fisseha Megersa
Girum Bekele
System Analyst
Nebiyu Alehegn Yonas Baye
System Design
Liyew Mesele and Natnael Otoro
Table 1.1 team composition

1.3
Statment of the Problem
Dashen bank of Ethiopia, Arbaminch branch is totally depends on the manual transaction of processes. So the organization faces a lot of problems in terms of cost, time, reliability, and efficiency.
1. Cost:When the existing transaction process problem is described according to its cost which includes: a. Improper cost of materials: - Which is expensed to buy paper, pen, and ruler. To the minimum the bank has five departments all want these materials for their work.
Final year project
Page 5
July 1, 2010
b. Human power: - The organization wants many clerks to provide fast and good service for its clients. 2. Time: - Since all function depends on human task, it consumes more time. Speed is one of the major problems of the existing manual system. 3. Reliability: - The other basic problem of the bank is lack of reliability. When clerks registers clients and calculates the money manually they may make mistakes which reduce the reliability of the existing manual operation. 4. Efficiency: - Since everything is done manually there might be errors when performing transactions like calculating an interest, deposit amount, withdrawal amount.
1.5 Objective of the project

When the project is initiated it has objectives to be in goal at the end of the project. The project objectives divide in to two groups. These are: 1. General objective and
2. Specific objectives To describe general and specific objectives:
1.5.1 General objective:
The general objective of the proposed project is to automate the current manual system of the
dashen bank of Ethiopia, Arbaminch branch.
1.5.2 Specific objective: The specific objective of the proposed project is:
1. To computerize registration of customer. 2.
To computerize the interest calculation for the deposit and Return of loaned money by the customer.
Final year project
Page 6
July 1, 2010
3. To computerize transfer of money in the bank (from one customer account to another),
deposit, Loan, and withdrawal. 4. Reducing manual errors by computerizing mathematical operations taken over there by the clerks.
1.6 Feasibility Analysis

The team analyzes the feasibility the proposed project according to the outcome that will happen after the development of the system. The team tried to divide these feasibility studies as:-
1.6.1 Operational Feasibility

The proposed project is accepted by the organization (Dashen bank) and it improves the activity of the bank by replaying the proper quality data, increase throughput response time, and increase efficiency of work in the bank. All in all, it replies proper solution for the operations that the workers of the bank are performing to carryout the task that they want to perform.
1.6.2 Technical Feasibilty

The proposed system is simple to use by the employees to perform a specific operation that is any employee having know how of computer operation can use the system. The training will be given for the new clerk to have know how for the system. The necessary hardware and software will provide by the organization for them.
1.6.3 Economic Feasibilty

Economically the proposed project doesnt cost much more and also the materials to implement the system doesnt cost great amount of money.
1.6.3.1 Cost Benefit Analysis A. Tangible Benefits

Since this project going to computerize there will be reduction of cost for materials used for manual operation: paper, pen, human power, space needed to record, and save data storage & time that the team can be induced or bring on during in the manual system. Final year project Page 7
July 1, 2010
The team calculated the corresponding tangible benefits based on the technique called the Time Value of
Money (TVM).
Cost reduction for material

materials cost for the current system
Item
Quantity per month
Unit price
Total Price per year
Papers Pen Ticket and receipt Total material cost
8 packet 4 packet 50 packet
80 Birr 50 Birr 10 Birr
7680 Birr 3200 Birr 60000 Birr 70880 Birr
Table 1.2 materials cost for the current system
Table 1.3 materials cost for the new system materials cost for the new system when deploys
Item
Quantity per month
Unit price
Total Price per year
Papers Pen Ticket and receipt

Final year project
4 packet 2 packet 50 packet
80 Birr 50 Birr 10 Birr

Page 8
Total material cost
July 1, 2010
Labor Cost
Role 2 System Analyst 2 system Designer 2 programmer
Total Labor Cost
Salary(For single) 5000 5500 5100
Total 10000 Birr 11000 Birr 10200 Birr
31200 Birr
Table 1.4 Labor Cost
Difference b/n before and after deployment money required for payment Cost Reduction for materials = 70880 birr 2700 birr = 68180 birr The total profit of the new system =68180birr from materials - 31200 birr for labor=36980
TP=36980 B. Intangible Benefit

The bank system provides the following intageble benefits:

Increase information accuracy in critical operation Information processing efficiency Saving loss of documents Increased speed of activity Increased flexibility, and On time information
1.6.3.2 Cost of the Project

July 1, 2010
a)
Tangible costs
The tangible costs to be incurred in developing the system are:i. ii. Hardware development cost Software development cost Key words: Salvage value: is the value that if you buy a computer, what will the price of the computer after 1 year and what is the price in the past 1 year. Reduction: decreasing in price within a short period. Life expectance (LE): the time in which software/other material to be access. Miscellaneous Cost: Cost for extra items Hardware cost
Item hp computer Laptop Printer CD-ROM
Quantity 6 1 1 2
Unit price 5500 Birr 10,000 Birr 5,000 Birr 16 Birr
Total Price 33000 Birr 10,000 Birr 5,000 Birr 32 Birr 48032 Birr
Total hardware cost
Final year project
Page 10
July 1, 2010
Table 1.5 Hardware cost
Salvage value=total hardware development cost/life expectancy (LE) for the software per year)*LE/month 12months*time to develop the software Salvage Value = (48032/5 year) x3 month 12 month Salvage Value = 12879.6 Yearly reduction Cost = (21466-12879.6)/5 years (LE) Yearly reduction Cost = 1717.28 Monthly reduction Cost = 1717.28/12 months Monthly reduction Cost = 143.106
Final year project
Page 11
July 1, 2010
Hardware improvement Cost = 143.1066x3 months
Software Cost
Item SQLserver2005 Microsoft Windows XP Professional Microsoft Office 2007 Visio Microsoft Visual studio. Net Total Software Cost
Price 1000 Birr 1400 Birr
Final year project
Page 12
July 1, 2010
Table 1.6 software cost
Hardware improvement Cost =429.3198birr Salvage Value = (6660/5 yrs) x 3 months 12 month Salvage Value = 333 Cost = 6660-333 / 5 yrs. (life expectancy) Yearly reduction Cost = 1265.4 Monthly reduction Cost =1265.4 / 12 months Monthly reduction Cost = 105.45 Software improvement Cost = 105.45x 3months Software improvement Cost = 316.35birr
Total cost of the project =48032 birr for hardware cost +6660 birr software cost
=54692 birr
The difference b/n total profit form new system and cost of the project =99380 birr for total
profit 54692 birr for cost of project
= 44688
b)Intangible costs
The intangible costs to be incurred or deserved and earn in developing the system are:
Human Knowledge Work satisfaction
1.6.3.3 Cost Breakdown

Beside tangible and intangible costs, the team breakdown cost of system development into two: one time cost and recurrent cost.
Final year project
Page 13
July 1, 2010
One time cost: Is a cost with project up and developments or system startup. This mean that it refers to those associated with project initiation and development cost and the startup of the system. The cost typing encompasses activities such as system development, new hardware & software purchase or system startup user training, and system or data conversion. Recurrent cost: Recurrent costs are those incurred for goods and services in the course of a budget year, and which must be regularly replaced since the team is developing this project for academic purpose the team may not gain any income.
1.6.4
Schedule Feasibility
All the team members expect that the project will be completed within the time frame stated, so that the system will be feasible regarding the schedule. The Project schedule is shown in the following Diagram
Final year project
Page 14
July 1, 2010
Activities
Timeline schedule 1 we ek 2 -3 week 4-5 week 6-8 Week 9-10 week End of 9th Week
Project Proposal Requirement Analysis Phase System & Object Design Implementatio n
Testing
Documentation And project submission Table 1.7 Timeline schedule
1.6.4 Political Feasibility

Since from the beginning the proposed project is politically feasible, that is different people such as the manager, clerks and other employees of the bank have good approach and view towards the
July 1, 2010
project and they encourage the team by giving good ideas to keep efficient result at the end of the project.
1.7 Scope and Limitation of the project

Since dashen bank performs its basic tasks manually the scope of this project is to develop and emplemet widow based system that works on network in the bank using work group computers.which will avoid the problems associated with the manual processing. Scope of the project Depositing money Loaning money Transfering money Withdrawing money The project also excludes the followings
Human resource management system of the bank & Finance system
1.7 Significances of the project

The proposed project is usefull for the bank to perform its activity in a simplified way.Since the bank is using the manual system for its operation it takes time and much human power so when it is become automted the bank can perform its task in a short period of time and little human power with little resource consumption.so the project is crucial for the bank .
1.8 Target Beneficiaries of the system

The beneficiaries of the proposed system will be all the society/who want to be the client of the bank who reside around Arbaminch town and other foriegn investers.
July 1, 2010
1.9 Tools and Methodologies Used Methodologies

Methodology of the project concentrates on the different method, tools and instruments for data collection, which helps for the fulfillment of the study.
1.9.1 Data collection method

To get a precise data from customers the team will use the following fact finding techniques. Those are: Interview : - to get the basic information and background information about the existing banking system, the team will interview the bank manager and some customer about the services that are assigned to them, and the problems associates with that environment. Observation: - Here the team will use to revise some data entry forms and repots associates with the banking process. Document analysis: - To get more information about the bank we refer books, documents and other reading materials about the dashen bank.
1.9. 2 System Analysis and Design methodology

Among the different methodologies available the team plan to use the object oriented design methodology for the development of the system. Because it is best way to construct, manage and assemble objects that are implement in the system, and the composition of objects and collaboration between objects on the system. Object oriented design methodology has two phases:Object Oriented Analysis (OOA): During this phase the team will look at the problem domain, and with the aim of producing a conceptual model of the information that exists in the area which will be analyzed. And this Model the functions of the system (use case modeling), identifying the business objects, organize the objects and also the relationship between them and finally model the behavior of the objects.
July 1, 2010
Object Oriented Design (OOD): During this phase Model object interactions and behaviors that support the use case scenario, and finally update object model to reflect the implementation environment. And also transforms the conceptual model produced in object-oriented analysis to take account of the constraints imposed to the proposed system format, so that the team will use this phase to refine the use case model to reflect the implementation environment.
1.9.3 Development Tools

In this project the following system development tools are use

Microsoft visual studio 2008: to design the graphical user interface and the whole application. Microsoft SQL server 2005: for designing the database.
Microsoft VISIO2003: for designing UML diagrams associated with the project. Microsoft office 2007: for documenting the corresponding deliverables associated with the project.
1.9.4 System Development Environment

The team will use windows 7 and window xp operating system to develop the system and the environment is .net framework of visual studio 2008, SQL Server .the language is vb.net
1.9.5 Requirements structuring and Data modeling tools

Since the team is being using an Object Oriented System Development methodology for structuring requirements and modeling the data, the team used a Unified modeling language (UML). The team used UML- diagrams for requirements structuring as well as data modeling.
1.9.6 Testing Procedures

Before directly deploying this system, the team will perform different testing for its functionality and meeting customers need. First the team tests each unit at each phase. So, if a problem is encountered it will immediately fixed. Then the team will perform an integration testing to check whether the system meets all the functional requirements. System will be tested using the following system testing procedures. Alpha testing:-In this testing method, the system will tested by giving the correct input. It is tested by a customer at the developer Site.
Final year project
Page 18
July 1, 2010
Beta testing: -In this testing method, team will force the system to be tested for incorrect data input. The System will be tested by the customer at their actual work place. If any failures occurred while testing the system in all the above testing methods, the team will take immediate correction beginning where this fault occurred before jumping to next work so that it will meet the goal. If all the above testing methods are carried out and find to be valid the system will directly deployed. Unit testing:-After developing an individual program module or component it would test it to ensure that it works according to the specification, operates within acceptable parameters, and meets the appropriate standards. Integration Testing:-When a number of components are complete; it will test to ensure that they integrate well with each other, the operating system, and other components. Quality Assurance (system) testing:-After preceded the above testing strategies the whole system will test with the participation of some other people. Behind that some questionnaires will prepared for them on how they get the system.
1.9.7 Implementation
The proposed system will implement parallel with the existing system until the awareness of the workers and customers towards the proposed system improved
1.9.8 Limitation Of the project

Due to shortage of time the team unable to complete the following functionalities The system do not perform cash exchange
The system does not support international money transfer services like western union
service etc.
1.9.7 Risk Assumption and Constraints Although the team Members planning to complete the project in a given dead line, the team may encounter unexpected problem or risk that can be either artificial or natural disaster. Such as:Final year project Page 19
July 1, 2010
Unfortunate failure of system Power problem and virus attack
To handle this problem the team has some method to resist not completely but partially by using back up mechanisms. Therefore whatever situation happen or occurred that hinder during the progression of the project the team try best to do what expected from us and reform it. Assumption The teams assume that the power and internet connection are available
CHAPTER TWO
2.1 Introduction
to the existing system
Dashen bank provides diferent banking services for the customers.services like depositing,loaning,and money transfer for the customers. Eventhough the bank is using the manual operation system,it has been giving good services for the customers.
2.2 Players of the existing system

players of the existing system are the following As the team has tried to mention in the previous chapter, the proposed system have many back side advancement over the existing system in many ways. Also the existing system is not securely supported system since it is manual; it needs number of labor to manage overall function of the system and it is not effective and clear. Existing system incorporates high number of labor (players) as compare with proposed system.
July 1, 2010
User of the bank (customers) :- includes any individual who wants to get the service from
the bank(first registered as the bank client to get services which are given there).
Employes(bank Clerks) :- includes individuals who are agents of the bank to provide
services which are requested by the customer.
The bank manager:-Administers all the transactions done by the clerks.
2.3. Major Function of the Existing System with Clear Input, Process and Outputs
The following section summerizes the basic functions with their clear input,process and output Depositing money Input:recieve customers information Process:checks the information Output:deliver the deposit reciept to the customer
Loaning money
Input:recieving the customers information Process:check the information validity
Page 21
Final year project
July 1, 2010
Output:deliver the loan reciept to the customer
Transfering money
Input:recieving the customers information Process: checking the information validity Output:deliver the reciept to the customer
2.4. Business Rule

This part specifies and gives somewhat understanding of activities which are being done in the existing system in terms of business rule. First of all the client will make contact with the counter to run his need. All customers should provide all the information which required by the Bank. Different forms and documents like registration form, saving form, deposit form and withdrawal forms should be fulfilled by the client depending on his/her need.
To open new account the client must come up with the minimum reqquirement of 50
birr with other basic information which can identify the customer
When a client take a loan from the bank by registering the loan returning date, if the
client cant return on that day he/she could penalized
2.5 Report generated in the existing system

In which includes reports that generated by the clerks to the Manager About daily registration of
customers, also daily transactions done by the clerk on each departments; in deposit, withdrawal, and loan.
2.6 Forms, Documents used in the existing system

The forms uses in the existing system are: Depositing form
Final year project
Page 22
July 1, 2010
Figure 2.1 Depositing form
Loan application form
Final year project
Page 23
July 1, 2010
Figure 2.2 Loan application form
Withdrawal form
Final year project
Page 24
July 1, 2010
Figure 2.3 Withdrawal form

Loan form
Figure 2.4 Loan form
2.7 Problem of the Existing System

The performance of any system is required to exhibit to meet the needs of users of that system. The current systems performance is weak, this is due to the following reasons: - first the acceptable throughput rate is relatively high i.e. the time required from initiation to completion of a particular task is relatively high.
July 1, 2010
The existing system has the problem of handling information becouse since it uses
manual system to store the recordes there is less secure and less reliable. The main input of the existing system is the customers information.this input is
redudant because it is written by hand and inflexible because when the customer fill the form if the error ocurres changing the form is the only choice. Due to the operation that is done by the hand most of the activities are prone to high
consumption of resources like papers, man power, time etc. This makes the current system inefficient while utilizing resources. There should be a mechanism that reduce wastage of resources and that make the system to be efficient.
2.8 Practices to be preserved from existing system

From the existing system the following are practices to be preserve System procedures The governing rule and regulation Formalities of the customer The business rules of the bank
2.9 Alternative options to address the problems of existing system

The Team Members have different alternative options to solve problems faced with the existing system. These are: Business project re engineering (BPR) for the current system.
The new proposed system Final year project Page 26
July 1, 2010
From the above alternative option the team members chose the new proposed system which is the proposed system. The main purpose of new system that the team is going to develop is in order to solve problems that faced the existing system in the functioning of the bank system, and it includes:-
Changing the whole manual system in to automated system without affecting the structure
of the company.
Developing easily accessible documents that is clear to employees when accessing data Avoiding wastage of time that the manual system can take during searching materials by
the computerized system
2.10. System Requirements of the New System 2.10.1 Functional requirements

Data manipulation on customer information ,on money deposit, withdrawal (i.e. save, update ,and delete) Perform calculation for interests paid by the customer at loan return time, and for the deposited money. Report generation by the clerk to the manager Security of the system(privilege , username and password )
2.10.2 Non-Functional Requirements

The following are the non functional requirements associated with the new system. The system must be error free while operating with a huge set of data. The system must be user friendly The system must be able to communicate users at different location. The system must recover immediately when a user enters erroneous data. The system must have a good response time.
July 1, 2010
The system must be compatible with any environment.
CHAPTER THREE
SYSTEM ANALYSIS
Introduction
Final year project
Page 28
July 1, 2010
This section consists of the modeling of the proposed system using object oriented methodology by applying unified modeling language (UML). All the activities performed by the actors (such as the customer, clerk and the administrator) are analyzed by using different modeling diagrams. These diagrams include use case diagram, sequence diagram, activity diagram, and conceptual diagram.
3.2 System Requirement Specifications (SRS) 3.2.1 Use case diagram
Figure 3.1 use case diagram for bank automation system
Use case documentation

Use case documentation for Login
Final year project
Page 29
July 1, 2010
Name Identifier Description Actors Precondition Post condition Basic course of action:
Login UC :01 To login a user in to the system to get and/or provide services Clerks and the manager The users have a user name and password. The user will login in to the system Actor action Step 1. The user wants to login into the system. Step 2. The user inputs his/her user name and password into the system via UI 01 Security Login Screen. Step 4. The use case ends. System response Step 3. The system verifies the user is eligible to login into the system according to business rule BR 01 Determine Eligibility to Login.
Alternate course of action:
A3: The user name does not exist. A.4: The system determines that the user name does not exist in t A.2: The system increments the number of frailer by one. A.5: The system informs the user the unavailability of his/her user name. A.6: The use case ends.
2. Use case documentation for New Client Registration Name Identifier Description Registration UC:02 This process is initialized when new client come to the bank to get services of
Page 30
Final year project
July 1, 2010
saving (deposit money) in the bank. Actors Precondition Client and Clerk client should come with all required information that needed for registration
Post condition Basic course of action:
If the client fulfills all required information that set by the bank and met with bank policy, then customer will be registered. Actor action Step1. The clerk select department System response
Step 5. If the required information provided by the client is validated Step2. The clerk successfully logged in and verified, then client will be registered. Step 3.Client should bring the required information by filling the application form. Step 4.Clerk enter the required information of the client to the system Step 6. The use case ends
A.5 If the customer did not come with the required information (or one of the required information of the client is not satisfied), then the customer will not be registered, and the system asks the client to come with a full information.
3. Use case documentation for Money withdraw Name Identifier Description withdrawal UC:03 This process is initialized when customer need to withdraw money from his A/c in the bank
Page 31
Final year project
July 1, 2010
Actors Precondition Post condition Basic course of action:
Clerk client should be registered and should have saving account If the client fulfill all requirement, then they can withdraw money Actor action Step1. The clerk select department Step2. The clerk successfully logged in Step 3. client should fulfill the requirement Step 4. The clerk should search for the existence of the A/c. Step 5. The clerk checks whether the client fulfills the requirements and enters the attributes. Step 8. If the required information is provided and validate, then client will withdraw the money for the client. Step 9. Use case end. System response Step 6.The system validate whether the given information is true or not Step7. The system calculates and set the A/c balance of the client after withdraw.
A.6 If the client did not fulfill the requirement(not registered and have no saving account),then cannot withdraw the money A.7 use case end
4. Use case documentation for Money Deposit

Name Identifier Description Actors Precondition
Final year project
Deposit UC:04 This process is initialized when customer need to add money to his saving account in the bank System user and customer Customer should be registered and should have saving account
Page 32
July 1, 2010
Post condition Basic course of action:
If the customer fulfill all requirement, then they can add money to his saving account Actor action Step1. The clerk select department Step 2. The clerk should successfully logged in Step 3. Client should fulfill the requirement for depositing money Step 3. The clerk checks that whether the client fulfills the requirements. Step4. The clerk enters client A/C No. to search its existence Step 6. If the required information is provided and validate, then the client current money he will be come with is added to his saving account. Step 7. Use case end. System response Step 5.The system validates and verifies whether the given information is true or not.
A.1 If the client did not fulfill the requirement (not registered and have no saving account),then cannot add money to their saving account
Final year project
Page 33
July 1, 2010
Name Identifier Description
Loan UC:05 This process is initialized when a client is come to loan money from the bank.
Actor Precondition:
Client and clerk The client come to loan money by filling an application form that is given there. On that application form the client fill the amount of money he wants to loan and the guarantee (property or valuable persons will be registered) and the time interval for returning the money could be registered on the application form. The application number and all needed information are registered and the money is given to the applicant.
Post condition:
Basic course of action:
Actor Action Step1. The clerk select department Step 2. The clerk should successfully logged in
System response Step 5.The system validate whether the given information is valid or
not according to the Step 3. Client should fulfill the requirement and bring the application bank rule. form to the clerk to loan the money.
Step 4: the clerk enters all the

required data to the system
Step 6: The required information provided is validated and verified, and then the requested money is given to the applicant. Step 7 .use case ends.

Final year project
A.1 If the client application form is not come with the required information when validated, the process should not take and he/she will be asked to come with full and reliable information. Page 34
July 1, 2010
6. Use case documentation for Money Return
Name Identifier Description
Return UC:06 This process is initialized when the client come to the bank to return the money he loaned from the bank.
Actor precondition
clerk Loaning money from the bank by registering the return date (interval) and rate of interest to be paid to the bank.
post condition Basic course of action
Return the money on the date guaranteed. Actor action Step1. The clerk select department Step 2. The clerk should successfully logged in Step 3.the client come with the money he/she promise to return & with the interest (from the day he loaned to the he come to return). Step 4. The clerk enters the lone number the suggested loan number and search the information. Step6. The clerk enters money with the calculated interest value to the system. Step 8. use case end System response Step 5. The system validate whether the given information is true or not. Step 7. The system calculates the return balance and adds it to the bank balance, and then subtracts the returned money from the lone balance other than the interest.
Alternate course of action

Final year project
A1. The client will not be fulfill the required data for returning the transaction cant operate. A2. If the client has not loaned money the process cannot take.
Page 35
July 1, 2010
7. Use case documentation for Money Transfer

Name Identifier Description Actors precondition Post condition Basic Course of action Transfer UC:07 This is initialized when the client of the bank come to get this service(he wants transfer money to other A/c in the bank) Clerk Client should come with an interest to transfer money If the client A/c is there if the bank the client has to transfer the money. Actor action System Response Step1. The clerk select department Step2. The clerk successfully logged in Step 3.The client should come with an account that he/she wants to transfer money to that A/c. Step 4. The clerk enters both clients A/c No. (the A/c No. of a person who transfer and who has transferred to) to search the existence their A/c in the bank. Step 6.The clerk enters the amount of
Step 5.The system checks whether the client is registered before (i.e. if he has an A/C in the bank). Step7. The system checks if the requested money to be transferred is less than or equal to the existing balance in the A/C. And then perform the transaction and update both A/c balances.
July 1, 2010
money to be transferred to. Step 8 .use case ends. Alternate course of action
9. Use case documentation for Loan Application

Name Identifier description Get_ loan Form UC:08 This process is initialized when a person wants to loan money from the bank ( loaner) Client and clerk The client should come with an interest to loan money and fulfilling all requirement i.e. listed on the loan application form Loaning money Actor action Step1.The clerk select the department Step2.The clerk success fully logged in Step3. The client should bring the application form by filling all listed requirements on it . Step4 the clerk enters the data to the system Step 6. Use case end Alternate Course of action A.1 If the application form is not filled correctly the transaction cant operates System response Step 5. The system checks whether the data is varied or not and verify it.
Actor precondition
Post
condition
Basic course of action
Final year project
Page 37
July 1, 2010
10. Use case documentation for Handles clerk information

Name Identifier Description clerk info. UC:09 This is used for adding (create a new clerk) when new clerk come to the bank, delete and modify clerk information because this is privilege of the manager. Manager 1) For adding clerk New clerk should be come (employed) to the bank. 2) For deleting clerk When a clerk leaves the bank his/her A\C information will be deleted. 3) Modify clerk For security depending on the principle of the bank in a definite time interval (monthly, in 3 or 6 month) the system manager has the right to modify clerk information.
Actor precondition
Post condition
1)For adding clerk A new clerk will be added when he is employed to the bank. 2) For deleting clerk A\C Clerk A\C is deleted because somebody (a clerk) leave the bank. 3) For modifying A\C -A clerk A\C is modified
Final year project
Page 38
July 1, 2010
1) For adding clerk Step1.The clerk comes with all information (fulfill all required information by the system) to be an employee of the bank Step2.The manager enters all information needed to the system. 2) For deleting clerk A\C Step1.The manager assures whether the clerk leave the bank or not. Step2.The manager removes all information (A\C) of the clerk. Step4. end of use case Actor Action: 3) Modify the clerk A\C Step1.The manager checks the period of an A\C when to modify it or any time he wants. Step2.The manager will be set the information to be modified (and enter to the system) Step4.end of use case
System response Step3. If all the required information about the clerk is registered the system validate it.
System response Step3.The system validate if the clerk is deleted or not.
System response: Step3.The system validates the clerk A\C if it is.
Alternate Course of action
A.1 If there is no new clerk come as employee to one of the department to the bank add, delete and modify process cant take. A.2. If all the information about the clerk is not fulfilled the process cant take.
Final year project
Page 39
July 1, 2010
11. Use case documentation for Handles clerk information

Name Identifier Branch info. UC:10 This is used for adding(create a new branch), delete branch, or edit when new clerk come to the bank because he is privilege of the manager to register new clerk new account because he/she is the only person to do this transaction. Actor precondition Manager 1) For adding Branch When new bank branch is opened that bank information will be added (registered). 2) For deleting Branch When a bank is closed from giving any service to its client that branch will be deleted. 3) Modify Branch When information is changed to the bank(like its name, branch number )
Post condition
1)For adding Branch A new branch bank will be added to the database. 2) For deleting Branch The branch information will be deleted. 3) For modifying Branch
A branch bank information will be modified 1) For adding Branch System response Step1.The branch fulfills service providing criteria it should be added( when it is opened) Step2.The manager enters all information Step3. If all the required information about the branch is registered the system validate it.
Final year project
Page 40
July 1, 2010
needed to the system. Step4. The branch will be opened. Step5. Use case end. 2) For deleting Branch Step1.The manager assures whether the branch has to close the branch or not. Step2.The manager removes (deletes) all information of the branch bank. Step4. The branch will be deleted (removed). Step5. end of use case Actor Action: 3) Modify the Branch Step1.The manager checks the any attribute that is changed in the bank when to modify it or any time he wants. Step2.The manager will be set the information to be modified and enter to the system. Step4. The branch information will be modified as needed. Step5. end of use case Alternate Course of action A.1 If there is no new clerk come as employee to one of the department to the bank add, delete and modify process cant take. A.2. If all the information about the clerk is not fulfilled the process cant take. System response: Step3.The system validates the attribute to be modified System response Step3.The system validate if the branch is deleted or not.
12. Use case documentation for generate report

Name
Final year project
Generate Report
Page 41
July 1, 2010
Identifier Description
UC:11 This process is initialized when system user and manager want to generate report about the tasks performed on the system System user and manager The manager need to view report about the customers and tasks performed in the system The report is generated by the system user and viewed by the manager Actor action Step 1.System user want to generate report Step 2.System user enter the required information to the system Step 5.The manager view the required report and help the decision making process System response Step 3.The system check entered information Step 4.The system generates report about the services given in the Bank within limited time.
Actors Precondition Post condition Basic course of action:
A.1 If the system user dont generate the report, the manager cannot view the required report
3.3. Sequence Diagram

1. Sequence Diagram for login
Final year project
Page 42
July 1, 2010
Figure 3.2. Sequence Diagram for login
2. Sequence Diagram for Customer Registration
Final year project
Page 43
July 1, 2010
Figure 3.3. Sequence Diagram for Customer Registration
3. Sequence withdrawal
Final year project
Page 44
July 1, 2010
Figure 3.4. Sequence Diagram for Money Withdrawal
4 .Sequence Diagram for Money Deposit
Final year project
Page 45
July 1, 2010
Figure 3.5. Sequence Diagram for Money Deposit
Final year project
Page 46
July 1, 2010
5. Sequence Diagram for Money Loan
Figure 3.6. Sequence Diagram for Money Loan
Final year project
Page 47
July 1, 2010
6. Sequence diagram for Money return
Figure 3.6. Sequence Diagram for Money Return
Final year project
Page 48
July 1, 2010
7. Sequence Diagram for Report Generation
3.4 Activity Diagram

July 1, 2010
1. Activity Diagram for login
Figure 3.7. Activity Diagram for Login
2. Activity Diagram for Client registration
Final year project
Page 50
July 1, 2010
Figure 3.8. Activity Diagram for Client Registration
3. Activity Diagram for Money deposit
Final year project
Page 51
July 1, 2010
Figure 3.9. Activity Diagram for Money Deposit
4. Activity Diagram for Money withdraw
Final year project
Page 52
July 1, 2010
Figure 3.10. Activity Diagram for Money Withdrawal
5. Activity Diagram for Money Return
Final year project
Page 53
July 1, 2010
Figure 3.11. Activity Diagram for Money Return
6. Activity Diagram for Money lone
Final year project
Page 54
July 1, 2010
Figure 3.12. Activity Diagram for Money Lone
7. Activity Diagram for Transfer
Final year project
Page 55
July 1, 2010
Figure 3.13. Activity Diagram for Money Transfer
8. Activity for compute interest
Final year project
Page 56
July 1, 2010
Figure 3.13. Activity Diagram for compute interest
3.2.5 Analysis Class Diagram of the Bank System

July 1, 2010
1. Conceptual diagram for report generation
Final year project
Page 58
July 1, 2010
Figure 3.14. Conceptual diagram for report generation 2. Conceptual diagram for Money return registration
Figure 3.15. Conceptual diagram for Money return
3. Conceptual diagram for customer Registration
Final year project
Page 59
July 1, 2010
Figure 3.16. Conceptual diagram for customer Registration

4. Conceptual diagram for deposit generation
Figure 3.17. Conceptual diagram for deposit

5. Conceptual diagram for withdrawal
Final year project
Page 60
July 1, 2010
Figure 3.18. Conceptual diagram for Withdrawal

6. Conceptual diagram for Money transfer
Figure 3.19. Conceptual diagram for Transfer
7. Conceptual diagram for loan generation
Final year project
Page 61
July 1, 2010
Figure 3.20. Conceptual diagram for Money Loan

8. Conceptual diagram for authentication
Figure 3.21. Conceptual diagram for authentication
3.2.6 User Interface Prototyping

Designing Interface
July 1, 2010
The main outputs from the designing of the human interface are forms and reports. In this system depending on the concerned form and report as follows designed. With the three specification narrative overview, sample design, and testing and usability assessment. The narrative over view provide a general overview of the characteristics of the target user, task, and environmental factor in which the form or report will be used. In the second section of the specification, a sample design of form is shown. This design is developed using VB.NET tools. The final section of the specification provides all testing and usability assessment information. a. Narrative Overview Form: User: Task: System: Environment: b. Sample Design Login All users Securing the system by providing password and user name Microsoft Windows Standard office environment
c. Testing and usability assessment user rated perception(all user) Table: Design specification for login.
Final year project
Page 63
July 1, 2010
c. Narrative Overview Form: User: Task: System: Environment: Client Registration All clerks registering all information of the client Microsoft Windows Standard office environment
b. Sample Design
c. Testing and usability assessment user rated perception(average 3 users)
Table: Design specification for Client Registration
Final year project
Page 64
3.2.7. Supplementary specification

Business rule
Name: determine eligibility to login Identifier: BR1 Description: The system should be used only by authorized persons, since there is a sensitive data that should not be altered by anybody. Therefore, only users having valid user name and password can login to a system Name: The customer should have to give all necessary information to be registered and to be a client of the bank Identifier: BR2 Description: during registration the customer should give all required information in order to be registered and to get services from the bank
Name: the customer should appear physically itself Identifier: BR3 Description: the customer should appear physically by himself/herself, that means cannot performed by agent Name: the customer should provide a minimum of 50 birr for saving registration Identifier: BR4 Description: the customer should have a minimum of 50 birr which kept in the account after the registration. Name: the customer should have in his/her account a minimum of 50 birr when withdrawing money (i.e. the minimum bank balance of the client to be in the saving account). Identifier: BR5
Description: the customer should have a minimum of 50 birr which kept in the account after the withdraw. Name: the customer account should be closed when his/her balance value become 0 birr. Identifier: BR6 Description: when a client is registered as a customer of the bank he has balance that kept in the bank, if 0 birr bank balance means the customer also dont want to get the service. So the bank manager deletes the account of the client from the bank. Name: the loan customer should be an account holder Identifier: BR7 Description: Any customers want to get loan from the bank, first they should be account holder in the bank Name: record may not be repeatedly stored Identifier: BR8 Description: for the sake of consistency and removal of data redundancy which leads to wastage of storage memory, it is necessary to remove redundancy whenever necessary Name: field emptiness Identifier:-BR 9 Description:-it is not allowed to leave a field empty before performing any operation Name: determine eligibility to see reports Identifier:-BR 10 Description:-it is not allowed to see all reports unless he/she is the manager. Name: determine eligibility to update Identifier:-BR 12 Description:-updating the clerk, client and branch information is not allowed for all other than the manager.
Name: determine eligibility to Add Identifier:-BR 13 Description:-addition of an item is not allowed unless the item is found in the database currently
Name: Interest calculation Identifier:-BR 14 Description:-the interest of an account balance is calculated annually for all clients depending on the amount of the balance in their account (it is calculated in percentile). This process also take when a client return the money he/she loaned from the bank.
CHAPTER FOUR SYSTEM DESIGN 4.1. Introduction

This project is designed in a manner that solves the problems of the organization by minimizing the work load that appears on the employees because of the existing manual system. It provides more efficient, reliable and time saving system. In this project design the team will try to show: How the project is designed
What are tasks done under the whole project The different modules and their way of functioning are described here. Generally, the project will be designed by addressing all of the above criteria of project design. It is designed to simplify functions of the manual system and it is capable of doing large amount of works in short period of time with more accuracy and reliability. Generally this project design will describe how the project is designed, what tasks done under this project and different modules and their way of functioning. The goal of system design according to the proposed project is to manage complexity by dividing the system into smaller, manageable pieces and to increase the system: Efficiency: the system doing something well and thoroughly without waste of money and time. Flexibility : the system able to change to suite new condition or situation Security: the system should be secured, i.e. not allow unauthorized users to access the system. Reliability: the system should be reliable.
4.2 Class type architecture
Figure 4.1 class type architecture
4.3
Class Modeling
Figure 4.2 class modeling
4.4 State chart modeling

4.4.1 Stat chart diagram for security login
Figure 4.3 Stat chart diagrams for security login
4.4.2 Stat chart diagram for customer registration
Figure 4.4 Stat chart diagram for customer registration
4.2.1
Stat chart diagram for withdrawal
Figure 4.5 Stat chart diagram for withdrawal
4.2.1
Stat chart diagram for Deposit
Figure 4.6 Stat chart diagram for Deposit
4.2.1
Stat chart diagram for report
Figure 4.7 Stat chart diagram for report
4.2.1
Stat chart diagram for transfer
Figure 4.8 Stat chart diagram for transfer
4.2.1
Stat chart diagram for return
Figure 4.9 State chart diagram for return
4.2.1
Stat chart diagram for loan
Figure 4.10 Stat chart diagram for loan
IV.5
Collaboration Modeling
Collaboration diagram for system login
Figure 4.11 Collaboration diagram for system login
Collaboration diagram for customer registration
Figure 4.12 Collaboration diagram for customer registration
Collaboration diagram for money deposit
Figure 4.13 Collaboration diagram for money deposit
Collaboration diagram for money withdrawal
Figure 4.14 Collaboration diagram for money withdrawal
Collaboration diagram for money loan
Figure 4.15 Collaboration diagram for money loan
Collaboration diagram of money return
Figure 4.16 Collaboration diagram of money return
Collaboration diagram for money transfer
Figure 4.17 Collaboration diagram for money transfer
IV.6 Component Modeling
Figure 4.18 Component Modeling
I.3
Deployment modeling
A Deployment diagram shows processors, devices, and connections. Each model contains single Deployment diagram which shows the connections between its processors and devices, and the allocation of its processes to processors.
Window server
Figure 4.19Deployment modeling
4.8. Persistence modeling
Figure 4.20 Persistence modeling
4.9 User Interface Design

In this sub title of the project the team tried to show some of the user interfaces that exist in the system.
Among these: 1. Security login user interface 2. New customer registration user interface 3. Money deposit user interface 4. Money withdrawal user interface 5. Money Loan user interface 6. Money Transfer user interface: 7. Security login user interface
Main form of the System
1. Security login user interface
2. New customer registration user interface
3. Money deposit user interface
4. Money withdrawal user interface
5. Money Transfer user interface
6. Money Loan user interface
CHAPTER FIVE
5.1
Implementation and Testing
System implementation and operation

During implementation and operation, physical design specification must be turned into working computer code, and then the code is tested until most of the errors have been detected and corrected. The system is installed, user sites are prepared for new system and user must come totally on the new system rather than the existing one to get there work done. There are some managerial activities in this, coding, testing, and installation
5.3 Coding
Coding is the process whereby the physical design specification created by the designers is turned in to working computer code by the programmer. Modern language that used is vb.net.
Sample code for the system
'Customer Registration Save Button code

Private Sub Registerbtn_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click Dim cid As String cid = Me.textaccountn.Text.ToUpper If textaccountn.Text = "" And Me.textFname.Text = "" And textaccountn.Text = "" And textaccountn.Text = "" And textpobxe.Text = "" Then MsgBox("Please Fill The customer Information ", MsgBoxStyle.Information, ) Me.textaccountn.Focus() Exit Sub End If If textaccountn.Text = "" Then MsgBox("Please Enter An Account No ", MsgBoxStyle.Information, ) textaccountn.Focus() Exit Sub End If cheak() Dim controlID As String controlID = Me.textaccountn.Text Dim dtrowusergeneralinfo As DataRow Dim foundAt = 0 Dim flag As Char = "n" If ((Me.textaccountn.TextLength <> 0) And (Me.textaccountn.Text.Length <> 0)) Then Try For Each dtrowusergeneralinfo In DTcustomer.Rows Dim CuID As String = dtrowusergeneralinfo.Item("AccountNo") If (Me.textaccountn.Text.ToUpper = CuID.ToUpper) Then flag = "y" Else foundAt += 1 End If Next Catch ex As Exception
MsgBox(ex.Message) End Try End If Try conn.Open() dacustomer.Fill(dss, "Customer") conn.Close() DTcustomer = dss.Tables("Customer") Catch ex As Exception End Try Try If (flag = "n") Then 'If the Id does not already exist Dim rowAdd As DataRow rowAdd = DTcustomer.NewRow rowAdd("FirstName") = Me.textFname.Text rowAdd("MiddleName") = Me.textMnamee.Text rowAdd("LastName") = Me.textLnamee.Text rowAdd("Age") = Me.textagee.Text rowAdd("Sex") = Me.combsexx.Text rowAdd("AccountNo") = Me.textaccountn.Text rowAdd("Address") = Me.textAddree.Text rowAdd("Postalcode") = Me.textpobxe.Text rowAdd("MobilePhone") = textmobilepe.Text rowAdd("AccountType") = textAcouTypee.Text rowAdd("DateJoind") = DateTimePicker4.Text rowAdd("Nationality") = cmbnationnal.Text rowAdd("MaritalStatus") = cmbMarital.Text rowAdd("BranchNo") = Me.cmbbranchNo.Text rowAdd("CurrencyType") = cmbcurrency.Text rowAdd("CampanyName") = TextBox1.Text rowAdd("HoueNo") = TextBox2.Text rowAdd("Kebele") = TextBox3.Text DTcustomer.Rows.Add(rowAdd) Try Dim cmdbldr As New SqlCommandBuilder(dacustomer) conn.Open() dacustomer.Update(dss, "Customer") conn.Close() MsgBox("You Are Finished your task on this Form Successfully, CONTINUE !", MsgBoxStyle.Information) texvisualizer() Deposit.Show() Me.Hide() clear() textaccountn.Focus() Catch ex As Exception MsgBox(ex.Message) End Try Else MsgBox("The ID You Entered""" & controlID & """Is Already Exist Please Enter New ID ", MsgBoxStyle.Information, ) textaccountn.Focus() Me.textaccountn.Clear() Exit Sub End If
Catch ex As Exception End Try End Sub
'Customer Balance Deposit Sample Code

Private Sub Depositbtn_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click Dim cmdselect2 As New SqlCommand cmdselect2.CommandText = "SELECT * FROM BankBranchs WHERE BranchNo='" & txtbranch.Text & "'" cmdselect2.CommandType = CommandType.Text dabranch.SelectCommand = cmdselect2 cmdselect2.Connection = conn conn.Open() dabranch.Fill(dss, "BankBranchs") conn.Close() If dss.Tables("BankBranchs").Rows.Count > 0 Then Dim cmdupdate As New SqlCommand cmdupdate.CommandText = "UPDATE BankBranchs SET TotalBalance='" & dss.Tables("BankBranchs").Rows(0)(16) + textedepamount.Text & "' where BranchNo='" & txtbranch.Text & "'" cmdupdate.CommandType = CommandType.Text dabranch.UpdateCommand = cmdupdate cmdupdate.Connection = conn dss.Tables("BankBranchs").Clear() conn.Open() dabranch.UpdateCommand.ExecuteNonQuery() conn.Close() Else MessageBox.Show("The movie is not found!!", "Error", MessageBoxButtons.OK, MessageBoxIcon.Error) End If Dim cmdselect22 As New SqlCommand cmdselect2.CommandText = "SELECT * FROM deposited WHERE AccountNo='" & ComboBox1.Text & "'" cmdselect2.CommandType = CommandType.Text dadeposit.SelectCommand = cmdselect2 cmdselect2.Connection = conn conn.Open() dadeposit.Fill(dss, "deposited") conn.Close() If dss.Tables("deposited").Rows.Count > 0 Then Dim cmdupdate2 As New SqlCommand cmdupdate2.CommandText = "UPDATE deposited SET OpeningBalance='" & dss.Tables("deposited").Rows(0)(1) + textedepamount.Text + CDbl(TextBox9.Text) & "' where AccountNo='" & ComboBox1.Text & "'" cmdupdate2.CommandType = CommandType.Text dadeposit.UpdateCommand = cmdupdate2 cmdupdate2.Connection = conn dss.Tables("deposited").Clear() conn.Open()
dadeposit.UpdateCommand.ExecuteNonQuery() conn.Close() MsgBox("Customer succesfuly Deposited Money!!!!", MsgBoxStyle.Information) Else MessageBox.Show("The movie is not found!!", "Error", MessageBoxButtons.OK, MessageBoxIcon.Error) End If End Sub
Interest
Calculation Button Sample Code
Private Sub InterestCalculatebtn_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button6.Click Try Dim P, I, A, R As Single R = TextBox8.Text P = TextBox1.Text Dim T As Integer Dim txtDate1 As Date = CType(Me.TextBox2.Text, Date) Dim txtDate2 As Date = CType(Me.DateTimePicker1.Text, Date) Dim MyDifference As TimeSpan MyDifference = txtDate2.Subtract(txtDate1) ' find the number of days apart MessageBox.Show(MyDifference.Days) ' Display to the user T = MyDifference.Days If T > 0 Then 'T = MyDifference.Days I = R * (P * T) / 36500 Else MsgBox("There is No Interst ", MsgBoxStyle.Information) TextBox9.Text = "0" 'I = P * R End If A=P+I TextBox10.Text = T TextBox9.Text = I 'TextBox3.Text = A Dim val2 As Double = CDbl(TextBox10.Text) If val2 = 364 / 2 Then MsgBox("This is six Month Deposit Interst", MsgBoxStyle.Information) ElseIf val2 = 365 Then MsgBox("This is one year Deposit Interst", MsgBoxStyle.Information) End If Catch ex As Exception End Try End Sub
Sample Module Code for All Forms to the Database connection

Imports System.Data Imports System.Data.SqlClient
Module module1 ''VideoNew Dim conn As New SqlConnection("data source=GirumPc; initial catalog=Bankinautomation; integrated security=True") 'Dim conn As New SqlConnection("Network Library=DBMSSOCN;data source=10.144.30.140,1433;initial catalog=Bankinautomation;integrated security=True") Public dabranch As New SqlDataAdapter("select * from BankBranchs", conn) Public daloan As New SqlDataAdapter("select * from tablloannew", conn) Public dawithdrow As New SqlDataAdapter("select * from Withdrowtable", conn) Public dadeposit As New SqlDataAdapter("select * from deposited", conn) Public datransfer As New SqlDataAdapter("select * from transferrrrrr", conn) Public dacustomer As New SqlDataAdapter("select * from Customer", conn) Public dausers As New SqlDataAdapter("select * from Users", conn) Public dauserlogin As New SqlDataAdapter("select * from UserLogin", conn) Public dacheque As New SqlDataAdapter("select * from chequeDeposit", conn) Public dausermanager As New SqlDataAdapter("select * from UserManager", conn) Public dapicture As New SqlDataAdapter("select * from picturetale", conn) Public dss As New DataSet Public dtmovie As New DataTable End Module
Sample code for login

Public Sub password() Dim cmdselectrt As New SqlCommand Dim ENCRYPTPASSINSERT, ENCRYPTPASSINSERTuser As String ENCRYPTPASSINSERTuser = stringunTMD5(txtusername.Text) ENCRYPTPASSINSERT = stringTMD5(txtpassword.Text) cmdselectrt.CommandText = "SELECT * FROM UserManager WHERE UserName ='" & ENCRYPTPASSINSERTuser & "'COLLATE SQL_Latin1_General_Cp1_CS_AS AND Password ='" & ENCRYPTPASSINSERT & "'COLLATE SQL_Latin1_General_Cp1_CS_AS " cmdselectrt.CommandType = CommandType.Text dausermanager.SelectCommand = cmdselectrt cmdselectrt.Connection = conn dss.Clear() conn.Open() dausermanager.Fill(dss, "UserManager") conn.Close() If dss.Tables("UserManager").Rows.Count > 0 Then Dim cmdselectt As New SqlCommand cmdselectt.CommandText = "SELECT * FROM UserManager WHERE Privillagre ='" & dss.Tables("UserManager").Rows(0)(2) & "'" cmdselectt.CommandType = CommandType.Text dausermanager.SelectCommand = cmdselectt cmdselectt.Connection = conn dss.Clear() conn.Open() dausermanager.Fill(dss, "UserManager") conn.Close() If dss.Tables("UserManager").Rows.Count > 0 Then If dss.Tables("UserManager").Rows(0)(2) = "Clerk " Then Dashen_Bank_Automation_System.Show() Dashen_Bank_Automation_System.ClerkRegistrationToolStripMenuItem.Visible = False Dashen_Bank_Automation_System.EditMenu.Visible = False Dashen_Bank_Automation_System.ReportToolStripMenuItem.Visible = False
Me.Close() Else Dashen_Bank_Automation_System.Show() Dashen_Bank_Automation_System.NewToolStripMenuItem.Visible = True Dashen_Bank_Automation_System.EditMenu.Visible = True Dashen_Bank_Automation_System.WindowsMenu.Visible = False Dashen_Bank_Automation_System.ToolsMenu.Visible = False Dashen_Bank_Automation_System.CustomerRegistrationToolStripMenuItem.Visible = False Dashen_Bank_Automation_System.TansferToolStripMenuItem.Visible = False Dashen_Bank_Automation_System.LoanToolStripMenuItem.Visible = False Dashen_Bank_Automation_System.ClerkRegistrationToolStripMenuItem.Visible = True Dashen_Bank_Automation_System.ReportToolStripMenuItem.Visible = True Me.Close() End If Else txtpassword.Text = "Invalid password privilage !!!!" 'Label7.Show() End If Else Label8.Show() txtpassword.Clear() txtpassword.Focus() End If End Sub Private Sub withdrow_login_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load conn.Open() dausermanager.Fill(dss, "UserManager") conn.Close() DTcustomer = dss.Tables("UserManager") End Sub Private Sub btnok_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnok.Click Dim cmdselect3 As New SqlCommand Dim ENCRYPTPASSINSERTus As String ENCRYPTPASSINSERTus = stringTMD(txtusername.Text) cmdselect3.CommandText = "SELECT * FROM UserManager WHERE UserName ='" & ENCRYPTPASSINSERTus & "'" cmdselect3.CommandType = CommandType.Text dausermanager.SelectCommand = cmdselect3 cmdselect3.Connection = conn dss.Clear() conn.Open() dausermanager.Fill(dss, "UserManager") conn.Close() If dss.Tables("UserManager").Rows.Count > 0 Then Dim cmdselect As New SqlCommand cmdselect.CommandText = "SELECT * FROM UserManager WHERE Privillagre ='" & dss.Tables("UserManager").Rows(0)(2) & "'" cmdselect.CommandType = CommandType.Text dausermanager.SelectCommand = cmdselect cmdselect.Connection = conn dss.Clear() conn.Open()
dausermanager.Fill(dss, "UserManager") conn.Close() If dss.Tables("UserManager").Rows.Count > 0 Then password() Else txtusername.Text = "Invalid user name privilage !!!!" txtusername.Clear() txtusername.Focus() End If Else Label7.Show() txtusername.Clear() txtusername.Focus() End If End Sub
Sample code Encryption And Decryption

Private Function stringTMD(ByVal content As String) As String Dim M5 As New Security.Cryptography.MD5CryptoServiceProvider Dim Bytestring() As Byte = System.Text.Encoding.ASCII.GetBytes(content) Bytestring = M5.ComputeHash(Bytestring) Dim Finalstring As String = Nothing For Each bt As Byte In Bytestring Finalstring &= bt.ToString("x2") Next Return Finalstring End Function Private Function stringTMD5(ByVal content As String) As String Dim M5 As New Security.Cryptography.MD5CryptoServiceProvider Dim Bytestring() As Byte = System.Text.Encoding.ASCII.GetBytes(content) Bytestring = M5.ComputeHash(Bytestring) Dim Finalstring As String = Nothing For Each bt As Byte In Bytestring Finalstring &= bt.ToString("x2") Next Return Finalstring End Function Private Function stringunTMD5(ByVal content As String) As String Dim M5 As New Security.Cryptography.MD5CryptoServiceProvider Dim Bytestring() As Byte = System.Text.Encoding.ASCII.GetBytes(content) Bytestring = M5.ComputeHash(Bytestring) Dim Finalstring As String = Nothing For Each bt As Byte In Bytestring Finalstring &= bt.ToString("x2") Next Return Finalstring End Function
5.4 Testing
Once code has begun, the testing process can begin and proceed in parallel.AS each program module is produced, it can be tested individually, as part of the larger program, and then as part of larger system. The following are different testing strategies.
Unit testing
Particularly each form and report with concerned database is tested by a specific data. In this only the team can illustrate the output of error in a specific manipulation.
Integration testing
By combining each individual form and report with their concerned database us tested by giving general date. From this the team can understand that how the system work using the separate module
Validation Testing or System Testing It is the final step of testing. In this the team members tests the entire system as a whole with all
forms, code, modules. This form of testing is popularly known as Black Box testing or System tests. In this the team members tests all the functionalities in the System. All errors in the forms, functions, modules are tested.
5.5 Training
The organization will give necessary trainings for the new employees to make them aware of how to use the system.
5.6. Installation
Installation is the process during which the current system is replaced by the new system. This includes conversion of existing data, software, documentation, and working producers to this consistent with the new system. In this system used parallel installation approach. Installation Guide Insert software package CD on CD Rome Double click on the Package or right Click on the Package and then Click Open
Fill the required information In the Installation Click NextNext
Select Every Users Access the system
Click Next Follow the instruction in the installation process. Finally click Finish Button
Now you are finished the installation of the software Click StartAll Programsthen Select the Shortcut (Dashen Bank Automation System) in the Program files. Then perform your operations.
CHAPTER SIX
6.1 Conclusion
It is known that developing software for such a big organization is not easy. But the team have tried our best and developed interesting system for transaction management system of a Dashen Bank. It is flexible, accurate and attractive to access, update, delete, and producing report for any data that is found in the database with easy GUI approach. The manual effort and time required to complete the registration process was greatly reduced and the system notifies when loan return date expired and the amount of money to be paid as penalty depending on the bank rule. These are a few of the main works of the system. In addition to these, there are many works which are not mentioned here. Generally, the team confidently can say that the software is completed successfully with negligible errors. Finally the team expects the software will change the general business atmosphere of the Organization and market it more profitable than the previous manual system
6.2 Recommendation
First of all the project team would like to thank all computer science staff members. And then the team would like to recommend that the department must give the chance for the students to start earlier the project because only one semester is not enough to finalize and to give life to the project. The other thing is the department must set power reservation electronic equipments in the lab because there is power fluctuation and which kills the time. Also the department (concerning bodies) must follow up both the students (each team) and project advisors how they are proceeding and what difficulties they are facing at project development time. From our project side the team would like to recommend that, if any of the successors who want work on bank automation system could must finish the functionalities such as:
visa card system International money transfer systems like Western union Money exchange(like changing Dollar with Birr and others) Transfer of money from one branch to another
The above listed functionalities that the team left is because of time limitation.
Glossary
UML TVM LE
Unified Modeling Language Time Value of Money Life Experience
OOA OOD
Object Oriented Analysis Object Oriented Design
SQL-
Standard Query Language
VB.NET -Visual Basic dot Net DB BPRDashen Bank Business Project Re Engineering
References
Whitten Bentley Dittman , System Analysis and Design Methods, Tata McGraw Hill Edition, 6th Edition Addison Wesley - Visual Basic .NET Power Coding A Programmers Introduction to Visual Basic.NET Mastering Visual Basic .NET Database Programming Addison Wesley - Database Access with Visual Basic .NET Other Reference Books From Library and Internet

Dashen Bank Automation

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Dashen Bank Automation

Încărcat de

Drepturi de autor:

Formate disponibile

July 1, 2010

DASHEN BANK AUTOMATION SYSTEM

DASHEN BANK AUTOMATION SYSTEM

DASHEN BANK AUTOMATION SYSTEM

The rationale behind its name, "Dashen Bank"

DASHEN BANK AUTOMATION SYSTEM

Streangth and weakness of the existing system

1.2.1 Streangth of the existing system

need in a short time.

weakness of the existing system

1.3 BACKGROUND OF THE PROJECT

1.3.1 Team composition

DASHEN BANK AUTOMATION SYSTEM

Nebiyu Alehegn Yonas Baye

Liyew Mesele and Natnael Otoro

Table 1.1 team composition

Statment of the Problem

Final year project

DASHEN BANK AUTOMATION SYSTEM

1.5 Objective of the project

2. Specific objectives To describe general and specific objectives:

1.5.1 General objective:

dashen bank of Ethiopia, Arbaminch branch.

Final year project

DASHEN BANK AUTOMATION SYSTEM

1.6 Feasibility Analysis

1.6.1 Operational Feasibility

1.6.2 Technical Feasibilty

1.6.3 Economic Feasibilty

1.6.3.1 Cost Benefit Analysis A. Tangible Benefits

DASHEN BANK AUTOMATION SYSTEM

Cost reduction for material

Quantity per month

Total Price per year

Papers Pen Ticket and receipt Total material cost

8 packet 4 packet 50 packet

80 Birr 50 Birr 10 Birr

7680 Birr 3200 Birr 60000 Birr 70880 Birr

Table 1.2 materials cost for the current system

Quantity per month

Total Price per year

Papers Pen Ticket and receipt

4 packet 2 packet 50 packet

80 Birr 50 Birr 10 Birr

1000 Birr 1100 Birr 600 Birr 2700 Birr

Total material cost

DASHEN BANK AUTOMATION SYSTEM

Salary(For single) 5000 5500 5100

Total 10000 Birr 11000 Birr 10200 Birr

TP=36980 B. Intangible Benefit

1.6.3.2 Cost of the Project

DASHEN BANK AUTOMATION SYSTEM

Item hp computer Laptop Printer CD-ROM

Unit price 5500 Birr 10,000 Birr 5,000 Birr 16 Birr

Total hardware cost

Final year project

DASHEN BANK AUTOMATION SYSTEM

Table 1.5 Hardware cost

Final year project

DASHEN BANK AUTOMATION SYSTEM

Hardware improvement Cost = 143.1066x3 months

Price 1000 Birr 1400 Birr

160 Birr 100 Birr 4000 Birr 6660 Birr