20 Group Sprint Plan（12.8）

[wrc123@]

The Link Your Class	https://bbs.csdn.net/topics/610142480
The Link Your Class	https://bbs.csdn.net/forums/MUEE308FZU202201
TeamName	20_KeyBorn
Video demo link	https://www.bilibili.com/video/BV1tK411X7RE
GitHub link	https://github.com/Aiorang/EE301_Lab3

1.Sprint

1.1 Plan

1.NPC interaction, including NPC actions, dialogues and corresponding scenarios

1.2 Table

Name	Completed Tasks	Duration of the task	Time remaining
YIWEI ZHONG(leader)	Code implementation required for interaction	12h	5h
ZHENKAI XIAO	Action production required for interaction	12h	6h
RUICHEN WU	Draw NPC pictures	10h	3h

1.3 Questions and Answers

Q:How to ensure the richness of npc actions

A:We designed the standby action, attack action and interaction action of NPC

Q:How to design the plot

A:By referring to other works

2. Stand-up Meeting

2.1 Meeting Content

We discussed the interaction design of NPC from two aspects: daily and combat. And designed a series of ups and downs of the plot.

2.2 Conference process

We had a meeting in the dormitory and discussed for about an hour.

3.Github

3.1Burnout Map

3.2 Github Related Code

4.Team Contribution

4.1 Table

Name	Contribution
YIWEI ZHONG(leader)	35%
ZHENKAI XIAO	35%
RUICHEN WU	30%

4.2 Contribution

1.Xiao ZhenKai
style: Be on the loose

skills:Proficiency with Unity,Scripting

programming interests:Embedded development

expected software engineering roles:Game programmer and part-time game planner

declaration：I live in caves

2.Zhong YiWei
style: be upright

skills:Writing，Pixel-style drawing，

programming interests:AI development

expected software engineering roles:Game planner part-time game artist

declaration：I'm going crazy

3.Wu RuiChen
style: Rich in character

skills:Draw

programming interests:Front-end development

expected software engineering roles:Game art

declaration：Live to be old and learn to be old

5.UML

LINK
Person in charge: Xiao ZhenKai
Description:Control all kinds of game objects.
Problems faced by this part:The data is complex and interleaved, the logic is difficult to separate from the data, and the scalability is poor in the later period.
Problems solved: Refactor code to separate data logic, increase interface to increase scalability, and facilitate subsequent development.
Attachment: (All UML diagrams of this part)