testbook
Banking Industry
Architecture Network
BIAN
How-to Guide v4
Design Principles & Techniques
Organization
| Authors | ||
|---|---|---|
| Role | Name | Company |
| BIAN Architect | Guy Rackham | BIAN |
| Status | |||
|---|---|---|---|
| Status | Date | Actor | Comment / Reference |
| DRAFT | 5th Mar 2015 | Magnus Thorburn | Formatting |
| Approved | TBD | Architectural Committee | Approval |
| Version | ||
|---|---|---|
| No | Comment / Reference | Date |
| 4.1 | First edited version | 5th Mar 2015 |
| 4.2 | Updated with the first set of comments | 16th Mar 2015 |
| 4.3 | Updated all diagrams | 27th Mar 2015 |
| 4.4 | Added text, updated diagrams | 13th Apr 2015 |
Copyright
© Copyright 2015 by BIAN Association. All rights reserved.
THIS DOCUMENT IS PROVIDED "AS IS," AND THE ASSOCIATION AND ITS MEMBERS, MAKE
NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THIS DOCUMENT ARE SUITABLE FOR ANY PURPOSE; OR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY
PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
NEITHER THE ASSOCIATION NOR ITS MEMBERS WILL BE LIABLE FOR ANY DIRECT,
INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR
RELATING TO ANY USE OR DISTRIBUTION OF THIS DOCUMENT UNLESS SUCH DAMAGES ARE
CAUSED BY WILFUL MISCONDUCT OR GROSS NEGLIGENCE.
THE FOREGOING DISCLAIMER AND LIMITATION ON LIABILITY DO NOT APPLY TO, INVALIDATE,
OR LIMIT REPRESENTATIONS AND WARRANTIES MADE BY THE MEMBERS TO THE
ASSOCIATION AND OTHER MEMBERS IN CERTAIN WRITTEN POLICIES OF THE ASSOCIATION.
Table of content
Table of diagrams
Diagram 1: The BIAN 'How-to Guide’ Design Principles & Techniques 9
Diagram 2: Process model of card billing cycle 14
Diagram 3: Process model aligned to capabilities – Service Domains 15
Diagram 4: Billing event as a network collaboration 15
Diagram 5: Asset type decomposition – top levels 17
Diagram 6: Unique business context example building vs business architecture 18
Diagram 7: Functional pattern table 19
Diagram 8: Asset decomposition Excel extract 20
Diagram 9: Structure of a Service Domain 21
Diagram 10: End to end states for the functional patterns 21
Diagram 11: Design properties and service domain schematic 23
Diagram 12: A service domain represents an organizational capability 24
Diagram 13: Two types of SOA - process & capability oriented 26
Diagram 14: Rescoping a BIAN Service Domain 28
Diagram 15: An example business scenario with guidelines 30
Diagram 16: Action terms, descriptions and examples 34
Diagram 17: Action terms mapped to Functional Patterns 35
Diagram 18: BIAN - the link between business & technical architectures 37
Diagram 19: Service Domain to Business Application one to one 40
Diagram 20: Service Domain to Business Application one to many 40
Diagram 21: Service Domain to Business Application many to one 41
Diagram 22: Utility application module re-use 42
Diagram 23: Configurable solution re-use 42
Diagram 24: Mapping Service Domains down the stack 50
Diagram 25: Service Domain split into two key components 51
Diagram 26: Using Service Domain partitions to do comparisons 52
Diagram 27: The stages of externalization 54
Diagram 28: More detail of loan externalization 54
Diagram 29: ESB based application assembly 56
Diagram 30: Cloud based deployment environment 57
Diagram 31: In the cloud communication can be semantic 58
Diagram 32: Cloud based service access control 60
Diagram 33: Client server BIAN design 61
Diagram 34: Three stage process for defining a blueprint 62
Diagram 35: Using the enterprise blueprint for planning & analysis 64
Diagram 36: BIAN designs help bridge between point and enterprise viewpoints 65