I remember the first time I was first interested in the development method of the software. At that time, I started learning the waterfall model. From that time, I know that some things I have written before can only be called "one code", which is far from software. It has also begun to confuse the development method of the software, excitement, feelings, and software development is the complex process. At that time, I think the waterfall model solved my long-lasting question: How did these huge software have been developed. At the same time, I feel that I have grown a lot of knowledge. How many items have fallen or heard, I always think that there is no scientific development method, if you let me manage, I will use a scientific management method, standard documentation, interface, and there will be no such problem. . It seems that what is the past idea is what it is true, but who is not coming from Tianzhen!
Later, I was working, and I started my love programmer. With the tension, exciting mood is gradually calm, I struggled out of the code pile, began to examine my own projects, and I also discussed the different development processes of each company. The set of waterfall models is found in reality, there are very few implementation.
The general development process is like this: first is the project, this project may be an outsourcing, there is a list of items that may be received, which may be a product to be developed by the company; then set up a project team, designate the project manager, leaders generally give The time limit; then the project manager puts the project to the project, a certain module Zhang San is responsible, a certain module Li 4 is responsible; then develop, each person gets the three-digit land; finally integrates test, modify one Pile of bugs. The final release of Release is generally unsatisfactory, what to do, project extension, and people are responsible for modifying their part. Until the project is completed.
Therefore, we see our project management from this management process is a person management, a bit like a workshop management. Everyone is a need for this piece, database design, class definition, interface definition, code writing, document work, test. Everyone is all encompasive. The final product can be imagined. From this management method, we have seen the problems we hate now: a person written by himself, he understands himself (no documentation, there is no understanding), everyone has made a CSTROKE class, integrated At a big pile of problems, etc.
I started reflection: Why don't you use a waterfall model? What better ways can solve this problem?
I also discussed the waterfall model with my classmates. Everyone thinks that the waterfall model is just a theory, there is no specific operability. I think this truth is right, knowing that the truth does not say what to do. Everyone continues to discuss, I feel that some things in the waterfall model are also very difficult in reality. The most obvious is the documentation. First of all, we have to admit that China's programmer is very problematic. Many things are written like a book, no one can understand (I am deeply experienced); secondly, these usual writing is all plagiarized programmers write documentation Strengthen, no one is willing to write, it is necessary to write to a long time.
