| View | Viewpoint |
|---|
| Payments |
Integration Point |
| Payments |
Adoption Recommendation |
| Payments |
Maturity Assessment |
| Payments |
Team |
| Payments |
Data Classification |
| Payments |
Processing Purpose |
| Payments |
Legal Basis |
| Payments |
owned by |
| Payments |
has recommendation |
| Payments |
has maturity |
| Payments |
integrates with |
| Payments |
carries data |
| Payments |
exposed by |
| Payments |
has classification |
| Payments |
processed for |
| Payments |
has legal basis |
| Payments |
closes gap |
| Payments |
Payments Team |
| Payments |
Platform Engineering |
| Payments |
Customer Experience |
| Payments |
Data Platform |
| Payments |
Order Management |
| Payments |
Identity & Access |
| Payments |
Finance IT |
| Payments |
HR Systems |
| Payments |
Kubernetes 1.29 |
| Payments |
PostgreSQL 16 |
| Payments |
Apache Kafka 3.7 |
| Payments |
Redis 7 |
| Payments |
Java 21 (LTS) |
| Payments |
Node.js 22 |
| Payments |
Oracle Database 19c |
| Payments |
MuleSoft ESB 3.x |
| Payments |
MongoDB 7 |
| Payments |
Terraform 1.8 |
| Payments |
SQL Server 2016 |
| Payments |
Argo CD 2.11 |
| Payments |
Payment Gateway |
| Payments |
Payment Ledger |
| Payments |
Customer Portal |
| Payments |
ACME Mobile App |
| Payments |
Order Service |
| Payments |
Inventory Service |
| Payments |
Identity Provider (IdP) |
| Payments |
Notification Service |
| Payments |
Data Warehouse |
| Payments |
ERP System (SAP) |
| Payments |
HRIS (PeopleSoft) |
| Payments |
Product Catalog |
| Payments |
Fraud Detection Engine |
| Payments |
API Gateway |
| Payments |
Legacy Payments (COBOL) |
| Payments |
Payment API (REST) |
| Payments |
Order Events (Kafka topic: order.*) |
| Payments |
Payment Events (Kafka topic: payment.*) |
| Payments |
Identity Token Endpoint (OIDC) |
| Payments |
Inventory API (gRPC) |
| Payments |
ERP Integration (SOAP/ESB) |
| Payments |
Customer Record |
| Payments |
Payment Transaction |
| Payments |
Order Record |
| Payments |
Employee Record |
| Payments |
Financial Transaction |
| Payments |
Product Data |
| Payments |
Analytics Event |
| Payments |
Fraud Signal |
| Payments |
Contract Fulfilment |
| Payments |
Legal Obligation |
| Payments |
Legitimate Interest |
| Payments |
GDPR Art. 6(1)(b) — Contract |
| Payments |
GDPR Art. 6(1)(c) — Legal Obligation |
| Payments |
GDPR Art. 6(1)(f) — Legitimate Interest |
| Payments |
Payment Processing |
| Payments |
Customer Onboarding |
| Payments |
Order Fulfilment |
| Payments |
Fraud Management |
| Payments |
Data Analytics |
| Payments |
Identity & Access Management |
| Payments |
Supply Chain Management |
| Payments |
Financial Management |
| Payments |
Talent Management |
| Payments |
Payment Processing — Level 3 (Target: 4) |
| Payments |
Customer Onboarding — Level 2 (Target: 4) |
| Payments |
Order Fulfilment — Level 3 (Target: 4) |
| Payments |
Fraud Management — Level 4 (Target: 5) |
| Payments |
Data Analytics — Level 2 (Target: 4) |
| Payments |
Identity & Access Management — Level 4 (Target: 4) |
| Payments |
Supply Chain Management — Level 2 (Target: 3) |
| Payments |
No real-time payment capability |
| Payments |
High onboarding friction |
| Payments |
Data silos across business units |
| Payments |
Payment Modernization Programme |
| Payments |
Customer Onboarding Revamp |
| Payments |
Enterprise Data Platform Initiative |
| Payments |
Payment Platform Technology Decision |
| Payments |
Legacy payment system cannot support real-time processing |
| Payments |
Option A: SaaS Payment Processor (Stripe) |
| Payments |
Option B: Build In-House |
| Payments |
Option C: Hybrid (Stripe + Internal Ledger) |
| Payments |
Artifact Catalog Home |
| Payments |
Artifact Counts by CSVLOD Type |
| Payments |
Viewpoint Summary |
| Payments |
Application Landscape Catalog |
| Payments |
Application Inventory |
| Payments |
Integration Points |
| Payments |
Technology Dependencies |
| Payments |
Technology Radar |
| Payments |
Technologies by Adoption Level |
| Payments |
Capability Heat Map |
| Payments |
Capabilities with Maturity |
| Payments |
Gaps and Initiatives |
| Payments |
Data Flow Map |
| Payments |
Data Objects with Classification |
| Payments |
Processing Purposes and Legal Basis |
| Payments |
ACME Corp Architecture Framework |
| Payments |
ACME Corp Metamodel |
| Payments |
ACME Corp Architecture Classifications |
| Payments |
Adoption Levels |
| Payments |
Adopt |
| Payments |
Trial |
| Payments |
Hold |
| Payments |
Retire |
| Payments |
Data Sensitivity |
| Payments |
Public |
| Payments |
Internal |
| Payments |
Personal Data |
| Payments |
Special Category |
| Payments |
Maturity Levels |
| Payments |
Level 1 — Initial |
| Payments |
Level 2 — Managed |
| Payments |
Level 3 — Defined |
| Payments |
Level 4 — Quantitatively Managed |
| Payments |
Level 5 — Optimizing |
| Payments |
ACME Asset Lifecycle |
| Payments |
Lifecycle Stages |
| Payments |
Planned |
| Payments |
Current |
| Payments |
Phase-out |
| Payments |
Retired |
| Payments |
ACME Corp Viewpoint Catalog |
| Payments |
Strategic Viewpoints |
| Payments |
Optimization Viewpoints |
| Payments |
Delivery Viewpoints |
| Payments |
Technology Radar |
| Payments |
Application Landscape |
| Payments |
Data Flow Map |
| Payments |
Capability Heat Map |
| Payments |
Solution Overview |
| Payments |
Deciding |
| Payments |
Designing |
| Payments |
Informing |
| Payments |
Governing |
| Payments |
Sales |
| Payments |
Order Desk |
| Payments |
Order Handling |
| Payments |
Billing Run |
| Payments |
Order Entry |
| Payments |
Order Service |
| Payments |
Pricing Service |
| Payments |
Shipping Service |
| Payments |
Invoicing Service |
| Payments |
Delivery Service |
| Payments |
Order Management |
| Payments |
Pricing Engine |
| Payments |
Discount Engine |
| Payments |
Reporting |
| Payments |
Order Capture |
| Payments |
Price Calculation |
| Payments |
App Server |
| Payments |
order.war |
| Payments |
Runtime |
| Payments |
Database |
| Payments |
Message Broker |
| Payments |
Pricing Node A |
| Payments |
Pricing Node B |
| Payments |
Print Server |
| Payments |
Order Record |
| Payments |
Price List |
| Payments |
Archive Record |
| Payments |
Customer Record |
| Payments |
Order Fulfilment |
| Payments |
Partner Management |
| Payments |
Fast Delivery |
| Payments |
Traceability |
| Payments |
Audit Trail |
| Payments |
Warehouse |
| Payments |
Example presentation contexts |
| Payments |
Architect |
| Payments |
Developer |
| Payments |
Executive |
| Payments |
Example notation |
| Payments |
Payments |
| Payments |
Payment gateway |
| Payments |
Ledger |
| Payments |
Checkout |
| Payments |
Payments |
| Payments |
Component |
| Payments |
Connector |
| Payments |
MessagingConnector |
| Payments |
PubSub |
| Payments |
MessageQueue |
| Payments |
RequestResponse |
| Payments |
HTTPAPI |
| Payments |
RPC |
| Payments |
SOAP |
| Payments |
DataFlowConnector |
| Payments |
Pipe |
| Payments |
BatchConnector |
| Payments |
DataConnector |
| Payments |
DBConnector |
| Payments |
FileShareConnector |
| Payments |
FTPConnector |
| Payments |
GITConnector |
| Payments |
Filter |
| Payments |
port |
| Payments |
Port |
| Payments |
qualified Port |
| Payments |
role |
| Payments |
Role |
| Payments |
qualified Role |
| Payments |
inPort |
| Payments |
InPort |
| Payments |
outPort |
| Payments |
OutPort |
| Payments |
proxyOf |
| Payments |
ProxyOf |
| Payments |
hasProxy |
| Payments |
HasProxy |
| Payments |
subscribedTo |
| Payments |
publishTo |
| Payments |
enqueue |
| Payments |
dequeue |
| Payments |
providesService |
| Payments |
invokesService |
| Payments |
readsRequest |
| Payments |
sendRequest |
| Payments |
readsReply |
| Payments |
sendReply |
| Payments |
flowsTo |
| Payments |
flowsFrom |
| Payments |
accessDataSource |
| Payments |
provideDataSource |
| Payments |
readsFrom |
| Payments |
writesTo |
| Payments |
provideDataReads |
| Payments |
provideDataWrites |
| Payments |
realizedByConnector |
| Payments |
Microservice |
| Payments |
API Gateway |
| Payments |
Container |
| Payments |
Kubernetes Cluster |
| Payments |
Message Broker |
| Payments |
Event Topic |
| Payments |
Managed Database |
| Payments |
Cache Store |
| Payments |
Observability Stack |
| Payments |
resilience level |
| Payments |
deployment strategy |
| Payments |
service tier |
| Payments |
container image |
| Payments |
replica count |
| Payments |
topic partitions |
| Payments |
database engine |
| Payments |
publishes to |
| Payments |
Publishing |
| Payments |
subscribes to |
| Payments |
Subscription |
| Payments |
deployed in |
| Payments |
Deployment |
| Payments |
Service Catalog |
| Payments |
Service Inventory |
| Payments |
Event-Driven Dependencies |
| Payments |
Deployment Status |
| Payments |
Deployment Guide |
| Payments |
Kubernetes Clusters |
| Payments |
Container Inventory |
| Payments |
Cloud Platform Architecture |
| Payments |
Cloud Platform Metamodel |
| Payments |
Cloud Platform Classification |
| Payments |
Runtime Services |
| Payments |
Data Services |
| Payments |
Integration Services |
| Payments |
Observability |
| Payments |
Infrastructure |
| Payments |
Cloud Platform Reference Data |
| Payments |
Resilience Levels |
| Payments |
Critical |
| Payments |
High |
| Payments |
Medium |
| Payments |
Low |
| Payments |
Deployment Strategies |
| Payments |
Blue-Green |
| Payments |
Canary |
| Payments |
Rolling |
| Payments |
Recreate |
| Payments |
Service Tiers |
| Payments |
Tier 1 (99.99%) |
| Payments |
Tier 2 (99.9%) |
| Payments |
Tier 3 (99%) |
| Payments |
Database Engines |
| Payments |
PostgreSQL |
| Payments |
MySQL |
| Payments |
MongoDB |
| Payments |
Redis |
| Payments |
Payment Platform |
| Payments |
Order Service |
| Payments |
Payment Service |
| Payments |
Notification Service |
| Payments |
Fraud Detection Service |
| Payments |
Reporting Service |
| Payments |
Payment API Gateway |
| Payments |
Orders Database |
| Payments |
Payments Database |
| Payments |
Session Cache (Redis) |
| Payments |
Kafka Cluster |
| Payments |
order-events |
| Payments |
payment-events |
| Payments |
fraud-alerts |
| Payments |
Observability Stack (Prometheus + Grafana + Jaeger) |
| Payments |
Production Cluster (eu-west-1) |
| Payments |
order-service container |
| Payments |
payment-service container |
| Payments |
notification-service container |
| Payments |
fraud-detection container |
| Payments |
reporting-service container |
| Payments |
Platform Engineer |
| Payments |
Solution Architect |
| Payments |
Site Reliability Engineer |
| Payments |
Developer |
| Payments |
Service Dependency View |
| Payments |
Deployment View |
| Payments |
Data Flow View |
| Payments |
Platform Overview |
| Payments |
Component |
| Payments |
Connector |
| Payments |
MessagingConnector |
| Payments |
PubSub |
| Payments |
MessageQueue |
| Payments |
RequestResponse |
| Payments |
HTTPAPI |
| Payments |
RPC |
| Payments |
gRPC |
| Payments |
SOAP |
| Payments |
DataFlowConnector |
| Payments |
Pipe |
| Payments |
BatchConnector |
| Payments |
SharedDataConnector |
| Payments |
DBConnector |
| Payments |
FileShareConnector |
| Payments |
FTPConnector |
| Payments |
GITConnector |
| Payments |
Filter |
| Payments |
port |
| Payments |
Port |
| Payments |
qualified Port |
| Payments |
role |
| Payments |
Role |
| Payments |
qualified Role |
| Payments |
inPort |
| Payments |
InPort |
| Payments |
outPort |
| Payments |
OutPort |
| Payments |
proxyOf |
| Payments |
ProxyOf |
| Payments |
hasProxy |
| Payments |
HasProxy |
| Payments |
subscribedTo |
| Payments |
publishTo |
| Payments |
enqueue |
| Payments |
dequeue |
| Payments |
providesService |
| Payments |
invokesService |
| Payments |
source |
| Payments |
sink |
| Payments |
realizedByConnector |
| Payments |
Example Element |
| Payments |
Invokes |
| Payments |
Claims handling |
| Payments |
Cloud Server |
| Payments |
Regulatory Constraint |
| Payments |
Strategic Capability |
| Payments |
Organisation |
| Payments |
Hosting |
| Payments |
Legacy |
| Payments |
Customer |
| Payments |
Claims Clerk |
| Payments |
Application Server |
| Payments |
Cloud Server 1 |
| Payments |
Handle Claim |
| Payments |
Register Claim |
| Payments |
Claim Service |
| Payments |
Orphan Service |
| Payments |
CRM |
| Payments |
crm |
| Payments |
Policy Administration |
| Payments |
Claims Portal |
| Payments |
Broker Portal |
| Payments |
Customer Management |
| Payments |
Customer Lookup |
| Payments |
Customer Data |
| Payments |
Policy Data |
| Payments |
CEO |
| Payments |
Faster claims |
| Payments |
Claims settled within 24h |
| Payments |
Unrealised requirement |
| Payments |
Keep claims for ten years |
| Payments |
Digital first |
| Payments |
Unbacked principle |
| Payments |
Claims Management |
| Payments |
Fraud Detection |
| Payments |
Customer Insight |
| Payments |
CRM upgrade |
| Payments |
Upgraded CRM |
| Payments |
Baseline |
| Payments |
Target |
| Payments |
Bank |
| Payments |
Bank |
| Payments |
NordFreight Organization |
| Payments |
Organization Chart |
| Payments |
Actor Catalogue |
| Payments |
Dispatcher |
| Payments |
Account Manager |
| Payments |
Customer Liaison |
| Payments |
Service Desk |
| Payments |
Rotterdam Hub |
| Payments |
fulfils |
| Payments |
UML Reference Example |
| Payments |
Ordering |
| Payments |
Order |
| Payments |
Line Item |
| Payments |
Item |
| Payments |
Priceable |
| Payments |
Currency |
| Payments |
EUR |
| Payments |
USD |
| Payments |
total |
| Payments |
lines |
| Payments |
calculateTotal |
| Payments |
Order realizes Priceable |
| Payments |
Order Lifecycle |
| Payments |
Idle |
| Payments |
Submitted |
| Payments |
Fulfilled |
| Payments |
submit |
| Payments |
Place Order |
| Payments |
customer |
| Payments |
orderService |
| Payments |
submit() |
| Payments |
NordFreight Logistics — Architecture Model |
| Payments |
EU Customs Compliance |
| Payments |
Operational Efficiency |
| Payments |
Carbon Neutral Operations by 2030 |
| Payments |
Shipper |
| Payments |
Receiver |
| Payments |
Cloud-First Principle |
| Payments |
API-First Design |
| Payments |
Shipment Tracking |
| Payments |
Freight Booking |
| Payments |
Customs Clearance |
| Payments |
Route Optimisation |
| Payments |
Fleet Management |
| Payments |
Booking Process |
| Payments |
Shipment Tracking Service |
| Payments |
Customs Declaration Process |
| Payments |
Freight Operations |
| Payments |
Customs Broker |
| Payments |
Shipment |
| Payments |
Waybill |
| Payments |
Booking Confirmed |
| Payments |
Shipment Delivered |
| Payments |
Transport Management System |
| Payments |
Tracking Portal |
| Payments |
Customs Gateway |
| Payments |
Route Optimisation Engine |
| Payments |
Shipment Data |
| Payments |
Customs Declaration Data |
| Payments |
Tracking API |
| Payments |
Booking API |
| Payments |
Azure North Europe |
| Payments |
AKS Kubernetes Cluster |
| Payments |
IoT Tracking Gateway |
| Payments |
Azure Event Hubs |
| Payments |
Azure Database for PostgreSQL |
| Payments |
Platform Modernisation Programme |
| Payments |
EU Customs Integration Project |
| Payments |
Target Architecture 2027 |
| Payments |
NordFreight Layered View |
| Payments |
NordFreight Capability Map |
| Payments |
NordFreight Application Cooperation |
| Payments |
Sales |
| Payments |
Order Desk |
| Payments |
Order Handling |
| Payments |
Billing Run |
| Payments |
Order Entry |
| Payments |
Order Service |
| Payments |
Pricing Service |
| Payments |
Shipping Service |
| Payments |
Invoicing Service |
| Payments |
Order Management |
| Payments |
Pricing Engine |
| Payments |
Discount Engine |
| Payments |
Reporting |
| Payments |
Order Capture |
| Payments |
Price Calculation |
| Payments |
App Server |
| Payments |
order.war |
| Payments |
Runtime |
| Payments |
Database |
| Payments |
Message Broker |
| Payments |
Pricing Node A |
| Payments |
Pricing Node B |
| Payments |
Print Server |
| Payments |
Order Record |
| Payments |
Price List |
| Payments |
Archive Record |
| Payments |
Customer Record |
| Payments |
Order Fulfilment |
| Payments |
Partner Management |
| Payments |
Fast Delivery |
| Payments |
Traceability |
| Payments |
Audit Trail |
| Payments |
Warehouse |
| Payments |
PayFlow — Backstage Catalog Model |
| Payments |
Message Broker |
| Payments |
Cache |
| Payments |
Payments |
| Payments |
Merchant Services |
| Payments |
Platform |
| Payments |
Payments Squad |
| Payments |
Merchant Squad |
| Payments |
Platform Team |
| Payments |
SRE Team |
| Payments |
alice.chen |
| Payments |
bob.eriksson |
| Payments |
Payment Gateway |
| Payments |
Merchant Portal |
| Payments |
Observability Platform |
| Payments |
payment-processor |
| Payments |
fraud-service |
| Payments |
fraud-model-scorer |
| Payments |
payout-service |
| Payments |
merchant-onboarding |
| Payments |
reporting-service |
| Payments |
webhook-dispatcher |
| Payments |
Payments API (OpenAPI) |
| Payments |
Merchant API (OpenAPI) |
| Payments |
Payment Events (AsyncAPI) |
| Payments |
Fraud Scoring API (gRPC) |
| Payments |
payments-db (PostgreSQL) |
| Payments |
merchant-db (PostgreSQL) |
| Payments |
event-bus (Kafka) |
| Payments |
redis-cache |
| Payments |
new-payment-service |
| Payments |
shared-library |
| Payments |
merchant-onboarding scaffolded from new-payment-service |
| Payments |
Tier |
| Payments |
PCI Scope |
| Payments |
PayFlow Service Catalog |
| Payments |
PayFlow API Dependency Map |
| Payments |
PayFlow Ownership Matrix |
| Payments |
Meridian Insurance Group — Enterprise Design Model |
| Payments |
Policyholder |
| Payments |
Insurance Agent |
| Payments |
Claims Adjuster |
| Payments |
Underwriter |
| Payments |
Protect What Matters |
| Payments |
From Mutual to Digital |
| Payments |
Risk Prevention Advice |
| Payments |
Underwriting |
| Payments |
Claims Management |
| Payments |
Policy Administration |
| Payments |
Customer Service |
| Payments |
Distribution Management |
| Payments |
Fraud Prevention |
| Payments |
First Notice of Loss |
| Payments |
Claims Assessment |
| Payments |
Settlement |
| Payments |
Risk Assessment |
| Payments |
Pricing |
| Payments |
Claims Assessment Process |
| Payments |
Underwriting Process |
| Payments |
Renewal Process |
| Payments |
Fraud Detection Engine |
| Payments |
Customer Data Platform |
| Payments |
Claims Workflow System |
| Payments |
Policy Administration System |
| Payments |
Actuarial Pricing Engine |
| Payments |
File a Claim |
| Payments |
Get Insured |
| Payments |
Track Claim Progress |
| Payments |
Receive Payment |
| Payments |
Renew My Policy |
| Payments |
Claims Journey |
| Payments |
Purchase Journey |
| Payments |
Renewal Journey |
| Payments |
Mobile App |
| Payments |
Customer Portal |
| Payments |
Agent Network |
| Payments |
Call Centre |
| Payments |
Meridian Insurance Group |
| Payments |
Meridian Nordics |
| Payments |
Claims Operations |
| Payments |
Home Insurance |
| Payments |
Motor Insurance |
| Payments |
Commercial Property Insurance |
| Payments |
Personal Lines Portfolio |
| Payments |
Meridian |
| Payments |
NordGuard |
| Payments |
Application |
| Payments |
Data |
| Payments |
Application |
| Payments |
Application |
| Payments |
Maturity: Managed |
| Payments |
Performance: Green |
| Payments |
Risk: Amber |
| Payments |
Performance: Amber |
| Payments |
Meridian Capability Map |
| Payments |
Meridian Claims Journey Map |
| Payments |
Meridian Identity Map |
| Payments |
Meridian Product Map |
| Payments |
Meridian Full Enterprise Map |
| Payments |
Core-vis Diagram Reference Example |
| Payments |
Order Service |
| Payments |
Payment Service |
| Payments |
Order Service serves Payment Service |
| Payments |
Payment Flow |
| Payments |
Application layer |
| Payments |
serves |
| Payments |
Retries are idempotent: the order id is the key. |
| Payments |
Core-vis Example Notation |
| Payments |
SAP LeanIX Meta Model v4 — Documentation Example Landscape |
| Payments |
Reduce IT run cost by 20% by 2027 |
| Payments |
ERP Consolidation Program 2026–2028 |
| Payments |
Customer Management |
| Payments |
Order Processing |
| Payments |
Finance |
| Payments |
Sales EMEA |
| Payments |
Accounting Shared Services |
| Payments |
Lead to Cash |
| Payments |
Create Customer Invoice |
| Payments |
Gold Credit Card |
| Payments |
SAP S/4HANA Finance |
| Payments |
Salesforce Sales Cloud |
| Payments |
Legacy Billing System |
| Payments |
Order export API |
| Payments |
Customer Profile |
| Payments |
Invoice Data |
| Payments |
PostgreSQL 15 |
| Payments |
Kubernetes cluster |
| Payments |
Database |
| Payments |
Cloud Platform |
| Payments |
Customer Data Platform |
| Payments |
SAP ERP Central System (ECC PROD) |
| Payments |
SAP |
| Payments |
Microsoft Azure |
| Payments |
Jane Doe |
| Payments |
Marcus Reid |
| Payments |
SAP S/4HANA Finance supports Order Processing |
| Payments |
SAP S/4HANA Finance requires PostgreSQL 15 |
| Payments |
SAP S/4HANA Finance uses Invoice Data |
| Payments |
Order export API carries Customer Profile |
| Payments |
Reduce IT run cost drives the ERP Consolidation Program |
| Payments |
Finance uses SAP S/4HANA Finance |
| Payments |
PostgreSQL 15 is provided by SAP |
| Payments |
PostgreSQL 15 is categorized as Database |
| Payments |
SAP S/4HANA Finance provides Order export API |
| Payments |
Salesforce Sales Cloud consumes Order export API |
| Payments |
Finance is the parent of Accounting Shared Services |
| Payments |
ERP Consolidation Program impacts SAP S/4HANA Finance |
| Payments |
Salesforce Sales Cloud is part of the Customer Data Platform |
| Payments |
SAP S/4HANA Finance supports Create Customer Invoice |
| Payments |
Lead to Cash realizes Customer Management |
| Payments |
Reduce IT run cost targets Order Processing |
| Payments |
SAP ERP Central System is composed of PostgreSQL 15 |
| Payments |
ERP Consolidation Program impacts the Customer Data Platform |
| Payments |
Maria Chen — Chief Architect |
| Payments |
James Park — Senior Domain Architect |
| Payments |
Aisha Okafor — Senior Platform Architect |
| Payments |
Tom Eriksson — Junior Architect |
| Payments |
Sarah Williams — VP Retail Banking |
| Payments |
David Kim — Head of Payments |
| Payments |
CTO Office |
| Payments |
Elena Rossi — Compliance Director |
| Payments |
Raj Patel — Product Owner, Mobile Banking |
| Payments |
ArchiMate Modeling |
| Payments |
TOGAF ADM |
| Payments |
Portfolio Analysis |
| Payments |
SPARQL Querying |
| Payments |
SHACL Validation |
| Payments |
Stakeholder Facilitation |
| Payments |
Cloud Architecture |
| Payments |
Financial Modeling |
| Payments |
Acme Corp EA Service Catalog 2026 |
| Payments |
Architecture Review |
| Payments |
Portfolio Assessment |
| Payments |
Impact Analysis |
| Payments |
Target State Design |
| Payments |
Technology Radar |
| Payments |
Onboarding Consultation |
| Payments |
Payment Platform |
| Payments |
Mobile Banking Application |
| Payments |
Retail Banking |
| Payments |
Customer Onboarding |
| Payments |
Request: Payment Platform Target State Design |
| Payments |
Payment Platform Target State Design |
| Payments |
Payment Platform Target State Architecture v1.0 |
| Payments |
ADR-042: Migrate Payment Platform to AWS EKS |
| Payments |
Request: Retail Banking Portfolio Assessment |
| Payments |
Retail Banking Portfolio Assessment |
| Payments |
Request: Mobile Banking Architecture Review |
| Payments |
Mobile Banking Architecture Review |
| Payments |
Mobile Banking Architecture Review Report |
| Payments |
Request: PSD2 Compliance Architecture Validation |
| Payments |
Request: Onboarding for Customer Onboarding Redesign Project |
| Payments |
Onboarding: Customer Onboarding Redesign |
| Payments |
Acme EA Maturity Assessment — Q1 2026 |
| Payments |
Fraud Analytics Team — Data Scientists |
| Payments |
Platform Team — Data Engineers |
| Payments |
Payments Team — Software Engineers |
| Payments |
Compliance Officer |
| Payments |
Payment Processing Service |
| Payments |
Transaction Database |
| Payments |
Notification Service |
| Payments |
Fraud Case Management UI |
| Payments |
Transaction Training Dataset v2.3 |
| Payments |
Engineered Feature Dataset v2.3 |
| Payments |
Fraud Feature Store |
| Payments |
Transaction ETL Pipeline |
| Payments |
Fraud Model Training Pipeline |
| Payments |
MLflow Experiment Tracker |
| Payments |
Fraud Detection Model v3.1 |
| Payments |
Fraud Model Registry |
| Payments |
Fraud Scoring Service |
| Payments |
Fraud Model Monitor |
| Payments |
Fraud Scoring Integration |
| Payments |
ADR-001: Use XGBoost for Fraud Detection |
| Payments |
Which ML algorithm for real-time fraud scoring? |
| Payments |
XGBoost Gradient Boosted Ensemble |
| Payments |
LSTM Recurrent Neural Network |
| Payments |
Random Forest |
| Payments |
Real-time Latency Requirement |
| Payments |
Model Explainability for PSD2 Compliance |
| Payments |
No GPU Infrastructure |
| Payments |
Sequential Transaction Pattern Detection |
| Payments |
Drift Detection Response Time |
| Payments |
Fraud Model Fairness Audit |
| Payments |
Atlas Global Bank — Enterprise Architecture Model |
| Payments |
Cloud-First Principle |
| Payments |
Data Sovereignty Principle |
| Payments |
PSD2 Open Banking Compliance |
| Payments |
Basel IV Capital Requirements |
| Payments |
Digital Disruption from Neobanks |
| Payments |
Increasing Regulatory Pressure |
| Payments |
Reduce Time-to-Market |
| Payments |
Improve Digital Customer Experience |
| Payments |
Reduce IT Operating Cost by 30% |
| Payments |
Retail Banking Division |
| Payments |
Corporate Banking Division |
| Payments |
Wealth Management Division |
| Payments |
Payment Processing |
| Payments |
Lending |
| Payments |
Risk Management |
| Payments |
Customer Onboarding |
| Payments |
Loan Origination Process |
| Payments |
Payment Execution Process |
| Payments |
Account Management Service |
| Payments |
Payment Service |
| Payments |
Customer Master Data |
| Payments |
Customer |
| Payments |
Account |
| Payments |
Transaction |
| Payments |
Loan |
| Payments |
Core Banking System (Logical) |
| Payments |
Temenos Transact |
| Payments |
Payment Hub (Logical) |
| Payments |
Finastra Payment Hub |
| Payments |
Open Banking API Gateway |
| Payments |
Mobile Banking Application |
| Payments |
Risk Calculation Engine |
| Payments |
AWS EU (Frankfurt) |
| Payments |
AWS EU (Ireland) |
| Payments |
Container Orchestration Service |
| Payments |
Managed Database Service |
| Payments |
Event Streaming Service |
| Payments |
Core Banking Migration Programme |
| Payments |
Open Banking Compliance Project |
| Payments |
Payments Value Stream |
| Payments |
Lending Value Stream |
| Payments |
Domestic Payments |
| Payments |
Cross-Border Payments |
| Payments |
Card Payments |
| Payments |
Atlas Business Capability Map |
| Payments |
Atlas Application Portfolio |
| Payments |
Atlas Migration Roadmap |
| Payments |
Atlas Motivation View |
| Payments |
Chief Architect |
| Payments |
Solution Architect |
| Payments |
Security Architect |
| Payments |
Enterprise Architect |
| Payments |
Architecture Review Board Process |
| Payments |
1. Request Submission |
| Payments |
Prepare architecture proposal |
| Payments |
Submit review request |
| Payments |
2. Review Preparation |
| Payments |
Triage review request |
| Payments |
Assign reviewers |
| Payments |
Distribute review materials |
| Payments |
3. Review Execution |
| Payments |
Individual review |
| Payments |
Board discussion |
| Payments |
Record findings and decision |
| Payments |
4. Review Follow-Up |
| Payments |
Publish review report |
| Payments |
Track remediation items |
| Payments |
Submission Deadline |
| Payments |
Architecture Review Gate |
| Payments |
Architecture Proposal Document |
| Payments |
Enterprise Architecture Standards |
| Payments |
Architecture Review Report |
| Payments |
Architecture Review Board Decision |
| Payments |
Payment Service |
| Payments |
Payment REST API |
| Payments |
ADD Iteration 1 — Establish Resilience Strategy |
| Payments |
Lead Architect |
| Payments |
Identify Architectural Drivers |
| Payments |
Select Pattern and Tactics |
| Payments |
Record Architecture Decision |
| Payments |
Payment Service Resilience Design |
| Payments |
Resilience Design Gate |
| Payments |
Payment Service 99.99% Availability |
| Payments |
Graceful Degradation Under Partial Failure |
| Payments |
Payment Latency SLA |
| Payments |
Option A — Circuit Breaker with Retry |
| Payments |
Option B — Active-Active Multi-Provider |
| Payments |
Risk: inconsistent behavior across payment providers |
| Payments |
Circuit Breaker |
| Payments |
Circuit Breaker |
| Payments |
Retry with Exponential Backoff |
| Payments |
Payment Retry Queue |
| Payments |
Payment Dead Letter Queue |
| Payments |
Payment Provider Router |
| Payments |
Provider Health Checker |
| Payments |
ADR-101: Use Circuit Breaker pattern for payment resilience |
| Payments |
Payment gateway failures cause cascading timeouts |
| Payments |
Order Service |
| Payments |
Orders Database |
| Payments |
Orders DB cannot handle peak load |
| Payments |
Solution Architect |
| Payments |
Product Owner — Orders |
| Payments |
Platform Team Lead |
| Payments |
Order Service Availability Under Peak Load |
| Payments |
Sub-Second Order Response Time |
| Payments |
Infrastructure Budget Limit |
| Payments |
Customer |
| Payments |
Option A — Vertical Scaling |
| Payments |
Option B — Read Replicas |
| Payments |
Option C — CQRS + Event Sourcing |
| Payments |
Single point of failure — no redundancy |
| Payments |
High complexity — team has no event sourcing experience |
| Payments |
Orders DB Read Replica 1 |
| Payments |
Orders DB Read Replica 2 |
| Payments |
PgBouncer Connection Proxy |
| Payments |
Event Store |
| Payments |
Orders Read Model |
| Payments |
Order Command Handler |
| Payments |
ADR-042: Use read replicas for Orders DB scaling |
| Payments |
System Performance Under Load |
| Payments |
ADR-017: Vertically scale Orders DB on demand |
| Payments |
ADR-051: Cache strategy for order lookups |
| Payments |
Option A — Read-through cache (Redis) |
| Payments |
Option B — Write-through cache (Redis) |
| Payments |
ADR-063: Adopt OpenTelemetry for distributed tracing |
| Payments |
ADR-063 — record body |
| Payments |
Microservices Reference Architecture |
| Payments |
API Gateway |
| Payments |
Backend for Frontend (BFF) |
| Payments |
Circuit Breaker |
| Payments |
Bulkhead |
| Payments |
Saga |
| Payments |
Circuit Breaker |
| Payments |
Retry with Backoff |
| Payments |
Bulkhead Isolation |
| Payments |
Load Balancing |
| Payments |
Active Redundancy |
| Payments |
Service Discovery |
| Payments |
Rate Limiting |
| Payments |
API Gateway |
| Payments |
Service Mesh |
| Payments |
Message Broker |
| Payments |
Kong API Gateway |
| Payments |
Istio Service Mesh |
| Payments |
Apache Kafka |
| Payments |
Circuit Breaker impact on API Gateway |
| Payments |
Circuit Breaker Sidecar |
| Payments |
Claims handling |
| Payments |
Cloud Server |
| Payments |
Strategic Capability |
| Payments |
Regulatory Requirement |
| Payments |
Organisation |
| Payments |
Hosting |
| Payments |
Legacy |
| Payments |
Customer |
| Payments |
Claims Clerk |
| Payments |
Application Server |
| Payments |
Cloud Server 1 |
| Payments |
Handle Claim |
| Payments |
Register Claim |
| Payments |
Claim Service |
| Payments |
Orphan Service |
| Payments |
CRM |
| Payments |
crm |
| Payments |
Policy Administration |
| Payments |
Claims Portal |
| Payments |
Broker Portal |
| Payments |
Customer Data |
| Payments |
CEO |
| Payments |
Faster claims |
| Payments |
Claims settled within 24h |
| Payments |
Unrealised requirement |
| Payments |
Keep claims for ten years |
| Payments |
Digital first |
| Payments |
Unbacked principle |
| Payments |
Claims Management |
| Payments |
Fraud Detection |
| Payments |
Customer Insight |
| Payments |
CRM upgrade |
| Payments |
Upgraded CRM |
| Payments |
Baseline |
| Payments |
Target |
| Payments |
Bank |
| Payments |
Bank |
| Payments |
Platform Design |
| Payments |
Stakeholder |
| Payments |
Role |
| Payments |
Consumer |
| Payments |
Producer |
| Payments |
Enabler |
| Payments |
Keystone |
| Payments |
Indirect Stakeholder |
| Payments |
Asset |
| Payments |
Capability |
| Payments |
Story |
| Payments |
Need |
| Payments |
Solution |
| Payments |
Touchpoint |
| Payments |
Value |
| Payments |
Compensation |
| Payments |
Channel |
| Payments |
Capability |
| Payments |
Capability Increment |
| Payments |
Desired Effect |
| Payments |
Operational Activity |
| Payments |
Operational Node |
| Payments |
Resource Flow |
| Payments |
Operational Rule |
| Payments |
Performer |
| Payments |
Condition |
| Payments |
Location |
| Payments |
Conceptual Data Entity |
| Payments |
Logical Data Entity |
| Payments |
Physical Data Entity |
| Payments |
System |
| Payments |
System Function |
| Payments |
System Interface |
| Payments |
Service |
| Payments |
Service Function |
| Payments |
Service Interface |
| Payments |
Standard |
| Payments |
Standards Forecast |
| Payments |
Project |
| Payments |
Milestone |
| Payments |
Organization |
| Payments |
Measure |
| Payments |
performs |
| Payments |
supports |
| Payments |
exchanges |
| Payments |
traces to |
| Payments |
realizes |
| Payments |
delivers |
| Payments |
applies to |
| Payments |
decomposes into |
| Payments |
deployed at |
| Payments |
constrained by |
| Payments |
DoDAF Viewpoint Catalog |
| Payments |
All Viewpoint (AV) |
| Payments |
Capability Viewpoint (CV) |
| Payments |
Data and Information Viewpoint (DIV) |
| Payments |
Operational Viewpoint (OV) |
| Payments |
Project Viewpoint (PV) |
| Payments |
Services Viewpoint (SvcV) |
| Payments |
Standards Viewpoint (StdV) |
| Payments |
Systems Viewpoint (SV) |
| Payments |
Mission Commander |
| Payments |
System Engineer |
| Payments |
System Integrator |
| Payments |
Software Developer |
| Payments |
Database Engineer |
| Payments |
Network Engineer |
| Payments |
Program Manager |
| Payments |
Analyst |
| Payments |
Acquirer |
| Payments |
AV-1: Overview and Summary Information |
| Payments |
AV-2: Integrated Dictionary |
| Payments |
CV-1: Vision |
| Payments |
CV-2: Capability Taxonomy |
| Payments |
CV-3: Capability Phasing |
| Payments |
CV-4: Capability Dependencies |
| Payments |
CV-5: Capability to Organizational Development Mapping |
| Payments |
CV-6: Capability to Operational Activities Mapping |
| Payments |
CV-7: Capability to Services Mapping |
| Payments |
DIV-1: Conceptual Data Model |
| Payments |
DIV-2: Logical Data Model |
| Payments |
DIV-3: Physical Data Model |
| Payments |
OV-1: High-Level Operational Concept Graphic |
| Payments |
OV-2: Operational Resource Flow Description |
| Payments |
OV-3: Operational Resource Flow Matrix |
| Payments |
OV-4: Organizational Relationships Chart |
| Payments |
OV-5a: Operational Activity Decomposition Tree |
| Payments |
OV-5b: Operational Activity Model |
| Payments |
OV-6a: Operational Rules Model |
| Payments |
OV-6b: State Transition Description |
| Payments |
OV-6c: Event-Trace Description |
| Payments |
PV-1: Project Portfolio Relationships |
| Payments |
PV-2: Project Timelines |
| Payments |
PV-3: Project to Capability Mapping |
| Payments |
StdV-1: Standards Profile |
| Payments |
StdV-2: Standards Forecast |
| Payments |
DoDAF Concept Scheme |
| Payments |
Entity by Viewpoint |
| Payments |
All Viewpoint (AV) |
| Payments |
Capability Viewpoint (CV) |
| Payments |
Data and Information Viewpoint (DIV) |
| Payments |
Operational Viewpoint (OV) |
| Payments |
Project Viewpoint (PV) |
| Payments |
Services Viewpoint (SvcV) |
| Payments |
Standards Viewpoint (StdV) |
| Payments |
Systems Viewpoint (SV) |
| Payments |
DoDAF |
| Payments |
DoDAF 2.02 Metamodel |
| Payments |
ADMIT |
| Payments |
ADMIT Metamodel |
| Payments |
ADMIT Concept Scheme |
| Payments |
Architecture Level |
| Payments |
Enterprise Architecture |
| Payments |
Solution Architecture |
| Payments |
System Architecture |
| Payments |
Architecture Domain |
| Payments |
Business Architecture |
| Payments |
Information/Data Architecture |
| Payments |
Application/Service Architecture |
| Payments |
Technology/Technical Architecture |
| Payments |
Architecture and Resource Dimension |
| Payments |
Workload |
| Payments |
Demand |
| Payments |
Throughput |
| Payments |
Latency |
| Payments |
Capacity |
| Payments |
Redundancy |
| Payments |
Architecture Design Forces |
| Payments |
Business Force |
| Payments |
Operation Force |
| Payments |
Aestheticism Force |
| Payments |
Future Force |
| Payments |
Simplicity Force |
| Payments |
Change Force |
| Payments |
Process Force |
| Payments |
Integration Force |
| Payments |
Implementation/Pattern Force |
| Payments |
Enterprise Force |
| Payments |
Constraint/Environment Force |
| Payments |
Failure Force |
| Payments |
Channel Force |
| Payments |
Content Force |
| Payments |
Platform Force |
| Payments |
Infrastructure Force |
| Payments |
Network Force |
| Payments |
Storage Force |
| Payments |
Security Force |
| Payments |
Cost Force |
| Payments |
Architecture Development Lifecycle |
| Payments |
Development Area |
| Payments |
Optimization Area |
| Payments |
Automation Area |
| Payments |
Planning/Strategy Phase |
| Payments |
Design/Execution Phase |
| Payments |
Management/Governance Phase |
| Payments |
Optimization Phase |
| Payments |
Automation Phase |
| Payments |
Identify business vision and strategy |
| Payments |
Plan stakeholder management |
| Payments |
Define architecture and technology strategy |
| Payments |
Assess current architecture |
| Payments |
Design target architecture |
| Payments |
Conduct gap analysis |
| Payments |
Develop execution roadmap |
| Payments |
Build reference architecture |
| Payments |
Review architecture with stakeholders |
| Payments |
Initiate a quick-win project |
| Payments |
Perform implementation governance |
| Payments |
Manage lifecycle changes |
| Payments |
Manage architecture assets |
| Payments |
Improve architecture and process continuously |
| Payments |
Automate lifecycle with tool and technology |
| Payments |
Business Force |
| Payments |
Operation Force |
| Payments |
Aestheticism Force |
| Payments |
Future Force |
| Payments |
Simplicity Force |
| Payments |
Change Force |
| Payments |
Process Force |
| Payments |
Integration Force |
| Payments |
Implementation/Pattern Force |
| Payments |
Enterprise Force |
| Payments |
Constraint/Environment Force |
| Payments |
Failure Force |
| Payments |
Channel Force |
| Payments |
Content Force |
| Payments |
Platform Force |
| Payments |
Infrastructure Force |
| Payments |
Network Force |
| Payments |
Storage Force |
| Payments |
Security Force |
| Payments |
Cost Force |
| Payments |
4+1 Architectural View Model |
| Payments |
4+1 View Model Metamodel |
| Payments |
4+1 Viewpoint Catalog |
| Payments |
End User |
| Payments |
Software Architect |
| Payments |
Developer |
| Payments |
System Engineer |
| Payments |
Project Manager |
| Payments |
Functionality |
| Payments |
Performance & Concurrency |
| Payments |
Software Management |
| Payments |
Deployment & Operations |
| Payments |
Validation & Consistency |
| Payments |
Logical Viewpoint |
| Payments |
Process Viewpoint |
| Payments |
Development Viewpoint |
| Payments |
Physical Viewpoint |
| Payments |
Scenarios Viewpoint (+1) |
| Payments |
Software Architecture Document (4+1) |
| Payments |
1. Introduction & Architectural Goals |
| Payments |
2. Architectural Scenarios |
| Payments |
3. Logical View |
| Payments |
4. Process View |
| Payments |
5. Development View |
| Payments |
6. Physical View |
| Payments |
7. Quality & Architectural Decisions |
| Payments |
4+1 Architectural View Model |
| Payments |
Logical View |
| Payments |
Process View |
| Payments |
Development View |
| Payments |
Physical View |
| Payments |
Scenarios View |
| Payments |
UAF Viewpoint Catalog |
| Payments |
Architecture Management Viewpoint (Am) |
| Payments |
Strategic Viewpoint (St) |
| Payments |
Operational Viewpoint (Op) |
| Payments |
Services Viewpoint (Sv) |
| Payments |
Personnel Viewpoint (Pr) |
| Payments |
Resources Viewpoint (Rs) |
| Payments |
Security Viewpoint (Sc) |
| Payments |
Projects Viewpoint (Pj) |
| Payments |
Standards Viewpoint (Sd) |
| Payments |
Actual Resources Viewpoint (Ar) |
| Payments |
Enterprise Architect |
| Payments |
Capability Planner |
| Payments |
System Engineer |
| Payments |
Service Architect |
| Payments |
Security Architect |
| Payments |
Program Manager |
| Payments |
Operational Planner |
| Payments |
Resource Manager |
| Payments |
Personnel Manager |
| Payments |
Standards Authority |
| Payments |
Am-Mv: Architecture Management Motivation |
| Payments |
Am-Tx: Architecture Management Taxonomy |
| Payments |
St-Mv: Strategic Motivation |
| Payments |
St-Tx: Strategic Taxonomy (Capability Taxonomy) |
| Payments |
St-Sr: Strategic Structure (Capability Configuration) |
| Payments |
St-Cn: Strategic Connectivity (Capability Dependencies) |
| Payments |
St-Rm: Strategic Roadmap (Capability Phasing) |
| Payments |
Op-Tx: Operational Taxonomy |
| Payments |
Op-Sr: Operational Structure |
| Payments |
Op-Cn: Operational Connectivity |
| Payments |
Op-Pr: Operational Processes |
| Payments |
Op-Ct: Operational Constraints |
| Payments |
Op-Hc: High-Level Operational Concept |
| Payments |
Sv-Tx: Services Taxonomy |
| Payments |
Sv-Sr: Services Structure |
| Payments |
Sv-Cn: Services Connectivity |
| Payments |
Pr-Tx: Personnel Taxonomy |
| Payments |
Pr-Sr: Personnel Structure |
| Payments |
Rs-Tx: Resources Taxonomy |
| Payments |
Rs-Sr: Resources Structure |
| Payments |
Rs-Cn: Resources Connectivity |
| Payments |
Rs-Pr: Resources Processes |
| Payments |
Sc-Tx: Security Taxonomy |
| Payments |
Sc-Sr: Security Structure |
| Payments |
Sc-Ct: Security Constraints |
| Payments |
Pj-Sr: Projects Structure |
| Payments |
Pj-Rm: Projects Roadmap |
| Payments |
Pj-Tr: Projects Traceability |
| Payments |
Sd-Tx: Standards Taxonomy |
| Payments |
Sd-Tr: Standards Traceability |
| Payments |
Ar-Sr: Actual Resources Structure |
| Payments |
Ar-Cn: Actual Resources Connectivity |
| Payments |
UAF Concept Scheme |
| Payments |
Entity by Viewpoint |
| Payments |
Architecture Management Viewpoint (Am) |
| Payments |
Strategic Viewpoint (St) |
| Payments |
Operational Viewpoint (Op) |
| Payments |
Services Viewpoint (Sv) |
| Payments |
Personnel Viewpoint (Pr) |
| Payments |
Resources Viewpoint (Rs) |
| Payments |
Security Viewpoint (Sc) |
| Payments |
Projects Viewpoint (Pj) |
| Payments |
Standards Viewpoint (Sd) |
| Payments |
Actual Resources Viewpoint (Ar) |
| Payments |
Entity by Aspect |
| Payments |
Motivation Aspect |
| Payments |
Taxonomy Aspect |
| Payments |
Structure Aspect |
| Payments |
Connectivity Aspect |
| Payments |
Processes Aspect |
| Payments |
States Aspect |
| Payments |
Sequences Aspect |
| Payments |
Information Aspect |
| Payments |
Constraints Aspect |
| Payments |
Roadmap Aspect |
| Payments |
Traceability Aspect |
| Payments |
UAF Element |
| Payments |
Measurable Element |
| Payments |
Phaseable Element |
| Payments |
Capability |
| Payments |
Capability Configuration |
| Payments |
Enterprise Goal |
| Payments |
Enterprise Objective |
| Payments |
Enterprise Vision |
| Payments |
Mission |
| Payments |
Opportunity |
| Payments |
Challenge |
| Payments |
Driver |
| Payments |
Operational Activity |
| Payments |
Operational Performer |
| Payments |
Operational Exchange |
| Payments |
Operational Agent |
| Payments |
Operational Connector |
| Payments |
Operational Constraint |
| Payments |
High-Level Operational Concept |
| Payments |
Operational Architecture |
| Payments |
Service |
| Payments |
Service Function |
| Payments |
Service Interface |
| Payments |
Service Contract |
| Payments |
Service Exchange |
| Payments |
Service Architecture |
| Payments |
Organization |
| Payments |
Person |
| Payments |
Post |
| Payments |
Responsibility |
| Payments |
Organizational Resource |
| Payments |
Resource Performer |
| Payments |
Function |
| Payments |
Resource Architecture |
| Payments |
Natural Resource |
| Payments |
Known Resource |
| Payments |
Resource Connector |
| Payments |
Resource Exchange |
| Payments |
Security Asset |
| Payments |
Security Control |
| Payments |
Security Control Family |
| Payments |
Security Enclave |
| Payments |
Security Constraint |
| Payments |
Project |
| Payments |
Project Milestone |
| Payments |
Project Phase |
| Payments |
Standard |
| Payments |
Standard Profile |
| Payments |
Protocol |
| Payments |
Actual Organization |
| Payments |
Actual Resource |
| Payments |
Actual Person |
| Payments |
Actual Post |
| Payments |
Actual Service |
| Payments |
Architecture |
| Payments |
Architectural Description |
| Payments |
Stakeholder |
| Payments |
View |
| Payments |
Viewpoint |
| Payments |
Whole Life Enterprise |
| Payments |
exhibits |
| Payments |
Exhibits |
| Payments |
performs |
| Payments |
Performs |
| Payments |
implements |
| Payments |
Implements |
| Payments |
realizes |
| Payments |
Realizes |
| Payments |
depends on |
| Payments |
Capability Dependency |
| Payments |
provides |
| Payments |
Provides |
| Payments |
consumes |
| Payments |
Consumes |
| Payments |
Unified Architecture Framework (UAF) |
| Payments |
DoDAF (predecessor) |
| Payments |
MODAF (predecessor) |
| Payments |
NAF (predecessor) |
| Payments |
UAF 1.2 Metamodel |
| Payments |
Technology |
| Payments |
Radar assessment |
| Payments |
Radar |
| Payments |
Ring |
| Payments |
Adopt |
| Payments |
Trial |
| Payments |
Assess |
| Payments |
Hold |
| Payments |
Retire |
| Payments |
Quadrant |
| Payments |
Techniques |
| Payments |
Platforms |
| Payments |
Tools |
| Payments |
Languages & Frameworks |
| Payments |
Movement |
| Payments |
New |
| Payments |
Moved in |
| Payments |
Moved out |
| Payments |
No change |
| Payments |
has assessment |
| Payments |
assessed technology |
| Payments |
ring |
| Payments |
quadrant |
| Payments |
movement |
| Payments |
published in radar |
| Payments |
governed by |
| Payments |
assessment date |
| Payments |
rationale |
| Payments |
publication date |
| Payments |
migration deadline |
| Payments |
replacement technology |
| Payments |
Technology Radar Framework |
| Payments |
Technology Radar Metamodel |
| Payments |
Technology Radar Concept Scheme |
| Payments |
Rings |
| Payments |
Quadrants |
| Payments |
Movements |
| Payments |
TIME Framework Concept Scheme |
| Payments |
TIME Dispositions |
| Payments |
Fit Ratings |
| Payments |
Fit Dimensions |
| Payments |
Assessment Statuses |
| Payments |
Evidence Types |
| Payments |
Lifecycle States |
| Payments |
Disposition Movements |
| Payments |
Application |
| Payments |
Business capability |
| Payments |
Technology component |
| Payments |
Person |
| Payments |
Fit assessment |
| Payments |
TIME assessment model |
| Payments |
Fit criterion |
| Payments |
Fit criterion score |
| Payments |
Evidence |
| Payments |
supports capability |
| Payments |
uses technology component |
| Payments |
has fit assessment |
| Payments |
assessed application |
| Payments |
assessor |
| Payments |
business owner |
| Payments |
IT owner |
| Payments |
uses assessment model |
| Payments |
has criterion score |
| Payments |
criterion |
| Payments |
has evidence |
| Payments |
evidence type |
| Payments |
dimension |
| Payments |
assessment status |
| Payments |
lifecycle state |
| Payments |
disposition movement |
| Payments |
previous disposition |
| Payments |
functional fit rating |
| Payments |
technical fit rating |
| Payments |
cost fit rating |
| Payments |
TIME disposition |
| Payments |
assessment date |
| Payments |
valid until |
| Payments |
functional fit score |
| Payments |
technical fit score |
| Payments |
cost fit score |
| Payments |
rationale |
| Payments |
reference URI |
| Payments |
source system |
| Payments |
email |
| Payments |
criterion score |
| Payments |
criterion justification |
| Payments |
criterion weight |
| Payments |
scale minimum |
| Payments |
scale maximum |
| Payments |
high threshold |
| Payments |
TIME disposition |
| Payments |
Tolerate |
| Payments |
Invest |
| Payments |
Migrate |
| Payments |
Eliminate |
| Payments |
Fit rating |
| Payments |
High |
| Payments |
Low |
| Payments |
Fit dimension |
| Payments |
Functional |
| Payments |
Technical |
| Payments |
Cost |
| Payments |
Assessment status |
| Payments |
Draft |
| Payments |
Approved |
| Payments |
Superseded |
| Payments |
Rejected |
| Payments |
Evidence type |
| Payments |
Architecture review |
| Payments |
Security assessment |
| Payments |
Operations metrics |
| Payments |
Cost analysis |
| Payments |
Business stakeholder input |
| Payments |
Vendor roadmap |
| Payments |
Technical debt register |
| Payments |
Other |
| Payments |
Lifecycle state |
| Payments |
Disposition movement |
| Payments |
Improved |
| Payments |
Degraded |
| Payments |
Unchanged |
| Payments |
New |
| Payments |
Plan |
| Payments |
Build |
| Payments |
Run |
| Payments |
Retire |
| Payments |
Invest assessment |
| Payments |
Migrate assessment |
| Payments |
Tolerate assessment |
| Payments |
Eliminate assessment |
| Payments |
Inconsistent Test Application |
| Payments |
Migrate-as-Tolerate Test Application |
| Payments |
Disposition-Only Test Application |
| Payments |
Derive disposition movement |
| Payments |
TIME Framework |
| Payments |
TIME Metamodel |
| Payments |
Utility Tree |
| Payments |
Quality Attribute Branch |
| Payments |
Sensitivity Point |
| Payments |
Tradeoff Point |
| Payments |
Architectural Risk |
| Payments |
Non-Risk |
| Payments |
Risk Theme |
| Payments |
ATAM Evaluation |
| Payments |
has QA branch |
| Payments |
branch quality attribute |
| Payments |
has scenario |
| Payments |
scenario priority |
| Payments |
sensitive to quality attribute |
| Payments |
affects element |
| Payments |
identified in scenario |
| Payments |
risk for quality attribute |
| Payments |
risk in decision |
| Payments |
risk in approach |
| Payments |
theme includes risk |
| Payments |
evaluates architecture |
| Payments |
has utility tree |
| Payments |
identified risk |
| Payments |
identified non-risk |
| Payments |
identified sensitivity point |
| Payments |
identified tradeoff point |
| Payments |
identified risk theme |
| Payments |
ATAM |
| Payments |
ATAM Metamodel |
| Payments |
EA Artifact Coverage Report (Zachman) |
| Payments |
1. Coverage Matrix |
| Payments |
2. Gap Analysis |
| Payments |
3. Artifacts by Perspective |
| Payments |
4. Summary Statistics |
| Payments |
5. Reification Transformation Coverage |
| Payments |
Zachman Framework |
| Payments |
Zachman Framework Metamodel |
| Payments |
Inventory / What |
| Payments |
Process / How |
| Payments |
Distribution / Where |
| Payments |
Responsibility / Who |
| Payments |
Timing / When |
| Payments |
Motivation / Why |
| Payments |
Executive / Identification |
| Payments |
Business Management / Definition |
| Payments |
Architect / Representation |
| Payments |
Engineer / Specification |
| Payments |
Technician / Configuration |
| Payments |
Enterprise / Instantiation |
| Payments |
Inventory Identification Viewpoint |
| Payments |
Process Identification Viewpoint |
| Payments |
Distribution Identification Viewpoint |
| Payments |
Responsibility Identification Viewpoint |
| Payments |
Timing Identification Viewpoint |
| Payments |
Motivation Identification Viewpoint |
| Payments |
Inventory Definition Viewpoint |
| Payments |
Process Definition Viewpoint |
| Payments |
Distribution Definition Viewpoint |
| Payments |
Responsibility Definition Viewpoint |
| Payments |
Timing Definition Viewpoint |
| Payments |
Motivation Definition Viewpoint |
| Payments |
Inventory Representation Viewpoint |
| Payments |
Process Representation Viewpoint |
| Payments |
Distribution Representation Viewpoint |
| Payments |
Responsibility Representation Viewpoint |
| Payments |
Timing Representation Viewpoint |
| Payments |
Motivation Representation Viewpoint |
| Payments |
Inventory Specification Viewpoint |
| Payments |
Process Specification Viewpoint |
| Payments |
Distribution Specification Viewpoint |
| Payments |
Responsibility Specification Viewpoint |
| Payments |
Timing Specification Viewpoint |
| Payments |
Motivation Specification Viewpoint |
| Payments |
Inventory Configuration Viewpoint |
| Payments |
Process Configuration Viewpoint |
| Payments |
Distribution Configuration Viewpoint |
| Payments |
Responsibility Configuration Viewpoint |
| Payments |
Timing Configuration Viewpoint |
| Payments |
Motivation Configuration Viewpoint |
| Payments |
Inventory Instantiation Viewpoint |
| Payments |
Process Instantiation Viewpoint |
| Payments |
Distribution Instantiation Viewpoint |
| Payments |
Responsibility Instantiation Viewpoint |
| Payments |
Timing Instantiation Viewpoint |
| Payments |
Motivation Instantiation Viewpoint |
| Payments |
has aspect |
| Payments |
has perspective |
| Payments |
row order |
| Payments |
column order |
| Payments |
Zachman Cell |
| Payments |
classified by cell |
| Payments |
related enterprise type |
| Payments |
related model type |
| Payments |
Zachman Framework Classification |
| Payments |
Zachman Aspect |
| Payments |
Inventory / What |
| Payments |
Process / How |
| Payments |
Distribution / Where |
| Payments |
Responsibility / Who |
| Payments |
Timing / When |
| Payments |
Motivation / Why |
| Payments |
Zachman Perspective |
| Payments |
Executive / Identification |
| Payments |
Business Management / Definition |
| Payments |
Architect / Representation |
| Payments |
Engineer / Specification |
| Payments |
Technician / Configuration |
| Payments |
Enterprise / Instantiation |
| Payments |
Enterprise Type |
| Payments |
Inventory Sets |
| Payments |
Process Flows |
| Payments |
Distribution Networks |
| Payments |
Responsibility Assignments |
| Payments |
Timing Cycles |
| Payments |
Motivation Intentions |
| Payments |
Model Type |
| Payments |
Scope Contexts |
| Payments |
Business Concepts |
| Payments |
System Logic |
| Payments |
Technology Physics |
| Payments |
Tool Components |
| Payments |
Operations Instances |
| Payments |
Zachman Cell |
| Payments |
Inventory Identification |
| Payments |
Process Identification |
| Payments |
Distribution Identification |
| Payments |
Responsibility Identification |
| Payments |
Timing Identification |
| Payments |
Motivation Identification |
| Payments |
Inventory Definition |
| Payments |
Process Definition |
| Payments |
Distribution Definition |
| Payments |
Responsibility Definition |
| Payments |
Timing Definition |
| Payments |
Motivation Definition |
| Payments |
Inventory Representation |
| Payments |
Process Representation |
| Payments |
Distribution Representation |
| Payments |
Responsibility Representation |
| Payments |
Timing Representation |
| Payments |
Motivation Representation |
| Payments |
Inventory Specification |
| Payments |
Process Specification |
| Payments |
Distribution Specification |
| Payments |
Responsibility Specification |
| Payments |
Timing Specification |
| Payments |
Motivation Specification |
| Payments |
Inventory Configuration |
| Payments |
Process Configuration |
| Payments |
Distribution Configuration |
| Payments |
Responsibility Configuration |
| Payments |
Timing Configuration |
| Payments |
Motivation Configuration |
| Payments |
Inventory Instantiation |
| Payments |
Process Instantiation |
| Payments |
Distribution Instantiation |
| Payments |
Responsibility Instantiation |
| Payments |
Timing Instantiation |
| Payments |
Motivation Instantiation |
| Payments |
Zachman Cell-Aspect Consistency |
| Payments |
Zachman Cell-Perspective Consistency |
| Payments |
Valid Zachman Cell Value |
| Payments |
EA on a Page Classification |
| Payments |
EA Artifact Types |
| Payments |
Considerations |
| Payments |
Standards |
| Payments |
Visions |
| Payments |
Landscapes |
| Payments |
Outlines |
| Payments |
Designs |
| Payments |
Principle |
| Payments |
Policy |
| Payments |
Conceptual Data Model |
| Payments |
Analytical Report |
| Payments |
Direction Statement |
| Payments |
Technology Reference Model |
| Payments |
Guideline |
| Payments |
Pattern |
| Payments |
IT Principle |
| Payments |
Logical Data Model |
| Payments |
Business Capability Model |
| Payments |
Roadmap |
| Payments |
Target State |
| Payments |
Value Chain |
| Payments |
Context Diagram |
| Payments |
Landscape Diagram |
| Payments |
Inventory |
| Payments |
Enterprise System Portfolio |
| Payments |
IT Roadmap |
| Payments |
Solution Overview |
| Payments |
Options Assessment |
| Payments |
Initiative Proposal |
| Payments |
Solution Design |
| Payments |
Preliminary Solution Design |
| Payments |
Maturity Stages |
| Payments |
Stage Zero — No Architecture |
| Payments |
Stage One — IT Optimization |
| Payments |
Stage Two — Solution Delivery |
| Payments |
Stage Three — Enterprise Architecture |
| Payments |
Governance Model |
| Payments |
Architecture Tiers |
| Payments |
One-Tier Model |
| Payments |
Two-Tier Model |
| Payments |
Three-Tier Model |
| Payments |
Governance Bodies |
| Payments |
Architecture Review Board |
| Payments |
Steering Committee |
| Payments |
Technology Council |
| Payments |
Governance Activities |
| Payments |
Architecture Review |
| Payments |
Approval |
| Payments |
Amendment |
| Payments |
Exemption |
| Payments |
Escalation |
| Payments |
Classification Dimensions |
| Payments |
Nature |
| Payments |
Rules |
| Payments |
Structures |
| Payments |
Changes |
| Payments |
Focus |
| Payments |
Business-Focused |
| Payments |
IT-Focused |
| Payments |
Scope |
| Payments |
Organization-Wide |
| Payments |
Initiative-Scoped |
| Payments |
Project-Scoped |
| Payments |
Lifecycle |
| Payments |
Permanent |
| Payments |
Long-Lived |
| Payments |
Short-Lived |
| Payments |
Usage Frequency |
| Payments |
Essential |
| Payments |
Common |
| Payments |
Uncommon |
| Payments |
Architecture Strategy |
| Payments |
1. Architecture Principles & Policies |
| Payments |
2. Business Capability Assessment |
| Payments |
3. Target State Architecture |
| Payments |
4. Strategic Roadmap |
| Payments |
Technology Strategy |
| Payments |
1. Technology Reference Model |
| Payments |
2. Current Technology Landscape |
| Payments |
3. Compliance Assessment |
| Payments |
4. Rationalization Roadmap |
| Payments |
Technology Reference Model |
| Payments |
1. Technology Categories |
| Payments |
2. Lifecycle Status |
| Payments |
3. Migration Guidance |
| Payments |
Solution Brief |
| Payments |
1. Business Context & Drivers |
| Payments |
2. Proposed Approach |
| Payments |
3. Estimates & Assumptions |
| Payments |
Solution Overview |
| Payments |
1. Business Context |
| Payments |
2. Solution Options |
| Payments |
3. Standards Compliance |
| Payments |
4. Recommended Approach |
| Payments |
5. Implementation Roadmap |
| Payments |
Solution Design |
| Payments |
1. Solution Context |
| Payments |
2. Component Architecture |
| Payments |
3. Interface Contracts |
| Payments |
4. Data Architecture |
| Payments |
5. Deployment Architecture |
| Payments |
6. Standards Compliance & Exemptions |
| Payments |
Architecture Principles Document |
| Payments |
1. Architecture Principles |
| Payments |
2. Architecture Policies |
| Payments |
3. Governance & Compliance |
| Payments |
Roadmap |
| Payments |
1. Current State Summary |
| Payments |
2. Target State |
| Payments |
3. Transition Phases |
| Payments |
4. Investment Priorities |
| Payments |
Consideration |
| Payments |
Standard |
| Payments |
Vision |
| Payments |
Landscape |
| Payments |
Outline |
| Payments |
Design |
| Payments |
influence creation |
| Payments |
influence structure |
| Payments |
influence outline structure |
| Payments |
influence design structure |
| Payments |
influence evolution |
| Payments |
influence selection |
| Payments |
initiate new |
| Payments |
guide structure |
| Payments |
guide evolution |
| Payments |
guide selection |
| Payments |
provide basis |
| Payments |
provide environment |
| Payments |
provide environment for outline |
| Payments |
provide environment for design |
| Payments |
provide guidelines |
| Payments |
provide guidelines for outline |
| Payments |
provide guidelines for design |
| Payments |
eventually shape |
| Payments |
Artifact Type |
| Payments |
classified by type |
| Payments |
EA Process |
| Payments |
Strategic Planning |
| Payments |
Initiative Delivery |
| Payments |
Technology Optimization |
| Payments |
EA Practice Participant |
| Payments |
Enterprise Architect |
| Payments |
Solution Architect |
| Payments |
Business Leader |
| Payments |
IT Leader |
| Payments |
EA Maturity Stage |
| Payments |
Governance Body |
| Payments |
Architecture Tier |
| Payments |
Governance Arrangement |
| Payments |
EA Process Phase |
| Payments |
Strategic Planning Cycle |
| Payments |
Initiation |
| Payments |
Realization |
| Payments |
Governance Activity |
| Payments |
Architecture Review |
| Payments |
Approval |
| Payments |
Amendment |
| Payments |
Exemption |
| Payments |
Escalation |
| Payments |
used in process |
| Payments |
artifact scope |
| Payments |
artifact lifecycle |
| Payments |
artifact nature |
| Payments |
artifact focus |
| Payments |
usage frequency |
| Payments |
process participant |
| Payments |
governed by |
| Payments |
governs tier |
| Payments |
escalates to |
| Payments |
tier level |
| Payments |
has governance arrangement |
| Payments |
has phase |
| Payments |
maturity stage process |
| Payments |
maturity benefit |
| Payments |
maturity challenge |
| Payments |
Consideration Shape |
| Payments |
Standard Shape |
| Payments |
Vision Shape |
| Payments |
Landscape Shape |
| Payments |
Outline Shape |
| Payments |
Design Shape |
| Payments |
Governance Body Shape |
| Payments |
Architecture Tier Shape |
| Payments |
No Self-Escalation Shape |
| Payments |
Maturity Stage Shape |
| Payments |
EA on a Page Viewpoint Catalog |
| Payments |
Strategic Viewpoints |
| Payments |
Optimization Viewpoints |
| Payments |
Delivery Viewpoints |
| Payments |
Governance Viewpoints |
| Payments |
Deciding |
| Payments |
Designing |
| Payments |
Informing |
| Payments |
Governing |
| Payments |
Business Capability Viewpoint |
| Payments |
Roadmap Viewpoint |
| Payments |
Landscape Viewpoint |
| Payments |
Standards Compliance Viewpoint |
| Payments |
Solution Design Viewpoint |
| Payments |
Options Assessment Viewpoint |
| Payments |
Governance Overview Viewpoint |
| Payments |
Maturity Assessment Viewpoint |
| Payments |
EA on a Page |
| Payments |
EA on a Page Metamodel |
| Payments |
MotivationElement |
| Payments |
BusinessArchitectureElement |
| Payments |
DataArchitectureElement |
| Payments |
ApplicationArchitectureElement |
| Payments |
TechnologyArchitectureElement |
| Payments |
ImplementationElement |
| Payments |
Principle |
| Payments |
Vision |
| Payments |
Requirement |
| Payments |
Constraint |
| Payments |
Assumption |
| Payments |
Gap |
| Payments |
Driver |
| Payments |
Goal |
| Payments |
Objective |
| Payments |
Measure |
| Payments |
Organization |
| Payments |
Actor |
| Payments |
Role |
| Payments |
Business Service |
| Payments |
Business Function |
| Payments |
Business Process |
| Payments |
Business Event |
| Payments |
Product |
| Payments |
Contract |
| Payments |
Location |
| Payments |
Data Entity |
| Payments |
Logical Data Component |
| Payments |
Physical Data Component |
| Payments |
Logical Application Component |
| Payments |
Physical Application Component |
| Payments |
Information System Service |
| Payments |
Application Interface |
| Payments |
Logical Technology Component |
| Payments |
Physical Technology Component |
| Payments |
Technology Service |
| Payments |
Technology Interface |
| Payments |
Platform |
| Payments |
Work Package |
| Payments |
Deliverable |
| Payments |
Plateau |
| Payments |
Capability |
| Payments |
supports |
| Payments |
realizes |
| Payments |
governs |
| Payments |
used by |
| Payments |
accesses |
| Payments |
communicates with |
| Payments |
decomposes into |
| Payments |
depends on |
| Payments |
tracks |
| Payments |
migrates from |
| Payments |
migrates to |
| Payments |
contains |
| Payments |
is realized through |
| Payments |
TOGAF Content Metamodel Taxonomy |
| Payments |
Entity by Domain |
| Payments |
Principles, Vision & Requirements |
| Payments |
Business Architecture |
| Payments |
Data Architecture |
| Payments |
Application Architecture |
| Payments |
Technology Architecture |
| Payments |
Implementation & Migration |
| Payments |
Entity by ADM Phase |
| Payments |
Preliminary |
| Payments |
Phase A: Architecture Vision |
| Payments |
Phase B: Business Architecture |
| Payments |
Phase C: Data Architecture |
| Payments |
Phase C: Application Architecture |
| Payments |
Phase D: Technology Architecture |
| Payments |
Phase E: Opportunities & Solutions |
| Payments |
Phase F: Migration Planning |
| Payments |
Phase G: Implementation Governance |
| Payments |
Phase H: Architecture Change Management |
| Payments |
TOGAF |
| Payments |
TOGAF Metamodel |
| Payments |
Architecture Vision |
| Payments |
1. Stakeholder Map |
| Payments |
2. Value Chain |
| Payments |
3. Solution Concept |
| Payments |
Architecture Definition Document |
| Payments |
1. Business Architecture |
| Payments |
2. Data Architecture |
| Payments |
3. Application Architecture |
| Payments |
4. Technology Architecture |
| Payments |
5. Gap Analysis |
| Payments |
Architecture Requirements Specification |
| Payments |
1. Drivers, Goals & Objectives |
| Payments |
2. Architecture Principles |
| Payments |
3. Requirements & Constraints |
| Payments |
Architecture Roadmap |
| Payments |
1. Work Packages |
| Payments |
2. Transition Architectures |
| Payments |
3. Capability Assessment |
| Payments |
Implementation Governance Model |
| Payments |
1. Deliverables & Compliance |
| Payments |
2. Contracts & Measures |
| Payments |
TOGAF Viewpoint Catalog |
| Payments |
Preliminary Phase |
| Payments |
Phase A: Architecture Vision |
| Payments |
Phase B: Business Architecture |
| Payments |
Phase C: Data Architecture |
| Payments |
Phase C: Application Architecture |
| Payments |
Phase D: Technology Architecture |
| Payments |
Phase E: Opportunities & Solutions |
| Payments |
Phase F: Migration Planning |
| Payments |
Phase G: Implementation Governance |
| Payments |
Phase H: Architecture Change Management |
| Payments |
Requirements Management |
| Payments |
Enterprise Architect |
| Payments |
Business Architect |
| Payments |
Data Architect |
| Payments |
Application Architect |
| Payments |
Technology Architect |
| Payments |
CIO |
| Payments |
Project Manager |
| Payments |
Business Owner |
| Payments |
Principles Catalog |
| Payments |
Stakeholder Map Matrix |
| Payments |
Solution Concept Diagram |
| Payments |
Value Chain Diagram |
| Payments |
Organization/Actor Catalog |
| Payments |
Driver/Goal/Objective Catalog |
| Payments |
Role Catalog |
| Payments |
Business Service/Function Catalog |
| Payments |
Location Catalog |
| Payments |
Process/Event/Control/Product Catalog |
| Payments |
Contract/Measure Catalog |
| Payments |
Business Interaction Matrix |
| Payments |
Actor/Role Matrix |
| Payments |
Business Footprint Diagram |
| Payments |
Business Service/Information Diagram |
| Payments |
Functional Decomposition Diagram |
| Payments |
Goal/Objective/Service Diagram |
| Payments |
Business Use-Case Diagram |
| Payments |
Organization Decomposition Diagram |
| Payments |
Process Flow Diagram |
| Payments |
Event Diagram |
| Payments |
Product Lifecycle Diagram |
| Payments |
Data Entity/Data Component Catalog |
| Payments |
Data Entity/Business Function Matrix |
| Payments |
Application/Data Matrix |
| Payments |
Conceptual Data Diagram |
| Payments |
Logical Data Diagram |
| Payments |
Data Dissemination Diagram |
| Payments |
Data Security Diagram |
| Payments |
Data Migration Diagram |
| Payments |
Data Lifecycle Diagram |
| Payments |
Application Portfolio Catalog |
| Payments |
Interface Catalog |
| Payments |
Application/Organization Matrix |
| Payments |
Role/Application Matrix |
| Payments |
Application/Function Matrix |
| Payments |
Application Interaction Matrix |
| Payments |
Application Communication Diagram |
| Payments |
Application and User Location Diagram |
| Payments |
Application Use-Case Diagram |
| Payments |
Process/Application Realization Diagram |
| Payments |
Application Migration Diagram |
| Payments |
Technology Standards Catalog |
| Payments |
Technology Portfolio Catalog |
| Payments |
Application/Technology Matrix |
| Payments |
System/Technology Matrix |
| Payments |
Environments and Locations Diagram |
| Payments |
Platform Decomposition Diagram |
| Payments |
Networked Computing/Hardware Diagram |
| Payments |
Communications Engineering Diagram |
| Payments |
Project Context Diagram |
| Payments |
Benefits Diagram |
| Payments |
Implementation Factor Matrix |
| Payments |
Consolidated Gap Matrix |
| Payments |
Architecture Roadmap Diagram |
| Payments |
Implementation Governance Diagram |
| Payments |
Architecture Contract |
| Payments |
Change Request Matrix |
| Payments |
Architecture Compliance Review |
| Payments |
Requirements Catalog |
| Payments |
Deciding |
| Payments |
Designing |
| Payments |
Informing |
| Payments |
Governing |
| Payments |
TOGAF 10 Enterprise Metamodel Taxonomy |
| Payments |
Entity by Domain |
| Payments |
Motivation (Principles, Requirements & Governance) |
| Payments |
Business Architecture |
| Payments |
Data Architecture |
| Payments |
Application Architecture |
| Payments |
Technology Architecture |
| Payments |
Implementation & Migration |
| Payments |
MotivationElement |
| Payments |
BusinessArchitectureElement |
| Payments |
DataArchitectureElement |
| Payments |
ApplicationArchitectureElement |
| Payments |
TechnologyArchitectureElement |
| Payments |
ImplementationElement |
| Payments |
Principle |
| Payments |
Requirement |
| Payments |
Constraint |
| Payments |
Assumption |
| Payments |
Gap |
| Payments |
Driver |
| Payments |
Goal |
| Payments |
Objective |
| Payments |
Measure |
| Payments |
Course of Action |
| Payments |
Organization Unit |
| Payments |
Actor |
| Payments |
Role |
| Payments |
Function |
| Payments |
Process |
| Payments |
Event |
| Payments |
Business Service |
| Payments |
Business Capability |
| Payments |
Business Information |
| Payments |
Product |
| Payments |
Contract |
| Payments |
Control |
| Payments |
Service Quality |
| Payments |
Location |
| Payments |
Data Entity |
| Payments |
Logical Data Component |
| Payments |
Physical Data Component |
| Payments |
Logical Application Component |
| Payments |
Physical Application Component |
| Payments |
Application Service |
| Payments |
Logical Technology Component |
| Payments |
Physical Technology Component |
| Payments |
Technology Service |
| Payments |
Work Package |
| Payments |
Capability |
| Payments |
Value Stream |
| Payments |
supports |
| Payments |
realizes |
| Payments |
governs |
| Payments |
used by |
| Payments |
accesses |
| Payments |
communicates with |
| Payments |
decomposes into |
| Payments |
depends on |
| Payments |
tracks |
| Payments |
contains |
| Payments |
is realized through |
| Payments |
Deciding |
| Payments |
Designing |
| Payments |
Informing |
| Payments |
Governing |
| Payments |
Structure |
| Payments |
Behavior |
| Payments |
Deployment |
| Payments |
Dependencies |
| Payments |
Governance |
| Payments |
Evolution |
| Payments |
Quality |
| Payments |
Cost |
| Payments |
Integration |
| Payments |
Stakeholder Interests |
| Payments |
Landscape Overview |
| Payments |
Component Catalog |
| Payments |
Process Flow |
| Payments |
Interface Map |
| Payments |
Deployment Map |
| Payments |
Dependency Matrix |
| Payments |
Impact Analysis |
| Payments |
Decision Log |
| Payments |
Stakeholder Map |
| Payments |
Standards Compliance |
| Payments |
Roadmap |
| Payments |
Gap Analysis |
| Payments |
Architecture Overview Document |
| Payments |
1. Architecture Landscape |
| Payments |
2. Stakeholder Analysis |
| Payments |
3. Component Inventory |
| Payments |
4. Dependency Analysis |
| Payments |
5. Standards Compliance |
| Payments |
Solution Design Document |
| Payments |
1. Solution Context |
| Payments |
2. Process Design |
| Payments |
3. Interface Design |
| Payments |
4. Deployment Design |
| Payments |
5. Architecture Decisions |
| Payments |
Change Impact Assessment |
| Payments |
1. Impact Analysis |
| Payments |
2. Dependency Assessment |
| Payments |
3. Gap Analysis |
| Payments |
4. Migration Roadmap |
| Payments |
Markdown Document |
| Payments |
HTML Report |
| Payments |
PDF Document |
| Payments |
Slide Deck |
| Payments |
Interactive Dashboard |
| Payments |
Rendering Mode |
| Payments |
Shape with Badge |
| Payments |
Icon-Centric |
| Payments |
Shape Only |
| Payments |
What does the model contain? |
| Payments |
Which elements are of this type? |
| Payments |
What is recorded about this element? |
| Payments |
What is this element directly related to? |
| Payments |
What reaches this element within two hops? |
| Payments |
Which elements take part in no relationship? |
| Payments |
Which elements appear in no view? |
| Payments |
Which elements have no definition? |
| Payments |
Which elements share a name with another of the same type? |
| Payments |
Which relationships are out of step with their direct triple? |
| Payments |
Which views show this element? |
| Payments |
What does this view present? |
| Payments |
Which elements does their view's viewpoint not admit? |
| Payments |
Which views follow a viewpoint the loaded metamodels do not define? |
| Payments |
What in the model belongs in a view of this viewpoint? |
| Payments |
What is baseline, target or still awaiting approval? |
| Payments |
Core Taxonomy |
| Payments |
ArchComponent |
| Payments |
LogicalComponent |
| Payments |
PhysicalComponent |
| Payments |
TechComponent |
| Payments |
BusinessComponent |
| Payments |
SoftwareComponent |
| Payments |
HardwareComponent |
| Payments |
CloudComponent |
| Payments |
SaaSComponent |
| Payments |
PaaSComponent |
| Payments |
IaaSComponent |
| Payments |
Compute |
| Payments |
AI + Machine Learning |
| Payments |
Analytics |
| Payments |
Blockchain |
| Payments |
Containers |
| Payments |
Databases |
| Payments |
Developer Tools |
| Payments |
DevOps |
| Payments |
Identity |
| Payments |
Integration |
| Payments |
Internet of Things |
| Payments |
Management and Governance |
| Payments |
Media |
| Payments |
Migration |
| Payments |
Mixed Reality |
| Payments |
Mobile |
| Payments |
Networking |
| Payments |
Security |
| Payments |
Storage |
| Payments |
Web |
| Payments |
ModelConcept |
| Payments |
Element |
| Payments |
QualifiedRelationship |
| Payments |
hasQualifiedRelationship |
| Payments |
unqualifiedForm |
| Payments |
Viewpoint |
| Payments |
View |
| Payments |
Catalog |
| Payments |
Matrix |
| Payments |
Diagram |
| Payments |
Model |
| Payments |
Metamodel |
| Payments |
Architecture |
| Payments |
Framework |
| Payments |
System |
| Payments |
Purpose |
| Payments |
Environment |
| Payments |
Stakeholder |
| Payments |
Consideration |
| Payments |
Concern |
| Payments |
Aspect |
| Payments |
Perspective |
| Payments |
PresentationFormat |
| Payments |
DeliverableTemplate |
| Payments |
TemplateSection |
| Payments |
ModelQuestion |
| Payments |
QuestionSet |
| Payments |
DatasetScope |
| Payments |
Model data |
| Payments |
Model and metamodel |
| Payments |
Question stages |
| Payments |
Orientation |
| Payments |
Resolution |
| Payments |
Discovery |
| Payments |
Analysis |
| Payments |
Enrichment |
| Payments |
Quality |
| Payments |
Views |
| Payments |
QualityAttribute |
| Payments |
Folder |
| Payments |
Concept Owner |
| Payments |
Master Data Source |
| Payments |
QualityMeasure |
| Payments |
hasQualityMeasure |
| Payments |
measuredQualityAttribute |
| Payments |
measuredEntity |
| Payments |
source |
| Payments |
target |
| Payments |
domainIncludes |
| Payments |
rangeIncludes |
| Payments |
Relationship Proposal Order |
| Payments |
definedByFramework |
| Payments |
isAbstract |
| Payments |
isAbstractClass |
| Payments |
refinedInto |
| Payments |
refines |
| Payments |
partOf |
| Payments |
hasPart |
| Payments |
viewConformsToViewpoint |
| Payments |
modelConformsToMetamodel |
| Payments |
inView |
| Payments |
inModel |
| Payments |
exposedInView |
| Payments |
partOfModel |
| Payments |
contains |
| Payments |
modelRepresentsSystem |
| Payments |
Architecture State |
| Payments |
architecture state |
| Payments |
Baseline |
| Payments |
Target |
| Payments |
Transitional |
| Payments |
Approval State |
| Payments |
approval state |
| Payments |
Proposed |
| Payments |
Approved |
| Payments |
meetsPurpose |
| Payments |
environment |
| Payments |
modelHasPurpose |
| Payments |
:purposeRequiresViewpoints |
| Payments |
:purposeRequiresViewpoints |
| Payments |
modelAddressesConsideration |
| Payments |
metamodelIdentifiesConsideration |
| Payments |
metamodelIdentifiesStakeholder |
| Payments |
stakeholderHasConcern |
| Payments |
stakeholderHasPerspective |
| Payments |
stakeholderHasInterestIn |
| Payments |
systemHasArchitecture |
| Payments |
modelExpressesArchitecture |
| Payments |
viewpointTargetsStakeholder |
| Payments |
viewpointFramesConcern |
| Payments |
viewpoint covers aspect |
| Payments |
viewpoint addresses perspective |
| Payments |
includesConcept |
| Payments |
view type |
| Payments |
resultsIn |
| Payments |
refinedByAspect |
| Payments |
viewpointHasPurpose |
| Payments |
preferred Visual Notation |
| Payments |
alternative Visual Notation |
| Payments |
modelConcepts |
| Payments |
architectureViewpoints |
| Payments |
architectureViewpointsRestrictions |
| Payments |
viewpointLibrary |
| Payments |
formalRules |
| Payments |
derivationRules |
| Payments |
conceptClassification |
| Payments |
crossLanguageMappings |
| Payments |
referenceData |
| Payments |
referenceModels |
| Payments |
standardsInformationBase |
| Payments |
associatedStandard |
| Payments |
hasDeliverableTemplate |
| Payments |
hasQuestionSet |
| Payments |
templateRequiresViewpoint |
| Payments |
templateHasSection |
| Payments |
sectionViewpoint |
| Payments |
sectionOrder |
| Payments |
sectionQuery |
| Payments |
sectionResultKey |
| Payments |
deliverableTemplateUsed |
| Payments |
templateTargetsPurpose |
| Payments |
templateHasFormat |
| Payments |
templateResource |
| Payments |
generatorCommand |
| Payments |
questionAddressesConcern |
| Payments |
questionTargetsStakeholder |
| Payments |
questionHasPurpose |
| Payments |
questionFitsViewpoint |
| Payments |
questionStage |
| Payments |
answers |
| Payments |
doesNotProve |
| Payments |
resultIsFinding |
| Payments |
findingSeverity |
| Payments |
findingFocus |
| Payments |
requiresDataset |
| Payments |
requiresMetamodel |
| Payments |
defaultLimit |
| Payments |
resultKey |
| Payments |
focus |
| Payments |
model |
| Payments |
view |
| Payments |
viewpoint |
| Payments |
conceptType |
| Payments |
from |
| Payments |
to |
| Payments |
sectionAsks |
| Payments |
sectionAddressesConcern |
| Payments |
sectionTargetsStakeholder |
| Payments |
templateParameter |
| Payments |
notationSet |
| Payments |
usesNotationSet |
| Payments |
inPresentationContext |
| Payments |
presentationContextScheme |
| Payments |
mentionedIn |
| Payments |
ModelingCategory |
| Payments |
PresentationCategory |
| Payments |
NavigationCategory |
| Payments |
MetamodelingCategory |
| Payments |
IT Service Quality |
| Payments |
Availability |
| Payments |
Responsiveness |
| Payments |
Integrity |
| Payments |
Usability |
| Payments |
Portability |
| Payments |
Recoverability |
| Payments |
Capacity |
| Payments |
Continuity |
| Payments |
Security |
| Payments |
Process |
| Payments |
Activity |
| Payments |
Task |
| Payments |
InformationItem |
| Payments |
Deliverable |
| Payments |
input |
| Payments |
output |
| Payments |
Agreement Processes |
| Payments |
Organizational Project-Enabling Processes |
| Payments |
Technical Management Processes |
| Payments |
Technical Processes |
| Payments |
ISO 12207 Software Lifecycle Model |
| Payments |
Concept |
| Payments |
Development |
| Payments |
Production |
| Payments |
Utilization |
| Payments |
Support |
| Payments |
Retirement |
| Payments |
Software Product Quality |
| Payments |
Functional Suitability |
| Payments |
Performance Efficiency |
| Payments |
Compatibility |
| Payments |
Usability |
| Payments |
Reliability |
| Payments |
Security |
| Payments |
Maintainability |
| Payments |
Portability |
| Payments |
Functional Completeness |
| Payments |
Functional Correctness |
| Payments |
Functional Appropriateness |
| Payments |
Time Behaviour |
| Payments |
Resource Utilization |
| Payments |
Capacity |
| Payments |
Co-Existence |
| Payments |
Interoperability |
| Payments |
Appropriateness Recognizability |
| Payments |
Learnability |
| Payments |
Operability |
| Payments |
User Error Protection |
| Payments |
User Interface Aesthetics |
| Payments |
Accessibility |
| Payments |
Maturity |
| Payments |
Availability |
| Payments |
Fault Tolerance |
| Payments |
Recoverability |
| Payments |
Confidentiality |
| Payments |
Integrity |
| Payments |
Non-Repudiation |
| Payments |
Accountability |
| Payments |
Authenticity |
| Payments |
Modularity |
| Payments |
Reusability |
| Payments |
Analysability |
| Payments |
Modifiability |
| Payments |
Testability |
| Payments |
Adaptability |
| Payments |
Installability |
| Payments |
Replaceability |
| Payments |
Quality in Use |
| Payments |
Primary User |
| Payments |
Secondary User |
| Payments |
Indirect User |
| Payments |
Process |
| Payments |
Activity |
| Payments |
Task |
| Payments |
InformationItem |
| Payments |
Deliverable |
| Payments |
input |
| Payments |
output |
| Payments |
Agreement Processes |
| Payments |
Organizational Project-Enabling Processes |
| Payments |
Technical Management Processes |
| Payments |
Technical Processes |
| Payments |
System |
| Payments |
Architecture |
| Payments |
Architecture Description |
| Payments |
Stakeholder |
| Payments |
Concern |
| Payments |
Architecture Viewpoint |
| Payments |
Architecture View |
| Payments |
Architecture Model |
| Payments |
Architecture Decision |
| Payments |
Architecture Rationale |
| Payments |
Correspondence |
| Payments |
Correspondence Rule |
| Payments |
Process |
| Payments |
Activity |
| Payments |
Task |
| Payments |
InformationItem |
| Payments |
Deliverable |
| Payments |
Architecture Repository |
| Payments |
input |
| Payments |
output |
| Payments |
maintains |
| Payments |
Architecture Governance |
| Payments |
Architecture Management |
| Payments |
Architecture Conceptualization |
| Payments |
Architecture Evaluation |
| Payments |
Architecture Elaboration |
| Payments |
Architecture Enablement |
| Payments |
Data Quality |
| Payments |
Accuracy |
| Payments |
Completeness |
| Payments |
Consistency |
| Payments |
Credibility |
| Payments |
Currentness |
| Payments |
Accessibility |
| Payments |
Compliance |
| Payments |
Confidentiality |
| Payments |
Efficiency |
| Payments |
Precision |
| Payments |
Traceability |
| Payments |
Understandability |
| Payments |
Availability |
| Payments |
Portability |
| Payments |
Recoverability |
| Payments |
Cost Model Shape |
| Payments |
Cost Item Shape |
| Payments |
Investment Case Shape |
| Payments |
Cost-Benefit Analysis Shape |
| Payments |
Budget Shape |
| Payments |
Technical Debt Cost Shape |
| Payments |
Cloud Cost Allocation Shape |
| Payments |
Cost Category |
| Payments |
Investment Type |
| Payments |
Cost Period |
| Payments |
Cost Model |
| Payments |
Cost Item |
| Payments |
Investment Case |
| Payments |
Cost-Benefit Analysis |
| Payments |
Budget |
| Payments |
Forecast |
| Payments |
Cloud Cost Allocation |
| Payments |
Technical Debt Cost |
| Payments |
Migration Cost |
| Payments |
Total Cost of Ownership |
| Payments |
Investment Prioritization |
| Payments |
Technical Debt Visibility |
| Payments |
Cloud Cost Optimization |
| Payments |
Cost Overview |
| Payments |
Investment Portfolio |
| Payments |
Technical Debt Landscape |
| Payments |
Cloud FinOps |
| Payments |
has cost model |
| Payments |
has cost item |
| Payments |
cost category |
| Payments |
annual amount |
| Payments |
one-time amount |
| Payments |
currency |
| Payments |
cost period type |
| Payments |
total TCO |
| Payments |
TCO horizon (years) |
| Payments |
cost model date |
| Payments |
cost model owner |
| Payments |
allocated to capability |
| Payments |
allocated to value stream |
| Payments |
allocation percentage |
| Payments |
has investment case |
| Payments |
investment type |
| Payments |
projected ROI |
| Payments |
payback period (months) |
| Payments |
investment amount |
| Payments |
investment currency |
| Payments |
investment status |
| Payments |
investment sponsor |
| Payments |
has cost-benefit analysis |
| Payments |
estimated cost |
| Payments |
estimated benefit |
| Payments |
net present value |
| Payments |
discount rate |
| Payments |
analysis horizon (years) |
| Payments |
CBA currency |
| Payments |
has budget |
| Payments |
budget amount |
| Payments |
budget currency |
| Payments |
fiscal year |
| Payments |
budget owner |
| Payments |
cloud provider |
| Payments |
cloud service type |
| Payments |
pricing model |
| Payments |
debt type |
| Payments |
debt description |
| Payments |
Financial Architecture Metamodel |
| Payments |
License Cost |
| Payments |
Infrastructure Cost |
| Payments |
Labor Cost |
| Payments |
Support Cost |
| Payments |
Integration Cost |
| Payments |
Compliance Cost |
| Payments |
Opportunity Cost |
| Payments |
Technical Debt Interest |
| Payments |
Training Cost |
| Payments |
Decommissioning Cost |
| Payments |
Run |
| Payments |
Grow |
| Payments |
Transform |
| Payments |
Annual |
| Payments |
Monthly |
| Payments |
Quarterly |
| Payments |
One-Time |
| Payments |
Financial Architecture Concept Scheme |
| Payments |
By Cost Type |
| Payments |
Direct Costs |
| Payments |
License Costs |
| Payments |
Infrastructure Costs |
| Payments |
Cloud Costs (FinOps) |
| Payments |
Labor Costs |
| Payments |
Indirect Costs |
| Payments |
Support & Maintenance Costs |
| Payments |
Compliance Costs |
| Payments |
Hidden Costs |
| Payments |
Technical Debt Costs |
| Payments |
Opportunity Costs |
| Payments |
Integration Costs |
| Payments |
By Investment Type |
| Payments |
Run (Keep the Lights On) |
| Payments |
Grow (Expand Capabilities) |
| Payments |
Transform (Modernize) |
| Payments |
By Analysis Type |
| Payments |
Total Cost of Ownership (TCO) |
| Payments |
Cost-Benefit Analysis (CBA) |
| Payments |
Return on Investment (ROI) |
| Payments |
Net Present Value (NPV) |
| Payments |
FinOps Cloud Cost Analysis |
| Payments |
Availability Tactic |
| Payments |
Detect Faults |
| Payments |
Recover from Faults |
| Payments |
Prevent Faults |
| Payments |
Preparation and Repair |
| Payments |
Reintroduction |
| Payments |
Interoperability Tactic |
| Payments |
Locate |
| Payments |
Manage Interfaces |
| Payments |
Modifiability Tactic |
| Payments |
Reduce Size of a Module |
| Payments |
Increase Cohesion |
| Payments |
Reduce Coupling |
| Payments |
Defer Binding |
| Payments |
Performance Tactic |
| Payments |
Control Resource Demand |
| Payments |
Manage Resources |
| Payments |
Security Tactic |
| Payments |
Detect Attacks |
| Payments |
Resist Attacks |
| Payments |
React to Attacks |
| Payments |
Recover from Attacks |
| Payments |
Reference Architecture |
| Payments |
Reference Model |
| Payments |
Pattern |
| Payments |
Architectural Pattern |
| Payments |
Integration Pattern |
| Payments |
Module Pattern |
| Payments |
Allocation Pattern |
| Payments |
Deployment Pattern |
| Payments |
Tactic |
| Payments |
Impact of Tactic |
| Payments |
Standard |
| Payments |
SBB |
| Payments |
ABB |
| Payments |
domain of interest |
| Payments |
pattern context |
| Payments |
pattern problem overview |
| Payments |
pattern forces overview |
| Payments |
pattern solution overview |
| Payments |
pattern concepts overview |
| Payments |
pattern constraints overview |
| Payments |
based on pattern |
| Payments |
contains pattern |
| Payments |
part of pattern |
| Payments |
related pattern |
| Payments |
applicable tactic |
| Payments |
applied tactic |
| Payments |
realizes tactic |
| Payments |
realized tactic |
| Payments |
related tactic |
| Payments |
broader tactic |
| Payments |
applied with tactic |
| Payments |
applied in pattern |
| Payments |
has impact of tactic |
| Payments |
impact of tactic |
| Payments |
impact measure |
| Payments |
affects element |
| Payments |
implemented already in element |
| Payments |
replicates element |
| Payments |
adds new element |
| Payments |
adds new element following pattern |
| Payments |
adds new element out of pattern |
| Payments |
modifies element |
| Payments |
implements tactic |
| Payments |
implemented tactic |
| Payments |
implements pattern |
| Payments |
uses reference architecture |
| Payments |
addressed quality attribute |
| Payments |
impacted quality attribute |
| Payments |
conforms to metamodel |
| Payments |
Decision Shape |
| Payments |
Accepted Decision Selection Shape |
| Payments |
Accepted Decision Rationale Shape |
| Payments |
Superseded Decision Shape |
| Payments |
Decision State Shape |
| Payments |
Issue Shape |
| Payments |
Option Shape |
| Payments |
Force Shape |
| Payments |
Requirement Shape |
| Payments |
Quality Attribute Requirement Shape |
| Payments |
Force Influence Shape |
| Payments |
Iteration Shape |
| Payments |
Decision |
| Payments |
Issue |
| Payments |
Option |
| Payments |
Force |
| Payments |
Principle |
| Payments |
Requirement |
| Payments |
Functional Requirement |
| Payments |
Quality Attribute Requirement |
| Payments |
Trend |
| Payments |
Personal Preference |
| Payments |
Decision State |
| Payments |
decision state |
| Payments |
Proposed |
| Payments |
Accepted |
| Payments |
Rejected |
| Payments |
Deprecated |
| Payments |
Superseded |
| Payments |
Force Influence |
| Payments |
Impending Influence |
| Payments |
Supporting Influence |
| Payments |
Impact |
| Payments |
Iteration |
| Payments |
Constraint |
| Payments |
Technical Constraint |
| Payments |
Business Constraint |
| Payments |
Policy |
| Payments |
pertains to |
| Payments |
related decision |
| Payments |
justification |
| Payments |
justification document |
| Payments |
influenced by |
| Payments |
influencing force |
| Payments |
has influence |
| Payments |
has influence measure |
| Payments |
has impact measure |
| Payments |
has impact flexibility |
| Payments |
has impact volatility |
| Payments |
related concept |
| Payments |
has selected option |
| Payments |
has alternative |
| Payments |
problem statement |
| Payments |
associated issue |
| Payments |
has issue |
| Payments |
has decision goal |
| Payments |
has decision |
| Payments |
issue caused by |
| Payments |
issue reported by |
| Payments |
issue owner |
| Payments |
includes concept |
| Payments |
affects concept |
| Payments |
makes use of concept |
| Payments |
adds concept |
| Payments |
removes concept |
| Payments |
modifies concept |
| Payments |
addresses force |
| Payments |
opposing force |
| Payments |
complementary force |
| Payments |
has risk |
| Payments |
supported by stakeholder |
| Payments |
has requirement |
| Payments |
requested by stakeholder |
| Payments |
has importance measure |
| Payments |
has difficulty measure |
| Payments |
on quality attribute |
| Payments |
QAS description |
| Payments |
QAS source of stimulus |
| Payments |
QAS stimulus |
| Payments |
QAS environment |
| Payments |
QAS artifact |
| Payments |
QAS response |
| Payments |
QAS response measure |
| Payments |
realize requirement |
| Payments |
caused by |
| Payments |
depends on |
| Payments |
replaces |
| Payments |
superseded by |
| Payments |
conflicts with |
| Payments |
applied in option |
| Payments |
quality attribute match |
| Payments |
ML-Enabled Systems Concept Scheme |
| Payments |
By Lifecycle Phase |
| Payments |
Data Preparation |
| Payments |
Model Development |
| Payments |
Model Deployment |
| Payments |
Model Monitoring |
| Payments |
By Component Role |
| Payments |
Inference Component |
| Payments |
Data Management Component |
| Payments |
Orchestration Component |
| Payments |
Governance Component |
| Payments |
By Stakeholder Domain |
| Payments |
Analytics Modeling (Data Science) |
| Payments |
Analytics Operations (Data Engineering) |
| Payments |
ML Governance |
| Payments |
ML Model Governance Shape |
| Payments |
Dataset Governance Shape |
| Payments |
Serving Infrastructure Shape |
| Payments |
Training Pipeline Shape |
| Payments |
ML Integration Contract Shape |
| Payments |
Explainability |
| Payments |
Fairness |
| Payments |
Adversarial Robustness |
| Payments |
ML Monitorability |
| Payments |
Reproducibility |
| Payments |
Data Privacy (ML) |
| Payments |
Trustworthiness |
| Payments |
Model Freshness |
| Payments |
ML-Enabled Systems Metamodel |
| Payments |
Data Scientist |
| Payments |
Data Engineer |
| Payments |
ML Engineer |
| Payments |
Ethics Committee / Officer |
| Payments |
ML Model Performance |
| Payments |
Data Quality |
| Payments |
Model Drift |
| Payments |
Explainability |
| Payments |
Fairness & Bias |
| Payments |
Adversarial Robustness |
| Payments |
ML Artifact Versioning |
| Payments |
ML Monitorability |
| Payments |
ML Privacy |
| Payments |
ML–SE Collaboration |
| Payments |
ML Component |
| Payments |
ML Model |
| Payments |
Training Pipeline |
| Payments |
Serving Infrastructure |
| Payments |
Feature Store |
| Payments |
Dataset |
| Payments |
ML Monitoring Component |
| Payments |
Experiment Tracker |
| Payments |
Model Registry |
| Payments |
Data Pipeline |
| Payments |
trained on |
| Payments |
produces model |
| Payments |
serves |
| Payments |
monitors |
| Payments |
feeds features |
| Payments |
registered in |
| Payments |
consumes data |
| Payments |
produces dataset |
| Payments |
integrates with |
| Payments |
triggers retraining |
| Payments |
Trained On |
| Payments |
Produces Model |
| Payments |
Integrates With |
| Payments |
Analytics Modeling |
| Payments |
Analytics Operations |
| Payments |
ML System Integration |
| Payments |
ML Ethics & Compliance |
| Payments |
ML Model Catalog |
| Payments |
has model version |
| Payments |
has performance metric |
| Payments |
has model architecture |
| Payments |
has framework |
| Payments |
has retraining schedule |
| Payments |
has serving latency SLA |
| Payments |
has data lineage |
| Payments |
has monitoring plan |
| Payments |
AI Governance Concept Scheme |
| Payments |
By Risk Level |
| Payments |
Unacceptable Risk |
| Payments |
High Risk |
| Payments |
Critical Infrastructure |
| Payments |
Employment & Workers |
| Payments |
Law Enforcement |
| Payments |
Migration & Border Control |
| Payments |
Education & Training |
| Payments |
Essential Services |
| Payments |
Limited Risk |
| Payments |
Minimal Risk |
| Payments |
By Principle |
| Payments |
Fairness |
| Payments |
Transparency |
| Payments |
Accountability |
| Payments |
Safety & Robustness |
| Payments |
Privacy & Data Governance |
| Payments |
Human Agency & Oversight |
| Payments |
Societal & Environmental Wellbeing |
| Payments |
By Lifecycle Phase |
| Payments |
Design & Development |
| Payments |
Testing & Validation |
| Payments |
Deployment |
| Payments |
Monitoring & Maintenance |
| Payments |
Decommissioning |
| Payments |
By Assessment Type |
| Payments |
Conformity Assessment |
| Payments |
Bias Assessment |
| Payments |
Explainability Assessment |
| Payments |
Human Oversight Assessment |
| Payments |
Data Governance Assessment |
| Payments |
Unacceptable Risk |
| Payments |
High Risk |
| Payments |
Limited Risk |
| Payments |
Minimal Risk |
| Payments |
Fairness |
| Payments |
Transparency |
| Payments |
Accountability |
| Payments |
Safety & Robustness |
| Payments |
Privacy & Data Governance |
| Payments |
Human Agency & Oversight |
| Payments |
Societal & Environmental Wellbeing |
| Payments |
Human-in-the-Loop |
| Payments |
Human-on-the-Loop |
| Payments |
Human-in-Command |
| Payments |
Planned |
| Payments |
In Progress |
| Payments |
Completed |
| Payments |
Overdue |
| Payments |
AI Ethics & Governance Metamodel |
| Payments |
AI System Governance Shape |
| Payments |
High-Risk AI System Shape |
| Payments |
Risk Classification Shape |
| Payments |
Conformity Assessment Shape |
| Payments |
Bias Assessment Shape |
| Payments |
Human Oversight Plan Shape |
| Payments |
AI Incident Shape |
| Payments |
AI Governance Policy Shape |
| Payments |
AI Risk Level |
| Payments |
AI Principle |
| Payments |
Human Oversight Mode |
| Payments |
Assessment Status |
| Payments |
AI System |
| Payments |
Risk Classification |
| Payments |
Conformity Assessment |
| Payments |
Bias Assessment |
| Payments |
Explainability Report |
| Payments |
Human Oversight Plan |
| Payments |
AI Governance Policy |
| Payments |
AI Incident |
| Payments |
Transparency Record |
| Payments |
Data Governance Record |
| Payments |
AI Regulatory Compliance |
| Payments |
AI Accountability |
| Payments |
AI Transparency |
| Payments |
Human Oversight of AI |
| Payments |
AI Governance Overview |
| Payments |
AI Risk Assessment |
| Payments |
AI Transparency & Disclosure |
| Payments |
AI Incident Tracking |
| Payments |
wraps ML model |
| Payments |
wraps serving infrastructure |
| Payments |
governed by |
| Payments |
has risk classification |
| Payments |
classified as |
| Payments |
classification rationale |
| Payments |
classification date |
| Payments |
classified by |
| Payments |
has conformity assessment |
| Payments |
has bias assessment |
| Payments |
has explainability report |
| Payments |
has human oversight plan |
| Payments |
has transparency record |
| Payments |
has data governance record |
| Payments |
has incident |
| Payments |
assessed against principle |
| Payments |
assessment result |
| Payments |
assessment date |
| Payments |
assessed by |
| Payments |
assessment findings |
| Payments |
remediation action |
| Payments |
oversight mode |
| Payments |
oversight responsible |
| Payments |
escalation procedure |
| Payments |
intervention conditions |
| Payments |
incident date |
| Payments |
incident description |
| Payments |
root cause analysis |
| Payments |
incident severity |
| Payments |
policy scope |
| Payments |
references framework |
| Payments |
policy effective date |
| Payments |
mandates principle |
| Payments |
Evolvability |
| Payments |
Safety |
| Payments |
Cybersecurity |
| Payments |
Anti-Tamper |
| Payments |
Survivability |
| Payments |
Capacity |
| Payments |
Longevity |
| Payments |
Interoperability |
| Payments |
Adaptability |
| Payments |
Availability |
| Payments |
Maintainability |
| Payments |
Performance |
| Payments |
Reliability |
| Payments |
Reparability |
| Payments |
Architecture Process |
| Payments |
Process Activity |
| Payments |
Process Task |
| Payments |
Process Deliverable |
| Payments |
Information Item |
| Payments |
Process Milestone |
| Payments |
Process Role |
| Payments |
has activity |
| Payments |
activity of process |
| Payments |
has task |
| Payments |
task of activity |
| Payments |
has sub-process |
| Payments |
milestone of process |
| Payments |
governs |
| Payments |
governed by |
| Payments |
input |
| Payments |
output |
| Payments |
produced by |
| Payments |
consumed by |
| Payments |
responsible for |
| Payments |
performed by |
| Payments |
approved by |
| Payments |
precedes |
| Payments |
follows |
| Payments |
triggered by |
| Payments |
related process |
| Payments |
Lifecycle Stage |
| Payments |
Lifecycle Model |
| Payments |
at lifecycle stage |
| Payments |
follows lifecycle |
| Payments |
part of lifecycle |
| Payments |
has stage |
| Payments |
stage order |
| Payments |
next stage |
| Payments |
previous stage |
| Payments |
Application Portfolio Lifecycle |
| Payments |
Plan |
| Payments |
Phase In |
| Payments |
Active |
| Payments |
Phase Out |
| Payments |
Retired |
| Payments |
Lifecycle Stage Assignment Shape |
| Payments |
Lifecycle Stage Shape |
| Payments |
Lifecycle Model Shape |
| Payments |
Canonical Lifecycle Stage Shape |
| Payments |
EA Service Type |
| Payments |
Engagement Status |
| Payments |
EA Maturity Level |
| Payments |
EA Service |
| Payments |
EA Service Catalog |
| Payments |
Service Engagement |
| Payments |
Service Request |
| Payments |
Service Outcome |
| Payments |
Satisfaction Assessment |
| Payments |
EA Capability |
| Payments |
EA Maturity Assessment |
| Payments |
Service Level Expectation |
| Payments |
EA Value Delivery |
| Payments |
EA Capacity Management |
| Payments |
EA Maturity |
| Payments |
Stakeholder Satisfaction |
| Payments |
EA Service Catalog |
| Payments |
Engagement Tracking |
| Payments |
EA Capability Portfolio |
| Payments |
EA Maturity Assessment |
| Payments |
Stakeholder Satisfaction |
| Payments |
offers service |
| Payments |
service type |
| Payments |
has service level expectation |
| Payments |
required capability |
| Payments |
has EA capability |
| Payments |
has engagement |
| Payments |
engagement status |
| Payments |
assigned architect |
| Payments |
engagement for |
| Payments |
engagement start date |
| Payments |
engagement end date |
| Payments |
results in engagement |
| Payments |
requested by |
| Payments |
request date |
| Payments |
request description |
| Payments |
request for service |
| Payments |
decline rationale |
| Payments |
has outcome |
| Payments |
produced deliverable |
| Payments |
influenced decision |
| Payments |
outcome description |
| Payments |
has satisfaction assessment |
| Payments |
satisfaction score |
| Payments |
satisfaction feedback |
| Payments |
satisfaction date |
| Payments |
expected turnaround (days) |
| Payments |
expected scope |
| Payments |
capability description |
| Payments |
capability level |
| Payments |
has maturity assessment |
| Payments |
maturity level |
| Payments |
maturity assessment date |
| Payments |
maturity findings |
| Payments |
maturity assessed by |
| Payments |
EA Service Shape |
| Payments |
Service Engagement Shape |
| Payments |
Service Request Shape |
| Payments |
Service Outcome Shape |
| Payments |
Satisfaction Assessment Shape |
| Payments |
EA Maturity Assessment Shape |
| Payments |
Service Catalog Shape |
| Payments |
EA-as-a-Service Metamodel |
| Payments |
Architecture Review |
| Payments |
Technology Radar |
| Payments |
Portfolio Assessment |
| Payments |
Target State Design |
| Payments |
Standards Guidance |
| Payments |
Impact Analysis |
| Payments |
Modernization Planning |
| Payments |
AI Readiness Assessment |
| Payments |
Compliance Validation |
| Payments |
Onboarding Consultation |
| Payments |
Requested |
| Payments |
Accepted |
| Payments |
In Progress |
| Payments |
Delivered |
| Payments |
Closed |
| Payments |
Declined |
| Payments |
Level 1 — Initial |
| Payments |
Level 2 — Developing |
| Payments |
Level 3 — Defined |
| Payments |
Level 4 — Managed |
| Payments |
Level 5 — Optimizing |
| Payments |
EA-as-a-Service Concept Scheme |
| Payments |
By Service Type |
| Payments |
Advisory Services |
| Payments |
Architecture Review |
| Payments |
Standards Guidance |
| Payments |
Onboarding Consultation |
| Payments |
Assessment Services |
| Payments |
Portfolio Assessment |
| Payments |
Impact Analysis |
| Payments |
AI Readiness Assessment |
| Payments |
Compliance Validation |
| Payments |
Design Services |
| Payments |
Target State Design |
| Payments |
Modernization Planning |
| Payments |
Intelligence Services |
| Payments |
Technology Radar |
| Payments |
By Engagement Duration |
| Payments |
Quick Consultation (< 1 week) |
| Payments |
Standard Engagement (1-4 weeks) |
| Payments |
Strategic Initiative (> 4 weeks) |
| Payments |
By Stakeholder Type |
| Payments |
Executive Leadership |
| Payments |
Product Teams |
| Payments |
Platform Teams |
| Payments |
Delivery Teams |
| Payments |
Governance Bodies |
| Payments |
By Maturity Level |
| Payments |
Level 1 — Initial |
| Payments |
Level 2 — Developing |
| Payments |
Level 3 — Defined |
| Payments |
Level 4 — Managed |
| Payments |
Level 5 — Optimizing |
| Payments |
EDGY 23 Presentation Contexts |
| Payments |
Enterprise designer |
| Payments |
Overview map reader |
| Payments |
EDGY 23 Reference Data |
| Payments |
EDGY Asset Types |
| Payments |
Intangible Asset |
| Payments |
Tangible Asset |
| Payments |
Application |
| Payments |
System Software |
| Payments |
Data |
| Payments |
Know-How |
| Payments |
Financial Asset |
| Payments |
Device |
| Payments |
Facility |
| Payments |
Equipment |
| Payments |
Material |
| Payments |
Network |
| Payments |
EDGY Metric Categories |
| Payments |
Priority |
| Payments |
Investment |
| Payments |
Cost |
| Payments |
Risk |
| Payments |
Performance |
| Payments |
Quality / Fitness |
| Payments |
Traffic Light Values |
| Payments |
Green |
| Payments |
Amber |
| Payments |
Red |
| Payments |
N/A |
| Payments |
EDGY Channel Types |
| Payments |
Digital Channel |
| Payments |
Physical Channel |
| Payments |
Human Interaction Channel |
| Payments |
Third-Party Channel |
| Payments |
Capability Maturity Levels |
| Payments |
Initial |
| Payments |
Developing |
| Payments |
Defined |
| Payments |
Managed |
| Payments |
Optimising |
| Payments |
EDGY 23 Circle Notation (v1) |
| Payments |
Enterprise Element |
| Payments |
Base Element |
| Payments |
Facet Element |
| Payments |
Intersection Element |
| Payments |
Identity Element |
| Payments |
Architecture Element |
| Payments |
Experience Element |
| Payments |
Enterprise Relationship |
| Payments |
Enterprise Label |
| Payments |
People |
| Payments |
Outcome |
| Payments |
Activity |
| Payments |
Object |
| Payments |
Purpose |
| Payments |
Story |
| Payments |
Content |
| Payments |
Capability |
| Payments |
Process |
| Payments |
Asset |
| Payments |
Task |
| Payments |
Journey |
| Payments |
Channel |
| Payments |
Organisation |
| Payments |
Product |
| Payments |
Brand |
| Payments |
links to |
| Payments |
Link |
| Payments |
qualified Link |
| Payments |
flows to |
| Payments |
Flow |
| Payments |
qualified Flow |
| Payments |
part of |
| Payments |
Tree |
| Payments |
qualified Tree |
| Payments |
Tagging |
| Payments |
Metrics |
| Payments |
has tag |
| Payments |
has metric |
| Payments |
contextualises purpose |
| Payments |
expresses purpose |
| Payments |
conveys story |
| Payments |
is part of journey |
| Payments |
uses channel |
| Payments |
traverses channel |
| Payments |
requires asset |
| Payments |
realises capability |
| Payments |
requires asset (process) |
| Payments |
builds brand |
| Payments |
makes product |
| Payments |
embodies brand |
| Payments |
serves task |
| Payments |
features in journey |
| Payments |
requires capability |
| Payments |
creates product |
| Payments |
pursues purpose |
| Payments |
authors story |
| Payments |
has capability |
| Payments |
performs process |
| Payments |
evokes story |
| Payments |
represents purpose |
| Payments |
supports task |
| Payments |
appears in journey |
| Payments |
performs activity |
| Payments |
uses object |
| Payments |
achieves outcome |
| Payments |
leads to outcome |
| Payments |
needed to achieve |
| Payments |
EDGY |
| Payments |
EDGY 23 Metamodel |
| Payments |
EDGY 23 Concept Scheme |
| Payments |
Base Elements |
| Payments |
Facet Elements |
| Payments |
Identity Elements |
| Payments |
Architecture Elements |
| Payments |
Experience Elements |
| Payments |
Intersection Elements |
| Payments |
Relationships |
| Payments |
Labels |
| Payments |
EDGY 23 Standard Notation |
| Payments |
Right Arrow |
| Payments |
Pill |
| Payments |
People glyph |
| Payments |
Tag pill |
| Payments |
Metric pill |
| Payments |
Identity colour |
| Payments |
Experience colour |
| Payments |
Architecture colour |
| Payments |
Organisation intersection colour |
| Payments |
Brand intersection colour |
| Payments |
Product intersection colour |
| Payments |
People notation |
| Payments |
Outcome notation |
| Payments |
Activity notation |
| Payments |
Object notation |
| Payments |
Purpose notation |
| Payments |
Story notation |
| Payments |
Content notation |
| Payments |
Capability notation |
| Payments |
Process notation |
| Payments |
Asset notation |
| Payments |
Task notation |
| Payments |
Journey notation |
| Payments |
Channel notation |
| Payments |
Organisation notation |
| Payments |
Brand notation |
| Payments |
Product notation |
| Payments |
Tagging notation |
| Payments |
Metrics notation |
| Payments |
Link notation |
| Payments |
Flow notation |
| Payments |
Tree notation |
| Payments |
Enterprise Design Overview |
| Payments |
Capability Map Document |
| Payments |
Customer Journey Document |
| Payments |
Service Blueprint Document |
| Payments |
Enterprise Identity Document |
| Payments |
Product Portfolio Document |
| Payments |
Organisation Design Document |
| Payments |
EDGY 23 Viewpoint Catalog |
| Payments |
Full Enterprise Map |
| Payments |
Identity Map |
| Payments |
Architecture Map |
| Payments |
Experience Map |
| Payments |
Capability Map |
| Payments |
Journey Map |
| Payments |
Organisation Map |
| Payments |
Product Map |
| Payments |
Brand Map |
| Payments |
Enterprise Designer |
| Payments |
C-Level Executive |
| Payments |
Enterprise Architect |
| Payments |
Service Designer |
| Payments |
UX Designer |
| Payments |
Product Owner |
| Payments |
Brand Strategist |
| Payments |
Communications Lead |
| Payments |
Operations Lead |
| Payments |
CTO |
| Payments |
Strategy Lead |
| Payments |
HR Lead |
| Payments |
Enterprise Alignment |
| Payments |
Cross-Facet Coherence |
| Payments |
Enterprise Purpose |
| Payments |
Brand Identity |
| Payments |
Storytelling |
| Payments |
Operational Efficiency |
| Payments |
Capability Planning |
| Payments |
Asset Management |
| Payments |
Customer Experience |
| Payments |
Channel Strategy |
| Payments |
Task Completion |
| Payments |
Modularisation |
| Payments |
Investment Decision |
| Payments |
Touchpoint Optimisation |
| Payments |
Service Blueprint |
| Payments |
Organisational Design |
| Payments |
Operating Model |
| Payments |
Governance |
| Payments |
Product Portfolio |
| Payments |
Product-Capability Alignment |
| Payments |
Value Delivery |
| Payments |
Brand Architecture |
| Payments |
Brand-Experience Alignment |
| Payments |
Brand Portfolio |
| Payments |
Element |
| Payments |
Named Element |
| Payments |
Namespace |
| Payments |
Typed Element |
| Payments |
Redefinable Element |
| Payments |
Packageable Element |
| Payments |
Comment |
| Payments |
Constraint |
| Payments |
Relationship |
| Payments |
Directed Relationship |
| Payments |
Type |
| Payments |
Classifier |
| Payments |
Structured Classifier |
| Payments |
Encapsulated Classifier |
| Payments |
Behaviored Classifier |
| Payments |
Class |
| Payments |
Interface |
| Payments |
Data Type |
| Payments |
Primitive Type |
| Payments |
Enumeration |
| Payments |
Enumeration Literal |
| Payments |
Signal |
| Payments |
Feature |
| Payments |
Structural Feature |
| Payments |
Property |
| Payments |
Operation |
| Payments |
Parameter |
| Payments |
Component |
| Payments |
Port |
| Payments |
Connector |
| Payments |
Connector End |
| Payments |
Collaboration |
| Payments |
Collaboration Use |
| Payments |
Package |
| Payments |
Model |
| Payments |
Profile |
| Payments |
Stereotype |
| Payments |
Profile Application |
| Payments |
Actor |
| Payments |
Use Case |
| Payments |
Extension Point |
| Payments |
Deployment Target |
| Payments |
Node |
| Payments |
Device |
| Payments |
Execution Environment |
| Payments |
Artifact |
| Payments |
Deployment Specification |
| Payments |
Manifestation |
| Payments |
Communication Path |
| Payments |
Behavior |
| Payments |
Event |
| Payments |
Trigger |
| Payments |
Opaque Behavior |
| Payments |
Function Behavior |
| Payments |
Activity |
| Payments |
Activity Node |
| Payments |
Action |
| Payments |
Call Action |
| Payments |
Send Signal Action |
| Payments |
Accept Event Action |
| Payments |
Control Node |
| Payments |
Initial Node |
| Payments |
Final Node |
| Payments |
Activity Final Node |
| Payments |
Flow Final Node |
| Payments |
Decision Node |
| Payments |
Merge Node |
| Payments |
Fork Node |
| Payments |
Join Node |
| Payments |
Object Node |
| Payments |
Activity Partition |
| Payments |
Activity Edge |
| Payments |
Control Flow |
| Payments |
Control Flows To |
| Payments |
Object Flow |
| Payments |
Object Flows To |
| Payments |
State Machine |
| Payments |
Region |
| Payments |
Vertex |
| Payments |
State |
| Payments |
Final State |
| Payments |
Pseudostate |
| Payments |
Transition |
| Payments |
Interaction Fragment |
| Payments |
Occurrence Specification |
| Payments |
Message End |
| Payments |
Interaction |
| Payments |
Lifeline |
| Payments |
Message |
| Payments |
Message Occurrence Specification |
| Payments |
Combined Fragment |
| Payments |
Interaction Operand |
| Payments |
Interaction Use |
| Payments |
Execution Specification |
| Payments |
Behavior Execution Specification |
| Payments |
State Invariant |
| Payments |
General Ordering |
| Payments |
Gate |
| Payments |
Interaction Constraint |
| Payments |
Destruction Occurrence Specification |
| Payments |
Continuation |
| Payments |
Information Item |
| Payments |
Information Flow |
| Payments |
Information Flows To |
| Payments |
Associated With |
| Payments |
Association |
| Payments |
Aggregates |
| Payments |
Aggregation |
| Payments |
Composed Of |
| Payments |
Composition |
| Payments |
Generalizes |
| Payments |
Generalization |
| Payments |
Realizes |
| Payments |
Realization |
| Payments |
Realizes Interface |
| Payments |
Interface Realization |
| Payments |
Depends On |
| Payments |
Dependency |
| Payments |
Uses |
| Payments |
Usage |
| Payments |
Abstracts |
| Payments |
Abstraction |
| Payments |
Includes |
| Payments |
Include |
| Payments |
Extends |
| Payments |
Extend |
| Payments |
Deployed On |
| Payments |
Deployment |
| Payments |
Imports Package |
| Payments |
Package Import |
| Payments |
Merges Package |
| Payments |
Package Merge |
| Payments |
Name |
| Payments |
Namespace |
| Payments |
Visibility |
| Payments |
Is Abstract |
| Payments |
Is Leaf |
| Payments |
Is Static |
| Payments |
Is Read Only |
| Payments |
Is Derived |
| Payments |
Is Ordered |
| Payments |
Is Unique |
| Payments |
Lower Bound |
| Payments |
Upper Bound |
| Payments |
Default Value |
| Payments |
Body |
| Payments |
Guard |
| Payments |
Effect |
| Payments |
Is Composite |
| Payments |
Is Orthogonal |
| Payments |
File Name |
| Payments |
Is Indirectly Instantiated |
| Payments |
Is Behavior |
| Payments |
Is Service |
| Payments |
Is Conjugated |
| Payments |
Has Lifeline |
| Payments |
Has Message |
| Payments |
Has Fragment |
| Payments |
Send Event |
| Payments |
Receive Event |
| Payments |
Message Sort |
| Payments |
Message Kind |
| Payments |
Message |
| Payments |
Signature |
| Payments |
Covered |
| Payments |
Represents |
| Payments |
Sequence Number |
| Payments |
Ordering Before |
| Payments |
Ordering After |
| Payments |
Execution Start |
| Payments |
Execution Finish |
| Payments |
Interaction Operator |
| Payments |
Has Operand |
| Payments |
Refers To |
| Payments |
Guard Constraint |
| Payments |
Has General Ordering |
| Payments |
To After |
| Payments |
To Before |
| Payments |
Formal Gate |
| Payments |
CFragment Gate |
| Payments |
Actual Gate |
| Payments |
Execution Occurrence Specification |
| Payments |
Execution |
| Payments |
Aggregation Kind |
| Payments |
Parameter Direction |
| Payments |
Pseudostate Kind |
| Payments |
Transition Kind |
| Payments |
Connector Kind |
| Payments |
Visibility Kind |
| Payments |
public |
| Payments |
private |
| Payments |
protected |
| Payments |
package |
| Payments |
Aggregation Kind |
| Payments |
none |
| Payments |
shared |
| Payments |
composite |
| Payments |
Parameter Direction Kind |
| Payments |
in |
| Payments |
out |
| Payments |
inout |
| Payments |
return |
| Payments |
Message Sort |
| Payments |
synchCall |
| Payments |
asynchCall |
| Payments |
asynchSignal |
| Payments |
createMessage |
| Payments |
deleteMessage |
| Payments |
reply |
| Payments |
Message Kind |
| Payments |
complete |
| Payments |
lost |
| Payments |
found |
| Payments |
unknown |
| Payments |
Pseudostate Kind |
| Payments |
initial |
| Payments |
deepHistory |
| Payments |
shallowHistory |
| Payments |
join |
| Payments |
fork |
| Payments |
junction |
| Payments |
choice |
| Payments |
entryPoint |
| Payments |
exitPoint |
| Payments |
terminate |
| Payments |
Transition Kind |
| Payments |
external |
| Payments |
internal |
| Payments |
local |
| Payments |
Interaction Operator Kind |
| Payments |
alt |
| Payments |
opt |
| Payments |
loop |
| Payments |
break |
| Payments |
par |
| Payments |
seq |
| Payments |
strict |
| Payments |
critical |
| Payments |
neg |
| Payments |
assert |
| Payments |
ignore |
| Payments |
consider |
| Payments |
Connector Kind |
| Payments |
assembly |
| Payments |
delegation |
| Payments |
UML 2.5.1 Standard Notation |
| Payments |
UML 2.5.1 Viewpoint Catalog |
| Payments |
Structural Viewpoints |
| Payments |
Behavioral Viewpoints |
| Payments |
Class Diagram |
| Payments |
Object Diagram |
| Payments |
Component Diagram |
| Payments |
Deployment Diagram |
| Payments |
Package Diagram |
| Payments |
Composite Structure Diagram |
| Payments |
Profile Diagram |
| Payments |
Use Case Diagram |
| Payments |
Activity Diagram |
| Payments |
State Machine Diagram |
| Payments |
Sequence Diagram |
| Payments |
Communication Diagram |
| Payments |
Timing Diagram |
| Payments |
Interaction Overview Diagram |
| Payments |
UML |
| Payments |
MOF 2.5.1 |
| Payments |
ODM 1.1 |
| Payments |
UML 2.5.1 Metamodel |
| Payments |
UML 2.5.1 Concept Scheme |
| Payments |
By Diagram Type |
| Payments |
Structural Diagrams |
| Payments |
Class Diagram |
| Payments |
Class |
| Payments |
Interface |
| Payments |
Data Type |
| Payments |
Enumeration |
| Payments |
Component Diagram |
| Payments |
Component |
| Payments |
Port |
| Payments |
Connector |
| Payments |
Package Diagram |
| Payments |
Package |
| Payments |
Deployment Diagram |
| Payments |
Node |
| Payments |
Device |
| Payments |
Execution Environment |
| Payments |
Artifact |
| Payments |
Composite Structure Diagram |
| Payments |
Collaboration |
| Payments |
Object Diagram |
| Payments |
Profile Diagram |
| Payments |
Profile |
| Payments |
Stereotype |
| Payments |
Behavioral Diagrams |
| Payments |
Use Case Diagram |
| Payments |
Actor |
| Payments |
Use Case |
| Payments |
Activity Diagram |
| Payments |
Activity |
| Payments |
Action |
| Payments |
Decision Node |
| Payments |
Fork Node |
| Payments |
Join Node |
| Payments |
State Machine Diagram |
| Payments |
State Machine |
| Payments |
State |
| Payments |
Transition |
| Payments |
Sequence Diagram |
| Payments |
Interaction |
| Payments |
Lifeline |
| Payments |
Message |
| Payments |
Combined Fragment |
| Payments |
Communication Diagram |
| Payments |
Timing Diagram |
| Payments |
Interaction Overview Diagram |
| Payments |
By Metaclass Category |
| Payments |
Classifiers |
| Payments |
Relationships |
| Payments |
Behaviors |
| Payments |
Packaging |
| Payments |
Deployment |
| Payments |
By Enumeration Value |
| Payments |
Visibility Kinds |
| Payments |
Aggregation Kinds |
| Payments |
Parameter Direction Kinds |
| Payments |
Message Sorts |
| Payments |
Message Kinds |
| Payments |
Pseudostate Kinds |
| Payments |
Transition Kinds |
| Payments |
Interaction Operator Kinds |
| Payments |
Connector Kinds |
| Payments |
Basic |
| Payments |
Basic Metamodel |
| Payments |
Basic Concept Scheme |
| Payments |
Basic Concepts |
| Payments |
Elements |
| Payments |
Relationships |
| Payments |
Basic Bubble Notation |
| Payments |
Element notation |
| Payments |
Element style |
| Payments |
Relationship notation |
| Payments |
Association notation |
| Payments |
Aggregation notation |
| Payments |
Node |
| Payments |
SpecialNode |
| Payments |
GroupNode |
| Payments |
Association |
| Payments |
Association |
| Payments |
qualified Association |
| Payments |
Aggregation |
| Payments |
Aggregation |
| Payments |
qualified Aggregation |
| Payments |
Connection |
| Payments |
Connection |
| Payments |
qualified Connection |
| Payments |
Basic Presentation Contexts |
| Payments |
Modeller |
| Payments |
Workshop participant |
| Payments |
Basic Rectangle Notation |
| Payments |
Element notation |
| Payments |
Element style |
| Payments |
Relationship notation |
| Payments |
Association notation |
| Payments |
Aggregation notation |
| Payments |
Activity |
| Payments |
AdHocSubProcess |
| Payments |
Artifact |
| Payments |
Assignment |
| Payments |
Association |
| Payments |
Auditing |
| Payments |
BaseElement |
| Payments |
BoundaryEvent |
| Payments |
BusinessRuleTask |
| Payments |
CallActivity |
| Payments |
CallChoreography |
| Payments |
CallConversation |
| Payments |
CallableElement |
| Payments |
CancelEventDefinition |
| Payments |
CatchEvent |
| Payments |
Category |
| Payments |
CategoryValue |
| Payments |
Choreography |
| Payments |
ChoreographyActivity |
| Payments |
ChoreographyTask |
| Payments |
Collaboration |
| Payments |
CompensateEventDefinition |
| Payments |
ComplexBehaviorDefinition |
| Payments |
ComplexGateway |
| Payments |
ConditionalEventDefinition |
| Payments |
Conversation |
| Payments |
ConversationAssociation |
| Payments |
ConversationLink |
| Payments |
ConversationNode |
| Payments |
CorrelationKey |
| Payments |
CorrelationProperty |
| Payments |
CorrelationPropertyBinding |
| Payments |
CorrelationPropertyRetrievalExpression |
| Payments |
CorrelationSubscription |
| Payments |
DataAssociation |
| Payments |
DataInput |
| Payments |
DataInputAssociation |
| Payments |
DataObject |
| Payments |
DataObjectReference |
| Payments |
DataOutput |
| Payments |
DataOutputAssociation |
| Payments |
DataState |
| Payments |
DataStore |
| Payments |
DataStoreReference |
| Payments |
Documentation |
| Payments |
EndEvent |
| Payments |
EndPoint |
| Payments |
Error |
| Payments |
ErrorEventDefinition |
| Payments |
Escalation |
| Payments |
EscalationEventDefinition |
| Payments |
Event |
| Payments |
EventBasedGateway |
| Payments |
EventDefinition |
| Payments |
ExclusiveGateway |
| Payments |
Expression |
| Payments |
Extension |
| Payments |
ExtensionAttributeDefinition |
| Payments |
ExtensionAttributeValue |
| Payments |
ExtensionDefinition |
| Payments |
FlowElement |
| Payments |
FlowElementsContainer |
| Payments |
FlowNode |
| Payments |
FormalExpression |
| Payments |
Gateway |
| Payments |
GlobalBusinessRuleTask |
| Payments |
GlobalChoreographyTask |
| Payments |
GlobalConversation |
| Payments |
GlobalManualTask |
| Payments |
GlobalScriptTask |
| Payments |
GlobalTask |
| Payments |
GlobalUserTask |
| Payments |
Group |
| Payments |
HumanPerformer |
| Payments |
ImplicitThrowEvent |
| Payments |
InclusiveGateway |
| Payments |
InputOutputBinding |
| Payments |
InputOutputSpecification |
| Payments |
InputSet |
| Payments |
InteractionNode |
| Payments |
Interface |
| Payments |
IntermediateCatchEvent |
| Payments |
IntermediateThrowEvent |
| Payments |
ItemAwareElement |
| Payments |
ItemDefinition |
| Payments |
Lane |
| Payments |
LaneSet |
| Payments |
LinkEventDefinition |
| Payments |
LoopCharacteristics |
| Payments |
ManualTask |
| Payments |
Message |
| Payments |
MessageEventDefinition |
| Payments |
MessageFlow |
| Payments |
MessageFlowAssociation |
| Payments |
Monitoring |
| Payments |
MultiInstanceLoopCharacteristics |
| Payments |
Operation |
| Payments |
OutputSet |
| Payments |
ParallelGateway |
| Payments |
Participant |
| Payments |
ParticipantAssociation |
| Payments |
ParticipantMultiplicity |
| Payments |
PartnerEntity |
| Payments |
PartnerRole |
| Payments |
Performer |
| Payments |
PotentialOwner |
| Payments |
Process |
| Payments |
Property |
| Payments |
ReceiveTask |
| Payments |
Relationship |
| Payments |
Rendering |
| Payments |
Resource |
| Payments |
ResourceAssignmentExpression |
| Payments |
ResourceParameter |
| Payments |
ResourceParameterBinding |
| Payments |
ResourceRole |
| Payments |
RootElement |
| Payments |
ScriptTask |
| Payments |
SendTask |
| Payments |
SequenceFlow |
| Payments |
ServiceTask |
| Payments |
Signal |
| Payments |
SignalEventDefinition |
| Payments |
StandardLoopCharacteristics |
| Payments |
StartEvent |
| Payments |
SubChoreography |
| Payments |
SubConversation |
| Payments |
SubProcess |
| Payments |
Task |
| Payments |
TerminateEventDefinition |
| Payments |
TextAnnotation |
| Payments |
ThrowEvent |
| Payments |
TimerEventDefinition |
| Payments |
Transaction |
| Payments |
UserTask |
| Payments |
AdHocOrdering |
| Payments |
Parallel |
| Payments |
Sequential |
| Payments |
AssociationDirection |
| Payments |
None |
| Payments |
One |
| Payments |
Both |
| Payments |
ChoreographyLoopType |
| Payments |
None |
| Payments |
Standard |
| Payments |
MultiInstanceSequential |
| Payments |
MultiInstanceParallel |
| Payments |
EventBasedGatewayType |
| Payments |
Parallel |
| Payments |
Exclusive |
| Payments |
GatewayDirection |
| Payments |
Unspecified |
| Payments |
Converging |
| Payments |
Diverging |
| Payments |
Mixed |
| Payments |
ItemKind |
| Payments |
Physical |
| Payments |
Information |
| Payments |
MultiInstanceBehavior |
| Payments |
None |
| Payments |
One |
| Payments |
All |
| Payments |
Complex |
| Payments |
ProcessType |
| Payments |
None |
| Payments |
Public |
| Payments |
Private |
| Payments |
RelationshipDirection |
| Payments |
None |
| Payments |
Forward |
| Payments |
Backward |
| Payments |
Both |
| Payments |
activationCondition |
| Payments |
activityRef |
| Payments |
artifacts |
| Payments |
assignment |
| Payments |
associationDirection |
| Payments |
attachedToRef |
| Payments |
auditing |
| Payments |
behavior |
| Payments |
body |
| Payments |
boundaryEventRefs |
| Payments |
calledChoreographyRef |
| Payments |
calledCollaborationRef |
| Payments |
calledElementRef |
| Payments |
cancelActivity |
| Payments |
cancelRemainingInstances |
| Payments |
capacity |
| Payments |
categorizedFlowElements |
| Payments |
categoryValue |
| Payments |
categoryValueRef |
| Payments |
childLaneSet |
| Payments |
choreographyRef |
| Payments |
completionCondition |
| Payments |
completionQuantity |
| Payments |
complexBehaviorDefinition |
| Payments |
condition |
| Payments |
conditionExpression |
| Payments |
conversationAssociations |
| Payments |
conversationLinks |
| Payments |
conversationNodes |
| Payments |
conversations |
| Payments |
correlationKeyRef |
| Payments |
correlationKeys |
| Payments |
correlationPropertyBinding |
| Payments |
correlationPropertyRef |
| Payments |
correlationPropertyRetrievalExpression |
| Payments |
correlationSubscriptions |
| Payments |
dataInputAssociation |
| Payments |
dataInputAssociations |
| Payments |
dataInputRefs |
| Payments |
dataInputs |
| Payments |
dataObjectRef |
| Payments |
dataOutputAssociation |
| Payments |
dataOutputAssociations |
| Payments |
dataOutputRefs |
| Payments |
dataOutputs |
| Payments |
dataPath |
| Payments |
dataState |
| Payments |
dataStoreRef |
| Payments |
default |
| Payments |
definition |
| Payments |
definitionalCollaborationRef |
| Payments |
direction |
| Payments |
documentation |
| Payments |
endPointRefs |
| Payments |
errorCode |
| Payments |
errorRef |
| Payments |
errorRefs |
| Payments |
escalationCode |
| Payments |
escalationRef |
| Payments |
evaluatesToTypeRef |
| Payments |
event |
| Payments |
eventDefinitionRefs |
| Payments |
eventDefinitions |
| Payments |
eventGatewayType |
| Payments |
expression |
| Payments |
extensionAttributeDefinition |
| Payments |
extensionAttributeDefinitions |
| Payments |
extensionDefinition |
| Payments |
extensionDefinitions |
| Payments |
extensionValues |
| Payments |
flowElements |
| Payments |
flowNodeRefs |
| Payments |
from |
| Payments |
gatewayDirection |
| Payments |
id |
| Payments |
implementation |
| Payments |
implementationRef |
| Payments |
import |
| Payments |
inMessageRef |
| Payments |
incoming |
| Payments |
incomingConversationLinks |
| Payments |
initiatingParticipantRef |
| Payments |
innerConversationNodeRef |
| Payments |
innerMessageFlowRef |
| Payments |
innerParticipantRef |
| Payments |
inputDataItem |
| Payments |
inputDataRef |
| Payments |
inputSet |
| Payments |
inputSetRefs |
| Payments |
inputSetWithOptional |
| Payments |
inputSetWithWhileExecuting |
| Payments |
inputSets |
| Payments |
instantiate |
| Payments |
interfaceRefs |
| Payments |
ioBinding |
| Payments |
ioSpecification |
| Payments |
isClosed |
| Payments |
isCollection |
| Payments |
isExecutable |
| Payments |
isForCompensation |
| Payments |
isImmediate |
| Payments |
isInterrupting |
| Payments |
isReference |
| Payments |
isRequired |
| Payments |
isSequential |
| Payments |
isUnlimited |
| Payments |
itemKind |
| Payments |
itemRef |
| Payments |
itemSubjectRef |
| Payments |
laneSets |
| Payments |
lanes |
| Payments |
language |
| Payments |
loopCardinality |
| Payments |
loopCharacteristics |
| Payments |
loopCondition |
| Payments |
loopDataInputRef |
| Payments |
loopDataOutputRef |
| Payments |
loopMaximum |
| Payments |
loopType |
| Payments |
maximum |
| Payments |
messageFlowAssociations |
| Payments |
messageFlowRef |
| Payments |
messageFlowRefs |
| Payments |
messageFlows |
| Payments |
messagePath |
| Payments |
messageRef |
| Payments |
method |
| Payments |
minimum |
| Payments |
monitoring |
| Payments |
mustUnderstand |
| Payments |
name |
| Payments |
noneBehaviorEventRef |
| Payments |
oneBehaviorEventRef |
| Payments |
operationRef |
| Payments |
operations |
| Payments |
optionalInputRefs |
| Payments |
optionalOutputRefs |
| Payments |
ordering |
| Payments |
outMessageRef |
| Payments |
outerConversationNodeRef |
| Payments |
outerMessageFlowRef |
| Payments |
outerParticipantRef |
| Payments |
outgoing |
| Payments |
outgoingConversationLinks |
| Payments |
outputDataItem |
| Payments |
outputDataRef |
| Payments |
outputSet |
| Payments |
outputSetRefs |
| Payments |
outputSetWithOptional |
| Payments |
outputSetWithWhileExecuting |
| Payments |
outputSets |
| Payments |
parallelMultiple |
| Payments |
parameterRef |
| Payments |
participantAssociations |
| Payments |
participantMultiplicity |
| Payments |
participantRef |
| Payments |
participantRefs |
| Payments |
participants |
| Payments |
partitionElement |
| Payments |
partitionElementRef |
| Payments |
processRef |
| Payments |
processType |
| Payments |
properties |
| Payments |
protocol |
| Payments |
renderings |
| Payments |
resourceAssignmentExpression |
| Payments |
resourceParameterBindings |
| Payments |
resourceParameters |
| Payments |
resourceRef |
| Payments |
resources |
| Payments |
script |
| Payments |
scriptFormat |
| Payments |
scriptLanguage |
| Payments |
signalRef |
| Payments |
source |
| Payments |
sourceRef |
| Payments |
sources |
| Payments |
startQuantity |
| Payments |
structureRef |
| Payments |
supportedInterfaceRefs |
| Payments |
supports |
| Payments |
target |
| Payments |
targetRef |
| Payments |
targets |
| Payments |
testBefore |
| Payments |
text |
| Payments |
textFormat |
| Payments |
timeCycle |
| Payments |
timeDate |
| Payments |
timeDuration |
| Payments |
to |
| Payments |
transformation |
| Payments |
triggeredByEvent |
| Payments |
type |
| Payments |
value |
| Payments |
valueRef |
| Payments |
waitForCompletion |
| Payments |
whileExecutingInputRefs |
| Payments |
whileExecutingOutputRefs |
| Payments |
sequence flow |
| Payments |
message flow |
| Payments |
association |
| Payments |
conversation link |
| Payments |
data association |
| Payments |
BPMN 2.0.2 Viewpoint Catalog |
| Payments |
Process Flow Diagram |
| Payments |
Collaboration Diagram |
| Payments |
Choreography Diagram |
| Payments |
Conversation Diagram |
| Payments |
BPMN |
| Payments |
BPMN 2.0.2 Metamodel |
| Payments |
BPMNDiagram |
| Payments |
BPMNPlane |
| Payments |
BPMNShape |
| Payments |
BPMNEdge |
| Payments |
BPMNLabel |
| Payments |
BPMNLabelStyle |
| Payments |
MessageVisibleKind |
| Payments |
initiating |
| Payments |
non_initiating |
| Payments |
ParticipantBandKind |
| Payments |
top_initiating |
| Payments |
middle_initiating |
| Payments |
bottom_initiating |
| Payments |
top_non_initiating |
| Payments |
middle_non_initiating |
| Payments |
bottom_non_initiating |
| Payments |
bpmnElement |
| Payments |
plane |
| Payments |
label |
| Payments |
labelStyle |
| Payments |
sourceElement |
| Payments |
targetElement |
| Payments |
choreographyActivityShape |
| Payments |
font |
| Payments |
isExpanded |
| Payments |
isHorizontal |
| Payments |
isMarkerVisible |
| Payments |
isMessageVisible |
| Payments |
messageVisibleKind |
| Payments |
participantBandKind |
| Payments |
DiagramElement |
| Payments |
Node |
| Payments |
Edge |
| Payments |
Shape |
| Payments |
LabeledShape |
| Payments |
Plane |
| Payments |
Label |
| Payments |
LabeledEdge |
| Payments |
Diagram |
| Payments |
Style |
| Payments |
bounds |
| Payments |
waypoint |
| Payments |
source |
| Payments |
target |
| Payments |
modelElement |
| Payments |
ownedElement |
| Payments |
owningElement |
| Payments |
owningDiagram |
| Payments |
rootElement |
| Payments |
planeElement |
| Payments |
ownedLabel |
| Payments |
ownedStyle |
| Payments |
style |
| Payments |
id |
| Payments |
name |
| Payments |
documentation |
| Payments |
resolution |
| Payments |
Definitions |
| Payments |
Import |
| Payments |
diagrams |
| Payments |
exporter |
| Payments |
exporterVersion |
| Payments |
expressionLanguage |
| Payments |
extensions |
| Payments |
importType |
| Payments |
imports |
| Payments |
location |
| Payments |
name |
| Payments |
namespace |
| Payments |
relationships |
| Payments |
rootElements |
| Payments |
targetNamespace |
| Payments |
typeLanguage |
| Payments |
BPMN 2.0.2 Standard Notation |
| Payments |
BPMN 2.0.2 Concept Scheme |
| Payments |
Flow Objects |
| Payments |
Connecting Objects |
| Payments |
Swim Lanes |
| Payments |
Artifacts |
| Payments |
Collaborations |
| Payments |
Activities |
| Payments |
Events |
| Payments |
Gateways |
| Payments |
Sequence Flow |
| Payments |
Message Flow |
| Payments |
Association |
| Payments |
Data Association |
| Payments |
Pool (Participant) |
| Payments |
Lane |
| Payments |
Data Object |
| Payments |
Data Store |
| Payments |
Message |
| Payments |
Group |
| Payments |
Text Annotation |
| Payments |
Collaboration |
| Payments |
Choreography |
| Payments |
Conversation |
| Payments |
Process Documentation |
| Payments |
1. Process Flows |
| Payments |
2. Participant Collaborations |
| Payments |
3. Conversation Overview |
| Payments |
Bounds |
| Payments |
Point |
| Payments |
Font |
| Payments |
x |
| Payments |
y |
| Payments |
width |
| Payments |
height |
| Payments |
name |
| Payments |
size |
| Payments |
isBold |
| Payments |
isItalic |
| Payments |
isUnderline |
| Payments |
isStrikeThrough |
| Payments |
ArchiMate 3.0 Concept Scheme |
| Payments |
Archimate Concept |
| Payments |
ArchimateElement |
| Payments |
ArchimateRelationship |
| Payments |
Structural Relationship |
| Payments |
Dependency Relationship |
| Payments |
Dynamic Relationship |
| Payments |
Other Relationship |
| Payments |
Relationship Connector |
| Payments |
ArchiMate Element by Layer |
| Payments |
Strategy Layer |
| Payments |
Business Layer |
| Payments |
Application Layer |
| Payments |
Technology Layer |
| Payments |
Physical Layer |
| Payments |
Implementation and Migration Layer |
| Payments |
ArchiMate Element by Aspect |
| Payments |
Motivation Element |
| Payments |
Structure Element |
| Payments |
Active Structure Element |
| Payments |
External Active Structure Element |
| Payments |
Internal Active Structure Element |
| Payments |
Passive Structure Element |
| Payments |
Behavior Element |
| Payments |
External Behavior Element |
| Payments |
Internal Behavior Element |
| Payments |
Event |
| Payments |
Composite Element |
| Payments |
ArchiMate 4.0 Reference Models |
| Payments |
Architecture Patterns |
| Payments |
Layered Architecture |
| Payments |
Microservices Architecture |
| Payments |
Event-Driven Architecture |
| Payments |
Service-Oriented Architecture |
| Payments |
Industry Reference Models |
| Payments |
BIAN (Banking Industry Architecture Network) |
| Payments |
TM Forum Frameworx |
| Payments |
ACORD Framework |
| Payments |
derivation certainty |
| Payments |
Derivation Certainty Level |
| Payments |
valid |
| Payments |
potential |
| Payments |
Qualify the model's relationships |
| Payments |
DR1: Transitivity of specialization |
| Payments |
DR2: Derivation between structural relationships |
| Payments |
DR3: Derivation between structural and dependency relationships |
| Payments |
DR4: Derivation between opposing structural and dependency relationships |
| Payments |
DR5: Derivation between structural and dynamic relationships |
| Payments |
DR6: Derivation between structural and flow relationships |
| Payments |
DR7: Derivation between structural and triggering relationships |
| Payments |
DR8: Derivation between triggering relationships |
| Payments |
PDR1: Specialization and another relationship, in line |
| Payments |
PDR2: Specialization and another relationship, in the opposite direction |
| Payments |
PDR3: Another relationship from the specialized element |
| Payments |
PDR4: Another relationship to the specialized element |
| Payments |
PDR5: Dependency to the source of a structural relationship |
| Payments |
PDR6: Dependency from the source of a structural relationship |
| Payments |
PDR7: Derivation between dependency relationships |
| Payments |
PDR8: Flow and a structural relationship, in line |
| Payments |
PDR9: Dynamic relationship from the source of a structural relationship |
| Payments |
PDR10: Derivation between flow relationships |
| Payments |
PDR11: Triggering and a structural relationship to its target |
| Payments |
PDR12: Elements aggregated in a grouping |
| Payments |
Appendix B.4, on derivations |
| Payments |
No Circular Composition |
| Payments |
No Circular Aggregation |
| Payments |
Composition Part Uniqueness |
| Payments |
AndJunction Type Homogeneity |
| Payments |
OrJunction Type Homogeneity |
| Payments |
Deep Specialization Chain Warning |
| Payments |
How is the model spread over the ArchiMate domains? |
| Payments |
Which relationships cross domains, and of which kind? |
| Payments |
Who is responsible for what? |
| Payments |
Which applications depend on which? |
| Payments |
Who reads and writes which information? |
| Payments |
What is affected if this element changes? |
| Payments |
What realises each capability? |
| Payments |
What do stakeholders care about? |
| Payments |
How does each requirement trace to goals and to the elements that realise it? |
| Payments |
What motivates each principle, and what does it constrain? |
| Payments |
What does each work package deliver, and what does that realise? |
| Payments |
What changes between these two plateaus? |
| Payments |
Which processes and functions has nobody been assigned to? |
| Payments |
Which services does nothing realise? |
| Payments |
Which application components run on no technology? |
| Payments |
Which information is read but never written? |
| Payments |
Which capabilities does nothing realise? |
| Payments |
Which requirements does no architecture element realise? |
| Payments |
Which principles has no requirement made concrete? |
| Payments |
What in the model belongs in a view of this ArchiMate viewpoint? |
| Payments |
Where could the model be more concrete? |
| Payments |
Which relationships give rise to the most potential derivations? |
| Payments |
Redundant Application Realizing Service |
| Payments |
Redundant Function Support |
| Payments |
Single Authoritative Data Writer |
| Payments |
Single Business Object Owner |
| Payments |
Application Component Ownership |
| Payments |
Process Performer |
| Payments |
Data Object Stewardship |
| Payments |
Business Process Direct Technology Dependency |
| Payments |
Technology Serving Business Directly |
| Payments |
Application Component Without Service |
| Payments |
Direct Component-to-Component Serving |
| Payments |
Excessive Technology Diversity Per Service |
| Payments |
Single Point of Failure |
| Payments |
Single Deployment Node |
| Payments |
Service Without Realization |
| Payments |
Capability Without Behaviour Realization |
| Payments |
Process Automated by Multiple Application Components |
| Payments |
Function Automated by Multiple Application Components |
| Payments |
Orphaned Element |
| Payments |
Capability Without Goal |
| Payments |
Requirement Without Realization |
| Payments |
Architecture Definition Document |
| Payments |
1. Business Domain |
| Payments |
2. Process Cooperation |
| Payments |
3. Application Domain |
| Payments |
4. Technology Domain |
| Payments |
5. Cross-Domain Overview |
| Payments |
6. Implementation & Deployment |
| Payments |
7. Realisation Roadmap |
| Payments |
Appendix. Quality of this Description |
| Payments |
Architecture Requirements Specification |
| Payments |
1. Stakeholders and Drivers |
| Payments |
2. Goals and Outcomes |
| Payments |
3. Requirements and their Realisation |
| Payments |
Architecture Principles Document |
| Payments |
1. Principles |
| Payments |
2. Strategy Alignment |
| Payments |
Change Impact Assessment (ArchiMate 4.0) |
| Payments |
1. What Depends on the Element |
| Payments |
2. Views to Update |
| Payments |
3. Baseline to Target |
| Payments |
ArchiMate 4.0 Concept Scheme |
| Payments |
Element by Domain |
| Payments |
Common Domain |
| Payments |
Business Domain |
| Payments |
Application Domain |
| Payments |
Technology Domain |
| Payments |
Strategy Domain |
| Payments |
Motivation Domain |
| Payments |
Implementation and Migration Domain |
| Payments |
Element by Aspect |
| Payments |
Structure |
| Payments |
Active Structure |
| Payments |
Internal Active Structure |
| Payments |
External Active Structure |
| Payments |
Behavior |
| Payments |
Internal Behavior |
| Payments |
External Behavior |
| Payments |
Event |
| Payments |
Passive Structure |
| Payments |
Composite |
| Payments |
Motivation |
| Payments |
Relationship by Category |
| Payments |
Structural Relationship |
| Payments |
Dependency Relationship |
| Payments |
Dynamic Relationship |
| Payments |
Other Relationship |
| Payments |
Structural Relationships by Strength |
| Payments |
Dependency Relationships by Strength |
| Payments |
Relationships in Order of Proposal |
| Payments |
Order of Proposal from a Grouping |
| Payments |
Order of Proposal from a Plateau |
| Payments |
Order of Proposal between Capabilities |
| Payments |
Order of Proposal from a Work Package to an Event |
| Payments |
Order of Proposal from a Facility to a Node |
| Payments |
Order of Proposal from a Node to an Artifact |
| Payments |
Order of Proposal from a Facility to a Device |
| Payments |
Order of Proposal between Events |
| Payments |
ArchiMate 4.0 Viewpoint Catalog |
| Payments |
Viewpoint by Category |
| Payments |
Viewpoint by Scope |
| Payments |
Basic Viewpoints |
| Payments |
Composition |
| Payments |
Support |
| Payments |
Cooperation |
| Payments |
Realization |
| Payments |
Motivation Viewpoints |
| Payments |
Strategy Viewpoints |
| Payments |
Implementation and Migration Viewpoints |
| Payments |
Single domain, single aspect |
| Payments |
Single domain, multiple aspects |
| Payments |
Multiple domains, single aspect |
| Payments |
Multiple domains, multiple aspects |
| Payments |
Application domain, multiple aspects |
| Payments |
Motivation domain |
| Payments |
Strategy domain |
| Payments |
Implementation and Migration domain |
| Payments |
Designing |
| Payments |
Deciding |
| Payments |
Informing |
| Payments |
Governing |
| Payments |
Enterprise Architect |
| Payments |
Process Architect |
| Payments |
Domain Architect |
| Payments |
Application Architect |
| Payments |
Solution Architect |
| Payments |
Information Architect |
| Payments |
Infrastructure Architect |
| Payments |
Business Architect |
| Payments |
ICT Architect |
| Payments |
Manager |
| Payments |
Operational Manager |
| Payments |
Business Manager |
| Payments |
Product Manager |
| Payments |
Requirements Manager |
| Payments |
Product Developer |
| Payments |
Business Analyst |
| Payments |
CxO |
| Payments |
Employee |
| Payments |
Shareholder |
| Payments |
Stakeholders |
| Payments |
Competencies, authority and responsibilities |
| Payments |
Application structure |
| Payments |
Consistency |
| Payments |
Completeness |
| Payments |
Reduction of complexity |
| Payments |
Structure and dependencies of data and information |
| Payments |
Stability, security, dependencies and costs of infrastructure |
| Payments |
Impact of change |
| Payments |
Flexibility |
| Payments |
The physical environment and how it relates to IT infrastructure |
| Payments |
Product development |
| Payments |
Value offered by products |
| Payments |
Dependencies |
| Payments |
Performance |
| Payments |
Scalability |
| Payments |
Dependencies between processes |
| Payments |
Responsibilities |
| Payments |
Relationships and dependencies between applications |
| Payments |
Orchestration and choreography of services |
| Payments |
Added value of processes |
| Payments |
Structure of application platforms and the technology supporting them |
| Payments |
Architecture mission |
| Payments |
Architecture strategy |
| Payments |
Architecture tactics |
| Payments |
Motivation |
| Payments |
Strategy development |
| Payments |
Business-oriented results |
| Payments |
Architecture vision |
| Payments |
Architecture policies |
| Payments |
History of models |
| Payments |
Organization Viewpoint |
| Payments |
Application Structure Viewpoint |
| Payments |
Information Structure Viewpoint |
| Payments |
Technology Viewpoint |
| Payments |
Layered Viewpoint |
| Payments |
Physical Viewpoint |
| Payments |
Product Viewpoint |
| Payments |
Application Usage Viewpoint |
| Payments |
Technology Usage Viewpoint |
| Payments |
Process Cooperation Viewpoint |
| Payments |
Application Cooperation Viewpoint |
| Payments |
Service Realization Viewpoint |
| Payments |
Implementation and Deployment Viewpoint |
| Payments |
Stakeholder Viewpoint |
| Payments |
Goal Realization Viewpoint |
| Payments |
Requirements Realization Viewpoint |
| Payments |
Motivation Viewpoint |
| Payments |
Strategy Viewpoint |
| Payments |
Capability Map Viewpoint |
| Payments |
Value Stream Viewpoint |
| Payments |
Outcome Realization Viewpoint |
| Payments |
Resource Map Viewpoint |
| Payments |
Project Viewpoint |
| Payments |
Migration Viewpoint |
| Payments |
Implementation and Migration Viewpoint |
| Payments |
ArchiMate 4.0 Metamodel |
| Payments |
ArchiMate 4.0 Standard Notation |
| Payments |
Banded Rectangle |
| Payments |
Tabbed Rectangle |
| Payments |
3D Box |
| Payments |
Wavy Rectangle |
| Payments |
Cloud |
| Payments |
Folder |
| Payments |
ArchiMate 4.0 Reference Data |
| Payments |
Environment Types |
| Payments |
Development |
| Payments |
Test |
| Payments |
Staging |
| Payments |
Production |
| Payments |
Disaster Recovery |
| Payments |
Criticality Levels |
| Payments |
Mission Critical |
| Payments |
Business Critical |
| Payments |
Business Operational |
| Payments |
Administrative |
| Payments |
permitted by |
| Payments |
permitted directly by |
| Payments |
drawn by |
| Payments |
permits access |
| Payments |
permits access directly |
| Payments |
draws access |
| Payments |
permits aggregation |
| Payments |
permits aggregation directly |
| Payments |
draws aggregation |
| Payments |
permits assignment |
| Payments |
permits assignment directly |
| Payments |
draws assignment |
| Payments |
permits association |
| Payments |
permits association directly |
| Payments |
draws association |
| Payments |
permits composition |
| Payments |
permits composition directly |
| Payments |
draws composition |
| Payments |
permits flow |
| Payments |
permits flow directly |
| Payments |
draws flow |
| Payments |
permits influence |
| Payments |
permits influence directly |
| Payments |
draws influence |
| Payments |
permits realization |
| Payments |
permits realization directly |
| Payments |
draws realization |
| Payments |
permits serving |
| Payments |
permits serving directly |
| Payments |
draws serving |
| Payments |
permits specialization |
| Payments |
permits specialization directly |
| Payments |
draws specialization |
| Payments |
permits triggering |
| Payments |
permits triggering directly |
| Payments |
draws triggering |
| Payments |
BehaviorElement |
| Payments |
InternalBehaviorElement |
| Payments |
ExternalBehaviorElement |
| Payments |
EventElement |
| Payments |
StructureElement |
| Payments |
ActiveStructureElement |
| Payments |
InternalActiveStructureElement |
| Payments |
ExternalActiveStructureElement |
| Payments |
PassiveStructureElement |
| Payments |
MotivationElement |
| Payments |
CompositeElement |
| Payments |
StrategyElement |
| Payments |
StrategyBehaviorElement |
| Payments |
CommonDomainElement |
| Payments |
BusinessDomainElement |
| Payments |
ApplicationDomainElement |
| Payments |
TechnologyDomainElement |
| Payments |
ImplementationAndMigrationDomainElement |
| Payments |
Role |
| Payments |
Collaboration |
| Payments |
Path |
| Payments |
Service |
| Payments |
Process |
| Payments |
Function |
| Payments |
Event |
| Payments |
Grouping |
| Payments |
Location |
| Payments |
Stakeholder |
| Payments |
Driver |
| Payments |
Assessment |
| Payments |
Goal |
| Payments |
Outcome |
| Payments |
Principle |
| Payments |
Requirement |
| Payments |
Meaning |
| Payments |
Value |
| Payments |
Resource |
| Payments |
Capability |
| Payments |
Value Stream |
| Payments |
Course of Action |
| Payments |
Business Actor |
| Payments |
Business Interface |
| Payments |
Business Object |
| Payments |
Product |
| Payments |
Application Component |
| Payments |
Application Interface |
| Payments |
Data Object |
| Payments |
Node |
| Payments |
Technology Interface |
| Payments |
Device |
| Payments |
System Software |
| Payments |
Equipment |
| Payments |
Facility |
| Payments |
Communication Network |
| Payments |
Distribution Network |
| Payments |
Artifact |
| Payments |
Material |
| Payments |
Work Package |
| Payments |
Deliverable |
| Payments |
Plateau |
| Payments |
And Junction |
| Payments |
Or Junction |
| Payments |
Composed Of |
| Payments |
Composition |
| Payments |
qualified Composition |
| Payments |
Aggregates |
| Payments |
Aggregation |
| Payments |
qualified Aggregation |
| Payments |
Assigned To |
| Payments |
Assignment |
| Payments |
qualified Assignment |
| Payments |
Realizes |
| Payments |
Realization |
| Payments |
qualified Realization |
| Payments |
Serves |
| Payments |
Serving |
| Payments |
qualified Serving |
| Payments |
Accesses |
| Payments |
Access |
| Payments |
Read Access |
| Payments |
Write Access |
| Payments |
Read-Write Access |
| Payments |
qualified Access |
| Payments |
Influences |
| Payments |
Influence |
| Payments |
qualified Influence |
| Payments |
Triggers |
| Payments |
Triggering |
| Payments |
qualified Triggering |
| Payments |
Flows To |
| Payments |
Flow |
| Payments |
qualified Flow |
| Payments |
Specializes |
| Payments |
Specialization |
| Payments |
qualified Specialization |
| Payments |
Associated With |
| Payments |
Association |
| Payments |
Directed Association |
| Payments |
qualified Association |
| Payments |
Access Type |
| Payments |
Influence Strength |
| Payments |
ArchiMate 4.0 Presentation Contexts |
| Payments |
Executive / C-Level |
| Payments |
Architect |
| Payments |
Developer / Engineering |
| Payments |
Operations / Infrastructure |
| Payments |
Governance / Compliance |
| Payments |
derivation certainty |
| Payments |
Derivation Certainty Level |
| Payments |
valid |
| Payments |
potential |
| Payments |
Qualify the model's relationships |
| Payments |
DR1: Transitivity of specialization |
| Payments |
DR2: Derivation between structural relationships |
| Payments |
DR3: Derivation between structural and dependency relationships |
| Payments |
DR4: Derivation between opposing structural and dependency relationships |
| Payments |
DR5: Derivation between structural and dynamic relationships |
| Payments |
DR6: Derivation between structural and flow relationships |
| Payments |
DR7: Derivation between structural and triggering relationships |
| Payments |
DR8: Derivation between triggering relationships |
| Payments |
PDR1: Specialization and another relationship, in line |
| Payments |
PDR2: Specialization and another relationship, in the opposite direction |
| Payments |
PDR3: Another relationship from the specialized element |
| Payments |
PDR4: Another relationship to the specialized element |
| Payments |
PDR5: Dependency to the source of a structural relationship |
| Payments |
PDR6: Dependency from the source of a structural relationship |
| Payments |
PDR7: Derivation between dependency relationships |
| Payments |
PDR8: Flow and a structural relationship, in line |
| Payments |
PDR9: Dynamic relationship from the source of a structural relationship |
| Payments |
PDR10: Derivation between flow relationships |
| Payments |
PDR11: Triggering and a structural relationship to its target |
| Payments |
PDR12: Elements aggregated or composed in a grouping |
| Payments |
Appendix B.4, on derivations |
| Payments |
ArchiMate Presentation Contexts |
| Payments |
Executive / C-Level |
| Payments |
Architect |
| Payments |
Developer / Engineering |
| Payments |
Operations / Infrastructure |
| Payments |
Governance / Compliance |
| Payments |
permitted by |
| Payments |
permitted directly by |
| Payments |
drawn by |
| Payments |
permits access |
| Payments |
permits access directly |
| Payments |
draws access |
| Payments |
permits aggregation |
| Payments |
permits aggregation directly |
| Payments |
draws aggregation |
| Payments |
permits assignment |
| Payments |
permits assignment directly |
| Payments |
draws assignment |
| Payments |
permits association |
| Payments |
permits association directly |
| Payments |
draws association |
| Payments |
permits composition |
| Payments |
permits composition directly |
| Payments |
draws composition |
| Payments |
permits flow |
| Payments |
permits flow directly |
| Payments |
draws flow |
| Payments |
permits influence |
| Payments |
permits influence directly |
| Payments |
draws influence |
| Payments |
permits realization |
| Payments |
permits realization directly |
| Payments |
draws realization |
| Payments |
permits serving |
| Payments |
permits serving directly |
| Payments |
draws serving |
| Payments |
permits specialization |
| Payments |
permits specialization directly |
| Payments |
draws specialization |
| Payments |
permits triggering |
| Payments |
permits triggering directly |
| Payments |
draws triggering |
| Payments |
Architecture Definition Document |
| Payments |
1. Business Organization |
| Payments |
2. Business Process Cooperation |
| Payments |
3. Application Cooperation |
| Payments |
4. Technology Infrastructure |
| Payments |
5. Cross-Layer Overview |
| Payments |
6. Implementation & Deployment |
| Payments |
7. Realisation Roadmap |
| Payments |
Appendix. Quality of this Description |
| Payments |
Architecture Requirements Specification |
| Payments |
1. Stakeholders and Drivers |
| Payments |
2. Goals and Outcomes |
| Payments |
3. Requirements and their Realisation |
| Payments |
Architecture Principles Document |
| Payments |
1. Principles |
| Payments |
2. Strategy Alignment |
| Payments |
Change Impact Assessment (ArchiMate 3.2) |
| Payments |
1. What Depends on the Element |
| Payments |
2. Views to Update |
| Payments |
3. Baseline to Target |
| Payments |
ArchiMate Reference Models |
| Payments |
Architecture Patterns |
| Payments |
Layered Architecture |
| Payments |
Microservices Architecture |
| Payments |
Event-Driven Architecture |
| Payments |
Service-Oriented Architecture |
| Payments |
Industry Reference Models |
| Payments |
BIAN (Banking Industry Architecture Network) |
| Payments |
TM Forum Frameworx |
| Payments |
ACORD Framework |
| Payments |
ArchiMate 3.2 Metamodel |
| Payments |
ArchiMate 3.2 Standard Notation |
| Payments |
Banded Rectangle |
| Payments |
Double Banded Rectangle |
| Payments |
Tabbed Rectangle |
| Payments |
3D Box |
| Payments |
Wavy Rectangle |
| Payments |
Wavy Banded Rectangle |
| Payments |
Cloud |
| Payments |
Folder |
| Payments |
How is the model spread over the ArchiMate layers? |
| Payments |
Which relationships cross layers, and of which kind? |
| Payments |
Who is responsible for what? |
| Payments |
Which applications depend on which? |
| Payments |
Who reads and writes which information? |
| Payments |
What is affected if this element changes? |
| Payments |
What realises each capability? |
| Payments |
What do stakeholders care about? |
| Payments |
How does each requirement trace to goals and to the elements that realise it? |
| Payments |
What motivates each principle, and what does it constrain? |
| Payments |
What does each work package deliver, and what does that realise? |
| Payments |
What changes between these two plateaus? |
| Payments |
Which processes and functions has nobody been assigned to? |
| Payments |
Which services does nothing realise? |
| Payments |
Which application components run on no technology? |
| Payments |
Which information is read but never written? |
| Payments |
Which capabilities does nothing realise? |
| Payments |
Which requirements does no architecture element realise? |
| Payments |
Which principles has no requirement made concrete? |
| Payments |
Where could the model be more concrete? |
| Payments |
Which relationships give rise to the most potential derivations? |
| Payments |
Redundant Application Serving |
| Payments |
Redundant Application Realizing Service |
| Payments |
Redundant Function Support |
| Payments |
Single Authoritative Data Writer |
| Payments |
Single Business Object Owner |
| Payments |
Application Component Ownership |
| Payments |
Business Process Ownership |
| Payments |
Data Object Stewardship |
| Payments |
Business Process Direct Technology Dependency |
| Payments |
Technology Serving Business Directly |
| Payments |
Application Component Without Service |
| Payments |
Direct Component-to-Component Serving |
| Payments |
Excessive Technology Diversity Per Service |
| Payments |
Single Point of Failure |
| Payments |
Single Deployment Node |
| Payments |
Business Service Without Realization |
| Payments |
Application Service Without Realization |
| Payments |
Capability Without Business Behavior Realization |
| Payments |
Business Behavior Realized by Multiple Application Components |
| Payments |
Business Function Realized by Multiple Application Components |
| Payments |
Orphaned Element |
| Payments |
Capability Without Goal |
| Payments |
Requirement Without Realization |
| Payments |
ArchiMate 3.2 Viewpoint Catalog |
| Payments |
Viewpoint by Category |
| Payments |
Viewpoint by Scope |
| Payments |
Basic Viewpoints |
| Payments |
Composition |
| Payments |
Support |
| Payments |
Cooperation |
| Payments |
Realization |
| Payments |
Motivation Viewpoints |
| Payments |
Strategy Viewpoints |
| Payments |
Implementation and Migration Viewpoints |
| Payments |
Single layer, single aspect |
| Payments |
Single layer, multiple aspects |
| Payments |
Multiple layers, single aspect |
| Payments |
Multiple layers, multiple aspects |
| Payments |
Application layer, multiple aspects |
| Payments |
Motivation |
| Payments |
Strategy |
| Payments |
Implementation and Migration |
| Payments |
Designing |
| Payments |
Deciding |
| Payments |
Informing |
| Payments |
Governing |
| Payments |
Enterprise Architect |
| Payments |
Process Architect |
| Payments |
Domain Architect |
| Payments |
Application Architect |
| Payments |
Solution Architect |
| Payments |
Information Architect |
| Payments |
Infrastructure Architect |
| Payments |
Business Architect |
| Payments |
ICT Architect |
| Payments |
Manager |
| Payments |
Operational Manager |
| Payments |
Business Manager |
| Payments |
Product Manager |
| Payments |
Requirements Manager |
| Payments |
Product Developer |
| Payments |
Business Analyst |
| Payments |
CxO |
| Payments |
Employee |
| Payments |
Shareholder |
| Payments |
Stakeholders |
| Payments |
Competencies, authority and responsibilities |
| Payments |
Application structure |
| Payments |
Consistency |
| Payments |
Completeness |
| Payments |
Reduction of complexity |
| Payments |
Structure and dependencies of the data and information used |
| Payments |
Stability, security, dependencies and costs of the infrastructure |
| Payments |
Impact of change |
| Payments |
Flexibility |
| Payments |
The physical environment and how it relates to the IT infrastructure |
| Payments |
Product development |
| Payments |
Value offered by products |
| Payments |
Dependencies |
| Payments |
Performance |
| Payments |
Scalability |
| Payments |
Dependencies between business processes |
| Payments |
Responsibilities |
| Payments |
Relationships and dependencies between applications |
| Payments |
Orchestration and choreography of services |
| Payments |
Added value of business processes |
| Payments |
Structure of application platforms and how they relate to supporting technology |
| Payments |
Architecture mission |
| Payments |
Architecture strategy |
| Payments |
Architecture tactics |
| Payments |
Motivation |
| Payments |
Strategy development |
| Payments |
Business-oriented results |
| Payments |
Architecture vision |
| Payments |
Architecture policies |
| Payments |
History of models |
| Payments |
Organization Viewpoint |
| Payments |
Application Structure Viewpoint |
| Payments |
Information Structure Viewpoint |
| Payments |
Technology Viewpoint |
| Payments |
Layered Viewpoint |
| Payments |
Physical Viewpoint |
| Payments |
Product Viewpoint |
| Payments |
Application Usage Viewpoint |
| Payments |
Technology Usage Viewpoint |
| Payments |
Business Process Cooperation Viewpoint |
| Payments |
Application Cooperation Viewpoint |
| Payments |
Service Realization Viewpoint |
| Payments |
Implementation and Deployment Viewpoint |
| Payments |
Stakeholder Viewpoint |
| Payments |
Goal Realization Viewpoint |
| Payments |
Requirements Realization Viewpoint |
| Payments |
Motivation Viewpoint |
| Payments |
Strategy Viewpoint |
| Payments |
Capability Map Viewpoint |
| Payments |
Value Stream Viewpoint |
| Payments |
Outcome Realization Viewpoint |
| Payments |
Resource Map Viewpoint |
| Payments |
Project Viewpoint |
| Payments |
Migration Viewpoint |
| Payments |
Implementation and Migration Viewpoint |
| Payments |
BehaviorElement |
| Payments |
InternalBehaviorElement |
| Payments |
ExternalBehaviorElement |
| Payments |
Event |
| Payments |
Interaction |
| Payments |
StructureElement |
| Payments |
ActiveStructureElement |
| Payments |
InternalActiveStructureElement |
| Payments |
ExternalActiveStructureElement |
| Payments |
Collaboration |
| Payments |
PassiveStructureElement |
| Payments |
MotivationElement |
| Payments |
CompositeElement |
| Payments |
CoreLayerElement |
| Payments |
BusinessLayerElement |
| Payments |
ApplicationLayerElement |
| Payments |
TechnologyLayerElement |
| Payments |
PhysicalLayerElement |
| Payments |
StrategyLayerElement |
| Payments |
ImplementationAndMigrationLayerElement |
| Payments |
Stakeholder |
| Payments |
Driver |
| Payments |
Assessment |
| Payments |
Goal |
| Payments |
Outcome |
| Payments |
Principle |
| Payments |
Requirement |
| Payments |
Constraint |
| Payments |
Meaning |
| Payments |
Value |
| Payments |
StrategyBehaviorElement |
| Payments |
Resource |
| Payments |
Capability |
| Payments |
Value Stream |
| Payments |
Course of Action |
| Payments |
Business Actor |
| Payments |
Business Role |
| Payments |
Business Collaboration |
| Payments |
Business Interface |
| Payments |
Business Process |
| Payments |
Business Function |
| Payments |
Business Interaction |
| Payments |
Business Event |
| Payments |
Business Service |
| Payments |
Business Object |
| Payments |
Contract |
| Payments |
Representation |
| Payments |
Product |
| Payments |
Application Component |
| Payments |
Application Collaboration |
| Payments |
Application Interface |
| Payments |
Application Function |
| Payments |
Application Interaction |
| Payments |
Application Process |
| Payments |
Application Event |
| Payments |
Application Service |
| Payments |
Data Object |
| Payments |
Node |
| Payments |
Device |
| Payments |
System Software |
| Payments |
Technology Collaboration |
| Payments |
Technology Interface |
| Payments |
Path |
| Payments |
Communication Network |
| Payments |
Technology Function |
| Payments |
Technology Process |
| Payments |
Technology Interaction |
| Payments |
Technology Event |
| Payments |
Technology Service |
| Payments |
Artifact |
| Payments |
Equipment |
| Payments |
Facility |
| Payments |
Distribution Network |
| Payments |
Material |
| Payments |
Work Package |
| Payments |
Deliverable |
| Payments |
Implementation Event |
| Payments |
Plateau |
| Payments |
Gap |
| Payments |
Grouping |
| Payments |
Location |
| Payments |
And Junction |
| Payments |
Or Junction |
| Payments |
Composed Of |
| Payments |
Composition |
| Payments |
qualified Composition |
| Payments |
Aggregates |
| Payments |
Aggregation |
| Payments |
qualified Aggregation |
| Payments |
Assigned To |
| Payments |
Assignment |
| Payments |
qualified Assignment |
| Payments |
Realizes |
| Payments |
Realization |
| Payments |
qualified Realization |
| Payments |
Serves |
| Payments |
Serving |
| Payments |
qualified Serving |
| Payments |
Accesses |
| Payments |
Access |
| Payments |
Read Access |
| Payments |
Write Access |
| Payments |
Read-Write Access |
| Payments |
qualified Access |
| Payments |
Influences |
| Payments |
Influence |
| Payments |
qualified Influence |
| Payments |
Triggers |
| Payments |
Triggering |
| Payments |
qualified Triggering |
| Payments |
Flows To |
| Payments |
Flow |
| Payments |
qualified Flow |
| Payments |
Specializes |
| Payments |
Specialization |
| Payments |
qualified Specialization |
| Payments |
Associated With |
| Payments |
Association |
| Payments |
Directed Association |
| Payments |
qualified Association |
| Payments |
Access Type |
| Payments |
Influence Strength |
| Payments |
ArchiMate 3.2 Concept Scheme |
| Payments |
ArchiMate Concept |
| Payments |
ArchiMate Element |
| Payments |
ArchiMate Relationship |
| Payments |
ArchiMate Connector |
| Payments |
Element by Layer |
| Payments |
Strategy Layer |
| Payments |
Business Layer |
| Payments |
Application Layer |
| Payments |
Technology Layer |
| Payments |
Physical Layer |
| Payments |
Implementation and Migration Layer |
| Payments |
Element by Aspect |
| Payments |
Active Structure |
| Payments |
Internal Active Structure |
| Payments |
External Active Structure |
| Payments |
Passive Structure |
| Payments |
Behavior |
| Payments |
Internal Behavior |
| Payments |
External Behavior |
| Payments |
Event |
| Payments |
Motivation |
| Payments |
Composite |
| Payments |
Strategy |
| Payments |
Relationship by Category |
| Payments |
Structural Relationship |
| Payments |
Dependency Relationship |
| Payments |
Dynamic Relationship |
| Payments |
Other Relationship |
| Payments |
Structural Relationships by Strength |
| Payments |
Dependency Relationships by Strength |
| Payments |
Relationships in Order of Proposal |
| Payments |
Order of Proposal from a Grouping |
| Payments |
Order of Proposal from a Plateau |
| Payments |
Order of Proposal between Capabilities |
| Payments |
Order of Proposal from a Work Package to an Implementation Event |
| Payments |
Order of Proposal from a Facility to a Node |
| Payments |
Order of Proposal from a Node to an Artifact |
| Payments |
Order of Proposal from a Device to System Software |
| Payments |
ArchiMate Reference Data |
| Payments |
Environment Types |
| Payments |
Development |
| Payments |
Test |
| Payments |
Staging |
| Payments |
Production |
| Payments |
Disaster Recovery |
| Payments |
Criticality Levels |
| Payments |
Mission Critical |
| Payments |
Business Critical |
| Payments |
Business Operational |
| Payments |
Administrative |
| Payments |
ArchiMate |
| Payments |
Stakeholder |
| Payments |
Driver |
| Payments |
Assessment |
| Payments |
Goal |
| Payments |
Outcome |
| Payments |
Principle |
| Payments |
Requirement |
| Payments |
Constraint |
| Payments |
Meaning |
| Payments |
Value |
| Payments |
Resource |
| Payments |
Capability |
| Payments |
ValueStream |
| Payments |
CourseOfAction |
| Payments |
BusinessActor |
| Payments |
BusinessRole |
| Payments |
BusinessCollaboration |
| Payments |
BusinessInterface |
| Payments |
BusinessProcess |
| Payments |
BusinessFunction |
| Payments |
BusinessInteraction |
| Payments |
BusinessEvent |
| Payments |
BusinessService |
| Payments |
BusinessObject |
| Payments |
Contract |
| Payments |
Representation |
| Payments |
Product |
| Payments |
ApplicationComponent |
| Payments |
ApplicationCollaboration |
| Payments |
ApplicationInterface |
| Payments |
ApplicationFunction |
| Payments |
ApplicationInteraction |
| Payments |
ApplicationProcess |
| Payments |
ApplicationEvent |
| Payments |
ApplicationService |
| Payments |
DataObject |
| Payments |
Node |
| Payments |
Device |
| Payments |
SystemSoftware |
| Payments |
TechnologyCollaboration |
| Payments |
TechnologyInterface |
| Payments |
Path |
| Payments |
CommunicationNetwork |
| Payments |
TechnologyFunction |
| Payments |
TechnologyProcess |
| Payments |
TechnologyInteraction |
| Payments |
TechnologyEvent |
| Payments |
TechnologyService |
| Payments |
Artifact |
| Payments |
Equipment |
| Payments |
Facility |
| Payments |
DistributionNetwork |
| Payments |
Material |
| Payments |
WorkPackage |
| Payments |
Deliverable |
| Payments |
ImplementationEvent |
| Payments |
Plateau |
| Payments |
Gap |
| Payments |
Grouping |
| Payments |
Location |
| Payments |
access |
| Payments |
accessType |
| Payments |
modifier |
| Payments |
isDirected |
| Payments |
composition |
| Payments |
aggregation |
| Payments |
assignment |
| Payments |
realization |
| Payments |
serving |
| Payments |
influence |
| Payments |
triggering |
| Payments |
flow |
| Payments |
specialization |
| Payments |
association |
| Payments |
ArchiMate 3.1 Concept Scheme |
| Payments |
Archimate Concept |
| Payments |
ArchimateElement |
| Payments |
ArchimateRelationship |
| Payments |
Structural Relationship |
| Payments |
Dependency Relationship |
| Payments |
Dynamic Relationship |
| Payments |
Other Relationship |
| Payments |
Relationship Connector |
| Payments |
ArchiMate Element by Layer |
| Payments |
Strategy Layer |
| Payments |
Business Layer |
| Payments |
Application Layer |
| Payments |
Technology Layer |
| Payments |
Physical Layer |
| Payments |
Implementation and Migration Layer |
| Payments |
ArchiMate Element by Aspect |
| Payments |
Motivation Element |
| Payments |
Structure Element |
| Payments |
Active Structure Element |
| Payments |
External Active Structure Element |
| Payments |
Internal Active Structure Element |
| Payments |
Passive Structure Element |
| Payments |
Behavior Element |
| Payments |
External Behavior Element |
| Payments |
Internal Behavior Element |
| Payments |
Event |
| Payments |
Composite Element |
| Payments |
BPMN Lite Standard Notation |
| Payments |
Process Shape |
| Payments |
SubProcess Shape |
| Payments |
Task Shape |
| Payments |
Call Activity Shape |
| Payments |
Event Shape |
| Payments |
Start Event Shape |
| Payments |
End Event Shape |
| Payments |
Boundary Event Shape |
| Payments |
Gateway Shape |
| Payments |
Participant Shape |
| Payments |
Lane Shape |
| Payments |
Data Object Shape |
| Payments |
Data Store Shape |
| Payments |
Message Shape |
| Payments |
Sequence Flow Shape |
| Payments |
Message Flow Shape |
| Payments |
Data Association Shape |
| Payments |
Process |
| Payments |
SubProcess |
| Payments |
Task |
| Payments |
User Task |
| Payments |
Service Task |
| Payments |
Send Task |
| Payments |
Receive Task |
| Payments |
Script Task |
| Payments |
Business Rule Task |
| Payments |
Manual Task |
| Payments |
Call Activity |
| Payments |
Event |
| Payments |
Start Event |
| Payments |
End Event |
| Payments |
Intermediate Event |
| Payments |
Boundary Event |
| Payments |
Gateway |
| Payments |
Exclusive Gateway |
| Payments |
Parallel Gateway |
| Payments |
Inclusive Gateway |
| Payments |
Event-Based Gateway |
| Payments |
Participant |
| Payments |
Lane |
| Payments |
Data Object |
| Payments |
Data Store |
| Payments |
Message |
| Payments |
Sequence Flow |
| Payments |
Sequence Flow |
| Payments |
Message Flow |
| Payments |
Message Flow |
| Payments |
Data Association |
| Payments |
Data Association |
| Payments |
Event Type |
| Payments |
Is Interrupting |
| Payments |
Condition |
| Payments |
Source Ref |
| Payments |
BPMN Lite Concept Scheme |
| Payments |
Flow Objects |
| Payments |
Connecting Objects |
| Payments |
Swim Lanes |
| Payments |
Data |
| Payments |
Activities |
| Payments |
Events |
| Payments |
Gateways |
| Payments |
Sequence Flow |
| Payments |
Message Flow |
| Payments |
Data Association |
| Payments |
Participant |
| Payments |
Lane |
| Payments |
Data Object |
| Payments |
Data Store |
| Payments |
Message |
| Payments |
BPMN Lite Metamodel |
| Payments |
Business Model Canvas |
| Payments |
Business Model Canvas Metamodel |
| Payments |
Business Model Canvas |
| Payments |
BMC Element |
| Payments |
Customer Segments |
| Payments |
Value Propositions |
| Payments |
Channels |
| Payments |
Customer Relationships |
| Payments |
Revenue Streams |
| Payments |
Key Resources |
| Payments |
Key Activities |
| Payments |
Key Partners |
| Payments |
Cost Structure |
| Payments |
System Overview Document |
| Payments |
1. System Context |
| Payments |
2. Container Architecture |
| Payments |
3. Deployment Topology |
| Payments |
Component Design Document |
| Payments |
1. Container Context |
| Payments |
2. Component Structure |
| Payments |
3. Dynamic Behavior |
| Payments |
C4 Model Viewpoint Catalog |
| Payments |
Core Levels |
| Payments |
Supplementary Diagrams |
| Payments |
System Context Diagram (Level 1) |
| Payments |
Container Diagram (Level 2) |
| Payments |
Component Diagram (Level 3) |
| Payments |
Code Diagram (Level 4) |
| Payments |
Deployment Diagram |
| Payments |
System Landscape Diagram |
| Payments |
Dynamic Diagram |
| Payments |
C4 Model |
| Payments |
Structurizr |
| Payments |
C4 Model Metamodel |
| Payments |
C4 Reference Data |
| Payments |
Container Technologies |
| Payments |
Web Application |
| Payments |
Mobile Application |
| Payments |
Desktop Application |
| Payments |
API Service |
| Payments |
Microservice |
| Payments |
Database |
| Payments |
Message Broker |
| Payments |
File System |
| Payments |
Serverless Function |
| Payments |
Deployment Environments |
| Payments |
Development |
| Payments |
Test |
| Payments |
Staging |
| Payments |
Production |
| Payments |
Person |
| Payments |
Software System |
| Payments |
Container |
| Payments |
Component |
| Payments |
Database |
| Payments |
Mobile App |
| Payments |
Client-side Web Application |
| Payments |
External Person |
| Payments |
External Software System |
| Payments |
Uses |
| Payments |
Using |
| Payments |
Has Container |
| Payments |
Container Containment |
| Payments |
Has Component |
| Payments |
Component Containment |
| Payments |
Technology |
| Payments |
Deployment Node |
| Payments |
Infrastructure Node |
| Payments |
Deployed On |
| Payments |
Deployment |
| Payments |
Instances |
| Payments |
Environment |
| Payments |
C4 Presentation Contexts |
| Payments |
Product Owner / Business |
| Payments |
Development Team |
| Payments |
Platform / DevOps Team |
| Payments |
C4 Model Concept Scheme |
| Payments |
C4 Element |
| Payments |
Context Level (L1) |
| Payments |
Person |
| Payments |
Software System |
| Payments |
External Person |
| Payments |
External Software System |
| Payments |
Container Level (L2) |
| Payments |
Container |
| Payments |
Database |
| Payments |
Mobile App |
| Payments |
Client-side Web Application |
| Payments |
Component Level (L3) |
| Payments |
Component |
| Payments |
Infrastructure |
| Payments |
Deployment Node |
| Payments |
Infrastructure Node |
| Payments |
C4 Relationship |
| Payments |
Uses |
| Payments |
Containment |
| Payments |
Deployment |
| Payments |
C4 Standard Notation |
| Payments |
Person |
| Payments |
Mobile Device |
| Payments |
Web Browser |
| Payments |
Cylinder |
| Payments |
Database |
| Payments |
Mobile App |
| Payments |
Client-side Web Application |
| Payments |
External Person |
| Payments |
External Software System |
| Payments |
LeanIX Meta Model v3 Metamodel |
| Payments |
Application Portfolio Report |
| Payments |
1. Application Portfolio |
| Payments |
2. Technology Landscape |
| Payments |
3. Interface Map |
| Payments |
Transformation Plan Document |
| Payments |
1. Capability Map |
| Payments |
2. Transformation Roadmap |
| Payments |
Fact Sheet |
| Payments |
Application |
| Payments |
Business Capability |
| Payments |
User Group |
| Payments |
Project |
| Payments |
Process |
| Payments |
Product |
| Payments |
IT Component |
| Payments |
Tech Category |
| Payments |
Tech Platform |
| Payments |
Interface |
| Payments |
Data Object |
| Payments |
Provider |
| Payments |
LeanIX Meta Model v4 Concept Scheme |
| Payments |
Fact Sheet Type |
| Payments |
Relationship Type |
| Payments |
Strategy & Transformation |
| Payments |
Objective |
| Payments |
Initiative |
| Payments |
Business |
| Payments |
Business Capability |
| Payments |
Organization |
| Payments |
Business Context |
| Payments |
Product |
| Payments |
Value Stream |
| Payments |
Process |
| Payments |
Application & Data |
| Payments |
Application |
| Payments |
Business Application |
| Payments |
Deployment |
| Payments |
Microservice |
| Payments |
Interface |
| Payments |
Data Object |
| Payments |
Technical |
| Payments |
IT Component |
| Payments |
Tech Category |
| Payments |
Platform |
| Payments |
Provider |
| Payments |
Optional |
| Payments |
System |
| Payments |
Supporting |
| Payments |
Requiring |
| Payments |
Interface Ownership |
| Payments |
Interface Consumption |
| Payments |
Data Usage |
| Payments |
Impact |
| Payments |
Driving |
| Payments |
Organizational Usage |
| Payments |
Provision |
| Payments |
Categorization |
| Payments |
Fact Sheet Hierarchy |
| Payments |
Platform Membership |
| Payments |
Context Support |
| Payments |
Context Realization |
| Payments |
Capability Targeting |
| Payments |
System Composition |
| Payments |
LeanIX Standard Notation |
| Payments |
SAP LeanIX Enterprise Architecture |
| Payments |
LeanIX Meta Model v4 Metamodel |
| Payments |
Fact Sheet |
| Payments |
Objective |
| Payments |
Initiative |
| Payments |
Business Capability |
| Payments |
Organization |
| Payments |
Organization Unit |
| Payments |
Business Context |
| Payments |
Product |
| Payments |
Value Stream |
| Payments |
Process |
| Payments |
Application |
| Payments |
Business Application |
| Payments |
Deployment |
| Payments |
Microservice |
| Payments |
Interface |
| Payments |
Data Object |
| Payments |
IT Component |
| Payments |
Tech Category |
| Payments |
Platform |
| Payments |
Provider |
| Payments |
System (optional) |
| Payments |
Supports |
| Payments |
Supporting |
| Payments |
Requires |
| Payments |
Requiring |
| Payments |
Has Interface |
| Payments |
Interface Ownership |
| Payments |
Consumes Interface |
| Payments |
Interface Consumption |
| Payments |
Uses Data |
| Payments |
Data Usage |
| Payments |
Impacts |
| Payments |
Impact |
| Payments |
Drives |
| Payments |
Driving |
| Payments |
Used by Organization |
| Payments |
Organizational Usage |
| Payments |
Provided By |
| Payments |
Provision |
| Payments |
Categorized By |
| Payments |
Categorization |
| Payments |
Parent Of |
| Payments |
Fact Sheet Hierarchy |
| Payments |
Part Of Platform |
| Payments |
Platform Membership |
| Payments |
Supports Context |
| Payments |
Context Support |
| Payments |
Context Realizes |
| Payments |
Context Realization |
| Payments |
Targets Capability |
| Payments |
Capability Targeting |
| Payments |
Composed Of |
| Payments |
System Composition |
| Payments |
Completion |
| Payments |
Fact Sheet Status |
| Payments |
Fact Sheet Status |
| Payments |
Active |
| Payments |
Archived |
| Payments |
Broken |
| Payments |
Lifecycle Phase |
| Payments |
Has Lifecycle Phase |
| Payments |
Phase Start |
| Payments |
Subscription |
| Payments |
Has Subscription |
| Payments |
Subscriber |
| Payments |
Subscriber Email |
| Payments |
Subscription Type |
| Payments |
Subscription Type |
| Payments |
Responsible |
| Payments |
Accountable |
| Payments |
Observer |
| Payments |
Subscription Role |
| Payments |
Tag |
| Payments |
Has Tag |
| Payments |
Tag Name |
| Payments |
Tag Group |
| Payments |
LeanIX Viewpoint Catalog |
| Payments |
Application Portfolio |
| Payments |
Technology Landscape |
| Payments |
Interface Map |
| Payments |
Capability Map |
| Payments |
Transformation Roadmap |
| Payments |
Component |
| Payments |
System |
| Payments |
API |
| Payments |
Resource |
| Payments |
Domain |
| Payments |
User |
| Payments |
Group |
| Payments |
Template |
| Payments |
Owned By |
| Payments |
Ownership |
| Payments |
Part of System |
| Payments |
System Membership |
| Payments |
Provides API |
| Payments |
API Provision |
| Payments |
Consumes API |
| Payments |
API Consumption |
| Payments |
Depends On |
| Payments |
Dependency |
| Payments |
Uses Resource |
| Payments |
Resource Usage |
| Payments |
Belongs to Domain |
| Payments |
Domain Membership |
| Payments |
Member Of |
| Payments |
Group Membership |
| Payments |
Child Of |
| Payments |
Group Parentage |
| Payments |
Subcomponent Of |
| Payments |
Component Composition |
| Payments |
Subdomain Of |
| Payments |
Domain Hierarchy |
| Payments |
TechDocs Delegated To |
| Payments |
TechDocs Delegation |
| Payments |
TechDocs Entity Path |
| Payments |
Scaffolded From |
| Payments |
Scaffolding |
| Payments |
Lifecycle (deprecated) |
| Payments |
Lifecycle State |
| Payments |
Lifecycle State |
| Payments |
Experimental |
| Payments |
Production |
| Payments |
Deprecated |
| Payments |
Component Type |
| Payments |
Component Type |
| Payments |
service |
| Payments |
website |
| Payments |
library |
| Payments |
API Type |
| Payments |
API Type |
| Payments |
openapi |
| Payments |
asyncapi |
| Payments |
graphql |
| Payments |
grpc |
| Payments |
API Visibility |
| Payments |
API Visibility |
| Payments |
Public |
| Payments |
Restricted |
| Payments |
Private |
| Payments |
Managed By Location |
| Payments |
Managed By Origin Location |
| Payments |
Orphan |
| Payments |
View URL |
| Payments |
Edit URL |
| Payments |
Source Location |
| Payments |
TechDocs Ref |
| Payments |
Source Template |
| Payments |
Time Saved |
| Payments |
External Identifier |
| Payments |
GitHub Project Slug |
| Payments |
GitHub Team Slug |
| Payments |
GitHub User Login |
| Payments |
GitHub User ID |
| Payments |
GitLab User ID |
| Payments |
LDAP RDN |
| Payments |
LDAP UUID |
| Payments |
LDAP DN |
| Payments |
Microsoft Graph Tenant ID |
| Payments |
Microsoft Graph Group ID |
| Payments |
Microsoft Graph User ID |
| Payments |
Jenkins Job Full Name |
| Payments |
GoCD Pipeline |
| Payments |
CircleCI Project Slug |
| Payments |
Sentry Project Slug |
| Payments |
Rollbar Project Slug |
| Payments |
SonarQube Project Key |
| Payments |
Periskop Service Name |
| Payments |
Vault Secrets Path |
| Payments |
Name |
| Payments |
Namespace |
| Payments |
API Version |
| Payments |
Kind |
| Payments |
Entity Reference |
| Payments |
UID |
| Payments |
ETag |
| Payments |
Title |
| Payments |
Description |
| Payments |
Tag |
| Payments |
Label |
| Payments |
Link |
| Payments |
Has Link |
| Payments |
Link URL |
| Payments |
Link Title |
| Payments |
Link Icon |
| Payments |
Link Type |
| Payments |
Status Item |
| Payments |
Has Status Item |
| Payments |
Status Type |
| Payments |
Status Level |
| Payments |
Status Level |
| Payments |
info |
| Payments |
warning |
| Payments |
error |
| Payments |
Status Message |
| Payments |
Display Name |
| Payments |
Email |
| Payments |
Picture |
| Payments |
Definition |
| Payments |
Resource Type |
| Payments |
Resource Type |
| Payments |
database |
| Payments |
s3-bucket |
| Payments |
kubernetes-cluster |
| Payments |
Group Type |
| Payments |
Group Type |
| Payments |
team |
| Payments |
business-unit |
| Payments |
product-area |
| Payments |
root |
| Payments |
System Type |
| Payments |
System Type |
| Payments |
product |
| Payments |
service |
| Payments |
feature-set |
| Payments |
Domain Type |
| Payments |
Domain Type |
| Payments |
product-area |
| Payments |
product-group |
| Payments |
bundle |
| Payments |
Service Catalog Document |
| Payments |
1. Service Catalog |
| Payments |
2. Ownership Matrix |
| Payments |
3. API Dependencies |
| Payments |
4. Lifecycle Portfolio |
| Payments |
System Architecture Document |
| Payments |
1. Domain Overview |
| Payments |
2. System Dependencies |
| Payments |
3. API Landscape |
| Payments |
4. Component Composition |
| Payments |
Organization Structure Document |
| Payments |
1. Group Hierarchy |
| Payments |
2. Group Membership |
| Payments |
3. Accountability |
| Payments |
Backstage Presentation Contexts |
| Payments |
Developer |
| Payments |
Platform Engineer |
| Payments |
Engineering Manager |
| Payments |
Backstage Reference Data |
| Payments |
Backstage Concept Scheme |
| Payments |
Backstage Element |
| Payments |
Software Entity |
| Payments |
Component |
| Payments |
System |
| Payments |
API |
| Payments |
Resource |
| Payments |
Template |
| Payments |
Organizational Entity |
| Payments |
Domain |
| Payments |
User |
| Payments |
Group |
| Payments |
Backstage Relationship |
| Payments |
Ownership |
| Payments |
System Membership |
| Payments |
API Provision |
| Payments |
API Consumption |
| Payments |
Dependency |
| Payments |
Resource Usage |
| Payments |
Domain Membership |
| Payments |
Group Membership |
| Payments |
Group Parentage |
| Payments |
Component Composition |
| Payments |
Domain Hierarchy |
| Payments |
TechDocs Delegation |
| Payments |
Scaffolding |
| Payments |
Backstage Standard Notation |
| Payments |
Backstage Software Catalog |
| Payments |
Backstage Catalog Metamodel |
| Payments |
Backstage Viewpoint Catalog |
| Payments |
Catalog Viewpoints |
| Payments |
Governance Viewpoints |
| Payments |
Service Catalog |
| Payments |
System Dependency Diagram |
| Payments |
API Dependency Diagram |
| Payments |
Ownership Matrix |
| Payments |
Domain Overview Diagram |
| Payments |
Organization Structure Diagram |
| Payments |
Lifecycle Portfolio |
