1. MFMS Micro Finance Management System INT/MFMS/MR.3 Team SE18 2E Presented by: SE 18 Team 2E Date : 17 th January 2012

2. Outline Project Background Project Overview Project Metrics High Level Architecture Implementation Details Post Implementation Review Q&A INT/MFMS/MR.3 Team SE18 2E

3. Project Background INT/MFMS/MR.3 Team SE18 2E

4. Microfinance Source: www.econ.worldbank.org Informal 1-on-1 personal Over 3 billion people live on less than $2 a day and Only 17% of them have access to formal financial services 18%37%26%4%16% Formal Semi – Formal Banks, Insurance co.s Microfinance Institutions Employers, relatives, neighbors. friends Moneylenders, pvt financiers ? 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. - NABARD & Scenario of supply of formal financial services to low income group evolved to serve a part of market largely avoided by traditional financial Institutions Provides affordable finance INT/MFMS/MR.3 Team SE18 2E

5. Project Information Project: Micro Finance Management System (MFMS) Client Integratech Pte Ltd, Singapore Actual Start Date 15 Jan 2011 Actual End Date 16 Jan 2012 INT/MFMS/MR.3 Team SE18 2E

6. Team Organization Client Project Manager Vijeyakumar K Project Manager (ISS) Maya Roosevelt Technical Lead Karthikeyan Krishna m urthy Business Analyst Anupama Sarada Database Administrator Jawahar Chelliah Solution Architect Satish Kumar Software Engineer Bright Devakadaksham Lilly Quality Manager Achilles Tan ** Jawahar Chelliah dropped out from the project in the 3rd Phase of the project. INT/MFMS/MR.3 Team SE18 2E

7. Project Objective To provide an automated solution for Micro Finance Organizations in their daily operations in the Branch Office as well as on the field. To enable mobility for the efficient field operations of MFI branches. INT/MFMS/MR.3 Team SE18 2E

8. Project Overview INT/MFMS/MR.3 Team SE18 2E

9. MFMS Workflow INT/MFMS/MR.3 Team SE18 2E 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

10. MFMS Major Functions Customer Registration To provide a means for the Loan Officer to register new Members by recording their personal and financial information into a Mobile Channel. The registration details must then be communicated back to the Branch Office. Loan Distribution To provide a way for the Loan Officer to disburse the approved loan to the registered members using a Mobile Channel. The disbursement confirmation must be communicated back to the Branch Office. Payment Collection To provide a way for the Loan Officer to collect dues from the Registered Members using a Mobile Channel. The collection details must be communicated back to the Branch Office. INT/MFMS/MR.3 Team SE18 2E

11. MFMS System Components INT/MFMS/MR.3 Team SE18 2E BackOffice (MIFOS) Caters to the daily operations of a MFI branch and is used by multiple branches with a common share enterprise data repository Mobile Channel Hosts an application to enable mobility to the field operations of MFI branches to make the MFI operation efficient and faster. BOSS Acts as a gateway between BackOffice and Mobile channel and it will perform data transfer operation between these two sub systems.

12. Use cases Implemented User Authentication BOSS Login/Logout Mobile Login/Logout Create Customer Profile Collect Details Upload Data to BOSS Loan Distribution Download Loans to Mobile View Loans List Loan Disbursement INT/MFMS/MR.3 Team SE18 2E Loan Payment Collection Download Collections (Savings & Payments) to Mobile View Collections List Confirm Collection Upload Collections to BOSS Sync Collections to MIFOS Manage Users Create/Update/Delete Users Device Management Create/Update/Delete Device Dashboard

13. System Architecture INT/MFMS/MR.3 Team SE18 2E

14. Overall System Architecture INT/MFMS/MR.3 Team SE18 2E

15. http://mifos.org/product/features MFMS 101 Mifos Handheld IPT300 Data Microfinance Management System INT/MFMS/MR.3 Team SE18 2E

16. 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 http://ci.mifos.org:9000/project/index/1 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 http://ci.mifos.org:9000/project/index/1 INT/MFMS/MR.3 Team SE18 2E

17. 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/MR.3 Team SE18 2E

18. 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/MR.3 Team SE18 2E

19. 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/MR.3 Team SE18 2E

20. 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/MR.3 Team SE18 2E

21. Development View Web Services INT/MFMS/MR.3 Team SE18 2E

22. MIFOS Technology Hibernate Struts JSP Spring BIRT reporting Code Modular build with Maven Run in any servlet container Code base divided into modules, API, plug-in Other 214 Database tables About 120,000 lines of code http://ci.mifos.org:9000/project/index/1 INT/MFMS/MR.3 Team SE18 2E

23. Technical Strategy INT/MFMS/MR.3 Team SE18 2E

24. Implementation Details INT/MFMS/MR.3 Team SE18 2E

25. Project Metrics INT/MFMS/MR.3 Team SE18 2E

26. Planned Vs Actual PhasesNoMilestoneTarget DateActual Date Inception Phase (Project Planning) 1Initial Planning 1.1Produce Project Plan23-Mar-11 1.2Produce Quality Plan16-Mar-11 2Requirements Specification 2.1User Requirements Specification1-Apr-11 3Phase 1 Management Admin / QA 3.1First Quality Audit5-Apr-11 3.2First Project Presentation12-Apr-11 Elaboration Phase (Analysis & Design) 4Functional Specification 4.1Produce Use Case Model survey19-Apr-1126-Apr-11 4.2Produce Use Case Realization Report (Analysis)19-May-1113-Jun-11 5Prototyping 5.1Develop Prototype for feasibility with MIFOS27-Apr-112-Jun-11 5.2Produce Prototype Study Report29-Apr-1114-Jun-11 6High level Design Specification 6.1Produce Software Architecture Specification25-Apr-1130-Jul-11 6.2Produce Transition Strategy from Analysis to Design25-Apr-1130-Jul-11 7Phase 2 Management Admin / QA 7.1Second Quality Audit2-Aug-11 7.2Second Project Presentation10-Aug-11 Notes :  The scope of the project was very wide based on business requirements.  MIFOS installation, setup, and interface had many problems. INT/MFMS/MR.3 Team SE18 2E

27. Planned Vs Actual PhasesNoMilestoneTarget DateActual Date Construction Phase (Implementation) 8Detailed Design Specification 8.1Produce Design Model Report27-Aug-1120-Oct-11 9Source and Executable Code 9.1Code and Unit Testing1-Nov-1123-Dec-11 10Systems Testing 10.1Produce Systems Test Plan & Test Cases2-Sep-1126-Nov-11 10.2Produce System Test Report18-Nov-1131-Dec-11 11Integration & Installation Testing 11.1Produce Integration Test Plan2-Sep-1126-Nov-11 11.2Produce Integration Test Report2-Dec-112-Jan-12 12Documentation 12.1Produce User Guide7-Dec-115-Jan-12 13Deployment and User Acceptance 13.1Produce User Acceptance Test Plan31-Oct-1126-Nov-11 13.2User Acceptance15-Dec-11 14Project Closure 14.1Produce End-Of-Project Report28-Dec-128-Jan-12 15Phase 3 Management Admin / QA 15.1Third Quality Audit10-Jan-12 15.2Third Project Presentation17-Jan-12 Notes :  UCRR had to be updated based on 2 nd audit and Unit 7 peer review audit comments  Mobile device was not available for development and testing all the time as the client needed it for overseas demos. INT/MFMS/MR.3 Team SE18 2E

28. Effort Estimate Unit of Measurement EstimateActualVariance (%) Total Project Effort Man Days51557011% INT/MFMS/MR.3 Team SE18 2E The Estimated Total Project Effort is based on estimates provided in the Project Plan (INT/MFMS/MP.2) section 6 Staff Effort Estimates. The Actual Total Project Effort is based on the figures calculated from the Action Items List form (INT/MFMS/MM.2). The form was used to record and track all action items in a weekly or bi-weekly basis during team meetings.

29. Challenges INT/MFMS/MR.3 Team SE18 2E

30. Management Challenges ChallengesResolution The scope of the project was very wide based on business requirements. Performed function counting and evaluated the functions to implement. Used existing backend application, MIFOS, for the team to focus on the and its integration with MIFOS (thru BOSS). The team was not proficient to handle Spring and Hibernate Adequate time was allocated to the team members to self-study in Spring. Mobile device was not available for development and testing all the time as the client needed it for overseas demos. The Mobile application and unit test was done in Emulation and the system test was done when the device was available One team member (Jawahar Chelliah) dropped from MTech and his tasks had to be distributed to others. The team approached the client and de-scoped the project work. However the major features were implemented. The client was busy with his real time projects and frequent overseas trips which delayed the sign off of the User Acceptance. - INT/MFMS/MR.3 Team SE18 2E

31. Technical Challenges ChallengesResolution Analysis and Design concerns in the project caused the team to rework on the UCMS and UCRR(A). Analysis and design work artefacts were subjected to Peer Reviews. Team consulted with expert (Boon Kui) and amended the documents. MIFOS installation, setup, and interface had many problems. Engaged in technical forums online for MIFOS. However, response was slow. Documented installation and setup procedures, specifically for MFMS. Mobile Channel target.NET platform version that is specific for the IPT300 had problems in compilation. Consulted with hardware and platform expert from Integratech (Sankar). Integration challenges between and BOSS. It took time to synchronize the XML data format and contents to be used by both components. Conducted more sessions for Integration. Defined Integration test cases to follow consistently. Development and testing were mainly done using emulation. There were issues encountered during system and integration testing. Conducted more sessions for testing on real hardware. Despite the fact that there is no fixed schedule on when the device is available, the team is in constant communication with Integratech regarding the lending of the device. INT/MFMS/MR.3 Team SE18 2E

32. Lessons Learnt INT/MFMS/MR.3 Team SE18 2E

33. Lessons Learnt Team communication Resource Planning Technology Adaptation Open source development Prototyping Integration Testing Documentation and File Organization Reviews INT/MFMS/MR.3 Team SE18 2E

34. Recommendations for Future Work INT/MFMS/MR.3 Team SE18 2E

35. Recommendations for Future Work Mobile Channel's additional data capturing services available in IPT300. Data transport over remote and wireless network. Automated Attendance sheet for Group meetings. Possible pilot in Philippines and Bangladesh INT/MFMS/MR.3 Team SE18 2E

36. Video of working System INT/MFMS/MR.3 Team SE18 2E

37. Video (place holder) INT/MFMS/MR.3 Team SE18 2E

39. MFMS Components MFMS has three main component BackOffice Caters to the daily operations of a MFI branch and is used by multiple branches with a common share enterprise data repository Mobile Channel Hosts an application to enable mobility to the field operations of MFI branches to make the MFI operation efficient and faster. Branch Office Support System (BOSS) Acts as a gateway between BackOffice and Mobile channel and it will perform data transfer operation between these two sub systems. INT/MFMS/MR.3 Team SE18 2E

40. Payment Collection: Get Centers and Groups (place holder) INT/MFMS/MR.3 Team SE18 2E

41. Payment Collection: Prepare Data for Download to Mobile (place holder) INT/MFMS/MR.3 Team SE18 2E

42. Payment Collection: Prepare Data for Download to Mobile (place holder) INT/MFMS/MR.3 Team SE18 2E

43. Payment Collection: View Collections (place holder) INT/MFMS/MR.3 Team SE18 2E

44. Payment Collection: Confirm Payment (place holder) INT/MFMS/MR.3 Team SE18 2E

45. Payment Collection: Upload Data to BOSS (place holder) INT/MFMS/MR.3 Team SE18 2E

46. Payment Collection: Sync Data with MIFOS INT/MFMS/MR.3 Team SE18 2E