[Teams can Ai Pipi - Forewarned is forearmed]

1.Github Address:

     https://github.com/ShiKeing/repository

 

2. Project summary reflect on the problem:

  • GitHub use unskilled, members of the difficulties uploading the code, usually issue submitted less. We should actively learn to use github to ensure practices. Skilled members actively share experiences, help each other.
  • Less exchange between team members, the low degree of completion of the project. Leader failed to fulfill their responsibility of coordinating team members, project development is slow, we are not enthusiastic, each module progress is not uniform, low development efficiency. In a later development, it should be more refined development goals, set deadline for each development task, and more mutual supervision, strengthen communication between each other.
  • Members of the limited capacity, most of the functionality is not implemented, the program several times to delete the middle, slow down the progress. We need to learn relevant knowledge of java program development / mysql of applications. 

 

 

 

 

 

 

 

 

3. Team Division:

  • Division of labor is not clear, but roughly divided into modules, there is no clear and detailed division of labor, resulting in the project development process, task overlap.                                           Improvement: The project needs a clear beginning, determine the package you want, follow a unified class, before the decision to develop a unified architecture, meticulous division of labor.
  • After the division of labor is less communication between members, project problems can not be timely feedback to improve.                                                                             Improvement: everyone in the realization of a portion of the function, to share, to communicate with everyone to do more to discuss, discover and solve problems.

 

 

 

 

 

4. Code specifications:

  • Name: variable, class unified name English name, hump nomenclature. Is not an abbreviation, do not be afraid long.
  • Format specification: Tab key 4 was replaced with spaces. Do not use a tab-delimited indent control. (Different systems, different performance style editor)   
  • Parenthesis: Each "{" and "}" are on a separate line. That is not to multi-branch-line statement on a single line.
  • Notes: clear, concise best. Complex function annotation should be placed first, we can use different display styles to represent different parts of the program.
  • css, js statement after the code plus ";" punctuation. js} before the last paragraph, may be added from time to add a semicolon.
  • Unified coding: UTF-8, plus all the file header are encoded statement, css, html, jsp
  • The establishment of a unified database with character set: utf8, the default collation: utf8_general_ci. Each field is increased Remarks table, comment table use in self-energizing ID.

Guess you like

Origin www.cnblogs.com/wxmteamblog/p/12080936.html