|
|
|
|
| Changed: |
<
< |
| >
> |
|
| Changed: |
<
< |
Here is a draft of the proposed MOAP system architecture. This document is intended to show how the component parts of the application would fit together. Each module would be linked through XML data interfaces, for a loosely-coupled architecture. Each component will maintain its own data store, if required. The areas of initial development emphasis will be in the Portfolio System and Security Layer. The remaining modules will be developed subsequently. Please see the SoftwareRequirementsSpecification for more details.
| >
> |
This document lays out the major components of the MOAP architecture. The MOAP architecture consists of a set of focused, well-designed tools that can be used in combination or independent of other tools. It is based on the idea of open data standards and interoperability.
|
| Changed: |
<
< |
This module will be used to track the institutions core savings and lendings activities. It will consist of modules to track clients and groups, loans and savings accounts, and manage the organization, its branches and loan officers. It will also include the functionality to generate portfolio reports. Reports will be created in standard XML format, which can then be formatted by the Report Formatter module.
| >
> |
|
| Changed: |
<
< |
This will be a basic accounting system. The system can be used to define a chart of accounts, make general ledger entries, and produce accounting reports like balance sheets and income statements. We will also include the provision to link the MOAP architecture to existing third-party accounting systems, using the MOAP Data Toolkit, described next.
| >
> |
|
| Changed: |
<
< |
This will be a 'glue' type of component, consisting of various tools and classes that link the other components using standard XML data formats. It will be able to perform the following tasks: 1) Export data from Portfolio system to XML format, 2) Export data from Accounting system to XML format, 3) Generate XML summary reports from Portfolio and/or Accounting systems, 4) Post Portfolio data to Accounting system and 5) Import Portfolio and Accounting data from branches. It will include a set of plug-ins to link with different portfolio and accounting systems (such as the ones included in the MOAP reference implementation). It is also likely that modules, such as the Report Generator, will be used in other components of the MOAP reference implementation.
| >
> |
This is a simple tool used to input data from the field. It will include basic data entry tasks such as inputting information about clients, groups, new account applications and transactions. It will allow for the creation of basic operational reports (using the Report Generator, below) and for the export of data for delivery to the central MFI office. It will be built with the mimimum system requirements and be easy to install and maintain.
- Implementation: Tomcat / MySQL
- Users: Loan Officers
- Locations: Branch, MFI
This will be a set of plug-ins to third party accounting systems. The basic tasks it will perform include export of transaction data into the accounting system and generation of reports requiring accounting data, such as balance sheets, income statements and certain indicator calculations. The MOAP project may eventually develop its own accounting package, but for now it is meant to work with existing third-party solutions.
- Implementation: Variable
- Users: Accountants, MIS Staff
- Locations: Branch, MFI
This tool will be used to create formatted HTML reports from a relational database. Initially it will support only the one or two RDBMS systems used elsewhere in MOAP. It will consist of two components: the first component will convert the relational data into a standard moap:report XML document, based on a specification in an included Report Description Language. The second component will be a report formatter, taking a document in moap:report format and converting it to a presentable / printable form such as HTML. It is likely that we can use some Open XML standards and tools to help in both these tasks.
- Implementation: TBD
- Users: All
- Locations: All
This module will be used to manage a consolidated loan portfolio. It will include tools to create financial products, set policies, manage loan officers and branches, review account applications, etc. It will be linked with the Report Generator module, allowing the manager to print reports required for management of the portfolio. It may also include graphical tools to analyze and track portfolio performance.
- Implementation: Tomcat / MySQL
- Users: Branch / MFI Managers
- Locations: Branch, MFI
This will be a 'glue' type of component, allowing for the import of consolidated report data from the branch offices. It will import XML data in moap:report format into the central MFI database. It will also export data to the branch offices for configuring the Portfolio Input Tool and setting institution-wide products and policies.
- Implementation: J2EE / MySQL
- Users: MFI MIS Staff / MFI Managers
- Locations: MFI
This tool is intended to consolidate data from a number of MFIs, useful for network organizations, donors, banks, rating agencies and others interested in interacting with a group of MFI partners. It will import XML data in moap:report format.
- Implementation: J2EE / MySQL
- Users: Networks / Banks / Rating Agencies
- Locations: Network Office
This tool will be used to analyze data about a number of MFI partners. Used in conjunction with the Network Aggregator, it will allow networks, banks, and other third-party observers to collect and analyze data across a number of MFIs. It will be linked to the Report Generator module for making consolidated analytical reports, and may also include other graphical tools to monitor and evaluate MFI performance.
- Implementation: J2EE / MySQL
- Users: Networks / Banks / Rating Agencies
- Locations: Network Office
This component will be used to create users with different priveleges that define their ability to access other system components. This will limit their access to the various components and features of the MOAP system. This should be implemented using JAAS and be uniform across the program modules.
- Implementation: JAAS
- Users: All
- Locations: All
Information relating to a microfinance account portfolio. Will include information about clients, groups, accounts, financial products, transactions, etc.
Specialized schema representing microfinance transaction information. May include data elements from standard financial transaction schemas.
Schema representing any kind of report or data to be exchanged across the MOAP network. Will include data elements from both the moap:transaction and moap:portfolio, as well as elements from a standard financial reporting language such as XBRL.
|
| Deleted: |
<
< |
This tool will be used to create formatted HTML reports from the raw XML source. It is likely that we can find some Open Source XML toolkits to help in this. This module can be considered part of the MOAP Data Toolkit.
This module will be used to create users with different priveleges that define their ability to access system components. This will limit their access to the various components and features of the MOAP system.
|
| Added: |
>
> |
-- TapanParikh - 7 May 2004
|
| Added: |
>
> |
%META:FILEATTACHMENT{name="moap-arch-new.jpg" attr="" comment="" date="1083971482" path="moap-arch-new.jpg" size="41940" user="TapanParikh" version="1.1"}% |
|
|
| Changed: |
<
< |
| >
> |
|
| Changed: |
<
< |
| >
> |
|
| Changed: |
<
< |
| >
> |
|
| Changed: |
<
< |
| >
> |
|
| Changed: |
<
< |
This tool will be used to create formatted HTML reports from the raw XML source. It is likely that we can find some Open Source XML toolkits to help in this. This module may also be considered part of the MOAP Data Toolkit.
| >
> |
This tool will be used to create formatted HTML reports from the raw XML source. It is likely that we can find some Open Source XML toolkits to help in this. This module can be considered part of the MOAP Data Toolkit.
|
| Changed: |
<
< |
| >
> |
|
|
|
| Changed: |
<
< |
Here is a draft of the proposed MOAP application architecture. This document is intended to show how the component parts of the application would fit together. Each module would be linked through XML data interfaces to support loosely coupled system development and evolution. Each component will maintain its own data store, if required. The areas of initial development emphasis will be in the Portfolio System and Security Layer. The remaining modules will be developed subsequently. Please see the SoftwareRequirementsSpecification for more details.
| >
> |
Here is a draft of the proposed MOAP system architecture. This document is intended to show how the component parts of the application would fit together. Each module would be linked through XML data interfaces, for a loosely-coupled architecture. Each component will maintain its own data store, if required. The areas of initial development emphasis will be in the Portfolio System and Security Layer. The remaining modules will be developed subsequently. Please see the SoftwareRequirementsSpecification for more details.
|
| Deleted: |
<
< |
|
| Changed: |
<
< |
This module will be used to track the institutions core savings and lendings activities. It will consist of modules to track clients and groups, loans and savings accounts, and manage the organization, its branches and loan officers. It will also include the functionality to generate portfolio reports. Reports will be generated in a standard XML format, that can then be formatted by the Report Formatter module.
| >
> |
This module will be used to track the institutions core savings and lendings activities. It will consist of modules to track clients and groups, loans and savings accounts, and manage the organization, its branches and loan officers. It will also include the functionality to generate portfolio reports. Reports will be created in standard XML format, which can then be formatted by the Report Formatter module.
|
| Changed: |
<
< |
This will be a basic accounting system. The system can be used to define a chart of accounts, make general ledger entries, and produce accounting reports like balance sheets and income statements - again in a standard XML format. We will also include the provision to link to existing third-party accounting systems, in which case we may include some provision for conversion of its reports and data into XML.
| >
> |
This will be a basic accounting system. The system can be used to define a chart of accounts, make general ledger entries, and produce accounting reports like balance sheets and income statements. We will also include the provision to link the MOAP architecture to existing third-party accounting systems, using the MOAP Data Toolkit, described next.
|
| Changed: |
<
< |
This will be a 'glue' type of component, used to link different types of accounting systems with the included portfolio system. It will be able to import data from both the accounting and portfolio systems (once again using XML), and produce consolidated reports requiring data from both components. This includes some common indicator calculations, such as the organizational sustainability figures published by SEEP. It will also be used to integrate data from branch offices to prepare consolidated organization-wide reports at the head office level. Finally, it will be used to export transaction data from the portfolio system (and maybe the branch offices) to the accounting system.
This module will be used to create users with different priveleges that define their ability to access system components. This will limit their access to the Portfolio and Data Integrator systems, and if they use the included Accounting System, then that as well.
| >
> |
This will be a 'glue' type of component, consisting of various tools and classes that link the other components using standard XML data formats. It will be able to perform the following tasks: 1) Export data from Portfolio system to XML format, 2) Export data from Accounting system to XML format, 3) Generate XML summary reports from Portfolio and/or Accounting systems, 4) Post Portfolio data to Accounting system and 5) Import Portfolio and Accounting data from branches. It will include a set of plug-ins to link with different portfolio and accounting systems (such as the ones included in the MOAP reference implementation). It is also likely that modules, such as the Report Generator, will be used in other components of the MOAP reference implementation.
|
| Changed: |
<
< |
This tool will be used to create formatted HTML reports from the raw XML source. It is likely that we can find some Open Source XML toolkits to help in this.
| >
> |
This tool will be used to create formatted HTML reports from the raw XML source. It is likely that we can find some Open Source XML toolkits to help in this. This module may also be considered part of the MOAP Data Toolkit.
|
| Added: |
>
> |
This module will be used to create users with different priveleges that define their ability to access system components. This will limit their access to the various components and features of the MOAP system.
|
| Deleted: |
<
< |
-- TapanParikh - 01 Apr 2004
|
| Changed: |
<
< |
%META:FILEATTACHMENT{name="moap-arch.jpg" attr="" comment="" date="1080783532" path="moap-arch.jpg" size="23630" user="TapanParikh" version="1.2"}%
| >
> |
-- TapanParikh - 2 April 2004
%META:FILEATTACHMENT{name="moap-arch.jpg" attr="" comment="" date="1080933040" path="moap-arch.jpg" size="30629" user="TapanParikh" version="1.3"}% |
|
|
| Added: |
>
> |
%META:TOPICINFO{author="TapanParikh" date="1080783240" format="1.0" version="1.1"}%
MOAP Architecture Draft
Here is a draft of the proposed MOAP application architecture. This document is intended to show how the component parts of the application would fit together. Each module would be linked through XML data interfaces to support loosely coupled system development and evolution. Each component will maintain its own data store, if required. The areas of initial development emphasis will be in the Portfolio System and Security Layer. The remaining modules will be developed subsequently. Please see the SoftwareRequirementsSpecification for more details.
This module will be used to track the institutions core savings and lendings activities. It will consist of modules to track clients and groups, loans and savings accounts, and manage the organization, its branches and loan officers. It will also include the functionality to generate portfolio reports. Reports will be generated in a standard XML format, that can then be formatted by the Report Formatter module.
This will be a basic accounting system. The system can be used to define a chart of accounts, make general ledger entries, and produce accounting reports like balance sheets and income statements - again in a standard XML format. We will also include the provision to link to existing third-party accounting systems, in which case we may include some provision for conversion of its reports and data into XML.
This will be a 'glue' type of component, used to link different types of accounting systems with the included portfolio system. It will be able to import data from both the accounting and portfolio systems (once again using XML), and produce consolidated reports requiring data from both components. This includes some common indicator calculations, such as the organizational sustainability figures published by SEEP. It will also be used to integrate data from branch offices to prepare consolidated organization-wide reports at the head office level. Finally, it will be used to export transaction data from the portfolio system (and maybe the branch offices) to the accounting system.
This module will be used to create users with different priveleges that define their ability to access system components. This will limit their access to the Portfolio and Data Integrator systems, and if they use the included Accounting System, then that as well.
This tool will be used to create formatted HTML reports from the raw XML source. It is likely that we can find some Open Source XML toolkits to help in this.
-- TapanParikh - 01 Apr 2004
%META:FILEATTACHMENT{name="moap-arch.jpg" attr="" comment="" date="1080783532" path="moap-arch.jpg" size="23630" user="TapanParikh" version="1.2"}% |
|
|
