A business rule system enables these financial institutes policies and other operational decisions to be defined, tested, executed. Rule engines typically support rules, facts, priority (score), mutual exclusion, preconditions, and other functions.

This module will enable MFI admin to add, remove or modify the business rule against pre-defined work flows in the application.

As financial institutes, the business process of the institute is governed by local regulatory, and internal rules and rules defined by other other stake holders. And MIS should have provision to define these rules in the application to achive the objectives of these rules defined by various stake holders.

Example: Insurance company does not provider insurance to any person above 65 age. In that case in the MIS if users tries to attach a insurance feed to a client's loan account whos age is more than 65 years then "business rule engine" should prevent that action with appropriate message.

The implementation would probably have 4 parts to it:

a) Code Hooks - Extend functionality of event listeners (what was done for "Guarantor Release for Blocked Funds" for loans) to include key business events like loan creation, loan approval, loan disbursement, savings account creation, savings account activation, savings withdrawal, client creation, client approval, etc. Pre- and Post- events to be enabled for these business events.
b) Enable rules (using Drools) for specific business events (Pre- and Post-)
c) If rule enabled, then evaluate rule. Rule should get the business object and any parent business object as input (Example for a loan disbursement, the loan account and the client details will be automatically supplied as inputs to the rule; For a savings withdrawal; the transaction, savings account and client details will be input to the rule. Evaluate rule and return true or false if the action should continue or not.
d) Implement Client level and account level limits using these rules - this will involve evaluating rules on data that is not directly supplied - For example: customer wants to withdraw 5,000. But has already touched the limit of 10,000 per day. The rule should be capable of evaluating the totals of transactions (i.e. use data not directly supplied to the rule).

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.

In most of the cases MFI wants to capture additional data during certain workflows (example: during client closing, wants to conduct exit survey, capture PPI during loan creation) and this requirement can fulfilled by adding option to attach datatable/survey/question group to the pre-defined workflows as certain points (example: during loan creation, during approval time or during disbursement etc).

Enhance data tables to emulate real-life workflows:

• Classification of data tables - as Data capture, UI-read-only, Surveys etc.

• Long internationalized labels for fields

• Sequencing of data tables

• Pre-conditions for a data table - so that the a data can be captured/screen is made visible only if certain conditions are met

• Conditional data tables - For example: some data to be captured for Individual Clients whereas other data to be captured for small businesses

• Data table to be captured along with main entity itself within the same transaction - for example: Address fields for client

• Self-service vs. Staff data tables
  (This list to be reviewed with Markus and Ed to ensure that there is no duplication of effort with other projects like SPM tool)

Helps organization to streamline their data capture process in the MIS and as well as in the field. And this leads toward more measurability of the MFI's impact in the field and more transparency.

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.

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's goal is to create an Amazon Cloud formation template for Mifos deployments at large Organisations. We would measure how we scale, with concrete scenarios and hard numbers, and produce documentation about this helping organization who are evaluating Mifos.

We would also try to identify and fix performance bottlenecks in the MifosX and the community app codebase

You would be creating a Cloud formation template on AWS for a sample high performance Mifos setup. The setup would include

• Approximately 5 web servers (Apache) on medium EC2 instances fronted with a load balancer
• Approximately 5 Tomcats servers on large EC2 instances fronted with a load balancer
• Multi Az extra Large RDS
• Distributed in memory cache environment

You would then use Jmeter (or a tool of your choice) to create realistic data and run and benchmark performance on this setup. Based on the figures, we would make fixes to either to the MifosX / Community app codebases to fix any identified performance bottlenecks and then carry out multiple iterations of tweaking the Cloud formation template to achieve best performance.

http://twitter.github.io/iago/

http://www.loadui.org (by the good people behind SOAPui)

Selenium WebDriver

https://jmeter.apache.org/

http://grinder.sourceforge.net/

http://opensta.org/

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

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