Reading DTS analysis model and Design Model

Sorry, I saw it in the afternoon.DTrAfter the analysis model and design model, I have summarized some suggestions for their improvement:

LIt is necessary to clarify the return types of all methods and how to consume returned objects!

LIt is necessary to clarify the association types and dimensions between classes.

LThe attribute definitions of design elements should be clarified.

LThe associated class diagram of the analysis class should be included in the analysis model.

LInclude (Channelprocessor.

LModify the model and add the class "direct encoding" to the model.

LClass and attribute names must be consistent and unified.

LThe names of method parameters must be consistent and uniform, and the types must be clear.

LExpression in the Design ModelProcessor chain.

 

When I came to the company today, I thought about it. I chatted with Wang zhenqiang For A While yesterday. I was thinking that there is a correct attitude called careful design. In fact, design is never equal to "idle ". Platform products must be developed in accordance with standard software processes. The more we work on design, the better our work products are designed and the better the architecture.

The first thing we need is not a dozen or a dozen.CodeIt is a thought, clear thinking, and organized model. Of course, there are also many ways to express this idea and organization, which is directly related to the project specifications.

I also thought about the difference between "self-knowledge" and "Expressive (well-organized model or other methods)" when talking to Wang zhenxiao, it is like the difference between "students understand themselves" and "teachers need to understand others. Imagine that when we were a student, we knew the concept of "Balance Tree" and thought we understood "Balance Tree". If we were to be teachers, the level of knowing alone cannot make students really understand the Balance Tree. Therefore, in the software development process, a similar situation is that we alone "know ourselves" is far from enough unless you can clearly express the specifications.

Avoid code odor and experienceProgramA clerk often goes beyond the design to Code directly. When there is such an idea, the Code he or she previously wrote may smell bad.

If software development is art, the work products for analysis, design, and coding are the work of art that is "elegant and common. "Elegance" is "The beauty of design and the beauty of architecture", and "Vulgarity" is "easy to understand". If our work products for analysis, design, and coding become "post-recognition, you can only imagine the meaning of the work at will, or you will not be able to understand it until many years later. However, for rigorous and simple software development, the "post-recognition" is absolutely undesirable!

I am wondering, if we advocate and/or advocate "What process ?" (XP , RUP) "," What methodology ( OOP , SOA , AOP) We often suffer from financial losses because, after years of hard work in the software R & D field, you will go back and see them (process or methodology) are in the same line.

Ideally, our need for analysis, design, and coding is as much as we care about the clothes and trim before the first appointment with a girl who has been in the same mood, our products (analysis, design, and coding) are also incredibly elegant (please refer to the beauty of software in nirvana ). Our attention to "work" is just like our attention to that girl. It is a pleasure to get along with that girl. It is also a pleasure to see our beautiful work achievements!

In my opinion, if possible at work, let's talk face to face, because face to face is not just a voice!

 

I hope you can correct me. Thank you for your feedback!