Week 12

Approximately 15 hours this week.

Put main effort in documentations this week. Had a discussion with Jeff about the details of the technical documentation and continued working on it. About 85% of the documentation is done. I also took some screen shots of the client user interface and give them to Allen to do the User Manual.

In terms of coding I did much testing and debugging and removed several bugs. Also added a new simple algorithm to calculate the accomplishment value based on the scores of the user. I think the current release of the program is ready for the tradeshow now.

Powerpoint slides were also created and submitted.

Week 11

Approximately 15 hours this week.

Code is near finished. Main job done this week was to

1. implement result data structure and combine it to the question class, so the system is able to record the result of a test / exam
2. re-implemented the SLOT and SIGNAL system of the question class, so the UI automatically switches between Quick test interface and Exam interface (slightly difference with different features supports)
3. saving of test result as a text file and store it to the current directory.

In addition, I also got the poster printed, and half of the technical documentation done. Includes a page for introducing the changes we’ve made since the release of preliminary documentation.

Week 10

Spent over 25 hours this week (including recess week)

Code part:

Basically fixing problems due to the newly added class in week 8. Implemented a new algorithm to select questions from different categories. The rule works as follows:

Minimum question number for a quick test is 30 (too small number leads to poor effect of exercise). Maximum number set to 200 (to prevent from exceeding the total number of questions in database). For each selected category, select one question of this category and put it in the sub list. Repeat this step until we fill up the sub list with the specified list size. If we run out of questions of a single category during allocation, then add one more question from the next category. If necessary shrink the total size of the list.

I also spent some time in implementing a method to traverse a question list. It turned out to be non-trivial as users may go to the next or previous question any time.

Much time was spent on implementing these algorithms and testing to make sure they work fine.

Added a test result form for simulation exam, which is rather simple.

Another main feature implemented is the saving of quick test by saving the current state of the user. User can load his last saved test and continue the test anytime.

 

Documentation part:

Working on the UML model, and continue the technical documentation.