one. Team show
1. Team Name: SixSix Team
2. Team member: Zhao Yutian 201521043043 (captain);
Akira Shen 201521122001;
Lin Yanping 201521122002.
3. Team project description:
A four arithmetic program developed using java language to serve teachers, parents, and students for questioning, viewing, and questioning.
4. Team members' style:
*Zhao Yutian: I am very interested in the JAVA language. I hope that I can undertake development tasks in the team and contribute my own strength to the team project.
* Shen Yingzhao: Can learn with an open mind, accept other people's suggestions, good at C language, C++, interested in WEB, the software role I hope is testing, my declaration is to carefully determine success or failure.
*Lin Yanping: Humorous, loves to tell jokes, usually likes to paint, paint and play games. I prefer JAVA, and I hope that I will be a software tester or developer in the future, but I am also very happy to be a front-end. Recalling the past, the years are thick, just like the classmates are young, and they are in full bloom.
5. Group photo:
6. 
Team Features:
Although the strength is not enough, it will come together later. We are all very hard working beings.
two. team project
1. Topic:
Develop a web-based four arithmetic program, which is used to serve teachers, parents, and students for setting, viewing, and doing questions. The expected number of users is (100-200).
2. Software value:
1). It is convenient for teachers to collect and correct homework, and it is easier for students to know the content of homework clearly than by manually assigning homework.
2) It is convenient for students to collect and check their own wrong questions.
3). Compared with the original paper work, it is easy to mess up and it is not easy to check. It is easier and intuitive for parents to check their children's recent and previous homework results, as well as common problems.
3. The git repository for the team project:
https://gitee.com/mylaylay/sixsix_sizeyunsuan
3. Team plan:
| Week 10 _ |
1. Team team, team blog |
|
|
2. Team introduction, member presentation, role assignment, topic selection |
|
|
3. Develop team plans and rules for team contribution points |
| Week 11 _ |
1. Requirements specification, use case diagram, use case specification |
|
|
2. Prototyping, team members estimate task difficulty and learn necessary techniques |
|
|
3. The coding specification is completed, the platform environment is established, and the preliminary architecture is established |
| Week 12 _ |
1. Prototype improvement (show the prototype to target users and further understand the requirements) |
|
|
2. Architecture design, class diagram design |
|
|
3. Test plan |
| Week 13 _ |
1. Team project Alpha task assignment plan |
|
|
2. 7 days of Alpha agile sprints, 7 daily Scrum Meeting blogs + code submissions |
| Week 14 _ |
1. User feedback + test plan improvement |
|
|
2. Team Alpha stage personal summary |
|
|
3. Team Project Alpha Blog: Release Notes, Test Reports, Showcase Blog, Project Management |
| Week 15 _ |
1. Team Project Alpha Blog: Postmortem Analysis |