Page Comparison

The BIAN Service Domains define the ‘what’ properties of the associated business capability and its main service offerings and dependencies. The techniques used to isolate Service Domains ensure that these specifications are canonical using a “commercial asset leverage” design technique as described in the How To Guide - Design Concepts & Techniques Practitioner´s Guide. Though the Service Domains describe standard functional partitions, they do not assume how the supporting systems might be implemented – for example how complex or sophisticated their internal decisioning may be or how fast/comprehensive or sophisticated their service responses may be. The designs also do not anticipate the skills or knowledge of users of the systems or the interaction rules/thresholds, pricing or risk/reward calculations that may be built into the systems logic – they simply define the big-picture modular structure. BIAN members have determined that little or no sustainable competitive advantage arises from the well architected ‘what’ of systems design that will improve the modularity and interoperability of systems. They anticipate that the standard designs will allow banks to redirect any saved investment on exploring truly differentiating and innovative aspects of the ‘how’ within these partitions