This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata
Target release1.0
Epic 
Document statusDRAFT
Document owner

Ed Cable

Designer
DevelopersRuphine Kengne
QAAwasum Yannick

Goals

  • Provide support in Apache Fineract CN for group-based financial inclusion methodologies including but not limited to Grameen-Style joint liability groups or solidarity groups, self-help groups, village banking, savings groups, etc. 

Background and strategic fit

A cornerstone of most financial inclusion providers and the legacy and heritage of the original Mifos software which evolved into Apache Fineract is joint liability group lending. The original Mifos 2.x (Generation 1 software) was an MIS purpose-built for Grameen-style Joint Liability Group Lending. While Mifos X/Apache Fineract (Generation 2) was built with greater flexibility and support for individual lending but still deeply catered to group and center-based operations. 

Assumptions

  • This specification document will need to be broken out into different specifications for each methodology
  • This specification should encompass the organizational, product, calendar, and accounting settings common across different group-based lending and savings methodologies
  • Aim to utilize the existing knowledge and learnings from previous two generations of software in the design and architecture of this support
  • Aim to utilize design and user experience/workflows from previous Mifos X UI

Requirements

#TitleUser StoryImportanceNotes
1
2    

User interaction and design

See the current Mifos X UI on top of Apache Fineract at https://demo.openmf.org (mifos/password) which was loosely based on the web mockups at https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/34111558/Usability+and+Design. This UI was built in 2013 and then reskinned in 2016 and since has had ongoing improvements. Various other UIs have been developed by partners which can also serve as examples - such system include Musoni System, FINEM, Ez Bank, Finable, Finflux, etc. 

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Resources

These are previous specs, requirements, API docs, user manuals so as not to forgot the great body of knowledge we're working from:

Generation 1 - Mifos 2.x

Generation 2 - Mifos X

 

Not Doing

 

 

Proposed Mock-ups For Group Loan Management Service

            

                 

            

 

            

 

          

 

         

 

        

            

          

  

        

 

          



DATABASE DESIGN

Here is the database design for Group Saving Products.  I was able to model this database with  some ideas gotten from the deposit-account management micro-service and Fineract 1.x




Database Design for Group loans

 

1 Comment

  1. Ruphine Kengne The idea behind the current group service is, a client of the group is treated like a member of the FI. This would cover the whole KYC portion. After the client is created as a member, you then can assign them to a group. I would suggest to keep the client to member flow as is, creating a new member in the member section, and use a type-ahead drop down list to assign the member to the group.