Solution Architecture Reference Model - Example

I will take a break from weblogic migration and will talk about Solution Architecture Reference Model. This entry is purely based on my understanding of  a solution architecture reference model.

Introduction

Architecture Reference models are abstract framework or ontology which comprises an interlinked set of clearly defined concepts. They help in understanding the solution  architecture of the enterprise from distinct viewpoints. This  reference models assists in clearly communicating the ideas of the  various components  and  solution building blocks used across the solution architecture landscape. The solution architecture reference model is clearly divided into three views namely Conceptual Reference Model, Logical Reference model and Physical reference model. I will describe the Conceptual Reference Model in this post.

Conceptual Reference Model

The CRM (Conceptual Reference Model) would capture the essential concepts (entities) and also represent the high level components of the solution architecture reference model. The conceptual reference model will layout the foundation of the architecture reference model from which the logical reference model and the physical reference model will be developed. 

The following diagram illustrates the Conceptual Reference Model.

CDM Reference Model

The conceptual  Reference model is structure into four distinct vertical layers and three horizontal layers which are cross-cutting across all the functional vertical layers. The following section defines each of the layers in details.

 Presentation Layer.

The presentation layer contains the components that implement and display the user interface and manage user interaction. This layer includes controls for user input and display, in addition to components that organize user interaction.

Domain Layer

The domain layer is responsible for representing concepts of the business, information about the business situation, and business rules. Business State management is  controlled and used here, even though the technical details of storing it are delegated to the infrastructure. This layer is the critical section of the  business software.

 Data Layer

The data layer provides  the capability  to create, format, and manage application data.

Infrastructure Layer

The Infrastructure Layer provides hypervisor services (VM resources) to the Platform and Software Layers. It defines the capabilities necessary for these VMs to execute; it includes hypervisor, physical servers, network devices, storage systems, and facilities (which include space, power, cooling, and physical interconnects).

Integration Layer

The Integration Layer is a key enabler for any architecture model  as it provides the capability to mediate which includes collaboration, transformation, routing, and protocol conversion . A service consumer interacts with the service provider via the Integration Layer. It also provides capabilities to enable B2B and System to System access of application and infrastructure capabilities

Security Layer

The security layer provides capabilities such as authentication, authorization encryption, non-repudiation to name a few  to secure all the vertical functional  layers.

Common Services  Layer

This layer consists of the common functionality that spans across the layers. 

In the Next Article i will cover the Logical Reference Model