Make your own free website on Tripod.com

 System Testing      System Introduction       Preliminary Investigation       System Analysis

SYSTEM DESIGN  

                 After completing my requirement analysis I started to develop my proposed system. The next step of software development is System Design. The system design was divided into two phases

Logical Design

       Data Flow Diagram 

         Entity Relationship Diagram 

       Physical Design

                  User Interface 

                     Reports

4.1 Logical Design:

                          A logical data flow diagram shows the flow of data through a transaction processing system without regard to the time period when the data flows or the processing procedures occur. Here I designed the software logically, using process modeling by Data Flow Diagram (DFD) and Data Modeling by ER-D technique.

4.1.1 Process Modeling:                   

          A process modeling is a simplified representation of some aspect of real world process, which is used to help us analyze the real world. A model is a real time representation of the real world element, group of elements and the relationship among them. As MIS is very complex it is very useful to develop process model to understand complex problems.         

  4.1.1.1 Data Flow Diagram (DFD):                               

                 DFD is one of the most powerful and useful techniques available to the system analyst. It graphically represents the information system. Which means it shows all the incoming data, processing of data and finally output destination of the information.

 Figure: 4.1 Context Level DFD for L oan Management System

Figure: 4.2 System Level DFD of Loan Management System

 

 Figure: 4.3 1st Level DFD of Loan Management System (New Loan Processing) 

  Figure: 4.4  1st Level DFD of Loan Management System (Not Due)

  Figure: 4.5 1st Level DFD of Loan Management System (Rephase)

 

Figure: 4.6 1st Level DFD of Loan Management System (Over Due)

5.1.2 Data Modeling:

            A database system is basically a computerized record-keeping system. The database itself can be regarded as a kind of electronic filing cabinet i.e., it is repository or container for a collection of computerized data files.

            Entity-Relationship Model (E-R Model) is a very useful tool for modeling the entities and their relationship in real world entities. So, I took the help of ER-D to model the data requirements of my automated loan system.       

 

 

Figure 4.7 ER diagram of Loan Management System

 

4.2 Physical Design:

 

           A user-friendly interface was developed for Loan Management System. I used Oracle Developer 2000 for developing the interface. Form 6i was used to develop input forms and report 6i was used to develop output reports.

 

4.2.1 Input Forms:

Main Screen: The form is a parent form. User can easily open different input forms and output reports from here. Initially when the system starts main screen is not activate.     

 

 

Form Name: Login Screen

 Description: This form is used to check users validity. If the user is valid then main screen activated.

From Name: Branch Information

Menu Path: Setup >>      Bran Information

Description: This screen is used to setup different branches.

Related Tables: BRANCH.

Form Name: Section Information

Menu Path: Setup        >>     Section Information

Description: This form is used to setup different sections.

Related Table: SECTION_TYPE 

Form Name: Ledger Information

Menu Path: Setup    >>        Ledger Information

Description: This form is used to setup different types of Ledger Section.

Related Table: LEDGER_SEC_INFO

Form Name: Project Information

Menu Path: Setup        >>     Project Information

Description: This form is used to setup new Project.

Related Table: PROJECT 

Form Name: Cycle Information

Menu Path: Setup         >>    Cycle Information

Description: This form is used to setup different types of installment cycle.

Related Tables: INS_CYCLE_INFO

Form Name: Other Charge Type

Menu Path: Setup         >>   Other Charge Information

Description: This form is used to setup different types of other charge type.

 Related Tables: OTHER_CHARG_TYPE

Form Name: New Currency Entry

Menu Path: Setup         >>   Currency Information

Description: This form is used to setup different types of currency.

Related Tables: CURRENCY_INFO

 Form Name: Loan Master

  Menu Path: Regular Entry           >> Not Due        >>   Loan Master

 

Description: when a new loan number is created this screen is used to entry/create the new loan number and other required information details. To complete this process user should input different type of related information such as project id, currency code, sanction details, installment details, disbursement details and other related information.   

Related Table: LOAN_MASTER & LOAN_BALACE.

 

Form Name: Loan Disbursement

  Menu Path: Regular Entry        >>    Not Due >>          Loan Disbursement

 

Description: This screen is used to entry Disbursement Information of a specific loan number. The information includes disbursement amount, value date, transact date etc.

Related Table: LOAN_DISBURSE

 Form Name: Repayment Schedule

  Menu Path: Regular Entry      >>         Not Due  >>          Repayment

 Description: This screen is used to prepare the Repayment Schedule of the Not Due Section for installment (Principle & Interest) fall.

Related Table: REPAY_SCH_MASTER & REPAY_SCH_DETAIL

Form Name: Amount Falling Form

  Menu Path: Regular Entry           >>  Not Due  >>           Amount Fall

Description: This screen is used to move all the due amounts to over due section.   

Related Table: LOAN_BALANCE

Form Name: Pay Receive

  Menu Path: Regular Entry         >>   Over Due        >>   Pay Receive

Description: This screen is used to entry the Received Amount. To entry in this screen user should give the project information with value date, loan number on which the pay amount will be adjusted

Related Table: PAY_RECEIVE_MASTER & PAY_RECEIVE_DETAILS

Form Name: Other Charge Entry Screen

  Menu Path: Regular Entry         >>   Over Due  >>         Other Charge

Description: This screen is used to entry Other Charges against loan number in over due section.

Related Table: OTHER CHARGE

Form Name: Rephrase Information

  Menu Path: Regular Entry        >>    Over Due       >>    Rephrase

Description: This screen is used for Rephasement Purpose. Here balance is transferred from old loan number to new loan number of the same project.  

Related Table: REPHARASE

Form Name: Rebate Information Screen

  Menu Path: Regular Entry       >>     Over Due   >>        Rebate 

Description: If any rebate is given against any loan number then this information is stored using this screen.

Related Table: Rebate

4.2.3 Reports:

 

Report Name: Not Due Ledger

  Menu Path: Reports           >> Not Due        >>    Not Due Ledger Balance       

Purpose:  This report shows branch wise ledger information of loan number.

 

Input Parameters: Branch Number

 Report Name: Disbursement Balance

  Menu Path: Reports  >>          Not Due     >>       Disbursement Balance

Purpose:  This report shows Disbursement Balance information of the Branch Name.

 

 

Input Parameters:  Branch Name

 Report Name: Pay Receive

  Menu Path: Reports     >>       Over Due     >>       Pay Receive

Purpose:  This report shows received amount in a particular time Period.

Input Parameters:  Dates

Report Name: Over Due Balance

  Menu Path: Reports  >>         Over Due   >>         Over Due Balance

Purpose:  This report shows the detail of the over due ledger.

  

 

 Input Parameters:  Branch Name

Report Name: Over Due Summery

Menu Path: Reports     >>      Over Due     >>       Over Due Balance

Purpose:  This report shows the summery over due balance of all the branches.

 

 Input Parameters: No input parameters needed.

Home