Originally posted by Bruno Taranta Arruda:
Hi,
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.
Best regards.
[ April 24, 2008: Message edited by: Bruno Taranta Arruda ]
Hi Bruno,
Let me try clarify your doubts answering your questions pontually Ok? Here we go ...
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?
R = Create to differente diagrams, one focusing on the analisys level, showing business entities, relationships, multiplicity, not mentioning attributes or methods and focusing on inheritance if applicable. The second diagram should be a structural explanation of your sequence diagrams, focusing on associations (aggreg or composi), dependencies, layers, packages, interfaces and realization, and some important attributes that should be valid mention at the diagram. At this second diagrama, you could mention some components like fa�ades and controllers, but do not mention those components (any of them) at the class diagram at analisys level.
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 ?
R = There is no rule for that. Choose one and ask yourself: I should be able to understand this diagram without all those details? Take a friend and ask him to understand your design. If could be a little complicate to understand, means that your diagram are poor. There is no pattern for that, architecture is about communication. Three diferents Java projects could have different architectures and forms to demonstrate it. Regardless the exam, design an architecture implies of create a structural mechanism to create an application in a controlled fashion.
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?
R = Both of them. Demonstrate at your sequence diagrams the behavior of some use case transversing your components and entities. Just keep and mind that based on the layers and tiers concept, some entities could not be accessed by some components, eg: Remote JVMs does not access JPA entities using LazyLoad. Rembemer that UML 2.0 offers some special kind of messages for construction and destruction of objects, try to use them.
Cheers,
Ricardo Ferreira
