Micro Finance Management System (MFMS)

Micro Finance Management System (MFMS)

For INTEGRATECH

The Team Project Background Scope Effort Estimate –contrast with FPC/Coster Risks Quality plan Technical Strategy (high level technical approach)

Agenda

M-Tech in Software Engineering Team2E

Anupama Bright D L Jawahar Chelliah Karthi K Maya Roosevelt Satish Kumar Tan Achilles

The Team

Team Organisation

Role NameProject Manager Maya RooseveltTechnical Lead Karthikeyan Krishnamurthy

Quality Manager Achilles TanSolutions Architect Satish Kumar

Database Administrator Jawahar Chelliah

Business Analyst Anupama Sarada

Software Engineer Bright Devakadaksham Lilly

Microfinance is the provision of financial services to low-income people or the self-employed, who lack access to banking and related services.

Microfinance Institutions (MFIs) brings the banking to the cooperative societies. In MFI context, each society is a small group of people, led by a team leader. Team leader acts as a point of contact between MFI branch and group. MFI branch allocates a loan officer for product like loan/Saving processing with each group and a loan collector for loan collection within vicinity.

Project Background

Currently, there are software systems available to meet MFI requirements but mobility of the business and level of cooperation between branch and its members requires better software solution with proper integration with mobile workflow.

On behalf of Integratech, Team 2E ISS, MTech will propose a software solution and develop this system – Microfinance Management System (MFMS) based on the collected requirement as per User Requirement Specification.

Project Background - continued

The high level scope of the project is to provide a total solution to the MFMS project by developing a system to integrate the back office (MIFOS) application with the mobile handheld device (IPT300) and thus enabling data exchange through a Middleware application

Scope

The total combined effort from Staff Effort Estimates table is calculated as 515 man-days.

1 man day represents 5 man hours Thus, estimated man-days for each team member

will be about 74 man-days (515 / 7).

(Details as per Project Plan)

Effort Estimate - FPC

(Details as per Project Plan)

Effort Estimate - Coster

The following are identified as potential risks and are addressed as part of this project (Project plan Appendix D)

Possibility of Change request Installation/Customisation of MIFOS Application Integration with Mobile Channel Team skill set Development on the Hardware IPT300 Sponsor support UI Design

Risks

Risks - Diagram

  Impact Likelihood

Possibility of Change request 2 3Installation/Customisation of MIFOS Application 2 3Integration with Mobile Channel 3 2Team skillset 3 3Development on the Hardware IPT300 4 3Sponsor support 2 2UI Design 2 3

1.5 2 2.5 3 3.5 4 4.50

0.5

1

1.5

2

2.5

3

3.5

Impact

Likelihood

Risks – Mitigation Plan

The Quality Plan talks about :

Project Organisation Liaison with Client, Point of Contacts Documentation Organisation Work plan and Deliverables Planning and Progress Control Quality Controls Standard, Method and Tools User and Change Management Defect Management

Quality Plan

Technical Strategy - 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

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

Technical Strategy

Q & A

Thank You !

STAFF EFFORT ESTIMATES

STAFF EFFORT ESTIMATES