This Meeting

1. Overall, the team found that the Test Plan is not detailed enough.  It is still very preliminary.
2. The Test Plan doesn't mention Booch method at all. 
3. It seems to the team that the Test Plan doesn't follow on from the SADD and SDD.
4. The format of the document doesn't follow the standards of other HTML documents.
5. There will be no such thing as "Test Manager"
6. There should only be one maintainer: Long Tang
7. The Test Plan mentioned 'Preliminary Test Plan', which never exist.  The final Test Plan evolved from the preliminary Test Plan, but at the end the team will only have one document, Test Plan.  The team will still need to mention something about the Preliminary Test Plan, not as a separate document but on how it evolves to produce the team's Test Plan.
8. It might be a good idea in the introduction to add these:
• How each sections are split up and what each section is all about
• Have Booch reference
9. Under each major heading, it will be good to have a description of what it is all about.
10. Consistency on naming the team.  It should be K-Team and not Team K
11. Java is not built in an object oriented manner.  Discard paragraph #4 of Intoroduction.
12. Replace sub-systems as modules.
13. "Equivalent classes" - this term just popped up from nowhere.  A detailed explanation of what it is will be essential.
14. Explanation of thread based testing.  The thread based testing should follow the scenario diagrams described in the SADD and SDD.
15. It might be a good idea to mention and describe what the team will do when a test fail.
16. Allocation of testers will be in meetings, during task allocations.
17. In Section 2, it says:  Integration testing is only conducted on those classes, more specifically class' attributes and methods that have already passed the unit testing.  This is not right.  Unit testing can only be done on classes and not on methods and attributes.  A class is made up of attributes and methods.  This sentence will have to be re-phrase. 
18. For the tables, instead of having ???, it will be better if the team put an actual example table.
19. Integration testing - might be a good idea to have the test ID the same as the use-cases  ID because they are threads.  Unit testing - takes class references from the SADD and SDD.
20. The Test Plan is missing steps for installation testing.
21. Section 3: UNIT TESTING
• Put Unit Testing before Integration Testing
• A better description of the critical and non-critical units is needed
• Section 3.1 - needs to be changed completely
• Section 3.2 - OK
• Section 3.3 - replace 'Test Manager' as 'Tester'
• Section 3.4 - in the 'Name of Tester' field, discard 'compulsary'.  Another table will probably be needed to describe any failures that may occur while tests are conducted.
• Replace structure diagrams to flow charts.
• Section 3.9 - Code inspection is to be done by someone other than the author.