Credit Scoring

Target release
Document statusDRAFT
Document owner 

Feature Name

Name of feature. Describe the feature in 5 - 7 words. For example: "Declining balance interest calculation" or "Displaying previously saved attendance values in Bulk-Entry".


Feature Summary

  • Brief 2-3 sentences summarizing the feature and overview of the functionality to be achieved. Some of this may be explained in the background section. An example for "declining balance" would be: This feature would allow MFIs to create loan repayment schedules with equal installments and interest based on the declining balance formula.

Background and strategic fit

Business Need

Feature Requirements


Requirements/User Stories

In this section provide as much detail as possible about the business processes and user stories the new feature would support as well as step-by-step instructions for how it would be used. When writing the step-by-step instructions you should consider all the different scenarios a user might encounter in working with the new feature. Typically these scenarios are broken down into two types. - primary and alternate flows.

First focus on documenting the primary flows - these are the most common ways a user would interact with a feature. 

Keep each user story concise and simple i.e. As a <type of user>, I want <some goal> so that <some reason>. These can broken down further into smaller more detailed user stories. Please see these resources for tips on writing good user stories

#TitleUser StoryImportanceNotes

Business Rules



Security and Permissions

Mifos Functionality Enhancements

New Screens

Changes to Existing Screens

Changes/Enhancements to Batch Jobs

Changes/Enhancements to Accounting Entries

User interaction and design

Exception Handling





Below is a list of questions to be addressed as a result of this requirements document:


Out of Scope