# This blog has not finished
1. Overall schedule (2 points)
| deadline | task |
|---|---|
| 11.01 | Determining front and rear ends negotiate the interface, the UI complete home, building frame front and rear ends to complete the project, task allocation and determination module |
| 11.15 | The front end of the body portion is completed, the rear end of the docking interfaces |
| 11.18 | Test, modify, improve performance, check the code, release Alpha version |
| 11.23 | Project to improve user feedback + + test plans to improve |
| 12.1 | The new version of the module were written based on feedback and demand, Beta version released |
| 12.4 | The official version of the complete user's manual + |
2. Team division (5 points)
alpha version needs to be done
Note: alpha release schedule in mid to late November
Detailed division of labor and TODO list
- Front section
- rear end
- Product manager
Burndown
3. FIG mind (2 minutes)
4. The assessment team contribution ratio (2 points)
Described as writing workflow requirements specification, the division of labor crew, crew workload ratio
| Crew | percentage | Original mandate | ||
|---|---|---|---|---|
| Su Wei Huan | ||||
| Wang Qi Hong | ||||
| Chen Wenbin | ||||
| Gong Lin Yang | ||||
| Lin Wentao | ||||
| Lin Honghai | ||||
| Dengzhi Xiong | ||||
| Lin Xiaotang | ||||
| Yang Shijie | ||||
| Zhang overseas |
Table 5. Design Review (1 min)
6. UML (found partially responsible for their own part of the UML do exercises) (10 points)
Will do figure:
Use Case Diagram
Class Diagram
Activity Diagram
State diagram
Entity Relationship Diagram
Bringing together members of the results of the following format:
part1
described here is which part of the system?
This part to face any kind of problem?
The following design which problems?
Annex: UML FIG
Part2
described herein which part of the system?
This part to face any kind of problem?
The following design which problems?
Annex: UML FIG
Part3
...
7. The tool of choice (we can share experiences, recommend each other, talk about why choose this tool) (2 points)
Wait asked Wentao and Tang small
8. Evaluation of the use of the tool (2 minutes)
9. summary reply (9 points)
This group of determined defense field score
Remove the highest score, lowest score, averaging points (2 decimal places)
Answer questions of other teams in this group
Answer every little point, the score deduct 5% deduction have been exhausted
Modify needs analysis report
According to the observations and recommendations put forward in defense of other groups to revise and improve this group needs analysis, and marked modify place
10. "Requirements Specification" (1 min)
The first group of 02 - needs analysis
Difficulties encountered and solutions 11. (2 points)
| Description difficult | What did try | Is resolved | What harvest |
|---|---|---|---|
12. PSP (1 min)
| PSP2.1 | Personal Software Process Stages | Estimated time consuming (minutes) | The actual time-consuming (minutes) |
|---|---|---|---|
| Planning | plan | ||
| · Estimate | • Estimate how much time this task requires | ||
| Development | Develop | ||
| · Analysis | · Needs analysis (including learning new technologies) | ||
| · Design Spec | Generate design documents | ||
| · Design Review | · Design Review (and his colleagues reviewed the design documents) | ||
| · Coding Standard | · Code specifications (development of appropriate norms for the current development) | ||
| · Design | · Specific design | ||
| · Coding | · Specific coding | ||
| · Code Review | · Code Review | ||
| · Test | · Test (self-test, modify the code, submit modifications) | ||
| Reporting | report | ||
| · Test Report | · testing report | ||
| · Size Measurement | · Computing workload | ||
| · Postmortem & Process Improvement Plan | · Hindsight, and propose process improvement plan | ||
| total |