Requirements as Code: Approved in 4 Clicks

We transferred requirements from scattered documents into a Git repository, where they follow the same rules as code: they have branches, go through reviews, and are compiled into documents automatically. 

In the course of our work, we encountered the fact that a lengthy approval process, lack of traceability to architectural elements, and the absence of a single up-to-date set of requirements led to real knowledge about the product being 'dissolved' across message threads, outdated diagrams, and developers' memory. This pushed us to look for an approach where requirements become the same kind of engineering artefact as code. 

We'll share how we arrived at the “requirements as code” model, built a process from writing in unified templates to approval in Git with the efforts of the entire team (analysts, architects, developers, testers), and continue to optimise this workflow for multiple parallel versions of the product.