[
http://mifosforge.jira.com/browse/MIFOS-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau updated MIFOS-3617:
----------------------------
Team: Reporting (was: Core)
> Agree Scope of First Phase of Data Warehouse
> --------------------------------------------
>
> Key: MIFOS-3617
> URL: http://mifosforge.jira.com/browse/MIFOS-3617
> Project: mifos
> Issue Type: Story
> Components: Scope
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Priority: Major
> Fix For: Release E - Iteration 7, Release E
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> After working in the Data Warehouse / Pentaho Platform area for a few weeks
> (using some standard reports as a basis for initial data warehouse
> requirements) below is my proposal for a minimum Data warehouse scope that
> moves DW a good step forward and implements key standard reports. (Need Adam
> F, Emily and Kay to get to grips with this). I know the words are a bit
> hurried but its better out than not, right?
> Timeframe
> =========
> About 1 month till deployment needed.
> To do a basic but running version of 3 reports and the "ETL" (datawarehouse
> work) to support them
> Reports:
> Loan officer detailed report
> MFI progress report
> Demand v Collection report
> The expectation is that the reports will run in initial testing on a
> first-cut ETL created database already available (but not completely
> accurate) within a few days. The ETL infrastructure will be updated to make
> the data accurate (taking into account changes to customer/LO/Branch
> hierarchy and customer/loan status changes). This will take 2 to 4 weeks and
> will involve as much review and tests are possible. Then when the data's
> good enough we can move to deployment.
> The ETL will support more than these 3 reports but is a minimum of what the 3
> reports need. Did consider doing sizeable parts of the reports without DW
> but felt (for me) it would not be useful (can always discuss why with
> whomever wants). It is, of course, possible to descope the reports so that
> they don't need 'historic' data and/or make them less complex to code but I'm
> suggesting we back the DW work in this time to see how we go. There are
> importants aspects of a DW implementation not in first scope... feel free to
> bring them back in first scope but do move out dates accordingly... We kind
> of need to see where we are with DW and, in a sense, needing some reports
> quite soon forces the issue.
> In First Scope
> ==============
> Client and Account metrics for branches, products, loan officers
> Schedule and Transaction data for loans and savings (including arrears data)
> Mostly, I'm only bringing in data items which are needed by the reports and
> reports like these. This includes items such as accurate hierarchy history
> and status history. This scope actually covers much of typical mifos
> reporting (beyond these 3 reports) but I found descoping further resulted in
> commensurate effort in the report itself which seemed a waste.
> Not In First Scope
> ==================
> Financial data imports
> Every/Most production data items
> metadata
> localisation (language support)
> full automated testing
> Not saying that what's not covered in first scope is not important... it is.
> But above is what's needed to get mifos feet under the datawarehousing table.
> I think automated testing,metadata and localisation will be essential... but
> can happen after.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
