File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes SCEA Part 2- Sequence Diagrams Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "SCEA Part 2- Sequence Diagrams" Watch "SCEA Part 2- Sequence Diagrams" New topic

SCEA Part 2- Sequence Diagrams

s khosa
Ranch Hand

Joined: May 15, 2003
Posts: 72

Do we have to list/mention technology aspects of our implementation in sequence diagrams for part2? E.g If we are using Entity Bean, should we be listing calls to Home/Remote interface as part of Sequence diagrams for part 2?

Also, should we be listing these details for class diagrams? I have seen listing mentioning around 40-50 classes for some of the submissions discussed on this list. I understand that this is highly subjective and it depends how granular you want to go, but whats the right approach from SCEA Exam perspective. I feel there should not be more than 14-15 classes for this subsmission at tht high level.

Any pointers?

Sreenivasa Majji
Ranch Hand

Joined: Jul 12, 2001
Posts: 224
I think you shouldn't put home/remote interfaces in sequence diagrams. The purpose of sequence diagram is to show the flow, not how J2EE distribution technology works.

When you draw a sequence diagram, think this way; by adding this piece of information does it helps anybody or if I discard piece of information can I still convey the message I want to covey.

Sreenivasa Majji
I agree. Here's the link:
subject: SCEA Part 2- Sequence Diagrams
It's not a secret anymore!