We have been continuing to do Customer Research in November. We interviewed 14 individuals in November, making up a total of 36 interviews. Since the holiday season is just around the corner, the main goal would be to research as much as possible before the year ends.
During the recent interviews, we learned that software design techniques such as domain-driven design and event storming are rapidly gaining popularity in the industry for visualising and documenting architecture diagrams.
Identified 3 primary purposes of software architecture diagrams Visual Thinking, Documentation and Presentation and started using these 3 aspects to analyse interviews.
Further realised that software architecture diagrams can be produced by individuals with various titles in an organisation, from CXO to Software Engineer, depending on the size and type of the organisation.
A software architecture diagramming tool has different requirements depending on what it's intended to accomplish and who it's intended for.
Depending on the individuals who produce decisions or code, there can be differences in thinking patterns and expectations regarding software architecture documentation.
People don't like opinionated tools. For example, a diagramming tool forces you to follow the C4 model and only the C4 model.
With architecture diagrams, you have a challenge in keeping the code and architecture documentation in sync due to the fact that you have two different sources of truth.
Still, the research is conducted without a target market segment and will continue to seek opportunities for market segmentation. Our November interviewees and their organisations are reflected in the statistics below.