Why do we use Frameworks or Employ Architecture

Sunday, November 5, 2017 | Likes: 0 | Comments: 0

Adrian Grigoriu

Executive Consultant

Contractor

Why do we use Frameworks or Employ Architecture

There are  common sense reasons such as enhanced understanding, productivity, predictability, repeatability, consistency etc. for the use of models, templates, standards, patterns...  

But why do we use frameworks, reference or generic architectures or, for that matter, why do we employ architecture? What is an Architecture method?

There is a clear distinction, often not made, between the value of architecture, the value of a reference or generic architecture and the value of an architecture framework. That is because we have to distinguish in the first place between an architecture, a reference and generic architecture and an architecture framework.

An Architecture describes a system in terms of its components and interconnections that channel the system flows. Architecture often covers the physical resources that realise the system.  Any system has an architecture or structure but some structures are simpler to control, maintain and change than others.

The value of architecture itself resides in structured description of the system which enables its faster comprehension, analysis, management, change and transformation.

Architecture principles guide the system transformation.

Generic Architecture. To represent a whole class of systems. an architecture must be "generic" enough. TOGAF Continuum emphasises the value of generic architectures. TM Forum's Frameworx is primarily a generic architecture because it describes the entities of a digital media company, i.e. the business processes, information and application maps.  

Reference Architecture is a generic architecture used as a template for the analysis and design of other systems in the same class. To be validated as reference, rather than declared as such from start by its promoters, an architecture must be generic enough to be reused in many endeavours.

A reference architecture enables reuse, predictable design, reproducibility and as such productivity which saves time and costs.

TOGAF is a reference architecture but not so much because it is used as a reference model by the industry but because it is designed by a standards organization with industry participation.

Architecture Framework is the architecture of an architecture. It looks like the skeleton of a body, the contents page of a book or the chassis of a car. It enables us to plug complying architecture artefacts into the framework in order to build the Architecture. It enables us to break the system complexity up in independently manageable parts. In other words, it facilitates independent and parallel change and as such quick and without side effects.

The architecture framework describes the key components of an architecture and their relationships. A Framework is usually  described in terms that stakeholders can grasp. The Metamodel is the technical expression of a framework. It is illustrated as a class diagram, It is ultimately unemployed as the repository schema for a tool.

An Architecture Method should exhibit:

  1. A generic/reference architecture for a class of systems
  2. An Architecture Framework and Metamodel that describe the structure of the architecture to enable its navigation
  3. An ensemble of Architecture Principles to guide a system transformation in order to reduce its complexity and enable change
  4. A system modelling process and associated controls to ensure proper governance and tools to measure progress, maturity, quality... This is part of an overall system transformation process  with regard to best practices, requirements, risks...
  5. A strategy framework that enables the specification  and the incorporation of strategic directions into the transformation

SaaS platform for Enterprise Architecture. The best option a CIO has for Technology Innovation and Digital Transformation.

© 2019 Dragon1