But Sequence and Component diagrams are very useful to document high-level design decisions. I personally created only few Use case and Flow chart diagrams during my career.
Interaction diagrams (especially useful is Sequence diagram from this bucket).Structure diagrams (except Class diagram).So when we need Class diagram, it’s smart to generate it from live code. You can generate new diagram from live code easily. Low level design may change easily and you don’t want to keep outdated diagrams around. There’s no need to create logic and tests, just APIs of the design.Īnd of course when you don’t need such generated diagram anymore, just wipe it out. You may find some important facts about the design while creating prototype. When we need to sketch class diagram upfront to consult design with the team, I would suggest to create prototype with desired class structure instead and generate class diagram from the live code (again with IDE). You just need to use plugin called ObjectAid. It is also easy with Eclipse or it’s flavors (e.g. To find out how to create such diagram, read this IntelliJ IDEA documentation.
0 kommentar(er)
