Teamwork 2 "requirements specifications"

I. Project Description

1. Content

Our team chose the topic of classic aircraft hit the java implementation.

2. expected amount of use

Classic original planes has many fans, we have to expand on it, it is now expected to amount to 2,000 users.

3. Requirements Specification

The basic functional requirements

• Players will control the aircraft A break through the barrier, the aircraft A can be moved to the front of the fire
• The easiest enemy can shoot forward, we can only move forward, more remains to be elite monster design
• Increasing difficulty level, but you can not not lead to clearance

Advanced Functional Requirements 

• Obstructions, and other airflow direction maps appear
• Optional difficulty, to facilitate Getting Started
• After the death of the enemy a chance to drop props, props will have to pick up a variety of effects

User-Oriented Analysis: as an improved version of the classic game, we pay tribute to the classic, partially reduced the original setting, on top of this to join our expanding.

Demand analysis: the smooth movement of shooting experience, and improve rules limit.

Technical requirements: the Java Swing interface making, java write enemy attack algorithm.

Second, the game features

• Truth
  • Launched several similar programs on small micro-channel, but also a team of college students choose the same project on the network
• Availability
  • This stand-alone game consumes few resources, configuration requirements are not high, the vast majority of players can run smoothly
• Value of
  • Classic tribute
• There are feelings
  • Relive childhood

Link cloud code: https://gitee.com/littlehui3/FeiJi

 Team project issues screenshots:

 

 

Third, the team plans

Original plan

Week 8	1. team team, team blog (✔)
	2. Team members show, role assignments, topics determined (✔)
	3. Develop team schedule, team contribution specified points (✔)
Week 9	1. Requirements Specification
	2. prototyping, the team estimated the difficulty of the task and learn the necessary technical
	3. coding specification is complete, the platform environment to build complete, the preliminary build architecture
Week 10	1. Improved prototype (a prototype to show to the target user, and to further understand the needs)
	2. architecture design, WBS, team members estimate the time required for each task
	3. Test Plan
Week 11	1. Alpha team project task assignment plan
	2.7 Alpha quick sprint consecutive days, seven daily Scrum Meeting blog Code submit +
Week 12	1. Improved user feedback + Test Plan
	2. Team Alpha stage personal summary
	3. Project Alpha Team blog: Release Notes, test reports, show blog, project management
Week 13	1. Project Alpha Team blog: post hoc analysis

After correction arrangement

Second, the team plans

Week 8	1. team team, team blog (✔)
	2. Team members show, role assignments, topics determined (✔)
	3. Develop team schedule, team contribution specified points (✔)
Week 9	1. Requirements Specification (✔)
	2. prototyping, the team estimated the difficulty of the task and learn the necessary technical (✔)
	3. coding specification is complete, the platform environment to build complete, the preliminary build architecture (✔)
Week 10	1. Improved prototype (a prototype to show to the target user, and to further understand the needs)
	2. architecture design, WBS, team members estimate the time required for each task
	3. Test Plan
Week 11	1. Alpha team project task assignment plan
	2.7 Alpha quick sprint consecutive days, seven daily Scrum Meeting blog Code submit +
Week 12	1. Improved user feedback + Test Plan
	2. Team Alpha stage personal summary
	3. Project Alpha Team blog: Release Notes, test reports, show blog, project management
Week 13	1. Project Alpha Team blog: post hoc analysis

Correction calculation method

Since the first 8 weeks and 9 weeks to give sufficient time for the system design and requirements analysis, team members this week are steadily according to plan, arrange to complete the original schedule given, no need this week on schedule to correct

Fourth, the division of work:

Guo Shaohua, Zhou Hong Ann: Game Design details

Lin Zhuohui: Implementing class aircraft and related methods, logic and other enemy attack

Liu Shigang, Wong Chi: The rest of the map interface to achieve and realize

Ye Jianting: Art

Guo Shaohua, Lin Zhuohui: Game Test

V. Completion:

Full: to discuss and draw general framework and needs analysis

Six members of thoughts:

Linzhuo Hui: This is the first time to participate in a team project, although not a deep understanding of the project, but with the help of other players, have a certain experience, we hope to eventually be able to complete this project brilliantly.

周泓安：作为PM，我对项目需求的理解要更为深刻一些，但在把需求分析转化为文字的时候，着实遇到了不少困难，好在我的队员们给予了我帮助，我们几番讨论过后才得出了最后的成果，这让我更清晰地认识到团队的强大，我们有信心把这个任务漂亮地完成。作为PM，我对项目需求的理解要更为深刻一些，但在把需求分析转化为文字的时候，着实遇到了不少困难，好在我的队员们给予了我帮助，我们几番讨论过后才得出了最后的成果，这让我更清晰地认识到团队的强大，我们有信心把这个任务漂亮地完成。

刘世刚：这个项目的需求分析其实就是把我们想做的东西用文字表达出来，还有仔细分析这些想法的可行性，为我们未来着手开发打下基础，同时将我们的想法统一起来。跟着团队一起思考，我认识到了自己想法的一些不足，也学习到别人的想法，特别是队长给了我们一个很好的方向。

王梓：这是我第一次参与系统计划开发,并且担当了需求分析这一工作,虽然工作中出现了许多差错,结果也不尽如人意。但是这次的经历给我以后的学习与工作带来了很好的经验,希望自己能再接再厉。

叶剑庭：这是第一次参加团队项目，在其他队员的帮助下，了解了项目的框架，学会了团队协作，做好了团队分工，希望这次的团队项目能够顺利完成。

郭绍华：第一周里我主要参与团队内的需求分析，功能分析讨论，自己在私下也查阅许多资料。通过这些，我也逐渐建立起对此次项目的认识与结构。队内的分工也以我们的讨论初步完成，希望接下来的阶段能顺利完成。