Link: https://ea.rna.nl/2023/06/18/the-other-side-of-requirements/
From R&A IT Strategy & Architecture
We tend to think of requirements as ‘incoming’ elements for our designs. But what we not always explicitly notice is that we also create many ‘outgoing’ requirements in our designs, often in the form of ‘constraints’ of the ‘users’ of the products that come from those designs. These requirements lead a hidden existence most of the time, and that invisibility makes our decision making sometimes less efficient.
What if we would make our outgoing requirements explicit? And how could we manage this? For that I created an actual small demo solution to manage solution designs in a library that links them and the requirements they give to each other, built as a plugin for Confluence.
