Hi All,
I am planning to have GUIRequestProcessor which is like a proxy for the GUIClient accessing the Business Logic (SLSB -the SessionFacade). Similarly I have an an actionProcessor and a frontController in my design for web-based requests that access this SLSB. From that point onwards everthing that web-client can do, the GUI client can do as well.
I want to take an opinion. Can we depict both the GUIRequestProcessor and the FrontController in the same sequence diagram or its better to show it in a seperate diagram. If I keep it in the same diagram, I am not sure how to depict it. Can someone give some guidance on how they approached it ?
I came across this issue because I planned to show the login usecase in all the sequence diagrams and also show that the request is coming from both web and swing client.
any thoughts.
thanks.
I am planning to have GUIRequestProcessor which is like a proxy for the GUIClient accessing the Business Logic (SLSB -the SessionFacade). Similarly I have an an actionProcessor and a frontController in my design for web-based requests that access this SLSB. From that point onwards everthing that web-client can do, the GUI client can do as well.
I want to take an opinion. Can we depict both the GUIRequestProcessor and the FrontController in the same sequence diagram or its better to show it in a seperate diagram. If I keep it in the same diagram, I am not sure how to depict it. Can someone give some guidance on how they approached it ?
I came across this issue because I planned to show the login usecase in all the sequence diagrams and also show that the request is coming from both web and swing client.
any thoughts.
thanks.