Timeline for What classes to put exactly in a class diagram?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 13, 2013 at 21:10 | history | edited | rae1 | CC BY-SA 3.0 | added 437 characters in body |
| Mar 13, 2013 at 21:08 | comment | added | rae1 | @MalikaQueen Like I mentioned, for the class diagram to be useful, you need to divided by layers, and by components within these layers, if needed. If it is still too complex, it means you might need to rethink the relationships among your classes, and mapping them all out can help understand which ones are needed, which ones can be combined, or deleted, and improve it to the point you have a simpler class diagram, thus a simpler program structure. | |
| Mar 13, 2013 at 21:00 | comment | added | FrustratedWithFormsDesigner | @MalikaQueen: A good time to stop is when it becomes difficult to read/understand the diagram because it has gotten too big/complex. That's when you start moving sub-components to separate diagrams. | |
| Mar 13, 2013 at 20:50 | comment | added | Angelika | @MichaelBorgwardt Thank you for your information , Have you an idea about the level of abstraction in class diagram ? I mean how to devide every entity to sub-entities and when to stop? | |
| Mar 13, 2013 at 20:11 | comment | added | Michael Borgwardt | No - the diagram will still contain classes. Putting every single implementation detail into UML is IMO counterproductive: it doesn't help understanding, is additional work for no benefit and has the potential of becoming actively harmful when it inevitably fails to be updated. | |
| Mar 13, 2013 at 19:04 | comment | added | rae1 | @MichaelBorgwardt I agree. Which is why I mention OP should try to divide the diagrams into meaningful sections or subsections. But to not include most classes will result in a program diagram rather than a class diagram, don't you think? | |
| Mar 13, 2013 at 18:58 | comment | added | Michael Borgwardt | It's supposed to help understand the system. A diagram that includes every single class in the system contains too much data and too little information about which of it is important. | |
| Mar 13, 2013 at 18:52 | comment | added | rae1 | @MichaelBorgwardt ...and so what is it suppose to do? | |
| Mar 13, 2013 at 18:45 | comment | added | Michael Borgwardt | no, that's not what a class diagram is supposed to do. | |
| Mar 13, 2013 at 18:06 | vote | accept | Angelika | ||
| Mar 13, 2013 at 18:06 | |||||
| Mar 13, 2013 at 17:49 | history | answered | rae1 | CC BY-SA 3.0 |