2.2.4 Technology Architecture Models

The purpose of this section is to provide a high-level view of the baseline technology architecture for the domain. If produced, the domain only needs to produce the relevant artifacts from those highlighted in this section as per their needs. In terms of quality criteria, this section may make clear: • Relevant views (diagrams) at the conceptual level illustrating the infrastructure services and their contracts (interactions) in scope for the baseline technology architecture • Description of the conceptual-level view(s) in order to understand the architectural decisions that have been taken and resulting key messages for the stakeholders • Definitions for the infrastructure services (in table format) in scope for the baseline technology architecture • Characteristics of the infrastructure services (in table format) in scope for the baseline technology architecture; the domains will need to decide whether characteristics are needed at the conceptual services level, logical component level, or both • Descriptions of the contracts (interactions) between the infrastructure services (in table format) in scope for the baseline technology architecture • If required, characteristics of the contracts (interactions) between the infrastructure services (in table format) in scope for the baseline technology architecture • Relevant views (diagrams) at the logical level illustrating the logical infrastructure components and their contracts (interactions) in scope for the baseline technology architecture; these logical infrastructure components group infrastructure services together based on common requirements/characteristics • Description of the logical-level view(s) in order to understand the architectural decisions that have been taken and resulting key messages for the stakeholders • Definitions for the logical infrastructure components (in table format) in scope for the baseline technology architecture • Characteristics of the logical infrastructure components (in table format) in scope for the baseline technology architecture; the domains will need to decide whether characteristics are needed at the conceptual services level, logical component level, or both • Descriptions of the contracts (interactions) between the logical infrastructure components (in table format) in scope for the baseline technology architecture • Characteristics of the contracts (interactions) between the logical infrastructure components (in table format) in scope for the baseline technology architecture • Any relationships between the business function categories, business functions, logical infrastructure components, and infrastructure services that are in scope for the baseline architecture • Any relationships between the business services and infrastructure services that are in scope for the baseline architecture • Any additional viewpoints and thus views that are required for this section due to new stakeholder requirements; these views will then be followed by descriptions for the views and definitions for the view artifacts • Any assumptions that have been used to define the baseline technology architecture; for example, one assumption (recommendation) that has already been stated is that the physical technology architecture is out of scope for the enterprise architecture