Skip to content

Forma3D.Connect — Enterprise Architecture

ArchiMate 3.2 Enterprise Architecture Documentation
Version: 1.0
Date: January 12, 2026

Overview

This folder contains the Enterprise Architecture documentation for Forma3D.Connect, modeled using the ArchiMate 3.2 specification and rendered with PlantUML Archimate-PlantUML.

Forma3D.Connect is an integration platform that bridges Shopify e-commerce with SimplyPrint 3D print farm management, enabling automated print-on-demand operations.

Architecture Layers

ArchiMate organizes architecture into multiple layers, each addressing different concerns:

Layer Description Diagram
Motivation Why the architecture exists - goals, stakeholders, drivers, requirements View
Strategy How to achieve the motivation - capabilities, resources, value streams View
Business What the business does - actors, processes, services, events View
Application How IT supports business - components, services, interfaces View
Technology Infrastructure supporting applications - nodes, devices, networks View
Implementation How to realize the architecture - work packages, deliverables View

Diagram Index

Overview Diagrams

Diagram Description
View High-level enterprise architecture showing all layers

Layer-Specific Diagrams

Diagram Layer Key Elements
View Motivation Stakeholders, Drivers, Goals, Principles, Requirements
View Strategy Capabilities, Resources, Value Streams, Course of Action
View Business Actors, Roles, Processes, Services, Events, Products
View Application Components, Services, Interfaces, Data Objects
View Technology Nodes, Devices, System Software, Networks, Artifacts
View Implementation Work Packages, Deliverables, Gaps, Plateaus

Cross-Cutting Views

Diagram Description
View Service Realization viewpoint showing how layers connect
View Information Structure viewpoint - data objects and relationships
View Full layered architecture view showing all layers together

Overview Diagram

uml diagram

Motivation

uml diagram

Strategy

uml diagram

Business

uml diagram

Application

uml diagram

Technology

uml diagram

Implementation

uml diagram

Viewpoints

uml diagram

Information Structure

uml diagram

Layered

uml diagram

How to View Diagrams

Option 1: VS Code with PlantUML Extension

  1. Install the PlantUML extension for VS Code
  2. Open any .puml file
  3. Press Alt+D (Windows/Linux) or Option+D (Mac) to preview

Option 2: JetBrains IDEs

JetBrains IDEs (IntelliJ, WebStorm, etc.) have built-in PlantUML support via the PlantUML Integration plugin.

Option 3: Online Viewer

  1. Copy the contents of any .puml file
  2. Paste into PlantUML Online Server
  3. Click "Submit" to render

Option 4: Command Line

# Install PlantUML
brew install plantuml  # macOS
# or
apt-get install plantuml  # Ubuntu/Debian

# Generate PNG
plantuml docs/enterprise/*.puml

# Generate SVG
plantuml -tsvg docs/enterprise/*.puml

ArchiMate Element Reference

Motivation Layer Elements

Element Icon Description
Stakeholder 👤 Individual, team, or organization with interests
Driver ⬆️ External or internal condition motivating change
Assessment 📊 Analysis of a driver's impact
Goal 🎯 High-level end state to be achieved
Outcome ✅ Result achieved by realizing goals
Principle 📜 Normative property of all solutions
Requirement 📋 Statement of need
Constraint ⛔ Restriction on implementation

Strategy Layer Elements

Element Icon Description
Resource 🔧 Asset owned or controlled
Capability 💪 Ability to achieve a particular outcome
Value Stream 📈 Sequence of activities delivering value
Course of Action 🎬 Approach to achieve goals

Business Layer Elements

Element Icon Description
Business Actor 🏢 Organizational entity performing behavior
Business Role 👔 Responsibility for specific behavior
Business Process ⚙️ Sequence of business behaviors
Business Service 🛎️ Externally visible functionality
Business Event ⚡ State change that triggers behavior
Business Object 📦 Passive element with business meaning
Product 📱 Coherent collection of services

Application Layer Elements

Element Icon Description
Application Component 🧩 Modular, deployable, replaceable part
Application Service 🌐 Externally visible application behavior
Application Interface 🔌 Access point to application services
Data Object 💾 Data structured for processing

Technology Layer Elements

Element Icon Description
Node 🖥️ Computational resource hosting artifacts
Device 📟 Hardware resource
System Software 💿 Software platform or middleware
Technology Service ☁️ Externally visible technology behavior
Artifact 📄 Physical piece of data
Communication Network 🌐 Medium for communication

Relationship Types

Relationship Symbol Description
Composition ◆─── Element consists of other elements
Aggregation ◇─── Element groups other elements
Assignment ●─── Allocation of responsibility
Realization ┄┄▸ More concrete element realizes abstract
Serving ───▸ Element provides functionality to another
Access ┄┄─ Behavioral element accesses data
Influence ····▸ Element affects another (motivation)
Triggering ──●▸ Temporal/causal relationship
Flow ───▸ Transfer of information/material
Association ─── Unspecified relationship

Document Conventions

Naming Conventions

  • Element IDs: Layer_ElementType_Name (e.g., App_Component_API)
  • Files: EA_##_LayerName.puml (e.g., EA_03_Business.puml)

Color Scheme (ArchiMate Standard)

Layer Color
Motivation Purple (#CCCCFF)
Strategy Tan (#F5DEB3)
Business Yellow (#FFFFB5)
Application Blue (#B5FFFF)
Technology Green (#C9E7B7)
Implementation Pink (#FFB5B5)
Document Description
Vision Document Project vision and objectives
Requirements Functional and non-functional requirements
Architecture Decision Records Technical architecture decisions
C4 Diagrams Software architecture views (C4 model)

Version History

Version Date Author Changes
1.0 2026-01-12 AI Assistant Initial ArchiMate EA documentation