system-architect

System identification uses a 6-dimension framework to analyze user touchpoints, data storage, core business logic, external integrations, deployment units, and technology stack. This structured decomposition discovers potential independent systems within a project to ensure maintainable architecture.

The best way to visualize microservices system context and dependencies is by generating C4 Level 1 diagrams and System Dependency Graphs using Mermaid. This clearly outlines responsibilities, inputs, outputs, and dependencies for each identified system in a visual format.

Yes, you can use this approach to define systems for a modular monolith architecture. The framework identifies independent systems within a project and outlines their boundaries, which is highly effective for planning or refactoring modular monoliths to ensure clear separation of concerns.

You need to generate a comprehensive architecture overview document when starting a new project or refactoring an existing one. It provides a clear, documented system architecture including system inventory, boundary matrix, and rationale that guides development and ensures maintainability.

System decomposition requires analyzing the technology stack as one of its 6 core dimensions. While you can begin identifying user touchpoints and business logic independently, defining the complete system architecture and deployment units requires concrete knowledge of the underlying technology stack.