Reflections on Software and Documents in Agile Development

xiaoxiao2021-03-06  36

I have also tried that "naked" without a document is advancing, and it is conceivable that finally, the project is often reworked, and the new personnel must be dedicated to reading the source code that has almost no comments left by the previous person.

Later, I tried it, formulating a perfect norm, using a large number of software development document templates, but unfortunately unfortunately reduce the burden on the developer, the other hand is awkward, the situation is not much better than the document, because in the project In the implementation, there are very few documents and software that can be fully synchronized. A simple demand document starts from the beginning to the project, often changed to the face, at the same time, it is necessary to spend a special software developer to organize the document, have to say a waste of resources.

With it to make a false document, wearing the emperor's new clothes, it is better to simmerly simply naked, this is my idea, but there is no courage to implement.

I don't know who said: Software = Program Document, I think half of the agreement, the software is ultimately to give the user something, the user is satisfied, it is a good software, not satisfied is not a good software. For the user, he needs to pay is the cost of software, and another part of the software development process, etc., is the company's upgrade, maintenance, and expansion after the product, users are not obligated to pay for this.

All along, we all use the CASE tool, use the UML map to communicate, sometimes these tools are difficult to meet our needs, we will also try to do what you mean. After using these tools, my feelings are that everyone has become dumb by the original normal people. Sometimes, I can solve the problem in a word, but it is more than the hand gesture for the last half.

The use of new technologies and new tools, bringing more common information between people and people, if the effect is just the opposite, then we have to consider, why do you like this.

Until exposure to agile development, I feel that I have been cheerful. Software development although there is no silver bomb, in different situations, there is always a suitable method to let developers climb out of the tar.

in"

The active practice of agile modeling limit programming and unified process ", the beginning of the book, the beginning of the beginning, they don't use the Case tool in fast communication, they use a few sheets of paper, and catch up The pen starts to draw a sketch, even, in the second half of the book, when designing the user interface, it is actually drawn from the sketch.

Maybe I look very ridiculous, but I really don't do this. I have always believed that strict management, strictly follow the norms to take high quality products, and now it seems that I am misunderstood. The goal of software design is to successfully develop a finished product that allows users to use it.

In the process of doing projects, we often pay attention to the extensibility and ease of use, so that excessive analysis needs, not only provide some functions that users do, but also let users invest in funds that don't take it. At the same time, we have wasted a lot of time.

In XP practice, there are many practices that are exciting, do not say other, although XP is not against document, but according to its thoughts, give developers as much as possible to write or do not write an excuse to write or write a document. I have not had a chance to practice the programming, but I don't feel it is a good thing. Although I don't believe it, I can increase the efficiency of a few percent, but the development of the software is a mental activity, be a small function, conversion It is a good way to think about it.

But in the programming, there is a place that makes me confused: Generally speaking, people have to do something, to enter the state, about 15 minutes, start time, then, whether any disturbance (including phone, someone asking Words, will cause the interruption of ideas, so that people should re-adjust the state, which is a few minutes of time spending. I don't think this will make people more focused (someone is also the same next time). Because there is no experience in the absolute programming, it is almost a few words.

转载请注明原文地址:https://www.9cbs.com/read-60194.html

New Post(0)