Agile Architecture: GitOps + Markdown + Mermaid
Software Architecture tooling does not need to be legacy. This post is about an ultra lightweight agile architecture tech stack and methodology for System/Software Architects and Software Developers.
The Context
You are a(n) (Embedded) System Architect, a(n) (Embedded) Software Architect or a(n) (Embedded) Software Developer and like agile, lightweight methodology of working and collaborating with the development team.
The Problem
Rather legacy software architecture tools like Sparx Systems Enterprise Architect
- tend to be an overshoot (model based design features are not required in majority of use cases, benefit of using 80 modelling languages?),
- tend to be clunky and inconvenient to use (diagram modeling convenience, team collaboration capabilities),
- tend to have bad support (if you don't want to pay for it extra) and little user communities,
- lack of support for diagram generation from new programming languages (no Go, no RUST, no Flutter, no TS, ...),
- lack of hyperlinking capabilities (diagram entities -> source code),
- lack of modern AI features (boosting productivity significantly) and
- are often quite expensive (a single EA license is > 109 EUR per user for example).
Don't we have a choice? Luckily, we have!
