Originally posted by Tibor Hegyi:
I have read through a couple of hudreds of threads in this forum to gain consistent understanding on approaches to creating diagrams for Part II.
Unfortunately, I could not resolve the ambiguties I found.
1. What exactly should be drawn in the class diagram? I have drawn my extended, slightly changed BDM with some controller classes
2. What about classes not directly related to the business case but rather to the implementation details? I mean classes like
Command or Factory? Shall these go into the Component Diagram? If so, in form of classes or of components?
3. Which diagram is the sequence diagram built on? Some on this forum said it should be built on the Class Diagram showing
messages sent between classes. Some said (along with Cade) it should be built on Components showing interaction of components.
I tend to think ... the sequence diagram should be based on the Component Diagram
4. ... does each component have to have a corresponding class in the Class Diagram?
I think I will treat as a component each:
- at least one shared JAR of server related classes,
- at least one shared common JAR (for server and client),
- each JAR of each EJB,
- the ServiceLocator,
- the BusinessDelegates (depends on ServiceLocator)
- each Factory
- each WebCommand/Command pair
- each JSP or Servlet,
- the Java-client in total,