SYSTEM AND METHOD FOR CREATING FINANCIAL TOOLS

• US 20130138544A1
• Filed: 08/06/2010
• Published: 05/30/2013
• Est. Priority Date: 08/06/2010
• Status: Abandoned Application

• Current Assignee: Infosys Limited
• Original Assignee: Infosys Limited
• Inventors: Chapman, Chris
• Application Number:
  US13/814,488
• Publication Number:
  US 20130138544A1
• Time in Patent Office: Days
• US Class Current: 705/35
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A system and method for developing a financial tool is provided. The system is an enterprise level framework. The system for developing a financial tool includes a User Interface Module, a Component Module, a Business Logic Layer Module, and an Application Programming Interface (API). The User Interface Module is configured to develop a user interface of a financial tool, based on the requirements of a business solution. The Component Module is configured to define the structure and the function of the user interface of the financial tool being developed, based on the requirement of the business solution. The Business Logic Layer Module is configured to process data in the financial tool, based on the requirement of the business solution. The API is configured to retrieve data from an end-user or an external data source to further process the retrieved data based on the requirement of the business solution.

Claims

1. A system for developing a financial tool, wherein the system is an enterprise level framework, the system comprising:

a User Interface Module configured to develop a user interface of a financial tool, based on the requirements of a business solution;

a Component Module configured to define the structure and the function of the user interface of the financial tool being developed, based on the requirement of the business solution; and

a Business Logic Layer Module configured to process data in the financial tool, based on the requirement of the business solution.

2. The system of claim 1, wherein the User Interface Module is further configured to select a layout for a user interface of the financial tool being developed, from one or more pre-stored layouts, based on the requirement of the business solution.

3. The system of claim 2, wherein the layout of the user interface selected from the one or more pre-stored layouts comprising at least one of:

an Input Panel configured to receive input data from an end-user to further execute computation in the financial tool;

an Output Panel configured to display the processed output/data of the received input data based on the requirement of the business solution; and

an Output Summary Panel configured to display a summary/outline output based on at least one of the processed output/data of the received input data and the requirement of the business solution.

4. The system of claim 1, wherein the Component Module configured to define the structure and the function of the user interface of the financial tool being developed comprising:

a Loader Component configured to load one or more programs associated with the financial tool and one or more other components associated with the financial tool;

a Slider Component configured to enable an end-user to select an input value with the help of predefined indicators outlined in a graphical user interface bar, wherein each of the predefined indicators corresponds to a predefined value;

a NavBar Component configured to implement navigation functionality in the financial tool, wherein the NavBar Component comprises one or more address links of various parts of the financial tool;

a Chart Component configured to render graphical representation of the processed data computed in the financial tool;

a Dialog window Component configured to implement a popup window used for at least one of, to display communication information to an end-user and to prompt an end-user to input a response; and

a Dropdown Component configured to enable the end-user to select an input value from a list of input values displayed in the financial tool.

5. The system of claim 4, wherein the Component Module is further configured to link at least one component selected from the Component Module to the user interface of the financial tool being developed based on the requirements of the business solution.

6. The system of claim 1, wherein the Business Logic Layer Module configured to process data in the financial tool comprising:

a. a Scenario Class configured to fetch and encapsulate one or more input values required to execute computation in a financial tool being developed;

b. a Simulator Class configured to perform computational simulation on the encapsulated one or more input values based on the requirement of the business solution; and

c. a Result Class configured to encapsulate at least one output of the computed data in the financial tool.

7. The system of claim 6, wherein the Business Logic Layer Module further comprising one or more objects, each of the one or more objects is configured to interact with one or more classes, selected from a Domain Class Module, configured to define methodology of computational functions used by the financial tool, to process the data in the financial tool, based on the requirement of the business solution.

8. The system of claim 1, further comprising a Domain Class Module configured to define the methodology of various computational functions used in the financial tool to further process data, based on the requirement of the business solution.

9. The system of claim 8, wherein the Domain Class Module comprising:

a Repayment Class configured to encapsulate information/data corresponding to a repayment and further defines the methodology to perform the repayment during computation performed in the financial tool;

a Withdrawal Class configured to encapsulate information/data corresponding to a withdrawal and further defines the methodology to perform the withdrawal during computation performed in the financial tool;

an Interest Class configured to encapsulate information/data corresponding to an interest and further defines the methodology to perform at last one of interest transaction and interest calculation during computation performed in the financial tool;

an Account Class configured to encapsulate the present state of an account at a predetermined instance of time;

a Transaction Class configured to encapsulate information/data corresponding to a transaction and further defines the methodology to perform the transaction during computation performed in the financial tool; and

a Projection Class configured to encapsulate a record of financial activities.

10. The system of claim 9, wherein each of the classes included in the Domain Class Module is selected based on a respective functional requirement of the financial tool, defined by the requirement of the business solution.

11. The system of claim 1, further comprising an Application Programming Interface (API) configured to retrieve data from at least one of input data provided by an end-user and received data from an external data source, to further process the retrieved data in the financial tool, based on the requirement of the business solution.

12. The system of claim 11, wherein the Application Programming Interface (API) is a JavaScript API.

13. The system of claim 11, wherein the Application Programming Interface (API) is further configured to enable a developer to embed the financial tool into one or more financial tools being developed.

14. A system for developing a financial tool, wherein the system is an enterprise level framework, the system comprising:

a User Interface Module configured to develop a user interface of a financial tool, based on the requirements of a business solution;

a Component Module configured to define the structure and the function of the user interface of the financial tool being developed, based on the requirement of the business solution;

a Business Logic Layer Module configured to process data in the financial tool, based on the requirement of the business solution; and

an Application Programming Interface (API) configured to retrieve data from at least one of input data provided by an end-user and received data from an external data source, to further process the retrieved data in the financial tool, based on the requirement of the business solution.

15. A method for developing a financial tool in an enterprise level framework, the method comprising:

receiving one or more parameters from a business requirement document (BRD), wherein the BRD describes the structural and functional attributes of the financial tool being developed;

initiating user interface development sequence based on the received one or more parameters;

linking one or more components to the financial tool, wherein each of the one or more components defines a functional and structural attribute of the financial tool, based on the received one or more parameters; and

defining a method to process data in the financial tool, based on the received one or more parameters.

16. The method of claim 15, wherein the one or more parameters comprises at least one of a set of input/output parameters based on the requirement of the financial tool being developed, the functional requirements of the financial tool being developed, and the structural layout of the financial tool being developed.

17. The method of claim 15, further comprising:

selecting a layout of a predefined user interface based on the received one or more parameters corresponding to the financial tool being developed; and

linking each of the one or more components to the selected layout of the user interface based on the received one or more parameters corresponding to the financial tool being developed.

18. The method of claim 15, wherein defining the method to process data in the financial tool further selects one or more predefined computational methodologies, based on the requirement of the business solution.