Author: Zhu Jincan
Source:Http://www.cnblogs.com/clever101
Sometimes I am thinking about: what role should users play in software development? In software development, can a user just find the food they need and pay the money to the salesperson like a customer entering the supermarket? I think this is not the case because of the special nature of software development. This kind of particularity lies in that the user does not consume the software at a time.
I thought about whether there are qualified users and unqualified users. I have worked on an arduous project. A user is an expert user. He has developed his own project and has a clear demand for himself. He wants to apply the system to practice, this saves a lot of trouble in requirement analysis, but there are a lot more problems in the development process (because it is not easy to satisfy his demanding requirements ). However, after the project is over, I feel that I have learned a lot and enjoy it. However, I have encountered many projects that users are reluctant to write even the requirement statement. They mean: I have handed you this project. You can help me complete the document first. After I modify it, you can give it to the entire system. Pure nonsense project!
someone may ask: this is the requirement analysis issue. However, the difficulty of Software Requirement Analysis is sometimes like Henry . Ford's famous saying : " if you ask customers who have never seen a car, what do they want, they will certainly say ' I want a horse that runs faster. In China, some users do not want to figure out whether they want a horse or a horse.