slp management system project - wordpress.com...slp accountant sydney loan portal accountant who...

SLP Management System Project

SIT Consulting

Presented by;

Oi Kwan Chan

Daniane Pereira Gomes

Mohammad Heydari

David Jeon

Kay Law

n

n

n

n

n

2 SLP Management System

Table of Contents

1. Introduction ............................................................................................................. 3 1.1 Scope and Purpose ......................................................................................................................................... 3 1.2 Glossary ......................................................................................................................................................... 4 1.3 Project Plan .................................................................................................................................................... 5

2. Functional Requirements ............................................................................................. 6

3. Non-functional Requirements ....................................................................................... 7 3.1. Operational Requirements ............................................................................................................................. 7 3.2. Performance Requirements ............................................................................................................................ 7 3.3. Security Requirements ................................................................................................................................... 7 3.4. Cultural and Political Requirements ............................................................................................................... 8

4. Use Case Description ................................................................................................. 9 4.1. ...................................................................................................................................................................... 9 4.2. .................................................................................................................................................................... 10 4.3. .................................................................................................................................................................... 11 4.4. .................................................................................................................................................................... 12 4.5. .................................................................................................................................................................... 13 4.6. .................................................................................................................................................................... 14 4.7. .................................................................................................................................................................... 15 4.8. .................................................................................................................................................................... 16 4.10. .................................................................................................................................................................. 18 4.12. .................................................................................................................................................................. 21

5. Special Issues ......................................................................................................... 22

6. Use Case Diagram ................................................................................................... 23

7. Activity Diagrams ................................................................................................... 24

8.Class Diagram ......................................................................................................... 36


1. Introduction

This document should provide an overview of the Sydney Loan Portal Management System project being developed and delivered by SIT Consulting. This document includes analysis of system requirements that are essential to delivering the project efficiently and flawlessly.

1.1 Scope and Purpose

Sydney Loan Portal is a mortgage broker company that offers member organizations loan products. The current process is very manual and inefficient. In addition clients do not have access to check loan statuses therefore Sydney Loan Portal needs to provide staff to support any client enquiries.

Sydney Loan Portal would like to implement a system that would enhance the quality of services and to minimize overheads. This includes providing an integrated system that would cater to the following requirements.

The purposes of the Sydney Loan Portal System are detailed below:

n Speed up the application process by up to 50percent.

n Automated direct streamline system between clients and members.

n Cutting expense as much as possible.

n Cutting as many jobs as possible.

n Eliminate the process of returning document because of wrong information.

n Allow customers to fill their own personal information.

n Show to the customers how much they can borrow based on their preferences.

n Simplify the membership application process.

n Automate the loan application process.

n Provide the ability to check the application status.

n Provide the ability to communicate between member organisations and SLP.

n Support the sharing of information between local member organisations and SLP.

n Provide the ability for clients to research loan products that best suit their requirements.

n Minimize the amount of paperwork and manual steps in the process.


1.2 Glossary

Term Definition

SLP Sydney Loan Portal

SLP Accountant Sydney Loan Portal accountant who maintain membership.

Member Real estate agencies, financial advisors and solicitors

Member principal The person who can apply for membership with SLP.

Loan processor The person who is part of member organization and is first contact point with potential customer.

Customer any individual or trust who is interested in having offered loan product

SNFR System Non Functional Requirement

UC Use Case

CRUD Create, Read, Update and Delete


1.3 Project Plan

ID Task Name DurationStart Finish Predecessors

1 Consulting with SLP 1 day Mon 13/08/12Mon 13/08/122 Identify Stakeholders 1 day Tue 14/08/12 Tue 14/08/12 13 Determine Project Scope 2 days Tue 14/08/12 Wed 15/08/1214 Determine Functional Requirements 4 days Thu 16/08/12 Tue 21/08/12 2,35 Review Functional Requirements 2 days Wed 22/08/12Thu 23/08/12 46 Determine Non-Functional Requirements 4 days Thu 16/08/12 Tue 21/08/12 2,37 Review Non-Functional Requirements 2 days Wed 22/08/12Thu 23/08/12 68 Develop Use Cases 5 days Fri 24/08/12 Thu 30/08/12 7,59 Identify Organisational Issues 4 days Fri 31/08/12 Wed 5/09/12 1

10 Preparing Presentation 4 days Thu 6/09/12 Sun 9/09/12 2,3,4,5,6,7,8,911 Developing Presentation 3 days Mon 10/09/12Wed 12/09/121012 Inform Stakeholders 1 day Thu 13/09/12 Thu 13/09/12 1113 Design Draft System Report 3 days Fri 14/09/12 Tue 18/09/12 1214 Submition of Draft System Report 1 day Wed 19/09/12Wed 19/09/121315 Further Analysis on All Functions and Report 15 days Wed 19/09/12Tue 9/10/12 1316 Determine Sub and Alternate Flows 10 days Fri 21/09/12 Thu 4/10/1217 Implement System 2 days Wed 26/09/12Thu 27/09/1218 Test System 2 days Thu 27/09/12 Fri 28/09/1219 Improve and Maintain System 4 days Mon 24/09/12Thu 27/09/1220 Final Report 7 days Fri 5/10/12 Mon 15/10/1213,16,17,18,19

M F T S W S T M F T S W S T M F T S W6 Aug '12 20 Aug '12 3 Sep '12 17 Sep '12 1 Oct '12 15 Oct '12

Task

Split

Milestone

Summary

Project Summary

External Tasks

External Milestone

Inactive Task

Inactive Milestone

Inactive Summary

Manual Task

Duration-only

Manual Summary Rollup

Manual Summary

Start-only

Finish-only

Deadline

Progress

Page 1

Project: INFO2110 Group ProjectDate: Fri 31/08/12


2. Functional Requirements

Priority Business Req. ID System Functional Requirement

Must 2 1.1. The principal of a member organisation must be able to apply for Membership with SLP.

Must 2 1.2. The accountant from SLP must be able to maintain the membership

Must 1 1.3. The applicant must be able to inquire on application status

Must 3 1.4. The loan processor must be able to maintain the loan application before sending it to SLP

Must 2 1.5. The loan processor must be able to view the status of the application.

Must 2 1.6. The principal should be able to check the application and approve the application to be sent to SLP.

Must 2 1.7. The principal, SLP accountant, and client must be able to communicate with each other in the system.

Must 3 1.8. The principal must be able to request a monthly report that provides details of enrolled customers and their status.

Must 1 1.9. Interested customers should be able to query for their preferred loan product by interest rate, financial organization, duration of the loan or place of member office.

Must 1 1.10. Registered customers should be able to complete a withdrawal form and submit it in the system to withdraw their application

Could 1 1.11. Registered customers should have ability to comment about the loan products or the loan application process.

Could 1 1.12. Registered customers should be able to recommend their member office to their friends.


3. Non-functional Requirements

3.1. Operational Requirements

Priority SNFR 1.Operational

Must 1.1. The principal, lenders, applicant and loan processor must be able to access the system from any desktop web browser.

Must 1.2. The system must be able to import Excel spread sheet files, word, PDF files, and JPEG images

3.2. Performance Requirements

Priority SNFR 2.Performance

Must 2.1. There should be a backup and recovery system implemented. System must hold backup files for at least 30 years.

Must 2.2. Response time for any interaction between user and the system should be less than 3 seconds.

Must 2.3. The system should update its internal data after new customer registration every one hour.

Must 2.4. The system should be available 24 hours a day, 7 days a week.

Must 2.5. There must be on site system support from one of our team member during working hours in weekdays in first month. After this time there will be technician on request from member principal or SLP accountant at their office.

Should 2.6. There should be an option for new users to take a tutorial and watch videos to learn about how the system works.

Should 2.7. The regular users of the system should be able to understand all functionality within the first 2 weeks of the system release.

3.3. Security Requirements


Priority SNFR 3.Security

Must 3.1. All information inside the system must be encrypted.

Must 3.2. Only customers with approved login credential by member principal should be able to see their details and their loan processing status

Should 3.3. The Customers can only see their submitted, saved, or withdrawn application history during business hours.

3.4. Cultural and Political Requirements

Priority SNFR 4.Cultural and Political

Must 4.1. Applicant requesting loan product must be an Australian citizen.

Must 4.2. All clients, SLP, members, and financial organization must follow Australian government and federal laws.


4. Use Case Description

4.1.

Name Apply for membership with SLP (FR 1.1)

ID Number UC - 1

Type External

Actor(s) Principal

Brief Description The principal of a member organisation must be able to apply for Membership with SLP.

Important Level High

Stakeholder(s) Principal, SLP Accountants

Trigger(s) Principal applies for the membership with SLP.

Normal Flow

n The principal apply for the membership with SLP.

n The system checks if the applicant meets all the criteria with SLP.

n If all the criteria are met, the SLP accountant approves the application.

n The principal is granted the membership with SLP.

Relationship Include: N/A Extend: N/A Association: Principal

Alternative Flow

n 1a: Principal fills out the application form incorrectly.

n 1a.1: System informs principal to refill the application form.

n 1a.1: Principal fills out the application form again.

n 1a.2: System returns principal to step 2 of normal flow of events.

n 2a: The applicant does not meet all the criteria for the application.

n 2a.1: System informs principal that he or she cannot apply for membership with SLP.

n 2a.2: Terminate the application process.


4.2.

Name Maintain membership with SLP (FR 1.2)

ID Number UC - 2

Type Internal

Actor(s) SLP Accountant

Brief Description SLP accountant should be able to create, read, update, and delete member(s)’ information.


Stakeholder(s) SLP accountant, principal, other members of SLP.

Trigger(s) SLP accountant

Normal Flow

n The accountant logs in to the system.

n The system validates the accountant.

n SLP accountant creates, read, update and deletes members’ information (CRUD operations).

n The system shows a message to the SLP accountant to confirm the information that has been updated from the previous state.

n The system displays the updated the information on the member upon the confirmation.

Relationship Include: N/A Extend: N/A Association: Principal, SLP Accountant,

Alternative Flow

n 1a: System cannot validate the client with provided user name or password.

n 1a.1: System validation of the user name/password combination fails due to incorrect entry.

n 1a.2: System returns to the step 1 of normal flow of events.

n 4a: System cannot validate the input from CRUD operation.

n 4a. 1: System returns to the step 3 of normal flow of events.


4.3.

Name Enquire application status (FR 1.3)

ID Number UC - 3

Type External

Actor(s) Applicant

Brief Description The applicant must be able to inquire on application status.


Stakeholder(s) Applicant

Trigger(s) Applicant requests about the status of the application.

Normal Flow

n The applicant logs in to the system.

n The system validates the applicant.

n The applicant enquires about his or her application status.

n The system prompts for application number.

n The system validates the application number.

n The system displays the application status.

Relationship Include: Login Extend: N/A Association: Applicant

Alternative Flow




n 5a: System validation of the application number fails due to incorrect entry.

n 5a.1: System informs client that application number is incorrect.



4.4.

Name Maintain loan application (FR 1.4)

ID Number UC - 4

Type External

Actor(s) Loan Processor

Brief Description The loan processor must be able to maintain the loan application before sending it to SLP.


Stakeholder(s) Loan Processor

Trigger(s) The loan processor requests to CRUD the loan application

Normal Flow

n The loan processor logs into the system.

n The system validates the loan processor.

n The loan processor creates, read, update and deletes members’ information (CRUD operations).

n The system shows a message to the loan processor to confirm the information that has been updated from the previous state.

n The system displays the updated the information on the loan application upon the confirmation.

Relationship Include: Login Extend: N/A Association: Loan Processor

Alternative Flow n 2a: System cannot validate the client with provided user name or password.



n 3a: System cannot validate the input from CRUD operation.

n 3a. 1: System returns to the step 3 of normal flow of events.

n 4a: Loan processor disapproves the update.

n 4a: System terminates.


4.5.

Name View the application status (FR 1.5)

ID Number UC - 5

Type External

Actor(s) Loan Processor

Brief Description This use case describes how a loan processor views the status of an application.


Stakeholder(s) Loan Processor

Trigger(s) The loan enquires about the status of an application.

Normal Flow

n The loan processor logs into the system.

n The system validates the loan processor.

n The loan processor enquires about the status of an application.

n The system prompts for the application number.

n The loan processor enters the application number.

n The system validates the application number.

n The system displays the status of the application.

Relationship Include: Login Extend: N/A Association: Loan Processor




n 4a: Loan processer enters invalid application number

n 4a. 1: System displays error message informing loan processer that they have entered an invalid application number

n 4a. 2: System displays screen requesting application number again

n 4a. 3: If user enters correct application number, system returns to step 5 of normal flow


4.6.

Name Authorise Application (FR 1.6)

ID Number UC - 6

Type External

Actor(s) Principal, Applicant

Brief Description This use case describes how the principal approves a loan application.


Stakeholder(s) Principal, Applicant, SLP Accountant

Trigger(s) The applicant submits an application for approval.

Normal Flow

n The registered applicant logs into the system.


n The applicant submits a loan application for approval.

n The system notifies the principal that the application requires authorisation.

n The principal opens application.

n The system displays the application.

n The principal approves the application.

n The system sends the application to SLP.

Relationship Include: Login Extend: N/A Association: Principal, Applicant, SLP Accountant




n 5a: The principal rejects the application

n 5a. 1: The principal rejects the applications

n 5a. 2: The system prompts the principal to enter a reason for the decline

n 5a. 3: The principal enters the reason for the decline

n 5a. 4: The system notifies the applicant that their application was declined and the reason for the decline


4.7.

Name Send messages (FR 1.7)

ID Number UC - 7

Type External

Actor(s) Principal, loan processor, SLP accountant, client

Brief Description The principal, SLP accountant, and client must be able to communicate with each other in the system.


Stakeholder(s) Principal, loan processor, SLP accountant, client

Trigger(s) Principal, loan processor, SLP accountant or client requests to create a new message.

Normal Flow

n The principal, loan processor, SLP accountant or client logs into the system.

n The system validates the user.

n The user requests to send a message.

n The system opens up the message editor.

n The user writes a message and a receiver.

n The system checks if the receiver is a registered user.

n The user submits the message.

n The system notifies the user that the message was sent.

Relationship Include: Login Extend: N/A Association: Principal, Loan Processor, SLP Accountant, client

Alternative Flow




n 7a: The system doesn’t find the user researched.

n 7a.1: The system notifies that the user wasn’t found.



n 9a:The system was not able to send the message.

n 9a.1: The system displays an error message.


4.8.

Name Generate customer’s report (FR 1.8)

ID Number UC - 8

Type External

Actor(s) Principal

Brief Description The principal must be able to request a monthly report that provides details of enrolled customers and their status.


Stakeholder(s) Principal

Trigger(s) Principal request to view a report about the customers.

Normal Flow

n The principal logs into the system.

n The system validates the principal.

n The principal selects the month he wants to generate the report about.

n The system searches for customers that were enrolled in the chosen month by the principal.

n The system displays a report containing the name, address, phone number, date of registration, requested loan amount and the application status.

Relationship Include: Login Extend: N/A Association: Principal

Alternative Flow





n 5a: The system doesn’t find registered data for the month chosen.

n 5a.1: The system notifies that no customers were found.


4.9

Name Choose Loan product (FR 1.9)

ID Number UC - 9

Type External

Actor(s) Applicant

Brief Description The system displays loan products available to the client and he or she can apply for the preferred loan product according to their preference.


Stakeholder(s) Applicant, Loan processor

Trigger(s) The applicant wants to see what loan product suits him/her independently.

Normal Flow

n The applicant fills in the form with personal information; contact details, employment status, financial status and desired loan amount.

n The system checks all the criteria with provided client’s information.

n The system displays the available loan products.

n The client applies for their preferred loan product.

Relationship Include: N/A Extend: N/A Association: Client

Alternative Flow

n 1a: Applicant does not fill out personal information completely or correctly.

n 1a.1: System informs the Applicant which information he or she did not fill out or filled out incorrectly.

n 1a.2: Applicant fills out the form again.

n 1a.3: System returns client to the step 2 of normal flow of events.

n 2a: System cannot find any loan products that meet client’s requirements.

n 2a.1: System informs client that there is no available loan product.



4.10.

Name Withdraw from an application (FR 1.10)

ID Number UC - 10

Type Internal

Actor(s) Applicant

Brief Description This use case describes how the registered applicants can withdraw from their application.


Stakeholder(s) Applicant

Trigger(s) The registered applicant wants to withdraw from his/her application.

Normal Flow n The applicant logs in to the system.


n The applicant requests a withdrawal form from the system.

n The system displays a warning message about the withdrawal and its consequences, offering applicant with ‘Continue’ or ‘Cancel’.

n The applicant chooses ‘Continue’.

n The system shows the withdrawal form.

n The applicant fills out the form and submits to the system.

n The system validates the form.

n The system requests applicant’s password to authorize withdrawal.

n The applicant enters his or her password.

n The system displaying confirmation on receiving withdrawal request along with a reference number.



Alternative Flow




n 5a: The applicant chooses ‘Cancel’.

n 5a.1: The system terminates.

n 8a: The system detects the form has been filled in incorrectly.

n 8a.1: System validation of the form detail fails due to incorrect entry.

n 8a.s: The System returns to the step 8 of the normal flow.

n 11a: Password confirmation failed.

n 11a.1: The System asks user to enter his or her password again.

n 11a.2: The System returns to step 10 of normal flow.


4.11.

Name Comment Loan processing (FR 1.11)

ID Number UC - 11

Type External

Actor(s) Applicant

Brief Description This use case describes how the applicant can comment on his or her application process.

Important Level Medium

Stakeholder(s) Applicant, Principal, SLP Accountant

Trigger(s) The applicant wants to write a comment on loan process.

Normal Flow

n The applicant logs in to the system.


n The applicant chooses ‘leave a comment’ page.

n The system displays a simple editor.

n The applicant types his or her comment and clicks submit.

n The system shows confirmation message with sent email.

n The system sends confirmation email to the applicant’s registered email address.


Alternative Flow




n 5a: Confirmation message failed

n 5a.1: System redirect the client to his or her profile to check his or her email address

n 5a.2: Clint fixes the error or re-enter his or her email address.

n 5a.3: System returns to the step 4 of the normal flow of events


4.12.

Name Recommend the SLP member office (FR 1.12)

ID Number UC - 12

Type External

Actor(s) Client

Brief Description This use case describes how the client can recommend their loan processing office to their friends.

Important Level Medium

Stakeholder(s) Client

Trigger(s) The client wants to recommends his/her loan processing office to other friends.

Normal Flow

n The client logs in to the system.

n The system validates the client.

n The client requests to recommend SLP member(s)’ office to others.

n The system displays a rating system with the client processing office.

n The client chooses a rating for his or her loan processing office.

n The system asks for applicants’ friend’s email address with the message field.

n The client enters his or her friend’s email address and submits.

n System shows confirmation message and sends the email.

Relationship Include: Login Extend: N/A Association: Client

Alternative Flow




n 5a: Client does not correctly enter his or her friend(s)’ email address.

n 5a.1: System returns to the step of the normal flow of events.


5. Special Issues n The system needs to be delivered within the time frame of at most 12 weeks.

n The system needs to be developed and implemented to SLP system within the budget of one million dollar.

n The system needs to meet all requirements asked by the federal, state government and the council.

n The lender can request the customer to present copies of receipts to explain how they are spending the granted loan.

n The customers should use the money exclusively in Australia; being prohibited its use in international transactions.

n The total loan value that a customer can have from SLP must be less than two million dollars.

n In the case of customer(s)’ death during loan process, his or her application can be taken over by anybody who is assigned in his or her will, or by judge.

n When customer request more than a million dollar he or she needs to have one financial cooperation and current employer of the customer to prove his or her financial status.

n After the loan approval by a lender, the lender cannot cancel the payment unless by a judge order or customer’s withdrawal request.

n Any bribery in any stage of the loan process to speed up the process is illegal and if discovered, customer's loan will be cancelled and will be fined accordingly. In addition any office member(s) involved in such situation will be suspended and face the court.

n In any stage of the process, if a lender, member, or SLP accountant finds out that the applicant is part of any gang or illegal activity, they can cancel the application, or approved loan immediately and report to police.

n The in-person or over-the-phone process still needs to be maintained for customer(s) with disabilities or special features for those with disabilities within the system.

n SIT consulting should be able to provide on-going training of the management system to the SLP members and accountants.

n All documents and data should not be used for personal purposes or cannot be accessed from unidentified IP address or without successful log in into the system.


6. Use Case Diagram UseCase Diagram0 2012/10/28 powered by Astah

SLPuc

PrincipalApply for membership with SLP

SLP Accountant

Maintain membership with SLP

Client

Enquire application status

Loan Processor

Maintain loan application

View the application status

Authorize application

Applicant

Send Messages

Generate customer's report

Choose loan product

Withdraw from an application

Comment loan processing

Reccomend the SLP member office

Login

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>


7. Activity Diagrams

Activity Diagram 1.1 2012/10/28 powered by Astah

Activity Diagram 1.1act

Membership Application

Fills Out Application Form

Checks Applicant's Requirement

[Invalid Input]

[Valid Input]

Accountant Checks Application

[Reject]

Displays Membership Detail

[Check Validation]

[Approve Application]

[Approve]




Enter Username & Passwod

Login

[Valid]

[Invalid]

Create Read Update Delete

[Check Validation]

[Check Validation]

[Check Validation]

[Invalid] [Invalid][Invalid]

[Valid] [Valid] [Valid]

Send message to SLP Accountant about Change

Displays Updated Information

[Check Validation]

[Approve][Disapprove]





[Invalid]

Login

[Valid]

Enquire Application Status

Enter Application Number

[Check Validation][Invalid]

Display Application Status

[Valid]

[Check Validation]




Enter Username & Password

Log In

[Check Validation]

[Valid]

[Invalid]

Create Read Update Delete

[Check Validation]

[Check Validation]

[Check Validation]

[Invalid] [Invalid][Invalid]

Send message to Loan Processor about Change

Displays Updated Information

[Check Validation]

[Valid] [Valid] [Valid]

[Approve][Disapprove]




Enter Applicaiton Number

Display Application

[Application Number Invalid]

[Application Number Valid]


[Invalid]

Login

[Valid]

[Check Validation]

[Check Validation]




Submit Applicaiton

Notify System

Open Applicaiton

Display Application

Applicaiton Validation

Enter Reason for Decline

Send Application

Notify that Application was Declined with Reason

[Application Approved]

[Application Rejected]


[Invalid]

Login

[Valid][Check Validation]

[Application Validation]





[Invalid]

Request to send a message

[Valid]

[Check Validation]

Define Receiver & Enter Message

[Check registered users]

[Invalid]

Send Message

[Valid]

Open message editor

[message fails]

Notify user that message was sent

[Message Successful]





[Invalid]

Request to generate report

[Valid]

[Check Validation]

Define month parameter

[Check data for the month][No data found]

Display customers report

[Data found]




Fill Out the Form

Check Criteria


[Valid]

Displays Messgae

Displays Available Loan Products

[No Matching Product]

[Matching Product]

Ask If User Want To Apply

Apply for Memberhip

[No][Yes]


Activity Diagram 1.10 2012/10/28 powered by Astah Activity Diagram 1.10act


Form being requested

Warning message display with options

System display withdrawal form

System returns to home page

Applicant fills and submits the form

Applicant enters password for authorization

Confirmation and referenced number displayed


[Valid]

[Continue][Cancel]

[Validate password]

[Valid]

[Invalid]

[Validate form]

[Valid]

[Invalid]

Log In




Comment Loan Processing

Displays Text Editor

Type the Comment

Submit Comment

Send Confirmation Mail

Notify user that message was sent

[Delivering Mail Successful]

Opens User's Profile

Check Email Address

Save Changes

[Delivering Mail Failed]


Login

[Valid]

[Invalid]




Request to Offer Member to others

Displays Rating System

Select Desired Rating

Enter Email Address

Submit

[Check Validation]

[Valid]

Sends Mail and Shows Confirmation Message

[Invalid]


Login

[Valid]

[Invalid]


8.Class Diagram

SLP Accountant 2012/10/28 powered by Astah SLPpkg

+ login() : void

- password : String- username : String

User

- financialOrganization : int- interestRate : double- start : date- status : String- expiration : date- amount : double

LoanProduct

+ receiveMessages() : void+ sendMessage() : void

- from : User- to : User- date : Date- text : String

Message

+ calculateLoan() : double

CustomerReport

- status : String

Application

1..*

0..*

+ recommendToPublic() : void

- member : Principal

RecomendationMember

+ payComission() : void+ receiveComission() : void

- percentage : double

Comission

+ applyAsMember() : void+ authorizeApplication() : void

Principal

+ withdrawApplication() : void+ maintainApplication() : void+ enquireApplicationStatus() : void

- status : String

Applicant

+ maintainMembership() : void

SLPAccountant

+ triggerRecommendation() : void

- creditBalace : double

Client

- staffId : int

LoanProcessor

0..*

1..*

+ triggerComission() : void

- organizationName : String

Lender

0..*

1

pays

0..1

0..*

1..*1

0..*

1+ recommendProduct() : void

ProductRecomendation

0..*

1

1

0..*

11

1

0..*

1

1

0..1

0..*paid to

0..1

0..*

paid to

0..1

0..*

paid to

0..*

1

0..*

1

slp management system project - wordpress.com...slp accountant sydney loan portal accountant who...

Documents