Skip to main content

Types of architecture

 

Based on Coverage or Scope

Different viewpoints of a system play a crucial role in architectural discussions. The same applies to architecture and its various types. (Note: This discussion is limited to IT and the software industry, not the construction industry.)

If we categorize architecture based on its coverage or scope, the following types emerge:

  • Enterprise Architecture: Covers the entire organization, including its people, business, and processes.
  • Segment Architecture: Focuses on a specific business unit or segment.
  • Solution Architecture: Addresses a particular application or function.

Based on Level of Abstraction

Architecture types can also be defined based on the level of abstraction at which a system is analyzed, including its constituents, their relationships, and behaviors:

  • Enterprise Architecture

    • Scope: Entire organization
    • Level: Abstract (less detail)
    • Outcome: Strategic insights
  • Segment Architecture

    • Scope: Business unit
    • Level: Moderate detail
    • Outcome: Business objectives
  • Solution Architecture

    • Scope: Specific application or function
    • Level: Detailed
    • Outcome: Specific operational solutions

Architecture Types Based on Aspect/Domain

Architecture can also be classified based on the domain or aspect it focuses on:

  • Business Architecture
  • Data/Information Architecture
  • Application Architecture
  • Technology (Infrastructure) Architecture

Enterprise Architecture can be considered a superset of these architecture types. Solution Architecture also describes Information Architecture, Infrastructure, Business View, and Application Architecture in more detail.


Relationship with Other Architectures

Systems Architecture vs. Software Architecture

  • Systems Architecture

    • Encompasses hardware, software, networks, and interactions within a system.
  • Software Architecture

    • Focuses on the detailed structure of a software system, including its components, their relationships, architectural style, and patterns.
    • It provides more detailed insights compared to Solution Architecture, as it is specific to software systems.

(There is a separate page on Software Architecture on this site for more details.)


Alternative Categorization of Architectural Work

Some divide architecture into the following types:

  • Enterprise Architecture – Covers the entire organization, strategic, high-level.
  • Domain Architecture – Focuses on specific domains such as applications, data, infrastructure, etc.
  • Solution Architecture – Operates at the project level, focusing on specific solutions.

Common Architectural Domains:

  • Application Domain
  • Infrastructure Domain
  • Data Domain
  • Business Domain
  • Security Domain (though its inclusion in this list is debatable)
  • Integration Domain
  • Network Domain (questionable, as every specialization does not necessarily constitute an architecture domain)

According to this perspective:

  • Enterprise Architects cover various domains but operate at a high level with broad scope and limited depth.
  • Solution Architects have broad coverage but work at a lower level of detail.
  • Software Architects are similar to Solution Architects but focus specifically on software design, including components, structures, patterns, layers, and frameworks. Their scope is narrower, but their depth is greater.
  • Domain Architects specialize in a specific domain, providing expertise across all levels within that domain.

Final Thoughts

Other types of architectures either introduce new terminology or overlap with existing ones. Many organizations and websites use different terms without clearly defining their relationships and distinctions. If you find a comprehensive list of such architectural jargons or duplications, please let me know.

Comments

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...

Examples 7: ArchiMate flow relationship between elements in layers

Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 20 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > title "ArchiMate 3.2 Valid Flow Relationships" left to right direction ' Business Layer Flow Relationships rectangle "Business Layer Flows" {     Business_Process ( bp1 , "Order Process" )     Business_Process ( bp2 , "Payment Process" )     Rel_Flow ( bp1 , bp2 , "Order data" )     note on link         Flow between Business Processes     end note         Business_Function ( bf1 , "Sales Function" )     Business_Function ( bf2 , "Delivery Function" )     Rel_Flow ( bf1 , bf2 , "Sales information" )     note on link     ...

SmartSimpleTextGenerator: A Smarter Way to Generate Text

  Introduction In the world of text generation, simple n-gram models can produce decent results, but they often lack context-awareness and coherence. To address these limitations, I have developed SmartSimpleTextGenerator , an improved version of my previous project, ImprovedSimpleTextGenerator . This new version enhances the text generation process by integrating Part-of-Speech (POS) tagging , n-gram models , and a back-off strategy , making the generated text more meaningful and contextually relevant. Key Features of SmartSimpleTextGenerator ✅ N-Gram Model with POS Tagging – Uses trigrams (default n=3) and applies POS tagging for better word prediction. ✅ Back-off Strategy – If a trigram sequence is unavailable, it falls back to bigrams and unigrams to ensure smooth text generation. ✅ Sentence Tokenization & Structure Preservation – Tokenizes input text properly while maintaining sentence integrity. ✅ Randomized Word Selection – Generates diverse outputs rather ...