2.2.3 Application Architecture Models

The purpose of this section is to define the baseline application architecture for the domain/sub-domain. 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 application services and their contracts (interactions) in scope for the baseline application 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 application services (in table format) in scope for the baseline application architecture • Characteristics of the application services (in table format) in scope for the baseline application 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 application services (in table format) in scope for the baseline application architecture • If required, characteristics of the contracts (interactions) between the application services (in table format) in scope for the baseline application architecture • Relevant views (diagrams) at the logical level illustrating the logical application components and their contracts (interactions) in scope for the baseline application architecture; these logical application components group application 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 application components (in table format) in scope for the baseline information architecture • Characteristics of the logical application components (in table format) in scope for the baseline application 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 application components (in table format) in scope for the baseline application architecture • Characteristics of the contracts (interactions) between the logical application components (in table format) in scope for the baseline application architecture • Any relationships between the business function categories, business functions, logical application components, and application services that are in scope for the baseline architecture • Any relationships between the business services and application 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 application architecture; for example, one assumption (recommendation) that has already been stated is that the physical application architecture is out of scope for the enterprise architecture