BIAN Data Architecture Specialist syllabus
Introduction
The syllabus outlines the knowledge the candidates need to master in order to pass the BIAN Data Architecture and Design Specialist Certification exam. It provides suggestions for preparation and highlights the benefits of taking this exam.
The Banking Industry Architecture Network (BIAN) is a global, not-for profit association of banks, solution providers, consultancy companies, integrators and academic partners with the shared aim of defining a semantic standard for the banking industry, covering the business and application architectural layers and the behavior, services and information viewpoints.
The BIAN Association strives to enhance the flexibility and agility of financial services systems by improving the integration of these with an architecture that is based on services.
BIAN’s vision and expectation is that a standard definition of business functions, service interactions and business objects that describe the general construct of any bank will be of significant benefit to the industry.
BIAN’s mission is to provide the world with the best banking architecture framework and banking standard. BIAN provides a trusted roadmap for constant innovation.
The goal of the BIAN Association is to develop the most important content, concepts and methods in interoperability, supporting the aim of lower integration costs in the financial services industry and facilitating business innovation and agility.
BIAN has defined various roles within a Financial Service industry team that works with BIAN, these roles have been visualized in the image below.
For four of these roles, BIAN establishes certifications that enable the various professionals to master the respective qualifications needed to execute their roles. Everyone working within a BIAN team is recommended to become BIAN Banking Architecture Foundation Certified. And to afterward obtain a specialist certification within their respective field. Or obtain all specialist certifications if he or she thoroughly wishes to master BIAN in full.
The BIAN Data Architecture and Design Specialist exam leads to the official BIAN Data Architecture and Design Specialist level certification by the Banking Industry Architecture Network and is carried out by Van Haren Learning Solutions.
The BIAN Data Architecture and Design Specialist Certification exam tests the delegate’s knowledge about the BIAN Data Architecture and the approach used by BIAN to create, maintain and manage this Architecture, and the possibilities to apply this Architecture and approach in practice.
By successfully passing the BIAN Data Architecture exam delegates will achieve the BIAN Data Architecture and Design Specialist level certification which ensures that they have been audited and have successfully mastered the required BIAN Data Architecture and Design Specialist level. This includes their ability to describe and apply certain knowledge about BIAN such as:
– To exploit the BIAN Business Object Model and Control Records;
– To apply the Business Object Modeling Approach in order to create more transparent data systems, to improve the data architecture and to improve the quality and reduce the cost of data integration;
– To enhance business and ICT system integration by improving the transparency of service interchanges.
Being certified in The BIAN Data Architecture and Design Specialist level acknowledges that a certified professional has mastered the BIAN Data Architecture and the approach used to build, maintain and manage it. A BIAN Data Architecture certified person is aware that financial institution’s data can be modelled in the BIAN way, which enables maximum interoperability and re-use and minimal ICT integration cost. A BIAN Data Architecture certified person is able to recognize and use this in the optimization of the data architecture of a financial institution as well as in dealings with other financial services providers.
Key benefits of the BIAN Data Architecture and Design Specialist Certification are:
- It increases the knowledge of BIAN and the BIAN BOM and Control Records;
- It enables professionals to leverage the benefits of the BIAN approach and its data-related deliverables (BIAN BOM and Control Records) in the creation of a more effective data architecture and more open and transparent ICT systems;
- It provides professionals and their organizations with a competitive advantage;
- It is a hallmark for the professionalism of banking professionals and banking architects responsible for information and data.
The BIAN Data Architecture and Design Specialist Certification Exam is intended for professionals in the financial services industry such as: information managers, information requirement analysts, data architects and modelers at both the enterprise and solution level. It is also intended for enterprise and solution architects, as well as consultants, who feel the need to extend their capabilities in the areas of information governance and data architecture and design.
The approach BIAN uses to elaborate and manage its Enterprise Data Architecture model, can be applied in any context. Therefore, the knowledge mastered by certifying in the BIAN Data Architecture and Design Specialist can also be relevant for professionals outside the financial sector who are active in the architecture and data domains.
The knowledge of the candidates will be tested through a multiple-choice exam. An overview of the exam characteristics is given in Table 1.
All exam candidates will get access to the online exam environment and will need to answer 60 multiple-choice questions within 60 minutes.
70% of the questions need to be answered correctly (or at least 42 of the 60 questions) to pass.
Questions can have one to many correct answers. Negative questions (… NOT…) are included.
Candidates are advised to read both questions and possible answers with care.
The candidate will receive the result immediately after the exam. (Digital) Access to your certificate will be given once you have passed.
Registration for the exam can be done by purchasing a participation exam at www.vanharen.net
The candidate can take a number of trial exams, but only one actual Certification exam. Taking trial exams before attempting the actual Certification exam is highly recommended.
Table 1 Overview of BIAN Data Architecture and Design Specialist Certification exam characteristics
| Number of questions: | 60 |
| Time (minutes) for the exam: | 60 minutes |
| Passing grade: | 70% |
| Open/closed book: | Closed |
| Language: | English |
| Exam format: | Online |
| Type of question: | Multiple choice One to many possible correct answers Negative questions included |
BIAN Certification levels
The BIAN Banking Architecture Certification consists of two levels. In addition to the foundation level, there is currently one specialization level:
- The Foundation level tests the knowledge and understanding of BIAN’s Architecture and its possible use;
- The Data Architecture and Design Specialist Certification tests the ability to exploit BIAN’s data-related deliverables and a fundamental knowledge of and ability to leverage the Business Object Modeling approach.
This syllabus describes the BIAN Data Architecture and Design Specialist level.
The BIAN foundation Certification in the Bloom Taxonomy
The BIAN Banking Architecture Foundation Certification audits candidates at the Bloom Levels 1 and 2.
This means (according to Bloom’s Revised Taxonomy):
- Remembering: Bloom Level 1
- Understanding: Bloom Level 2
- Bloom Level 3: Apply: Use information or a skill in a new situation.
The learning objectives state what the candidate needs to know and be able to do. Achieving these objectives is expressed by passing the BIAN Data Architecture and Design Specialist Certification exam.
For the Data Architecture and Design Specialist Certification, the student needs to demonstrate:
- An understanding of what BIAN is and what its purposes and design principles are;
- The ability to recognize the elements of the BIAN Architecture in relation to their role in creating and exploiting BIAN’s data-related deliverables;
- The ability to read and understand BIAN’s data-related deliverables (Control Record and Business Object Model (BOM)), in the ArchiMate and UML languages. This involves knowing and understanding the meaning of the elements of these languages as used by BIAN;
- An understanding of the Business Object Modeling approach, its steps and its patterns, and the ability to apply this approach;
- An understanding of the documentation techniques BIAN uses in view of the exploitability and manageability of its data-related deliverables;
- An understanding of the ways in which BIAN’s data-related deliverables, its Business Object Modeling approach and its documentation approach, can be of use on in information governance and on data architecture and design level.
To test these learning objectives, the scope of the BIAN Foundation Certification encompasses the following subjects.
Table 2 BIAN Foundation Certification exam topics and their weight
| Exam Specification | Weight % | |
| Introducing BIAN, its Framework and principles | 5% | |
| Overview of the elements of the BIAN Architecture and their relationship to its data-deliverables | 10% | |
| Using ArchiMate and UML to document BIAN’s data-related deliverables | 15% | |
| The Business Object Modeling Approach, its patterns and guidelines | 35% | |
| Documenting with a view to the manageability of BIAN’s data deliverables | 10% | |
| Applying BIAN’s deliverables and Business Object Modeling approach on governance, architecture and design levels | 25% | |
Introducing BIAN and its Framework
The candidates need to remember and understand the characteristics of BIAN and its offerings.
BIAN is a content standard. It does not prescribe the use of a modeling language to users of this architecture, nor does it prescribe a documentation tool.
BIAN is strictly semantic, it is implementation and technology agnostic.
BIAN is exhaustive: it offers a definition of business functions, service interactions and business objects. It covers all activities on an architecture and design level.
BIAN’s Architecture is elaborated by working groups, each focusing on a specific area and aspect of the banking architecture.
The BIAN Framework is a “toolbox” that contains its Reference Architecture for the Financial Industry as well as the means to support its adoption, such as an open digital repository and an API portal, training, publications and seminars, and a certification program.
BIAN’s Architecture is based on Agile principles. It systematically uses “building block thinking”, on the level of functionality, information and interactions.
The candidates need to remember the concepts used in the BIAN Architecture. They need to master the terminology and understand the role of each element in the whole of the BIAN Architecture, in particular in relation to the data-related deliverables.
The BIAN Metamodel defines the types of building blocks BIAN uses to capture the reality of a financial institution in an architecture model. It prescribes the way the BIAN deliverables are stored in the digital repository.
The BIAN Service Landscape is a representation that organizes the BIAN Service Domains and facilitates finding and accessing Service Domains.
The Service Domain is a core concept in the BIAN Architecture. A BIAN Service Domain represents the smallest functional partition that can be service-enabled as a discrete and unique business responsibility.
A Service Domain is constructed according to a pattern that ensures its uniqueness. A Service Domain fulfills its role by executing a Functional Pattern on instances of an Asset Type.
The complete collection of business information governed by a Service Domain is described by the Service Domain Information Profile. The Service Domain Information Profile consists of information on two levels: information at the level of Service Domain used for the control and management of the Service Domain as a service center; and information at the level of the Service Domain’s role execution, called the Control Record level.
The Control Record is based on a pattern: it represents the information about the Asset Type of the Service Domain, combined with the information that is central to the execution of the Functional Pattern: the Generic Artifact. The Control Record can be further decomposed into Behavior Qualifiers according to a Behavior Qualifier Type. The latter refines the Generic Artifact, it is representing the type information resulting from a refinement of the Functional Pattern.
The BIAN BOM (Business Object Model) is elaborated by modeling the information needs of every BIAN Service Domain, as expressed in its Control Record, according to the “Business Object Modeling approach”. The resulting individual Service Domain Business Object Models (Service Domain BOMs) are consolidated into the BIAN BOM. The “Business Object Modeling approach” ensures the consistency of the BIAN BOM.
The Business Object Modeling approach uses a Content Pattern[1] and a Structure Pattern to support unambiguous definitions for business concepts and, supported by a classification pattern, the detection of the building blocks of the data model. Content and Structure patterns also support the modeling activity itself and the creation of a coherent enterprise data model (the BIAN BOM).
Every Service Domain offers a collection of Service Operations. A Service Operation offered by a Service Domain is made available to the environment through an access point called a Semantic API Endpoint. The collection of the Semantic API Endpoints of one Service Domain is represented by its Semantic API.
The purpose of a service is characterized by an Action Term. The Message, containing the information exchanged in a Service Operation, refers to the Information Profile of the Service Domain, or any of its constituent parts. A machine-readable Swagger File can be generated from the Semantic API. The Semantic API Swaggers can be extended to create executable APIs.
BIAN Business Scenarios and Wireframes provide practical examples of how Service Domains can interact through Service Connections, exchanging Service Operations.
A Business Capability represents the bank’s abilities and capacities to realize its banking strategies and to create value in its ecosystem. BIAN defines Business Capabilities, described as a collaboration between Service Domains, that can be used as such or can inspire a bank’s own business capabilities.
[1] The Content Pattern is an abstract idata model, valid for any business. It contains the Business Objects and their relationships, that make up any business, on a high abstraction level. This model can be made more specific for a particular business context.
The candidates need to be able to read and understand BIAN’s data-related deliverables (Control Record and Business Object Model (BOM)), in the ArchiMate and UML languages. They need to be able to use these conventions actively. This involves knowing and understanding the meaning of the elements of these languages as used by BIAN.
For its data-related deliverables, BIAN uses the documentation elements depicted in Figure 1. There are conventions for what documentation element to use, for what purpose (i.e. what their role and is in a model and what meaning they reflect).
The ArchiMate language is used for documentation on architecture level, the UML language for documentation on a more detailed (high level) design level. Although different symbols are used for the same concepts in these two languages, the concept itself is managed only once.
Figure 1 Overview the elements in ArchiMate and UML, used to document data-related deliverables
The candidates need to understand the Business Object Modeling approach, its steps and its patterns. This requires a knowledge of the Business Objects of the Content Pattern and their relationships, as well as a knowledge of the concepts represented in the Structure and Classification pattern. They need to be able to recognize the definition guideline. The candidates need to be able to apply the BOMing approach.
The Business Object Modeling approach is based on clearly and unambiguously detecting the business concepts, required to fulfill the information requirements. Business concepts however, are (usually) “information products” and not “information building blocks”. These building blocks – or Business Objects, need to be “distilled” and their relationships need to be discovered.
The resulting information model, will be used to decide how the data, required to provide the required business concept information, will be stored and managed on the ICT platform.
The Business Object Modeling (BOMing) approach uses a Content Pattern and a Structure Pattern, as well as definition guidelines, to support unambiguous definitions for the business concepts. Using a Classification Pattern, the building blocks of the information model can be detected.
The Content Pattern is an abstract information model, valid for any business. It contains the Business Objects and their relationships, that make up any business, on a high abstraction level. This model is made more specific for the business concept’s particular business context. The Structure Pattern supports this concretization.
By using the Content and Structure Pattern for subsequent business areas (in BIAN’s context, Service Domains), it becomes clear how these areas fit together/ where similar or overlapping information is detected. As such, a coherent Enterprise Data Model can be created.
BIAN’s BOM is a reference Data Architecture Model for the financial industry.
The candidates need to have an understanding of how the general abilities of the BIAN Architecture and the specific abilities of its data-related views and approach, can be applied in information and data governance, architecture and design. The candidates need to be ready to apply this in their own organization and field of expertise.
The BIAN BOM offers a MECE[1] collection of elementary, semantic building blocks for a bank’s information requirements. Its elements are named and canonically defined to a reasonable level of detail. As such, it is well positioned to be used as a “common language” and “common Frame of Reference” for the information, as required and managed by business and present on the application platform (or with service providers). It can be used as a common language in service exchanges.
The BIAN BOM and/or its tailored version – a bank can always tailor and expand the BOM into its very own “canonical data model”- can be used as follows:
- It can be used as a common language to facilitate understanding between speech communities.
- Data classification (value and risk) on an enterprise level becomes easier. Information and data governance roles can be unambiguously assigned.
- The business and data solution landscape can be overlaid on the BOM, as a Frame of Reference, in order to uniquely identify the data used and managed by business organizations and processes, stored, used and managed in data stores, and “moved around” in data services and flows.
- This facilitates the gathering of quality requirements – and the evaluation and comparison of the quality of data sources.
- It is a powerful tool for managing (exploring, charting, evaluating, optimizing) the data architecture, both “data at rest” and “data in motion”.
- As (documentation of) existing data stores and services/flows are “canonically labeled”, reuse is promoted and possibly enforced.
- The data architecture can be steered by using the Business Object Model, its patterns and principles, as basis for a conceptual reference data architecture.
- The canonical data model supports the creation of a “business intelligence” environment where all data available in the enterprise need to be navigable.
- API messages can be expressed in “common language”, facilitating service-oriented cooperation within the organization and with service providers.
These practices need can be introduced step by step. The BIAN Architecture provides a MECE collection of stable, well-delimited partitions for a bank’s activities and information. This supports an area-by-area introduction.
In process management and application design, the BIAN Service Domains can be used as (high level) reusable process steps and as reliable “Agile” delimitation for application components. If the organization introduces the use of BIAN in all its aspects, the information/data analyst can profit from this: the “sum” of the Control Records of the Service Domains used to describe the process and/or application system requirements, is a nice starting point for gathering and modeling the information requirements.
[1] Mutually Exclusive, Collectively Exhaustive
The candidates need to remember what techniques BIAN uses to document its BOM with a view to its manageability as an Enterprise Information Architecture Model. They need to understand how these documentation techniques contribute to the exploitability and manageability of its data-related deliverables.
In terms of manageability, an Enterprise Information Model requires abstraction levels. These allow the user of this model to “zoom in” and find the information he/she is looking for. These abstraction levels are also (and not least) an indispensable management instrument for the enterprise data architect. To “divide and conquer”, to enforce a generic structure in each system data model and to support reuse. BIAN uses “helper diagrams” for this purpose.
Reuse and “generic structures” are relevant on a more detailed level too. BIAN uses “data types” that describe standard structures and reusable attribute-groups. These are used to create Control Records, and to document Service Domain BOMs on design level.
The BIAN Data Architecture and Design Specialist Certification is based on knowledge articulated in the publication “A pattern-based approach to enterprise data management”, due to be available in 2023. Prior to publication, the BIAN Data Architecture & Design Specialist Courseware will cover this content.
The book “BIAN 2nd Edition – a framework for the financial services industry”[1] treats the entirety of BIAN, including a more limited view on its data deliverables. This book contains the information required for the BIAN Foundation Certification and offers valuable background for this certification. The chapters mentioned in Table 3 are of direct use in preparation for this certification.
Self-study should take about 30 hours, depending on existing knowledge. It is recommended that candidates have a working knowledge of data architecture and design.
To support the candidates, an accredited BIAN Data Architecture and Design Specialist training course is available. The recommended number of contact hours for this training course is 16 hours or 2 days.
Table 3 gives an overview of the exam topics and where they are covered in the accredited training course and the related publication, and in the book “BIAN 2nd Edition – a framework for the financial services industry”.
Table 3 Exam topics – training module and literature mapping
| Exam specification | Training module and related publication | Book chapter/section | |
| Introducing BIAN, its Framework, and principles | Part I, Chapter 1 | Part I, Chapter 1 | |
| Overview of the BIAN Architecture elements and their relationship to its data-deliverables | Part I, Chapter 2 | Part I, Chapter 2 | |
| Using ArchiMate and UML to document BIAN’s data-related deliverables | Part II, Chapters 3 to 4 | ||
| The Business Object Modeling Approach, its patterns and guidelines | Part II, Chapter 5 | ||
| Documenting with a view to the manageability of BIAN’s data deliverables | Part II, Chapter 6 | ||
| Applying BIAN’s deliverables and Business Object Modeling approach on governance, architecture and design level | Part III, Chapters 7 to 12 | Part II, Chapters 4, 5, 8, 9 | |
[1] ISBN Hard copy: 978 94 018 0768 5, ISBN eBook: 978 94 018 0769 2, ISBN ePub: 978 94 018 0770 8
Exam regulations
General rules
A BIAN Data Architecture and Design Specialist Certification is a prestigious qualification, and fraud is not tolerated. Your exam will be immediately rejected if fraud is found to have been committed during or after completion of the exam. As a result, you will not be reimbursed for your examination fees.
If you fail to pass the exam, you will not receive a certificate. This also means that you must purchase and take a new exam for your certification. Every candidate only gets one attempt per exam to succeed.
Sharing of exam questions is illegal
It is not allowed to share exam questions with others or make them public. This is a violation of the copyright and IP of the BIAN Association, Envizion cvba and Van Haren Learning Solutions. Doing so can lead to legal action by Van Haren Learning Solutions with potentially harmful consequences.
Key terms and concepts
The terms and concepts described in Table 4 need to be known and understood in order to successfully pass the BIAN Foundation Certification exam.
Table 4 Terms and expressions, key to taking the BIAN Data specialist Certification exam.
| Term/expression | Definition or meaning, as used in the BIAN context |
| Account | A measuring state on which movements in value or amounts of assets, rights and obligations are registered. |
| Account Entry | The record of a movement in value or amounts of assets, rights and obligations. |
| Aggregation relation | a relation that expresses that one Object combines one or more other Objects. An aggregation does not imply dependency. |
| Agreement | A formal or informal common understanding between two or more parties, concerning one or more subject matters, expressed in a set of arrangements, terms, and conditions. |
| Architecture | The aspired structure of the components of a system, their interrelations, and the principles and guidelines governing their design and evolution over time. The structure of components and their inter-relationships is described in an architecture model (The Open Group (2019)). |
| Arrangement | A promise between two or more parties to do or not to do something, to give or not to give something. |
| Asset Type | Something tangible or intangible the bank has ownership and/or influence over, that can create value for the bank. |
| Association relation | A relation between two Objects that is not further specified. Specified in the sense of “integrity rules, like any other relation, an association relation can be attributed with roles for the involved objects, a name for the relation and multiplicities. |
| Behavior Qualifier | A set of business information that qualifies (i.e., refines) the Control Record of a Service Domain. |
| Behavior Qualifier Type | A type of information that refines the Generic Artifact and specifies a classification of Behavior Qualifiers. |
| BIAN BOM | Reference information architecture model for the financial industry. |
| BIAN Framework | BIAN’s Reference Architecture for the Financial Services Industry and its standard, and the toolbox BIAN offers in support for their adoption. |
| BIAN Metamodel | The constructs and rules according to which the BIAN Architecture models the reality of the financial industry. |
| Business Object | Something that exists in reality, concrete or abstract, and participates and/or influences the nature of the business. |
| Business Object Attribute | A descriptor that is not solely used as identifier nor provides data about the Business Object’s lifecycle stage. |
| Business Object Descriptor | A data element that describes a Business Object. |
| Business Object Lifecycle Descriptor | A characteristic referring to a state transition in the Business Objects lifecycle. |
| Business Object Relationship | Information about the relationship between two or more Business Objects. |
| Business Scenario | A linked sequence of interactions between Service Domains in response to a business event. |
| Bustiness Object Identifier | A value that is able to uniquely distinguish one instance of a Business Object from another. |
| Canonical | In a common language, meant to enable communication between “speech communities”. |
| Canonical Data Model | A data model that contains all data required for the organization, in a canonical format. |
| Channel | An interface through which parties can communicate or exchange goods or services. |
| Classification | Any label or category that classifies something. We distinguish Taxonomical classification and Functional Classification. |
| Composition relation | A relation that expresses a whole/part relation and an existence dependency. |
| Concept Classification Pattern | A pattern that allows the classification of business concepts from a data modelling point of view. |
| Conceptual Data Model | A data model reflecting solely the structure of the data , independent of how they are to be used. |
| Content Pattern | An abstract data model, valid for any business. It contains the Business Objects and their relations, that make up any business, on a high abstraction level |
| Control Record | A set of business information that reflects all information needed to support the fulfillment of the role of Service Domain on instances of an Asset Type. |
| Data | A discrete value of a data element, that depicts a characteristic of a thing. Facts, describing a Business Object. |
| Data Architect | Role of a person who is responsible for defining the policies, procedures, models and technologies to be used in collecting, organizing, storing and accessing company data.4 |
| Data Type | The notation conventions and internal structure of a business object descriptor. |
| Diagram | A visual representation of (part of) a model for the purpose of communication. |
| Enumeration | A series of values that describe and/or limit the possible values of a business object descriptor. |
| Event | Something that happens, has happened, can happen or is planned to happen. |
| Frame of Reference | The set of reference or anchor points offered by BIAN, that enable a unique identification, understanding and positioning of the elements of a bank. |
| Functional Classification | A classification by functional meaning of the things. |
| Functional Pattern | A behavior or mechanism that can be applied to some asset in the execution of commercial business. |
| Generalization relation | A relation between a more specific thing and a more general thing. |
| Generic Artifact | The general type of artifact produced and/or managed by any Service Domain that conforms to the Functional Pattern. |
| Good | A tangible or intangible thing. |
| Helper Diagram | A diagram that depicts one (more abstract) Business Object, its relations with other Business Objects and its specializations.. |
| Implementation Agnostic | Indicating what needs to be done/known and not how and with what this needs to be implemented. |
| Information | What business needs/wants to know. |
| Information Classification | A process in which organizations assess the level of quality and protection that should be given to their information. This level is based on the value the information represents for the organization and the risks involved in lacking Confidentiality, Integrity or Availability. |
| Information governance | A holistic approach to managing corporate information by implementing processes, roles and structures, controls and metrics that treat information as a valuable business asset[1]. |
| Information Owner | Role of a person who is accountable for the assessment of the of the value and risk of specified information and for the establishment and enforcement of adequate controls, as well as mitigating actions during its lifecycle. |
| Information Profile | The information required for a Service Domain to function. |
| Information Steward | Role of a person who is responsible for the quality of specified information. This includes the establishment and day to day enforcement of adequate controls, as well as mitigating actions during the entire lifecycle of this information. |
| Information Value and Risk | Assessment of the importance of information for the results of an organization (value), and the gravity of the consequences (e.g. financial, reputational, legal) in case of less than maximal quality and protection of this information (risk). |
| Instruction | A request to do “something.” |
| Landscape | The actual structure of the components of a system and their interrelationships |
| Location | An addressable space/position both in real and virtual environments |
| Logical data Model | A data model that takes into account its structure as well as its exploitation. |
| Logical Data Store | A collection of data that is managed and exploited as a whole. This concept is independent of the technology used to store the data. E.g. a database, a spreadsheet, an address booklet. |
| Message | The input and output parameters exchanged through a Semantic API Endpoint. |
| Multiplicity | The possible number of participating instances in a relation. |
| Party | A person or an organization. |
| Physical data Model | A model depicting the structure according to which data will be stored in the storage system of choice. |
| Product | A type of Good or Service or a coherent package thereof, which is offered to internal or external customers. |
| Product Feature | A characteristic of a product, expressed in offered services and/or goods and the terms and conditions applicable to the delivery of the services. |
| Reference Architecture | An architecture that steers the design of solutions and their end-to-end embedding in the enterprise architecture. It does so by providing reference models, patterns, principles and guidelines, and by prescribing standards. |
| Reference Architecture for the Financial Services Industry | The architecture model in which BIAN captures the reality of the financial industry. It provides reference models, patterns and principles applicable for the financial industry. |
| Rule Set | A set of rules to guide, direct or operate a subject matter. e.g., regulation, policy, law, guideline, principle, standard. |
| Semantic | Expressed in business language, indicating what needs to be done/known and not how and with what this needs to be implemented. |
| Semantic API | The collection of the Semantic API Endpoints of one Service Domain. |
| Semantic API Endpoint | An access point where one Service Operation offered by one Service Domain is made available to the environment. |
| Semantic API Message | The input and output parameters exchanged through a Semantic API Endpoint. |
| Service Domain | An elemental or atomic functional building block that can be service-enabled as a discrete and unique business responsibility. |
| Service Domain BOM | Data model of the business information, governed by a Service Domain, modelled according to the BOM approach. |
| Service Domain Information Profile | The complete collection of business information governed by a Service Domain when implemented as a stand-alone service center. |
| Service Landscape | A representation that organizes the BIAN Service Domains and facilitates access to them. |
| Service Operation | A business service that is exposed by a Service Domain. |
| Specialization relation | A relation which expresses that one Object is a particular kind of another. |
| Specialization relation | A relation that expresses that one Object is a particular kind of another. |
| Specialization relation | A relation that expresses that one Object is a particular kind of another. |
| Standard | Element of BIAN’s Reference Architecture for the Financial Services Industry for which the ambition is to achieve a consensus among leading banks and providers in the financial services industry, which in due time should lead to standardized services. |
| Structure Pattern | A model that depicts the structure of the data that can describe a business concept. |
| Tailoring the BIAN Architecture | Adding/deleting and adapting elements of the BIAN Architecture in view of the specificities of the bank. |
| Taxonomical Classification | A classification by the nature of the things. |
| Technology agnostic | Unbiased towards what technology is used for implementations. |
| Time | A dimension expressing when something happens or will happen. It can be a period, date, a calendar, a more detailed time indication. |
| Transaction | The act of doing “something”. |
| Wireframe | An interaction representing the available Service Connections for a selection of Service Domains. |
[1]Based on Techtarget.com dd november 2022
