Hi groupmates, I found that some of you made one Class Diagram for the assignment. How can one class diagram illustrate all classes in the application? Where can my EJBs or helper classes be placed? As I know that, there would have three kinds of classes, entity, boundary and control classes. Each kind of them gives its own functionality, e.g. entity class declares the business entity. While I am preparing for the assignment, I found difficult on differentiating the class diagram and the component diagram. Does the class diagram only the business model? or Should I draft more and more class diagrams. Please help!! Franky
Personally I fit all of my classes into one Class Diagram without much of a problem. It was a pain to get all the lines to look nice without crossover though . I started out with three separate Class Diagrams and then consolidated them at the end. As far as the difference between Class and Component Diagrams, there is difinitely a significant one. Think coarse-grain for the Component Diagram and fine-grain for the Class Diagram, so your helper and miscellaneous classes will not be part of the Component Diagram. The Component Diagram is also where you get a chance to illustrate the separate servers where all of the components reside.