At last I am getting around to posting some details about my solution
My background : I have several years experience in
J2EE. Apart from real-world experience, I have been studying pretty thoroughly the theory (see the
SCEA books listed here) and the examples (e.g. the petstore application). All of this is in my opinion an absolute must if you want to pass the exam.
Don't ask me how long it took. Too long.
I made one class diagram, one component diagram and 10 sequence diagrams. The sequence diagrams referred to other included sequence diagrams ( e.g. Select Customer, Select Itinerary)
To create the diagrams I used JUDE, but I regret that, since JUDE does not support UML 2.0 as good as I would have liked to. But I used comments as workarounds.
The class diagram contains 28 classes. No fields and no methods, but stereotypes (both in classes and associations), multiplicity and comments are there. I did like the "Processor"
pattern and I also described here what is going to be an Entity or Stateless bean (as stereotypes)
The component diagram contains 20 components. As suggested many times in this forum, a component is a technological
unit, so I have here components like "Front Controller", "Data Access Object" and so on, and in the comments I do write , for instance, what DAOs are actually going to be created.
The sequence diagrams are very detailed and I used the same approach as in the component diagram - objects who have similar functions (Views , Processors) are aggregated , and this is explained in the comments.
The assumptions document is 7 pages long. I created it using NVU. I wrote a short paragraph at the beginning where I explained the conventions I followed in the diagrams, and then a part I called "Application Structure", where in turn there are subparagraphs for every relevant part in the application (e.g. Beans, Daos, Clients, Views...) and where I explain in detail what might not be obvious looking at the diagrams.
That's all folks !
