Architecture Definition Document
type: DeliverableTemplate
definition: The primary ArchiMate 4.0 deliverable documenting the target architecture across business, application, and technology domains. Uses the domain-based structure of ArchiMate 4.0 with merged cross-domain behavior elements.
template resource: templates/architecture-definition-document.md.hbs
template requires viewpoint: Organization
template requires viewpoint: ProcessCooperationVP
template requires viewpoint: ApplicationStructureVP
template requires viewpoint: TechnologyVP
template requires viewpoint: LayeredVP
template requires viewpoint: ImplementationDeploymentVP
template has section: 1. Business Domain
template has section: 2. Process Cooperation
template has section: 3. Application Domain
template has section: 4. Technology Domain
template has section: 5. Cross-Domain Overview
template has section: 6. Implementation & Deployment
template targets purpose: Designing
template targets purpose: Informing
template has format: MarkdownFormat
template has format: HTMLFormat
template has format: PDFFormat

1. Business Domain
type: TemplateSection
section order: 1
section viewpoint: Organization
section result key: businessDomain
definition: Business actors, roles, collaborations, and organizational structure.
section query: PREFIX am4: <https://meta.linked.archi/archimate4/onto#> PREFIX arch: <https://meta.linked.archi/core#> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> SELECT ?element ?label ?type ?description ?assignedTo WHERE { ?element a ?type ; skos:prefLabel ?label . VALUES ?type { am4:BusinessActor am4:Role am4:Collaboration am4:BusinessInterface am4:Location } OPTIONAL { ?element skos:definition ?description } OPTIONAL { ?element am4:assignedTo ?target . ?target skos:prefLabel ?assignedTo . FILTER(lang(?assignedTo) = "en") } FILTER(lang(?label) = "en") } ORDER BY ?type ?label

2. Process Cooperation
type: TemplateSection
section order: 2
section viewpoint: ProcessCooperationVP
section result key: processCooperation
definition: Cross-domain processes, functions, events, services, and their interactions.
section query: PREFIX am4: <https://meta.linked.archi/archimate4/onto#> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> SELECT ?element ?label ?type ?description ?flowsTo ?serves WHERE { ?element a ?type ; skos:prefLabel ?label . VALUES ?type { am4:Process am4:Function am4:Event am4:Service am4:BusinessObject am4:DataObject } OPTIONAL { ?element skos:definition ?description } OPTIONAL { ?element am4:flowsTo ?ft . ?ft skos:prefLabel ?flowsTo . FILTER(lang(?flowsTo) = "en") } OPTIONAL { ?element am4:serves ?sv . ?sv skos:prefLabel ?serves . FILTER(lang(?serves) = "en") } FILTER(lang(?label) = "en") } ORDER BY ?type ?label

3. Application Domain
type: TemplateSection
section order: 3
section viewpoint: ApplicationStructureVP
section result key: applicationDomain
definition: Application components, interfaces, and data objects.
section query: PREFIX am4: <https://meta.linked.archi/archimate4/onto#> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> SELECT ?element ?label ?type ?description ?serves ?accesses WHERE { ?element a ?type ; skos:prefLabel ?label . VALUES ?type { am4:ApplicationComponent am4:ApplicationInterface am4:DataObject } OPTIONAL { ?element skos:definition ?description } OPTIONAL { ?element am4:serves ?sv . ?sv skos:prefLabel ?serves . FILTER(lang(?serves) = "en") } OPTIONAL { ?element am4:accesses ?ac . ?ac skos:prefLabel ?accesses . FILTER(lang(?accesses) = "en") } FILTER(lang(?label) = "en") } ORDER BY ?type ?label

4. Technology Domain
type: TemplateSection
section order: 4
section viewpoint: TechnologyVP
section result key: technologyDomain
definition: Nodes, devices, system software, networks, equipment, facilities.
section query: PREFIX am4: <https://meta.linked.archi/archimate4/onto#> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> SELECT ?element ?label ?type ?description ?assignedTo WHERE { ?element a ?type ; skos:prefLabel ?label . VALUES ?type { am4:Node am4:Device am4:SystemSoftware am4:Path am4:CommunicationNetwork am4:DistributionNetwork am4:Equipment am4:Facility am4:TechnologyInterface am4:Artifact am4:Material } OPTIONAL { ?element skos:definition ?description } OPTIONAL { ?element am4:assignedTo ?at . ?at skos:prefLabel ?assignedTo . FILTER(lang(?assignedTo) = "en") } FILTER(lang(?label) = "en") } ORDER BY ?type ?label

5. Cross-Domain Overview
type: TemplateSection
section order: 5
section viewpoint: LayeredVP
section result key: crossDomainOverview
definition: Cross-domain serving and realization relationships.
section query: PREFIX am4: <https://meta.linked.archi/archimate4/onto#> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT ?source ?sourceLabel ?relType ?target ?targetLabel WHERE { { ?source am4:serves ?target . BIND("serves" AS ?relType) } UNION { ?source am4:realizes ?target . BIND("realizes" AS ?relType) } ?source skos:prefLabel ?sourceLabel . ?target skos:prefLabel ?targetLabel . FILTER(lang(?sourceLabel) = "en") FILTER(lang(?targetLabel) = "en") } ORDER BY ?relType ?sourceLabel

6. Implementation & Deployment
type: TemplateSection
section order: 6
section viewpoint: ImplementationDeploymentVP
section result key: implementationDeployment
definition: Work packages, deliverables, plateaus, and artifact deployment.
section query: PREFIX am4: <https://meta.linked.archi/archimate4/onto#> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> SELECT ?element ?label ?type ?description ?realizes ?deployedOn WHERE { ?element a ?type ; skos:prefLabel ?label . VALUES ?type { am4:WorkPackage am4:Deliverable am4:Plateau am4:Artifact am4:Node am4:Device am4:SystemSoftware } OPTIONAL { ?element skos:definition ?description } OPTIONAL { ?element am4:realizes ?rl . ?rl skos:prefLabel ?realizes . FILTER(lang(?realizes) = "en") } OPTIONAL { ?element am4:assignedTo ?dep . ?dep skos:prefLabel ?deployedOn . FILTER(lang(?deployedOn) = "en") } FILTER(lang(?label) = "en") } ORDER BY ?type ?label

Architecture Requirements Specification
type: DeliverableTemplate
definition: Documents architecture requirements, goals, and constraints.
template resource: templates/architecture-requirements-spec.md.hbs
template requires viewpoint: StakeholderVP
template requires viewpoint: GoalRealization
template requires viewpoint: RequirementsRealization
template requires viewpoint: MotivationVP
template targets purpose: Deciding
template has format: MarkdownFormat
template has format: PDFFormat

Architecture Principles Document
type: DeliverableTemplate
definition: Documents architecture principles and strategy alignment.
template resource: templates/architecture-principles-document.md.hbs
template requires viewpoint: MotivationVP
template requires viewpoint: StrategyVP
template targets purpose: Governing
template has format: MarkdownFormat
template has format: PDFFormat