MFMSMicro Finance Management System

INT/MFMS/MR.3 Team SE18 2E

Presented by: SE 18 Team 2EDate : 17th January 2012

Outline• Project Background

• Project Overview

• Project Metrics

• High Level Architecture

• Implementation Details

• Post Implementation Review

• Q&A

INT/MFMS/MR.3 Team SE18 2E

Project Background

INT/MFMS/MR.3 Team SE18 2E

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

Project InformationProject:

Micro Finance Management System (MFMS)Client

Integratech Pte Ltd, SingaporeActual Start Date

15 Jan 2011Actual End Date

16 Jan 2012

INT/MFMS/MR.3 Team SE18 2E

Team Organization

** Jawahar Chelliah dropped out from the project in the 3rd Phase of the project.

INT/MFMS/MR.3 Team SE18 2E

Project ObjectiveTo 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

Project Overview

INT/MFMS/MA.1 Team SE18 2E

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

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

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.

• BOSSActs as a gateway between BackOffice and Mobile channel and it will perform data transfer operation between these two sub systems.

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 

System Architecture

INT/MFMS/MR.3 Team SE18 2E

Overall System Architecture

INT/MFMS/MR.3 Team SE18 2E

http://mifos.org/product/features

MFMS 101

Mifos Handheld IPT300Data

Microfinance Management System

INT/MFMS/MA.1 Team SE18 2E

MFMS - Mifos

Web

Se

rvic

es

git://mifos.git.sourceforge.net / mifos/head http://ci.mifos.org:9000/project/index/1

INT/MFMS/MA.1 Team SE18 2E

Mifos Handheld IPT300

Data

Microfinance Management System

BOSSData

Branch Office Support System (BOSS)

INT/MFMS/MA.1 Team SE18 2E

HTML 5

Java Server PagesSpring MVC Framework

Data CollectionData Delivery

DashboardDevice mgmt Auth

entic

atio

n Se

rvic

e

Service Layer

Spring WS REST

Apache Tomcat web server 6.0

MySql DB

MFMS User Interface

IPT 300 .NET Library

Data Access layer

.net compact framework

MS SQL CE

Mifo

s

BOSS

MFMS Mobile

MFMS Architecture

INT/MFMS/MA.1 Team SE18 2E

Persistence – Hibernate ORM

Business Layer

Business Layer

Development

INT/MFMS/MA.1 Team SE18 2E

Implementation Strategy

INT/MFMS/MA.1 Team SE18 2E

Development

INT/MFMS/MA.1 Team SE18 2E

Unit TestingSystem testing Integration Testing

Bottom Up testingUser Accesptance Test

MFMS System Components

INT/MFMS/MA.1 Team SE18 2E

Development View

Web Service

s

MIFOS

INT/MFMS/MR.3 Team SE18 2E

Technical Strategy

INT/MFMS/MR.3 Team SE18 2E

Implementation Details

INT/MFMS/MR.3 Team SE18 2E

Project Metrics

INT/MFMS/MR.3 Team SE18 2E

Planned Vs ActualPhases No Milestone Target Date Actual Date

Inception Phase

(Project Planning)

1 Initial Planning    

1.1 Produce Project Plan 23-Mar-11 23-Mar-11

1.2 Produce Quality Plan 16-Mar-11 16-Mar-11

2 Requirements Specification    

2.1 User Requirements Specification 1-Apr-11 1-Apr-11

3 Phase 1 Management Admin / QA    

3.1 First Quality Audit 5-Apr-11 5-Apr-11

3.2 First Project Presentation 12-Apr-11 12-Apr-11

Elaboration Phase(Analysis & Design)

4 Functional Specification    

4.1 Produce Use Case Model survey 19-Apr-11 26-Apr-11

4.2 Produce Use Case Realization Report (Analysis) 19-May-11 13-Jun-11

5 Prototyping  

5.1 Develop Prototype for feasibility with MIFOS 27-Apr-11 2-Jun-11

5.2 Produce Prototype Study Report 29-Apr-11 14-Jun-11

6 High level Design Specification    

6.1 Produce Software Architecture Specification 25-Apr-11 30-Jul-11

6.2 Produce Transition Strategy from Analysis to Design 25-Apr-11 30-Jul-11

7 Phase 2 Management Admin / QA    

7.1 Second Quality Audit 2-Aug-11 2-Aug-11

7.2 Second Project Presentation 10-Aug-11 10-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

Planned Vs ActualPhases No Milestone Target Date Actual Date

Construction Phase

(Implementation)

8 Detailed Design Specification    8.1 Produce Design Model Report 27-Aug-11 20-Oct-119 Source and Executable Code    9.1 Code and Unit Testing 1-Nov-11 23-Dec-1110 Systems Testing    10.1 Produce Systems Test Plan & Test Cases 2-Sep-11 26-Nov-1110.2 Produce System Test Report 18-Nov-11 31-Dec-1111 Integration & Installation Testing    11.1 Produce Integration Test Plan 2-Sep-11 26-Nov-1111.2 Produce Integration Test Report 2-Dec-11 2-Jan-1212 Documentation    12.1 Produce User Guide 7-Dec-11 5-Jan-1213 Deployment and User Acceptance    13.1 Produce User Acceptance Test Plan 31-Oct-11 26-Nov-1113.2 User Acceptance 15-Dec-11  14 Project Closure    14.1 Produce End-Of-Project Report 28-Dec-12 8-Jan-1215 Phase 3 Management Admin / QA    15.1 Third Quality Audit 10-Jan-12 10-Jan-1215.2 Third Project Presentation 17-Jan-12  

Notes : UCRR had to be updated based on 2nd 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

Effort EstimateUnit of Measurement

Estimate

Actual Variance (%)

Total Project Effort

Man Days 515 570 11%

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.

Challenges

INT/MFMS/MR.3 Team SE18 2E

Management ChallengesChallenges Resolution

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

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

-

Technical ChallengesChallenges Resolution

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.

Lessons Learnt

Lessons LearntTeam communicationResource PlanningTechnology AdaptationOpen source developmentPrototypingIntegration TestingDocumentation and File OrganizationReviews

INT/MFMS/MR.3 Team SE18 2E

Recommendations for Future Work

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.

INT/MFMS/MR.3 Team SE18 2E

Video of working System

INT/MFMS/MR.3 Team SE18 2E

Video (place holder)

INT/MFMS/MR.3 Team SE18 2E

INT/MFMS/MR.3 Team SE18 2E

MFMS ComponentsMFMS 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

Payment Collection: Get Centers and Groups

(place holder)

INT/MFMS/MR.3 Team SE18 2E

Payment Collection: Prepare Data for Download to Mobile

(place holder)

INT/MFMS/MR.3 Team SE18 2E

Payment Collection: Prepare Data for Download to Mobile

(place holder)

INT/MFMS/MR.3 Team SE18 2E

Payment Collection: View Collections

(place holder)

INT/MFMS/MR.3 Team SE18 2E

Payment Collection: Confirm Payment

(place holder)

INT/MFMS/MR.3 Team SE18 2E

Payment Collection: Upload Data to BOSS

(place holder)

INT/MFMS/MR.3 Team SE18 2E

Payment Collection: Sync Data with MIFOS

INT/MFMS/MR.3 Team SE18 2E