Learn to think

The blog has not been updated for a long time. These days have been busy with a small project named "resource editor. Today, I finally handed in "Results" to my boss. No matter how arrogant the boss is, I am so ignorant and arrogant that I am waiting for him. I will set a tone for myself.

Although the project is small, it is dirty. From requirement analysis, to design, to coding implementation, there are some standards, of course, to a certain extent. Therefore, from this small project, I learned happy for design that I had never experienced before ).

This is the first step to develop a project plan for yourself (the previous project risk analysis is not available here, after all, it is done by hand ). How to set a plan shows the gap between people with design and project experience and common coder. I started to think that it would take at least five days for coding between 8 and 9 days. However, such a suggestion immediately raises an objection. The length of the coding time must be reduced. If the design time cannot be guaranteed, the time for reverse engineering will be longer or even fail. This statement is simple and difficult to implement. Later I decided:

This setting seems to have begun to focus on design.

During the entire project process, the UML diagram shows the design idea. In the demand analysis stage, an example is provided:

It is very exciting to enter the class design. Previously, I learned Oo and learning patterns. These things were only designed, but I never gave myself such an opportunity. There was always no such idea and there was no effective way to do it. If you want me to write one or two classes to implement some function, it may be okay, but if you want me to use OO to organize a system with my own classes, haha, afraid! This time, I would like to thank the boss for this opportunity and a wealth of guidance. Let me write my core class library boldly. It is the best choice to use a class chart to show all of these:

There must be errors and not enough, but now I have realized the joy of design. I don't have to worry about implementation details, but I think about problems based on my own ideas. It's really a pleasure to do it :)

For class design, many of my friends must have the same feeling as I do not know how to start and how to put a function in that class. Yes, this is one of my biggest troubles. It seems a good method to analyze the class method through the time sequence diagram :) (this is what the boss said, thanks to ing )!

Having written so much does not seem to express my thoughts as much as possible.

The last point is the conflict between design and implementation.

Like many friends, I spent a lot of time researching a technology implementation to study a detailed problem. Remember <clouds to code> there is a saying like this: there is almost no lower level than talking about details, except for optimization. Yes, if you think too much about the details in the project design phase and how to implement it, it will distract you and prevent you from actually focusing on the design layer. The process of thinking will also be interrupted frequently. Through this project, I also realized this.

Well-designed and distinguished class responsibilities, so that each class can do its own thing, and difficult implementations will be broken down.

Unfortunately, this project does not use a pattern. It is not because it is not available, but because it lacks the ability to refactor. It cannot be discovered. I feel that rfileeditor can use the singleton mode here. I designed it as an abstract class to provide services through static.

There are too many questions about initial design. I don't want to miss someone, just make a note myself :)

Finally, paste the page:

 

If you are interested in the mode, add this group: 26227899.

 

2006-9-25