The calculation method. It's always a good idea to give examples, which can be used as test cases. You can't inspect quality into a product at the system testing phase. The quality needs to be there right from the start of development. At the module level its good practive to document exactly what was done to prove that the module does what the specification says it should.
Positive testing is important but more important for robust software is the negative testing.
Checking that the system satisfies all of the requirements specify in the analysis report. You'd be suprised how many people call meetings and don't specify what the purpose of the meeting is. For a meeting to be effective there should always be an agenda which the chairman sticks to. Again if you're going to have a meeting its important to document what decisions were made and reasons behind them. Also action points need to be assigned so that progress is made.