Originally posted by Bruno Taranta Arruda:
I work with java applications(with architecture and design) for some time. We all know there aren�t single answers for those problems we encounter at our profession, with design of j2ee apps is no exception.
I�m used to do the things "my way" based on some experience and a lot of materieal that I�ve learned thorught the past years. But now I need to finish my part2 of the "old" exam and I�m a bit confused. I just want to know what the examiners commonly see, cause there is no conversation and meeting like a real job has.
I hope I don�t cross the line of the questions regarding this forum rules.
1- A class diagram can show classes obviously, but with some research throught this forum I�ve noticied that the majority of ppl make the class diagram as an extension of the BDM, excluding details about the design of the solution, I was not very confortable with it at the beggining but I accepted it, and now I want to know if I should put the subsystems (payment and mileage) on this diagram, and if there is room for some patterns like adapters to isolete the dependency in this same diagram, or it should be all on the component diagram?
2- About the component diagram, I want to know if I need to specify every component of my application, for example, if I want to use DAO pattern, should I put a DAO for every entity like customer amd etc, or just put a DAO component to illustrate the architecture and put a note that should be one for each entity ?
3- If there is no design decisions on the class diagram, what I should interaface with at the sequence diagrams? WIth the components itself or should i create the classes at the sequence diagrams?
I�m sorry for my english and thanks a lot for the cooperation.
[ April 24, 2008: Message edited by: Bruno Taranta Arruda ]