FDC3: Interoperability for the Financial Desktop

The ever-increasing pace of change on the financial desktop requires us to think differently about building software and enabling better and more efficient workflows. The move to micro-frontends, enabled by FDC3, increases developer efficiency by allowing the reuse of siloed applications into new workflows. Created by leading organizations in the financial industry, FDC3 is an open standard that enables application interoperability, allowing developers to focus on providing value to their organizations. This course is aimed at financial professionals working in business roles, program management, or technical architecture, who would like to understand how FDC3 can help them achieve integrated workflows between applications in their portfolios. This course will also be invaluable to software developers seeking a thorough introduction to the technical concepts that form part of the FDC3 Standard. LFS177x discusses the FDC3 standard for application interoperability. You will learn about FDC3 and what problems it addresses. Additionally, you will gain an understanding of the challenges of integration and the need for a shared language, as well as the specification and key components that make up FDC3. The course also covers workflow-driven design as a method of adopting FDC3. At the end of this course, you will know how to participate in the FDC3 community. The course prepares business professionals to make informed decisions in the planning or procurement process for new software and helps to ensure that workflows are joined up effectively. The course teaches software and fintech professionals the key FDC3 concepts and helps to use the appropriate concepts when developing applications.

• Understand FDC3 and what problems it addresses
• Discuss the challenges of integration and the need for a shared language
• Understand the specification and key components that make up FDC3
• Discuss workflow-driven design as a method of adopting FDC3
• Participate in the FDC3 community

• We presume learners have some exposure to software workflows in institutional finance and a familiarity with the landscape of the financial desktop (participating vendors, etc.).