Skip to main content

Example 9: ArchiMate serving relationships in various layers and across layers

 Diagram:



Code:

@startuml


!include <archimate/Archimate>


<style>

element {

    HorizontalAlignment: left;

    MinimumWidth: 180;

    Padding: 20;

}

note {

    BackgroundColor: #FFFFCC;

    RoundCorner: 5;

    MaximumWidth: 250;

}

</style>


left to right direction

title "ArchiMate 3.2 Valid Serving Relationships"


' Strategy Layer Serving Relationships

rectangle "Strategy Layer Serving" {

    Strategy_Capability(cap1, "Capability 1")

    Strategy_Capability(cap2, "Capability 2")

    Rel_Serving(cap1, cap2, "serves")

    note on link

        Capability serving another

        Capability

    end note

}


' Business Layer Serving Relationships

rectangle "Business Layer Serving" {

    Business_Service(bs1, "Customer Service")

    Business_Process(bp1, "Fulfill Customer Request")

    Rel_Serving(bs1, bp1, "serves")

    note on link

        Business Service serving

        Business Process

    end note

    

    Business_Service(bs2, "Payment Service")

    Business_Function(bf1, "Finance Management")

    Rel_Serving(bs2, bf1, "serves")

    note on link

        Business Service serving

        Business Function

    end note

    

    Business_Interface(bi1, "Customer Portal")

    Business_Service(bs3, "Account Management")

    Rel_Serving(bi1, bs3, "serves")

    note on link

        Business Interface serving

        Business Service

    end note

    

    Business_Process(bp2, "Order Validation")

    Business_Process(bp3, "Order Processing")

    Rel_Serving(bp2, bp3, "serves")

    note on link

        Business Process serving

        another Business Process

    end note

    

    Business_Function(bf2, "Sales")

    Business_Function(bf3, "Marketing")

    Rel_Serving(bf2, bf3, "serves")

    note on link

        Business Function serving

        another Business Function

    end note

    

    Business_Interface(bi2, "Customer Support Interface")

    Business_Process(bp4, "Handle Customer Inquiry")

    Rel_Serving(bi2, bp4, "serves")

    note on link

        Business Interface serving

        Business Process

    end note

    

    Business_Interface(bi3, "Vendor Portal")

    Business_Function(bf4, "Procurement")

    Rel_Serving(bi3, bf4, "serves")

    note on link

        Business Interface serving

        Business Function

    end note

}


' Application Layer Serving Relationships

rectangle "Application Layer Serving" {

    Application_Service(as1, "Data Processing Service")

    Application_Process(ap1, "Process Transactions")

    Rel_Serving(as1, ap1, "serves")

    note on link

        Application Service serving

        Application Process

    end note

    

    Application_Service(as2, "Authentication Service")

    Application_Function(af1, "User Management")

    Rel_Serving(as2, af1, "serves")

    note on link

        Application Service serving

        Application Function

    end note

    

    Application_Interface(ai1, "Web API")

    Application_Service(as3, "Data Service")

    Rel_Serving(ai1, as3, "serves")

    note on link

        Application Interface serving

        Application Service

    end note

    

    Application_Process(ap2, "Data Validation")

    Application_Process(ap3, "Data Transformation")

    Rel_Serving(ap2, ap3, "serves")

    note on link

        Application Process serving

        another Application Process

    end note

    

    Application_Function(af2, "Reporting")

    Application_Function(af3, "Analytics")

    Rel_Serving(af2, af3, "serves")

    note on link

        Application Function serving

        another Application Function

    end note

    

    Application_Interface(ai2, "Mobile API")

    Application_Process(ap4, "Process Mobile Requests")

    Rel_Serving(ai2, ap4, "serves")

    note on link

        Application Interface serving

        Application Process

    end note

    

    Application_Interface(ai3, "Integration API")

    Application_Function(af4, "Data Integration")

    Rel_Serving(ai3, af4, "serves")

    note on link

        Application Interface serving

        Application Function

    end note

}


' Technology Layer Serving Relationships

rectangle "Technology Layer Serving" {

    Technology_Service(ts1, "Database Service")

    Technology_Process(tp1, "Data Storage Process")

    Rel_Serving(ts1, tp1, "serves")

    note on link

        Technology Service serving

        Technology Process

    end note

    

    Technology_Service(ts2, "Networking Service")

    Technology_Function(tf1, "Network Management")

    Rel_Serving(ts2, tf1, "serves")

    note on link

        Technology Service serving

        Technology Function

    end note

    

    Technology_Interface(ti1, "Server API")

    Technology_Service(ts3, "Hosting Service")

    Rel_Serving(ti1, ts3, "serves")

    note on link

        Technology Interface serving

        Technology Service

    end note

    

    Technology_Process(tp2, "Backup Process")

    Technology_Process(tp3, "Restoration Process")

    Rel_Serving(tp2, tp3, "serves")

    note on link

        Technology Process serving

        another Technology Process

    end note

    

    Technology_Function(tf2, "Storage Management")

    Technology_Function(tf3, "Capacity Planning")

    Rel_Serving(tf2, tf3, "serves")

    note on link

        Technology Function serving

        another Technology Function

    end note

    

    Technology_Interface(ti2, "Hardware Interface")

    Technology_Process(tp4, "Hardware Monitoring")

    Rel_Serving(ti2, tp4, "serves")

    note on link

        Technology Interface serving

        Technology Process

    end note

    

    Technology_Interface(ti3, "Cloud Interface")

    Technology_Function(tf4, "Cloud Resource Management")

    Rel_Serving(ti3, tf4, "serves")

    note on link

        Technology Interface serving

        Technology Function

    end note

}


' Cross-Layer Serving Relationships - CORRECTED

rectangle "Cross-Layer Serving" {

    ' Application to Business (correct direction)

    Application_Service(as4, "Portal Service")

    Business_Service(bs4, "Customer Self-Service")

    Rel_Serving(as4, bs4, "serves")

    note on link

        Application Service serving

        Business Service

    end note

    

    Application_Service(as5, "Order Data Service")

    Business_Process(bp5, "Order Processing")

    Rel_Serving(as5, bp5, "serves")

    note on link

        Application Service serving

        Business Process

    end note

    

    Application_Service(as6, "Product Information Service")

    Business_Function(bf5, "Product Management")

    Rel_Serving(as6, bf5, "serves")

    note on link

        Application Service serving

        Business Function

    end note

    

    ' Technology to Application (correct direction)

    Technology_Service(ts4, "Database Hosting Service")

    Application_Service(as7, "Data Storage Service")

    Rel_Serving(ts4, as7, "serves")

    note on link

        Technology Service serving

        Application Service

    end note

    

    Technology_Service(ts5, "Server Processing Service")

    Application_Process(ap5, "Batch Processing")

    Rel_Serving(ts5, ap5, "serves")

    note on link

        Technology Service serving

        Application Process

    end note

    

    Technology_Service(ts6, "Data Management Service")

    Application_Function(af5, "Data Administration")

    Rel_Serving(ts6, af5, "serves")

    note on link

        Technology Service serving

        Application Function

    end note

    

    ' Technology to Business (possible but less common)

    Technology_Service(ts7, "IT Infrastructure Service")

    Business_Service(bs5, "Enterprise IT Service")

    Rel_Serving(ts7, bs5, "serves")

    note on link

        Technology Service serving

        Business Service (less common)

    end note

    

    Technology_Service(ts8, "Disaster Recovery Service")

    Business_Process(bp6, "Business Continuity")

    Rel_Serving(ts8, bp6, "serves")

    note on link

        Technology Service serving

        Business Process (less common)

    end note

    

    Technology_Service(ts9, "Systems Operations Service")

    Business_Function(bf6, "Operations Management")

    Rel_Serving(ts9, bf6, "serves")

    note on link

        Technology Service serving

        Business Function (less common)

    end note

}


@enduml

Labels:

Comments

Post a Comment

Popular posts from this blog

Virtual environments in python

 Creating virtual environments is essential for isolating dependencies and ensuring consistency across different projects. Here are the main methods and tools available, along with their pros, cons, and recommendations : 1. venv (Built-in Python Virtual Environment) Overview: venv is a lightweight virtual environment module included in Python (since Python 3.3). It allows you to create isolated environments without additional dependencies. How to Use: python -m venv myenv source myenv/bin/activate # On macOS/Linux myenv\Scripts\activate # On Windows Pros: ✅ Built-in – No need to install anything extra. ✅ Lightweight – Minimal overhead compared to other tools. ✅ Works across all platforms . ✅ Good for simple projects . Cons: ❌ No dependency management – You still need pip and requirements.txt . ❌ Not as feature-rich as other tools . ❌ No package isolation per project directory (requires manual activation). Recommendation: Use venv if you need a simple, lightweight solut...
Post a Comment
Read more

Building a Simple Text Generator: A Hands-on Introduction

Introduction Text generation is one of the most exciting applications of Natural Language Processing (NLP) . From autocorrect and chatbots to AI-generated stories and news articles , text generation models help machines produce human-like text. In this blog post, we’ll introduce a simple yet effective text generation method using Markov Chains . Unlike deep learning models like GPT, this approach doesn’t require complex neural networks—it relies on probability-based word transitions to create text. We’ll walk through: ✅ The concept of Markov Chains and how they apply to text generation. ✅ A step-by-step implementation , fetching Wikipedia text and training a basic text generator. ✅ Example outputs and future improvements. The Concept of Markov Chains in Text Generation A Markov Chain is a probabilistic model that predicts future states (or words) based only on the current state (or word), rather than the full sentence history. How it works in text generation: 1️⃣ We analyze a gi...
Post a Comment
Read more

Mastering Trade-Off Analysis in System Architecture: A Strategic Guide for Architects

 In system architecture and design, balancing conflicting system qualities is both an art and a science. Trade-off analysis is a strategic evaluation process that enables architects to make informed decisions that align with business goals and technical constraints. By prioritizing essential system attributes while acknowledging inevitable compromises, architects can craft resilient and efficient solutions. This enhanced guide provides actionable insights and recommendations for architects aiming to master trade-off analysis for impactful architectural decisions. 1. Understanding Trade-Off Analysis Trade-off analysis involves identifying and evaluating the conflicting requirements and design decisions within a system. Architects must balance critical aspects like performance, scalability, cost, security, and maintainability. Since no system can be optimized for every quality simultaneously, prioritization based on project goals is essential. Actionable Insights: Define key quality ...
Post a Comment
Read more