PPI Functional Spec
Release | Leila E |
Current Owners | Kay Chau |
Status (Draft, In Review, Approved) | In Review |
Contents:
- 1 Introduction
- 1.1 User Stories
- 1.2 Goals
- 1.3 Non-Goals
- 1.4 Definitions and Terminology
- 1.5 Related Documents
- 2 Use Cases
- 2.1 Access PPI's
- 2.2 Activate India PPI
- 2.3 Change where the PPI questions are asked
- 2.4 Have PPI questions asked in more than one flow
- 2.5 Inactivate PPI
- 2.6 Save PPI Answers
- 2.7 Save another set of PPI Answers
- 2.8 Update Incorrect Answers Captured with a PPI Survey
- 2.9 Update Incorrect Questions/Answer Choices with a specific PPI Survey Version
- 2.10 Update Incorrect Answers' Point Values with a specific PPI Survey Version
- 2.11 Update Incorrect Lookup Table(s) with a specific PPI Survey Version
- 2.12 Update NEW PPI Survey version
- 2.13 View PPI Score and Likelihoods
- 3 Functional Requirements
- 4 Standard Considerations
- 4.1 Security
- 4.2 Impacts to System
- 4.3 Globalization/Localization
- 4.4 Logging
- 4.4.1 Change Log
- 4.4.2 Reporting
- 4.5 Performance
- 4.6 Setup and Installation
- 4.6.1 New Installations
- 4.6.2 Backward Compatibility and Upgrades
- 4.6.3 Hosting Support
- 4.6.4 Configuration
- 5 Open Issues
- 6 Reviews and Approvals
Introduction
PPI as it is in Mifos is difficult to use and does not meet all the needs of an MFI who using PPI. We need to implement the feature in Mifos so that it is more flexible, and provides the reporting capabilities to do analysis. For Leila E, we must meet our Cisco commitments.
If the PPI form for a country is determined by an XML, does this mean the MFI can download and replace their template at anytime without updating Mifos? If this is the case, what do we have in place to make sure they aren't changing the XML file or altering it?