Idea list

Please take a moment to read about the relationship between Allevo and the FinTP open source project.
These ideas are mainly related to the FinTP project or its sub projects and were contributed by the developers or users of the FinTP platform.

1. FinTP UI – Administration Section (user management, DB integration, UI for defining users’ profiles)

Brief explanation

A friendly screen where admins are allowed to manage the roles of various users (permissions and constraints), considering that depending on users’ business position there will be flows that should be kept “secret”, being available only to their owner. A flow is usually composed of several functional units, such as: queues and message types to which correspond specific action buttons that users are allowed to use according the business rules and we expect this to be configurable. There is another specific role that should be taken into account which allows working on reports.

Expected results

Easy administration of users in a complex business environment. Enhanced user profiles protection.

Required knowledge Java, JSP, Spring, SQL.

2. FinTP UI – Forecasting (big data, data mining, algorithm for data interpretation)

Brief explanation

This should act as a useful tool for decision making business users in a financial hectic world. These decisions should be taken considering large data statistics gathered within the shortest possible time period from the payment transactions stored in fintp database . All relevant data are expected to be displayed on meaningful dashboards. The algorithm should discover behavior, patterns, expected market outcomes and trends.

Being involved a huge quantity of data that in time may get even greater than initially considered, it is critical to have scalable and high performance framework.

Expected results

This tool will enable high level decision based on financial hidden insights, consensus within a distributed workforce, grant scores for each possible course of action.

Required knowledge Java, JSP, Spring, SQL.

3. FinTP UI – Reporting

Brief explanation

This should allow users to have real-time images of the transactions dynamic flows, and to convert these into inputs for decision making areas. These reports should be highly configurable to allow users to follow any of the possible leads coming from data held by various financial transaction types. The reporting section is expected to offer a search area that will allow quick return of relevant data (low rate of false hits, mechanisms including various operators, and imbricated complex functions). Querying the database should not be harmful in any way for the daily operations.

Expected results

Consolidated and coherent reports, configurable reporting and search criteria, sorting features, high performance.

Required knowledge Java, JSP, Spring, SQL.

4. Visual Flow Configuration

Brief explanation

An administrative area of the application where business flows owners are enable to easily create specific financial transactions flow as per  business area requirements.   This implies designing the right routing schemas whose routing rules will eventually allow setting the distribution criteria over queues defined considering possible validation and message transformations (using mechanisms such as xslt files), user actions, exit channels to third party systems.

The duplicate detection is a critical feature of a financial application that will prevent institutions from possible damage due to outgoing payments’ lack of coherence and of integrity. This feature should be highly configurable, its criteria should base on relevant business data so that it will return as less as possible false hits for operative effectiveness and efficiency.

Expected results

Generally these are actions expected to be performed by a tech person, but the actual input should come from a business user. So, the main benefits will include cutting the geeky-middle-man and allow business users to become sole owners of the operations management on one hand and reduce as much as possible human intervention, on the other.

Required knowledge Java, JSP, Spring, SQL.

5. X Message/ Data Generation Tool

Brief explanation

This is intended both for developers and testers. In order to avoid real-life scenarios to crash our great code, we thought it wise to bring these among us. Consequently, this tool should allow generating messages based on given structures and constraints. It should be both configurable (to accommodate various types of messages and standards’ and regulations’ modifications) and friendly (if provided as a feature for the clients to test their release). It might store the original schemas, message structures, standards.

Expected results

Reliable, accurate testing, shorter  testing duration.

Required knowledge Java, JSP, Spring, SQL.

6. Alerts Management

Brief explanation

The alerts are intended to avoid delays in handling unexpected behaviors of transactions (such as, duplicates, negative answers received from third party applications, lack of answers from third party applications, failure on validation rules) that may turn these into critical issues. Some operational issues must be assessed and addressed by business users as soon as possible. This feature should allow admins to define the means of communication (mobile, local network mail account, www mail account), triggers for sending alerts (transactions’ status), and alerts’ valuable content.

Expected results

Early warning of the business users about possible mishaps that could affect daily operations by delaying the appropriate reaction to a given situation.

Required knowledge Java, JSP, Spring, SQL.

7. Multi-currency Support

Brief explanation

This feature is intended to offer an aggregated view of accounts, providing real-time data that can be quickly interpreted as the business user needs. It should allow converting the displayed amounts in various currencies. Code behind may use online web services such as Google Currency Converter to get latest rates and calculate instantaneously the resulting amounts. This ability to see funds in various currencies should allow business users to reach quicker decisions, such as transferring money between accounts when needed.

Expected results

One aggregated report offering instant info of available funds, updating amounts when changing currency, possibility to move funds from one account to the other.

Required knowledge Java, JSP, Spring, SQL.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

code