Soft [practice] Beta version of your work

Links section

Team name: girls team

Leader blog: blog links

Job blog: blog links

First, vision and goals

1, our software to solve the problem? Whether clearly defined? Is there a clear description of the typical user and a typical scenario?

• Our software solutions question is: to help users using scientific methods to develop good habits , sent when necessary to give them some habits like small reminder to help users improve the life happiness. At the same time, be able to pet companionship way to help users better fulfill their own definition of the mission journey and mission systems.
• It has been defined very clearly. (For details, see needs analysis PDF extraction code: X24E )
• Typical users are: the majority of the younger generation (12 years old -32 years old) population . (In the needs analysis report PDF extraction code: x24e already described)
• A typical scenario: Fu students - Chen . (In the needs analysis report PDF extraction code: x24e already described)

2, we reached the goal yet (function originally planned to do a few? As originally planned delivery time delivered what? Originally planned to reach the number of users reached it?)?

• Not yet fully achieve the goal, the original plan have been completed six functions: Log in Register, add punch task, and the "I" talk show task list, journey classification, weather remind push. The remaining task will be completed in Beta version.
• Complete the delivery in Alpha version specified time. And Alpha versions of classroom display.
• It did not make a clear definition of the number of users in the original plan. Users also need to promote the acquisition amount after the completion of the Beta version.

3, number of users, users in advance of the expected acceptance of what is consistent and important functions we? Our goal from the closer it?

• Yet to promote, so no amount of users. Away from the goal one step closer.

4. What are the lessons? If history all over again, what would we do to improve?

• Should advance the entire development process of the project and the problems you might encounter predict, plan ahead, and to develop in advance of each stage of the detailed figures and delivery time. If you do it all again , we will strictly required to complete the project in accordance with the specified delivery time, and task scheduling, where appropriate, adjusted according to the situation each time to complete, and will set clear goals late good amount of users in advance.

Second, the plan

1, if there is enough time to do the plan?

• Plan is there, but due to a variety of force majeure reasons, the final implementation deviate

2, the team at the planning stage is how to resolve the disagreement colleagues for planned?

• Communication is the most powerful way, we all try to find a satisfactory solution

3, the original plan if you work finally done? If you have not done, and why?

• The original plan in consecutive liver for a few nights basically completed after all; but in the front and rear end butt on there are still many problems have not been resolved, because in the integration project has no time.

4, you do not find some hindsight did not need or do not count for much?

• In the functional design a little too on the complex , dug ourselves a lot of pit
• On the back-end framework gone too detour

5, whether each task are clearly defined and measurable deliverables?

• No, because the whole program is not very smooth conduct, so basically all standard field communication , then adjust

6, the whole process if the project were carried out according to plan, the project what had happened? What are the risks was not estimated, why not estimated?

• The whole process did not completely according to plan
• In the course of the project, due to lack of experience , stepped on a lot of pits in the project docking, there are many problems
• The risk is that if the user behavior analysis , to achieve this because of the difficulty a bit beyond expected

7, there is no buffer left in the plan, the buffer role it?

• They are: Break Break Break! ! !
• After the break role is more of a fresh liver!

8, future plans will do what changes? (Eg: buffer defined, overtime)

• Plan is to continue the liver! , Usually learn their part responsible in doing the project on people with liver
• The rest on the rest of the overtime on overtime, nothing is staying up late can not be solved !

9, What have we learned? If history all over again, what would we do to improve?

• I learned a lot, deployment server, back-end structures, interface design and implementation, database structures, etc.
• If you do it all again, first of all we must not give themselves dug so many pit up! , Second is to strengthen the task of analysis , study well in advance to use the knowledge, estimated good job of difficulty , rather than to modify the final

Third, resources

1, we have enough resources to fulfill the tasks it?

• We have sufficient resources to complete the task. We have a group of people have come into contact with the front end of back-end algorithms, and there are artists, talent, we all get along well with both sweet.

2, time and other resources required for each task is how to estimate how accuracy?

• The time required tasks in accordance with the experience of the past development point of view, and with the progress of the project development process to be constantly modified, the accuracy is not accurate, there are a number of bug not previously encountered, leading to cost a lot time, so in some places there is no timely completion of the alpha stage.

3, the test of time, manpower and software / hardware resources are sufficient? For those without programming resources (graphic design / copy) whether underestimate the difficulty?

• Test of time, manpower and software / hardware resources are not enough.
• Since the back end there are some problems, so the first time back-end interaction of a number of problems, leading to flash back and other problems, there have been many test questions.
• We did not underestimate the difficulty. We do have a special group of artists and staff specialize in copywriting, they can complete the task within the specified time, and is faster and better! ( Simply too praised! Team's efficiency and aesthetic level they have been pushed up! )

4. Have you ever felt that you can do to let others do the (more efficient)?

• I think I will do things that make Android Studio students to do, then, it is entirely possible! There may even do better than me ( especially the aesthetic and detail ) "

5. What are the lessons? If history all over again, what would we do to improve?

• We should at the time of allocation of tasks, try to assign tasks to everyone, and let each task much detail as possible, does not appear that some people do not understand the task, in the case of wandering in situ, resulting in the barrel theory, projects overall progress is reduced. And we should be clear that the difficulty of the task, assign the appropriate event to the task, so that time and resources to maximize!

Fourth, change management

1, each of the relevant employees are aware of the news in time to change?

• Yes, whenever there is a change and we will inform changes in the details of all the members of the group Li Aite.

2, we have adopted a way of determining what is "delayed" and "must be achieved" feature?

• app's main functions, ie functions that must be implemented, and more details of features and extensions can be postponed.

3, the project's export conditions (Exit Criteria - what "done") have a clear definition of it?

• There, the basic functions of a complete project, logic intact, no test bug.

4, for a possible change whether contingency plans?

• Most energy, most of the change is within the controllable range.

5, whether employees can work unexpected efficiently handle requests?

• In most cases able, before and after the small part of the case at the end coordination and mutual assistance, and ultimately can handle.

6, What have we learned? If history all over again, what would we do to improve?

• Learn teamwork and coordination of front and rear ends. If history all over again, we are in the very beginning the project will be a good frame, front and rear end at the same time.

Fifth, the design / implementation

1, designed to operate at what time and by whom done? Is the right time, right people?

• Prototyping team to discuss the first draft by the Ya-Qin Hui Cho drawn. As the team discussed the finalization of a rougher, after Avon and Yu Wai prototype design has been modified and refined. These efforts are conducting needs analysis report when completed (a team working on). During development of the project and the prototype has been adjusted. Prototyping is involved in basic personnel front-end implementation, so iterative prototyping will be updated based on the idea of ​​front-end staff and achievement. Therefore, time and personnel are more appropriate.
• The main database and interface design done by grace, and assigned to Jun Xi, Gimhae refinement. Three students are all back-end implementation of the students, before the start of the back-end work to complete the design and to determine a front-end design students, and staff time interfaces are appropriate.

2, the design work have not encountered ambiguous situations, how the team is resolved?

• There encounter ambiguous situations, there are differences between the logical group members in the front page jump, while the back-end database design group in case there is some controversy.
• The front group after discussion, decided to adjust the page in a concise, clear and based, to determine the final version. Member behind the group is also determined by the exchange and discussion of the design of the database, and a clear division of labor.

3, the team whether using unit testing (unit test), test-driven development (TDD), UML, or other tools to help design and implement? These tools are effective?

• Unit testing is done in the Android Studio, Android Studio test environment for developing Android-friendly and convenient.

4, UML documentation beginning of the project and compare the current state What is the difference? How these differences are produced? Do you want to update UML documents?

• The difference is quite large. Because it was discovered the presence of some of the details obscure the original document in the project development process, it needs to be updated to better assist development.

5, Bug What is the function of generating the most, and why? After publication found out what is important Bug? Why are we in the design / development when there is no thought of these cases?

• During development, many functions have had a Bug, produce the most functional bug push messages should be realized, because the team is for most people just getting started in this course language and system environments. Once published, found that there Bug messaging and information transfer between the front and rear ends in the front-end activities, there is the problem of information storage, which is due to the development team members are not familiar with the concept for the front and rear ends of the interaction is less clear.

6, code review (Code Review) is how to proceed, whether the strict implementation of the code specifications?

• Because of the time we do not have reason code review. However, before the development of the front group and the rear end of the group of classmates to code standards and regulations were discussed for the file (or variable) name, code comments, spacing and indentation and so were the norm, the situation is still the team to execute code specifications can.

7. What have we learned? If history all over again, what would we do to improve?

• We learned a lot, the team members for the project development process have a deeper understanding and practical insights, for personnel required to develop a project, the tools and the division of labor have their own understanding. If history all over again, we would spend more time for more in-depth discussion of the details in the design phase, in order to avoid ambiguity affect the project development schedule.

Sixth, test / release

1, if there is a team test plan? Why not?

• There is a team test plan, each completed a module in the development process of the project are all tested, that have always been in the test. Since the app but not too perfect, just some very simple test to check the bug, so do not put out, planned in the late early 12 app perfected the black box testing.

2, whether formal acceptance testing?

• No formal acceptance testing, in some parts of the front and rear end is not yet fully consolidated, is expected to begin testing in early December.

3, the team tested whether there are tools to help test?

• Testing tools, is responsible for testing the students are expected with GT and itest, Jmeter performance test app, Android studio there are tools that can be optimized.

4, the team is how to measure and track the effectiveness of the software? From the results of the actual operation of the software, these tests work useful? What improvements should have?

• GT and itest these testing tools can test the app performance, GT is a portable app debugging platform, you can always view the debugging on your phone. The role of test work, because our app has a permanent background, power consumption and performance have been resident period must be taken into account and a certain degree of optimization. Improved local optimization of current thought is to reduce energy consumption.

5, which I found unexpected problems during the release of?

• Currently app has yet to release stage, the app is not expected to pack a big problem with Android studio comes with the packaging tools.

6, What have we learned? If history all over again, what would we do to improve?

• After dozens of days of staying up late a lot of teams from white to be responsible for front-end or back-end module of a certain, different players have learned, you learned how to set up the back-end database, how to achieve linkage through the interface and front-end, and to learn how to obtain real-time data from the cloud front-end players have had a lot of basic development projects, but also learned about many aspects of the logical call. If history all over again, then we will start early to develop our project, staying up late it is really painful ah.

Seven, the role of team management, cooperation

1, how each team is to determine the role, is not the best use?

• Our team is scheduled to determine the role of individual competence. Three girls in the front group of more skilled in terms of AS, assumed the task group within the front end portion; a rear end portion is held by some of the boys learning capacity is relatively strong, smooth cooperation between each other; documents, PPT, and other parts of speech Code can be relatively weak competition and the students have experience in this respect is completed.
• Overall, our team a clear division of labor, so that the best use.

2, there is help each other what among team members?

• Have. Our team is a large part of the project together (late at night) complete, problems arise in the process of completion of the project will directly ask the scene to solve; the difficulties encountered by the individual will be completed online communication (QQ spark that way)

3, when the issue of project management, cooperation appears, team members how to solve the problem?

• Our news team doing well in terms of cohesion, in addition to the technical aspects of the fact there is no question what the project management. The relationship between the members of each group are very close, very smooth progress of cooperation in communication, different groups experienced a run-in this period of time is also very familiar with each other, the process of cooperation is also very smooth.

4, each member represents a clear publicly thank the members of helpful (and write in their blog in):

• I thank my classmates Pan Haidong our help, because we recommend to Ali cloud server, helps us save time.

5. What have we learned? If history all over again, what would we do to improve?

• Through this alpha sprint, we are the team division of labor, management, cooperation learned: to be a division of labor based on each person's abilities and interests in the process of division of labor. As a team project, successful cooperation determines whether or not the project can succeed only everyone choose their own team orientation, their ability to play as much as possible, to let the whole team to achieve good results.
• If you choose again, then our choice will still be the case.

Eight, summary

1, do you think the current state of the team belongs grade CMM / CMMI in?

• The initial stage (initial)
  work disorder, the project process often abandon the original plan. Perhaps this is our team Alpha sprint time of the state, due to the pressure of other subjects and ddl, we select the team keep things simple, complex projects either deleted or thrown Beta sprint. The effectiveness of unstable development projects, the success of the project mainly rely on a few people have the ability (referred to as "thigh") experience and ability. Sprint hopes beta was only able to achieve repeatable level (Repeatable).

2, do you think the team is currently in its infancy / running / specification / create a stage which stage?

• In the specification stage
  I would like to go through the program and the Alpha team sprint, our team has been running pretty well, but for a good part of the team that everyone is responsible for the code does not deal with, or take time to achieve the "norm."

3, do you think this team compared to the previous milestone a milestone any improvement?

• Currently (alpha stage) compared to the previous milestone (needs analysis), the entire team got to communicate more, and we have been greatly improved in terms of technology, team collaboration capabilities better.

4. What do you think most need to improve aspects is?

• Technology is our most areas for improvement

5, the control principle of agile development, do you think your team is doing the best of which are several principles? Please list specific examples.

1. Business people and developers must work together every day in the project development process.

2. Whether inside and outside the team, face to face communication is always the most effective way to communicate.

• Our team are all together in most of the Alpha coding sprint man and discussion, this ratio hit each line of code efficiency is improved a lot.

1. Concise oriented - it is trying to simplify the art of unnecessary workload.

• Panel discussions will be completed before each function if this function is our body, we often talk about the original demand report writing function you do not need to have deleted.

Team photo

Respondent summary

Everyone on the team to assess the contribution of proportion to this assignment, workflow-oriented description of current work, the division of labor crew, crew workload ratio

work process

• Alpha leader determined for each phase must sprint to complete the task, and the division of labor;
• Division of labor arrangements for publicity, if the crew meaningful and constructive suggestions, then modify the corresponding part;
• Crew arrangements for the implementation of the division, part of their responsibility to deliver within the specified time;
• Head of the responsible person or aggregated, and were revised format.

Full name	Task Effort (60)	Individual participation (10)	Timely completion of (10)	Leader score (20)	Score (100)	Contribution ratio (%)
Enze	60	10	10	20	100	12.0
Autumn piano	60	10	10	20	100	12.0
Avon	60	10	10	20	100	12.0
Yu Hui	60	10	10	20	100	12.0
Yinshan	40	9	10	15	74	8.8
City Season	40	10	10	18	78	9.3
Jun Xi	50	10	10	17	87	10.4
Gimhae	50	10	10	17	87	10.4
Ya-hui	50	10	10	20	90	10.8
Wan Yee	10	0	2	5	17	2.0

This group obtained the scene of the respondent Score: remove the highest score, lowest score, averaging points (reserved a decimal)

Remove the highest score, lowest score, averaging share: 52.6

Other groups of collection issues raised by this group, and answer

Team to answer questions link

The first set of questions:

Q: The back end of the main algorithm can introduce it?

A: The back-end server is mainly built by Ali cloud, server push is achieved by pushing app integration Aurora, specific data analysis algorithm has not yet been perfected.

The second set of questions:

Q: For people who actually of little self-discipline, self-discipline is not more useless, the user will not guarantee?

A: We designed the app is mainly played a supporting role, is willing to enhance their healthy people can get feedback through our app, plus interactive pet, I believe there will be a lot of people like to try. As usefulness can not say that after using can change a person, this is a gradual process.

The third group of questions:

Q: How do the main interface is beautiful and perfect pet?

A: This course is achieved (xd) by pressing art.

The fourth group of questions:

Q: What do you intend to attract users?

答：app主打的自律牌相信本身就能吸引到一部分想改变自己的人，再加上可爱的界面和宠物也能吸引一些小姐姐。

第五组的提问：

问：希望可以设计宠物各个阶段的不同动画形态。

答：这个我们目前已经实现了，当然后续还会添加其它宠物的（再次压榨美工xd）。

第六组的提问：

问：宠物是动态还是静态的，如果是动态，是用gif还是3d引擎？

答：是动态的噢，目前是用gif实现，3d引擎的话目前能力有限以后会考虑的。

第七组的提问：

问：如果要常驻后台，耗电量能不能小一点？

答：首先我们是极不希望常驻后台的，目前还是在寻找方法来解决后台推送面临的问题。如果迫不得已要强制常驻后台的话，当然会尽可能减少耗电。

第八组提问：

问：对于一事手机自带的日历有日程提醒，你们这个项目的优势在哪呢？

答：优势在于人性化的提醒，不仅仅是自己设置日程，更带有暖心的日常提醒，也具有更大的灵活性。

第九组问题：

问：对于需要这个软件的用户来说宠物界面是否会太花里胡哨？

答：宠物作为主界面，我们设计的风格偏向简约的暖色调，不会设计的太花哨。后面也会继续完善。

第十一组问题：

问：宠物怎么动起来，不能是放gif吧？

答：目前使用gif，如果时间和能力允许，会改进。

第十二组问题：

问：你们打算如何实现宠物界面？是否使用图形学技术？

答：宠物现在已经使用gif实现，目前没有考虑使用图形学技术。

PSP与学习进度条

个人PSP

PSP2.1	Personal Software Process Stages	预估耗时（分钟）	实际耗时（分钟）
Planning	计划	15	5
· Estimate	· 估计这个任务需要多少时间	15	5
Development	开发	670	790
· Analysis	· 需求分析 (包括学习新技术)	20	50
· Design Spec	· 生成设计文档	0	0
· Design Review	· 设计复审	20	20
· Coding Standard	· 代码规范 (为目前的开发制定合适的规范)	10	10
· Design	· 具体设计	50	10
· Coding	· 具体编码	540	640
· Code Review	· 代码复审	20	30
· Test	· 测试（自我测试，修改代码，提交修改）	10	30
Reporting	报告	25	30
· Test Repor	· 测试报告	10	10
· Size Measurement	· 计算工作量	10	10
· Postmortem & Process Improvement Plan	· 事后总结, 并提出过程改进计划	5	10
	合计	710	825

个人学习进度条

第N周	新增代码（行）	累计代码（行）	本周学习耗时（小时）	累计学习耗时（小时）	重要成长
1	103	103	14	14	学会了十三水的玩法，对原型设计有了一定的基础
2	400	503	10	24	学习C# winform开发，完善具体设计思路
3	1313	1816	30	54	实现核心算法“自动分牌”
4	1153	2969	22	76	界面设计与代码实现，完成各窗体与接口的实现
5	0	2969	15	91	详细了解商业计划书以及产品介绍视频的制作
6	0	2969	20	111	学习了UML类图的绘制，了解需求规格说明书的书写
7	120	3089	5	116	学习了Android Studio，查资料能力增强，对算法有了一定的框架
8	730	3819	25	141	对Android的API调用，服务器部署，spring框架
9	400	4219	15	156	算法设计，API 完善
10	120	4339	14	170	数据分析，Beta整合