Clever Geek Handbook

What do you see in the sequence diagram to indicate that the system is well archived?

What good practice icons are you looking for in the sequence of method calls as shown in the sequence diagrams?

+1


source to share


2 answers


Look for the control central controller. A well thought out system will have an equal division of responsibilities between classes. A poorly rated system instead tends to have a sequence diagram with many messages going to or from a class in the middle that frantically receives messages, makes decisions, invokes subordinates, and generally starts everything.



It's no coincidence that the controller class is also significant, has a lot of procedural code, and usually looks like FORTRAN in a funny hat.

+4


source


I would say the same as for good software:



  • Naming (classes and methods not instance names)
  • How many parameters do methods have (if shown)?
  • Does the call chaining make sense with respect to the level of detail (e.g. grain to fine or coarse?)
+1


source






More articles:


All Articles