ArchiMate — One Service, All the Way Down
A single vertical slice from a customer-facing service to the artifact that implements it, which is the view that answers 'what breaks if this server goes down'. Every layer boundary is crossed by realization going up and serving going across, which is the ArchiMate pattern worth learning first.
Make it your own.
title "Balance enquiry, top to bottom"
business-actor Cust "Account holder"
business-service BalSvc "Balance enquiry"
business-process Enquire "Check balance"
business-role Channel "Digital channel"
business-object Balance "Account balance"
layer application
application-service ApiSvc "Account API"
application-component Mobile "Mobile app"
application-component Core "Core banking"
application-function Compute "Compute balance"
data-object AcctRec "Account record"
layer technology
technology-service Db "Ledger database service"
node Mainframe "Mainframe LPAR"
system-software Db2 "Db2"
artifact CoreLoad "Core banking load module"
Cust assigned-to Channel
Channel assigned-to Enquire
Enquire realizes BalSvc
Enquire reads Balance
ApiSvc serves Enquire
Mobile serves Enquire
Core realizes ApiSvc
Compute assigned-to Core
Compute accesses AcctRec
Db serves Core
Db2 realizes Db
Mainframe composed-of Db2
CoreLoad assigned-to Mainframe
CoreLoad assigned-to Core
AcctRec associated-with Balance