Skip to main content

Example 6: ArchiMate realization relationships in various layers and across layers

 Diagram



Code

@startuml
!include <archimate/Archimate>

<style>
element {
    HorizontalAlignment: left;
    MinimumWidth: 180;
    Padding: 25;
}
note {
    BackgroundColor: #FFFFCC;
    RoundCorner: 5;
    MaximumWidth: 250;
}
</style>

left to right direction

title "ArchiMate 3.2 Realization Relationships"

rectangle "Business Layer" {
    Business_Service(service_customer_support, "Customer Support Service")
    Business_Process(process_support, "Support Process")
    Rel_Realization(process_support, service_customer_support, "Realization")
    note on link
    Support Process realizes Customer Support Service.
    end note

    Business_Role(role_manager, "Manager Role")
    Business_Collaboration(collab_management, "Management Collaboration")
    Rel_Realization(collab_management, role_manager, "Realization")
    note on link
    Management Collaboration realizes Manager Role.
    end note

    Business_Interface(interface_client, "Client Interface")
    Business_Service(service_client, "Client Service")
    Rel_Realization(interface_client, service_client, "Realization")
    note on link
    Client Interface realizes Client Service.
    end note
}

rectangle "Application Layer" {
    Application_Service(app_service_data_analysis, "Data Analysis Service")
    Application_Function(app_function_data_processing, "Data Processing Function")
    Rel_Realization(app_function_data_processing, app_service_data_analysis, "Realization")
    note on link
    Data Processing Function realizes Data Analysis Service.
    end note

    Application_Component(app_component_crm, "CRM System")
    Application_Collaboration(app_collab_sales, "Sales Collaboration")
    Rel_Realization(app_collab_sales, app_component_crm, "Realization")
    note on link
    Sales Collaboration realizes CRM System.
    end note

    Application_Interface(app_interface_api, "API Interface")
    Application_Service(app_service_api, "API Service")
    Rel_Realization(app_interface_api, app_service_api, "Realization")
    note on link
    API Interface realizes API Service.
    end note
}

rectangle "Technology Layer" {
    Technology_Service(tech_service_network_monitoring, "Network Monitoring Service")
    Technology_Function(tech_function_network_management, "Network Management Function")
    Rel_Realization(tech_function_network_management, tech_service_network_monitoring, "Realization")
    note on link
    Network Management Function realizes Network Monitoring Service.
    end note

    Technology_Node(tech_node_server, "Server")
    Technology_Collaboration(tech_collab_cloud, "Cloud Collaboration")
    Rel_Realization(tech_collab_cloud, tech_node_server, "Realization")
    note on link
    Cloud Collaboration realizes Server.
    end note

    Technology_Function(tech_function_data_storage, "Data Storage Function")
    Technology_Artifact(artifact_backup, "Backup Artifact")
    Rel_Realization(artifact_backup, tech_function_data_storage, "Realization")
    note on link
    Backup Artifact realizes Data Storage Function.
    end note
}

rectangle "Motivation & Strategy Layer" {
    Motivation_Outcome(outcome_profit, "Increased Profit")
    Motivation_Goal(goal_growth, "Business Growth")
    Rel_Realization(goal_growth, outcome_profit, "Realization")
    note on link
    Business Growth realizes Increased Profit.
    end note

    Motivation_Goal(goal_compliance, "Regulatory Compliance")
    Motivation_Principle(principle_security, "Security Principle")
    Rel_Realization(principle_security, goal_compliance, "Realization")
    note on link
    Security Principle realizes Regulatory Compliance.
    end note
}

rectangle "Implementation & Migration Layer" {
    Implementation_WorkPackage(work_package_upgrade, "Upgrade Work Package")
    Implementation_Plateau(plateau_modernization, "Modernization Plateau")
    Rel_Realization(plateau_modernization, work_package_upgrade, "Realization")
    note on link
    Modernization Plateau realizes Upgrade Work Package.
    end note

    Implementation_Deliverable(deliverable_report, "Final Report")
    Implementation_Plateau(plateau_final, "Final Plateau")
    Rel_Realization(plateau_final, deliverable_report, "Realization")
    note on link
    Final Plateau realizes Final Report.
    end note
}

rectangle "Cross-Layer Realizations" {
    Application_Component(app_component_crm2, "CRM System")
    Business_Service(service_customer_management, "Customer Management")
    Rel_Realization(app_component_crm2, service_customer_management, "Realization")
    note on link
    An Application Component can realize a Business Service.
    end note
   
    Application_Function(app_function_reporting, "Reporting Function")
    Business_Function(business_function_analysis, "Business Analysis Function")
    Rel_Realization(app_function_reporting, business_function_analysis, "Realization")
    note on link
    An Application Function can realize a Business Function.
    end note
   
    Technology_Service(tech_service_database, "Database Service")
    Application_Service(app_service_persistence, "Data Persistence Service")
    Rel_Realization(tech_service_database, app_service_persistence, "Realization")
    note on link
    A Technology Service can realize an Application Service.
    end note
   
    Technology_Node(tech_node_middleware, "Middleware Node")
    Application_Component(app_component_api, "API Gateway")
    Rel_Realization(tech_node_middleware, app_component_api, "Realization")
    note on link
    A Technology Node can realize an Application Component.
    end note

    Application_Service(as1, "Account Management Service")
    Business_Service(bs1, "Customer Account Management")
    Rel_Realization(as1, bs1, "realizes")
    note on link
    Account Management Service realizes
    Customer Account Management.
    end note

    Application_DataObject(do1, "Customer Record")
    Business_Object(bo1, "Customer")
    Rel_Realization(do1, bo1, "realizes")
    note on link
    Customer Record realizes Customer.
    end note

  Application_Service(as2, "Payment Service")
  Technology_Service(ts1, "Web Service")
  Rel_Realization(ts1, as2, "realizes")
  note on link
  Web Service realizes Payment Service.
  end note

  Application_DataObject(do2, "Account Data")
  Technology_Artifact(art1, "Account Tables")
  Rel_Realization(art1, do2, "realizes")
  note on link
  Account Tables realizes Account Data.
  end note

  Business_Service(bs2, "Payment Processing")
  Technology_Service(ts2, "Database Service")
  Rel_Realization(ts2, bs2, "realizes")
    note on link
    Database Service realizes Payment Processing.
    end note


  Business_Object(bo2, "Account")
  Technology_Artifact(art2, "Customer Database")
  Rel_Realization(art2, bo2, "realizes")
  note on link
  Customer Database realizes Account.
  end note


}
@enduml
Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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     ...
Post a Comment
Read more

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 ...
Post a Comment
Read more