Let's assume that our tank team is moving forward-demand Improvement & System Design

Requirement and prototype Improvement

During the class discussion in the demand manual last week, the instructor raised a question about the design of the game's user interface.

After discussion by the Group members, our ideas are as follows: after entering the game, the game name is followed by three buttons "Start game", "item Collection", and "exit game", with a suitable background image.

In addition, we have defined the game level selection rules. after starting the game, we will enter the level selection interface. At the beginning, the game only has one level. Only after customs clearance will the next level selection button appear, players can choose a new level or a level that has been previously cleared to enter the game. Random items picked up by players in the game will be viewed in "item Collection", and certain levels will be enabled only when the collection of items reaches a certain value, in order to increase the playability of the game. The game clearance method is to eliminate enemy tanks for victory. Different levels can be used to improve the difficulty through scenario arrangement and tank volume damage.

System Design

Implementation of tank movement: Write the listening keyboard response time in the tank class, and the listening upper and lower sides will have the tank X, and the Y axis will change accordingly to draw a tank.

Tank attack: after detecting the attack command through the keyboard listening, generate a bullet class in the direction of the barrel of the tank position, so that the bullet class can always draw a bullet.

Collision: the collision of tanks, walls, and bullets. When a tank bullet is drawn, there will be a collision detection method. Methods in the tank, wall, and missile Classes define their own scopes. Each collision method has its own results. For example, a collision between a bullet and a tank may result in an explosion.

Prop pick-up: blood bag or equipment pick-up is also a collision method.

Alpha task allocation plan product to be implemented

Function	Estimated time/h	Task Arrangement member
Tank Class	10	Zhong qiyong
Wall class	10	Zhong qiyong
Missile class	10	Min Zhuo 'an
Equip class	10	Min Zhuo 'an
Main class	10	Chen weihao
Before entering the game	10	Chen weihao

 

 

Test Plan

After implementation of each class, you can also test whether the corresponding object can be drawn. when combined with other classes, you can test the game when the game is completed, and check whether the drawn object is correct.

We tentatively set each test time to 1 hour. After each modification, we need to re-test it. The responsible person of the corresponding function will test it on his own. The final finished product is tested by all members in two hours.

Schedule

Time	Task progress
WEEK 1	1. Team team, team blog (? Completed)
	2. Team Introduction, member presentation, role assignment, and selection confirmation (? Completed)
	3. Set the team plan and team contribution score (? Completed)
WEEK 1	1. Requirement specification (? Completed)
	2. In prototype design, the team members estimate the Task Difficulty and learn the necessary technologies (? Completed)
	3. Complete coding specifications, complete platform environment setup, and preliminary architecture setup (? Completed)
WEEK 1	1. Prototype improvement (presents prototype to target users and further understands requirements) (? Completed)
	2. architecture design, WBS, and team members estimate the time required for their respective tasks (? Completed)
	3. Test Plan (? Completed)
WEEK 1	1. Team Project Alpha task allocation plan
	2. 6 consecutive Alpha agile sprints, 7 daily scrum meeting blogs + code submissions
WEEK 1	1. user feedback + test plan Improvement
	2. Personal Summary of Team Alpha stage
	3. Team Project Alpha blog: Release description, test report, display blog, Project Management
WEEK 1	1. Team Project Alpha blog: post-event analysis
	2. One person in each team must leave and find the next one to accept the team. The team posted a blog to announce the success of team departure and Acceptance

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Team members

Zhong Qianyi, Yan zhuo'an, Chen weihao

Let's assume that our tank team is moving forward-demand Improvement & System Design