19 group - topic selection and requirement analysis report

激动的小马劈叉 2022-12-04 16:19:15

The Link Your Class	FZU-SE-EE308-2022秋社区-CSDN社区云
The Link of Requirement of This Assignment	LAB 3-1 Topic selection and requirement analysis of team project-CSDN社区
Group number	19
Group members	Xiao Ma （Leader）, Honghao Chen , Mingjun Cao , Xing Wang , Xuan Chen
My MU STU ID and FZU STU ID	20122187(MU)_832001215(FZU)
Leader's MU STU ID and FZU STU ID	20123990(MU)_832001206(FZU）

1.Team Gathering

1.1 Team members' introduction:

1.2 Description of team characteristics:

1.3 Logo of the team:

1.4 The first group photo of the team:

2. Start action

2.1 Project Introduction

2.2 Individual Contribution Points

2.3 Contribution Proportion

3. Drip Record

3.1Mind Map and Burnout Map

3.2 UML

3.2.1 Diagram of activity

3.2.2 Diagram of order

3.2.3 Use case diagram

3.2.4 Diagram of state

3.3 Learning progress bar

3.4 Experience

3.4.1 UML design tools

3.4.2 Difficulties and Solutions

4. Video clip

5. Conclusion

1.Team Gathering

1.1 Team members' introduction:

Xiao Ma (Leader)

Division of labor: Project Leader

Skills: Organized and self-motivated professional，Demand analysis，Software Testing

Interests: Working out, Playing badminton, Photoshop

Roles in the team: Orgenizer

Motto: When you feel sad and miserable, it is better to learn something. Learning will make you invincible forever.

Mingjun Cao

Division of labor: Front-end development

Skills: Demand analysis，Front-end development，Database Design

Interests: Playing table tennis, Cycling, Working on circuits

Roles in the team: Creator

Motto: No pains, no gains.

Honghao Chen

Division of labor: Back-end development

Skills: UI Design，Softare Testing，Back end development

Interests: Playing badminton, Running, Designing interfaces

Roles in the team: Pusher

Motto: Never give up.

Xing Wang

Division of labor: Software Tester

Skills: Software Development，Software Testing，Front-end development

Interests: Tell jokes, Draw pictures, Make mini-games

Roles in the team: Coordinator

Motto: Unity is strength.

Xuan Chen

Division of labor: UI design

Skills: UI Design，Back end development

Interests: Play basketball, Play games, Design web pages

Roles in the team: Mascot

Motto: Failure is always a part of life.

1.2 Description of team characteristics:

We have a small number of team members and adopt the mode of online and offline cooperation for team cooperation (because two team members are isolated outside the school). This kind of offline and online cooperation may be the characteristic of our team.

Core competitiveness:

The project of our group is about building fitness apps. Members of our group are very familiar with fitness and often use other sports apps, which will be our advantage.

1.3 Logo of the team:

1.4 The first group photo of the team:

2. Start action

2.1 Project Introduction

Exercise software dedicated to lowering the threshold of beginner fitness.

致力于降低初学者健身门槛的运动软件。

2.2 Individual Contribution Points

Our individual contribution points are judged according to how well each person completes the assigned task. The leader determines the tasks assigned to each person according to their characteristics and strengths.

We evaluate the degree of completion, and if the member completes the task, they get their share of the task. If a member does not complete a task and needs the help of another member, the share of the task will be given to the helper. Similarly, if a member assists someone else with a task. That member gets an additional share.

To be fair, everyone in our group had to rate all members (including ourselves). We then averaged each person's scores to determine the final grade.

2.3 Contribution Proportion

Name	Task Contents	Proportion
Xiao Ma (Leader)	Task report, idea design, ppt making and presentation, Software Development	120%
Mingjun Cao	Front-end development, Prototype of model and UML diagrams	100%
Honghao Chen	Back-end development, Video clip production	100%
Xing Wang	Software Testing	90%
Xuan Chen	UI design	90%
Total		500%

3. Drip Record

3.1Mind Map and Burnout Map

Mind Map

Burnout Map

3.2 UML

3.2.1 Diagram of activity

3.2.2 Diagram of order

3.2.3 Use case diagram

3.2.4 Diagram of state

3.3 Learning progress bar

Week N	New code (line)	Cumulative code (line)	Time spent on learning this week (hours)	Cumulative time spent on learning (hours)	Important growth
1	600	600	10	10	Determine the project theme, survey the target population, determine the user needs, and prepare the proposal report. Familiar with Android studio,java and javascript.
2	1800	2400	18	28	Build the software framework, design the UI interface, and complete the SRS report, defense slides and presentation videos. Start developing the back end and front end.

3.4 Experience

3.4.1 UML design tools

The UML tool of choice for our team is edraw(亿图）. The main reason for choosing it is that it is free and has abundant UML diagram templates. These templates are functional and easy to operate for the first time users, which allows us to get started faster and complete the UML diagram more efficiently.

3.4.2 Difficulties and Solutions

Difficulties:

1. We had very little team development experience.

2. We lack experience in making UML diagrams.

3. We have team members who are isolated off campus, unable to collaborate offline.

Solutions:

1. We have held many team meetings, and defined the division of tasks for our members, so that we have a better understanding of cooperation.

2. We used a simpler uml design tool to make it easy for us to use.

3. We adopt the method of online meeting and online collaboration, and use inkknife and other tools for collaboration.

4. Video clip

https://www.bilibili.com/video/BV1cP411M7HY/?vd_source=8762105a81a481d8fb6a3d2e72ed0088

5. Conclusion

This experiment is the first time for us to do a team project, and we all lack the experience of team cooperation and some knowledge of project development. As a result, our project is not perfect. If we have more time to finish this project, I believe we can do better. Including in the design and functional implementation, can be richer and more perfect. With the experien-ce of this cooperation, we believe we can have a better understanding and do better in the following cooperation.