From diagrams to dependency: how analysts can speak the same language as the Java team

Systems and business analysis can be conducted more effectively when the programming language used for development is considered.
Most projects in the bank and fintech are based on Java. But what does this mean for those who design a solution? What kind of imprints does this language impose, and how does it differ from other back-end languages?

Any programming language is primarily a set of libraries and frameworks. Any programming language has its own patterns and antipatterns. The development paradigm is based on the unique aspects of the Java language. Does Java impose additional requirements on business or system analysis? Modern Java uses Git as a version control system, Maven as a build tool, Spring as a project management framework, JDBC as the main database driver, and Hibernate as a means of interacting with databases.

In the talk, I would like to take an excursion into the above-mentioned frameworks, as well as show their impact on analytics.