[Soft Industry Top Understanding Group] 0416 8th meeting

Regular meeting time: 12:30, April 16, Host: Guo Jun

Time of next regular meeting: 12:30, April 17, Moderator: Du Bowei

1. Work report

personnel	Completed the task yesterday	Tasks to be completed tomorrow
Qiao Xihua	Network experiment, rest	Learn and make empty classroom query front-end interaction
Zhang Yixuan	Learn the front-end and back-end interaction of the login page https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Frontend/issues/18	Write the front-end and back-end interactions of the login page
Shan Yanbo	Completed the page design of the course center https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Frontend/issues/7	Complete the interaction between the course center and the backend
Hu Binbin	Complete encryption and decryption functions, interfaces, and return format https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/45	Make front-end or crawler interactions
Li Jiacheng	Optimize database design and create a database modification interface for crawlers to call https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/22	Make front-end or crawler interactions
Du Bowei	Crawl Course Center DDL https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/9	Integrate the three existing functions
Guo Jun	Submit meeting records and complete the Alpha-1 stage acceptance https://github.com/SE2020-TopUnderstanding/BUAA-Campus-Tools-Backend/issues/18	Continue to follow up the project

Second, the meeting screenshot

3. Difficulties encountered at work

• Alpha-1 stage acceptance

  There are too few scoring items available for reference at this stage, and bugs and dates that are closely related to the scoring items cannot be tested at this stage. Therefore, it is considered to score at the end of the Alpha stage, which is only for acceptance. In the same way, in order to maintain the consistency of scoring with everyone, the evaluation of PM has also been postponed to the end of the Alpha stage.

  front end:

  According to the burndown chart, the front-end progress has not reached half. Although there is no time deduction item in the Alpha-1 stage, we still hope that the front end will speed up the progress. If you really have difficulties, you must communicate in time and try not to delay the progress.

  In terms of code, I have read all the PRs on the front end. Zhang Yixuan's code contains comments on lines, while Qiao Xihua and Shan Yanbo have no comments. Of course, as a front-end framework, the importance of comments is not necessarily as significant as the back-end, and there are not many places where comments can be written, mainly on page design.

  In addition, I am not familiar with Java's Android programming specifications, and it is inconvenient to add comments here. The acceptance results will be evaluated mainly in terms of function and experience. Personally think that the comments for each line are not necessary, but the lack of comments is not very good. It is recommended to write simple comments by component , and make necessary comments on the data structures set in the code .

  rear end:

  The naming of the app is not reasonable interface, interface2this naming is no reference value, there is no order between the two APP, recommended learning named below.

  Wrongly write "DDL" as "dll" and modify it in time.

  But need to pay attention: 1. According to Python's lint rules, comments should be written below the line of the function / class definition, such as:

  class query_ddl(APIView):
  	"""查询DDL页面
  	"""
  	def get(self, request, format=None):
          """GET方法，获取ddl
          参数：student_id - 学生学号
          返回值：content - ddl信息
          """
          foo()
  

  2. It is not necessary to write such long and detailed comments. These detailed rule definitions should be written in the interface documentation , because the front-end developers who need to call these messages will not read your source code, but the documentation. I hope that the backend and the crawler can set the interface document to an important issue to complete.

  Multi-line comments suggest using triple quotes """as delimiters.

  And, the error handling information is defined. Although the status code does not conform to the specifications, the framework is there, and the so-called robustness is also stronger.

  The back-end should discuss with each other a unified error handling method, and can even wrap the error type and return information as a utils.py in the back-end.

  reptile:

  The overall quality of Du Bowei's code is relatively high. The OOP mode is used to program the crawler and the comments are in place, which is worth advocating.

  At present, it is unclear whether this code has bugs, reusability, and performance issues. You need to wait for the interaction with the backend to be completely built before you can evaluate it.

• Encryption and decryption: The encryption algorithm uses an easy-to-implement algorithm to ensure that the front end can achieve encryption.

• The database is tested using a local database to prevent migration problems.

4. Burndown chart

front end:

rear end:

5. Code or document check-in records

front end:

rear end:

reptile: