Table of Contents
Several pages of documentation on mifos.org are outdated, reflecting specs for version 1.0 but not explicitly flagged as such. In addition, several newly added features either need documentation pages, or existing pages need to be added to the functional specifications table of contents.
Update: On 7/16/2008 added notice regarding status of content.The page links to an Excel spreadsheet archived at mifos.java.net that describes configuration inputs. This spreadsheet has not been updated for over 10 months. It should be checked for accuracy.
Update: On 7/16/2008 added notice regarding status of content.
- Has the concept of "user locale" been implemented?
- Which open issues have been resolved, and which remain?
- Update the list of features identified as out of scope for V1.1
Update: On 7/16/2008 added notice regarding status of content.
Update: On 7/16/2008 added notice regarding status of content.
This page describes features to be implemented in version 1.1. Verify which ones are actually implemented, and document accordingly.
Update: On 7/16/2008 added notice regarding status of content.
These pages include a section at the end titled "Out of Scope for Version 1.0", or sometimes just "Out of Scope", and containing a list of one or more features. This section should be retitled "Out of Scope for Version 1.1", and the list should be reviewed to be sure that each feature is still planned for a future version but has not yet been implemented.
Several projects listed at the DevelopmentProjectPages have seen intense activity recently, and may now be included in release 1.1, but several lack functional specs pages. The projects should be reviewed and their status in 1.1 documented. In some cases (see links below), developer wiki pages include functional specs of varying completeness, and could be linked to directly from the Functional Specs TOC. Or at least serve as a starting point for formal documentation of their function.
Most of these pages have not been updated for months or, in some cases, years. Yet some features have been updated and others have been deferred to v2.0. I strongly suggest that developers add to their workflow the requirement to updated these project pages when they have been involved in either implementing them or in decisions to defer them.
See this development project page
No activity. Assume deferred/out of scope?
See this development project page
This BIRT report is now installed – see ReportsImprovements below.
See this development project page
No activity. Assume deferred/out of scope?
See this development project page for an initial set of specifications.
Development has been active – see the issues that have been submitted and resolved, leading to new functionality. Functional specs should be updated accordingly.
See this development project page
Active development. Ensure that setup and configuration documentation is up to date.
See this development project page I do not know the status of this feature.
See this development project page
No activity. Identify as out of scope?
See this development project page
Ensure that deployment procedures include up-to-date instructions on configuring application settings.
See this development project page
Deferred to vNext per issue `1618 <https://mifos.dev.java.net/issues/show_bug.cgi?id=1618>`_. Should be marked as out of scope for release 1.1.
UPDATE: marked as out of scope on 7/16/2008.
See this development project page
Discussions on the developer listserve suggest that this feature is deferred.
See this development project page
According to issue `1664 <https://mifos.dev.java.net/issues/show_bug.cgi?id=1664>`_, this feature has been deferred to vNext.
See this development project page
No functional specs exist. The development page has a pretty complete description, but may need updating in light of recent development efforts. Espcecially lacking is
h>. Redoing Loan Disbursals
See this development project page
See this development project page
See gt;`_. Listed on the `Roadmap as deferred to V2.0.
See gt;`_. Listed on the `Roadmap as deferred to V2.0.
See gt;`_ . Listed on the `Roadmap as uhscheduled.
See this development project page THis feature is pretty completely implemented and needs to be included in V1.1 functional specs.
See here
Most of the web pages that describe These ENDA features have not been updated since 2007. Have any of them been added to V1.1? If so, descriptions of their features should be added to the Functional Specs table-of-contents. If not, they should be documented as either ENDA-specific, or out of scope for general 1.1 release, or features not planned for general implementation. Here are specific examples:
See gt;`_. Identified in the `Product roadmap as added to V1.1 Needs to be part of 1.1 functional specs.
See here `This post <http://groups.google.com/group/mifosdeveloper/search?group=mifosdeveloper&q=multiple+adjustments&qt_g=Search+this+group>`_ seems to indicate that the feature has been added. If so, add to functional specs.
See here Status unknown. Does not appear on the product roadmap.
See gt;`_. The page has not been updated for a year. Searching developer listserv, I found only `one reference to a failed attempt at a patch. The feature is not listed anywhere on the Product roadmap.
This page does not exist in Mifos.org. Can't find any information on this feature.
See here
This feature was added in March, 2008. This developers wiki page describes the functional specification for the feature.
TODO: Add a link to the wiki page from the functional specs table of contents.
See gt;`_. Identified in the `Product roadmap as added to V1.1 Needs to be part of 1.1 functional specs.
Documented at gt;`_. The fact that there is a `test plan for this feature implies that it has been implemented.
TODO: Add link to above wiki page from functional specs, and update client and/or group functional specs pages.
See here
This wiki page documents the specs for this feature, but I am not sure of its status for release 1.1. Discussion on the developer listserv seems to imply that the feature may not be working correctly and that it will be disabled for release 1.1. If so, then that should be documented.
TODO:
- Add link to this page from Function Specs table of contents.
- verify whether the feature will be enabled for release 1.1
- document the feature's status for release 1.1.
See here This feature has been implemented in V1.1, and should be documented in functional specs.See `these issues <http://tinyurl.com/5wto62> for more information.
Update: On 7/16/2008 added notice regarding status of content.
See here Does not appear on product roadmap.
See gt;`_. Listed on the `Roadmap as unscheduled.
See here This is a feature in its infancy, and has not yet hit the product roadmap.
See here
These pages include references to features that are restricted in version 1. This should be reviewed and updated to reflect any constraints remaining in version 1.1.