Tear-resistant Team alpha pre-release spoiler

Preface

Qi classmate finally in this Monday 80% blood volume Resurrection, praise, gratifying to celebrate. The first thing after the resurrection, work, work, work. Because of the effort, the yellow collar is the driving force of the shirt. Ha ha. Another off-topic: tear-resistant Regiment vice captain yesterday in the EI, gratifying to congratulate.

Body

In Monday, I began to work with my teammates to prepare the alpha release of the tear-resistant team, and we were serious because the software was produced to be trustworthy. (I'm proud again). In the afternoon of Monday, I finished two technical prototypes: 1. The phone client listens to the server "start answering" Password 2. The server-side listens for a "I Rob" request from the client. After finishing these two technical prototypes, I probably have a few, alpha release around the corner. The implementation of these two modules was my greatest concern. After two prototypes, I was programmed in Monday afternoon with the vice-captain Lin Xiao-tie, and finished the client UI that the Alpha release was going to use.

In accordance with our expectations, alpha before release we want to complete the Web Part development to the Captain Rui Brother (trustworthy). In the evening of Tuesday, we had a standing meeting. We integrate Web Engineering, Android client engineering, server monitoring engineering, make a responder executable version, if these days do not update, at least as an Alpha release content to display. (Two days of scattered time, I am surprised that we can make this thing, of course, let ourselves surprised not only the human potential, but also to the small yellow shirt efforts of the will)

in the previous small friends standing meeting report, the common problem is the lack of display, Yang teacher also left a message to urge. In this blog, QI students will be shown, but also is Alpha before the release of a spoiler. The captain was absent that day, and he was expected to show up on the lieutenant. Of course I can guess, there will be a Groove UI, no way, my aesthetic innate poor. Even wearing clothes depends on female ticket guidance.

My impression is that the scenario should look like this:

Two users to take the answer for example, they took their own mobile phone to the landing, respectively, called Qi and Chu. Figure one shows the effect:

Figure A

Figure II

After landing, two shows. Answer the button for red can not press, waiting for the server to start answering the instructions.

Next, the host on the Web click on the Start Answering button, three. Next, two responder's phone on the answering button turned green, you can answer.

Might

Figure Four

This is called Qi of the responder first press the button, there is a figure five, figure five is the status of the responder's mobile phone answer button Red, can not press. The second set of Web-side (the user qi) discoloration, the second group quickly grabbed.

Figure Five

Figure Six

After the end of the problem, the host points to the next question, the effect of Figure six appears. And then repeat the host point to start answering the question--------the answer to the question----the score (Alpha may not finish before release, a semester of work, we always have to have a plan to complete.) ), the next question. Figure Seven is "Chu" This user grabbed "bright elder brother has a woman ticket?" "This problem.

Figure Seven

In general, the alpha release of the spoiler is here. At the very least, our team is pleased that we've got the core functionality of the product we're going to do, even though we can't do all the things we want to do in a week's time (piecemeal because there are other jobs), but it's always a good thing to be able to work out an executable program that's never better than a pie.

The project was submitted to:

Https://git.coding.net/zhengrui0452/QiangDaQi.git

The following is attached to the classmate's PSP:

Job	Type	Date	Start	End	Total
Client Listener Prototype	Coding	2016.3.28	13:30	14:45	75
Service-side response to answering the prototype	Coding	2016.3.28	15:00	16:30	90
Android Client UI Implementation	Pair programming (paired with two people in the forest)	2016.3.28	17:00	18:00	60
Develop responder client and server listener	Coding	2016.3.29	15:00	16:00	60
Integrated Responder all projects	Pair programming (tear-resistant group of four pairs)	2016.3.29	20:25	8:55	30

Work table

	Number of lines of code	Blog words	Knowledge points
Week Four	590	1520	Alpha release Pair programming Standing meeting

Tear-resistant Team alpha pre-release spoiler