Since July, I have been busy writing technical documents for various fund projects and technical documents for national 863 projects. Although I am tired, I have gained a lot. The biggest gains are in two aspects:
- By writing technical documents for software platforms and documents, I have the time and opportunity to rethink the system architecture, features, and possible future development directions of our platforms and products, by taking advantage of this opportunity, we have basically completed a systematic description of the platform and products. In the future, we will apply for funds or communicate with customers, and there will be ready-made materials.
- By writing 863 project technical documents, I learned the basic framework and ideas for writing such documents from instructor Zeng, and realized that there are some rules to write these documents, with these frameworks and ideas, writing similar documents or pursuing a doctorate degree in the future will have a deeper Foundation.
The basic framework for writing such a type of technical document 863 consists of four main parts:
- The first is to briefly introduce the project situation, including the purpose and significance of the project (why does the country spend money to support your project and what practical value it has, which is briefly described here ), briefly describe the content of the project to be studied and the final goals to be achieved;
- The second point is to describe the development of the related technologies involved in the project at home and abroad, because it has already been explained that the implementation of this project is of great significance, here, I would like to fully understand whether other people at home and abroad have studied the related technologies of the project and how the research is going. Here, we need to make full reference to domestic and foreign documents. On the one hand, we need to understand the current technical situation (it must be that the current technical solution is not enough to meet the requirements of the project; otherwise, what do you need to study ?), On the other hand, we need to understand the development trend of technology. This is important at 01:10. If researchers at home and abroad do not take the project-related technologies as the future development trend, what will they do for you to study? Another point is that you need to query the patents of related technologies. If someone else applies for a patent on these technologies, there is no need to do it. However, the patent search is not to say that there is no such thing, if there is no relevant patent, it will be explained from the perspective that the relevant technology is not the current development trend.
- The third point is to propose the main research content of the project, that is, what problems can be solved by your project. It is also worth noting that I have made a mistake, that is, when describing the research content, do not describe the relevant technology too detailed, this will make reviewers think that your technology has been implemented and what else should you do. Therefore, we need to first describe the overall system structure of the project, and present the various research contents as much as possible on the diagram, this general structure is used to give reviewers a general understanding of the system, and then gradually describe the research content. The second step is to describe the content of the study. In fact, it is to propose one or more solutions to the problems encountered in each project, mostly using descriptive languages, with less specific technical details involved.
- The fourth point is to propose the solution to this project based on the research content. Use as much ink as possible to describe the abstract technical level, such as the overall security policy and system architecture. Try to make people feel that the technical level is high, and the specific technical details are rarely described, because we are not applying for a fund.
When writing 863 documents, the first three points are the most important, because the core content of a project can be fully reflected in these three parts, therefore, the overall thinking of the first three parts must be clear, and the content we want to study and its significance must be described with the least amount of ink. We must be able to increase the technical level of the project, if the reviewers can feel this, the project declaration will be successful for more than half. The fourth part of the description is relatively detailed, and reviewers generally do not read it carefully.
