Facebook Twitter Linkedin
 

Blog

Archive for tag: open source

SIBOS 2018 Sydney Wrap-up

 

 

The last two days of Sibos 2018 Sydney brought interesting debates on regulatory compliance, real-time payments (over and over again), contextual banking, managing the emerging AML and regulatory risks of new payment methods, aaand… the weakest link in cyber-security: the people!

 

Hot topic 1: Reconciling real-time payments with financial crime and fraud controls

  • How to increase speed without sacrificing security?
  • Can technology contribute to fraud and financial crime prevention, rather than simply speeding up payments?
  • How much risk is too much in terms of instant payments?
  • Financial crime compliance teams should shift their focus to prevention rather than detection!

 

Hot topic 2: The impact of open banking for corporate treasury

  • Open banking and emerging technologies are driving a digital transformation in the corporate to bank landscape.
  • Bank business models change on one side and a rich ecosystem of third party solution providers is being created on the other side.
  • Thus, corporate treasurers can now address key industry challenges in unimaginable ways.

 

 

Fast-forward on Day 3

 

Regulatory compliance uses up capital and human resources, consumes IT budgets and puts pressure on margins, but it also allows financial institutions to review their existing business models in line with current market practices to better serve their customers. The complexity of the new regulatory framework creates dynamics and fosters the innovation process in a sustainable way.

 

 

Innotribe’s Future of Money session focused on contextual banking, specifically how data, computing power and AI will bring about a revolution in hyper-personalisation and enable the promise of contextual banking.

 

 

“People don’t buy mortgages, they buy homes; they don’t take out car loans, they buy a car. This is what we mean by contextual banking – it’s about putting the right product or service in front of customers at the right time, and embedding it within the end product itself. […] Contextual banking offers a way for the industry to re-bundle financial services for their customers’ benefit, help retain customer loyalty and ultimately trust.”

 

 

Fast-forward on Day 4

 

  • We are at the beginning of API adoption for retail and wholesale banking.
  • Reach, standardization and security remain the key problems to solve in an API-connected environment.
  • Faster payments are at the center of the digital revolution.
  • Digital identity is at a crisis point and we need a holistic approach.
  • Cyber-security isn’t an individual, corporate, or even industry problem, but one that needs to be addressed globally, across multiple industries.
  • Open source communities are successful because they go beyond providing access to source code – they honor the principles of transparency, accountability, participation, collaboration, and access.
  • Wake-up call for banks in the open era: elevate service offerings in order to retain consumer loyalty!

 

 

 

Sneak Peek into Our Automated Testing Tool

 

 

 

Part of our EU-funded corporate treasury project, meet our FinTPc automated testing tool! Why this need for automation? Because it is more reliable and way quicker than manual tests, hence we all get faster feedback and benefit from improved quality.

 

The automated testing tool is an open-source functional extension of FinTPc designed to make the testing process more objective. Its main purpose is to assist and help people involved in the testing and validation process, providing fast and complete checks of FinTPc:

-        after the initial installation in the customer’s environment;

-        after configuration changes;

-        after the installation of major releases or patches, also known as regression testing;

-        after extending the product with new features.

 

It is built as a collection of modules that can be used on their own to test certain business or technical functionalities. The automated testing is performed:

-        in different deployment architectures;

-        for different versions of prerequisites;

-        for different technical interfaces with other applications;

-        for custom configurations.

 

 

 

 

The automated testing handles functional tests, integration tests and unit tests. All these are predefined, any change to the FinTPc application has impact on the tool’s test repository and generates updates.

 

Functional tests are built based on the specification document that identifies test cases that make sense being automated, following a black box testing method. These are customizable and follow specific already implemented business flows. The tool allows defining input data (or test data generation) and set expected results based on a predefined list in its repository. It all ends with a validation phase that analyzes the output data of the test and the configured expected result summarized in a log (that may also include technical errors occurred).

 

Integration tests represent a logical chaining of more functional tests that validate a whole business flow. This validation ends at first error encountered, continuing the test would not assure any consistency.

 

Unit tests are predefined for each logical component of FinTPc, are usually run at the build stage and are addressed to the developers of the application.

 

Easy to install and easy to use, the automated testing tool can provide a measure of the current quality of the software, monitors and controls the testing execution, reports and records testing results and archives their history along with the context in which the testing was run.

 

Different testing modules can be configured and used separately in order to best help in the diagnosis activity and in determining the root cause of a problem.

 

Intertek ISO 9001:2008CMMI Level 2ISO  9001/2008 Dun & Bradstreet