-The last thing that I want to mention about class diagrams is - -2
-some creation tips. So something I know based on my experience and the - -3
-experience of others, I can recommend to do when creating a class - -4
-diagram. So the first tip is to understand the problem. So take the - -5
-time to look at the description of the system that you have - -6
-to build, to make sure that you understand the domain. That you understand - -7
-what you are supposed to build. Because that is going to save you - -8
-time later. It's going to help you identify from the beginning, a more relevant - -9
-set of entities in the description of the system. This - -10
-one might seem trivial but is very important to choose - -11
-good class names. Why? Because class names communicate the intent - -12
-of the class, and clarify what the class refers to. So - -13
-having a good class name allows you, makes it easier, to - -14
-create the mapping between the real-world object and the entities in - -15
-your model. And of course, it also makes it easier - -16
-to understand the system, after the system is built. Third tip, - -17
-concentrate on the what. So here, in the class diagram, - -18
-we're just representing the structure of the system. We're representing - -19
-what is in the system. What are the entities? What - -20
-are the characteristics of the entities? We are not focusing - -21
-at all, on how things are done. So, be careful. - -22
-DonÃ¢ÂÂt think about the how, just think about the what. - -23
-Proceed in an itinerary way. So, start with a simple - -24
-diagram and refine it. There is no need to identify, - -25
-right away, all of the details of the system you need to - -26
-build. It is much easier to look at the description, identify an initial - -27
-rough class diagram and then refine it, because in this way, you'll - -28
-also gather more understanding of the system as you build it, and you'll - -29
-most likely end up with a better product at the end. And - -30
-if you proceed in this way, then make sure to refine until you - -31
-feel the class diagram is complete, until you feel that you represent - -32
-the system that you're supposed to build. So your final goal should be - -33
-to have a class diagram that is complete. - -34
-So it represents all of the relevant entities - -35
-in the system and their characteristics, and it's - -36
-correct so it represents them in the right way -- cgit 1.4.1