Integratech
BOSS
Design Model Report
Issue 1.0
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
Issue:
1.1
Issue Date: 12/Jun/2011
Revision History
Date
12/06/2011
Issue
1.0
Description
First Issue
Author
Jawahar Chelliah
Distribution
Name
Department
Vijeyakumar K
Management
Dave Hufton
Suria R Asai
Anupama
Bright D L
Jawahar Chelliah
Karthi K
Maya Roosevelt
Satish Kumar
Tan Achilles
ISS Faculty
ISS Faculty
MTech SE18 2E
MTech SE18 2E
MTech SE18 2E
MTech SE18 2E
MTech SE18 2E
MTech SE18 2E
MTech SE18 2E
Organisation
Email
Integratech.Pte. Ltd.
vijey@integratech.com.sg
NUS
NUS
NUS
NUS
NUS
NUS
NUS
NUS
NUS
issdrh@nus.edu.sg
suria@nus.edu.sg
g0802147u@nus.edu.sg
A0065792@nus.edu.sg
A0065999@nus.edu.sg
A0065977@nus.edu.sg
A0065877@nus.edu.sg
A0065901@nus.edu.sg
achillestan@nus.edu.sg
Page 2 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
Issue:
1.1
Issue Date: 12/Jun/2011
Table of Contents
1.
2.
3.
Brief Description
4
1.1
1.2
1.3
1.4
4
4
4
4
System Set Up
System Administrator Operation
Branch Officer Operation
Loan Officer Operation
Transaction from Analysis to Design
4
2.1
2.2
Persistence Mechanisms
Object Creation
2.2.1 Object Constructors
2.3
Use of API
2.4
Transaction Strategy
2.4.1 Design Transaction Strategy
2.4.2 Transition Strategy for data persistence (MySQL)
2.4.3 Package Diagram
5
5
5
5
6
6
7
8
Appendix
9
Page 3 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
Issue:
1.1
Issue Date: 12/Jun/2011
Design Model Report for BOSS
1.
Brief Description
This is BOSS interface system. The system allows Branch Officer(BO) and Loan Officer(LO) to upload and
download data from MIFOS and Mobile channel also system allows to generate various reports for Branch Officer
and Administrator.
The system shall be written as a java based window application (J2SE). For the data storage the system used MySQL
Database for persistence data. Use credential is provided to use the system.
The system functions have given in below table.
System Function
User Management
Device Management
Report Generation
Download Data(Mobile channel
to BOSS offline data transfer)
Manage Data
Sync Data (BOSS to MIFOS and
vice versa)
Push Data (BOSS to Mobile
channel)
1.1
Actor
System Administrator
System Administrator
System Administrator and Branch Officer
Branch Officer and Loan Officer
Branch Officer and Loan Officer
Branch Officer
Branch Officer
System Set Up
The main user interface is start up by system controller. The user can used the system by using follow for respective
user level –
System Administrator/Branch Officer/Loan Officer – From Main Window, click on the respective button and
activate the user log in page. Then enter the credential to perform related function.
1.2
System Administrator Operation
To be updated
1.3
Branch Officer Operation
To be updated
1.4
Loan Officer Operation
To be updated
2.
Transaction from Analysis to Design
The design of BOSS Application is based on the analysis report. The use case structure is defined inn the Use-Case-
Page 4 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
Issue:
1.1
Issue Date: 12/Jun/2011
Model-Survey and the requirement of each use case are defined in the “Use Case Realization Report (Analysis”
document for each use case.
The changes from analysis to design transaction are following –
 Persistence mechanisms
 Object Creation
 Use of Java API
 Transaction Strategy
2.1
Persistence Mechanisms
To updated
2.2
Object Creation
For ensuring that all objects have references to the objects to which require communicating is described by following
2.2.1 Object Constructors
Every object is created by constructor. This operation has the same name as the object in Java Language. These
operations have been added to each object.
2.3
Use of API


Java AWT Swing
Java.lang.Properties
Page 5 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
2.4
Transaction Strategy
2.4.1
Design Transaction Strategy
Issue:
1.1
Issue Date: 12/Jun/2011
The GUI of the BOSS will be implemented using the Java Swing Library. The screen design diagram will guide
programmer to follow the design strategy. We will not explain details of the implementation some we will leave it for
programmer feel free to program with their own knowledge. For the screen –we use frame, Message dialog and
panel. For the user trigger the event, we use button and radio button.
Impacted Analysis Objects
We adapted Swing objects to implement the user display and trigger user actions. All the boundary objects are
impacted. All the controllers’ objects that interact with boundary object are affected. The controller objects are
adapted Action Listener object which are included in AWT object to be able to accept user’s request.
Impacted Use Cases
Page 6 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
2.4.2
Issue:
1.1
Issue Date: 12/Jun/2011
Transition Strategy for data persistence (MySQL)
Design Considerations:



Future adaptability to other enterprise databases
Extensibility of new tables and flexible table design
Generic In Memory Database for fast data access
Proposed Architecture:

DAO + Abstract Factory Pattern will suit the design requirements of this project. It provides
uniform implementation for different database vendors including flat files. For each domain
object, corresponding Data Access Objects are created with a predefined interface (to maintain
uniformity) to perform CRUD operations. The information is passed on to different layers using
Data Transfer Objects or Value Objects.
AbstractDAOFactory instantiates appropriate DAO Factory based on the passed argument and
allows seamless adaptability to other database implementations without much change to the
interfacing layers.
DAOFactory Type
Value
Page 7 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
Issue:
1.1
Issue Date: 12/Jun/2011
PropertiesDAOFactory
0
OracleDAOFactory
1

InMemoryDatabase is composed of Table which in turn has Row and list of columns.

CommonUtils contains logic to read and write the data from and to flat files (.properties) along
with a set of helper classes viz. ConnectionHandler, PropertyReader, Property Writer.
CommonUtils identifies all the files from the data directory as per the application configuration

PropertyReader, PropertyWriter uses java.lang.Properties to read and write the data to the file.
2.4.3 Package Diagram
BOSS Application, all the user interfaces (View) are located in view package. Utils package is used for system
Page 8 of 9
Micro Finance Management System
Rational Unified Process Use-Case Realization Report
(Requirements)Design Transition Report
INT/MFMS/SU.3
Issue:
1.1
Issue Date: 12/Jun/2011
configuration file. Dao package includes all the data access layer classes which will communicate with properties
files. The controller package includes all the controller objects of the system which will directly call by Main
package. Main packages included system step up classes. Data Transfer Object (DTO) includes all the display
entities. Exception packages includes all the details exception classes.
3.
Appendix
Please refer the separated for each use case realization report.
Page 9 of 9