FINANCE MANAGEMENT SYSTEM

DONE AT

CCSIT, PUDUKAD
Submitted in partial fulfillment of the requirement for the award of degree of

MASTER OF COMPUTER APPLICATIONS Project Report

Submitted by

VIDYA RAVINDRAN
Reg.No:CPAIMCA025

CENTRE FOR COMPUTER SCIENCE AND INFORMATION TECHNOLOGY UNIVERSITY OF CALICUT PUDUKAD, THRISSUR KERALA

UNIVERSITY OF CALICUT

CENTRE FOR COMPUTER SCIENCE AND INFORMATION TECHNOLOGY

PUDUKAD, THRISSUR

CERTIFICATE
This is to certify that the project entitled FINANCE MANAGEMENT SYSTEM is a bonafide record of the project work done by Miss. VIDYA RAVINDRAN(CPAIMCA025) in partial fulfillment of the requirements for the award of the MASTER OF COMPUTER APPLICATIONS during the fifth semester. Submitted for the university examination held on

Internal Examiner Head of the department

External

DECLARATION
I, VIDYA RAVINDRAN(Reg No:CPAIMCA025) hereby declare that the entire work embodied in this dissertation has been carried out by me and no part of it has been submitted for any degree or diploma of any institution previously .This project work is FINANCE MANAGEMENT SYSTEM submitted in Centre For Computer Science And Information Technology ,Pudukad is a record of original work done by me under the

supervision and guidance of Mrs.DIVYA, lecturer in CCSIT Pudukad.

VIDYA RAVINDRAN

Place Date

: :

ACKNOWLEDGEMENT
Apart from the efforts of me, the success of this project depends largely on the encouragement and guidelines of many others. I would like to take this opportunity to express my sincere gratitude to all people who make me to complete this project successfully through their timely guidance, help and support.

.It is great pleasure for me to acknowledge the assistance and contributions to Miss. Dhanya M.V, Associate coordinator, CCSIT, Pudukad for her prompt and timely help in the official clearances and valuable suggestions during the development of this project. I am highly grateful to my project guide Mrs.DIVYA ,Lecturer of CCSIT ,Pudukkad who had given valuable suggestions and encouragements for the successful completion of the project.

Apart from those mentioned here, I have to thank many others who have directly or indirectly helped me in the completion of this project. Without their cooperation this project would not have been possible. Finally, yet importantly, I express my heartiest gratitude to Almighty god, my Parents, friends for their love and blessings to complete the project successfully. Sincerely, VIDYA RAVINDRAN

SYNOPSIS
The project Finance Management System aims the computerization of existing manual system and fulfills the needs of users. This is used to manage all transactions in systematic way. High speed, accuracy and security are main objectives of this project. This project consists of various functions of the financing system. This project involves various operations like account open, deposit, withdrawal, loan issuing, loan closing etc. This system is generally classified into three modules:  Initial Setup  Transaction  Gold loan The description of each module is given below: Initial setup module contains account open entry and interest setting operations. Transaction module contains deposit entry and withdrawal entry operations. Gold loan module contains gold loan lending, gold loan repayment and gold loan closing operations. The project Finance Management System is designed and developed in Windows environment by using Visual Basic 6.0 as front end and Oracle as back end.

. .

CONTENTS
1.Introduction 1.1 Project profile 2.System analysis 2.1 Existing system 2.23 Proposed system 2.3 Need for computerization 2.4 Feasibility study 3.System specification 3.1Software specification 3.2Hardware specification 4.System design 4.1 Table design 4.2.EER Diagram 4.3Datafolwdiagram 4.4 Class diagram 4.5Usecase diagram 4.6Sequence Diagram 4.7 Activity diagram

5.Coding 5.1 Features of the language 5.2 Functional description 6.Testing 6.1 Introduction to testing 6.2 Levels of testing 7.Implementation 8.Future enhancement 9.Conclusion Appendix Bibliography

1.INTRODUCTION
1.1 PROJECT PROFILE
.This all help the management to maintain details regarding the software,hardware that

have,been installed in the system and to helped to track. When the need arises the management may know the exact configuration of the system.This software will give support to manage systems in a firm easily by an administrator. The project Finance Management System aims the computerization of existing manual system and fulfills the needs of users. This is used to manage all transactions in systematic way. High speed, accuracy and security are main objectives of this project. This project consists of various functions of the financing system. This project involves various operations like account open, deposit, withdrawal, loan issuing, loan closing etc. This project contains three modules as:  Initial Setup  Transaction  Gold loan The Initial Setup module has two operations. They are: ACCOUNT OPEN ENTRY INTEREST SETTING ACCOUNT OPEN ENTRY: Here a new account is opens for a customer. Customer details are stores into acc_open_entry table and issues an account number to the customer. INTEREST SETTING: Here an interest rate is set for each account type. The details are stored into inst_set table.

The transaction module has two operations. They are: deposit entry withdrawal entry DEPOSIT ENTRY: This is use for depositing amount into an account. We enters account no, deposit date, deposit amount etc for this purpose. The details are stores in the deposit_entry table. WITHDRAWAL ENTRY: This is use for withdrawing amount from an account. Account no, withdrawal date, withdrawal amount etc are enters into the withdraw_entry table. The gold loan module has three operations. They are: gold loan lending gold loan repayment gold loan closing GOLD LOAN LENDING: This is the process of issuing gold loan to a customer. Account no, loan no, loan from date, loan to date, item details etc are enters into the gold_loan_lend and gold_loan_item tables. GOLD LOAN REPAYMENT: This is the process of repaying the gold loan. Loan no, repayment date, repayment amount etc are stores into the gold_loan_close table. The project Finance Management System is designed and developed in Windows environment by using Visual Basic 6.0 as front end and Oracle as back end

2.SYSTEM ANALYSIS

System Analysis is the detailed study of the various operations performed by the system and their relationships within and outside the system. Analysis is the process of breaking something into its parts so that the whole may be understood. System analysis is concerned with becoming aware of the problem, identifying the relevant and most decisional variables, analyzing and synthesizing the various factors and determining an optimal or at least a satisfactory solution. During this a problem is identified, alternate system solutions are studied and recommendations are made about committing the resources used to design the system System Analysis is the process of gathering and interpreting facts and diagnosing problems and using the information to recommend improvements on the system. System Analysis is a problem solving activity that requires intensive communication between the system users and the system developers. System Analysis or Study is an important phase of any system development process. The system is studied to the minute, detailed and analyzed. System Analyst plays the role of an interrogator and dwell deep into the working of the present system. The system is viewed as a whole and the inputs to the system is identified. A detailed study of this process must be made by various techniques like interviews, questionnaires, etc. The data collected from various sources must scrutinize to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the Existing System. Now the existing system is subject to close study and problem areas are identified. The designer functions as a problem solver and tries to sort out the difficulties that the enterprise faces.

Here in this project, a detailed study of the existing system is carried along with all the steps in the system analysis. An idea of creating a better project was carried out and the next steps were followed.

2.1 EXISTINGSYSTEM
Existing system refers to the system that is being follow till now. Presently all the work are done manually, where data are stored in paper files.. They handle many files regarding the detailes of a customers. The situation is very difficult to maintain . The manual process take a lot of time and there is a chance of error occurrence. A lot of complexity is involved in various operations like search, calculation of interest etc when the number of customer and loans are increased Maintain all files is space and time consuming. For getting details about the systems we want search different departments .Movement management is process. also a time consuming

LIMITATIONS OF EXISTING SYSTEM

Lack of accuracy. Complexity of calculations. Needs a huge amount of storage space. Human effort is high. Errors may occur because of manual calculation. Data security is not fully guarantee .

2.2 PROPOSED SYSTEM

The proposed system should be capable of overcoming the problems in the present system. The proposed system is the computerized version of existing system. It should satisfy the needs of the end user.All the requirement should be considered while developing the new system. The new system should be easy to incorporate changes.The user should be able to make changes without any difficulty at any time.All the features are available online this will help the admin to check it when he is outside the organization. The system is easy and user friendly.We can check about the system very easily. This system involves various financial operations like account opening, deposit and withdrawal entry, gold loan lending, gold loan repayment and closing.We can easily search the details of customers.When a new customer is introduced, his details are stored efficiently and accurately .

ADVANTAGES OF PROPOSED SYSTEM Response time can be greatly improved. Complex calculations can done more easily and accurately. Reduce errors and speed up the processing. Less storage space is required. Data entry and retrieval is more easy. Less human effort. Ensure data integrity and minimize data redundancy

2.3 NEED FOR COMPUTERISATION

The existing system is time consuming. Adding and deleting details according to the changes is very difficult. The overall maintenance by the administrator is a difficult job. Giving support request to the venders also need many paper works. It is difficult to manage all the activities. Workload is very high for the officials. They cannot get any idea about the system if they are outside the organization. It is very time consuming one to keep various records and to search various information. It will provide accuracy. It will avoid high degree of human errors.It will speedup your activities. Time consuming system.

2.4 FEASIBILITY STUDY

A feasibility analysis usually involves a thorough assessment of the operational(need), financial and technical aspects of a proposal. Feasibility study is the test of the system proposal made to identify whether the user needs may be satisfied. using the current software and hardware technologies, whether the system will be cost effective from a business point of view and whether it can be developed with the given budgetary constraints. A feasibility study should be relatively cheap and done at the earliest possible time. Depending on the study, the decision is made whether to go ahead with a more detailed analysis. When a new project is proposed, it normally goes through feasibility assessment. Feasibility study is carried out to determine whether the proposed system is possible to develop with available resources and what should be the cost consideration. Facts considered in the feasibility analysis were. y Technical Feasibility

y y

Economic Feasibility Behavioral Feasibility

2.4.1 Technical Feasibility

Technical Feasibility deals with the hardware as well as software requirements. Technology is not a constraint to type system development. We have to find out whether the necessary technology, the proposed equipments have the capacity to hold the data, which is used in the project, should be checked to carryout this technical feasibility. The technical feasibility issues usually raised during the feasibility stage of investigation includes these y This software is running in windows 2000 Operating System, which can be easily installed. y y The hardware required is Pentium based server. The system can be expanded.

2.4.2 Economical Feasibility

This feasibility study present tangible and intangible benefits from the prefect by comparing the development and operational cost. The technique of cost benefit analysis is often used as a basis for assessing economic feasibility. This system needs some more initial investment than the existing system, but it can be justifiable that it will improve quality of service. Thus feasibility study should center along the following points: Improvement resulting over the existing method in terms of accuracy, timeliness. Cost comparison

Estimate on the life expectancy of the hardware Overall objective Our project is economically feasible. It does not require much cost to be involved in the overall process. The overall objectives are in easing out the requirement processes.

2.4.3 Operational Feasibility

This analysis involves how it will work when it is installed and the assessment of political and managerial environment in which it is implemented. People are inherently resistant to change and computers have been known to facilitate change. The new proposed system is very much useful to the useful to the users and there for it will accept broad audience from around the world.

3. SYSTEM SPECIFICATION
The system specification describes the specifies the requirements for a system and the methods to be used to ensure that each requirement has been met. The hardware and software should be configured based on the system specification. The proper configuaration of the complete system optimizes the performance of the system.

3.1 SOFTWARE REQUIREMENTS

In order to implement a new system,the choice of a processor with maximum possible speed is made.There should be sufficient memory to store data and software tools for efficient processing. Operating System : Windows 2000/XP/other higher Windows versions Front-End Back-End : : MICROSOFT VISUAL BASIC 6.0 MS SQL SERVER 2005

3.2HARDWARE SPECIFICATION
In order to implement a new system the choice of a processor with maximum possible speed is made. There should be sufficient memory to store data and software tools for efficient processing. The selection of hardware is very important in the existence and proper working of any software. When selecting hardware, the size and requirements are also important. Processor Processor Speed : : : Primary memory(cache memory) : Pentium III or above Minimum 1.0 GHz,Recommended: 2.0 GHz or faster Minimum 512MB.Recommended

: Secondary memory Pheripherals Hard Disk Capacity CD ROM Drive Monitor : :

2.0 GB or More Minimum 5 GB or above Mouse,Keyboard

: 20GB or Above : 52 X RW : SVGA Color

4.SYSTEM DESIGN

DEFINITION The most creative and challenging face of the system development is System Design. It provides the understanding and procedural details necessary for implementing the system recommended in the feasibility study. Design goes through the logical and physical stages of development. In designing a new system, the system analyst must have a clear understanding of the objectives, which the design is aiming to fulfill. The first step is to determine how the output is to be produced and in what format. Second, input data and master files have to be designed to meet the requirements of the proposed output. The operational phases are handled through program construction and testing. Design of a system can be defined as a process of applying various techniques and principles for the purpose of defining a device, a process or a system in sufficient detail to permit its physical realization. Thus system design is a solution to how to approach to the creation of a new system. Thus important phase provides the understanding and the procedural details necessary for implementing the system recommended in the feasibility study. The design step provides a data design, architectural design, and a procedural design .

4.1 DATABASE DESIGN

Table design refers to outside the logical data structures are to be physically stored in the storage device. Table design also deals with the design of physical database. A key field determines how the access Is to be implemented. Suitable key fields are identified various tables and are coded approximately. The type, width and size of the fields are identified The designing of the tables in

the database is done according to the rules specified for databases . In the proposed project, 8 tables are used. Insertion and retrieval of values are easy by designing the database in this way.

DATABASE TABLES ACCOUNT OPEN ENTRY TABLE

FIELD ACC_NO ACC_NAME ACC_DATE ACC_BAL CUST_NAME AGE OCCUPATION PHONE H_NAME PLACE POST PIN TYPE NUMBER VARCHAR2(15) VARCHAR2(25) NUMBER VARCHAR2(20) NUMBER VARCHAR2(15) NUMBER VARCHAR2(20) VARCHAR2(20) VARCHAR2(20) NUMBER CONSTRAINT PRIMARY KEY

INTEREST SET TABLE

FIELD ACC_NAME INST_RATE TYPE VARCHAR2(20) NUMBER CONSTRAINT

DEPOSIT ENTRY TABLE FIELD ACC_NO DEPT_NO DEPT_DATE DEPT_AMT TOT_BAL TYPE NUMBER NUMBER VARCHAR2(25) NUMBER NUMBER CONSTRAINT FOREIGN KEY PRIMARY KEY

WITHDRAW ENTRY TABLE FIELD ACC_NO WITHDRAW_NO WITHDRAW_DATE WITHDRAW_AMT CUR_BAL TYPE NUMBER NUMBER VARCHAR2(25) NUMBER NUMBER CONSTRAINT FOREIGN KEY PRIMARY KEY

GOLD LOAN LEND TABLE FIELD LOAN_NO ACC_NO LOAN_FROM_DATE LOAN_TO_DATE TOT_WEIGHT TOT_AMT TYPE NUMBER NUMBER VARCHAR2(25) VARCHAR2(25) NUMBER NUMBER CONSTRAINT PRIMARY KEY FOREIGN KEY

GOLD LOAN ITEM TABLE FIELD LOAN_NO ITEM_NAME ITEM_COUNT GRAM TYPE NUMBER VARCHAR2(15) NUMBER NUMBER CONSTRAINT FOREIGN KEY

GOLD LOAN REPAY TABLE FIELD LOAN_NO LOAN_REPAY_DATE REPAY_AMT INST_AMT OTHER_AMT TOT_AMT BAL_AMT_REPAY TYPE NUMBER VARCHAR2(25) NUMBER NUMBER NUMBER NUMBER NUMBER CONSTRAINT FOREIGN KEY

GOLD LOAN CLOSE TABLE

FIELD LOAN_NO LOAN_CLOSE_DATE CLOSE_AMT INST_AMT OTHER_AMT TYPE NUMBER VARCHAR2(25) NUMBER NUMBER NUMBER CONSTRAINT FOREIGN KEY

4.2 ER DIAGRAM
An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes. Also Known As: ER Diagram, E-R Diagram, entity-relationship model

ER DIAGRAM

CUST_ NAME

AGE

OCCUPATION H_NAME DEPT_NO

WITHDRA W_AMT
WITHDRA W_NO ACC_ NO WITHDRA W_DATE

ACC_B AL ACC_NA ME ACC_N O CUR_BAL ACC_D ATE

DEPT_ AMT DEPT_ DATE

PLACE ACC_NO PHONE

N
WITHDRAW_ENTRY

FOR_ WITHD RAW

ACC_OPEN_ENTRY

N
FOR_D EPOSIT

DEPT_ENTRY

FOR_ LOAN
LOAN_ NO ITEM_NAME LOAN_ NO ACC_ NO TOT_WEI GHT LOAN_AMT

INST_AMT

1 1
GOLD_LOAN_LEND

TOT_AMT

LOAN_ NO

TOT_ AMT

N
GOLD_LOAN_ITEM
FOR_ ITEM

1
FOR_ CLOSE

1
LOAN_FROM _DATE

GOLD_LOAN_CLOSE

1
FOR_ REPAY MENT

LOAN_TO_ DATE

LOAN_FRO M_DATE

LOAN_CLO SE_DATE

ITEM_COU NT

GRAM

LOAN_ NO

N
GOLD_LOAN_REPAYM ENT

REPAY_AMT

LOAN_TO _DATE

REPAY_DATE

TOT_AMT

4.3 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. DFDs can also be used for the visualization of data processing (structured design). There are various symbols used in a DFD. Bubbles represent the processes. Named arrows indicate the data flow. External entities are represented by rectangles and are outside the system such as vendors or customers with whom the system interacts. They either supply or consume data. Entities supplying data are known as sources and those that consume data are called sinks. Data are stored in a data store by a process in the system. Each component in a DFD is labeled with a descriptive name. Process names are further identified with a number. DFDs can be hierarchically organized, which help in partitioning and analyzing large systems. As a first step, one DFD can depict an entire system, which gives the system overview. It is called Context Diagram of level 0 DFD. The Context diagram can be further expanded. The successive expansion of a DFD from the context diagram to those giving more details is known as leveling of DFD. Thus a top down approach is used, starting with an overview and then working out the details. The main merit of DFD is that it can provide an overview of what data a system would process, what transformation of data are done, what files are used, and where the results flow.

DATA FLOW DIAGRAM

Context diagram (Level0)

level1

level2

4.4 Class Diagram

In the Unified Modeling Language (UML), a class diagram is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, and the relationships between the classes. It represents the static view of an application. Class diagram is not only used for visualizing, describing and documenting different aspects of a system but also for constructing executable code of the software application. The class diagrams are widely used in the modelling of object oriented systems because they are the only UML diagrams which can be mapped directly with object oriented languages. The class diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It is also known as a structural diagram.

WORKS_FOR PERSON

*
ORGANIZATION UNIT

0..1

SUBDIVISION

+ NAME: STRING

0..1

MANAGER

*
BRANCH + BRANCH_NO: INT + ADDRESS:STRING ACCOUNT EMPLOYEE CUSTOMER + ADDRESS: STRING # ACC NO: INT + ACC NAME: STRING + CUST NAME: STRING + ACC BAL: INT=0 +WITHDARW() +DEPOSIT() #UPDATED BAL() CLERK GOLD LOAN + ITEM_NAME: STRING + ITEM_COUNT: INT + GRAM: INT
+ GOLD LOAN LEND() + REPAYMENT() + CLOSE()

# EMP ID: INT

0..1

1..2

ACC HOLDER TRANSACTION ACCOUNT TYPE + ACC NAME: STRING + INTEREST RATE: INT + PERIOD: INT + DATE: DATE

4.5 Use Case Diagram

A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases. A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted. Use Case diagrams are formally included in two modeling languages defined by the OMG: the Unified Modeling Language (UML) and the Systems Modeling Language (SysML). In RTPMS modeling Usecase diagram shows the interactions of Administrator, Manager and User with the system separately and very clearly. users helps to understand the requirements. . The interaction between the system and its

ACCOUNT OPEN ENTRY

INTEREST SETTING

DEPOSIT ENTRY

CLERK

WITHDRAWAL ENTRY

GOLD LOAN LENDING

CUSTOMER

GOLD LOAN OFFICER

GOLD LOAN REPAYMENT

GOLD LOAN CLOSING

4.6 Sequence Diagram

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event scenarios, and timing diagrams. Sequence diagrams demonstrate the behavior of objects in a use case by describing the objects and the messages they pass. Sequence diagrams generally show the sequence of events that occur. In FMS sequence diagrams specifies the different events that occur during the login of each user. These sequence diagrams describes the events that occur from the login to logout of each user according to their status whether he is an employee, or customer. Each sequence diagram has its own purpose.

login

Deposit

withdrawal

Gold loan

Account

customer

Account

Deposit Commit

withdrawal
Commit

Gold loan Commit time

invalid login

4.7 Activity Diagram

Activity diagram is another important diagram in UML to describe dynamic aspects of the system. Activity diagram is basically a flow chart to represent the flow form one activity to another activity. The activity can be described as an operation of the system. So the control flow is drawn from one operation to another. This flow can be sequential, branched or concurrent. Activity diagrams deals with all type of flow control by using different elements like fork, join.etc. It does not show any message flow from one activity to another. Activity diagram is some time considered as the flow chart. Although the diagrams looks like a flow chart but it is not. It shows different flow like parallel, branched, concurrent and single.
start
Customer approaches office

Employee login No valid login

yes
Choice menu

Account open entry

Deposit

Withdrawal v

Gold loan

Proceed transaction

stop

5.CODING
Visual Basic 6.0 (Front End ) Like the BASIC programming language, Visual Basic was designed to be easily learned and used by beginner programmers. The language not only allows programmers to create simple GUI applications, but can also develop complex applications. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions of those components, and writing additional lines of code for more functionality. Since default attributes and actions are defined for the components, a simple program can be created without the programmer having to write many lines of code. Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue. Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have attributes and event handlers associated with them. Default values are provided when the control is created, but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application Alternatively, a Visual Basic component can have no user interface, and instead provide ActiveX objects to other programs via Component Object Model (COM). This allows for server-side processing or an add-in module. In addition to catching errors on the fly, Visual Basic also partially compiles the code as it is entered. When you are ready to run and test your application, there is only a brief delay to finish compiling. If the compiler finds an error, it is highlighted in your code. You can fix the error and continue compiling without having to start over. Because of the interactive nature of Visual Basic, you'll find yourself running your application frequently as you develop it. This way you can test the effects of your code as you work rather than waiting to compile later.

ABOUT THE DATABASE:

ABOUT SQL SQL is a relational database management system.A relational database management system stores data in the form of multiple related tables.It consist of user databases created by administrators for storing and retrieving data used by database client and system database that store the information needed for SQL Server , enabling it to actual function. SQL*Plus is an Oracle command-line utility program that can run SQL and PL/SQL commands interactively or from a script. SQL*Plus operates as a relatively simple tool with a basic command-line interface. Programmers and DBAs commonly use it as the default available fundamental interface in almost any Oracle software installation. The Oracle Database (commonly referred to as Oracle RDBMS or simply as Oracle) is an object relational database management system (ORDBMS)[ produced and marketed by Oracle Corporation. SQL is a database access, nonprocedural language. Users describe in SQL what they want done, and the SQL language compiler automatically generates a procedure to navigate the database and perform the desired task. IBM Research developed and defined SQL, and ANSI/ISO has refined SQL as the standard language for relational database management systems.The minimal conformance level for SQL99 is known as Core. Core SQL-99 is a superset of SQL-92 Entry Level specification. Oracle9i is broadly compatible with the SQL-99 Core specification. Oracle SQL includes many extensions to the ANSI/ISO standard SQL language, and Oracle tools and applications provide additional statements. The Oracle tools SQL*Plus and Oracle Enterprise Manager let you run any ANSI/ISO standard SQL statement against an Oracle database, as well as additional statements or functions that are available for those tools. Oracle SQLJ lets applications programmers embed static SQL operations in Java code in a way that is compatible with the Java design philosophy. A SQLJ program is a Java program

containing embedded static SQL statements that comply with the ANSI-standard SQLJ Language Reference syntax. Although some Oracle tools and applications simplify or mask SQL use, all database operations are performed using SQL. Any other data access method circumvents the security built into Oracle and potentially compromise data security and integrity

6.TESTING

6.1 INTRODUCTION TO TESTING

The test cases generated for and executed on Finance Management System. A real-time system is one in which the correctness of the computations not only depends upon the logical correctness of the computation but also upon the time at which the result is produced. If the timing constraints of the system are not met, system failure is said to have occurred. Test cases are evaluated independent of one another, having no effect on the evaluation of the other test cases. Software testing can also be stated as the process of validating and verifying that a software program/application/product: 1. meets the business and technical requirements that guided its design and development; 2. works as expected; and 3. can be implemented with the same characteristics. Software testing, depending on the testing method employed, can be implemented at any time in the development process During testing if a test case fails, then testing will be suspended for all the related modules of the test case. A log will be prepared where in the error will be reported along with the description.

6.2 LEVELS OF TESTING

Unit testing Unit testing refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors. These type of tests are usually written by developers as they work on code (white-box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather is used to assure that the building blocks the software uses work independently of each other. Unit testing is also called component testing. Integration Testing Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together ("big bang"). Normally the former is considered a better practice since it allows interface issues to be localized more quickly and fixed. Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system Validation Testing Entering incorrect values does the validation testing and it is checked whether the errors are being considered. Incorrect values are to be discarded and the errors are rectified. Validation will alert the user about the type of data and the null ability of data. Alpha testing is where the end user tests the system rather than the developer, but in a controlled environment. The software is used on a natural setting with the developer monitoring the user using the system. The developer records the errors and usage problems encountered by the user. After the integration testing, software is completely assembled as a package.

Software validation is achieved through a series of black box tests that demonstrates conformity with requirements.

System Testing System tests are test designed to verify that the finished system meets its requirements. The purpose of this step is to test the system under realistic condition. It is a combination of different testing exists recovery testing, security testing, performance testing and stress testing. Testing performed in two ways.-white box testing and black box testing. White box testing is a test case design method that used the control structure of the procedural design to deliver the test cases. Black box testing was conducted for each of the modules and all of them were established to work properly. . For user acceptance testing, the system was given to the end user to use. The errors found are rectified.

Output Testing After performing the validation testing, the next step is the output testing of the software. Since no system could be useful, if it does not produce the required output in the specified format. Asking about the format required by them tests the output generated or displayed by the system under consideration. Its real testing phase where the interfaces are evaluated.

GUI Testing

GUI software testing is the process of testing a product that uses a graphical user interface, to ensure it meets its written specifications. This is normally done through the use of a variety of test cases. Most clients in client/server and web-based systems deliver system functionality using a graphical user interface (GUI). When testing complete systems, the tester must grapple with the additional functionality provided by the GUI. GUIs make testing systems more difficult for many reasons: the event-driven nature of GUIs, unsolicited events, many ways in/many ways out and the infinite input domain problems make it likely that the programmer has introduced errors because he could not test every path.

To generate a good set of test cases, the test designer must be certain that their suite covers all the functionality of the system and also has to be sure that the suite fully exercises the GUI itself. The difficulty in accomplishing this task is twofold: one has to deal with domain size and then one has to deal with sequences. In addition, the tester faces more difficulty when they have to do regression testing. There are many levels of testing have to be done before implementing the system. Unit testing is done here with the MDI main window load by checking the accuracy of timing constraints, loading logos, proper display of the subsequent window forms. Module testing is also done with proper test cases. The interface testing done with validating the inputs in each text box as required and checking proper messages and tool tips are provided in a right way or not. Performance testing is the one in which checking for the proper events are happening in a right way or not. Here in the FMS implementation, the various levels of testing remove most of the errors and irrelevant entries to the system. And the validation of the system is also very important. Before going to implement the whole system in to the client area the demo software have to be run with the sample inputs from a random number generator

IMPLEMENTATION
A crucial phase in the system life cycle is the successful implementation of the new system design. Implementation includes all those activities that take place to convert from the old system to the new one. The new system may be completely new replacing an existing manual or automated system or it may be implementation becomes necessary so that a reliable system based on the requirements of the clients can be provided. Successful implementation may not guarantee improvement in the organization using the new system. But improper installation will prevent it. It has been observed that even the best system cannot show good results if the analyst managing the implementation do not attend to every important detail. The implementation and maintenance is the last phase of Software Development Life Cycle. After testing is performed, that is checked whether the system works properly, by putting realistic data items, the system is implemented in the clients computer. Here is the most important part that is user training. The working of the system is explained to the user. The main objective of this part is that the user can able to understand the different process. Only the external working is explained to the user, and not the internal logic. Then check to see whether the implemented system satisfies the user's various needs. The major steps for implementation are Installation of hardware if required. Installation of newly developed software into hardware at the worksite. Training to the users. Demonstration of all users by entering a test data and taking the output . Preparation and distribution of operational manual. The new system may be totally new, replacing an existing system or it may be the modification to the existing system. In either case proper implementation is essential to provide a reliable system to meet the organizational requirements.

Maintenance is necessary to eliminate errors in the working system during its working life. After a system is successfully implemented, it should be maintained in a proper manner. System maintenance is an important aspect in the software development life cycle.

8. FUTURE ENHANCEMENTS
The scope for improvements and future enhancements does exist. In the future we can make more refined versions of FMS by adding new features required by the management. This application is currently an open one, which promises any amount of modules to be integrated along with it. This means that the future is in store as aspects can be incorporated in this application such that this can made even more enhanced considering the current trends and the developments the future might offer this is considered as an excellent system with a promising bright future in coming years. New security methods should be developed to avoid the misuse of the system in wide environment.

CONCLUSION
The FINANCE MANAGEMENT SYSTEM has been developed in Microsoft Visual Basic 6.0 and all the modules are tested and the system worked with real data successfully. Computerization was proposed as solution to the problem of being outdated with fast present technologies. In this project our aim is to computerize the system accordingly that meet the user needs. The FINANCE MANAGEMENT SYSTEM is working better than the existing system in all aspects. All efforts have been put to make sure that the system can handle all the requirements efficiently. The results are obtained in a timely and consistent manner since each process is implemented using modules. The system is liable to further modifications and also provides easy maintenance. We can improve the system as when needed by writing functions and procedures. By using other softwares we can make more attractive. With the blessing of Lord Almighty, support of parents and family and the immeasurable guidance of internal guide and my project coordinator, I had successfully completed my project with short allotted time. This project gave us encouragement and confidence to take such work in future

APPENDIX

FORM DESIGN

LOGIN FORM

MDI FORM-FINANCE MANAGEMENT SYSTEM

ACCOUNT OPEN ENTRY FORM (NEW ENTRY)

ACCOUNT OPEN ENTRY FORM (SEARCH)

INTEREST SETTING FORM

DEPOSIT ENTRY FORM

WITHDRAWAL ENTRY FORM

GOLD LOAN LENDIND FORM

GOLD LOAN REPAYMENT FORM

GOLD LOAN CLOSING FORM

REPORTS

ACCOUNT HOLDER DETAILS

GOLD LOAN LENDING DETAILS

BIBLIOGRAPHY

TEXT BOOK y y Visual Basic .NET Black Book The programming language of oracle --Steven Holzer Ivan Bayross

WEBSITE y www.wikipedia.com