How do you design software?

My coffee break challenge

A big thanks to everybody that came along to the Why do software projects fail? session last night, it was a really fun evening! The slides from my talk are available to download/view online.

Coffee break challenge

As I said in my talk, here's my challenge to you. Next time you grab a coffee with your team, have a quick discussion about how *you* design software. By "design software", I mean taking a set of vague requirements with a blank sheet of paper and creating a software solution. Think about things like your process, approach, tools, techniques, etc. Can you explain how you design software within the time it takes to finish your coffee break?

Please do let me know how you get on. I'll post a follow-up next week...

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.

Re: How do you design software?

I could give an overview during that time frame, but could I actually explain how I design systems? Not a chance. I've put up 35 posts so far and only begun to scratch the surface.

Communication, collaboration, and pragmatism are, for me, the key concepts.

Re: How do you design software?

OK, so I've been meaning to respond to this for a while after seeing updates flying around on Twitter. I've taken a coffee break (honestly) and pulled together a post in response.

Add a comment Send a TrackBack