What good-practice-indicating idioms do you look for in a sequence of method invocations, as depicted on sequence diagrams?
What good-practice-indicating idioms do you look for in a sequence of method invocations, as
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What good-practice-indicating idioms do you look for in a sequence of method invocations, as depicted on sequence diagrams?
Look for the telltale central controller. A well-factored system will tend to have an even allocation of responsibilities among the classes. A poorly factored system instead tends to have a sequence diagram with many messages going to or from a class in the middle, which is frantically getting messages, making decisions, calling underlings, and generally running everything.
Not coincidentally, that controller class also tends to be big, have lots of procedural code, and generally look like FORTRAN in a funny hat.