Hey everyone! I'm currently at university and we've been taught a whopping 13 different types of UML diagrams like use case, sequence, and class diagrams, along with other modeling techniques from last semester (Merise). I've asked around for advice but keep getting mixed answers. So, I'm curious—how many of these modeling diagrams do I actually need to know? And is it true that modeling should always come before coding? If so, why is that? Thanks in advance for your insights!
4 Answers
Diagrams are actually really helpful for explaining concepts to clients and teammates. When you're in design discussions, having a shared diagram can set a solid foundation. Some firms even use UML tools to generate code, helping to maintain specifications. We've been using Mermaid diagrams lately, and they work great for us!
I disagree with that! While I do think that sequence diagrams are super useful, it really depends on what you're working on. Class and deployment diagrams are also essential. You might not use them as per formal specs often, but understanding them fully helps you decide which ones are worth keeping in your toolkit.
Just a heads up, modeling isn't always done before you write code. There are lots of iterative development processes out there that don't rely on extensive modeling beforehand.
Honestly, you might not need to know all 13. In my experience, UML can be overrated. The only ones I've really relied on at work are class and sequence diagrams. If your team uses UML, sure, learn it, but otherwise, a simple whiteboard sketch might be enough to get by.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically