design controller object

[nitin kumar]

Hi I have already done my use case diagram and Im fixed in the sequence diagram. My scenario is that an actor interacts with the system and the system responds to the input .Here the input is dynamic .The system basically picks up the log of users and it gives according to what port or protocol or source or destination.These all input is not needed at once.Any one will do.
Now my question is should I go for a controller object which validates the input and another object which handles request from the actor.
please guide me

[Jose Botella]

Controllers shouldn't be performing domains task, but receiving the system events and delegating to those objetcs in the domain that carry out the related system operations.
Controllers are like facades between the UI and domain layers.
[ August 17, 2002: Message edited by: Jose Botella ]

[Vikrama Sanjeeva]

Hi,
In addition to the above, Controller should be the part of Buisness Model rather than Presentation layer.
I am confused why Larman has included in GRASP?.Why not it included in Design Pattern catogory.I think role of Controller is important in Designing s/w rather than assinging responsibilities.
Bye,
Viki.