ALL OF THE POINTS BELOW ARE PERSONAL OPINIONS (just in case... ) A few comments: - I have no idea why I lost so many points in the class diagram. I was actually quite satisfied with it, I thought I had applied the proper design patterns in the right spots. Anyways, the diagram contained roughly 60 classes/interfaces with only the methods that I considered relevant. - The component diagram contained roughly 50-60 components. I've applied a logic similar to the one in the "official" Study Guide and put Views, Controllers, EJBs, DAOs - Sequence diagrams took me an enoooormous time (for 12 points! *SIGH*).
Note (probably evident): don't even think about NOT using a UML tool for this. I've used "Poseidon for UML" that proved to be reasonably stable though it regularly required rebooting my laptop to get to the proper level of performance.
In terms of technical choices (EJBs, DAOs, WEB vs. Application), I think I've proposed reasonable solutions - at least the ones I'd have applied in the real life (I've been working with Java since 1995, poor old me). Again, no idea about why I got 36/44 on the class diagram, whether it was for my implementation choices or other things such as saying that the UC Log In didn't need details as I'd use JAAS to fulfil the requirements. Yes, my architect's feelings got hit here
In terms of documentation, I've written what I felt was required to justify my choices - technical and "functional" - and the level of details I've applied to the various diagrams. I relied on the fact that the reader knew what Design Patterns were and when/how they should be used.
In terms of references for this work, there are a few "absolute must": - "Gang of Four" Design Patterns - Core J2EE Design Patterns and a few recommended ones: - Designing Enterprise Applications 2.0 (free on java.sun.com) - SCEA study guide
Finally, I'd say that working on this assignment took me 35-40 hours plus the time to "digest" the requirements (that I really - really! - suggest you read carefully).