Skip to main content

Example 4: ArchiMate Aggregation relationship in various 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 Valid Aggregation Relationships"


rectangle "Business Layer Aggregations" {

    Business_Actor(actor_organization, "Organization")

    Business_Actor(actor_department, "Department")

    Rel_Aggregation(actor_organization, actor_department, "Aggregation")

    note on link

    Business Actors can aggregate other Business Actors.

    Organization aggregates Departments.

    end note

    

    Business_Collaboration(collab_project, "Project Team")

    Business_Collaboration(collab_workgroup, "Work Group")

    Rel_Aggregation(collab_project, collab_workgroup, "Aggregation")

    note on link

    Business Collaborations can aggregate

    smaller collaborative structures.

    end note

    

    Business_Process(process_sales, "Sales Process")

    Business_Process(process_lead_qualification, "Lead Qualification")

    Rel_Aggregation(process_sales, process_lead_qualification, "Aggregation")

    note on link

    Business Processes can aggregate sub-processes.

    end note

    

    Business_Function(function_finance, "Finance Function")

    Business_Function(function_accounting, "Accounting Function")

    Rel_Aggregation(function_finance, function_accounting, "Aggregation")

    note on link

    Business Functions can aggregate sub-functions.

    end note

}


rectangle "Application Layer Aggregations" {

    Application_Component(app_banking_system, "Banking System")

    Application_Component(app_payment_module, "Payment Module")

    Rel_Aggregation(app_banking_system, app_payment_module, "Aggregation")

    note on link

    Application Components can aggregate 

    other Application Components.

    end note

    

    Application_Collaboration(app_collab_integration, "System Integration")

    Application_Collaboration(app_collab_messaging, "Messaging Framework")

    Rel_Aggregation(app_collab_integration, app_collab_messaging, "Aggregation")

    note on link

    Application Collaborations can aggregate 

    smaller collaborative components.

    end note

    

    Application_Interface(app_interface_api, "API Gateway")

    Application_Interface(app_interface_endpoint, "REST Endpoint")

    Rel_Aggregation(app_interface_api, app_interface_endpoint, "Aggregation")

    note on link

    Application Interfaces can aggregate 

    smaller interface elements.

    end note

    

    Application_Function(app_function_data_processing, "Data Processing")

    Application_Function(app_function_data_validation, "Data Validation")

    Rel_Aggregation(app_function_data_processing, app_function_data_validation, "Aggregation")

    note on link

    Application Functions can aggregate sub-functions.

    end note

    

    Application_Service(app_service_auth, "Authentication Service")

    Application_Service(app_service_token, "Token Management Service")

    Rel_Aggregation(app_service_auth, app_service_token, "Aggregation")

    note on link

    Application Services can aggregate

    more specialized services.

    end note

}


rectangle "Technology Layer Aggregations" {

    Technology_Node(tech_node_datacenter, "Data Center")

    Technology_Node(tech_node_server, "Physical Server")

    Rel_Aggregation(tech_node_datacenter, tech_node_server, "Aggregation")

    note on link

    Technology Nodes can aggregate 

    other nodes (physical or virtual resources).

    end note

    

    Technology_Collaboration(tech_collab_cluster, "Server Cluster")

    Technology_Collaboration(tech_collab_server_instance, "Server Instance")

    Rel_Aggregation(tech_collab_cluster, tech_collab_server_instance, "Aggregation")

    note on link

    Technology Collaborations can aggregate

    smaller collaborative units.

    end note

    

    Technology_Interface(tech_interface_network, "Network Gateway")

    Technology_Interface(tech_interface_port, "Network Port")

    Rel_Aggregation(tech_interface_network, tech_interface_port, "Aggregation")

    note on link

    Technology Interfaces can aggregate 

    more specific interfaces.

    end note

    

    Technology_Function(tech_function_storage, "Storage Management")

    Technology_Function(tech_function_backup, "Backup Function")

    Rel_Aggregation(tech_function_storage, tech_function_backup, "Aggregation")

    note on link

    Technology Functions can aggregate sub-functions.

    end note

    

    Technology_Service(tech_service_hosting, "Hosting Service")

    Technology_Service(tech_service_load_balancing, "Load Balancing Service")

    Rel_Aggregation(tech_service_hosting, tech_service_load_balancing, "Aggregation")

    note on link

    Technology Services can aggregate 

    more specialized services.

    end note

}


rectangle "Implementation & Migration Layer" {

    Implementation_WorkPackage(work_program, "Migration Program")

    Implementation_WorkPackage(work_project, "Migration Project")

    Rel_Aggregation(work_program, work_project, "Aggregation")

    note on link

    Work Packages can aggregate smaller work packages.

    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