Logo
NeoArc Studio

Architectural Views

Create different perspectives of your architecture for different stakeholders. Tailor your documentation to executives, developers, operations, and security teams.

The Architectural Views directory is where you create stakeholder-specific perspectives of your architecture. Different audiences need different levels of detail and focus areas.

What Belongs Here

This directory organises architecture documentation by viewpoint rather than by technical domain:

Recommended Content Blocks

Different viewpoints benefit from different content blocks:

ViewpointUseful Blocks
ExecutiveDiagram (overviews), Trade-off Matrix (decisions), Risk Register (strategic risks)
DeveloperCode, Component Responsibility, Schema Definition, REST API Endpoint, Diagram (C4)
OperationsOperational Note, Failure Scenario, Diagram (deployment)
SecurityRisk blocks, Principle (security principles), NFR (security requirements), Constraint (compliance)
SolutionAll blocks: combines elements from each viewpoint for a complete solution picture

Framework Alignment

Architectural views align with established frameworks:

TOGAF Viewpoints
Business, Data, Application, and Technology architecture views as defined in TOGAF ADM
C4 Model Levels
Context, Container, Component, and Code diagrams for different zoom levels
4+1 Views
Logical, Development, Process, Physical views plus scenarios
ISO 42010
Stakeholder-driven architecture views following international standards

Example Directory Structure

architectural-views/
├── executive/
│   ├── business-capability-overview.cf.page.json
│   ├── technology-investment-roadmap.cf.page.json
│   └── risk-summary.cf.page.json
├── developer/
│   ├── service-architecture-guide.cf.page.json
│   ├── coding-standards.cf.page.json
│   └── local-development-setup.cf.page.json
├── operations/
│   ├── deployment-guide.cf.page.json
│   ├── monitoring-and-alerting.cf.page.json
│   └── incident-response-playbook.cf.page.json
├── security/
│   ├── threat-model.cf.page.json
│   ├── security-controls.cf.page.json
│   └── compliance-mapping.cf.page.json
└── solutions/
    ├── checkout-flow/
    └── user-authentication/

Learn more