MFMS Micro Finance Management System Presented by: SE 18 Team 2E Date : 10 th August 2011 INT/MFMS/MA.1 Team SE18 2E

Outline Introduction Use Case Modeling Overall Architecture Demo Transition Strategy Project Progress Implementation Strategy 2 INT/MFMS/MA.1 Team SE18 2E

Introduction INT/MFMS/MA.1 Team SE18 2E 3

Micro-Finance is provision of thrift, credit and other financial service and products of very small amounts to the poor in rural, semi-urban and urban areas for enabling them to raise their income levels and improve living standards. Objective  Improve the socioeconomic status of low income people  Increase employment by improving their access to financial services INT/MFMS/MA.1 Team SE18 2E 4 Micro Finance

Overview Provide a complete IT solution for Micro Finance operations incorporating a Mobile channel which will cover Enrolment System Loan Disbursement /Collection using Mobile Channel Transparent & Scalable solution Handle large Volume of Data Micro Finance Management System (MFMS) INT/MFMS/MA.1 Team SE18 2E 5

The Components of the proposed System Back Office System ie., MIFOS Mobile Channel (IPT 300) Branch Office Support System Micro Finance Management System (MFMS) INT/MFMS/MA.1 Team SE18 2E 6

Micro Finance Management System (MFMS) Users of the System Administrator Administer the entire system that will be located in the Head Office Branch Officer/Manager Manage the Field Operation Loan Officers Identify the Members, Form the group, Distribute the Loan and Collect Payments INT/MFMS/MA.1 Team SE18 2E 7

Workflow Micro Finance Management System (MFMS) Loan Officer collects Members data using the Mobile Channel Branch Manager approves the Member and the Loan Amount Branch Officer uploads data into MIFOS Branch Officer downloads /uploads data into Mobile Loan Officer disburses the loan Loan Officer collects payment INT/MFMS/MA.1 Team SE18 2E 8

Use Case Modeling INT/MFMS/MA.1 Team SE18 2E 9

10 Use Case Model Survey

INT/MFMS/MA.1 Team SE18 2E 11 Use Case: Loan Payment Collections

INT/MFMS/MA.1 Team SE18 2E 12 Use Case: Upload Data to MobileChannel

Overall Architecture 13 INT/MFMS/MA.1 Team SE18 2E

Value Proposition Eliminate Paper Oriented Process Information Anywhere Bring MFI services to the user Effective resource utilization MFMS 101 Mifos Handheld IPT300 Data Microfinance Management System INT/MFMS/MA.1 Team SE18 2E 14

Mifos Technology Hibernate Struts JSP Spring BIRT reporting Code Modular build with Maven/Hudson Run in any servlet container Code base divided into modules, API, plug-in 214 Database tables About 120,000 lines of code Mifos-webservices module Spring WS Contract first web service ClientService, LoanService, SavingService Web Services 5060 git://mifos.git.sourceforge.netgit://mifos.git.sourceforge.net / mifos/head mifos/head INT/MFMS/MA.1 Team SE18 2E 15

Mifos Handheld IPT300 Data Microfinance Management System BOSS Data Branch Office Support System (BOSS) Technical Requirements Data Transformation Central point of communication Configuration management Download business data from Mifos Transform data for IPT300 Receive data from IPT300 Apply Business rules Send formatted data to Mifos Admin control Dashboard for monitoring Economically feasible to solution INT/MFMS/MA.1 Team SE18 2E 16

HTML Java Server Pages Spring MVC Framework Data Management Data Exchange Service Sync Service Device Management Authenticati on Service Service Layer Spring WS Hibernate Object Relational Manager Apache Tomcat web server 7.0 MySql DB MFMS User Interface IPT 300.NET Library Communication management Device Sync Management Device Security Remote Data Access Web Services Data Access layer.net compact framework MS SQL CE Business Layer Mifos BOSSBOSS MFMS Mobile MFMS Architecture INT/MFMS/MA.1 Team SE18 2E 17

Prototype Mifos- BOSS interface prototyping Study Mifos and classify functionalities required for BOSS Proof of concept Estimate development effort required for Mifos 5060 Demo MFMS Mobile UI Customized User Interface Screen space optimization and data organization INT/MFMS/MA.1 Team SE18 2E 18

MFMS System Components MFMS Mobile Client Communication Manager Device Synchronization Manager Remote Data Access Device Application Branch Office Support System Data Access Manager Data Management User Management BOSS Console Sync Service Authentication Service INT/MFMS/MA.1 Team SE18 2E 19

Architecture - Physical view *Hardware redundancy has not been shown INT/MFMS/MA.1 Team SE18 2E 20

Sizing and Performance Max No of Clients handled by Loan offOfficer (8 Hrs per day * 60) minutes /10 = 48 ~ 50 clients Total number of clients served in a day 50 Clients per loan officer * 400 Loan Officers = Clients Estimated number of transactions per customer will be limited to 3. (Assuming a client registration, a loan disbursement/loan collection and a saving account.) Transaction per day = clients * 3 transactions = transactions Estimated number of transactions on average to the BOSS server: 2 per sec Avg Transactions/sec = 60000/(8 Hrs *60 * 60 ) = ~2 Transactions per second. Estimated maximum data upload size: 3 MB per day Client record size = Average no of data fields per request = data fields per request * 100 bytes per field = 3000 bytes /1024 ~ 3KB Total size = * 3KB = 18000KB ~ 18MB Response time for client request and timeout: 1 second response and 5 second timeout BOSS database must be able to store data up to one week Data must be processed within a week. Database size for 7 days client records storage: Total size = 7* 18 = 126 MB INT/MFMS/MA.1 Team SE18 2E 21

Demo INT/MFMS/MA.1 Team SE18 2E 22

Menus / Menu items MIFOS - Mobile Channel Prototype INT/MFMS/MA.1 Team SE18 2E 23

Create Profile MIFOS - Mobile Channel Occasionally connected system First Name INT/MFMS/MA.1 Team SE18 2E 24

MIFOS - Mobile Channel Prototype Create Profile Date of birthSalutation INT/MFMS/MA.1 Team SE18 2E 25

MIFOS - Mobile Channel Prototype Savings – Deposit collection INT/MFMS/MA.1 Team SE18 2E 26

MIFOS - Mobile Channel Prototype Savings – Deposit collection INT/MFMS/MA.1 Team SE18 2E 27

Transition Strategy INT/MFMS/MA.1 Team SE18 2E 28

The mobile channel application for the Micro Finance system is built into IPT300 Handheld device. Application development on the device will use.NET Compact Framework 3.5 with the aid of SDK for IPT300 handheld. To store data locally SQLCE 3.5 DB shall be used on IPT-300 Industrial Handheld Terminal MVC Architecture on.NET compact Edition shall be used; which helps in A structured way of passing data Better organized code Platform independent navigation to views More details along with analysis and package diagram are described in the Transition strategy for Mobile Application document Mobile Channel Transition Strategy INT/MFMS/MA.1 Team SE18 2E 29

BOSS is installed as a web Model View Control (MVC) on Apache tomcat BOSS shall be written as a java based web application (J2EE) implementation approach for BOSS is to use Spring MVC BOSS has its own data storage and for that we are using MySQL DispatcherServlet is one of the boundary objects of BOSS RequestDispatcher is the control object ModelAndView contains the model data and the name of the view BOSS Transition Strategy INT/MFMS/MA.1 Team SE18 2E 30

Project Progress INT/MFMS/MA.1 Team SE18 2E 31

Project Progress – Where are we ? Completed Phase 2 activities INT/MFMS/MA.1 Team SE18 2E 32

Project Progress – Phase 3 INT/MFMS/MA.1 Team SE18 2E 33

Project Progress – Phase 3 INT/MFMS/MA.1 Team SE18 2E 34

Strategy for Implementation of MFMS System INT/MFMS/MA.1 Team SE18 2E 35

Major Tasks for the Phase 3 Prepare the development environment Prepare the required documents such as Detailed Design Spec, Test Plan Develop the Source code Perform the Unit Test, system Integration Test and UAT Provide Training Roll out to Production system INT/MFMS/MA.1 Team SE18 2E 36 Management Strategy

Appendix INT/MFMS/MA.1 Team SE18 2E 37

Changes to dynamic behavior (BOSS) Sequence diagram for create-user use case INT/MFMS/MA.1 Team SE18 2E 38

Static behavior changes to MFMS Mobile UCRR(A)

Management Problems INT/MFMS/MA.1 Team SE18 2E 40 NoProblemDescriptionSolution 1 Communication and Resource Management Member is unavailable for discussion. Fix schedule and venue for next meeting. Clearly specify agenda and attendances. Manage and encourage flexible discussions. Such as encourage separate informal discussions 2 Delegation/Task Control Member unconfident to take tasks. Member unable to finish tasks assigned on time. Team discussion to assign work based on what areas the member is strong Seek agreements from members on the tasks assigned. 3 Stress among team members Due to study load, workload, together with our final project load Encourage team members to prioritize tasks and use time efficiently. Such as 1- 2 hours/day for projects. Stress reduction.