Development – The Database

The database was also designed as two parts namely the “System” part and the “Business” part. System portion of the database was designed to hold data that is vital to system functionality but has less use when it comes to business functionalities. For that purpose the Business portion of the database was designed. This design approach enabled the separate development of system driving logic and business process driving logic.



System

Contains data required for system level functionality. This mainly includes User management and User privilege management.

The Entity Relationship (ER) diagram for the system part is as below.

Logic


Contain data for dealing with business logic (in this case, Fixed Deposit management process) and logic for creating reports.

The ER diagram for the logic part is somewhat extensive. So I’ll just give the list of tables here with a brief definition stating the use of each table.

• lgc_address (Address information)
• lgc_application (Fixed Deposit application information)
• lgc_bank (Bank information)
• lgc_bank_branch (Bank branch information)
• lgc_certificate (FD certificate information)
• lgc_city (City information that will be used in addresses)
• lgc_client (FD client information)
• lgc_client_type (FD client type information)
• lgc_cl_cl_type (Client to client type mapping)
• lgc_district (District information that will be used in addresses)
• lgc_employment (FD client employment details)
• lgc_eod (Data for End of the Day process)
• lgc_interest_rates (FD interest rate information)
• lgc_interest_schedule (FD interest schedule information for an application)
• lgc_payment (FD payment details)
• lgc_payment_schedule (FD payment schedule information for an application)
• lgc_province (Province information that will be used in addresses)
• lgc_receipt (FD receipt information)
• lgc_renewals (FD renewal information)
• lgc_withdrawals (FD withdrawal information)