Belongs to the class
2019 autumn Charms software engineering practices Z class (Fuzhou University)
Work requirements
Team Name
First, the sprint schedule
| date | plan management |
|---|---|
| 11.5 | Confirm discuss development plan |
| 11.6 | Implementation of the development, UI design architecture design |
| 11.7 | Background database design |
| 11.8 | Background Interface Design |
| 11.9 | Interface confirm, server, function development |
| 11.10 | Interface development, functional development |
| 11.11 | function test |
Second, questions and answers
FIG improvement ER, table design
emmmm, there are nine of ten questions about the PPT, and this is really the designer's mistakes, without taking into account projected onto the wall effect on the experience we produced apologize.
(Stuff after revision)
Third, thinking and summary
Due to time constraints, it may leave us to improve not a lot of time, so we intend to do more each day plan as much as possible, instead of the planned static.
Questions about functionality, empathy, because the staffing levels and the time factor, it is possible to develop incomplete problems, Please forgive us.
The task long way to go, the team is a great challenge, not just a test of technology, more of a test of mental and energy, but also do a groundwork for future work.
Fourth, the division of labor
| member | Division of work |
|---|---|
| Bristly | Front-end design, this project manager |
| Po Lin Zheng | Test, utility, UI design |
| Leach | Written primarily algorithm |
| Yuan Jiahong | Front-end development and design |
| Zhang Lei | Write back-end engineering |
| Li Cheng | Write back-end engineering |
Given the small team of staff, a person is likely to occur multiple roles of thing.
V. code specification
Our team decided to use Google code specifications
Sixth, the construction of the law read chapter 13-17
completed..