I just came back from a meeting with assessor Wan Rohania. Me and Sean went booked a slot each to ask a few FYP documentation related questions. Here’s some tips for your docs.

1. The preliminary investigation chapter, just write an overview of everything. Kind of like your PSF but a little bit more detailed.

2. For the analysis chapter, primary research is all non IT related (means your business flow, content info, gaming idea and bla bla) Secondary research is all your technical research (which includes your programming language, algorithms, hardware and bla bla) For the comparison of programming language, methodology and process, only put your critical evaluation. There is no need to explain each and every programming language, methodology and process.

3. For the design chapter, chuck a bit of crap in, if your are using UML, and reusing some design patterns, you can put it in this section.

4. For the construction chaper, Wan Rohania said to put some important codes samples in, (e.g. some ‘chun’ted algorithm that you have coded) Screen design can be shown here also. If you are reusing certain modules (like me, I’m using available open source PHP forum source codes) that you did not code yourself, you have to state it here too.

5. Testing phase , not all test plan is needed. Just pick the important modules and show the various tests you did on that module.

6. Critical evaluation is the most important chapter. Here, Wan Rohania just said just write your story book and the ‘Making and process of finishing your FYP’. Put your coding experience, research experience, stuff u encountered, how you over come your problems and bla bla.

*extra tip. Cut the crap, write what is only needed. If your documentation is still over 30,000 words in the end, try putting the less important stuff in the Appendix.

IM or email me if you have other questions. Need some sleep...so tired...going to watch Troy later.