"Tear-resistant" team first discussion-"Responder" demand analysis

Team name: "Tear resistant"

Team members: Zigaliang, Liu Weixian, Cheng Lin, Zheng

Project name: "Responder" (need to improve)

First time Discussion

Time: 20160316

Location: the Software

Personnel: All

Content: Demand Analysis

Main content:

This time hope to develop a mobile phone software, with the function of the responder, the main application in the debate game, knowledge competition and other needs to answer the game. The future through evolution, can also be used to rob red envelopes, Rob Girlfriend, Rob Money, Rob Banks and other occasions.

First, the role:

The following three types of roles are identified in the initial responder:

1. The responder (the average user in the picture)

2. Moderator

3. System administrator

Second, for different users, determine the main functions have the following:

1. Responder:

Login

Read the question

Answer

Bomb screen

Check the number of clicks on the answer after you click on the list of all the respondents

See the results of your quiz points

Quiz Countdown

2. Moderator:

Read the question

Start answering.

Show Top n clicks on the responder

Scoring for the right person

3. Administrator:

Search and delete of topics

Management of the responder's points

	peripheral function	Killer function
Necessary requirements	Caller Login Answer Start answering. The moderator scored the answer to the responder. Administrator on the topic of additions and deletions to change Administrator's management of the responder's points	Bomb screen
Ancillary requirements	The answer to the question The responder looks at his answer to the score. Moderator Read the question The host shows the top n the first responder	The answer to the answer after clicking on the answer to their own in all the responder's click Time Ranking Quiz Countdown

Thirdly, according to the difficulty of implementation, the team decided to make the following prototypes:

1. The prototype of the phone-answering start

Solution: Use the Android monitoring service

2. The prototype of the preemptive order

Solution: Tentatively accurate to microseconds, based on server received phone request time

3. Phone drop, re-access the system

Solution: Log back in

Next week to do project design, welcome team members to improve.

"Tear-resistant" team first discussion-"Responder" demand analysis