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.

Initial version of Mifos X was not designed to be database agnostic. Goal of this project is to make it so, and test this out in practice by running it locally on Oracle, make sure our test suite runs against Oracle as well as mysql, and well documenting how this can be set up by end-user clients, if they wish to go for this deployment.

To make this possible, all business logic has to be concentrated in the middle tier with the database being as dumb as possible. This means the platform does not rely on any database specific stored procedures or on the database to generate unique keys. And also application heavily use prepared statements (Spring jdbctemplate) for retrieving data and need to make sure all these queries use full JOIN syntax, and bracket the JOINs so that each join is between a single table and bracketed expression.

MFI with large client base can use the application with Oracle or any other commercial databases.

Mifos has abstraction from underlying database using:

• Hibernate as ORM (must have good experience with Hibernate)
• Liquibase as Database refactoring tool
• DbUnit as test dataset maintenance

Primary objective of this project is to build a standalone installer for MifosX platform. Standalone installer is a great way to evaluate and explore MifosX platform quickly. We want:

• Possibility of Mifos self-contained demo package
• Simple / easy launch of integration/acceptance testing, without requiring an external DB
• Development without manual MySQL installation

Standalone installer will consist of an embeded apache server and a DB. It should also ship with the latest mifosx build war file which should automatically deployed
on to the embedded server at the installation time.

1. Develop the installer as an executable jar format so that it will support many platforms with JRE.
2. Provides a simplified installation option with an embedded data base and a server.
3. Develop GUI and command line base installation modes.

GUI MODE OPTIONS
================

Tomcat Port This is the port at which to run tomcat.
MySQL Port This is the port at which to run mysql
File > Quit This menu item stops tomcat and mysql and then closes the application.
File > Launch Browser This menu item opens the MifosX login page for the current web application context.
File > Clear Output This clears the output log in a user interface text area. But does not clear the log file which will written on the file system.
Start This button runs tomcat, which will automatically start the mysql database engine if it was not already running. For the embedded mysql, the first connection automatically starts the mysql engine.
Stop This button stops tomcat and then also stops the mysql database engine, without closing the application.

COMMAND LINE OPTIONS
====================

-mysqlport Use to override the mysql port in the runtime properties file.
-tomcatport Use to override the tomcat port in the runtime properties file.
-start Use to start the server.
-stop Use to stop the server.
-browser Use to launch a new browser instance.

This sub-project would port / apply our MIFOS-5157 Installer-free simple launcher from classic Mifos to Mifos X, and then look at how to extend such a package to run without any existing external database as planned in MIFOS-4926 (which MIFOS-5157 doesn't cover). The first thought that comes to mind is to achieve this with a pure-Java in-memory database such as H2 or Derby. However, in order to avoid maintaining & supporting 2 different databases for Mifos, we'd like to base this on https://github.com/vorburger/MariaDB4j. While we are at it, we should also replace the classic GPL mysql driver by the LGPL MariaDB Client Library.

For many microfinance institutions who lack technical skills, installing Mifos X is a burden that prevents them from using this software to more efficiently serve the poor. Often they get lost in the installation process when having to separately install java, their web server, MySQL, and then deploy Mifos. A self-contained package acting as a simple one-step installer for Mifos would help make the software more accessible to more organizations and allow for MFI to more easily test the software and see the immense value it provides.

https://wiki.openmrs.org/display/docs/OpenMRS+Standalone
https://github.com/openmrs/openmrs-standalone
https://github.com/openmrs/openmrs-standalone/tree/master/src/main/config

See Linux Installers wiki page

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

The Mifos X platform as of today is a well structure but monolithic code base - one Git repo, one build, one WAR. This has worked out well for us, but as we grow, it could be interesting to introduce a proper SDK and plug-in concept, allowing contributors to build individual JARs that can be dropped into a certain directory of Mifos X to augment the core platform on well defined extension points and hooks. These modules would be loaded at run-time, not require rebuilding Mifos X, and would remain compatible when a customer upgrades their core platform version.

We currently see the SDK as something more relevant to the Java back-end, so in this project you would likely work less on our AngularJS UI (barring some configuration UI for the plug-ins probably); but if you do have any ideas how to make the front-end more modular and extensible as well, we would love to hear from you.

This project will have three axis/phases: 1. platform infrastructure framework kind of work, based on a very simple or fictitious example extension; 2. identifying the functionally which could require / be sensible to extend in Mifos X, extracting clear and documented Java APIs from it, and then make changes to existing functional platform services to make them extensible by plug-ins; 3. well document this - such plugins will only be written if it's easy and clear how to do this. Note that the more technical part 1. should only take about 1/4 of your project, the focus will have to be putting the "theory" from 1. into "practice" in phases 2. & 3.

Many other Java-based platform have such mechanism, and you would be expected to draw at least conceptual, if not outright technical inspiration (re-using code, if feasible) from things like the Eclipse Plug-In architecture (or similar non-OSGi based ones in other IDEs), research if Spring itself or some extension from someone has anything useful for this (think like Guice Multibindings plus ServiceLoader API as discussed on this StackOverflow, or this blog, or these Mycila Guice Extensions; but without going all the way to OSGi-based Spring DM / Dynamic Modules; again, overkill, here), get inspiration from drop-in add-on modules extension capabilities in enterprise software such as e.g. Atlassian plug-in framework, and learn how e.g. our friends at OpenMRS do this (see OpenMRS SDK doc and OpenMRS project).

To allow field-based staff to manage their daily schedules and to ensure that their supervisors are able to review these tasks and to plan field operations and bring in more efficiency and transparency for field operations

Field officers typically have a predefined set of tasks to follow, for example: Do survey for a locality, Conduct Group Trainings, Conduct Group Tests, Do Center Meetings and Collections. Each could have a task code to make operations streamlined.

Field officers manage their calendars by selecting an activity and specifying a center, date and time for which this activity is planned. This becomes their planned activity for this slot.

A simple workflow to manage each slot – when field officer starts the activity, status of the slot is changed from “new” to “open” and when the activity is completed, it is set to “closed”. It would be ideal to manage this workflow using a mobile tool – preferably an inbound SMS message. For example: an SMS from the field officer’s phone with the text “OPEN 1430” will change the status to “OPEN” of the field officer’s activity that was planned for 2:30pm.

Field officer may change his plan up to a certain time prior to the start of the activity.

Auditors and branch managers will review the activities and track the field officers’ planning and efficiency.

To run any business successfully, you need the insight of the business and that is possible when you have information system in which you can get the information in the format your business analysis team needs. And in current world business are very much market adaptive and market scenarios changes very rapidly. To cope up with that  good MIS need to have Ad-hoc report builder.

Easy-to-use, drag-and-drop report designer builds crosstabs, tables, and chart-based reports using a standard browser.

The ad hoc reporting will be based on a logical mapping of Mifos data elements to business entities (like customer, loan account, savings account, loan transactions, savings transactions etc.) and business attributes (like loan approved date, loan amount, loan outstanding amount etc.). An end user will be able to configure and generate reports based on these business entities and business attributes.

Reporting fields and reporting criteria will support basic derived fields like "days overdue", "amount overdue", "customer total outstanding amount", "customer total relationship value" etc.

The reporting will support basic functions like summing up totals, sorting based on different fields and grouping based on different fields.

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.

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

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

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.

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

During last year's GSoC 2013, star student (and GSoC 2014 mentor) Anuruddha has greatly contributed to the scalability of the Mifos X by adding server-side pagination and distributed caching to the platform. This project's goal is to measure just how well we really scale - with concrete scenarios and hard numbers, and produce documentation about this helping organization who are evaluating Mifos.

Beyond a one time exercise, you should set up infrastructure we can keep using, and integrate the tools you've used into our build chain so that, even after you've gone, help us to keep up good perf.

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/

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,

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

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.

Initial version of Mifos X was not designed to be database agnostic. Goal of this project is to make it so, and test this out in practice by running it locally on Oracle, make sure our test suite runs against Oracle as well as mysql, and well documenting how this can be set up by end-user clients, if they wish to go for this deployment.

To make this possible, all business logic has to be concentrated in the middle tier with the database being as dumb as possible. This means the platform does not rely on any database specific stored procedures or on the database to generate unique keys. And also application heavily use prepared statements (Spring jdbctemplate) for retrieving data and need to make sure all these queries use full JOIN syntax, and bracket the JOINs so that each join is between a single table and bracketed expression.

MFI with large client base can use the application with Oracle or any other commercial databases.

Mifos has abstraction from underlying database using:

• Hibernate as ORM (must have good experience with Hibernate)
• Liquibase as Database refactoring tool
• DbUnit as test dataset maintenance

Primary objective of this project is to build a standalone installer for MifosX platform. Standalone installer is a great way to evaluate and explore MifosX platform quickly. We want:

• Possibility of Mifos self-contained demo package
• Simple / easy launch of integration/acceptance testing, without requiring an external DB
• Development without manual MySQL installation

Standalone installer will consist of an embeded apache server and a DB. It should also ship with the latest mifosx build war file which should automatically deployed
on to the embedded server at the installation time.

1. Develop the installer as an executable jar format so that it will support many platforms with JRE.
2. Provides a simplified installation option with an embedded data base and a server.
3. Develop GUI and command line base installation modes.

GUI MODE OPTIONS
================

Tomcat Port This is the port at which to run tomcat.
MySQL Port This is the port at which to run mysql
File > Quit This menu item stops tomcat and mysql and then closes the application.
File > Launch Browser This menu item opens the MifosX login page for the current web application context.
File > Clear Output This clears the output log in a user interface text area. But does not clear the log file which will written on the file system.
Start This button runs tomcat, which will automatically start the mysql database engine if it was not already running. For the embedded mysql, the first connection automatically starts the mysql engine.
Stop This button stops tomcat and then also stops the mysql database engine, without closing the application.

COMMAND LINE OPTIONS
====================

-mysqlport Use to override the mysql port in the runtime properties file.
-tomcatport Use to override the tomcat port in the runtime properties file.
-start Use to start the server.
-stop Use to stop the server.
-browser Use to launch a new browser instance.

This sub-project would port / apply our MIFOS-5157 Installer-free simple launcher from classic Mifos to Mifos X, and then look at how to extend such a package to run without any existing external database as planned in MIFOS-4926 (which MIFOS-5157 doesn't cover). The first thought that comes to mind is to achieve this with a pure-Java in-memory database such as H2 or Derby. However, in order to avoid maintaining & supporting 2 different databases for Mifos, we'd like to base this on https://github.com/vorburger/MariaDB4j. While we are at it, we should also replace the classic GPL mysql driver by the LGPL MariaDB Client Library.

For many microfinance institutions who lack technical skills, installing Mifos X is a burden that prevents them from using this software to more efficiently serve the poor. Often they get lost in the installation process when having to separately install java, their web server, MySQL, and then deploy Mifos. A self-contained package acting as a simple one-step installer for Mifos would help make the software more accessible to more organizations and allow for MFI to more easily test the software and see the immense value it provides.

https://wiki.openmrs.org/display/docs/OpenMRS+Standalone
https://github.com/openmrs/openmrs-standalone
https://github.com/openmrs/openmrs-standalone/tree/master/src/main/config

See Linux Installers wiki page

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

The Mifos X platform as of today is a well structure but monolithic code base - one Git repo, one build, one WAR. This has worked out well for us, but as we grow, it could be interesting to introduce a proper SDK and plug-in concept, allowing contributors to build individual JARs that can be dropped into a certain directory of Mifos X to augment the core platform on well defined extension points and hooks. These modules would be loaded at run-time, not require rebuilding Mifos X, and would remain compatible when a customer upgrades their core platform version.

We currently see the SDK as something more relevant to the Java back-end, so in this project you would likely work less on our AngularJS UI (barring some configuration UI for the plug-ins probably); but if you do have any ideas how to make the front-end more modular and extensible as well, we would love to hear from you.

This project will have three axis/phases: 1. platform infrastructure framework kind of work, based on a very simple or fictitious example extension; 2. identifying the functionally which could require / be sensible to extend in Mifos X, extracting clear and documented Java APIs from it, and then make changes to existing functional platform services to make them extensible by plug-ins; 3. well document this - such plugins will only be written if it's easy and clear how to do this. Note that the more technical part 1. should only take about 1/4 of your project, the focus will have to be putting the "theory" from 1. into "practice" in phases 2. & 3.

Many other Java-based platform have such mechanism, and you would be expected to draw at least conceptual, if not outright technical inspiration (re-using code, if feasible) from things like the Eclipse Plug-In architecture (or similar non-OSGi based ones in other IDEs), research if Spring itself or some extension from someone has anything useful for this (think like Guice Multibindings plus ServiceLoader API as discussed on this StackOverflow, or this blog, or these Mycila Guice Extensions; but without going all the way to OSGi-based Spring DM / Dynamic Modules; again, overkill, here), get inspiration from drop-in add-on modules extension capabilities in enterprise software such as e.g. Atlassian plug-in framework, and learn how e.g. our friends at OpenMRS do this (see OpenMRS SDK doc and OpenMRS project).

To allow field-based staff to manage their daily schedules and to ensure that their supervisors are able to review these tasks and to plan field operations and bring in more efficiency and transparency for field operations

Field officers typically have a predefined set of tasks to follow, for example: Do survey for a locality, Conduct Group Trainings, Conduct Group Tests, Do Center Meetings and Collections. Each could have a task code to make operations streamlined.

Field officers manage their calendars by selecting an activity and specifying a center, date and time for which this activity is planned. This becomes their planned activity for this slot.

A simple workflow to manage each slot – when field officer starts the activity, status of the slot is changed from “new” to “open” and when the activity is completed, it is set to “closed”. It would be ideal to manage this workflow using a mobile tool – preferably an inbound SMS message. For example: an SMS from the field officer’s phone with the text “OPEN 1430” will change the status to “OPEN” of the field officer’s activity that was planned for 2:30pm.

Field officer may change his plan up to a certain time prior to the start of the activity.

Auditors and branch managers will review the activities and track the field officers’ planning and efficiency.

To run any business successfully, you need the insight of the business and that is possible when you have information system in which you can get the information in the format your business analysis team needs. And in current world business are very much market adaptive and market scenarios changes very rapidly. To cope up with that  good MIS need to have Ad-hoc report builder.

Easy-to-use, drag-and-drop report designer builds crosstabs, tables, and chart-based reports using a standard browser.

The ad hoc reporting will be based on a logical mapping of Mifos data elements to business entities (like customer, loan account, savings account, loan transactions, savings transactions etc.) and business attributes (like loan approved date, loan amount, loan outstanding amount etc.). An end user will be able to configure and generate reports based on these business entities and business attributes.

Reporting fields and reporting criteria will support basic derived fields like "days overdue", "amount overdue", "customer total outstanding amount", "customer total relationship value" etc.

The reporting will support basic functions like summing up totals, sorting based on different fields and grouping based on different fields.

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.

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

During last year's GSoC 2013, star student (and GSoC 2014 mentor) Anuruddha has greatly contributed to the scalability of the Mifos X by adding server-side pagination and distributed caching to the platform. This project's goal is to measure just how well we really scale - with concrete scenarios and hard numbers, and produce documentation about this helping organization who are evaluating Mifos.

Beyond a one time exercise, you should set up infrastructure we can keep using, and integrate the tools you've used into our build chain so that, even after you've gone, help us to keep up good perf.

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/

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,

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.

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

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