Functional Gaps

Use this page to capture gaps in Mifos 1.1 that may require refactoring at a larger scale than the class or method level. We can consider these as we plan for 2.0.

Roshan Vikas- GAP Analysis

See apos;s post that lists several roadblocks to adoption of Mifos by Roshan Vikas.

Natural ID numbers

"R.V follows category wise unique IDs Ex: SHG Code , Constituency number , Loan Account Number , Saving Account Number. This feature is not available in Mifos – Mifos gives System ID to every instance irrespective of the nature and category of entry. We need Global Ids with Prefix like SA-0023 for Saving Accounts."

This request would likely be repeated by potential customers that already have systems in place that expect entities' global identifier to follow some business pattern, rather than being system-generated without business content.

If this truly is a roadblock for customer implementation, then we should consider how to make Mifos's global-id-generation easily customizable. Potential alternative solutions:

  • Create a pluggable interface to a global-id-generator, into which a customer could plug their own coded implementation. Strategy pattern might apply here.

Flexible Fiscal Year

Roshan Vikas follows Indian fiscal year as 1 APR to 31 MAR

Intelligent criteria for granting loans

R.V Loans are sanctioned based on Balance of Savings available and loan repayment history of respective groups. But Mifos Loans are sanctioned irrespective of their Savings and previous Loans Repayment.

Meeting-date coupling and uncoupling

More meeting-date woes:

R.V follows meeting dates for all groups and members but all financial transitions must be independent of meeting date. But In Mifos Meeting Dates are very important, Saving Deposit Schedule , Loan Disbursements and Loan Repayments are depends on Meeting Dates. Meeting date should not restrict any financial transactions.

R.V Meetings takes place as per the convenience of respective Groups irrespective of their scheduled meeting dates. But Mifos meeting dates are given to centers and no flexibility to the groups in that center to change meeting dates as per their convenience. Meeting dates need to be definable at the group level.

Monitoring Hooks

See apos;s use of monitoring tools like Munin. Graeme states "If there are performance hooks in Mifos it should be reasonably simple to write a plugin to gather and graph data." Are hooks in place to enable use of this and other tools?

Also see Network Monitoring, currently a rough collection of links on the subject of network monitoring with Mifos.