Originally posted by tony clare:
do I need to create two sequence diagrams one for web users and the other for swing users ?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Saritha ventrapragada:
If both the Web and Swing components are using same business logic why cant we have a generic Actor called UI, ...
Originally posted by Saritha ventrapragada:
... generic Actor called UI, which initiates business logic
Originally posted by Saritha ventrapragada:
We can draw seperate sequence diagrams for Swing and Web application.
In these diagram for the business part logic we would refer to the above sequence diagrams.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Thomas Taeger:
An actor should not (at least not directly) initiate any business logic, not for technical but for design pattern reasons. The needed conjunction is a web-server-side frontcontroller/helper and a client-side GUI/Swing controller/model.
Originally posted by tony clare:
by using reference, I understand there are 3 sequence diagrams for each use case: web client, swing client and a common shared EBJ tier. Right ?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Saritha ventrapragada:
Actually I was thinking of one more layer of POJO classes (like facade classes) ...
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.