final presentation

1. COLLEGE OF INFORMATICS

2. 1.INTRODUCTION
This paper is a project proposal paper for Industrial Project which is done on
automating saving and loan System of Dessie menafesha micro- bank institution.
The project will purposely do on Automating the current paper based functioning
of this institution.
This project will be done by proposed and analyzing the system, by using
different methods, will accomplish and be designed by using tools available for
this purpose. After a while, the project will give many benefits and solutions for
the analyzed problems to the organization and to the customer service as well.

3. 2.Historical Background of the organization
Dessie Credit and Savings Institution (DCSI) was Initially established in October
1988 E.C as a branches with the former Ethiopian Relief Organization (ERO), The
current Organization for Rehabilitation and development in Amhara (ORDA).
 It was licensed by the national bank of Ethiopia as a micro bank intermediary share
company in April 1989.
Now a day this Dessie Credit and Savings Institution has been offering service in all
,Woreda , and 86%(3224) of the total kibbles in the Region through 4000 Sub-
branches and 157 micro banks.
The main reason for the establishment of Dessie micro bank management system
was to support ACSI S/ Wollo zone people, with low income ,with loan by asking
small collateral ,but our project is concern on automated computer based system.
 This organizational structure:-DCSI has three structural layers.
Head office ,Branches office and Sub branches office

4. 3. Vision:
By the year 2007 G.C. creating an institution which can provide money for those
who are unable to work because of financial problem and becoming customer’s first
choice.
 ACSI aspires to see peoples of the region liberated from grips of object poverty
with all the power determining their future in their own hands and to ensure its
institutional sustainability.
4. Mission:
The mission of Amhara micro bank is developing our country economy by
integrating s/Wollo dessie menafesha micro bank’s (finance) with governmental and
non-governmental institutions.
To provide money for customers with financial problem.
5. Values
A. Creating permanent relationship with customers.
B. Employees are the institution’s main asset.
C. Our employees give priority to organizational benefit rather than personal
benefit.
D. Delivering quality services with skilled, motivated, inspired, ethical and
presentable staff.
E. Transparent working procedure is a norm and Fair treatment of staff.

5. 6.Statement of the Problem
Lack of accuracy and loss of document: Since registration is
handled manually there is getting of two or more for single
husband and wife and also there is lots of applicant
information.
Data Redundancy: Since there is no organized database there
is a problem of giving more than 5001 birr for a single person.
There is wastage of vast amount of human power.
There is no security in the documents of the system.
It has wastage of time in the system.
Data modification is very difficult. etc

6. Figure 1.1work flow diagram
Figure1. 2 Work Hierarchical diagram

7. 7. General Objectives
•To develop web based (automate) micro banking management system.
8. Specific Objectives
Study the existing system and identify its problem.
Design the system as per user requirement specification.
Develop user friendly interfaces.
Develop the website as per the business rules.
Creating a different access role in the system.
Develop a database for the recording system.
Testing the system to overcome the system functions.
Generate different reports as per the demand of the organization.

8. 9.Scope of the Project
The scope of the project is about tasks that will be performed throughout the
system.
Our main goal in doing this system is making the existing manual based micro
bank service management system into an automated, more efficient, less time
consuming and overall a better working system and users can access the
information web based.
Accept and record all customer data.
Create account and record the loan data.
Accept and record withdrawal data.
Accept and record customer information.
Assign people into their house, address.
Register employee detail information.
Prepare the yearly budget and handles expenditure summary.
Create account, Update, delete, search and so on….

9. 10. Limitation of the project
Limitation the system means the weakness or the inability of performing tasks
compared to other similar systems. Our system has limitations compared to
others in terms of online transactions since there is money transaction (not
money transfers) but it is difficult to exchange web based.
Our system has also limitations on a place that has not internet accessibility
because it is depend on connection since it is web based.
The limitation of our system is that all users may not be participating directly to
the system since it is not done by a local language.
Power availability is also scarce, with vast rural areas that are not connected to
power grids as well as frequent blackout in major urban areas such Kombolcha,
dessie etc.
Use only on this micro bank and Time and budget.
Universal micro bankers may be tempted to take excessive risk.

10. 11.Significance and Beneficiaries of the project
Bring the institution’s system to be centralized within the single branch.
Help the saving and loan operations to be performed effectively and efficiently.
Provide up-to-date factual information for the manager.
Fasten the organization activities.
Decrease resource wastage of the organization.
Ensure the reliability of the organization (reliability in terms of security, resource
management, etc.).
It minimizes the workload of employees.
It minimizes loss of documents.
It minimizes time to retrieve search and update files.
To avoid the data redundancy of the system.
To minimize the human power for implementing the system.
To improve the efficiency of registration and certification.

11. The target beneficiary groups are:-
Societies:-
The users become beneficiary and save them from extra expense for finding
customer and They maximize customer choices.
Gets satisfactions the needs of information for customer.
They save time and money at the same time.
Government:-Gets the correct tax values from the organization and Get satisfactions
since the government is the society.
Users:- Be profitable since they gets the correct commissioning and the system is
available for a every users. Decreasing workload and Save time and energy loose by
searching. You Known by others since it is an web based application and Avoids
redundancy of documents. They got loyalty and truthfulness.
They promote customer easily.

12. 12. Feasibility Study (analysis)
To meet user requirements and
 Best utilization of available resources.
Develop cost effective system and
To develop a Economic, technically , Political feasible systems.
13. Software tools
The different kind of software we used for developing the project i
Microsoft office word 2007 for documentation.
Microsoft Visio 2010 – to design Gantt chart or planning and for scheduling
phase.E-Draw Max-– to design Sequence Diagram, Class Diagram, Activity diagram and
Use case Diagram…..
Wamp server - for web server software and xamp server - for xstisibl server
software. Programming language- PHP and java scripit.

13. 14.The reason that we choose this MYSQL server is:-
1. Scalability and Flexibility
2. High Performance
3. High Availability
4. Robust Transactional Support
5.Web and Data micro banking Strengths
6.Strong Data Protection
7.Comprehensive Application Development
8.Management is to Ease
9.Lowest Total Cost of Ownership
10. Open Source Freedom and 24 x 7 Supports

14. ID Name Responsibility
ITR/1489/04 Dessale andargie ALL
ITR/1404/03 megersa regasa ALL
ITR/1382/03 DERBE TAYE ALL
Project Advisor: Instructor ALEMU JERGIE
15.Project Team Organization

15. Chapter Two
Introduction
The main objective of this part is to study the nature of the system in detail and
identify the problem as well as to define the relevant way to design a new system
for S/ Wollo Dessie branches micro bank management system.
we will try to explain the tasks performed as follow:
Opening Saving Account and Giving loan services.
Withdrawal and Deposit and manage by using manually.
Gives pension payment but not regularly.
Existing System
The existing system refers the manual system that is available currently. In this
chapter we deeply describe the existing system in order to have a better
understanding.
 a massive knowledge about the existing system.

16. 2.1 The main reason why the existing system describing is:-
To know the back ground of the existing system.
To identify which of these problems could be solved by the current project.
To determine the essential business practice to be preserved if any.
To identify problem of the existing system.
To know the statement of the problem and challenge of the system and to come
up with the perfect solution
The major players that are involved in the existing system are:
1.clerck 2.cashery
3.manaager 4.Supervisor
5.customer re/n office 6.customer
7. Loan Officer

17. Problem of the Current (existing) System
•The customers will decrease.
•The productivity of the organization is not effective.
•Information related problem
Output
•Generating report requires skilled person and greater attention. The report may
encounter inaccuracy. Inaccuracy in updating relevant information and calculating
interest (balance). Data is not flexible – not easy to meet new information needs
from stored data.
Input
•Redundant information is captured. Customer information is registered in various
cards again and again. The inputs are not validated (i.e. the system cannot check
whether the customer has account before). Mishandling of customer information
may occur.

18. Problem of the Current (existing) System
The customers will decrease.
The productivity of the organization is not effective.
Information related problem
Output
Generating report requires skilled person and greater attention. The report
may encounter inaccuracy
Input
Redundant information is captured. Customer information is registered in
various cards again and again. The inputs are not validated (i.e. the system cannot
check whether the customer has account before). Mishandling of customer
information may occur.
Storage
Data is difficult to correct and maintain. Data is stored redundantly in multiple
files.
Data is not secure from accident or vandalism (damage).

19. Constraints of the Existing System
Performance: The micro banking management system take weeks and months for
manual verification of certificates, reports and any sort of other service requests .
There is a different constraint that limits us to perform required activities.
 Due to limited development time we cannot perform activities with related
organizations, because of environmental constraints we cannot did an online
transaction in our system, due to less experience of the organization it makes us less
informed about how the system does.
Economics:-
Costs (Budget of the office……)
Stationary cost is increasing.
Birr of Po.box.
Security:-
Too little security or control
Service:-
The existing system is not that easy to use.
The existing system is uncomfortable to use.
The system is not easy to coordinate.
-un real able forever.

20. New system
The advantage of the new system is:
Performance: The performance of the proposed system does provide fast response time
because it is easy to access data from the stored document.
1. Economy
2. Efficiency: the Web based placement and management System by itself is short and
clear and in this system there is no duplication of data through the new system is
powerful to manage things around house.
3. Service: the system can be visited by anybody who is a member of the house agency.
5. Accessibility: the system can easily be accessed by the operators (authorized persons).
6. Availability: The system is available with its components until it has failed (replaced by
another system) throughout the life of the organization.
7. Security:

21. Functional Requirements
Updating customer Account (balance)
The system update the customer balance
Storing Customer Information.
Change Customer Information
The system changes the customer information like signature, address and other
related information as needed at.
The main functional requirements of the system are:-
Register Users: The customer re/n officer can register the customers if they
cannot able to write and read. The customers can register web based by visiting
the this micro bank.
customer Registration: Customers as well as user can register the available
properties that can be loan or deposit.

22. •Non Functional Requirements

24. System use case diagram and Documentation

25. Name Login
Description It allows user to login into the system.
Actor/s Customer re/n officer, administrator, Manager, supervisor.
Precondition The users should have registered into the system.
Post condition The user will login in to the system and able to access the
required home page.
Basic course:
of action
Actor customer re/n
officer Step 1. Initiated
when the user wants to
login into the system
Step3.The user fill the
inputs his/her user
name and password.
System response Step2. The system
Displays the User Login Page. Step4.
The system verifies the username and
password.Step5.The system displays the
appropriate home page.Step6. The use
case ends
System Use case documentation for Login

26. 6 Sequence Diagram Documentation
Sequence diagrams are used to model the logic of usage scenarios.
 A usage scenario is exactly what its name indicates the description of
a potential way that your system is used.
The logic of a usage scenario may be part of a use case, perhaps an
alternate course.
It may also be one entire pass through a use case, such as the logic
described by the basic course of action or a portion of the basic course
of action plus one or more alternate scenarios.
 It may also be a pass through the logic contained in several use cases

27. Figure6.2
Sequence
diagram
for
loan
account
Figure6.2 Sequence diagram for loan account

28. Activity Diagram Documentation
An Activity diagram is similar to a flowchart to represent the flow from one activity to
another activity.
Activity diagrams and State chart diagrams are related. While a State chart diagram
focuses attention on an object undergoing a process (or on a process as an object), an
Activity diagram focuses on the flow of activities involved in a single process.
 The Activity diagram shows how these single-process activities depend on one
another

29. State chart modeling diagram Documentation
The state chart diagram is shows the change of an object through time from one
state to the other state. State chart modeling is used to show the sequence of states
that an object goes through, the events that cause the transition from one state to
the other and the actions that result from a state change . The following figure
shows the state of the objects.
production
placed
process order
(amount<=25,000)
deliver
product
to
customer
state chart diagram
customer sumit
oreder web based
delivered invoiced
isuue of
to customer
process order
[amount<=25,000]
customer to make deposit required

30. Chapter three
System Design
Introduction
This chapter mainly concerned with the design part of micro banking management
system. In order to make the implementation easy the design is very important.
In this chapter we will see the different type of class type architecture. such as user
interface layer, process/control layer, business/domain layer, persistence layer and
system layer and also different types of system modeling techniques that are used for
the implementation of the system such as class modeling, state chart modeling and
also some system design techniques such as user interface design are also to be
covered in this chapter.

31. Purpose of the system
The main purpose of system design is to provide architecture design, design
goals of the system, detailed class design and database design for the system.
It is the process of defining and developing systems to satisfy specified
requirements of the user.
Goal of Software Design
Verification, Correctness, Testing ,Formal verification ,Code Inspection etc
 This part of the document mostly is driven from the non-functional requirement of
the Requirement Analysis Document.
The design goals represent the desired qualities the system should have and provide
a consistent set of criteria that would be taken into consideration when making
design decisions.The aim of the design is improving the following non-functional
requirements .Faces many challenges to produce a good product, e.g. shifting
requirements. But .what do we mean by good? We need some clear goals her.

32. Class Diagram
INTRDUCTION
Class diagram is the building block of the system that we develop.
 It shows all the objects and tells us how they are interrelated.
Class diagrams are the most popular UML diagrams used by the object oriented
community.
 It describes the objects in a system and their relationships.
 Class diagram consists of attributes and functions.
A single class diagram describes a specific aspect of the system and the collection of
class diagrams represents the whole system.
Class diagram Basically the class diagram represents the static view of a system.
Class diagrams are the only UML diagrams which can be mapped directly with
object oriented languages. So it is widely used by the developer community

34. Proposed Software Architecture
Figure 35.4the Architectural View of micro bank Management system

35. 3Class type architecture
The Class Type Architecture of the DMBM System has the following layers and
these layers will be discussed in the table below one by one.
•Interface (user interface and system interface) Layer
•Process (application and controller) Layer
•Business (Domain) Layer
•Data (Persistence) Layer
•System Layer

36. Figure 38.model of hierarchy modeling diagram
micro bank
mgt system
user
admin manager supervisor
customer
relation
officer
update
delete
create user
account
login
logout
view
report
check
balance
aprove
account
generate
report
generate
report
view report
login
logout
open cust account
withdraw
payment
check balance
login
logout
module hierarchy diagram

37. •The Class type architecture of the system
Figure 37.4class type user interfaces

38. Layers Descriptions
Interface (User
Interface) layer
The interface layer is the layer in which the user interacts with
the WRMS System
Process (application
and controller) Layer
The process layer is a layer in which different applications of the
WRMS System like login, registration and search employee
profile are performed
Business (Domain)
Layer
This layer implements and compare the user data within the
business objects, which means it validate the required data with
the existing data for its correctness.
Data (Persistence)
Layer
Persistence layers encapsulate the capability to store, retrieve,
and delete objects/data and it is the class layer in which all data
about the employee and the file are stored and accessed.
System Layer System classes provide operating-system-specific functionality
for DMBMS System. This layer includes communicate all of the
remaining four layers.
Class type architecture

39. 5 Deployment modeling
 Deployment modeling is used to show the hardware of the system,
the software that is installed in the hardware and also shows how the
software and the hardware components work together.

40. Persistence Modeling for Object Oriented Data Base

41. Component Modeling DIAGRAM
Component diagrams show how the physical components of a system are
organized.
 shows which component or objects will be accessed by whom and what type of
security infrastructures it is using. The diagram is simulated below.

42. Figure 29.2 Activity diagram for generating loan report

43. Chapter four
Implementation
Introduction
Developing software is a complex process.
 No matter how hard we try to eliminate all faults simply by going through the
development phases which is requirements elicitation, requirement analysis, system
design, and implementation, however through good practice we can make sure that
the most series fault does not occur in the first place.
 In addition we need a separate testing phase, with the goal of elimination all
remaining faults before release the system.
To simplify the testing process the project team followed the different types of tests
that break the testing process up into the distinct levels

44. PURPOSES OF TESING
The main purpose of software testing is to assess or evaluate the capabilities or
attributes of a software weather it meets the customer’s requirement and used to
identify error of the system before release.
Testing and evaluation of the system gives different benefits for the system
development team.
 It helps the team to find defects and builds confidence.
Therefore, the team should select appropriate testing approach based on the
project area

45. UNIT TESTING
 Is done at the source or code level for language-specific programming
errors such as bad syntax, logic errors, or to test particular functions or
code modules.
The unit test cases shall be designed to test the validity of the programs
correctness.
Sample Tests
•Check whether the return type of the functions is correct.
•Check how the sub procedures or functions are call correctly.
•Check if the correct output is produced for different inputs.
•Check the efficiency of the code with respect to the memory and CPU time.
•Check the input data that we write on the GUI must be submitted to the
data base

46. Integration Testing
In this level of testing we have examined how the different procedures
work together to achieve the goal of the sub system.
The type of integration testing that we have followed is bottom up.
Sample Tests
1. Check the interaction between individual functionality which
performs the specific tasks.
2. Evaluate the functionality of subsystem after combination all
individual functionality.
3. Identify the independency of each subsystem with other subsystem.

47. System Testing
In this level of testing process we have examined how the whole subsystems of
DMBMS work together to achieve the desired goal (user’s requirements of the
system).
The goals of system testing are to detect faults that can only be exposed by testing
the entire integrated system or some major part of it.
Sample Tests
1. Evaluate the functionality of subsystem after combination of individual subsystem
weather it works correctly or not.
2. Check the coherence and coupling of each subsystem.
3. Check the overall functionality of DMBMS that to achieves the user’s
requirement.
4. Measure the system boundary which is beyond the goal or not.
5. Measure the weakness and the strength of the system using different metrics.
6. Check the interaction of each subsystem that performs the specified business
process.
7. Verify the system completeness based customer’s requirement.

48. Acceptance Testing
Our customer (real users) will participate on the acceptance testing of our
system. According to system requirements and other resources(documentation,
source code, user manual) test cases are generated to determine(validation and
verification) whether the system satisfies users need and expectation to maintain
the reliability of our system and also meet the users requirements.
Test Plan
Features to be tested (Functional Test Specifications)
This section of the test plan lists some of the items of Micro bank Management
System and web based application that will be tested.
The tests that are done are as follow:
Sample Tests:-
•Test Login user Test Register employee
•Test Record Customer information.
•Test Create user account Test Create customer account.
•Test Control user account

49. Test Case ID Test Case ONE
Description Tests the Login Screen
Applicable for Firefox, internet explorer, Google chrome, opera etc.
Initial Conditions The system can display “login” user interface/login URL
Step Task & Expected Result
1  Step Description: local host /MICRO BANK/index.php
 Expected Result: login page will be displayed in the right panel of the home page. Login page has the following
fields.
- “User name”, text field.
- “Password”, text field.
- “Login”, button.
2  Description: when already login page is displayed, enter username and password.
 Expected Result: pass criteria or fail criteria
- Fail criteria: invalid username or invalid password, error message will be displayed and the page will be redirected
to the URL http://localhost/afms/.
- Pass criteria: valid username and password, and the page will navigate to the home by his/her user privilege.

50. We will recommend for Future Work’s
 create user attendance.
 create Customer management.
To create maintenance of DMBM system.
Add Foreign currency exchanging system(money,
dollar, pound, Etc..).
To create Money transfer for any branch in all Ethiopia
Micro bank branch.
Interest rate with in change time to time system
activity.

51. I will say’s that thanks for Our
1 . Advisor’s Mr. Alemu jergie
2. Examiner‘s mr. Julius’s
3.
4. department head mr.yonass
5.group members ( Megarsa and Diribie)
6.class mate students
Thank you so much !!.

52. 1.Dessale…ITR/1489/04
3. Diribie…..ITR/1382/03 2.Megars….ITR/1404/03
I WISH GOOD LUCK FOR YOUR GRAGUATION!!!