Forums Register Login

Action classes in component diagram

+Pie Number of slices to send: Send
Hi everyone,

I am creating my component diagrams, and i have used the Front Controller design pattern. My question is this: Should I use some action classes after the Front Controller ?

I think that for a complete design of this pattern, i agree with the fact that the controller does not execute any business rule or call any business object. It just delegate this to a action class (And it is a Command pattern).

But, in the other hand, i see that insert this classes in the component diagam, will over glutter it, since there will be to many actions for a single use case, or boundaire.

Could someone help me fix this doubt ?

Att,

Ricardo Ferreira - Brazil
+Pie Number of slices to send: Send
Hello Ricardo! :-)

My advice is to follow your instincts and keep the good sense. If you think it�d be better to hide some components in order to keep your model simpler, that�s no problem as long as you document it. Following this rule, you can keep things clean and simple, but always writing down some comments about it using UML�s notes.

take care and good luck,

Fred
+Pie Number of slices to send: Send
Hello my friend, that a good thing to know that you're here.

Thanks a lot Fred, I'll follow your advice and try to keep my diagram simplier but reasonable to the evaluator. Some tip from a good experienced person is the better thing that i could get.

See you

Att

Ricardo Ferreira - Brazil

Originally posted by Frederico Melo:
Hello Ricardo! :-)

My advice is to follow your instincts and keep the good sense. If you think it�d be better to hide some components in order to keep your model simpler, that�s no problem as long as you document it. Following this rule, you can keep things clean and simple, but always writing down some comments about it using UML�s notes.

take care and good luck,

Fred

 
+Pie Number of slices to send: Send
There are many ways to do it, so I don't have "one right answer".

I'd just like to echo the good advice - keep it simple, readable but complete. Not everything need to appear on the sequence diagram. But at the same time, it should not have gaping holes.

When you need to express more, but are afraid of complexity and size, use creative methods such as stereotypes and anchored notes. And as I have recommended here before, when you're finished, have it peer reviewed by someone who understands UML and Java. Your goal - anyone looking at your diagrams should understand most of it, if not all.
Evacuate the building! Here, take this tiny ad with you:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 926 times.
Similar Threads
Part 2 design doubt:SCEA help
What are the differences btw MVC and Front Controller design patterns?
component diagrams.
JAR the web-application or use WSDL/SOA ?!?!
Too many classes in the diagram!!! Am I wrong?
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 16:36:01.