Final review report on online exam system

Project: Online test system

Group name: Golden State Warriors

Group leader: Yin Liangliang

Members: Teshritu, Hanbin, Hao Nan

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?

The online examination of the students makes the traditional cumbersome examination process easier. The definition is clear. Typical users are teachers and students, and typical scenarios are exams.

2. Do you have enough time to plan?

There is plenty of time to plan, but the plan will change as the project progresses.

3. How does the team solve the different opinions of their colleagues in the planning phase?

The discussion of different opinions will be decided by the team leader in the end.

Plan

1. Has the original work been done in the end? If there's anything unfinished, why?

All the work in the plan has been completed.

2. Have you found something that did not seem necessary or valuable afterwards?

No.

3. Are deliverables clearly defined and measured for each task?

Basically no, is the task completed after the completion of the results of the decision, if the leader decides can be delivered.

4. Is the whole process of the project carried out according to the plan?

Yes, there are some changes planned in the process, but they all follow the plan, and the tasks in the plan are all done.

5, in the plan to leave a buffer, buffer function?

The first half of the buffer is not set and the second half leaves the buffer. The buffer zone gives you a better adjustment to the corresponding task.

Resources

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

There are plenty of resources and the areas where you want to improve later are well done.

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

Early in the project is a rough estimate, the second part of the project is based on the team members prior to the completion of the task to estimate, relatively early and more accurate.

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

Enough.

Change Management

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

The change of the message has the leader of the team directly informed to each member, more timely.

2. What methods have we adopted to determine the "delayed" and "must be" functions?

Group to be discussed and ultimately decided by the team leader.

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

Yes. But part of it is a temporary adjustment made after the change.

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

For unexpected job requests, the number of occurrences is not many, but the team members completed the situation better.

Design/ Implement

1, when the design work, by whom to complete? Is it the right time for the right person?

The design work was initially discussed by the group, and the post-adjustment was completed by the team leader. Is the right time for the right person.

2, the design work has encountered ambiguous situation, how to solve the team?

Yes. There is a group discussion, the leader decided.

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

No.

4, what function produces the most bugs, why?

In the current bug report, each part of the bug is similar!

5, code Review How to do, whether strictly enforce the code specification?

The implemented features are reviewed by peers to see if the code is incorrect or can be improved, but the code specification is not strictly enforced.

Test/Release

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

There is a complete test plan.

2. Have you conducted a formal acceptance test?

Acceptance of the test but not formal.

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

No.

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

No performance tests were performed.

5. What unexpected problems were found during final release?

Because the final release has a pre-walkthrough, the release process is relatively smooth, but there is a slow server situation, fortunately, the publisher is a good solution.

Final review report on online exam system