Sleep Monkey--alpha Phase project summary

Vision and Objectives

1. What problems does our software solve? Is it clearly defined? Do you have a clear description of typical users and typical scenarios?

For the vast number of people suffering from insomnia, especially the program ape users insomnia problem. Defined clearly. has been described.

2. Do you have enough time to plan?

Have half a day to make plans.

3. How does the team solve the different opinions of their colleagues about the plan during the planning phase?

To seek common ground, to discuss different opinions, and to make a full-hearted effort to reach the results.

Plan

1. Have you finished your original work? If there's anything unfinished, why?

Basically in line with the original design, some projects have simplified functionality due to technical problems.

2. Did you find that you did something that didn't seem necessary or valuable afterwards?

There are, for example, parts of the team that have functional repetition that need to be realized, and the learning process wastes time and effort.

3. Is there a clearly defined and measurable deliverable for each task?

Most of them, some because of technical problems and did not make specific requirements.

4. Is the whole process of the project in accordance with the plan?

Most of them follow the plan, and there are some technical problems that have changed the design in the middle.

5. Are there any buffers left in the plan, and does the buffer function?

There are buffers that are useful. Due to the lack of technology, to a large extent in the original period of time there are functional defects, buffer exists to solve a lot of problems.

6. What changes will be made to future plans?

The length of the buffer should be clarified and more specifically designed and partitioned.

Resources

1. Do we have enough resources to complete the tasks?

In many cases, it takes a lot of time to set up icons and pictures.

2. How is the time and other resources required for each task estimated and how accurate?

The beginning of the precision is very rough, and later with the project task of aggravating, we are only to work, no time to consider the problem of precision.

3. Is the user testing time, manpower and software/hardware resources sufficient?

Not enough, the financial situation of the students determines that our applicable models are limited.

4. Do you feel that what you do can be done by others (more efficient)?

Although the task is divided according to the function page, but the personal page icons and other landscaping work is not good, need full-time art.

Change Management

1. Every relevant employee is informed of the change in time?

As everyone was in the same dorm, the news spread faster.

2. What approaches have we adopted to determine the "deferred" and "must be" functions?

Members of the group recognize the features that must be implemented, as other functions are erected on top of them.

3. Are the export conditions (exit criteria) of the project clearly defined?

We don't know what "export conditions" are, and we don't use them in this project.

4. Can a contingency plan be developed for possible changes?

Basically no, then randomly arrested on top.

5. Are employees able to effectively handle unexpected job requests?

Inevitably there will be other subjects of homework to be completed, of course, the completion is still to be completed, there is buffer space to do the adjustment.

Design/implementation

1. When and by whom is the design work done? Is it the right time for the right person?

The design process was attended by all members, and the depth of the design was reasonable. are more appropriate.

2. Is there any ambiguity in the design work and how does the team solve it?

The main thing is to look at the efficiency of the implementation, if there is really ambiguous situation need to weigh, usually choose easy to achieve one, after all, everyone's time is not rich.

3. Does the team use unit test, test-driven development (TDD), UML, or other tools to help design and implement? Do these tools work?

Using unit tests, the overall view of the bug is not many. It is not implemented using test-driven development (TDD), UML, and other tools.

4. What features produce the most bugs, why?

Statistical functions require large amounts of data access and analysis, as well as bugs.

5. How is code Review performed, and is code specification strictly enforced?

There are not enough people in the group to review the code, strictly enforcing the code specification.

Test/Release

1. Does the team have a test plan? Why not?

We have a test plan.

2. Have you conducted a formal acceptance test?

It was done, but it didn't pass.

3. Does the team have testing tools to help test?

No.

4. How does the team measure and track the performance of the software? Is it useful to see how the software actually works? What should be improved?

Less people, more things, efforts to achieve the function, but no attention to performance.

5. What unexpected problems were found during the release process?

There was a flashback on some of the models that had not been encountered before.

Sleep Monkey--alpha Phase project summary