About UML diagram
- All the diagram could just reflect some aspect of the whole system from a specified angle, which the owner wants to express.
- It's just a tool to present your understanding about the system under design. obviously, diagram is easier way to get the whole picture. what's more, the process of drawing could help you to organize thoughts.
- The thoughts beneath the diagram is essential, which you can deduce using method of OOA/OOD. Design pattern is great experience pioneers have summarized up and stands time of testing. Consider these pattern when practising.
To be honest, I don't learn as much as I expected from this training. The main cause is I'm not familiar with Object-oriented design, although I've read some books in this area. How to abstract classes from the business domain? How to create use case and how to make these class interact with each other... All of these needs time of practice.
So what's the follow-up action?
1. Try to think the project I've worked on in an O-O way and embody these thoughts with UML diragrams.
2. When playing with open-source project, always ask self several questions.
- How is the problem domain split up, which is represented with various classes.
- Does it take some kind of design pattern?
- Is it possible to address the problem in another different or better way?
