Mifos (Fineract) of course has a documented REST API already. It currently has two limitations:

1. It's source is simply a HTML file that is maintained manually in parallel to the source code which actually defines the REST API, and therefore can be out of sync
2. It's not "live", that is one currently has set up a REST tool such as e.g. Postman & Co. to "explore" it; contrary to the approach you can see e.g. on the Swagger Petstore example and (increasingly) other sites offering REST APIs.

The goal of this project is address this by using Swagger (now Open API Initiative OAI), most probably combined with SpringFox in for Mifos (Fineract), and replace the current apiLive.htm.

Phase II: once the Swagger live documentation is working it would be interesting to use the Swagger descriptor to generate client libraries (e. g. Java, Angular2). Nice to have optional add-on ideas for the end of the project: Add a paragraph to this new REST API Doc explaining how to easily import the (latest) Mifos Swagger into Postman, and perhaps add a Run in Postman button?

Someone suggested a potential alternative to using Swagger & SpringFox may be to instead use Spring REST Docs; if you feel that is better suite to fulfill the requirements above, please do feel free to explain this to your mentor and pursue in that direction.

• familiarize yourself with Swagger + SpringFox
• create working v1 code demonstrating feasibility of approach
• propose it to the community (mailing list), and react to feedback
• don't loose any documentation that's already on the current (manual) REST API doc, maintain it's human readable comments (by moving that into JavaDoc/annotations in code which SpringFox/Swagger exploit), the "sections", etc.

Our AngularJS Community App is the standard application on the Mifos X platform that provides all the core functionality for the most common methods of financial inclusion and products and services. It's also the starting point for any partners looking to customize or extend the UI. It's constantly being improved based on user feedback, better performance, and to integrate new design standards.

The project will involve the following:

• Update the AngularJS version to 1.5.x
• Performance improvements by introducing on demand loading
• Implement a new skin for the app
• Migrate the stylesheets to Sass
• Upgrade to latest version of http://angular-ui.github.io/bootstrap/
• Upgrade all plugins to versions compatible with Angular 1.5.x

We have released several versions of our Android app for field officers to go out in the field to process transactions, create clients, etc. Most recently, several outreaching interns added in significant new enhancements including refactoring, implementation of material design, offline, surveys, and new functionalities taking it from Version 1 to Version 2.

This project would continue that work and transform it into Version 3 - by following the refactoring design standards, providing a design refresh, and adding in new functionality.

Allows staff to go directly into the field to connect to the client. Reduces cost of operations by enabling organizations to go paperless and be more efficient.

https://github.com/openMF/android-client

We have recently released a full set of client-facing APIs to enable self-service channels for clients to interact with their own data and transact in a self-service manner. Previously all Mifos operations were performed by back office staff. Now clients can authenticate themselves, view and edit their account details. and make repayments or transactions between their own accounts.

It is now possible for them to have direct banking apps that they can utilize including smartphone-based mobile banking, USSD-based mobile banking, and online banking via a web app.

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood.

Customer Self Service

Customer Self Service - Phase 2

We have recently released a full set of client-facing APIs to enable self-service channels for clients to interact with their own data and transact in a self-service manner. Previously all Mifos operations were performed by back office staff. Now clients can authenticate themselves, view and edit their account details. and make repayments or transactions between their own accounts.

It is now possible for them to have direct banking apps that they can utilize including smartphone-based mobile banking, USSD-based mobile banking, and online banking via a web app.

The focus of this project would be designing and implementing a clean and simple Meteor.JS application that can be used as a reference web & hybrid mobile app for financial institutions to directly deploy and offer to their customers or for our our support partners to customize and enhance to the local needs of their market.

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood.

Customer Self Service

Customer Self Service - Phase 2

Agent Banking has become a key new delivery channel to increase reach, lower cost, and broaden the depth of services available. We will be taking over the Egalite codebase that's being donated to the Mifos Initiative by BFSI Consulting - it's a fully functional Android-based app for agents that works with any core banking system. This project would involved extending the application so it fully integrates with and works on top of the Mifos X platform

The current codebase is stand-alone and can integrate with any core banking system. This project will involve converting it to work on top of Mifos X by leveraging the Mifos X APIs for all functionalities that exist in Mifos X and adding in APIs for the functionalities that aren't present in Mifos X but in Egalite.

By enabling branchless banking, the costs of serving the poor are dramatically lowered, outreach can be extended to rural offerings, and brand new products and services that are more relevant can be delivered.

This has a dependency on the Self-Service backend API's being available 

Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood. Enable members of the society on-demand access to their.financial records even with basic mobile handset

Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Mobile money platforms like M-Pesa offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits.  For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system.

Based on the extent of the APIs available through the various mobile money platforms, the level and seamlessness of integration can vary from real-time to end-of-day file-based integration.  This project would work to provide several file, message, and or API-based reference integrations with leading mobile money platforms, including

• M-Pesa
  • File-based integration
  • API based integration
• TigoCash
• OrangeMoney
• AirtelMoney

Great efficiency, reduced risk for clients, more impactful and relevant products & services.

•   Research & Data on Various Mobile Money Platforms  - http://goo.gl/XkSbdl

Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Mobile money platforms like M-Pesa offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits.  For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system.

Based on the extent of the APIs available through the various mobile money platforms, the level and seamlessness of integration can vary from real-time to end-of-day file-based integration.  This project would work to provide several file, message, and or API-based reference integrations with leading mobile money platforms, including those from Zimbabwe and/or Zambia

Great efficiency, reduced risk for clients, more impactful and relevant products & services.

•   Research & Data on Various Mobile Money Platforms  - http://goo.gl/XkSbdl

Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Mobile money platforms like Orange Money and MTN Mobile Money offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits.  For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system.

Hence integrating Mobile money and Orange money to Mifos X in Central and West Africa will give the MFI an edge over their competitors and assist the client to carry out secured distance transactions. The end product of this project should allow a client to save from his mobile money account to his MifosX account, request or withdraw money from his Mifos X account to his mobile money account using probably a small mobile application to carry out these transactions. The Client self service API will be used in its fullness to accomplish this Tasks. Other APIs could be developed and used if the present Client self service API are not able to this these.

Based on the extent of the APIs available through the various mobile money platforms, the level and seamlessness of integration can vary from real-time to end-of-day file-based integration.  This project would work to provide several file, message, and or API-based reference integrations with leading mobile money platforms, including

• MTN Mobile Money
• OrangeMoney
  
  

Great efficiency, reduced risk for clients, more impactful and relevant products & services.

•   Research & Data on Various Mobile Money Platforms  - http://goo.gl/XkSbdl

In outbound SMS notification MFI decides when and what information need to be sent to client, but as part of client protection, client has complete rights to request for information about her/his account details(any time any where). Using inbound SMS client can query for her account details such loan amount, status of new loan application, outstanding loan amount.

This topic has traditionally been of interest to end-users, and one thing you could do is start an email thread on our Mifos end-user and developers mailing list, and perhaps on the chat room, to ask for input from others for Inbound SMS requirements, and add that to the Wiki, and then create a project proposal based on what you've learnt.

Transparency and client protection.

See SMS Integration and Outbound SMS

• Hooks
• Showcase of sending event-based SMS
• Functional requirements and use cases
• Outbound SMS
• JIRAs flagged as SMS and SMS-v2

Microfinance institutions usually work with various external parties, such as funders or investors. Using the data that is available in MifosX we would like to offer those stakeholders a seperate portal showing accurate and high-level information about the institution that would otherwise be reported manually by the institution. This information helps them in their decision making processes, but also enables them to assess the broader impact they are having with their funding.

To develop a portal that aggregates information from different Mifos X deployments and report on predefined social and operational metrics

Objectives:

• Implement back-end logic in MifosX required to make information available to the client impact portal
• Implement UI and back-end logic of the Client impact portal

2014 GSOC Client Impact Portal Project

• Client Impact Portal User Guide
• GSoC 2014 - Client Impact Portal
• Source Code: https://github.com/openMF/mifosx/pull/1047

Vision for Generic SPM Framework for Mifos X (PPI)

Background on Client Impact Portal

• Client Impact Portal
• Data Analytics & Client Insight - Are we making an impact? (Client Impact Portal demo)
• Client Impact Portal POC - (mifos/password are login credentials)

Because of regulatory reasons or to do background check of a client (risk management), MFIs depend on credit bureaus. As part of it, MFI must submit client details to credit bureau and also need to pull client information from credit bureau before approving any new loans to a client.Mifos X can be integrated with a popular CBs in India and from other regions (based on the demand).

This will be an optional module inside Mifos X, and this module can be turned on/off based on the institutes requirements. And will be flexible to configure with different CBs (may not be practical to integrate with all CBs).

The major functionality will be sending the data to CBs on regular intervals in the format CB expects. And option to pull the client’s information from CB whenever loan officer/branch manager/ user wants to view the information for a particular client.

The credit report shows account information such as repayment record, defaults, type of loan, amount of loan, etc. of the customer. This information facilitates prudent decision-making when the credit underwriter processes the loan application. This help MFI to reduce the risk of bad loans and reduces the multiple lendings to same person from different MFIs.

1. Build a module that extends loan product definition to include specific physical product ordering - e.g. a clean energy loan associated with a specific solar product. Create a daily batch process to send data in JSON or XML to appropriate third party system (e.g. MEC Tracker). Extend this to include "down payments" on the product purchase - i.e. only partially financed.
2. Build a supplier ordering/invoice & financial reconciliation process and transfer funds directly to "Supplier Account" upon fulfillment of order.
3. Create reports on aging of orders, fulfillment timing, and geographic spread.

MFIs become more capable of integrating with third party systems for management of deliveries, after-sales service, and carbon tracking.

As financial inclusion evolves, more loan products are collateral-based and require more detailed tracking of the asset (gold, property, etc.) along with its value, and its depreciation.

We have a complete specification in place and need a team to build out a new module on top of the platform that tracks the additional collateral values. The work involved includes creation of new APIs and database tables to track additional parameters for the collateral, and to build out the UI screens for this module.

Clients and Small Businesses are able to take out higher value loans when they can offer up different forms of collateral.

As financial inclusion evolves, complexity too, we will build an enterprise social driven platform which increases communication with focus on business and control on small but complex automation of tasks.

We have a complete specification in place and need a team to build out a new module on top of the platform that will driven by the concepts of social parameters like instant chat and message based data movement and total UI overhaul

Clients and Small Businesses are able to interact in a manner without making it complex.

A crucial part of financial inclusion is micro-insurance and the ability for clients to safely manage risk in their lives. Mifos X will not fully handle the entire lifecycle of an insurance product but it should integrate with microinsurance system and track the key parts of the process that relate to the core banking system - collection and pass through of the premium and tracking claims and processing of these.

This project would involve building out a separate module that tracks claims being made by a client, likely leveraging the CRM functionality being build to track activities. It will integrate with APIs to enable processing of the claim and tracking what proceeds must be paid out to the client.

It will involve creating a new module with data model, UI screens and business logic that leverages Mifos X APIs

Clients are able to lower their risk and have a much larger safety net when they have affordable access to insurance policies.

See http://www.openunderwriter.com/

See Insurance Product

This project is a continuation of the initial PayGoSol foundation that was led by 2014 GSOC intern, Antonio Carella.

1. Create a pre-paid account mechanism as an account type or account option in Mifos (perhaps extending existing classes), zero fees.
2. Create a new API for consuming pre-paid account balances.  
3. Create a simple external model that mimics consumption by a household on a daily basis - imagined as a set of data received from solar panel (watts used, time of day, volts present).  
4. Load up pre-paid account by account transfer in P2P interface (my phone to your account) or via trusted agent - i.e. trusted agent receives cash and loads account on Mifos.

Work in 2015 will include adding the following features to make it an out-of-the-box solution that any PAYG hardware provider could use:

Providers of pay-as-you-go solar can use MIFOS for their operations. MFIs can become such providers.

Mifos Android Client on MifosX

• CGAP Research on PAYG Business Models: http://www.cgap.org/publications/access-energy-digital-finance-models-innovation

Data migration can be one of the most challenging and time-consuming phases of an implementation of a core banking system. In 2013, GSOC intern, Avik Ganguly, built our data import tool for generating pre-configured Excel templates to migrate data into Mifos X. In 2014, Diunuge, extended this to other types of information in Mifos X along with integrating it from a stand-alone web app to a core part of the platform. The data import tool is now the foundation for all of our data migration tools.

This project would continue to extend the data import tool to new types of data and APIs that need to be imported, enabling office-level import, and continued integration into the platform. This project will also involve building on top of the data import tool to provide out of the box migrations from other legacy systems such as MicroBanker or Loan Performer.

• Import for other types of data not currently supported
• Populate date using bulk APIs
• Enable office-level imports for larger organizations who find it too cumbersome to migrate an entire organizations worth of data at once
• Build out scripts on top of the data import tool to get data and transform it out of legacy systems like MicroBanker or Loan Performer.

It has many impacts

1. This drastically reduces the time to set up of initial configuration/data of Mifos X for organization adopting this system as MIS.
2. For data entry operator, this feature can be used as bulk creation option (such as import bulk loans, import clients)
3. These templates can be used as offline store. And once user has internet connectivity can upload these templates with captured data.

GSOC 2013 - Data Import Tool

GSoC 2014 - Data Import/Export feature

Data migration can be one of the most challenging and time-consuming phases of an implementation of a core banking system. It's often a barrier to financial institutions moving on to new and better more modern systems. It's critical to cleanly migrate over the historical data of a client and their transactions. Often the legacy system data needs to be cleaned up and transformed before it can be migrated into Mifos X and is one of the most costly and time-consuming phases of a deployment. We have an existing data migration tool for migrating from Mifos 2 to Mifos X that utilizes the Pentaho Kettle ETL tool.

This project would extend the existing Mifos 2 to Mifos X Kettle-based migration tool to provide a standard migration tool from Mambu - another modern system that is widely used by customers potentially looking to migrate to Mifos. It would provide one standard tool that any partner or financial institution could use for migrating from that specific system - it wouldn't require new tools to be made each time a migration is done.

Extend the existing Kettle-based Mifos to Mifos X migration tool

• Write ETL scripts to get data and transform data it from Mambu format to Mifos format

It has many impacts

1. This drastically reduces the time to set up of initial configuration/data of Mifos X for organization adopting this system as MIS.
2. It widely opens the market that Mifos X is applicable for as it lessens the burden of converting from other systems.
3. It dramatically lowers the cost of implementing a system like Mifos X by reducing the complexity of the deployment
4. It increases transparency by ensuring financial institutions using Mifos can retain the full history for their clients.

http://nayan.github.io/move-to-mifosx/

https://github.com/openMF/move-to-mifosx

Data migration can be one of the most challenging and time-consuming phases of an implementation of a core banking system. It's often a barrier to financial institutions moving on to new and better more modern systems. It's critical to cleanly migrate over the historical data of a client and their transactions. Often the legacy system data needs to be cleaned up and transformed before it can be migrated into Mifos X and is one of the most costly and time-consuming phases of a deployment. We have an existing data migration tool for migrating from Mifos 2 to Mifos X that utilizes the Pentaho Kettle ETL tool.

This project would extend the existing Mifos 2 to Mifos X Kettle-based migration tool to provide a standard migration tool from Loan Performer - a low-cost, widely adopted system in use by hundreds of microfinance institutions throughout Africa and Latin America. It would provide one standard tool that any partner or financial institution could use for migrating from that specific system - it wouldn't require new tools to be made each time a migration is done.

Extend the existing Kettle-based Mifos to Mifos X migration tool

• Write ETL scripts to get data and transform data it from Mambu format to Mifos format

It has many impacts

1. This drastically reduces the time to set up of initial configuration/data of Mifos X for organization adopting this system as MIS.
2. It widely opens the market that Mifos X is applicable for as it lessens the burden of converting from Loan Performer - a system that is widely used but not as modern and sophisticated as Mifos X.
3. It dramatically lowers the cost of implementing a system like Mifos X by reducing the complexity of the deployment
4. It increases transparency by ensuring financial institutions using Mifos can retain the full history for their clients.

http://nayan.github.io/move-to-mifosx/

https://github.com/openMF/move-to-mifosx

For better usability system needs to have notifications to the logged in user about actions he/she needs to perform in the application.

Build real time notification system in application to notify to users about pending/new actions she/he needs to take. Example if branch manager login to the application and 3 new loans are created and pending for approval then system should notify him/her about the pending actions.

This involves both invoking and triggering these notifications based on these actions or activities as well as the extension of the user interface to support the display of the notifications as well as the ability of the user to take action upon the notifications.

Right now Mifos X contains core client management functionalities including tracking basic demographic information, know your customer information, document management, and survey collection through data tables. As financial institutions serving the poor begin to offer a more in-depth and diverse range of financial inclusion products, the need for more robust client management and in-depth client understanding has grows. Their core system needs to provide more and more CRM-type functionality that complement the portfolio management and financial/social reporting the Mifos X provides.

This project will work to deliver the initial set of customer relationship management functionalities including a module for tracking inquiries, complaints

This module will have a request management functionality. A request can be of 2 types: Complaints and Service Requests. Each request must be against a customer and optionally against an account of the customer. Each request will go through a simple workflow.

Actions that can be performed on a request:

Assign -> will change status to "assigned"

Start Work --> will change status to "in progress"

Close --> will change status to "closed" (with a sub-reason code)

At each step user can enter comments.

The customer summary screen will have a link to view the requests of the customer - along with a summary and current status - with option to click-through to get the complete history of each request.

Deepening the client relationship and ensuring fair, responsible, and transparent financial services to the poor is a core piece of the industry's roadmap for financial inclusion. Providing customers the ability to voice their concerns and feedback about the services they're receiving provides a simple yet powerful tool to protect the client. Empowering the financial institution with the ability to track these inquiries and overall maintain a more holistic relationship tracking entire lifecycle of their clients gives them a much better ability to understand their clients and respond to their needs with appropriately designed services and products.

Integrate MifosX with an opensource Point of Sale (POS) called JPOS.

Use case would be to get a debit transaction (cash withdraw from checking account) thru the POS device /local runtime with 2FA.  In India, the ability to get cash out through a point of sale network is provided for under RBI regulations. In production there will likely need to be an intermediate "Merchant Acquisition" or "Payment Processor" in between a single POS and MifosX Instance, but this could be abstracted out as a payment gateway only (primarily data mapping). The implementation target is the ability to do a 2 factor authentication on a POS device running JPOS (emulator ok), input account number (via some simple method), then be able to do a (cash-out) account withdrawal in real time to the MifosX account. Additional use cases would be to implement a transaction for payment for goods. i.e. enter specific goods, then do payment from MifosX account to Merchant Account (probably also in Mifos).

Familiarity with API work. Understanding of transactional flows.

Java.

Two-factor authentication - see other project idea .

https://github.com/jpos/jPOS/

We believe the Mifos X platform is super secure and impenetrable. Your mission, should you choose to accept it, is to prove us wrong, and help close gaps you may find.

Beyond a one time exercise, you should integrate (some of) the tools you've used into our build chain so that, even after you've gone, tools flag up future newly introduced potential vulnerabilities.

https://www.owasp.org/index.php/Main_Page

https://code.google.com/p/zaproxy/

http://wapiti.sourceforge.net

Run FindBugs & related tools for some serious static code analysis

http://en.wikipedia.org/wiki/Penetration_test

This project would seek to create one unified ID/login and profile for community members similar to the OpenMRS ID. It would achieve the following two primary objectives:

1. One unified profile and identity for community members in which they can share with the community who they are and also build reputation and recognition. This ability to discover and self-identify with other community members is difficult when we have so many different tools and profiles to maintain.
2. Single Sign On for our various collaboration and community infrastructure tools listed below.

1. Identifying a single sign-on authentication protocol that ties together authentication of our various community collaboration tools: 1) Atlassian Studio - JIRA, Confluence, JIRA Agile, 2) Social Q&A - AnswerHub 3) Mailing Lists - Mailman (administered through SourceForge 4) Source Code Version Control - GitHub 5) Continuous Integration - Jenkins 6) General Community Website (mifos.org) - Wordpress 7) Partner Directory
   1. This could be built out independently, tie into some OpenID protocol, or leverage one of our existing tools for this authentication - Atlassian Studio/Crowd or AnswerHub or another common OpenID protocol. 
2. Design and implement a dashboard to handle the creation of this unified ID
3. Design and create a common profile tied to this ID with basic information and photos that is searchable by the community.

Design a profile

Extra Credit:

• Gamification/Reputation Building - Tie into Open Badge system like Mozilla Open Badges http://openbadges.org/ or Ushahidi Badges: http://ushahidi.github.io/Badges/

Impact is two-fold:

• Common unified profile and identity can help to grow collaboration and participation in the community. By being able to simply share who you are or discover who's in your community, we can deepen the bonds of community which motivates each member to participate more often and invest personally in the health of the community. Building reputation and recognizing efforts of each type of community member (users, partners, volunteers, etc) in a tangible way also helps to increase participation.
• Single sign-on will it make much easier for community members to collaborate and communicate. Right now there is often a high barrier to signing up for the various tools - SSO will make that process easier but also encourage others to more regularly be involved.

Create a POC of a scalable MifosX implementation (with load balanced tomcats and percona servers) on an openstack setup on a public cloud. Also publish a whitepaper with details of Openstack setup

Mifos X was built to be cloud ready from the ground up. One of the most popular deployment environments for MifosX has been on Amazon EC2, however due to country specific regulation, many implementors are forced to seek alternative models that can scale as effectively. The aim of this project is two-fold:

• Propose a scalable deployment model for Mifos (includes load balanced tomcats, percona mysql server etc.) on OpenStack. The POC would be on a public cloud provider (e.g. Rackspace?). Your GSOC application should highlight a starting point with some details of your planned deployment architecture, as Mentors would be not giving you step-by-step instructions in this project, just "nudge" you along; you would be expected to learn about how to deploy Mifos yourself and by autonomously using the documentation available and help from the public mailing list and IRC channel, and figure out the details of the Cloud deployment.
• Propose how the above proposed model could be contributed to Mifos in the form of e.g. ready-to-run "scripts" / OpenStack (or how about OpenShift) "configurations" etc. allowing ANYONE to deploy THE LATEST VERSION of Mifos in the Cloud themselves, and then implement this approach in practice. (Contrast this with a "one-off exercise", e.g. taking the current Mifos X WAR file, and UI, and manually making some changes to it, and then manually deploying that to some Cloud PaaS - this would not be sufficient for this project's expectations.)
• Implement a Continous Deployment "Devops" EXAMPLE instance of this scalable blueprint using the latest nightly Mifos build artifacts.
• Publish a high level whitepaper of the same, which can be used as a reference for local implementors, who would additionally take care of provisioning their own hardware. This documentation should be ideally high-level, and what it described much be automated; only providing lengthy step-by-step manual instructions would not be sufficient for this project's expectations.

To prepare for this project, applying students must demonstrate at least that they have already successfully locally built and ran a Mifos X REST back-end server and UI, populated the database etc. as well as provided a simple pull request proposing some minimal deployment related improvement.

Mifos X today is typically used on Tomcat (with Jetty known to work). For a certain class of users, testing it on "Enterprise Stack" application servers (meaning IBM WebSphere and Oracle WebLogic) is desirable - this project would properly test Mifos X on these configurations, make any adaptations to the code which may be required, and produce easy to follow documentation or even small tools helping future users how to go about this.

This project could be combined with and taken up by the same candidate as the Enterprise database project.

Java, Application Server configuration, WAS classloading crap tricks, documentation writing.

Use Cargo, Arquillian etc. for automated testing against WAS & WLS containers?

Vendor pages

At present MIfos X platform is shipped with Community-App (SPA) as default UI, but initial load time of the application high. And for users on narrow bandwidth internet it takes a considerable amount of time to load the app.

Instead of loading the app every time, we can convert the Community-App into a Chrome App and user can download them once and install it on the machine, and it can used as thick client.

Community-App is completely developed on top of JavaScript, CSS and HTML. And Chrome apps are also written in same stack. Using grunt we should be able to repackage Community-App(SPA) into Community-App(Chrome App)

Users with slow internet connectivity can use this app (Installed on the machine) instead of loading Community-App (SPA) on the browser. Users will also have a continually updated app. This will also allow MFIs to potentially use Chromebooks as field-based devices for their branches.

The AngularJS-based Mifos X UI, like most of today's AngularJS-based or really most web apps, is "coded out" with JavaScript & HTML partial views. This project aims to explore and deliver at least partially working solution, based on and applied to Mifos X UI as a "case study", how web UI of modern SPA web applications can be "modeled" (described), and "generated" (at build, or better, runtime right within the browser). Advantages of such a model driven (MDA / MDD) approach incl. that less technical users can change screen definitions themselves, and that changes to the underlying technical architecture (e.g. AngularJS version and other JS frameworks used) ideally only affect the generators, not the functional screen models.

You could base this on ongoing explorations in https://github.com/vorburger/MUI.js, and using EFactory / ESON as model syntax (see https://github.com/vorburger/efactory; ESON a JSON-like EMF Xtext technology which is currently being incubated as a formal eclipse.org project). The goal and expected outcome of this project isn't some write up, but actually running code.

MIfos X platform is shipped with a Community-App (SPA) as the default UI which is optimized for Web Browser display on large screens (Mobile, Laptops and Tablets). We need to extend the same to support mobile views (with minor changes to workflow) and provide offline functionality

Community-App is completely developed on top of JavaScript, CSS and HTML. Also since there is a clear separation between the view and the Controllers in Angular JS, we should be able to spin up mobile views fairly easily reusing the same Controllers and Services. As it is quite common for Mobile users to have intermittent data connection, we should also support offline functionality,

Offline functionality is critical such because users

Field officers can access MifosX from a Mobile optimized view, capture data offline that can be synced back to the server when an internet connection is available.

It also becomes easier for the community volunteers to maintain the mobile view ( as we reuse most of the code from the Community app) as opposed to maintaining a separate Android app.

Other Resources

Develop ETL scripts to create OLAP cubes (fact and dimension tables in MySQL). This will allow managers to perform ad hoc slicing and dicing of their data 
to answer important questions about their operations.

• Create ETL scripts and tests
• Create a Mondrian schema to work with Saiku Analytics

This project would extend off of the work of a previous GSOC intern in building out integration with Saiku

Saiku Analytics Demo - demo.analytical-labs.com
Wikipedia OLAP Article - http://en.wikipedia.org/wiki/Olap
Introduction to OLAP - http://www.db-class.org/course/video/preview_list
Gentle Introduction to MDX - http://www.iccube.com/support/documentation/mdx_tutorial/gentle_introduction.html

MIFOSX-1448 - Getting issue details... STATUS

While the Mifos X Community App front-end UI based on AngularJS-based currently does already have some JS unit tests, we lack a full UI level web tests which continually non-regression test common scenarios. We believe having this could add value in terms of quality, including ensuring automated cross browser testing.

Possibly building upon a extremely limited small scale existing POC (if you find it to be a useful starting point), your mission, should you chose to accept it, would be to build out comprehensive UI walk through scenario test coverage for the Mifos X UI. If you can build more such tests faster and more maintainable (= less code) by using any of the existing frameworks listed below or others you know of / will find, or build useful such infrastructure yourself as part of this code, we're eager to hear from you! Keep in mind that the main deliverable of this project is not (only) a foundation framework, but must actually include an extensive suite of running tests integrated into the Mifos build.

http://docs.seleniumhq.org/projects/webdriver/

https://github.com/vorburger/mifosx-ui-selenium-webdriver-tests

https://github.com/vorburger/webdriver-runner

https://saucelabs.com or https://browserling.com

https://github.com/FluentLenium/FluentLenium

http://www.gebish.org

http://www.thucydides.info

Before booking a loan the customer needs to require and assess the details of the loan he is enquiring for and there is no way to personally judge it, based on the parameters, Sales staff right now is using different external loan calculator and loan product schemes are not documentated we need a frontend experience service with personal match

https://docs.google.com/document/d/18rS0gVWkjQvNdRnNj40uKNl32zuTh-uuzNv161n6YrY/edit?usp=sharing