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

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. 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 host an application in the Mobile Channel to enable mobility to the field operations of MFI branches in order to make the MFI operations more efficient and faster To provide Branch Office Support System (BOSS) act as a gateway to perform data transfer operation between the mobile device and the branch office. INT/MFMS/MR.3 Team SE18 2E

7. Project Overview INT/MFMS/MA.1 Team SE18 2E

8. Scope Provide software solution that will enable data exchange between mobile channel (IPT 300) and back office application (MIFOS) through a Branch Office Support System (BOSS). INT/MFMS/MR.3 Team SE18 2E

9. High Level Functional Requirements 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. 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

10. 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

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

12. Effort Estimate ( Details as per Project Plan ) Unit of Measurement EstimateActualVariance (%) Total Project Effort Man Days51557011% Project Duration Months12 0 INT/MFMS/MR.3 Team SE18 2E

13. Use cases Implemented Login Create Member Profile View Loan Details Loan Distribution Loan Payment Collection Manage Users Manage Loan Manage Payment INT/MFMS/MR.3 Team SE18 2E

14. 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

15. 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

16. Architecture INT/MFMS/MR.3 Team SE18 2E

17. 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

18. MFMS System Components MFMS Mobile Client Communication Manager Device Synchronization Manager Remote Data Access Device Application MFMS Middleware Data Access Manager Data Exchange Service User Management Middleware Console Sync Service Authentication Service INT/MFMS/MR.3 Team SE18 2E

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

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

21. Implementation details (place holder) INT/MFMS/MR.3 Team SE18 2E

22. Challenges

23. 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 was developed and unit test was done in Emulation and the system test was done when the device was available Project tasks were paused for 2 weeks before the 3 rd and 4th semester exams. The project schedule was adjusted accordingly. 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. Some team member’s official and personal overseas trip challenged the team to complete the scheduled tasks. Organized online meeting sessions. However, the team found out that this is less effective. Nevertheless, it was the best that could be done. The client was busy with his real time projects and frequent overseas trips which delayed the sign off of the URS. -

24. 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.

25. Video of working System

26. Video (place holder)