{"id":18512340,"url":"https://github.com/plantuml-stdlib/archimate-plantuml","last_synced_at":"2026-01-30T16:53:16.002Z","repository":{"id":47238277,"uuid":"165775901","full_name":"plantuml-stdlib/Archimate-PlantUML","owner":"plantuml-stdlib","description":"PlantUML macros and other includes for Archimate Diagrams","archived":false,"fork":false,"pushed_at":"2025-11-12T10:24:23.000Z","size":6228,"stargazers_count":247,"open_issues_count":1,"forks_count":64,"subscribers_count":17,"default_branch":"master","last_synced_at":"2025-11-12T12:12:58.864Z","etag":null,"topics":["archimate","architecture","architecture-as-code","diagram","graphviz","plantuml","uml","uml-diagrams"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/plantuml-stdlib.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGES.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2019-01-15T03:06:09.000Z","updated_at":"2025-11-12T10:24:27.000Z","dependencies_parsed_at":"2022-09-03T13:02:20.124Z","dependency_job_id":"54ca9363-9878-4d9d-9c7c-6d957d4030a6","html_url":"https://github.com/plantuml-stdlib/Archimate-PlantUML","commit_stats":null,"previous_names":[],"tags_count":6,"template":false,"template_full_name":null,"purl":"pkg:github/plantuml-stdlib/Archimate-PlantUML","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/plantuml-stdlib%2FArchimate-PlantUML","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/plantuml-stdlib%2FArchimate-PlantUML/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/plantuml-stdlib%2FArchimate-PlantUML/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/plantuml-stdlib%2FArchimate-PlantUML/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/plantuml-stdlib","download_url":"https://codeload.github.com/plantuml-stdlib/Archimate-PlantUML/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/plantuml-stdlib%2FArchimate-PlantUML/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28915938,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-30T16:37:38.804Z","status":"ssl_error","status_checked_at":"2026-01-30T16:37:37.878Z","response_time":66,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["archimate","architecture","architecture-as-code","diagram","graphviz","plantuml","uml","uml-diagrams"],"created_at":"2024-11-06T15:33:45.235Z","updated_at":"2026-01-30T16:53:15.991Z","avatar_url":"https://github.com/plantuml-stdlib.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Archimate-PlantUML\n\nPlantUML macros and includes for creating Archimate Diagrams easily.\n\n![Archimate-PlantUML Sample image - Internet Browser](./images/Archimate%20Sample%20-%20Internet%20Browser.png) \n\n## Table of Contents\n1. [Background](#background)\n   - [PlantUML](#plantuml)\n   - [ArchiMate](#archimate)\n2. [Getting Started](#getting-started)\n   - [Using built-in support](#using-built-in-support) \n   - [Using a version available on the internet](#using-a-version-available-on-the-internet)\n3. [Usage](#usage)\n   - [ArchiMate Elements](#archimate-elements)\n   - [ArchiMate Relationships](#archimate-relationships)\n   - [ArchiMate Groups](#archimate-groups)\n   - [Special shapes](#special-shapes)\n   - [Nesting of Components](#nesting-of-components)\n   - [Theme Support](#theme-support)\n   - [Sequence Diagrams using Archimate elements](#sequence-diagrams-using-archimate-elements)\n4. [Example](#example)\n5. [Contributing](#contributing)\n6. [License](#license)\n7. [Acknowledgments](#acknowledgments)\n\n## Background\n\n### PlantUML\n[PlantUML](http://en.plantuml.com/) is an open-source project that allows you to create UML diagrams using a simple text language. It utilizes [Graphviz](https://en.wikipedia.org/wiki/Graphviz) for diagram layout, generating images in PNG, SVG, or LaTeX formats.\n\n### ArchiMate\n[ArchiMate](http://pubs.opengroup.org/architecture/archimate3-doc/) is an enterprise architecture modeling language that supports the description, analysis, and visualization of architecture across business domains.\n\nArchiMate offers a common language for describing the construction and operation of business processes, organizational structures, information flows, IT systems, and technical infrastructure. This is just like an architectural drawing in classical building where the architecture describes the various aspects of the construction and use of a building. This insight helps the different stakeholders to design, assess, and communicate the consequences of decisions and changes within and between these business domains. \n\n[Archimate-PlantUML](https://github.com/plantuml-stdlib/Archimate-PlantUML) combines the benefits of PlantUML and ArchiMate for providing a simple way of creating and managing ArchiMate diagrams. The Archimate-PlantUML is a set of macros and other includes written on top of [PlantUML Archimate specification](http://plantuml.com/archimate-diagram), with an aim to simplify the syntax for creating elements and defining relationships.\n\n## Getting Started\nInclude the `Archimate.puml` file in your `.puml` or `.wsd` file. There are multiple options, depending on how current you want to be\n\n### Using built-in support\n```plantuml\n' to use the built-in support\n!include \u003carchimate/Archimate\u003e\n\n' optionally choose one of the available themes\n'!theme archimate-alternate from \u003carchimate/themes\u003e\n'!theme archimate-handwriting from \u003carchimate/themes\u003e\n'!theme archimate-lowsaturation from \u003carchimate/themes\u003e\n'!theme archimate-saturated from \u003carchimate/themes\u003e\n'!theme archimate-standard from \u003carchimate/themes\u003e\n\n```\n\n### Using a version available on the internet\n\nYou will need to:\n1. download the latest version of `Archimate.puml`, including the themes folder and store them some place locally\n   * `./dist/plantuml/plantuml-stdlib/stdlib/archimate/Archimate.puml`\n   * `./dist/plantuml/plantuml-stdlib/stdlib/archimate/themes/` folder plus files\n2. Add a `!global $ARCH_LOCAL = %true()` to your PlantUML file prior to the include statement \n\n```plantuml\n\n!global $ARCH_LOCAL = %true()\n!$LOCAL_FOLDER = \"[path to the folder that holds Archimate.puml]\"\n!include $LOCAL_FOLDER/Archimate.puml\n\n' optionally choose one of the available themes\n'!theme archimate-alternate from $LOCAL_FOLDER/themes\n'!theme archimate-handwriting from $LOCAL_FOLDER/themes\n'!theme archimate-lowsaturation from $LOCAL_FOLDER/themes\n'!theme archimate-saturated from $LOCAL_FOLDER/themes\n'!theme archimate-standard from $LOCAL_FOLDER/themes\n```\n\n\u003e [!IMPORTANT]\n\u003e Using `!include` on `https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/dist/plantuml-stdlib/stdlib/archimate/Archimate.puml`\n\u003e **may** not work, because that file by default relies on the built-in themes, which may not be compatible with the latest version of `Archimate.puml`\n\u003e on `master`.\n\n## Usage\nAfter you have included `Archimate.puml` you can use the defined macros for ArchiMate elements. \n\n### ArchiMate Elements\nThe ArchiMate elements are defined in the following pattern, with two mandatory parameters and two optional parameters:\n```plantuml\nCategory_ElementName(nameOfTheElement, \"description\", $nest=%false(), $special=$ARCH_SPECIAL_SHAPES)\n```\n\nNesting and special shapes are explained further down this page.\n\nFor example:  \n* To define a `Stakeholder` element, which is part of `Motivation` category, the syntax will be\n    ```plantuml\n    Motivation_Stakeholder(StakeholderElement, \"Stakeholder Description\")\n    ```\n    Output:  \n    ![Stakeholder](./images/Example-Stakeholder.png)\n* To define a `Business Service` element,\n    ```plantuml\n    Business_Service(BService, \"Business Service\")\n    ```\n    Output:  \n    ![Business Service](./images/Example-BusinessService.png) \n\n### ArchiMate Relationships\nThe ArchiMate relationships are defined with the following pattern:\n```plantuml\nRel_RelationType(fromElement, toElement, \"description\")\n```\nand to define the direction / orientation of the two elements:\n```plantuml\nRel_RelationType_Direction(fromElement, toElement, \"description\")\n```\nThe `RelationTypes` supported are:\n - Access, Access_r, Access_rw, Access_w\n - Aggregation\n - Assignment\n - Association, Association_dir\n - Composition\n - Flow\n - Influence\n - Realization\n - Serving\n - Specialization\n - Triggering\n\nThe `Directions` supported are:\n - Up\n - Down\n - Left\n - Right\n\nFor example:\n* To denote a `composition` relationship between the Stakeholder and Business Service defined above, the syntax will be\n    ```plantuml\n    Rel_Composition(StakeholderElement, BService, \"Description for the relationship\")\n    ```\n    Output:  \n    ![Composition Relationship](./images/Example-Composition.png)\n* To orient the two elements in left-right position, the syntax will be\n    ```plantuml\n    Rel_Composition_Right(StakeholderElement, BService, \"Description for the relationship\")\n    ```\n    Output:  \n    ![Composition Relationship Right](./images/Example-CompositionRight.png)\n\n### ArchiMate Groups\nGroups in ArchiMate are denoted using one of the following 3 possible ways:\n```plantuml\nGroup(nameOfTheGroup, \"Group\"){\n    //Define the ArchiMate Elements\n}\n\nGrouping(nameOfTheGroup, \"Grouping\"){\n    //Define the ArchiMate Elements\n}\n\nOther_Grouping(nameOfTheGroup, \"Other_Grouping Type\"){\n    //Define the ArchiMate Elements\n}\n```\n\nFor example\n\n| Group Type     | Result                                                |\n|----------------|-------------------------------------------------------|\n| Group          | ![Group](./images/Example-Group.png)                  |\n| Grouping       | ![Grouping](./images/Example-Grouping.png)            |\n| Other_Grouping | ![Other_Grouping](./images/Example-OtherGrouping.png) |\n\n### Special shapes\nBy default, all shapes are rectangular (either with sharp, rounded, or beveled corners) and show a stereotype icon in the\ntop right. Some elements can be shown in a different shape, without the stereotype. This is controlled by setting\n`$ARCH_SPECIAL_SHAPES` to `%true()` (default is `%false()`). The supported elements have an optional named parameter that allows\nyou to override the setting for an individual shape.\n\nShapes that support special shapes are:\n* Business Actor\u003csup\u003e*\u003c/sup\u003e\n* Business Role\n* Business Service\u003csup\u003e*\u003c/sup\u003e\n* Business Product\n* Application Service\u003csup\u003e*\u003c/sup\u003e\n* Technology Node\n* Technology Artifact\n* Technology Service\u003csup\u003e*\u003c/sup\u003e\n* Motivation Stakeholder\n* Motivation Meaning\n* Motivation Value\u003csup\u003e*\u003c/sup\u003e\n* Strategy Value Stream\n    \n\u003e [!IMPORTANT]\n\u003e The special shapes marked with \u003csup\u003e*\u003c/sup\u003e do not support nesting other elements within them, so you need to add a \n\u003e `$nest=%true()` parameter when nesting using these elements with special shapes.\n\n```plantuml\n@startuml\n\n!global $ARCH_SPECIAL_SHAPES = %true()\n\n!include \u003carchimate/Archimate\u003e\n\nMotivation_Stakeholder(MS, \"Motivation Stakeholder\") {\n    Motivation_Stakeholder(MSI, \"Inner Stakeholder\", $special=%true())\n    Motivation_Stakeholder(MSI2, \"Another Inner Stakeholder\", $special=%false())\n}\nMotivation_Meaning(MM, \"Motivation Meaning\") {\n    Motivation_Meaning(MMI, \"Inner Meaning\", $special=%true())\n    Motivation_Meaning(MMI2, \"Another Inner Meaning\", $special=%false())\n}\nMotivation_Value(MV, \"Motivation Value\", $nest=%true()) {\n    Motivation_Value(MVI, \"Inner Value\", $special=%true())\n    Motivation_Value(MVI2, \"Another Inner Value\", $special=%false())\n}\nStrategy_ValueStream(SV, \"Strategy Value Stream\", $nest=%true()) {\n    Strategy_ValueStream(SVI, \"Inner Value Stream\", $special=%true())\n    Strategy_ValueStream(SVI2, \"Another Inner Value Stream\", $special=%false())\n}\n\nBusiness_Actor(BA, \"Business Actor\", $nest=%true()) {\n    Business_Actor(BAI, \"Inner Actor\", $special=%true())\n    Business_Actor(BAI2, \"Another Inner Actor\", $special=%false())\n}\nBusiness_Service(BS, \"Business Service\", $nest=%true()) {\n    Business_Service(BSI, \"Inner Service\", $special=%true())\n    Business_Service(BSI2, \"Another Inner Service\", $special=%false())\n}\nBusiness_Product(BP, \"Business Product\", $nest=%true()) {\n    Business_Product(BPI, \"Inner Product\", $special=%true())\n    Business_Product(BPI2, \"Another Inner Product\", $special=%false())\n}\n\nTechnology_Node(TN, \"Technology Node\"){\n    Technology_Node(TNI, \"Inner Node\", $special=%true())\n    Technology_Node(TNI2, \"Another Inner Node\", $special=%false())\n}\n\nTechnology_Artifact(TA, \"Technology Artifact\") {\n    Technology_Artifact(TAI, \"Inner Artifact\", $special=%true())\n    Technology_Artifact(TAI2, \"Another Inner Artifact\", $special=%false())\n}\n\n@enduml\n```\n\nResult:\n\n![Special Shapes for some types](./images/SpecialShapes.png)\n\n### Nesting of Components\nNesting allows grouping components hierarchically, improving diagram clarity. There are no limitations on the number of levels of nesting.\nThe implementation allows nesting of any components inside any other components. When nesting, the element will be displayed in its normal shape, with the archimate archetype on the top right corner.\n\nNesting is automatic by default, just add the nested elements between curly braces `{ ... }`:\n```plantuml\nCategory_ElementName(nameOfTheElement, \"description\") {\n    Category_ElementName(uniqueName, \"description)\n}\n```\n\nFor example:\n```plantuml\nBusiness_Product(\"BusProduct01\", \"Business Product 01\") {\n    Business_Service(\"BusService01\", \"Business Service 01\")\n    Business_Service(\"BusService02\", \"Business Service 02\")\n    Business_Service(\"BusService03\", \"Business Service 03\"){\n        Business_Function(\"BusFunction\", \"Business Function\")\n    }\n}\n\nTechnology_Node(\"TechDevice01\", \"Technology Device 01\") {\n    Technology_Node(\"TechDevice02\", \"Technology Device 02\")\n    Technology_Node(\"TechnDevice03\", \"Technology Device 03\") {\n        Technology_Node(\"TechnDevice04\", \"Technology Device 04\")\n        Technology_Node(\"TechnDevice05\", \"Technology Device 05\")\n    }\n}\n\n```\nOutput:\n\n![Nesting Example](./images/Example-Nesting.png)\n\n#### Nesting with special shapes\n\n\u003e [!IMPORTANT]\n\u003e As mentioned above, some elements support special shapes. However, when using special shapes, nesting is not always possible using the \n\u003e special shape. This applies to all `Service` elements, the `Motivation_Value` element, and the `Business_Actor` element. If you have\n\u003e special shapes active, you have to add a `$nest=%true()` parameter to these elements to avoid errors or unexpected results.\n\n### Theme Support\nTheme support is enabled and 5 variations are available. All the themes are based on Archimate specifications.\n\nTheme can be enabled by adding the following line.\n```plantuml\n!theme [theme-name] from \u003carchimate/themes\u003e\n\n// Example\n!theme archimate-saturated from \u003carchimate/themes\u003e\n```\n\n| Theme Name               | Preview                                               |\n|--------------------------|-------------------------------------------------------|\n| Default (No line added)  | ![default](./images/theme-default.png)                |\n| archimate-standard       | ![standard](./images/theme-standard.png)              |\n| archimate-alternate      | ![alternate](./images/theme-alternate.png)            |\n| archimate-saturated      | ![saturated](./images/theme-saturated.png)            |\n| archimate-lowsaturation  | ![low saturation](./images/theme-lowsaturation.png)   |\n| archimate-handwriting    | ![handwriting](./images/theme-handwriting.png)        |\n\n### Sequence Diagrams using Archimate elements\nAdditional support for using ArchiMate elements in sequence diagrams is provided by setting a global variable prior to activating ArchiMate support:\n\n```puml\n!global $ARCH_SEQUENCE_SUPPORT = %true()\n!include \u003carchimate/Archimate\u003e\n```\nAlternatively, you can choose to only include the sequence support file directly:\n```puml\n!include \u003carchimate/ArchimateSequenceDiagramSupport\u003e\n```\n\nBoth methods define additional procedures that can be used to create participants in sequence diagrams using Archimate elements.\nFor example:\n\n```puml\n@startuml\n!global $ARCH_SEQUENCE_SUPPORT = %true()\n!include \u003carchimate/Archimate\u003e\n\ntitle Archi Print Usage\n\n' Define Elements\n$actor(\"Architect\",\"architect\")\n$applicationComponent(\"Archi\",\"archi\")\n$applicationFunction(\"Update\\nModel\",\"update\")\n$applicationFunction(\"Print\\nView\",\"print\")\n$systemSoftware(\"Windows\\nPrint\\nService\",\"windowsPrint\")\n$equipment(\"Printer\", \"printer\")\n\n' Define Sequence\narchitect-\u003earchi ++\narchi-\u003eupdate ++ : Make changes\nnote right update #FFFFA5: \u003c\u0026document\u003e Not exactly correct!\\nBut you get the idea.\nreturn Updated Model\narchi -\u003eprint ++ : Click print\nprint -\\windowsPrint ++\nprint –\u003e archi -–: Sent to printer\nwindowsPrint -\u003e printer ++\nreturn Complete\narchi –\u003e architect --\n\n@enduml\n```\n\nOutput:\n\n![Sequence Diagram using Archimate elements](./images/Archimate-Sequence-Diagram.png)\n\nCall the procedure with a label, and if the label is not unique within the diagram also provide an ID to refer to the participant.\n```puml\n$elementType(\"Label\")\n$elementType(\"Label\", ID)\n```\n\nThe supported elements for sequence diagrams are listed in the table below.\n\n\u003cdetails\u003e\n\n\u003csummary\u003eClick to show the table\u003c/summary\u003e\n\n| Aspect                       | Type                  | Procedure                   |\n|------------------------------|-----------------------|-----------------------------|\n| Application                  | Component             | `$applicationComponent`     |\n| Application                  | Collaboration         | `$applicationCollaboration` |\n| Application                  | Data Object           | `$dataObject`               |\n| Application                  | Event                 | `$applicationEvent`         |\n| Application                  | Function              | `$applicationFunction`      |\n| Application                  | Interaction           | `$applicationInteraction`   |\n| Application                  | Interface             | `$applicationInterface`     |\n| Application                  | Process               | `$applicationProcess`       |\n| Application                  | Service               | `$applicationService`       |\n| Business                     | Actor                 | `$actor`                    |\n| Business                     | Collaboration         | `$businessCollaboration`    |\n| Business                     | Contract              | `$contract`                 |\n| Business                     | Event                 | `$businessEvent`            |\n| Business                     | Function              | `$businessFunction`         |\n| Business                     | Interaction           | `$businessInteraction`      |\n| Business                     | Interface             | `$businessInterface`        |\n| Business                     | Object                | `$businessObject`           |\n| Business                     | Process               | `$businessProcess`          |\n| Business                     | Product               | `$product`                  |\n| Business                     | Role                  | `$role`                     |\n| Business                     | Service               | `$businessService`          |\n| Business                     | Representation        | `$representation`           |\n| Implementation and Migration | Deliverable           | `$deliverable`              |\n| Implementation and Migration | Gap                   | `$gap`                      |\n| Implementation and Migration | Implementation Event  | `$implementationEvent`      |\n| Implementation and Migration | Plateau               | `$plateau`                  |\n| Implementation and Migration | Work Package          | `$workPackage`              |\n| Motivation                   | Assessment            | `$assessment`               |\n| Motivation                   | Constraint            | `$constraint`               |\n| Motivation                   | Driver                | `$driver`                   |\n| Motivation                   | Goal                  | `$goal`                     |\n| Motivation                   | Meaning               | `$meaning`                  |\n| Motivation                   | Outcome               | `$outcome`                  |\n| Motivation                   | Principle             | `$principle`                |\n| Motivation                   | Requirement           | `$requirement`              |\n| Motivation                   | Stakeholder           | `$stakeholder`              |\n| Motivation                   | Value                 | `$value`                    |\n| Strategy                     | Capability            | `$capability`               |\n| Strategy                     | Course Of Action      | `$courseOfAction`           |\n| Strategy                     | Resource              | `$resource`                 |\n| Strategy                     | Value Stream          | `$valueStream`              |\n| Technology                   | Artifact              | `$artifact`                 |\n| Technology                   | Collaboration         | `$technologyCollaboration`  |\n| Technology                   | Communication Network | `$communicationNetwork`     |\n| Technology                   | Device                | `$device`                   |\n| Technology                   | Event                 | `$technologyEvent`          |\n| Technology                   | Function              | `$technologyFunction`       |\n| Technology                   | Interaction           | `$technologyInteraction`    |\n| Technology                   | Interface             | `$technologyInterface`      |\n| Technology                   | Node                  | `$node`                     |\n| Technology                   | Path                  | `$path`                     |\n| Technology                   | Process               | `$technologyProcess`        |\n| Technology                   | Service               | `$technologyService`        |\n| Technology                   | System Software       | `$systemSoftware`           |\n| Technology - Physical        | Distribution Network  | `$distributionNetwork`      |\n| Technology - Physical        | Equipment             | `$equipment`                |\n| Technology - Physical        | Facility              | `$facility`                 |\n| Technology - Physical        | Material              | `$material`                 |\n\n\u003c/details\u003e\n\n## Example\n```plantuml\n@startuml\n!include \u003carchimate/Archimate\u003e\n!theme archimate-standard from \u003carchimate/themes\u003e\n\ntitle Archimate Sample - Requirement \u0026 Application Services\n\n'Elements'\nMotivation_Requirement(ReqPayrollStandard, \"Do Payroll with a standard system\")\nMotivation_Requirement(ReqBudgetPlanning, \"Do budget planning within the ERP system\")\n\nApplication_Service(ASPayroll,\"Payroll Service\")\nApplication_Service(ASBudgetPlanning,\"Budget Planning Service\")\nApplication_Component(ACSAPFinanceAccRec, \"SAP Finance - Accounts Recievables\")\nApplication_Component(ACSAPHR, \"SAP Human Resources\")\nApplication_Component(ACSAPFin, \"SAP Finance\")\nApplication_Component(ACSAP,\"SAP\") \n\n'Relationships'\nRel_Realization_Up(ASPayroll, ReqPayrollStandard)\nRel_Realization_Up(ASBudgetPlanning, ReqBudgetPlanning)\nRel_Realization_Up(ACSAPFinanceAccRec, ASBudgetPlanning)\nRel_Realization_Up(ACSAPHR, ASPayroll)\n\nRel_Composition_Up(ACSAPFin, ACSAPFinanceAccRec)\nRel_Composition_Up(ACSAP, ACSAPHR)\nRel_Composition_Up(ACSAP, ACSAPFin)\n@enduml\n```\n\nOutput:  \n![Archimate-PlantUML Sample image - Requirement \u0026 Application Services](./images/Archimate%20Sample%20-%20Requirement%20%26%20Application%20Services.png)\n\n## Contributing\nIf you have any ideas, [open an issue](https://github.com/plantuml-stdlib/Archimate-PlantUML/issues/new) or fork the repository and submit a pull request.\n\n## License\nThis project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details\n\n## Acknowledgments\n* [PlantUML Reference Guide](http://plantuml.com/PlantUML_Language_Reference_Guide.pdf) - PlantUML Reference Guide\n* [Archimate 3.1 Specification](http://pubs.opengroup.org/architecture/archimate3-doc/) - Archimate Specifications\n* [Plant UML Archimate Specifications](http://plantuml.com/archimate-diagram) - for archimate spec in PlantUML\n* [C4-PlantUML](https://github.com/plantuml-stdlib/C4-PlantUML) - for inspiration, base structure and scripts idea\n* Steven Mileham, for allowing inclusion of his [Sequence Diagram support for Archimate elements](https://smileham.co.uk/2019/04/23/archimate-plantuml-sequence-diagram-joy/)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fplantuml-stdlib%2Farchimate-plantuml","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fplantuml-stdlib%2Farchimate-plantuml","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fplantuml-stdlib%2Farchimate-plantuml/lists"}