Thanks, Anil.
Could u pls share your thoughts on Part 2/3. Thanks
The biggest thing is, apply the KISS principle. Or, to paraphrase Einstien, your submission should be as simple as possible, but no simpler. I've been working in a pretty high-ceremony environment for a while, so it took a while to get that little idea through my head. Actually, it was this forum that brought me around to a simpler approach.
Look at the case study in the Cade book. I had some pretty laborious diagrams at first, but then I scaled them down to the level of detail in that case study.
I did use some of the
patterns from the Core J2EE Patterns book, but only where they felt natural. I used
Struts, but that was my personal preference. I don't know that a MVC framework is required, but it is a blueprints best practice to use one.
Rose is horrible for sequence diagrams. If I had to do it over, I'd draw them in crayon and scan them.
Overall, I found the best study material to be the Designing Enterprise Applications... blueprints book and the Cade book. I started off analyzing Petstore to get some feel for the kind of design practices they might be looking for, until I understood that Petstore uses everything but the kitchen sink, for the purpose illustration, and no real application should be designed that way.
Remember when shopping for study guides, you can't judge a book by it's mass. On the moon a thick book and a thin one will both fall at the same rate.