• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Omit JSP in sequence diagram?

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I want to follow Harish' approach on the sequence diagram : there will be 2 diagrams to explain how MVC works for 2 different clients. A few diagrams for use cases. The user case diagrams show the core business logic independent of client. (Thus, both clients share the same business logic). I am not sure for those diagrams, what should they start with...BusinessDelegate?

Thanks,
Nancy
 
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Nancy,

I am not sure for those diagrams, what should they start with...BusinessDelegate?


I am in the same boat as you. It was very hard to remove the JSPs from the sequence diagrams. Well I could have kept the clients separate from the rest of the sequence diagram, but in that case I would have 3 sequence diagrams for each use case.
 
Nancy Field
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Sudhansu Pati:
Hi Nancy,
It was very hard to remove the JSPs from the sequence diagrams. Well I could have kept the clients separate from the rest of the sequence diagram, but in that case I would have 3 sequence diagrams for each use case.



I think the 2 MVC diagrams are generic for all the use cases. That is why I will separate web-tier sequence from the core biz part..in that way, we will avoid the duplication in all the seq diagrams. So I will not list specific JSPs in the MVC diagram....I will use "ScreenView" to stand for a JSP. I will list all the JSP components in either the document or a note in the component diagram. The problem is if the sequence diagram omits the web-tier, it will not show the full action path from user to backend. Maybe someone used the same seq style and passed the exam can certify?
 
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Nancy & Sudhansu,

So what have you guys decided. Even I am too stuck with the same problem !
Thang Vu's posting gives a similar sort of information, Need to take a decision.

https://coderanch.com/t/152836/java-Architect-SCEA/certification/Passed-SCEA

Senthil
 
I wasn't selected to go to mars. This tiny ad got in ahead of me:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic