This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I was doing the SCEA part-2 assignment. I have a lot of classes around 64 in my design. If I show the complete details of each classes (properties and behavior), then it would be too difficuilt to understand.
Can I keep a main class diagram showing relationships and separate class diagrams showing each of the components in the diagram?
or is it mandatory to show the complete details in the same diagram?
I haven't yet done the part 2, however what you are suggesting seems reasonable. As a matter of fact I have been doing this as showing associations & properties for where there are large number of classes makes the diagram very difficult to understand.
64 classes seems to me too much. Well there is no magic number like we should have only 30 or 40. In my assignment, i had only 45 and i didn't show attributes, i just showed all methods which are there in my sequence diagrams and i clearly mentioned that in the notes.
I will suggest stick to one class diagram concept only and there is no need for two class diagrams.
I agree with deepak 64 classes seems way to much..perhaps its based on your assignment too. I had one class diagram with 25-30 classes and I included the methods and fields which I had to show in the sequence diagram.
Again, I would go with Humphrey Sheil's example problem (Chapter 9). He has a fairly complex bidding example and uses less than 20 classes in the class diagram. My submission for Part II had about 25-30 classes.
Also, if your assignment says "Class Diagram" (not diagrams), I'm not sure if the assessor/examiner would expect multiple diagrams and/or go through all in so much detail.
My understanding is - point out the main classes and as Rupesh has mentioned, keep it simple.
I agreed with Ravi. One high level class diagram should be good enough. Remember the purpose of the diagram is to show how your system will work, not how you are implementing the system. In my assignment (Big Cigar), I only have about 15 classes including only entities (with only entity names) and service beans (with only method names - no signatures).
Anyway, in real life if your diagrams aren't understandable within 5 minutes, you won't be able to sell your solution to any executive which is normally on of the main objectives of a SA.
“Everything should be as simple as it is, but not simpler.” Albert Einstein
I split mine into 2 class diagrams. I had 26 classes, but it was still hard to follow as one diagram. I did put the properties/methods with the classes. I didn't list out every one though. Just a representative sample and methods that show up in the sequence diagram.
I think what you are proposing with the split is ok. It's like a high level diagram and then zooming in.