After reading all the use cases I've prepared the first draft of the class diagram for Fly By Night assignment. I've based my diagram on BDM, added some classes that wasn't present in BDM (Payment and Credit Card), and added some statless session beans as processors/managers (my diagram is "Cade-style"). I believe that the diagram is fully sufficient for all the requirements mentioned in the assignment.
But while reading the posts found in this forum I've found that many people mentioned that their class diagrams were much bigger than mine. Many people claim that they have much more that 20 classes, whereas my diagram has a little bit more than 10. Because of such significant difference I'm starting to worry if I'm missing some important issues. I'm thinking about adding User base abstract class and two inheriting classes for InternetUser and TravelAgent, but I can't figure out any other classes to add - as I said, IMO my class diagram is perfectly sufficient for the requirements.
Could you give me some clues? What else should I consider and what other classes can I add?
Joined: Jan 30, 2001
You can add JSP, Servlets, JavaBeans, EJBS in your class diagram. Make it as elaborate as possible.
SCEA, SCBCD, SCWCD, SCJD, SCJP
Joined: May 03, 2007
"You can add JSP, Servlets, JavaBeans, EJBS in your class diagram. Make it as elaborate as possible."
I believe that such components should go into the Component Diagram, not into Class Diagram. Am I right?
Joined: May 10, 2007
Class diagrams should only contain classes - not JSPs. And while Servlets (and JSPs) are really Java classes, they are rarely included on class diagrams and instead are more appropriate on Component diagrams.
Worried about the number of classes on your class diagram? Don't worry about it - if your class diagram allows your solution to meet the requirements of the system, then it is complete for your specific solution. Just ensure that you are meeting all of the requirements!
Joined: Sep 27, 2005
I suggest you to focus on requirements and maybe ORM issues. Quantity does not always means quality