part II - class diagram, how detailed?

[SJ Adnams]

To those who have passed part 2.
How many classes roughly speaking did you put in your class diagram?
Did you include any Exception classes (or just note this assumptions)
Did you include home & remote EJB classes?
Did you go for the whole DAO, DAOImpl, DAOFactory stuff, or just note it in assumptions?
So far I have done all the sequence diagrams & have the class diagram in a rough form which needs cutting down a bit or the examiner isn't going to like the size of my gif file.
If your doing part 2 now (which I know lots of you are) feel free to post your class count - I don't think is the same as discussing solutions is it?
Cheers, Simon
(class count just over 100, I plan to cut this down & submit around 25 with a list of assumtions)
------------------
http://www.x-nt.com

[herve attia]

I'm starting Part II and I'm asking myself the same question : how detailed class and sequence diagram must be ?
The following JavaRanch threads may help to answer :
http://www.javaranch.com/ubb/Forum26/HTML/000407.html http://www.javaranch.com/ubb/Forum26/HTML/000105.html
herve

[herve attia]

another insight
http://groups.yahoo.com/group/scea_j2ee/message/3947

[SJ Adnams]

All a bit arm-waving isn't it?
It would be nice too see the examiners point scoring checklist, I really cant see the use of exception classes and even modelling the EJB interface classes. I've spent longer than I had planned doing this project so I think I'm just gonna submit it & hope for the best. If I fail - I fail, it's only money after all :/
------------------
http://www.x-nt.com

[Tiger Scott]

I think one should not be very detailed in the class diagram. It just clutters up the diagram. I would opinion avoid repetetive classes - like a DAO for each EJB or all Exceptions etc.
Sanjay
SCEA

[herve attia]

I agree with Sanjay.
Sun SCEA document mentions, for instance, "it is not necessary to provide each method name and attribute in the class".
That means they don't want UML diagrams confused and complicated to read.
The human, who will grade you, will check it out :
-UML compliant
-Correct usage of entity CMP/BMP, choice of session stateful/stateless.
-Applicability of design patterns.
-Consistency of your architecture
-Suggestions
For instance, you can just add a note in your sequence diagram that an exception (application or system, related to transaction)will be log or thrown, and show in your sequence diagram a link to an "error jsp" object.
Don't forget you provide a kind of BluePrint. The FBN CEO has to clearly understand your architecture/Design.
It is not a "reference manual" for the developpers.