Lending System free essay sample

In overview of this SRS, the system we made aims to provide a client a satisfaction through his business without any failure to what he is working and to get him more gain from his business because he will not anymore needing an accountant just to breakdown his savings and expenses. This SRS was made through the IEEE standard, IEEE Recommended Practice for Software Requirements Specification. 1. 4 DEFINITION, ACRONYM AND ABREVIATION CIENT a user of the services | COSTUMER a person or organization to whom goods or services are provided and sold. INVENTORY a record of a businesss current assets, including property owned, merchandise on hand, and the value of work in progress and work completed but not sold | USER somebody or something that uses something (computer users)| SRS Software Requirement Specification IEEE Institute of Electrical and Electronic Engineering 1. 5 DOCUMENT CONVENTIONS 1. 6 REFERENCES AND ACKOWLEDGMENTS REFERENCE * IEEE Recommended SRS. pdf 1 OVERALL DESCRIPTION 2. 1 PRODUCT PERSPECTIVE Quick Books-A 24/7 Accountant of A Lending Company is a simple system that will help the lending companies operation become easily, precise and satisfaction. This product is a new system, we make few tables connecting to each other in order the user to manage easily the system. Figure 2. 1a: Use case context diagram. Interview Client Credit Admin. Loan Officer Process Loan Application Verify Collateral Ratio Analysis Branch Mgr. Process Payments 2. 2 PRODUCT FUNCTIONALITY * Daily transaction of costumer * For payments / billing * Manage inventory * Costumer credit Balance Collateral gt;=150% of loan request Valid Details Invalid Details Credit Client Account Sanction Loan Requested Calculate Financial Statement Produce Report Deny Loan Check Collateral Input Loan Application Detail Display Application Detail Form Input forms Fill application form Unfavorable financial statement For payments Produce Information Calculate the interest Check Balance Favorable financial statement Collateral lt; 150% of loan request FIGURE 2. 2. a Data Flow Diagram of the system showing how function relate to each other. 2. 3 USERS AND CHARACTERISTICS A user is anything with behavior including the system under discussion when it calls upon other systems to provide it with services. Users are not only roles played by people, but also organizations, software and machines. Users are of two types: primary and supporting users. Primary Users These are users whose roles are fulfilled through using the services of the system under discussion. Considering the case for the loan assessment system, the primary users are the loan officers since they do a lot as far as loan assessment is concerned. Primary users are also the same as main users. In the new loan assessment system, the main user is the credit officer. The loan assessment system also includes other interested parties. Manager 2. Credit administrator 3. Supervisor 4. Accountant Supporting Users These are users that provide a service to the system under discussion. Supporting users are identified in order to clarify the external interfaces and protocols. 2. 4 OPERATING ENVIRONMENT As indicated earlier on, implementation of the system was done using MYSQL, VB. NET, and HTML. MYSQL was selected because it is one of the freely available software suitable for creating, modifying and deleting tables. It also offers fast access when accessing a database through the web interface. On the other hand, HTML was for fine-tuning areas of the interface that could not be handled by other applications like web authorizing software. The purpose of choosing and using these programming languages was to achieve the general objective. 2. 5 DESIGN AND IMPLEMENTATION CONSTRAINT 1. Most of the members were busy and did not find sufficient time to spare for the study, however we the researcher kept checking on them till some of the members responses. 2. The lending industry is very secretive in nature and some information was kept secret from us the researcher. 3. Due to financial constraints, the study was limited. 4. Since we are required to use the VB. NET, we have no choice to select other languages that we are most familiar that’s why we as a group before starting in making our system was then first study how to use or the syntax in coding such language. 2. 6 USER DOCUMENTATION 2. 7 ASSUMPTION AND DEPENDENCIES 3 SPECIFIC REQUIREMENTS 3. 1 EXTERNAL INTERFACE REQUIREMENTS 3. 1. 1 User Interface Screen for logging in the system The homepage provides options for the user to login. These users may be loan officers or managers requiring information about an existing client or enter information about the new client. Screen for the Main Menu of the system The screen below indicates the option available after logging in. It provides reports about the number of clients registered on a daily basis. On this screen, there is no option to update or delete but instead you view reports, print if you want and logout. Screen for Payments This screen provides the user to transact payments. All he has to do is just fill in the customer id or the name of the debtor and it will automatically appear on the screen. Fill in also the amount he has to pay and it will also automatically calculate the change if there is, and the record of the debtor will also be updated instantly. Screen for Re-Loan This screen provides the user the information of a debtor. It shows the current balance and other information that make the debtor favorable to the management. Screen for searching The screen below provides the users to search names that are in the list or the database. It provides some information of the debtor and transacts business from it. It also gives an option to edit names, view an account and exit. New Customer Registration Screen Figure below shows screen for new customer, it provides the customer to fill in the information needed by the company in order for him/her to register and transact loan. The screen allows for any deletion if in case the user got mistakes while his filling in the information box. Borrowers Information Screen This screen has a similarity to the new customer registration screen. It provides the user to view all the information or the transaction of the debtor he had made in the company, except the checking of balance. 3. 1. 2. HARDWARE INTERFACES 3. 1. 3. SOFTWARE INTERFACES 3. 1. 4. COMMUNICATIONS INTERFACES The client and the loan officers will be communicating in this prepared system. This system was designed for loan process, updating user, and checking balance. Studying first about this system will make the user more comfortable from using it. 3. 2. FUNCTIONAL REQUIREMENTS 3. 2. 1. Loan Process Loan Process Client Brief Description The Client will process a loan transaction. Initial Step-by-Step Description Before the Client transact or process his/her loan he/she must first fill in the application form issued by the loan officer. If the application is unacceptable the transaction will be invalid, else if the application granted, the following step will be taken: 1. The loan officer will check if the collateral is greater or equal to 150% of loan request. 2. If it is greater or equal to 150% of loan request the loan officer will calculate the financial statement of the client. 3. 3. 2. 2. OTHER USE CASES 3. 3. DETAILED NON-FUNCTIONAL REQUIREMENT 3. 3. 1. LOGICAL STRUCTURE OF THE DATA 3. 3. 2. DESIGN CONSTRAINTS * Short timeline for this project 4 OTHER NON-FUNCTIONAL REQUIREMENTS 4. 1. PERFORMANCE REQUIREMENTS * The system can run with multiple threads. * The system can accept several users to be stored. * Easy to operate. 4. 2. SAFET Y AND SECURITY REQUIREMENTS Password are security features. Password are important to keeping your system information safe. Picking a good password and remembering it is easy if you use a few tricks. If you dont use a system for your password, youll end up writing them down somewhere which is unsafe. Writing Down Password: Passwords, often get written on the very things they are supposed to protect. Some folks write their Password on their debit or credit card. Of course, this gives the holder of that card a free pass to your account. If the card is lost or stolen, a dishonest person will appreciate that they have the Password conveniently written right on the card. Dont do it. Remembering Passwords: There are a variety of tricks you can use to remember Passwords. Each has its advantages and disadvantages. The rest of this page highlights a few of the methods you can use along with the pros and cons. The Word Method: One way to create and remember a Password. Think of the numbers and letters on your telephone. Then think about how you dial-by-name in a companys phone system. A disadvantage of password is that automated hacking programs can use words from the dictionary in a brute force attack. However, most systems will lock you out after a few unsuccessful attempts. The Date Method: Another way to create and remember a Password is to create it from significant dates. For example, if your birthday is November 15th, 1946, you can create a Password derived from your birthday. You might use 1115 (for the 11th month November and 15th day). You might also try 1546. The disadvantage of this method is that somebody who knows you may be able to guess your Password with their knowledge of your personal life. For best results, mix up the numbers: use part of a date with part of your address or phone number, etc. The Longer the Better: You should use the longest possible Password. Due to the miracles of math, there are more possible combinations of numbers in a longer series vs a shorter series. If youre allowed to use more than 4 digits, do so. 4. 3. SOFTWARE QUALITY ATTRIBUTES RELIABILITY * The system shall save the data stored in the user data structures * The system shall save the data of an active user whenever a new user is created. * The system shall save the data of an active user whenever a new account is created. * The system shall save the data of an active user whenever a user password is changed. The system shall reboot itself automatically if there is a power failure and restore all saved data to the user accounts. AVAILABILITY * The system shall be available and running in a stable state at all times * The Loan Officer Software shall be available at all times. SECURITY * The system shall require a password to allow a user to logon. * The system shall require the user to know their own password and account number. MAINTAINABILTIY The source code shall be available to the developers. 5 OTHER REQUIREMENTS 6 APPENDIX-A SYSTEM LOG 7 APPENDIX-B GROUP LOG 8 INDEX