Behavior answer does not really show behavior in the first glance.

[mroodbari]

Behavior: The behavior answer is not really expressing much about the behavior. I have these reasons:

• First of all, when you go directly to that question, first thing we see is the Logical View point. There is nothing related to behavior there but rather structure of the system which I think we have shown in other questions, like role and implementation.
• In the same Logical View Point, "Behavior Entities" come very last and they are empty in case of Display Products.
• In the Development View we do get a diagram connected. But it's too far from focus, and it's not even relevant that much to the behavior of this feature. It's about pagination. I know there were few of those diagrams there
• In the UI, we do get a meaningful diagram, but I think it's still to far from point of focus.
• In general, I as a user, will have a very difficult time to understand the behavior of this feature. Also to relate the parts of the diagram to the rest of the structure.

[mroodbari]

Also, why don't we have usecases anywhere in the behavior diagram. Usecases have good useful sequence diagram. In fact, I think those diagrams must be the first thing user should see when they look for the behavior of a feature.