Survey on the use of sketches and diagrams

This is a guest post by Sebastian Baltes, University of Trier. Please consider taking part in his short study (details see below).

Over the last decade, studies have shown that, despite the dominance of source code, sketches and diagrams play a major role in software engineering practice.

The focus of our current research is to expand our knowledge on the use of sketches and diagrams in software engineering practice. We are particularly interested in how these visual artifacts are related to source code. We do not exclusively focus on software developers, but on all "software practitioners" including testers, architects, project managers, but also researchers and consultants.

If you think that you belong to this group of software practitioners, please help us gaining deeper insights into your work practice by participating in our short survey. It just takes five to ten minutes of your valuable time:

For more information, don't hesitate to contact me.
Thanks in advance for your participation!

About the author

Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.

You can find Simon on Twitter at @simonbrown ... see for information about his speaking schedule, videos from past conferences and software architecture training.

Add a comment Send a TrackBack