Name of the project
Objective /Vision
Users of the system
Functional Requirements
Non-Functional Requirements
ii.
iii.
Optional Features
User Interface Priorities
Microfinance
To provide users a way to use their local PCO/CSC booths to
perform micro-finance banking away from the physical bank
To provide banks an effective way to interact with
1. Bank microfinance customers with bank accounts,
passbooks and photo identification.
2. Bank administrators to manage customers.
3. Bank managers to evaluate individuals performances
and assistance required.
User
1. Secure identification.
a. Identification of anyone assisting the user in
using the application.
2. History of loans, repayments, future options.
3. Opportunities in the domain of the user’s operation or
expertise.
4. Roadmap for financing and returns on effort invested.
Administrator
1. Details of financed individual.
2. Relevant history of funds utilization.
3. History of repayments and other borrowing
behaviour.
4. Brief and relevant history of kinds of transactions
conducted.
5. List of possible assistance from bank / institution.
6. Assistance for profession related matters of customer
/ user
7. Planning future activities.
Manager:
1. Most productive investments.
a. Assistance to be provided to these
individuals.
2. Most productive loans administrators.
3. Government support available in users’ domains.
i. Secure access of confidential data (user’s details).
SSL can be used.
24 X 7 availability
Better component design to get better performance at
peak time
Flexible service based architecture will be highly desirable for
future extension
A. Professional look and feel
B. Use of AJAX atleast with all registration forms
C. Browser testing and support for IE, NN, Mozila, and
Firefox.
D. Use of Graphical tool like JASPER to show strategic
data to admin
E. Reports exportable in .XLS, .PDF or any other desirable
format
Reports 1. For user:
2. Transaction record.
3. Statement of privacy from bank, service provider and
PCO operator.
4. For bank:
5. Transaction records by language.
6. Services used and requested.
7. Planning additional services for users.
8. For PCO operator:
9. User names.
10. Duration of use.
11. Any next scheduled date of use.

Other Important Issues 1. Transactions may be assisted by CSC operator. This

is why assistant-identification is important.
2. Some level of face-to-face administrator-interaction is
important. Plan your business process accordingly.

Team Size 2- 4 members

Technologies to be used
Tools to be used
Final deliverables must include
Documents
UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
• ROSE/RSA / WebSphere Modeler
• Eclipse/ RAD / Lotus Forms Designer / Portlet Factory
• WebSphere Portal/ WAS/ WAS CE / WPS
• DB2 Express – ‘C’ or DB2 UDB
• Tivoli CDP/TSM / Tivoli Directory Server
• Linux will be the preferred OS.
A. Online or offline help to above said users, Application
deployment executive and developer
B. Application archive ( .war/.ear ) with source code
C. Database backup and DDL Script
D. Complete Source code