Sequence diagram detail level

[Mauro Nenci]

Hi guys.
I'm approaching to upload my SCEA Part II package.
But i'm uncertain about sequence diagram detail level.
I've designed diagrams that have high level details up to EJB Session Beans, but about EJB Entity Beans i've preferred to display both Home and Component interfaces. The first to signal create/find operations, the second to signal (where necessary) data access. Both have <<entity>> stereotype.
I don't know if is necessary to mantain both interfaces or collapse all into one single component that collects all create/find/data access messages.
I would glad if someone give me some tips.
Thanks in advance.

[ September 01, 2006: Message edited by: Mauro Nenci ]
[ September 03, 2006: Message edited by: Mauro Nenci ]

[Mauro Nenci]

There's anybody that could give me some tips?
Thanks.

[Cleuton Sampaio]

Please know that I haven�t received my results yet.

I have completed all 3 steps.

In my diagrams I represented EJBs as just one class with a stereotype indicating that it is an EJB (with the propper sub-type: entity, stateless session, or stateful session).

Note that these diagrams are high-level architectural diagrams, not detailed design diagrams.

[Mauro Nenci]

Hi Cleauton.
Thanks for your reply. So do you haven't used <<boundary>>,<<control>> and <<entity>> stereotype in your sequence diagrams? I've used this stereotypes in my sequence diagrams, innstead i've used stereotypes that you've noticed to me (<<servlet>>,<<EJB Session Bean Stateful>>,<<EJB Session Bean Stateless>>,<<EJB Entity Bean>>>) in my component diagram.
Just one question. How is possible that you've completed Part II and Part III without receiving result of Part II almost?
[ September 05, 2006: Message edited by: Mauro Nenci ]

[Ray Ye]

But i'm uncertain about sequence diagram detail level.

It is OK to be detailed. I did something similar as to separating Home interface from Business interface in my sequence diagram.

[Mauro Nenci]

Hi Ray.
One question. Do you have kept separated for ALL EJB components (Session, Entity) or only for Entity? I've kept separated only for EJB Entity (to better depict separation of create/find messages regards other data access). In this way any of my sequence diagrams have beyond 20 object instances. I'm trying to keep diagrams as clear as possible, but i'm afraid that using this approach they become very confused.

[Cleuton Sampaio]

Hi,

You have to send a note to [email protected] asking upload rights for your assignment, sending your id along.

When you receive the upload rights, you have to upload your jar file and, after that, immediatelly schedulle your phase III essay exam.

They will only work on your assignment after you have completed the essay exam.

The essay exam servers, among other purposes, to know if you have written your assignment by yourself.

[Ray Ye]

Do you have kept separated for ALL EJB components (Session, Entity) or only for Entity? I've kept separated only for EJB Entity (to better depict separation of create/find messages regards other data access).

I did it only for Entity beens too (for the same reason as you mentioned). So you should be fine :-)