This time, I started a new project in the laboratory. It was a project that the teacher took over, and it was also the most important project for me in the laboratory, because the previous projects either participated in a little by myself, which was like making soy sauce (but There will also be some gains), and there are some projects that I do privately for my classmates or a teacher. The scale is not large and the technical content is not very high (but it also made me familiar with many things). In addition, this project is largely controlled by me in terms of progress and technical difficulties, and I also hope to be able to make a relatively complete and complete project before graduation. Therefore, for various reasons I still attach great importance to this project.
It turned out that when I was in class, I felt that it was unnecessary to write documents and make requirements. However, now, I found that the original idea was really wrong, and it was a big mistake.
First, we must understand what the customer's needs are. Some time ago, I took over a project (an ERP system) from a senior. He helped the teacher do it, but he didn't want to do it, so he gave it to us. However, so far, I have not explained this project to the teacher, because I have not finished it, not because of lack of technical ability, we have completed almost every module now, but in the end, we found that it is difficult to walk down an overall process, and , because the requirements are not made by us, but by the teacher's graduate student. Recently, I found that the fields in the table are too different, so this project is dead in my hands (I don't know how to communicate with the teacher. explain it). However, here, I understand that if the project wants to start, the requirements must be done, and it must be done well, and you must fully understand what the customer wants to do and what they want, otherwise, you will make something that feels good to you. It's all a piece of junk.
Secondly, determine the customer's needs and do not change it (completely unchanged is impossible, because the only constant in project development is that the customer's needs have been changing, but basically it has to be determined). When I used to help a boss maintain the website (written in asp, I learned java), we took the things we made and let the boss read it three times and he still said that he was very satisfied, but when we finally wanted to deliver , but he said that it was not good, it did not conform to the habits of their industry, and there was no artistic atmosphere (I'll stop it), so he changed it again, almost rewriting the front desk. Therefore, it is very important to determine the needs of customers, otherwise, it may not be thankful. (Because it was introduced by a classmate and I was in school again, so there was no contract)
To sum up, learn from the above, before the OA system started this time, the requirements have been done for a long time, and due to the large number of departments, there are still several departments whose requirements are not clear. However, due to the progress problem, now start from One department starts doing it, and then, gets more people involved.
However, if there are many people, there will be many problems. You can't explain the requirements to everyone. Therefore, at this time, you need to know the importance of documents. Requirements should not only be kept in mind, but also written into documents—requirements specification. In this way, firstly, I will not forget it; secondly, I don’t have to tell everyone every day, anyone who doesn’t know can just read the document directly; thirdly, this also determines the goal of the project; fourthly: customer review However, we also reached an agreement with the customer (signed a contract).
Therefore, the requirements specification is very important, and it is the first.