Linked.Archi

Linked.Archi Backstage Viewpoints

Viewpoint Definitions

https://meta.linked.archi/backstage/viewpoints#

v0.1.0 draft bsvp: Kalin Maldzhanski Linked.Archi Modified: 2026-04-16 License

Backstage Software Catalog viewpoints for visualizing service ownership, system dependencies, API landscapes, domain organization, organizational structure, and lifecycle portfolio. Each viewpoint maps to a common Backstage use case.

Contents

IntegrationConcern

API Dependency Diagram

Shows which components and systems provide and consume which APIs. Enables API lifecycle management and consumer impact analysis. Answers: "Who provides and who consumes this API?"
Purpose: Designing
Concerns: IntegrationConcern, DependencyConcern
View type: Diagram
Included concepts:
Component System API

StructureConcern

Domain Overview Diagram

Shows domains, any nesting between them, and their constituent systems and components. Provides a high-level view of how the software landscape is organized by business domain. Answers: "How is the catalog organized by domain?"
Purpose: Informing
Concerns: StructureConcern, GovernanceConcern
View type: Diagram
Included concepts:
Domain System Component

Service Catalog

A catalog-style inventory of all registered components, systems, and APIs in the Backstage Software Catalog. Provides a searchable overview of the software landscape. Answers: "What services exist and what APIs do they expose?"
Purpose: Informing
Concerns: StructureConcern, IntegrationConcern
View type: Catalog
Included concepts:
Component System API Resource

GovernanceConcern

Lifecycle Portfolio

A catalog of components and APIs grouped by lifecycle state and type. Supports deprecation tracking and portfolio review. Answers: "What is still experimental, what is in production, and what is deprecated but still catalogued?"
Purpose: Governing
Concerns: GovernanceConcern
View type: Catalog
Included concepts:
Component API

Organization Structure Diagram

Shows the group hierarchy and the users who belong to each group. Provides the organizational half of the catalog, which ownership views reference but do not themselves show. Answers: "How is the organization structured, and who is in which team?"
Purpose: Informing
Concerns: GovernanceConcern, StructureConcern
View type: Diagram
Included concepts:
Group User

Ownership Matrix

A matrix showing which groups or users own which catalog entities. Supports governance reviews and accountability tracking. Answers: "Who owns what?"
Purpose: Governing
Concerns: GovernanceConcern, StructureConcern
View type: Matrix
Included concepts:
Component System API Resource Domain Group User

DependencyConcern

System Dependency Diagram

Shows systems, their constituent components, consumed APIs, and the entities they depend on. Supports impact analysis and change planning. Answers: "What does this system depend on?"
Purpose: Deciding
Concerns: DependencyConcern, StructureConcern
View type: Diagram
Included concepts:
System Component API Resource
Source: linked-archi-meta • Linked.Archi