Today The Open Group released the updated whitepaper, Integrating the TOGAF® Standard with the BIAN Service Landscape. This release might be beneficial for those architects in the banking space that use or considering to use TOGAF in conjunction with BIAN.
For those not familiar with BIAN, it is a not-for-profit organization which seeks to accelerate the adoption of Service-Oriented Architecture (SOA) in the banking industry. It does so by promoting convergence towards a common service landscape, and by providing semantic standards which makes it easier and more cost-effective to integrate such services.
This whitepaper aims to support Enterprise Architects within the banking industry, reaping the synergies of two complementary industry frameworks:
TOGAF®, an Open Group Standard, is a proven Enterprise Architecture methodology and framework used by leading global organizations to improve business efficiency.
BIAN, the Banking Industry Architecture Network, delivers an overall framework and set of IT Service definitions and BIAN Business Scenarios specific to the banking industry, aimed at improving systems interoperability.
In the heart of the White Paper, both the TOGAF standard and BIAN are mapped to each other. The leverage of the BIAN deliverables in the context of the TOGAF Architecture Development Method (ADM) is further elaborated. For each step in an architecture development process, the integration of BIAN deliverables is described.
Claims Processing Reference Architecture provides quality services in the field of Auto Insurance Claims Processing however these components can be leveraged for other forms of claims processing such as: Home, Medical, Mortgage, and other general claims processing services to work on behalf of clients for better advanced services. Today, global insurance industry is facing a challenge to provide cutting edge services and value added customer experience coupled with faster response time and easily adaptable services. Like with the other Financial Services architectures released, this reference architecture leverages the ACORD standard throughout. This insurance interoperability with both Commercial Off The Shelf (COTS) and custom built applications in your enterprise.
Shown above is the flow and business process demonstrated in the reference architecture. There are multiple personas involved from third parties, agents and internal personal such as various underwriters.
All of this workflow is managed from Windows Workflow Foundation (WF) and uses various technologies to implement.
This reference architecture addresses the space of structured product creation. This is unique and complex process in capital markets. This is due largely to non standardization and isn’t often like anything the bank is already trading. This presents a problem in that these types of deals are unlikely to be captured in a core trading system immediately.
Below is an illustration of the process captured from the creation of the product to selling and finally managing that product.
This reference architecture addresses the space of structured product creation. This is unique and complex process in capital markets. This is due largely to non standardization and isn’t often like anything the bank is already trading. This presents a problem in that these types of deals are unlikely to be captured in a core trading system immediately.
Below is an illustration of the process captured from the creation of the product to selling and finally managing that product.
This reference architecture addresses the space of structured product creation. This is unique and complex process in capital markets. This is due largely to non standardization and isn’t often like anything the bank is already trading. This presents a problem in that these types of deals are unlikely to be captured in a core trading system immediately.
Below is an illustration of the process captured from the creation of the product to selling and finally managing that product.
This reference architecture addresses the space of structured product creation. This is unique and complex process in capital markets. This is due largely to non standardization and isn’t often like anything the bank is already trading. This presents a problem in that these types of deals are unlikely to be captured in a core trading system immediately.
Below is an illustration of the process captured from the creation of the product to selling and finally managing that product.
I am very excited to announce that we have finally released the Virtual Lab for The Microsoft Lending Reference Architecture Version 1. I have heard from you load an clear over the past few months! We now have an Virtual Machine in the "Cloud" ready for you to examine workflows, dive into code or just play with the scenario.
Keep an eye out for future releases of the Lending Reference Architecture as we have been heads down on version 2.0 with a ton of huge additions. Version 2 will be released in the same style as with version one which will include whitepapers, source code and source code.
A compile of version 1 Lending Reference Architecture materials include:
We have a lot of great partners that have used either the bits or have used the Microsoft Guidance to influence the future direction of their architectures. One in particular is a gold partner in Australia called Dataract. See my post:
This release adds support for ribbons, form-skinning, various CommandAdapters and UIElements are also added, some of which extend CAB as well as offer basic support for DevExpress controls.
The BankTeller QuickStart application has also been updated to incorporate samples of the new XtraWindowWorkspace and DxMenuItemCommandAdapter.
Other changes of note:
The file structure of the release has been reorganized so that things are slightly easier to find and consistent
The project has been renamed from DevExpress.CompositeUI to CABDevExpress.ExtensionKit (to avoid conflicts with DevExpress’ Project Converter tool)
The base namespace has changed from DevExpress.CompositeUI to CABDevExpress (this will break existing code but is copy/paste job to fix) CAB dlls are now included as part of the release to allow for easier download-and-compile
The code has been cleaned up to some extent, to remove unused includes, unused variables and other anomolies
Today we started bright and early, 7am Australian time. I had the opportunity to meet some the players here in the Aussie market.
We went through Microsoft’s position on industry standards, namely ACORD.
Then I went into the international insurance trends that many insurance companies are focusing on today. Many of these trends are a result of regulatory compliance like issues. Once we talked about the challenges in the industry we chatted about what are the Microsoft based solutions to help with these very specific challenges.
I received some great questions during the session such as:
How mature is ACORD XML? The ACORD standard has released several versions of their XML schema. Right now the standard is going through a slight flux in their scehmas.
What is the ACORD roadmap? ACORD just released version two of their standard and the next release which will be several minor revisions over a period of about five years will take the standard to a unified standards with a common ontology behind the standard.
BizTalk Performance and Scalability?
Does Microsoft have advice on governance of Service Orientated Architectures. What is the governance strategy for composite applications and their associated workflows? The larger part of this question is governance. Governance is a tricky function. It greatly depends on the organizational culture and maturity. It is difficult for Microsoft to address this prescriptively. However there are best practices industry wide that can be adopted.
![clip_image002[8]](http://blogs.msdn.com/blogfiles/mikewalker/WindowsLiveWriter/NewFinancialComponentsReleased_A4E7/clip_image002%5B8%5D.jpg)
