## [small blessing bbs- Forewarned is forearmed]
1. sprint time schedule (seven-day sprint time, arrangements between 2019-11-3--2019-11-14)
| Sprint time | plan management |
|---|---|
| 2019.11.6 | Meetings, arrange concrete work |
| 2019.11.7 | UI reconstruction completed |
| 2019.11.8 | The front section of the page delivered to the back-end, back-end start to complete some functions |
| 2019.11.9 | Two front end interface 17 is completed |
| 2019.11.10 | UI improvements, improved front page, the back-end part of the functional test given to UI |
| 2019.11.11 | Most of the back-end to complete the function operation, front-end UI to complete most of the functionality test |
| 2019.11.12 | Completed access database operation |
| 2019.11.13 | Each test, analyze, to fill a vacancy trapping |
| 2019.11.14 | Finishing work |
2. The answer to the last working students, teaching assistants raised the issue of
Q: Is the idea to add a reprint function?
A: reprint function intended to be reproduced plus circle of friends, the binding of Api micro-channel can be achieved, if there is spare capacity will do
Q: how other schools achieve user authentication information?
A: temporary users did not consider other schools, mainly for the university's
Q: use of frameworks is not clear at this stage?
A: VUE stage is intended to use the framework to accomplish this APP, making a uniapp, multi-terminal can be published at the same time
3. If you need to consummate class diagram or table structures, which are rendered by the chart, please paste together to essays
4. thinking and summary for the previous lack of local jobs
Panel members last previous job completion time of all the Capitol is complete, we expect the group to discuss the job done ahead of time, refused to procrastination!
The need to improve the team division (for the previous lack of a need to strengthen and improve local teamwork and division of labor)
Team relatively small number of meetings, relations within the group of students is not very harmonious little rusty. After the start of the sprint team, will meet to discuss every day at a fixed location, strengthen teamwork, although the division of labor is very clear, but will still help each other.
6. team code standards
Team code standards will be the first meeting, put on the table on Wednesday (11.6) team work, discussion on the specifics.
① named Style:
code name can not start with an underscore or a dollar sign, can not end with an underscore, or dollar sign. Code named prohibited use Pinyin mixed with English, but does not allow direct use of Chinese fashion. Use UpperCamelCase style class name. Method name, parameter name, member variables, local variables are consistent use lowerCamelCase style, you must comply with the hump form. Constant naming all uppercase, separated by an underscore between words, semantic and strive to complete
the whole clear, not too long name. Abstract class name or the beginning of the use Abstract Base; exception class named using ends Exception; test class named after the name of its class to be tested beginning to the end of the Test. Unified lowercase package name, point
separator between the character and there is only one natural language of English words. Eliminate completely non-standard abbreviations, meaning I do not know to avoid looking text.
② code format:
with four spaces to indent, prohibit the use of tab characters. all must be a space between the if / for / while / switch / do and other reserved words and brackets. Use braces conventions. If it is empty, succinctly written within braces {}, do not need wrapping
③ statute NOTE:
possible for others to read the comments given.
7. Read the chapter 13-17 of the law building
Chapter XIII talking about software testing, including functional testing and non-functional testing, test methods unit testing, code coverage, build verification testing, acceptance testing test "exploratory", and regression testing scenarios, integration, system testing, partner testing, performance testing, stress testing, internal / external public testing, usability testing
Chapter XIV talking about the quality of quality + quality assurance software engineering, software quality program =
Chapter XV talking about the stability and release phases of the software, and stable in the early stages, the team simply decided to repair those defects, and team members to modify and test the code, after the release stage, the need to review the process and learned what
The 16 chapters talking about the IT industry in innovation, a good idea will bring a great innovation, will be allowed to become a pioneer in innovation will bring a winning machine
Chapter XVII talking about the people, performance and work ethic, teamwork is essential, then running from bud to regulate, to create, in order to succeed, the software engineer must have their own professional ethics