Hi,

I would like to know whether to represent the session facade as control class or an entity class in the analysis model of UML design?

Thanks in advance.

Probably a control class, though if it does nothing but pass entity data back and forth, an entity might be more accurate.

Or ... invent your own "Session Facade" stereotype and use that. Accuracy is better than shoe-horning things into narrow categories. UML is flexible for a reason.

Thanks for ur response.

When session facade controls the flow of invocation of various entities and also contains business validations in it, doesn't it become as a control class.

When I responded to your original post, I did not notices you were asking about stereotypes for the analysis model. For the analysis model, a controller stereotype would be appropriate.

For your design model, though, you should be more accurate, because your session facade will probably not be the only kind of controller in your application. For example, you will almost certainly have controllers in your UI layer as well (such as Struts Action classes).

Thanks for your feedback Paul

Since it is a facade, I suppose there is a possibility that it might be a boundary class...is it fronting a subsystem or tier for usage by any actors?

If u look at the subsystem perspective then Yes u r right. But when the system is developed the boundary is defined for the entire system know.